[
http://jira.jboss.com/jira/browse/JBIDE-468?page=comments#action_12358120 ]
Rob Stryker commented on JBIDE-468:
-----------------------------------
1) Because I'm not sure on how to parse it
2) Because I'm not sure how to access the EMF model that DOES parse it
3) Because I assume this information is available through the public APIs of the module,
ie the WebModule,. the EjbModule, etc., and when i do module.getName(), I'm assuming
it's drawing the name from the common.component file.
4) Because I'm really not sure where you're even reading about it or where people
find docs on this stuff. What draft manuscript are you talking about? Link?
Anyway, if I can at some point figure out how to use it I will. Right now if someone tries
to make a War package out of a POJP, it tries to make a logical config with what it's
given. If someone tries to do it out of a dynamic web project, it uses flexible project
APIs to try to find out the children (libraries), the structure, etc.
In the end, if the user doesn't like what he's given he can create his own package
custom. It's really not all that hard.
Integrate packaging with .settings/org.eclipse.wst.common.component
-------------------------------------------------------------------
Key: JBIDE-468
URL:
http://jira.jboss.com/jira/browse/JBIDE-468
Project: JBoss IDE
Issue Type: Feature Request
Components: Packaging
Reporter: Max Andersen
Reading "Eclipse WEb Tools Platform" draf manuscript and noticing them
describing .settings/org.eclipse.wst.common.component
Any reason why we don't (as an option) uses the info in here as a
"packaging" node/option ?
--
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