This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
All projects were created inside Eclipse, with default maven structures (except test-project), then the pom's were added accordingly.
The most important error I'm getting right now is in the ejb project, when exporting/deploying ... the project uses one jbpm jar, and in the Eclipse IDE it shows no errors, since maven plugin resolves all dependencies.
Now the problem is that, when I export, the ejb manifest has no classpath attributes entries ... the jar is located in the ear root, but it isn't specified in the manifest file, so I have a ClassNotFoundException because I'm using a class from the jar.
That's ok, so I went to eclipse, project ejb -> "Java EE Module Dependencies", it doesn't show the jars of the classpath ... so I cannot select them into the manifest file.
If I add it manually to the manifest file, the project goes ok, but no jars are present. Since all is maintained by the maven plugin, I only have the possibility to choose a "Maven Dependencies" entry, that doesn't add anything to the manifest.
I'm testing with just one jar, but the project will have lot's of jars, so including them by hand is a pain, and future maintenance will became chaotic.
Shouldn't the manifest be automatically maintained by eclipse?
I know maven build will create one, but I intended to have this also managed in eclipse, so I could add a server and auto-deploy inside eclipse for development and testing.