In my opinion, to answer this question, you need to think in terms of project life cycle and version control. In other words, does the parent pom have its own life cycle i.e. can it be released separately of the other modules or not? If the answer is yes (and this is the case of … Read more
You create a new project. The new project is your EAR assembly project which contains your two dependencies for your EJB project and your WAR project. So you actually have three maven projects here. One EJB. One WAR. One EAR that pulls the two parts together and creates the ear. Deployment descriptors can be generated … Read more
The Maven Help Plugin is somehow already proposing something for this: help:evaluate evaluates Maven expressions given by the user in an interactive mode. Here is how you would invoke it on the command line to get the ${project.version}: mvn org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate \ -Dexpression=project.version As noted in the comments by Seb T, to only print the version … Read more
Simply specify the version in your current pom. The version specified here will override other. Forcing a version A version will always be honoured if it is declared in the current POM with a particular version – however, it should be noted that this will also affect other poms downstream if it is itself depended … Read more
Here’s what’s been working for me: <plugin> <artifactId>exec-maven-plugin</artifactId> <groupId>org.codehaus.mojo</groupId> <executions> <execution><!– Run our version calculation script –> <id>Version Calculation</id> <phase>generate-sources</phase> <goals> <goal>exec</goal> </goals> <configuration> <executable>${basedir}/scripts/calculate-version.sh</executable> </configuration> </execution> </executions> </plugin>
In Eclipse from your project: Right-click on your project Click Properties Java build path: Libraries; Remove the “JRE System Library[J2SE 1.4]” Click Add Library -> JRE System Library Select the new “Execution Environment” or Workspace default JRE
The Maven Dependency Plugin will help, especially the dependency:analyze goal: dependency:analyze analyzes the dependencies of this project and determines which are: used and declared; used and undeclared; unused and declared. Another thing that might help to do some cleanup is the Dependency Convergence report from the Maven Project Info Reports Plugin.
I’m not surprised that system scope dependencies are not added (after all, dependencies with a system scope must be explicitly provided by definition). Actually, if you really don’t want to put that dependency in your local repository (for example because you want to distribute it as part of your project), this is what I would … Read more
I recommend using type instead of classifier (see also: classifier). It tells Maven a bit more explicitly what you are doing (and I’ve found that m2eclipse and q4e both like it better). <dependency> <groupId>com.myco.app</groupId> <artifactId>foo</artifactId> <version>1.0-SNAPSHOT</version> <type>test-jar</type> <scope>test</scope> </dependency>
What has worked for me (may be a newer feature of Maven) is merely doing wildcards in the exclusion element. I have a multi-module project that contains an “app” module that is referenced in two WAR-packaged modules. One of those WAR-packaged modules really only needs the domain classes (and I haven’t separated them out of … Read more