Re: cvs commit: maven-components/maven-plugin/src/test/resources/source IdeaPlugin.java

2004-05-23 Thread Jerome Lacoste
On Fri, 2004-05-21 at 20:50, [EMAIL PROTECTED] wrote: > jvanzyl 2004/05/21 17:50:06 > > Modified:maven-plugin project.xml >maven-plugin/src/test/resources/source IdeaPlugin.java > Added: maven-plugin/src/main/java/org/apache/maven/plugin/generator >

Re: cvs commit: maven-plugins/javadoc plugin.jelly

2004-05-23 Thread Dion Gillard
On 23 May 2004 22:02:54 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > aheritier2004/05/23 15:02:54 > > Modified:javadoc plugin.jelly > Log: > re-ident + code optimization [snip] > +COUCOU Did you really mean to leave that in there? ---

Re: cvs commit: maven-plugins/javadoc/src/plugin-test project.properties maven.xml project.xml

2004-05-23 Thread Dion Gillard
Huh? maven.src.set should be set automatically by maven. You can then add to it using addPath (from memory). On 23 May 2004 22:05:00 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > aheritier2004/05/23 15:05:00 > > Modified:javadoc/src/plugin-test maven.xml project.xml > Add

Re: [GUMP@brutus]: maven/maven-bootstrap failed

2004-05-23 Thread Adam R. B. Jack
I guess this is the descriptor that has been there for ages, Gump coverage has just finally crept up to this depth. Sure we can update it & halt the nag. regards, Adam - Original Message - From: "Brett Porter" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "'Maven Developers List'" <[EM

RE: [GUMP@brutus]: maven/maven-bootstrap failed

2004-05-23 Thread Brett Porter
Hi, Can someone explain how this came about? I haven't seen any updates on the gump list to indicate that Maven was going to be bootstrapped there yet. A few issues: - can we change it not to go to [EMAIL PROTECTED] until the gump end is working, as it is probably just confusing - commons-grant i

cvs commit: maven-plugins/javadoc/src/plugin-test project.properties maven.xml project.xml

2004-05-23 Thread aheritier
aheritier2004/05/23 15:05:00 Modified:javadoc/src/plugin-test maven.xml project.xml Added: javadoc/src/plugin-test project.properties Log: Actually I can't succeed to set the maven.compile.src.set dynamically in the maven.xml. I need to set it manually in the project.prope

cvs commit: maven-plugins/javadoc plugin.jelly

2004-05-23 Thread aheritier
aheritier2004/05/23 15:02:54 Modified:javadoc plugin.jelly Log: re-ident + code optimization Revision ChangesPath 1.39 +77 -68maven-plugins/javadoc/plugin.jelly Index: plugin.jelly === RCS

RE: Xdoc plugin and "goals" documents

2004-05-23 Thread Arnaud Heritier
> -Message d'origine- > De : Dion Gillard [mailto:[EMAIL PROTECTED] > Envoyé : dimanche 23 mai 2004 23:19 > À : Maven Developers List > Objet : Re: Xdoc plugin and "goals" documents > > On Sun, 23 May 2004 19:20:02 +0200, Arnaud Heritier > <[EMAIL PROTECTED]> wrote: > > > > +1, I'm ok wi

Re: Xdoc plugin and "goals" documents

2004-05-23 Thread Dion Gillard
On Sun, 23 May 2004 19:20:02 +0200, Arnaud Heritier <[EMAIL PROTECTED]> wrote: > > +1, I'm ok with your proposal. > In any case, I won't have the time to work on this before several weeks (so > I hope that the 1.0 will be released). I prefer to fix bugs and enhance > documentations if possible bef

[ANN] Maven taglib Plug-in 1.1 released

2004-05-23 Thread Fabrizio Giustina
The maven-taglib team is pleased to announce the Maven taglib Plug-in 1.1 release! http://maven-taglib.sf.net Maven taglib Plug-in is a maven plugin for jsp tag libraries developers. It eases the generation, documentation and testing of jsp tag libraries. Changes in this version include:

[Strategy] How to manage several subprojects as one project?

2004-05-23 Thread Vincent Massol
Hi guys, I'm still trying to slowly convert the Cactus build (which uses Ant) into a Maven build. Here's a use case I have. Currently I have the following: framework/ |_ src |_ share-12-13-14 |_ share-13-14 |_ j2ee-12 |_ j2ee-13 |_ j2ee-14 |_ build.xml |_ [...] Where 12

RE: Xdoc plugin and "goals" documents

2004-05-23 Thread Arnaud Heritier
+1, I'm ok with your proposal. In any case, I won't have the time to work on this before several weeks (so I hope that the 1.0 will be released). I prefer to fix bugs and enhance documentations if possible before the 1.0 final. Just a remark concerning the point 3: I don't think that we can create