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 2008/01/17 22:58:34 UTC

[jira] Commented: (UIMA-708) fix maven build so eclipse:eclipse goal doesn't add src/main/resources/META-INF/LICENSE, NOTICES, and DISCLAIMER

    [ https://issues.apache.org/jira/browse/UIMA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560100#action_12560100 ] 

Marshall Schor commented on UIMA-708:
-------------------------------------

These issues have been previously discovered and reported on - see http://issues.apache.org/jira/browse/UIMA-521 .

The 3 files have to be in the source tree when generating sources using the maven goal source:jar (used to deploy to the maven repository.)

The proper fix seems to be to leave things as is, but skip the copying if the goal is eclipse:eclipse.

> fix maven build so eclipse:eclipse goal doesn't add src/main/resources/META-INF/LICENSE, NOTICES, and DISCLAIMER
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-708
>                 URL: https://issues.apache.org/jira/browse/UIMA-708
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Trivial
>
> Currently, every time you run eclipse:eclipse, the parent POM is configured for the life-cycle phase of generate-resources to run an ant script to copy the LICENSE, NOTICES, and DISCLAIMER files into the source tree, and because eclipse:eclipse runs the phases up to "generate-resources" (see http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html where it says: "Invokes the execution of the lifecycle phase generate-resources prior to executing itself."), these files end up in the source tree, and need to be manually deleted.
> Change this to the maven-way of doing this:  add a <resources> element to the parent POM that is configured to add these files to the meta-inf of the result.
> Adam said that he tried this earlier, and got strange failures.  I just tried it and it seems to work now.  I ran the whole build, both install and assembly:assembly.  So, I think the prior issues have been resolved with the 2.0.7  level of Maven (current level is now 2.0.8).

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