Re: Ignore missing goals when using reactor?
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 something overwrite the goal in their own maven.xml. Jon Andersen wrote: 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 me. I don't want to ignore goals that fail, just goals that don't exist. Has anyone solved this before? Thanks, -Jon Andersen Software developer 734-260-6083 (work) 734-646-5577 (home) Digital Media Commons - Duderstadt Center University of Michigan - 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: Ignore missing goals when using reactor?
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 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 something overwrite the goal in their own maven.xml. Jon Andersen wrote: 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 me. I don't want to ignore goals that fail, just goals that don't exist. Has anyone solved this before? Thanks, -Jon Andersen Software developer 734-260-6083 (work) 734-646-5577 (home) Digital Media Commons - Duderstadt Center University of Michigan - 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: Ignore missing goals when using reactor?
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 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 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 something overwrite the goal in their own maven.xml. Jon Andersen wrote: 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 me. I don't want to ignore goals that fail, just goals that don't exist. Has anyone solved this before? Thanks, -Jon Andersen Software developer 734-260-6083 (work) 734-646-5577 (home) Digital Media Commons - Duderstadt Center University of Michigan - 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]
Ignore missing goals when using reactor?
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 me. I don't want to ignore goals that fail, just goals that don't exist. Has anyone solved this before? Thanks, -Jon Andersen Software developer 734-260-6083 (work) 734-646-5577 (home) Digital Media Commons - Duderstadt Center University of Michigan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ignore missing goals when using reactor?
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 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 me. I don't want to ignore goals that fail, just goals that don't exist. Has anyone solved this before? Thanks, -Jon Andersen Software developer 734-260-6083 (work) 734-646-5577 (home) Digital Media Commons - Duderstadt Center University of Michigan - 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]
Using reactor to generate navigation.xml
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 wondering if someone
Had already done the donkeywork ?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using reactor to generate navigation.xml
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-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 wondering if someone
Had already done the donkeywork ?
-
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: Using reactor to generate navigation.xml
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 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 wondering if someone
Had already done the donkeywork ?
-
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]
/ /OREF:CPTA1F6C Build Failed when using Reactor
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 copy.
However, if I run the sub project's xml file directly, all goes well.
base maven.xml
goal name=reeferbk-buildall
m:reactor basedir=${basedir}
includes=*/project.xml
goals=reeferbk-dist
banner=Building Project
ignoreFailures=false/
/goal
sub project's maven.xml
goal name=reeferbk-dist
echo[INFO] Installing WAR file.../echo
attainGoal name=war:install/
echo[INFO] Generating site content.../echo
attainGoal name=site:generate/
/goal
Has anyone else had this problem?
Any ideas to what might be causing this?
Thanks in advance,
--Alen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem using reactor from console
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 up the reactor everything still works fine. The reactor calls the goals in each subproject. The problem occurs when I start the reactor from the console (maven console target). The first time I call the 'dist-all' target everything works fine, but the second time I receive errors like: - org.apache.commons.jelly.JellyTagException: file:/home/nfs/joel/projects/legalmanager/:11:38: maven:reactor Goal [jar:install] has no action definition. - Does anybody know a way to fix or work around this issue? I'm using maven RC1. Regards, Joel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using reactor
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 that bar.jar isn't in the repository. It is as if Maven is trying to resolve dependencies of .all. projects before it starts processing .any. projects. In my case, one of my projects satisfies dependencies of another, so this strategy does not work. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using reactor
We use multiproject:install and it happily uses the reactor to compile and install all jars based on their dependency order. Not in beta 10. The multiproject plugin does not work in beta 10, because it's syntax when using j:set is incorrect (uses name instead of value). Can you show us those dependencies again? From the original mail: I have the following layout: maven.xml (Main project) applications/registration/project.xml (Builds foo.ear) modules/web/project.xml (Builds foo.war) modules/bar/project.xml (Builds bar.jar from source code) I want foo.ear to contain foo.war 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 ... snip ... /project modules/web/project.xml project idfoo/id groupidfoo/groupid ... snip ... dependencies dependency groupIdfoo/groupId artifactIdbar/artifactId ... snip ... properties war.bundletrue/war.bundle /properties /dependency ... snip ... /dependencies ... snip ... /project Found one additional thing: in a setup like this, before anything is built, try calling multiproject:clean (which also doesn't work under beta 10, but you can call multiproject:goal with goal=clean:clean). This generates an error, because Maven claims it can't find the jar in the repository. This is true, but it should not need the jar to clean out the project. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using reactor
Lester Ward [EMAIL PROTECTED] wrote on 04/09/2003 12:20:50 AM: We use multiproject:install and it happily uses the reactor to compile and install all jars based on their dependency order. Not in beta 10. The multiproject plugin does not work in beta 10, because it's syntax when using j:set is incorrect (uses name instead of value). Correct, I use CVS HEAD. Can you show us those dependencies again? From the original mail: I have the following layout: maven.xml (Main project) The above has no dependencies on other projects. applications/registration/project.xml (Builds foo.ear) The above must state a dependency on foo.war modules/web/project.xml (Builds foo.war) Must state a dependency on foo.jar modules/bar/project.xml (Builds bar.jar from source code) No other interproject dependencies. I want foo.ear to contain foo.war 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 ... snip ... /project modules/web/project.xml project idfoo/id groupidfoo/groupid ... snip ... dependencies dependency groupIdfoo/groupId artifactIdbar/artifactId ... snip ... properties war.bundletrue/war.bundle /properties /dependency ... snip ... /dependencies ... snip ... /project Found one additional thing: in a setup like this, before anything is built, try calling multiproject:clean (which also doesn't work under beta 10, but you can call multiproject:goal with goal=clean:clean). This generates an error, because Maven claims it can't find the jar in the repository. This is true, but it should not need the jar to clean out the project. Maven needs the dependencies to be satisfied before it will do ANYTHING with a project. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using reactor
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 in-place debugging) it is extremely useful not to have code of a .war bound into a .jar file. The problem is coming where the code in the .war file requires bar.jar and bar.jar is generated by code. Maven needs the dependencies to be satisfied before it will do ANYTHING with a project. Doesn't this, then, preclude using Maven from doing things which make sure the dependencies are satisfied? If I must first have a jar in the repository in order to clean the project that creates that jar, how does anything get built from scratch? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using reactor
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 code in the .war file requires bar.jar and bar.jar is generated by code. Maven needs the dependencies to be satisfied before it will do ANYTHING with a project. Doesn't this, then, preclude using Maven from doing things which make sure the dependencies are satisfied? If I must first have a jar in the repository in order to clean the project that creates that jar, how does anything get built from scratch? No. A reactored jar:install, or multiproject:install will build from the bottom up. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
