Re: site.xml inheritence

[Phil Steitz]

Better links (specifying svn revision numbers, so links are stable)


Parent pom:
http://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox/pom.xml

http://svn.apache.org/viewvc/jakarta/commons/trunks-sandbox/pom.xml?revision=437831

Parent site.xml:
http://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox/src/site/site.xml

http://svn.apache.org/viewvc/jakarta/commons/trunks-sandbox/src/site/site.xml?revision=430908

Child pom:
http://svn.apache.org/repos/asf/jakarta/commons/sandbox/csv/trunk/pom.xml

http://svn.apache.org/viewvc/jakarta/commons/sandbox/csv/trunk/pom.xml?revision=430702

Child site.xml:
http://svn.apache.org/repos/asf/jakarta/commons/sandbox/csv/trunk/src/site/site.xml

http://svn.apache.org/viewvc/jakarta/commons/sandbox/csv/trunk/src/site/site.xml?revision=437546

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: site.xml inheritence

[Phil Steitz]

On 9/8/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote:

I've already read that,
there is no example of the child module's site.xml in there.
I've been trying for ages to get the child module's site.xml to inherit
the parent's site.xml (which is also the parent pom of it's own pom) and
add a few links, with no luck.


Here is an example, which is in development and will likely change
(possibly to remove the site inheritence).  As of now, though, it does
illustrate how menus, links and style info can be inherited.

Parent pom:
http://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox/pom.xml
Parent site.xml:
http://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox/src/site/site.xml
Child pom:
http://svn.apache.org/repos/asf/jakarta/commons/sandbox/csv/trunk/pom.xml
Child site.xml:
http://svn.apache.org/repos/asf/jakarta/commons/sandbox/csv/trunk/src/site/site.xm

Installing or deploying the parent POM also deploys/installs the
parent site descriptor.  There is no reference to the parent in the
child site.xml.  Apparently, inheritance is triggered by the POM
dependency.  In the example, the child is not defined as a module of
the parent, but it used to be and that worked as well.  It could be
that in that case you need to do something like "mvn -N deploy" or
"mvn -N install" from the parent to get the parent descriptor
installed before building the child.

Style info, links and a menu are inherited in the example.  The inherited menu

uses the inherit attribute for positioning, as mentioned in the docs.

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: site.xml inheritence

[Phil Steitz]

On 9/7/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote:

Are there any examples of this available?

The docs doesn't show how to make a module site.xml "extend" from the
parent project's site.xml.





Have a look at the "inheritence" section in the site plugin howto:
http://maven.apache.org/plugins/maven-site-plugin/howto.html
As stated in the docs, when you publish the parent POM, the site
descriptor is also published and available for inheritence, as long as
the child inherits the parent POM.

Hope this helps.

Phil

--




With kind regards,
Geoffrey De Smet


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m1] Problems resolving external dtd reference

[Phil Steitz]

Lukas Theussl wrote:

This is a known issue: http://jira.codehaus.org/browse/MPXDOC-179

For stand-alone projects, you can make it work by specifying an absolute 
path for the external entity, but this will not work in a multiproject 
set-up. Otherwise, I'm afraid I can't offer anything else right now.


Thanks.  Unfortunately absolute path will not work for this. It is odd, 
though, that I am using the same version (1.9.2) of the xdoc plugin in 
both cases and it only fails under 1.1-beta-2. Must be the parser or 
something to do with the context that the plugin gets the resource.


I am interested in others' approaches to handling common menus shared by 
multiple projects.  I don't like the entity reference approach that we 
use in commons now and am thinking about writing a plugin to do things 
in a cleaner way.  I would be interested in ideas on how best to 
approach this.


Phil


-Lukas


Phil Steitz wrote:

After installing 1.1-beta-2, the following external reference 
(included in navigation.xml files) that we use to include common menus 
on the Jakarta Commons sites is no longer working:


'../../commons-build/menus/menus.dtd'>


The xdoc plugin generates the following error:

Relative URI '../../commons-build/menus/menus.dtd' cannot be resolved 
without a base URI.


