[
https://issues.apache.org/jira/browse/UIMA-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-709.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.3
This change generates the MANIFEST.MF that Eclipse needs. Therefore, after
checking out the eclipse plugin projects, the maven command to set things up
has to include building up to and including the packaging phase, in addition to
doing eclipse:eclipse.
A typical way to build from a fresh checkout would be:
mvn install eclipse:eclipse
or if you have old versions of things you want to get rid of, try
mvn clean install eclipse:clean eclipse:eclipse
> eclipse plugins won't compile if uimaj-ep-runtime project is open
> -----------------------------------------------------------------
>
> Key: UIMA-709
> URL: https://issues.apache.org/jira/browse/UIMA-709
> Project: UIMA
> Issue Type: Improvement
> Components: Eclipse plugins
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.3
>
>
> The Eclipse plugin, uimaj-ep-runtime, is a "library" plugin, containing jars
> from other projects. It is built during the release by custom assembly code.
> When the project is in the workspace and is "open", it is currently "empty"
> because it has no source in it. Other plugin projects which depend on this
> fail to compile, because they look to this empty plugin for classes (and find
> none).
> Find some approach to allow Eclipse builds (as well as maven builds) to
> succeed, without copying or having duplicate resources, so Eclipse
> compilation can succeed with this project present / open.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
