You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Carlos Sanchez <ca...@apache.org> on 2005/11/01 00:46:44 UTC
Maven build fixes affecting almost all projects
Hi,
I've been working on fixing the maven project.xml files so they work
with maven 1.1 too and to improve the future releases and possible
upgrade to maven 2.
I don't have rights in the commons svn, so I'd like to know if you
prefer a patch for everything as a bugzilla issue, separated patches
(this would be a PITA), or just a mail attachment.
These patches include:
- fixing xml according to schema
- use of "version-SNAPSHOT" instead of "version-dev"
- adding some helper tags to improve the m1 pom conversion to m2.
Regards
Carlos Sanchez
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Maven build fixes affecting almost all projects
Posted by Carlos Sanchez <ca...@apache.org>.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37314
On 10/31/05, Dion Gillard <di...@gmail.com> wrote:
> Post away...
>
> On 11/1/05, Carlos Sanchez <ca...@apache.org> wrote:
> > It's 30KB. I haven't changed dependencies or anything related directly
> > to the projects and their functionality, mainly syntax fixes, that's
> > why I took the responsability of doing it at a time instead of one at
> > a time.
> >
> > I can send the patch if you think is not too big for the mailing list.
> >
> > On 10/31/05, Dion Gillard <di...@gmail.com> wrote:
> > > Carlos, I think we the developers should work with you on this one.
> > >
> > > Post the patch as an attachment here so we can all look at it. How big is it?
> > >
> > > On 11/1/05, Carlos Sanchez <ca...@apache.org> wrote:
> > > > Hi,
> > > >
> > > > I've been working on fixing the maven project.xml files so they work
> > > > with maven 1.1 too and to improve the future releases and possible
> > > > upgrade to maven 2.
> > > >
> > > > I don't have rights in the commons svn, so I'd like to know if you
> > > > prefer a patch for everything as a bugzilla issue, separated patches
> > > > (this would be a PITA), or just a mail attachment.
> > > >
> > > > These patches include:
> > > > - fixing xml according to schema
> > > > - use of "version-SNAPSHOT" instead of "version-dev"
> > > > - adding some helper tags to improve the m1 pom conversion to m2.
> > > >
> > > > Regards
> > > >
> > > > Carlos Sanchez
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> >
> >
>
>
> --
> 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
Re: Maven build fixes affecting almost all projects
Posted by Dion Gillard <di...@gmail.com>.
Post away...
On 11/1/05, Carlos Sanchez <ca...@apache.org> wrote:
> It's 30KB. I haven't changed dependencies or anything related directly
> to the projects and their functionality, mainly syntax fixes, that's
> why I took the responsability of doing it at a time instead of one at
> a time.
>
> I can send the patch if you think is not too big for the mailing list.
>
> On 10/31/05, Dion Gillard <di...@gmail.com> wrote:
> > Carlos, I think we the developers should work with you on this one.
> >
> > Post the patch as an attachment here so we can all look at it. How big is it?
> >
> > On 11/1/05, Carlos Sanchez <ca...@apache.org> wrote:
> > > Hi,
> > >
> > > I've been working on fixing the maven project.xml files so they work
> > > with maven 1.1 too and to improve the future releases and possible
> > > upgrade to maven 2.
> > >
> > > I don't have rights in the commons svn, so I'd like to know if you
> > > prefer a patch for everything as a bugzilla issue, separated patches
> > > (this would be a PITA), or just a mail attachment.
> > >
> > > These patches include:
> > > - fixing xml according to schema
> > > - use of "version-SNAPSHOT" instead of "version-dev"
> > > - adding some helper tags to improve the m1 pom conversion to m2.
> > >
> > > Regards
> > >
> > > Carlos Sanchez
> > >
> > > ---------------------------------------------------------------------
> > > 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
>
>
--
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
Re: Maven build fixes affecting almost all projects
Posted by Carlos Sanchez <ca...@apache.org>.
It's 30KB. I haven't changed dependencies or anything related directly
to the projects and their functionality, mainly syntax fixes, that's
why I took the responsability of doing it at a time instead of one at
a time.
I can send the patch if you think is not too big for the mailing list.
On 10/31/05, Dion Gillard <di...@gmail.com> wrote:
> Carlos, I think we the developers should work with you on this one.
>
> Post the patch as an attachment here so we can all look at it. How big is it?
>
> On 11/1/05, Carlos Sanchez <ca...@apache.org> wrote:
> > Hi,
> >
> > I've been working on fixing the maven project.xml files so they work
> > with maven 1.1 too and to improve the future releases and possible
> > upgrade to maven 2.
> >
> > I don't have rights in the commons svn, so I'd like to know if you
> > prefer a patch for everything as a bugzilla issue, separated patches
> > (this would be a PITA), or just a mail attachment.
> >
> > These patches include:
> > - fixing xml according to schema
> > - use of "version-SNAPSHOT" instead of "version-dev"
> > - adding some helper tags to improve the m1 pom conversion to m2.
> >
> > Regards
> >
> > Carlos Sanchez
> >
> > ---------------------------------------------------------------------
> > 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
Re: Maven build fixes affecting almost all projects
Posted by Carlos Sanchez <ca...@apache.org>.
SNAPSHOT is a reserved word used by maven. When you deploy an artifact
whose version has the word SNAPSHOT it gets automatically deployed
also as a dated version, eg. 1.0-SNAPSHOT gets deployed as
1.0-20051115.203021.
About the javadoc dependency, the patch is wrong, shouldn't be
commented. In the other hand IMHO it shouldn't generate a new jar but
depend on the tools.jar, which btw is closer to the approach used in
m2. Anyway we'll have to fix this pom manually when used in the m2
repo.
On 11/8/05, Phil Steitz <ph...@gmail.com> wrote:
> On 11/8/05, Carlos Sanchez <ca...@apache.org> wrote:
> > 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.
>
> Can someone explain why "-SNAPSHOT" is better than "-dev"?
> >
> > On 11/8/05, Dion Gillard <di...@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
>
> Did you look at the maven.xml? It seems to try to create and install
> this. It took me several attempts to get this to build (prior to
> change), but it did eventually.
> >
> > > 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
> >
>
> ---------------------------------------------------------------------
> 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
Re: Maven build fixes affecting almost all projects
Posted by Phil Steitz <ph...@gmail.com>.
On 11/8/05, Carlos Sanchez <ca...@apache.org> wrote:
> 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.
Can someone explain why "-SNAPSHOT" is better than "-dev"?
>
> On 11/8/05, Dion Gillard <di...@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
Did you look at the maven.xml? It seems to try to create and install
this. It took me several attempts to get this to build (prior to
change), but it did eventually.
>
> > 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Maven build fixes affecting almost all projects
Posted by Carlos Sanchez <ca...@apache.org>.
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 <di...@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 <ph...@gmail.com> wrote:
> > On 11/2/05, robert burrell donkin <ro...@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
Re: Maven build fixes affecting almost all projects
Posted by Dion Gillard <di...@gmail.com>.
Questions:
1) The javadoc dependency in attributes/compiler/project.xml has been
commented out. Why?
2) cli/project.xml has changed from current version 2.0 to 2.0-SNAPSHOT. Why?
3) codec/project.xml has changed from current version 1.3 to 1.4-SNAPSHOT. Why?
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.
5) chain/apps/agility/project.xml changes an incorrect version element
with a version of 1.0.0 into a correct currentVersion element with
1.0.1-SNAPSHOT. Why the version increase?
6) chain/apps/mailreader/project.xml changes an incorrect version
element with a version of 1.0.0 into a correct currentVersion element
with 1.0.1-SNAPSHOT. Why the version increase?
7) chain/apps/mailreader/project.xml changes do not fix the bad
resource elements, they simply remove them.
8) cli/project.xml changes currentVersion to 2.0-SNAPSHOT from 2.0. Why?
9) jelly/jelly-tags/project.xml changes currentVersion from 1.0 to
1.0.1-SNAPSHOT. Why?
On 11/6/05, Phil Steitz <ph...@gmail.com> wrote:
> On 11/2/05, robert burrell donkin <ro...@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
Re: Maven build fixes affecting almost all projects
Posted by Oliver Heger <ol...@t-online.de>.
Phil Steitz wrote:
>On 11/2/05, robert burrell donkin <ro...@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
>
>
I am just preparing a release candidate for the 1.2 release of
commons-configuration. Because this process involves updating the pom
anyway I went ahead and applied the proposed changes for configuration's
project.xml. It would be nice if someone double checks this.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Maven build fixes affecting almost all projects
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
Phil,
If you apply the patch, I'm happy to test Validator afterwards.
Niall
----- Original Message -----
From: "Phil Steitz" <ph...@gmail.com>
Sent: Saturday, November 05, 2005 8:46 PM
On 11/2/05, robert burrell donkin <ro...@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
Re: Maven build fixes affecting almost all projects
Posted by Phil Steitz <ph...@gmail.com>.
On 11/2/05, robert burrell donkin <ro...@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
Re: Maven build fixes affecting almost all projects
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
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.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Maven build fixes affecting almost all projects
Posted by Dion Gillard <di...@gmail.com>.
Carlos, I think we the developers should work with you on this one.
Post the patch as an attachment here so we can all look at it. How big is it?
On 11/1/05, Carlos Sanchez <ca...@apache.org> wrote:
> Hi,
>
> I've been working on fixing the maven project.xml files so they work
> with maven 1.1 too and to improve the future releases and possible
> upgrade to maven 2.
>
> I don't have rights in the commons svn, so I'd like to know if you
> prefer a patch for everything as a bugzilla issue, separated patches
> (this would be a PITA), or just a mail attachment.
>
> These patches include:
> - fixing xml according to schema
> - use of "version-SNAPSHOT" instead of "version-dev"
> - adding some helper tags to improve the m1 pom conversion to m2.
>
> Regards
>
> Carlos Sanchez
>
> ---------------------------------------------------------------------
> 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