Any ideas how to work around this?  Any better ideas on how to include 
common menus and portions thereof on multiple sites?  The commons 
sites indivdual navigation.xml files refer to entities defined in the 
dtd referenced above, so common elements can be maintained in one place.


Thanks in advance.

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[m1] Problems resolving external dtd reference

[Phil Steitz]

After installing 1.1-beta-2, the following external reference (included 
in navigation.xml files) that we use to include common menus on the 
Jakarta Commons sites is no longer working:


'../../commons-build/menus/menus.dtd'>


The xdoc plugin generates the following error:

Relative URI '../../commons-build/menus/menus.dtd' cannot be resolved 
without a base URI.


Any ideas how to work around this?  Any better ideas on how to include 
common menus and portions thereof on multiple sites?  The commons sites 
indivdual navigation.xml files refer to entities defined in the dtd 
referenced above, so common elements can be maintained in one place.


Thanks in advance.

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to add to local repository

[Phil Steitz]

Siegfried Heintze wrote:

I just corrected the groupid for the htmlparser I proposed for upload into
ibiblio. Now how do I use this jar file while I'm waiting for carlos to put
it in ibiblio?

Could someone kindly point me to the URL for the documentation on how to add
a third party jar file to one's own repository for m1 and m2?


For m2:

http://maven.apache.org/guides/mini/guide-installing-3rd-party-jars.html

In m1, I know of no other way than to hack the repo file structure or 
build locally and jar:install.


Phil



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ant plugin doesnt work?

[Phil Steitz]

Arnaud HERITIER wrote:

Hi Phil,

[SNIP]

Thx for the summary.




If what you want is to get the plugin to generate a build 
script with a different default value for libdir, I do not 
think that is possible now.  One improvment that might make 
sense would be to at least have it use ${maven.repo.local} 
instead of ${user.home}/.maven/repository in the template.



We setted libdir to ${user.home}/.maven/repository instead of 
${maven.repo.local} to not use maven properties in the generated ant
script.


Sorry, what I meant was to have the plugin grab the *value* of 
${maven.repo.local} and put that into the generated script by default.


Phil


Arnaud




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: ant plugin doesnt work?

[Phil Steitz]

Looks like we may have a misunderstanding here.  The maven.ant.use.properties 
property just controls whether the generated ant build file will look for 
user-defined properties when it runs (under Ant).  It just adds


to the top of the file.  A property *exposed*  by the plugin-generated script 
is ${libdir}, which takes as its default value ${user.home}/.maven/repository.  
 So to get Ant to use a libdir different from the default, you have to do as 
Arnaud suggests, set maven.ant.use.properties to true (which I think is the 
default, btw) and put a build.properties file with libdir=whatever-you-want in 
a location where the Ant script can find it when it executes.
 
If what you want is to get the plugin to generate a build script with a 
different default value for libdir, I do not think that is possible now.  One 
improvment that might make sense would be to at least have it use 
${maven.repo.local} instead of ${user.home}/.maven/repository in the template.
 
hth,
 
Phil

-Original Message- 
From: m h [mailto:[EMAIL PROTECTED] 
Sent: Tue 9/6/2005 2:32 PM 
To: Maven Users List 
Cc: 
Subject: RE: ant plugin doesnt work?



Thanx for the quick reply.  Yes, I am using 1.0.2.  I
shoudl be able to specify maven.ant.use.properties int
the project.properties file, correct?

Also, the doc on the website says this is supposed to
be the default behavior.  Furthermore,that commandline
doesnt produce the desired result.

We have a picky client who doesnt want deps
downloaded.  Otherwise we wouldnt be modifying the
properties. ;)

mike



--- Arnaud HERITIER <[EMAIL PROTECTED]> wrote:

