[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4703) Include pi4soa CDL editor plugins into JBT

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12484069#action_12484069 ] 

Nick Boldt commented on JBIDE-4703:
-----------------------------------

After a few more tweaks and refactorings, I have pi4soa building (no tests, just runtime, sources, sdk) using the Athena harness.

To run it locally, check it out from svn and rename the appropriate build.properties.example.* file for your OS, then adjust the paths for workspace, build dir , and JVM accordingly.

https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/trunk/releng/

---

However, integrating it into the existing JBT build will be tricky since it depends on:

1. These plugins from Eclipse Orbit: org.apache.xml.resolver, javax.xml, org.apache.xml.serializer, org.apache.xerces, org.apache.xalan
2. This plugin from Mozilla: org.mozilla.xpcom_1.8.1.3-20080312.jar

I could set up a separate Hudson build for pi4soa and then later integrate the pi4soa update site zip into the JBT update site zip as a downstream step; then, the JBT uberbuild would treak pi4soa as a requirement (like the Drools runtime) rather than a build (like the Drools IDE).

---

As to categorization on the JBT update site, I can easily create a new category for Savara tools, if we want to collect them and keep them separate from the core JBT runtimes. Of course if there's only ONE feature at the moment - pi4soa - does it need its own category?

> 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