[
https://issues.apache.org/jira/browse/UIMA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-5384:
---------------------------------
Summary: uv3 migration tool class path setup (was: uv3 migration tool PEAR
class path add)
> uv3 migration tool class path setup
> -----------------------------------
>
> Key: UIMA-5384
> URL: https://issues.apache.org/jira/browse/UIMA-5384
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework, Tools
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 3.0.0SDK-beta
>
>
> The v3 migration code when migrating Pears takes care to add the pear
> classpath in front of the migrateClasspath. This fails in 2 cases 1) the
> migrate classpath is null, and when it contains java classpath wildcards.
> The v3 migration step where it compiles converted files doesn't use the
> proper classpath, especially with PEARs.
> The compile converted files classpath needs to have prefixed, the classpath
> for uimaj-core, v3.
> The migrateClasspath, when processing from classes roots, is used for
> decompiling, and must include uimaj-core v2.
> The migrateClasspath is required for decompiling, and may be required for
> compiling. It is not used when parsing source.
> The migrateClasspath, when decompiling inside a JAR, should have that Jar
> pre-pended to the classpath.
> When compiling classes,
> * the classpath should start with the migrateClasspath,
> * prepend any PEAR classpath
> * set the sourcePath compiler arg to converted/v3 to pick up any converted
> source (see
> http://docs.oracle.com/javase/8/docs/technotes/tools/windows/javac.html#BHCJJJAJ)
> * prepend the uv3 uimaj-core jar
> When compiling a class picked up from inside a JAR,
> * prepend the JAR
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