> You are using maven 1.0.2 ?
>
> "maven ant -Dmaven.ant.use.properties=true" should
> create the build.xml in your project's root
> directory.
>
> Then in your build.properties (stored in your
> project's root dir or in your user's home dir) you
> should set the properties for the
> script :-(
>
> Arnaud
>
> >
> > Hi all
> >
> > Im trying to produce an ant build.xml that works.
> I put a
> > build.properties file in my project base dir that
> specifies
> >
> > libdir=somedir
> >
> > but when I do maven ant, the libdir is not set to
> my
> > specification.   I have tried moving the
> > build.properties file to my home dir, and I have
> tried
> > setting the maven.ant.use.properties=true (even
> though this
> > is the default).
> >
> > When I run with the -X option, the output
> indicates that the
> > file is being used, however this is not backed up
> by what I
> > see in the resulting build.xml.
> >
> > Please advise.
> >
> > Thank you.
> >
> > __
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> protection
> > around http://mail.yahoo.com
> >
> >
>
-
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> >
>
>
>
>
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiproject site navigation question

[Phil Steitz]

Wendy Smoak wrote:

From: "Jay H. Hartley" <[EMAIL PROTECTED]>


You mention that you "need" to have the documentation as part of the root
web site. Would having it one link down but clearly labeled at the top of
the sub-project list satisfy the need?



No, the files really need to be up at the top level.  I'm integrating 
the existing Struts site into the Maven-generated multi-project site, 
and I don't want to break all the links that are already out there.  
It's looking good so far... I just wanted to be sure I wasn't doing more 
work than necessary in navigation.xml. :)


Another multiproject site question:  Is there a way to override the 
directory name that 'multiproject:site' comes up with for each 
subproject? It seems to be coming from the  tag in project.xml.  
Some of the s don't match the directory names we've been using for 
those projects, but they are correct for use in the .jar file name.


For example, the Struts Flow website is http://struts.apache.org/flow, 
yet its  is 'struts-flow'.  Once the documentation gets pushed down 
under /struts/current/flow/xdocs, I need to retain the directory name 
for the website, yet the .jar file needs to be struts-flow-x.x.x.jar.


There's a property for everything else. :)  But I don't see anything 
relevant on http://maven.apache.org/reference/plugins/site/properties.html


Is this possible to override, or is the answer possibly as simple as a 
postGoal to rename the directory?


No, there is no way to override this.  The multiproject plugin creates 
the directories in a loop over subprojects, using the artifact id to 
name each directory.


Using a postGoal to multiproject:site to rename should work, assuming 
you are specifying your own nav's.


Phil



Thanks,



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiproject site navigation question

[Phil Steitz]

Wendy Smoak wrote:

From: "dan tran" <[EMAIL PROTECTED]>


Wendy, from maven-site-plugin doco, you dont create nagivation.xml at
the root.  Let the multiproejct:site generate it for you.



I have a bunch of  "user-supplied documentation" that I need to link in, 
and I need it to be part of the root website.  AFAICT, to do that I need 
to make a navigation.xml file.  True?


Thanks,


FWIW, I struggled with this on a couple of projects and ended up finding 
it easier and more flexible to just maintain navigation.xml at each 
level.  One thing that can make it slightly easier to manage the common 
elements (assuming you have these) is to use XML entities.  Have a look 
at the commons-build project 
 
that defines a setup shared by Jakarta Commons components. The 
navigation.xml file there and in all of the commons subprojects refer to 
an external dtd that defines xml entities corresponding to the shared 
menu items.  This is a little convoluted - maybe not maven "best 
practice" - but works and is not that hard to maintain once you have it 
set up.


Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m1] Keeping plugins up to date

[Phil Steitz]

Grant Ingersoll wrote:

Yeah, I did that which is fine when you know the specifics of what you
want to update.  I will see if I can come up w/ some script that does it
for me.  


Problem I had was I had a few developers who didn't have the same
version of the jar-plugin, and were seeing different results.  Being
able to validate that everyone has the same plugins (and update) would
be useful, I think


maven --info will display version numbers for installed plugins, if that 
helps.


Phil


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: combining multiproject javadocs

[Phil Steitz]

