[
https://jira.jboss.org/jira/browse/JBIDE-4703?page=com.atlassian.jira.plu...
]
Gary Brown commented on JBIDE-4703:
-----------------------------------
Not sure why the dependency on those plugins would be a problem - but the solution you
suggest sounds reasonable to me.
In terms of the category - there will be other Savara related plugins appearing in the
future, some internal and others in external repositories. So just thinking that it would
be good to bundle all these features/plugins into a single managed unit associated with
the Savara project - rather than having (for example) the pi4soa plugins on a separate
update site.
So rather than change things in the near future, thought it would be best to structure the
builds in preparation for the additional plugins.
Include pi4soa CDL editor plugins into JBT
------------------------------------------
Key: JBIDE-4703
URL:
https://jira.jboss.org/jira/browse/JBIDE-4703
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.1.0.M3
Reporter: Gary Brown
Assignee: Nick Boldt
Fix For: 3.1.0.M4
The pi4soa project provides a WS-CDL editor and associated capabilities that are required
for project Overlord.
The location of the pi4soa plugins is at:
https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/trunk
There are two features that need to be included: org.pi4soa.feature.core and
org.pi4soa.feature.monitor.
The monitor feature and associated plugin may only be required temporarily, as a web
based monitoring UI is being developed, but for now it is required.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira