Hallo Eugene, yes, i will try to extract all the necessary stuff out of my project to create a sample project.
But one question in general: What does the m2plugin if the current dependent project in workspace has an other version number? Let me say if i have project A that declares a dependency to project B -version 1.0 that is checked out in the same workspace and have the version 0.9. I will assume the dependency point to the deployed jar found in the repository with the correct version instead of using that project in workspace. correct? But in general i assume that not in all project it is a good solution to reference projects in workspace. It offers you a really great interaction mode to fix problems or develop features across multiple projects, but it requires you to have all projects up to date and checked out in your Workspace. (simply you must keep all in sync) bye Andreas Eugene Kuleshov <[EMAIL PROTECTED]> schrieb am 30.01.2007 18:39:46: > Andreas, > > Is it possible to reproduce this issue without Myeclipse, i.e. using > only WTP projects? If so, can you please create an issue in jira and > attach some sample projects that would allow to reproduce issue, along > with all necessary instructions. > > You can also create an enhancement request for disabling resolving > projects from the workspace. > > Thanks > > Eugene > > > [EMAIL PROTECTED] wrote: > > 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 > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email
