[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=12484222#action_12484222 ] 

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

Well, my eventual goal with JBT/JBDS is this:

a) each component builds and runs its tests independently. Therefore component owners are only responsible for their own "run it locally or in Hudson" microbuild, which might take as much as 5-20 mins to run, including tests.
b) JBT is nothing more than an aggregator build, in the same way that Galileo aggregates 30+ Eclipse projects into a single update site. Additional integration-related tests may be run here.
c) JBDS is nothing more than a repackaging of the JBT update site into an installer, and a rebranded update site. Additional integration- and -installer-related tests may be run here.

So, Savara as a single offering would be like (b) above, and then it too would be aggregated into JBT. Thus everyone can "own" their own component build and someone like myself would be responsible for the work to aggregate the pieces into a larger bundle (namely, an update site and/or zip).

---------

As to refactoring to run tests, convention can be seen here:

http://anonsvn.jboss.org/repos/jbosstools/trunk/jmx/tests/
http://anonsvn.jboss.org/repos/jbosstools/trunk/jmx/features/org.jboss.tools.jmx.tests.feature/

Generally, if your test plugin is for org.foo.functionality, the test will be called org.foo.functionality.test. You may split into org.foo.bar.ui and org.foo.bar.core, and thus have org.foo.bar.ui.test and org.foo.bar.core.test. You may also use ".tests" if you prefer that to ".test"

I would prefer if YOU do this refactoring. Once done I'll hook up the tests to the build and verify they can be run headlessly. Sound like a fair share?

> 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