commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann" <jochen.wiedm...@gmail.com>
Subject Re: Release of Commons POM?
Date Sat, 07 Oct 2006 20:01:41 GMT
On 10/7/06, Phil Steitz <phil.steitz@gmail.com> wrote:

> >   Therefore, I propose to replace
> >       <resources>
...
> >       </resources>
> >   with
> >       <plugin>
...
> >         <artifactId>maven-antrun-plugin</artifactId>
...
> >       </plugin>
> >
> +1

Done.


> > There is one additional issue, which I do have myself. Checking out
> > the trunks-proper directory  in order to edit the POM will typically
> > result in checking out all of jakarta-commons. Obviously, that's not
> > what I want. Therefore, I propose to create a module
> > commons/commons-parent, change the pom's artifactId from "commons" to
> > "commons-parent" and move the POM to that place.
> >
> +1

I'll wait some more days before doing that. If noone intervenes, I'll
proceed next week.


> I would also like to find a way to decouple the inherited site
> elements from the parent POM.  The current setup will publish the
> parent site metadata with the POM, so site l & f changes will require
> re-release of the POM, which I don't like.  Is there any way to
> accomplish this other than to create commons-site and then all the
> foo-sites separately?

I don't know, what you are referring to? Neither the commons parent
POM nor the Apache POM contain configuration of reports and/or site
plugin?

Jochen

-- 
My wife Mary and I have been married for forty-seven years and not
once have we had an argument serious enough to consider divorce;
murder, yes, but divorce, never.
(Jack Benny)

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message