Andrei Szabo wrote:
Hello,
I’ve been looking around the archives for an answer to
this question, but couldn’t find any decent answer,
although the same question surfaced several times.
I have a project which has several sub-projects.  I
want to be able generate one set of Javadocs that
combines the Javadocs from all the sub-projects. Is
there an easy way to do this with maven (something
that doesn’t require me to write a custom plugin or
use some weird jelly scripting)? I found several ways
of achieving the desired result, but they all seem
like “hacks” to me and I’d like to know if there is
any elegant solution to this problem :)
The svn-head version of the dist plugin will do this.  If you want to do 
it as part of site generation and don't want to build and use the 
svn-head dist plugin, you can borrow the following "weird jelly 
scripting" from the plugin source:


   
  
   
   
 
   
 
   

Though I have not tested this exact setup, it should work to wrap this 
in , changing the first line above to
.

I know the following example works as presented, where naming-xxx are 
the subprojects.



  
  
  
  
  
  
  

  

  

  
hth,
Phil
Thanks a lot,
Andrei.

		
__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to get LICENSE.txt included in jars generated by (generated) ant build.xml

[Phil Steitz]

I need to make sure that LICENSE.txt is included in the META-INF of jars 
generated both by maven's jar plugin and by the build.xml generated by 
ant:generate-build.  If I include LICENSE.txt as a resource in 
project.xml explicitly, this works to get it into build.xml, but causes 
the maven jar plugin to add two copies of the file (with different 
dates).  Is there a simple way to do this?

-Phil
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: CheckStyle and Multiproject plugin?

[Phil Steitz]

I don't know exactly what causes this problem, but I suspect it is the 
old properties file format.  I eliminated this problem by removing all 
checkstyle.properties files from subprojects, putting an xml-formatted 
checkstyle.xml file in the top level project directory and setting 
maven.checkstyle.properties=checkstyle.xml in the top level project.xml 
and maven.checkstyle.properties=${basedir}/../checkstyle.xml in the 
subprojects project.xml files.

Phil

Eric Pugh wrote:
Hi all,

when running the maven multiproject plugin, any project with checkstyle as a
report fails:
BUILD FAILED
File..
file:/c:/java/maven/plugins/maven-multiproject-plugin-1.1-SNAPSHOT/
Element... maven:reactor
Line.. 69
Column 7
Unable to obtain goal [site] --
file:/c:/java/maven/plugins/maven-checkstyle-plu
gin-2.1-SNAPSHOT/:127:65:  Unable to create a Checker:
unable to
 parse C:\clients\Upstate\catalog\project.properties - Content is not
allowed in
 prolog.:1:1
Total time: 22 seconds
Finished at: Sun Sep 28 17:35:00 CEST 2003
What is this content is not allowed in prolog error that I keep getting?

ERic Pugh

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Performance Test Plugin?

[Phil Steitz]

Has anyone written a performance test plugin for Maven?  What I am 
looking for is something that runs Junit tests repeatedly and 
accumulates basic statistics on test case performance.

Phil



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: linkcheck plugin questions

[Phil Steitz]

Ben Walding wrote:
Phil Steitz wrote:

Two questions:

1. Does this plugin have a properties file?  If so, where can I find 
an example/docs?


Not really, you can control it marginally using properties found at
http://maven.apache.org/reference/plugins/linkcheck/properties.html
What kind of control were you looking for?
Things like configuring a timeout.

Ignore maven.linkcheck.enabled, it is out-of-date

2. Does the plugin require " or ' in href's -- i.e., can it handle 
things like  or does it need http://www.apache.org";> ? 


This would be a function of what tidy can do. If tidy can fix your bogus 
html with bad attributes, then linkcheck will validate it.  Couldn't 
tell you offhand.  Fixing the html would be a good start.
Thanks.

Cheers,

Ben

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

linkcheck plugin questions

[Phil Steitz]

Two questions:

1. Does this plugin have a properties file?  If so, where can I find an 
example/docs?

2. Does the plugin require " or ' in href's -- i.e., can it handle 
things like  or does it need http://www.apache.org";> ?

thx,

Phil



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]