[overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling
[
https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s...
]
Stefan Bunciak commented on SRAMP-16:
-------------------------------------
Hi [~brmeyer]!
The 2 main use cases for the Eclipse plugins are basically finished - you can give it a
try https://github.com/bouskaJ/-S-RAMP_repository_browser/tree/master/PoC.
However, we are struggling with dependencies inclusion. As you will notice, the only
dependency is s-ramp-client, but it's transitive deps. makes the final plugin jar
quite big (including almost 40 other jars). My suggestion is to create a s-ramp-client
plugin that could be installed into the target platform/eclipse and S-RAMP IDE plugin
could just reference it in its MANIFEST as required bundle. Any hints on this? Thanks!
Eclipse IDE: S-RAMP tooling
---------------------------
Key: SRAMP-16
URL: https://issues.jboss.org/browse/SRAMP-16
Project: S-RAMP
Issue Type: Task
Components: IDE Integration
Affects Versions: 0.6.0.Final
Reporter: Kurt Stam
Assignee: Brett Meyer
Attachments: UIMockup.gliffy, UImockup.gliffy
Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several
interesting use cases. For instance, allowing an app developer to search for a WSDL in
S-RAMP, then pull it down into his/her project (all from within the IDE) would be
powerful.
One idea would be to look into writing this as a JBoss Forge plugin. Not only would we
gain Eclipse support, but also any other Forge-supported environment. The unknown is how
to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the
Forge shell.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)