[
https://issues.jboss.org/browse/ARTIF-16?page=com.atlassian.jira.plugin.s...
]
Brett Meyer edited comment on ARTIF-16 at 8/25/15 12:36 PM:
------------------------------------------------------------
Work in progress:
https://github.com/brmeyer/s-ramp/tree/ide. TODOs:
1.) Needs switched to an approach similar to
https://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts (pom-first, as
opposed to the manually-maintained manifest-first approach the PR has now)
2.) pom.xml utilizes a Kepler-specific repo. Research what that implies for other Eclipse
versions. It's unknown how version-specific the dependencies really are...
3.) Search and replace all instances of "s-ramp", "sramp", etc.
Replace with new Artificer nomenclature.
was (Author: brmeyer):
Work in progress:
https://github.com/brmeyer/s-ramp/tree/ide. Needs switched to an
approach similar to
https://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts
Eclipse IDE: S-RAMP tooling
---------------------------
Key: ARTIF-16
URL:
https://issues.jboss.org/browse/ARTIF-16
Project: Artificer
Issue Type: Task
Components: IDE Integration
Affects Versions: 0.6.0.Final
Reporter: Kurt Stam
Fix For: 1.1.0.Final
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.15#6346)