Christian-Luc,
We still need JIRA issue for tracking purposes. Please also note, that
even if it is easy to reproduce anything, it still take fair amount of
time to create test projects for us and it also require bit of guessing
if there is not enough details in the bug report. For example, your
short description imply certain knowledge on how all those projects are
configured and how their poms look like. So, by providing test project
you would save us time and increase chances that issue will be fixed.
regards,
Eugene
houzecl wrote:
This is very easy to reproduce:
You have an EAR project, a WAR project, a JAR project
EAR depends on WAR and JAR
What happens is that The M2E dependency resolver will show only the JAR
dependency not the WAR
This is very bad because Eclipse will not see the dependency and therefore,
if you launch an Eclipse Build Project on the EAR, it wiil only lauch the
Build on Jar, and then the EAR, but will forget the WAR
Christian-Luc
Eugene Kuleshov wrote:
Thomas,
Please create jira issue for this and attach test projects along with
the step by step instructions how to reproduce it. See some hints at
http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues
BTW, what did you mean by "enable the project references"?
regards,
Eugene
Thomas Tardy wrote:
Hi all,
I have a workspace with an EAR, an EJB, a WAR and several utilty
projects and everything is working well expect that the WAR project
cannot have project references. If I enable the project references on
the WAR project, it loses the dependencies to the artefact in the
workspace. If I disable the project references, the jar references are
being used correctly.
Any idea what the problem could be. I don't get any error.
Regards,
Thomas
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
