RE: cvs commit: jakarta-commons-sandbox/workflow build.xml
Hello Craig, I have a good and a bad news. The good is that the problem is fixed in CVS (http://jira.codehaus.org/browse/MPANT-16), but the bad is that the ant plugin wasn't release before maven 1.0. If this bug is really annoying (what I understand) I can publish a new release for the ant plugin. Do you want? Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : jeudi 15 juillet 2004 23:31 À : 'Jakarta Commons Developers List' Objet : RE: cvs commit: jakarta-commons-sandbox/workflow build.xml Ok, Craig I hoped that you used an old release ;-) I will try to found what is happening! Arnaud -Message d'origine- De : Craig McClanahan [mailto:[EMAIL PROTECTED] Envoyé : jeudi 15 juillet 2004 22:41 À : Jakarta Commons Developers List Objet : Re: cvs commit: jakarta-commons-sandbox/workflow build.xml Arnaud Heritier wrote: Hello Craig, Which maven release do you use?? I thought that we fixed this bug!! It seems that you committed some absolute paths! Arnaud I used the 1.0 final release :-(. Reproducible test case -- go to jakarta-commons-sandbox/workflow and run maven ant. Craig - 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]
Re: cvs commit: jakarta-commons-sandbox/workflow build.xml
On Sun, 18 Jul 2004 18:34:34 +0200, Arnaud Heritier [EMAIL PROTECTED] wrote: Hello Craig, I have a good and a bad news. The good is that the problem is fixed in CVS (http://jira.codehaus.org/browse/MPANT-16), but the bad is that the ant plugin wasn't release before maven 1.0. If this bug is really annoying (what I understand) I can publish a new release for the ant plugin. Do you want? Phew ... at least it wasn't my stupidity :-). As to what to do, that would seem sort of dependent on how Maven wants to handle updates of plugins. If they are going to have their own separate release cycles, then it would make sense to publish an updated Ant plugin separately (I presume that plugins are versioned like dependencies are, so I can pick the ones I want, right?). If not, you're pretty likely to confuse Maven users if you start publishing individual jars with no version info on top of the 1.0 release. To say nothing of confusing Maven developers when they get a bug report, and have no idea what combination of plugins are actually being used by the reporter. Arnaud Craig -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : jeudi 15 juillet 2004 23:31 À : 'Jakarta Commons Developers List' Objet : RE: cvs commit: jakarta-commons-sandbox/workflow build.xml Ok, Craig I hoped that you used an old release ;-) I will try to found what is happening! Arnaud -Message d'origine- De : Craig McClanahan [mailto:[EMAIL PROTECTED] Envoyé : jeudi 15 juillet 2004 22:41 À : Jakarta Commons Developers List Objet : Re: cvs commit: jakarta-commons-sandbox/workflow build.xml Arnaud Heritier wrote: Hello Craig, Which maven release do you use?? I thought that we fixed this bug!! It seems that you committed some absolute paths! Arnaud I used the 1.0 final release :-(. Reproducible test case -- go to jakarta-commons-sandbox/workflow and run maven ant. Craig - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: jakarta-commons-sandbox/workflow build.xml
[EMAIL PROTECTED] wrote: Hello Craig, I have a good and a bad news. The good is that the problem is fixed in CVS (http://jira.codehaus.org/browse/MPANT-16), but the bad is that the ant plugin wasn't release before maven 1.0. If this bug is really annoying (what I understand) I can publish a new release for the ant plugin. Do you want? Phew ... at least it wasn't my stupidity :-). ;-) As to what to do, that would seem sort of dependent on how Maven wants to handle updates of plugins. If they are going to have their own separate release cycles, then it would make sense to publish an updated Ant plugin separately (I presume that plugins are versioned like dependencies are, so I can pick the ones I want, right?). If not, you're pretty likely to confuse Maven users if you start publishing individual jars with no version info on top of the 1.0 release. To say nothing of confusing Maven developers when they get a bug report, and have no idea what combination of plugins are actually being used by the reporter. Maven core is published with a set of plugins provided by default. Now that this first release is out, each plugin have their own release cycles. A user can update or add a plugin with a command like : maven plugin:download -DgroupId=group -DartifactId=artifact -Dversion=release In fact, when we have a doubt to reproduce a bug, the developer can ask the user's configuration with the -i option for example. We have regularly some bugs not correctly classified in Jira but we move them ;-) I will propose to the maven team to release the ant plugin. Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: jakarta-commons-sandbox/workflow build.xml
Hello Craig, Which maven release do you use?? I thought that we fixed this bug!! It seems that you committed some absolute paths! Arnaud + property name=defaulttargetdir value=/home/craigmcc/Apache/jakarta-commons- sandbox/workflow/target + /property + property name=libdir value=/home/craigmcc/Apache/jakarta-commons- sandbox/workflow/target/lib + /property + property name=classesdir value=/home/craigmcc/Apache/jakarta-commons- sandbox/workflow/target/classes + /property + property name=testclassesdir value=/home/craigmcc/Apache/jakarta-commons- sandbox/workflow/target/test-classes + /property + property name=testclassesdir value=/home/craigmcc/Apache/jakarta-commons- sandbox/workflow/target/test-classes + /property + property name=testreportdir value=/home/craigmcc/Apache/jakarta-commons- sandbox/workflow/target/test-reports - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-commons-sandbox/workflow build.xml
Arnaud Heritier wrote: Hello Craig, Which maven release do you use?? I thought that we fixed this bug!! It seems that you committed some absolute paths! Arnaud I used the 1.0 final release :-(. Reproducible test case -- go to jakarta-commons-sandbox/workflow and run maven ant. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: jakarta-commons-sandbox/workflow build.xml
Ok, Craig I hoped that you used an old release ;-) I will try to found what is happening! Arnaud -Message d'origine- De : Craig McClanahan [mailto:[EMAIL PROTECTED] Envoyé : jeudi 15 juillet 2004 22:41 À : Jakarta Commons Developers List Objet : Re: cvs commit: jakarta-commons-sandbox/workflow build.xml Arnaud Heritier wrote: Hello Craig, Which maven release do you use?? I thought that we fixed this bug!! It seems that you committed some absolute paths! Arnaud I used the 1.0 final release :-(. Reproducible test case -- go to jakarta-commons-sandbox/workflow and run maven ant. Craig - 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]
