You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2009/08/28 21:16:32 UTC

[jira] Created: (UIMA-1536) move RunWithJarPath into its own project

move RunWithJarPath into its own project
----------------------------------------

                 Key: UIMA-1536
                 URL: https://issues.apache.org/jira/browse/UIMA-1536
             Project: UIMA
          Issue Type: Bug
          Components: Build, Packaging and Test, Tools
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor


Testing reveals some issues using RunWithJarPath.  
* it should use parent-first class loading.  without this, it causes LinkageErrors if one of the jars in its path duplicates a base Java Jar (as is the case: for JMX Beans in Java 5 vs 6).
* it should be in a jar by itself or with just its dependencies, because anything else in its jar cannot see the new classes (since its jar was loaded by the parent).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (UIMA-1536) move RunWithJarPath into its own project

Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.

     [ https://issues.apache.org/jira/browse/UIMA-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor closed UIMA-1536.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3

> move RunWithJarPath into its own project
> ----------------------------------------
>
>                 Key: UIMA-1536
>                 URL: https://issues.apache.org/jira/browse/UIMA-1536
>             Project: UIMA
>          Issue Type: Bug
>          Components: Build, Packaging and Test, Tools
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.3
>
>
> Testing reveals some issues using RunWithJarPath.  
> * it should use parent-first class loading.  without this, it causes LinkageErrors if one of the jars in its path duplicates a base Java Jar (as is the case: for JMX Beans in Java 5 vs 6).
> * it should be in a jar by itself or with just its dependencies, because anything else in its jar cannot see the new classes (since its jar was loaded by the parent).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.