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

[Gary Brown (JIRA)]

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

Gary Brown commented on JBIDE-4703:
-----------------------------------

Final comment for tonight - I think it is a classloader issue.

Correct me if I am wrong, as you probably have a better understanding of the internals of Eclipse plugin architecture, but when the unit tests are run inside Eclipse, it is simply a Java app using the normal classpath mechanism - so classes in different plugins are loaded with the same class loader used by the test.

However when running the test in the headless build, it is creating deployed plugins, so when the tests are run they are within their own OSGi bundle and class loader. So the tests, and the classes they are testing, are effectively in different classloaders - which seems to cause the normal package scope rules a problem.

If I run the junit tests as a Plug-in Test, then I get the same failures.

So I think the only option would be to make the relevant methods public - any other suggestions?


> 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
>
>         Attachments: test.xml_3.zip, testresults.zip
>
>
> 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