[
https://issues.jboss.org/browse/JBDS-2923?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2923:
--------------------------------------
[~maxandersen] I asked for investigation around the removal of PDE, so just for the
posterity, I can provide some arguments about why I opened this ticket:
* I wasn't aware that OSGi development is something we do actually want to support in
JBDS. (it's actually because there are some -around 0.1% maybe ;) - people doing Web
Development with OSGi that Eclipse JEE is shipped with PDE too)
* I just thought PDE might be there just because it has been implemented like that or to
re-use some basic of its APIs that might be avoidable.
* The cost of PDE is that the application is more complex, has more menus and more
features than what our average users (JEE/Mobile/Web developers) may need. So for those
who don't use PDE features, adding PDE actually reduce the quality of the
application.
But I'm fine with keeping it, since it is something we seem to actually want.
Verify whether JBDS really needs PDE
------------------------------------
Key: JBDS-2923
URL:
https://issues.jboss.org/browse/JBDS-2923
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: build
Reporter: Mickael Istria
Assignee: Alexey Kazakov
Priority: Minor
Fix For: 8.0.0.Beta2
It looks like by default, JBDS embeds PDE and its UI contributions, which are totally
off-topic.
We should consider removing PDE. For this we need to check what depends on it first.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)