[
https://issues.apache.org/jira/browse/UIMA-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756140#action_12756140
]
Marshall Schor commented on UIMA-1575:
--------------------------------------
Turns out we can't use the dependency:dependency-copy plugin to copy the
artificats from the Maven repos because maven renames the jars in the repo to
<artifactId>-<version>.jar and plugins are required to have a match between
the jar name and the "id" of the plugin. Instead, copy from the project's
/target dir - this will require the projects be checked out before building,
and put into the usual "flat" hierarchy corresponding to the Eclipse workspace.
> Change eclipse update site and feature generation to use common maven
> mechanisms
> --------------------------------------------------------------------------------
>
> Key: UIMA-1575
> URL: https://issues.apache.org/jira/browse/UIMA-1575
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.3
>
>
> Change the Eclipse update site generation:
> 1) make the Feature projects into maven projects, adding a pom specifying
> "jar" packaging, and making the jar have the normal LIC/NOT/DIS and the
> feature.properties and feature.xml files
> 2) make the update site into a maven projects, having its pom:
> * invoke the feature poms to build those features
> * use dependency:dependency-copy to copy plugin artifacts into its plugin
> directory
> * use dependency:dependency-copy to copy the feature jar artifacts into its
> features directory
> * use the ant-run plugin to build the update site
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
