[overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling
[
https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s...
]
Brett Meyer commented on SRAMP-16:
----------------------------------
(CC [~eric.wittmann] & [~objectiser])
[~bouskaj], hello! Glad to have your help!
The approach looks like a great start! You've encompassed the 2 main use cases:
uploading an artifact to S-RAMP, and downloading artifacts from S-RAMP and incorporating
them into your project. Here's a few comments:
- When you upload an artifact, it would be useful to use a popup screen where the user
could provide artifact metadata (name, artifact type, properties, etc.).
- Your S-RAMP repo screen currently has 1 "Query" box. Definitely keep that --
that will allow developers to use the S-RAMP query language. However, we might also need
a sidebar with an advanced search form, really similar to what the web UI has. That way,
users can still filter the artifacts, even if they don't know the full query
language.
Other than that, you're on the right track! Thanks again for the help!
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
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.1#6329)