[
https://jira.jboss.org/jira/browse/JBIDE-5840?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5840:
--------------------------------------------
Stop/Start would work as connect/disconnect.
If this is considered more like a svn/cvs kinda of thing maybe it's just a matter of
naming things so they don't "overlap" conceptually ?
About running standalone - well, a majority of all our plugins are build to run standalone
and requiring WTP doesn't mean requiring *all* parts of WTP.
The Teiid designer would be dragging in DTP anyway which would make the adding of WTP
server core/view a minimal addition I would say - but I do understand your concern.
Deployment is something the server view actually does - but if your deployment is more
like a "commit" then maybe the modeshape should be a Team provider instead ?
p.s. is any of the modeshape guys going to be at EclipseCon ?
Modeshape should use the existing publishing framework and server
view
----------------------------------------------------------------------
Key: JBIDE-5840
URL:
https://jira.jboss.org/jira/browse/JBIDE-5840
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: modeshape
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: LATER
Were reading the docs in modeshape plugin and screenshots (couldn't get it to run
outofbox - probably some misconfig in my eclipse)
and noted that this seem to be duplicating both resource filtering, deployment, console
and server views for the modeshape repositiories.
That sounds/feels very redundant.
Why not create a WTP Server which can deploy these things instead of a complete separate
and duplicate functionality ?
--
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