Re: Ignore missing goals when using reactor?

2005-02-22 Thread baleineca
One solution would be to have the sub projects inherit from a common parent (probably where you are running your reactor from): see http://maven.apache.org/reference/project-descriptor.html#extend You can then have the goal in the parent maven.xml that does nothing. Sub projects that want to do

Re: Ignore missing goals when using reactor?

2005-02-22 Thread baleineca
It appears there was a reply already similar to this... I didn't mean to repeat it... I'm playing around with my gmail POP settings :- ) and didn't catch the previous reply... baleineca wrote: One solution would be to have the sub projects inherit from a common parent (probably where you are

RE: Ignore missing goals when using reactor?

2005-02-22 Thread Arnaud HERITIER
Two replies are better than nothing ;-) Arnaud -Message d'origine- De : baleineca [mailto:[EMAIL PROTECTED] Envoyé : mardi 22 février 2005 19:20 À : Maven Users List Objet : Re: Ignore missing goals when using reactor? It appears there was a reply already similar to this... I

Ignore missing goals when using reactor?

2005-02-18 Thread Jon Andersen
I'd like to use the reactor to execute goals across many projects, but not have the build fail when a goal does not exist. That is, if a sub-project doesn't have the required goal, just ignore that subproject and move on. The reactor has the ignoreFailures attribute, but that doesn't work for

Re: Ignore missing goals when using reactor?

2005-02-18 Thread dan tran
long short, can you make all projects inherit a master project which has your goal to do nothing. This way reactor will invoke the dummy goal when it is not able to find goal in the targeted project. -D On Fri, 18 Feb 2005 14:41:01 -1000, Jon Andersen [EMAIL PROTECTED] wrote: I'd like to use

Using reactor to generate navigation.xml

2004-05-06 Thread Nigel Magnay
Is there any example of using the reactor to auto-generate a navigation.xml to subprojects ? I have j:forEach var=reactorProject items=${reactorProjects} echo${reactorProject.artifactId}/echo /j:forEach But I haven't looked at how to write out the navigation.xml file so I was

Re: Using reactor to generate navigation.xml

2004-05-06 Thread Emmanuel Venisse
You can use the multiproject plugin, it's more simple. Emmanuel - Original Message - From: Nigel Magnay [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 06, 2004 6:02 PM Subject: Using reactor to generate navigation.xml Is there any example of using the reactor to auto

RE: Using reactor to generate navigation.xml

2004-05-06 Thread Arnaud Heritier
The multiproject plugin does this. It generates an entry for each subproject Arnaud -Message d'origine- De : Nigel Magnay [mailto:[EMAIL PROTECTED] Envoyé : jeudi 6 mai 2004 18:02 À : [EMAIL PROTECTED] Objet : Using reactor to generate navigation.xml Is there any example

/ /OREF:CPTA1F6C Build Failed when using Reactor

2004-02-27 Thread aribic
Hi All, I have an issue when I run reactor from my base project.xml. I get a BUILD FAILED with following message: ... Element... m:reactor Line.. 17 Column 40 ... Unable to obtain goal [reeferbk-dist] -- ... ant:copy Warning: Could not find file ~/projects/MyPrj/target/taglib.xml to

Problem using reactor from console

2003-10-10 Thread Wijngaarde [Us Media]
Hi, I have started an EJB project using maven. The EJB project is divided in 4 sub projects. One WEB project, one UTIL project, one EJB project and a final EAR project to build the resulting EAR file. Everything works fine when i start the goals in side every subproject directly. After setting

RE: Using reactor

2003-09-04 Thread Lester Ward
No. A reactored jar:install, or multiproject:install will build from the bottom up. I agree that it .should. be doing so. My problem is that it is not. According to the Our processing order: list, bar.jar is correctly getting built first, but before anything is built I get the error saying

RE: Using reactor

2003-09-03 Thread Lester Ward
which contains bar.jar. This means bar.jar needs to get built first, then foo.war, then foo.ear. As near as I can figure, the only way to control the build order using reactor is to set up the dependencies in a certain way: modules/bar/project.xml project ... snip ... idbar/id

RE: Using reactor

2003-09-03 Thread dion
. This means bar.jar needs to get built first, then foo.war, then foo.ear. As near as I can figure, the only way to control the build order using reactor is to set up the dependencies in a certain way: modules/bar/project.xml project ... snip ... idbar/id ... snip ... /project

RE: Using reactor

2003-09-03 Thread Lester Ward
modules/web/project.xml (Builds foo.war) Must state a dependency on foo.jar No, it mustn't. It must state a dependency on bar.jar. You are misunderstanding the example. There is no foo.jar. A .war file is perfectly capable of containing its own code. In some cases (particularly for

RE: Using reactor

2003-09-03 Thread dion
Lester Ward [EMAIL PROTECTED] wrote on 04/09/2003 01:49:23 AM: modules/web/project.xml (Builds foo.war) Must state a dependency on foo.jar No, it mustn't. It must state a dependency on bar.jar. You are misunderstanding the example. Sorry. [snip] The problem is coming where the