Hello David, thank you for your reply. I worked similar to your solution and used the dependency-maven-plugin:copy-dependencies that will do the job for copying all required dependencies to my webapp/WEB-INF/lib folder. That works fine if you don't use SNAPSHOT dependencies. The problem with this is that, the maven-dependency-plugin strips down the timestamp so your jar naming is like "artifactId-version-SNAPSHOT.ja" and will be duplicated with the dependeny that will correctly be resolved with the m2plugin builder. So MyEclipse will copy all libs under Web-INF/lib and all Project dependencies that are registered with the Eclipse Project and that creates duplicates. This may or may not a problem for other projects. But for our project (we resolve all modules with a special descriptor in the MANIFEST.MF and found duplicates) it is a problem. So i changed that Handling to avoid that copy of all dependencies and use only those dependencies that are brought to the Project by the m2plugin builder. Since MyEclipse copy that jars to the Target WebContainer Installation it works like a charme.
With 0.0.10 that handling is broken during Project references instead of references to simple deployed jars. So for the meantime i fall back to the 0.0.9 which is not a great approach. :-( bye Andreas Hartmann "David COURTIN" <[EMAIL PROTECTED]> schrieb am 30.01.2007 17:32:58: > Hello Andreas, > > I've been faced with the same problem for a long time, and I've find > today "the less worst" solution. > Since we used Maven and Maven2 plugin the "best" way is to let Maven > do his job of packaging for you with the m2plugin builder. By this > way you will have all the required libs in a directory like > target\project_name\WEB-INF\lib . After a build with the package > goal, you can define in one click J2EE modules dependencies in the > project properties by selecting the jars in the generated target > directory. By this way the next time you deploy your application > with the WTP tools, this libraries will be take into account. > > Hope this help. > > Bye. > > David > > > > -----Message d'origine----- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > Envoyé : vendredi 26 janvier 2007 11:56 > > À : [email protected] > > Objet : [m2eclipse-user] Dependency Management > > > > > > hello guys, > > > > first of all it's a nice job done for this release. So > > settings and profiles with proxies will be recognized and > > this will help most users to adopt maven in their development > > environment. > > But one question: > > the behaviour of dependency management has changed in this > > release. So dependencys that are located in the actual > > workspace will be resolved by direct project references. > > this will be niice for any projects but i realized problems > > on deploying a WEB project with myeclipse (underlying WTP). > > the dependent direct project references can not be deployed > > with myeclipse. > > "Error occured during deploy. the library should not be a directory". > > > > Whatever is it possible to disable such direct project > > references and working only on packaged jar references? > > Has anybody recognized the same problem? > > > > Thanks in advance! > > > > _________________________________________ > > Andreas Hartmann > > Consultant / Softwareentwicklung > > > > > > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be > copied, disclosed to, retained or used by, any other party. If you > are not an intended recipient then please promptly delete this e- > mail and any attachment and all copies and inform the sender. Thank you. > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email
