[
https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s...
]
Stefan Bunciak commented on SRAMP-16:
-------------------------------------
SRAMP-626 is going to be a big deal of help. Thanks!
{quote}
Can you bump sramp.version up to 0.6.0.Final or, even better, 0.7.0-SNAPSHOT?
{quote}
Sure.
{quote}
Are you guys interested in any feedback, yet? Really, it's just a few nitpicky
improvements for the look and feel. Functionality wise, this is great.
{quote}
Of course we are ;-)
{quote}
Once you're satistifed with where it's at, I'd say let's go ahead and
integrate it as a module in the actual project, but within a branch until it's
"finished".
{quote}
I suppose we could consider it finished later this month. It depends on how much feedback
will you give us, but basically from functionality perspective I think we are done for
now. So, once we incorporate your feedback we can send a pull request.
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)