|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-dependenci... Inge Solvoll (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Inge Solvoll (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Inge Solvoll (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Inge Solvoll (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Inge Solvoll (JIRA)
it's most likely because the "nbm" files cannot be placed on compilation classpath. You need the module jar on CP in order to have all the regular maven plugins to work properly. That's the difference between the application and nbm projects.
I'm not entirely sure what the problem you are trying to solve is. In your nbm project you should have only the dependencies on other projects that your project needs for compilation, that are explicitly used by the code in the project. That's typically unique to each project and should be declared in the pom.