In a multi-module Maven project, what could make the parent project not to be a part of the reactor?
I was just reading the source code for the [Versions Maven Plugin](
http://mojo.codehaus.org/versions-maven-plugin/), and noticed this snippet
of code:
if ( reactorProjects.contains( getProject().getParent() ) )
{
getLog().info( Project's parent is part of the reactor );
return;
}
When would the reactor not contain the parent module/project?
Best regards,
Behrang
http://www.behrang.org
Re: In a multi-module Maven project, what could make the parent project not to be a part of the reactor?
I see. Thanks.
Best regards,
Behrang
http://www.behrang.org
On Thu, Aug 7, 2014 at 9:35 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
* When you use -pl to restrict the reactor,
* when you use -f to build a specific pom
* When the parent is not at the specified relativePath
* etc
Many reasons
On 7 August 2014 12:29, Behrang Saeedzadeh behran...@gmail.com wrote:
I was just reading the source code for the [Versions Maven Plugin](
http://mojo.codehaus.org/versions-maven-plugin/), and noticed this
snippet
of code:
if ( reactorProjects.contains( getProject().getParent() ) )
{
getLog().info( Project's parent is part of the reactor );
return;
}
When would the reactor not contain the parent module/project?
Best regards,
Behrang
http://www.behrang.org
Re: Multiple single-module projects vs one multi-module project
Thanks for affirming this Ron. By the way, how do you ensure that all those projects depend on the same set of external dependences without duplicating the information for each POM? Cheers, Behrang Saeedzadeh http://www.behrang.org On Tue, Sep 27, 2011 at 2:17 AM, Ron Wheeler rwhee...@artifact-software.com wrote: I agree. 4- better visibility into the project for the manager. You know which modules are being changed and which ones are supposed to remain unchanged. You also get a bit of a warning about scope issues or potential problems when a new module gets added to the list of things that need changing after the development plan has been set. 5- more sense of responsibility for testing and the deploying of new SNAPSHOTs and releases. The functional definition of the module tends to be clearer if it is deployed to the team even if it is only a SNAPSHOT. The team expects a personal guaranty to go with a deploy. This tends to make programmers more careful about testing and documenting functionality of stubs and SNAPSHOTs with partial functionality as well as fully functional modules. Ron On 26/09/2011 11:48 AM, Behrang Saeedzadeh wrote: Hi, For large projects, wouldn't multiple single module projects work better than one multi-module project, because: 1- when using a dvcs, the repositories tend to become very large and when the project is divided into multiple single module projects, each project can have a small dvcs repository compared to one large monolithic repo. 2- new developers can be exposed only to the subset of projects that they need to work with 3- finer grained security over which developers can see which parts of the project Thanks in advance, Behrang -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Multiple single-module projects vs one multi-module project
Hi, For large projects, wouldn't multiple single module projects work better than one multi-module project, because: 1- when using a dvcs, the repositories tend to become very large and when the project is divided into multiple single module projects, each project can have a small dvcs repository compared to one large monolithic repo. 2- new developers can be exposed only to the subset of projects that they need to work with 3- finer grained security over which developers can see which parts of the project Thanks in advance, Behrang -- Cheers, Behrang Saeedzadeh http://www.behrang.org
Using TestNG with Maven
Hi, When creating a new Maven project using archetype:create maven by default uses JUnit as the unit testing framework. Is it possible to override this on the command line to use TestNG instead? Thanks in advance, Behrang -- View this message in context: http://n2.nabble.com/Using-TestNG-with-Maven-tp2427290p2427290.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using TestNG with Maven
Are there any alternatives to the archetype plugin for creating projects, that either use TestNG or let users choose TestNG on the commandline? - Behi Brett Porter-2 wrote: Not in the archetype - however you can create your own archetypes. Note that all is required by default is to switch the dependency to testng. - Brett On 05/03/2009, at 2:54 PM, Behrang Saeedzadeh wrote: Hi, When creating a new Maven project using archetype:create maven by default uses JUnit as the unit testing framework. Is it possible to override this on the command line to use TestNG instead? Thanks in advance, Behrang -- View this message in context: http://n2.nabble.com/Using-TestNG-with-Maven-tp2427290p2427290.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://n2.nabble.com/Using-TestNG-with-Maven-tp2427290p2427350.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using TestNG with Maven
That's exactly the kind of thing I don't want to do. That's why I asked about overriding this default on the command line. Rusty Wright wrote: After you create the project, open the file pom.xml and find the lines dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency and replace them with dependency groupIdorg.testng/groupId artifactIdtestng/artifactId version5.8/version scopetest/scope classifierjdk15/classifier /dependency Adding these dependency things to your pom.xml file is a regular activity. Also see http://www.exist.com/better-build-maven http://www.sonatype.com/book/reference/public-book.html Behrang Saeedzadeh wrote: Are there any alternatives to the archetype plugin for creating projects, that either use TestNG or let users choose TestNG on the commandline? - Behi Brett Porter-2 wrote: Not in the archetype - however you can create your own archetypes. Note that all is required by default is to switch the dependency to testng. - Brett On 05/03/2009, at 2:54 PM, Behrang Saeedzadeh wrote: Hi, When creating a new Maven project using archetype:create maven by default uses JUnit as the unit testing framework. Is it possible to override this on the command line to use TestNG instead? Thanks in advance, Behrang -- View this message in context: http://n2.nabble.com/Using-TestNG-with-Maven-tp2427290p2427290.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://n2.nabble.com/Using-TestNG-with-Maven-tp2427290p2427394.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using TestNG with Maven
That was my reply to Rusty's message. Otherwise, this is what I replied to Brett: Are there any alternatives to the archetype plugin for creating projects, that either use TestNG or let users choose TestNG on the commandline? After which came the Brett's reply that you quoted. :-) Cheers, Behi Wayne Fay wrote: That's exactly the kind of thing I don't want to do. That's why I asked about overriding this default on the command line. This is why Brett wrote: Not in the archetype - however you can create your own archetypes. You'll need to make your own archetype. Feel free to specify whatever testing library you wish to use in the behi-maven-archetype. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://n2.nabble.com/Using-TestNG-with-Maven-tp2427290p2427436.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: WELCOME to users@maven.apache.org
Hi, How can I exclude certain JAR files (like those that are only needed during unit testing, say TestNG JARs, or for code generation, like XDoclet) from being added to my distribution ZIP file? -- Science is a differential equation. Religion is a boundary limit - Alan Turing Behrang Saeedzadeh http://www.jroller.com/page/behrangsa http://my.opera.com/behrangsa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
