[
https://jira.jboss.org/jira/browse/JBIDE-2516?page=com.atlassian.jira.plu...
]
arne anka commented on JBIDE-2516:
----------------------------------
don't know what magic does that.
right click the project->properties
-> java build path: add a library
-> j2ee module dependencies: check the new entry
and after that it will be deployed to jboss when deploying/republishing the web app.
thus i'd expect the achiver to do the same kind of magic.
build path' referenced libraries not included in war
----------------------------------------------------
Key: JBIDE-2516
URL:
https://jira.jboss.org/jira/browse/JBIDE-2516
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 2.0.1
Environment: eclipse 3.3.2, jboss tool 2.0.1.GA (dunno why it's not listed
above)
Reporter: arne anka
creating a war in archive view (why no entry in context menu? that view is not really
intuitive) results in a war not deployable -- jboss complains over not being able to
create smth.
further research shows that libraries referenced in the build path (and _not_ physically
located in WEB-INF/libs/) are _not_ included while creating the war.
deploying the application from the jboss ide includes those libs, though -- but for
productive use the app needs to be packed as war and thus include even libs only
referenced ...
a workaround might be to create a fileset by hand -- but because those libs are spread
over several places it's a rather tedious task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira