Is there a way to set a default lifecycle action?

So suppose I have 2 projects: projectLib and projectWar. Whenever I'm in the projectLib folder where the pom.xml is, I'd like to just type mvn and have it run the mvn install lifecycle Whenever I'm in the projectWar folder where the pom.xml is, I'd like to just type mvn and have it run the mvn

Re: Is there a way to set a default lifecycle action?

Thanks very much. -- View this message in context: http://maven.40175.n5.nabble.com/Is-there-a-way-to-set-a-default-lifecycle-action-tp4647944p4648209.html Sent from the Maven - Users mailing list archive at Nabble.com. - To

m2eclipse: missing Navigate menu items

This is more a m2eclipse plugin issue and less maven but if any has an answer or can point me in the right direction, I'd appreciate it. I have eclipse indigo (v3.7) for mac and it came preinstalled with m2eclipse (v1.0.0.20110607-2117). I believe both are one of the most recent builds. Anyways,

Re: Misunderstanding modules: Two or more projects in the reactor have the same identifier

Yes, this was definitely helpful. We'll have to rethink the way we're doing things for sure. Just to clear one more thing up. Using the same example where libraries A and B depend on C. If Product X needs these libraries, can it just include as modules A and B or does it need C as well? That is,

Re: Misunderstanding modules: Two or more projects in the reactor have the same identifier

Hi Wayne, Yes, I understand I don't have to have to depend on C from product X, but do I need to include it as a module? -Kane -- View this message in context:

Unrecognised tag: 'useAllReactorProjects'

I copy-pasted an assembly config from the web and it doesn't work. it doesn't like the useAllReactorProjects node under moduleSet. I'm using maven 3.0.3. Any ideas what may be wrong here: { assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2;

Misunderstanding modules: Two or more projects in the reactor have the same identifier

So it seems Maven handles dependency inheritance pretty well. Let's say I have a parent project A that depends on projects B and C. And both B and C depend on D. This works fine as dependencies. But suppose I wanted to make B and C modules of A. And I want to make D a module of B and C, then

Re: Misunderstanding modules: Two or more projects in the reactor have the same identifier

I found this reference to my problem: http://dspace.2283337.n4.nabble.com/DSpace-1-7-0-amp-Maven-3-0-2-DuplicateProjectException-Missing-pom-xml-properties-td3339149.html So Maven 3 removed the enable nested module option from the earlier version? I guess that might have helped with my situation.

Re: Archiva vs. Nexus

My 2 cents: I'm very new to Maven and its repository and I found Nexus very easy to install, set up, and use. I haven't tried Archiva though -- View this message in context: http://maven.40175.n5.nabble.com/Archiva-vs-Nexus-tp4594364p4614051.html Sent from the Maven - Users mailing list archive

Re: Misunderstanding modules: Two or more projects in the reactor have the same identifier

Well, I would like to be able to call a maven phase like compile in the top-level parent project and have it combine all of its dependencies/submodules. That's really the only reason I'm using modules instead of sticking with dependencies. -- View this message in context:

Re: Misunderstanding modules: Two or more projects in the reactor have the same identifier

I guess I don't really understand the Maven modules then. Well, this is what I have. My company has a bunch of components and our own home-brewed build system. We want to translate it to the Maven environment. The library components depend on each other in that they may reference classes in other

When to use pluginManagement

Can someone explain to me or point me to a page that explains what the pluginManagement is and when it needs to be included? In some examples I see: build pluginManagement plugins ... In other examples I see: build plugins ... What's the difference? And how do you know when you

Re: When to use pluginManagement

Thanks. That cleared it up. -- View this message in context: http://maven.40175.n5.nabble.com/When-to-use-pluginManagement-tp4610500p4610553.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe,

Referencing modules in a sibling folder

Hello, I'm very new to Maven. I'm trying to convert my company's build environment from a proprietary configuration to Maven's. We components that are dependent on one another and they lie in sibling folders. e.g. We may have components ./myComponents/A ./myComponents/B ./myComponents/C

Re: Referencing modules in a sibling folder

I thought the dependency section was just for artifacts that are located in the repository. For artifacts that consist of my own code, aren't those modules? I may be confusing the two. Our code base actually contains several different products, so I don't think it makes sense to have one pom that

Re: Referencing modules in a sibling folder

I tried using dependency but I'm getting a similar error, that it can't find the artifact. { ERROR] Failed to execute goal on project developmentenvironment: Could not resolve dependencies for project com.inferlink.entitybase:developmentenvironment:jar:1.0-SNAPSHOT: Could not find artifact

Re: Referencing modules in a sibling folder

Ah thanks. I forgot the mvn install part of it, which I guess makes it available in the repository for other artifacts to use. I just did a mvn compile on the dependency component. I've got different errors now--a sign of progress. Thanks guys, Kane -- View this message in context: