Even though this has already gotten the “approved answer”, it turns out that there is this AWESOME versions plugin that handles the neverending version maintenance problem. For those lazy people here are some of its goals: versions:display-dependency-updates scans a project’s dependencies and produces a report of those dependencies which have newer versions available. versions:display-plugin-updates scans … Read more
Running mvn dependency:tree on the sample project posted in the bug link specified above, [INFO] Building MEAR-143 1.0-SNAPSHOT [INFO] ———————————————————————— [INFO] [INFO] — maven-dependency-plugin:2.3:tree (default-cli) @ mear-143 — [INFO] ljnelson:mear-143:pom:1.0-SNAPSHOT [INFO] \- junit:junit:jar:4.8.2:test [INFO] [INFO] ———————————————————————— [INFO] Building MEAR-143 Leaf 1.0-SNAPSHOT [INFO] ———————————————————————— [INFO] [INFO] — maven-dependency-plugin:2.3:tree (default-cli) @ mear-143-leaf — [INFO] ljnelson:mear-143-leaf:jar:1.0-SNAPSHOT [INFO] \- … Read more
You can achieve this by specifying the finalName property in your pom like this: <build> <finalName>${project.artifactId}</finalName> </build>
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
This is a “feature” of the M2E plugin that had been introduced a while ago. It’s not directly related to the JBoss EAR plugin but also happens with most other Maven plugins. If you have a plugin execution defined in your pom (like the execution of maven-ear-plugin:generate-application-xml), you also need to add additional config information … Read more