Igor Fedorenko <[EMAIL PROTECTED]> wrote on 16/06/2008 11:43:31:
> Maven projects with packaging=war will be automatically configured as
> Dynamic Web WTP project during project import or update configuration
> action. All relevant project dependencies will be added to WTP J2EE
> Module Dependencies (and removed from Maven Dependencies) and J2EE
> Module Dependencies and Maven Dependencies will be automatically updated
> as projects dependencies change.
>
> There is still some bugs/limitations in this area, but this mostly works
> ;-) You may want to try to create/import WAR project in WTP 2.0.x and
> see how changes to dependencies in POM get reflected in J2EE Module
> Dependencies.
But that is the bit that is not working.
I have a WAR project that I "Update Project Configuration" on. The pom of
this war file has three major dependencies in it.
A tools project, that has been released and deployed. This one does show
up in the list of maven managed dependicies, just like any other jar
files.
It has a resource jar (as a JAR project) that is listed as a dependency of
the WAR project. The resource jar's version is 1.0-SNAPSHOT and it exists
in the same workspace.
There is also the EJB jar (as an EJB project) and ditto for the version
and workspace.
The EJB and Resource jar's are not being included, nor are the being
updated as a referenced project.
Is that what you expect?
Lunch time for me. I don't think too well on an empty stomach... :-)<back
soon>
-Chris
**********************************************************************
CAUTION - This message is intended for the addressee named above. It may
contain privileged or confidential information.
If you are not the intended recipient of this message you must:
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer
immediately.
Internet emails are not necessarily secure. Australian Associated Motors
Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not
accept responsibility for changes made to this message after it was sent.
Unless otherwise stated, views expressed within this email are the author's own
and do not represent those of AAMI.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
