[JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling
by Jan Bouška (JIRA)
[ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s... ]
Jan Bouška commented on SRAMP-16:
---------------------------------
[~brmeyer] PoC folder is not actual. Look at https://github.com/bouskaJ/-S-RAMP_repository_browser/tree/master/final/S... .
> 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)
10 years
[JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s... ]
Stefan Bunciak commented on SRAMP-16:
-------------------------------------
Version updated, wsdl issue fixed (problem was when importing derived artifacts). You can give it another try ;-)
Do you have some estimate when SRAMP-626 could be fixed? I suppose you target it to 0.7.0, right?
> 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)
10 years
[JBoss JIRA] (SRAMP-628) Completely remove Fuse/Jetty/OSGi concepts
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-628:
---------------------------------
Summary: Completely remove Fuse/Jetty/OSGi concepts
Key: SRAMP-628
URL: https://issues.jboss.org/browse/SRAMP-628
Project: S-RAMP
Issue Type: Task
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 1.0
SRAMP-620 deprecated Fuse and Jetty support. In 1.0, take it further:
1.) completely remove the modules
2.) remove all OSGi dependencies
3.) remove Felix annotations
4.) replace "bundle" packaging with "jar"
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years