commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Sanchez <car...@apache.org>
Subject Re: Maven build fixes affecting almost all projects
Date Tue, 08 Nov 2005 18:10:49 GMT
About adding SNAPSHOT the reason is the same as other people has
already given. I looked in the properties files and tried to guess the
right version which is currently in development, other people will
know better than me. The rule is if last version released was 1.0 it
should be 1.0.1-SNAPSHOT, unless explicitly working towards 1.1, which
would be 1.1-SNAPSHOT.

On 11/8/05, Dion Gillard <dion.gillard@gmail.com> wrote:
> Questions:
>
> 1) The javadoc dependency in attributes/compiler/project.xml has been
> commented out. Why?

The better way I can think about to fix this is adding tools.jar as a
dependency, and overriding it in the project.properties.
Something like
maven.jar.override=on
maven.jar.tools=${java.home}/../lib/tools.jar

> 4) betwixt/project.xml has a change which places a directory element
> inside an includes element. According to the docs on
> http://maven.apache.org/maven-1.x/reference/project-descriptor.html#class_UnitTest
> this is not correct.

I just moved up the includes, but yes the directory is not needed
there. It doesn't break under the xml schema though.


> 7) chain/apps/mailreader/project.xml  changes do not fix the bad
> resource elements, they simply remove them.

They are already under the right <resources> tag at the end of the pom

>
> On 11/6/05, Phil Steitz <phil.steitz@gmail.com> wrote:
> > On 11/2/05, robert burrell donkin <robertburrelldonkin@blueyonder.co.uk> wrote:
> > > On Tue, 2005-11-01 at 11:16 +1100, Dion Gillard wrote:
> > > > Carlos, I think we the developers should work with you on this one.
> > >
> > > +1
> > >
> > > probably more effective that way
> > >
> > > but i'm comfortable about proposing commons karma for any existing
> > > apache committer who wants it.
> >
> >
> > I have taken a look at Carlos' patch and what it does is:
> >
> > 1) Change all current development version specs from -dev to -SNAPSHOT
> > 2) Introduces artifactId, groupId (in some cases, not everywhere?)
> > 3) Introduces scope tags for dependencies (in some cases)
> > 4) Eliminates some (unused?) resources elements from chain's build section
> > 5) Eliminates empty id, organization, email from contributors
> >
> > None of these look (to me) like they will affect builds or cause
> > problems.  We should probably all agree that we want to follow the
> > "maven way" in 1); though and test all of the builds before
> > committing.  I am willing to test all of the builds and then commit if
> > others are OK with this.  If I hear no objections, I will do this in a
> > couple of days.  In the mean time, it would be good for a [chain]
> > committer to look at the mods to there.
> >
> > Thanks, Carlos.
> >
> > Phil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
>
> --
> http://www.multitask.com.au/people/dion/
> "You are going to let the fear of poverty govern your life and your
> reward will be that you will eat, but you will not live." - George
> Bernard Shaw
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
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