[
http://jira.jboss.com/jira/browse/JBIDE-1820?page=comments#action_12401271 ]
Max Andersen commented on JBIDE-1820:
-------------------------------------
FYI I Fully agree.
this file is a leftover from before Exadel plugins were built on eclipse. We have it on
our roadmap to dissolve these things - being made aware of specific issues in them will
help us.
Please use the standard Eclipse files for project dependencies the
org.jboss.tools.jst.web.xml is a complete mess
-----------------------------------------------------------------------------------------------------------------
Key: JBIDE-1820
URL:
http://jira.jboss.com/jira/browse/JBIDE-1820
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Affects Versions: 2.0.0.GA
Environment: Windows, any really
Reporter: Stephen Westbom
Assigned To: Viacheslav Kabanovich
Priority: Critical
The org.jboss.tools.jst.web.xml file duplicates information that is already contained in
the .classpath file and the org.eclipse.wst.common.component file in the settings
directory and does it pretty badly (no java environment variables supported, it puts jar
files in the web-inf/lib directory that Eclipse should do at build time only). This just
adds yet another place to configure a project's artifacts, lots of broken project
settings because of conflicts and incompatibility with Maven 2.
Can this be cleaned up in future releases? It is as if the plugin was built with no
prior knowledge of Eclipse.
These changes are critical to having a usable tool. Right now I cannot use the plugin
for much more than editing JSF pages and building broken deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira