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
