[
https://issues.apache.org/jira/browse/UIMA-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-392.
-----------------------------
Resolution: Fixed
Assignee: Adam Lally
I think I traced the problem to the Maven assembly plugin version 2.2 (which is
still a beta). I have changed our top-level pom to explicitly specify that
version 2.1 of the assembly plugin should be used.
I think I was trying out assembly plugin version 2.2 before and that's what
version was in my local maven repo and was being picked up by my subsequent
builds. So that's why others may not have seen this.
> Eclipse Plugin packaging not working correctly
> ----------------------------------------------
>
> Key: UIMA-392
> URL: https://issues.apache.org/jira/browse/UIMA-392
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: 2.2
> Environment: Maven 2.0.6
> Reporter: Adam Lally
> Assigned To: Adam Lally
> Fix For: 2.2
>
>
> For some reason our build is now producing an extra level of directories for
> the Eclipse plugins. For example the CDE plugin now has a top-level
> directory named "uimaj-ep-configurator-2.2-incubating-SNAPSHOT.zip" in the
> final build, which should not be there.
> I don't know what caused this. It was working fine for the 2.1.0 build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
