[JBoss JIRA] (ARTIF-16) Eclipse IDE: S-RAMP tooling
by Brett Meyer (JIRA)
[ 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)
8 years, 10 months
[JBoss JIRA] (ARTIF-759) Add an Aesh "web console" to the web UI
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-759:
---------------------------------
Summary: Add an Aesh "web console" to the web UI
Key: ARTIF-759
URL: https://issues.jboss.org/browse/ARTIF-759
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
An Aesh contributor created the ability to run an Aesh console in the web browser. It would be interesting to try and incorporate this into the Artificer web UI, allowing full Artificer CLI use without actually having the shell distro installed (ala, "thin clients").
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (ARTIF-759) Add an Aesh "web console" to the web UI
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-759?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-759:
------------------------------
Description:
An Aesh contributor created the ability to run an Aesh console in the web browser. It would be interesting to try and incorporate this into the Artificer web UI, allowing full Artificer CLI use without actually having the shell distro installed (ala, "thin clients").
https://github.com/aeshell/nanook
was:An Aesh contributor created the ability to run an Aesh console in the web browser. It would be interesting to try and incorporate this into the Artificer web UI, allowing full Artificer CLI use without actually having the shell distro installed (ala, "thin clients").
> Add an Aesh "web console" to the web UI
> ---------------------------------------
>
> Key: ARTIF-759
> URL: https://issues.jboss.org/browse/ARTIF-759
> Project: Artificer
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> An Aesh contributor created the ability to run an Aesh console in the web browser. It would be interesting to try and incorporate this into the Artificer web UI, allowing full Artificer CLI use without actually having the shell distro installed (ala, "thin clients").
> https://github.com/aeshell/nanook
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (ARTIF-758) Support Bower
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-758:
---------------------------------
Summary: Support Bower
Key: ARTIF-758
URL: https://issues.jboss.org/browse/ARTIF-758
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Bower is a general "package manager for the web", allowing a web developer to grab frameworks through dependency management (identified through a JSON file). Dependencies can be defined by simple URLs.
It would be really interesting to try creating a new web service that would serve up whatever format Bower expects, allowing Artificer artifacts to be used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (ARTIF-757) Extend query syntax to allow all endpoints "somehow connected" to another
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-757:
---------------------------------
Summary: Extend query syntax to allow all endpoints "somehow connected" to another
Key: ARTIF-757
URL: https://issues.jboss.org/browse/ARTIF-757
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Example: Find all Organizations "somehow connected" to this specific schema. That path would look something like XSD -> WSDL -> service -> organization. But the goal would be to find *all* organizations "somehow" using that schema. This would be extremely useful to incorporate into the relationship visualizations for use during impact analysis.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (ARTIF-756) Weight some relationships heavily over others
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-756?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-756:
------------------------------
Parent: ARTIF-694
Issue Type: Sub-task (was: Feature Request)
> Weight some relationships heavily over others
> ---------------------------------------------
>
> Key: ARTIF-756
> URL: https://issues.jboss.org/browse/ARTIF-756
> Project: Artificer
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> This one really needs thought through. When the UX team and I were discussing relationship visualizations, they asked whether or not one relationship could be weighted over another. It's a great question.
> Ex: A WSDL imports an XSD and uses its type declarations. Realistically, the relationship showing a specific Message's use of a specific ComplexTypeDeclaration is "more useful" than the general WSDL-imports-XSD relationship. If the former could be heavily weighted and highlighted on the visualization, as opposed to the latter, it might be helpful...
> The usefulness extends beyond purely the visualizations.
> Since the weighting would be highly context-specific, this might need rolled into ArtifactBuilder itself.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (ARTIF-756) Weight some relationships heavily over others
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-756:
---------------------------------
Summary: Weight some relationships heavily over others
Key: ARTIF-756
URL: https://issues.jboss.org/browse/ARTIF-756
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
This one really needs thought through. When the UX team and I were discussing relationship visualizations, they asked whether or not one relationship could be weighted over another. It's a great question.
Ex: A WSDL imports an XSD and uses its type declarations. Realistically, the relationship showing a specific Message's use of a specific ComplexTypeDeclaration is "more useful" than the general WSDL-imports-XSD relationship. If the former could be heavily weighted and highlighted on the visualization, as opposed to the latter, it might be helpful...
The usefulness extends beyond purely the visualizations.
Since the weighting would be highly context-specific, this might need rolled into ArtifactBuilder itself.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months