On 1/13/2013 4:20 PM, Richard Eckart de Castilho (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/UIMA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552315#comment-13552315 > ] > > Richard Eckart de Castilho commented on UIMA-2560: > -------------------------------------------------- > > Created branches of uimaj and build for this issue because these changes > should be well tested and may need amendments: > > * Upgraded maven-bundle-plugin to 2.3.7 which is required for m2e to support > the *Embed-Dependency* directive (see FELIX-3061). Note this may require the > m2e tycho plugin to work properly. I tried running the CAS Editor before this > change and got ClassNotFound exceptions. After the upgrade, the classes were > found. > * Removed *inline* from the *Embed-Dependency* directive in uimaj-ep-runtime, > because inlined artifacts are not supported by FELIX-3061. _*Is there a > special reason for inlining?*_ I think inlining was intended to get the artifacts included, but the copy/unpack dependencies also does that. So maybe not an issue?
> * Removed maven-dependeny-plugin/unpack-dependencies execution from > uimaj-ep-runtime. now put back (as copy-dependencies) > * Ignoring any runs of the maven-dependency-plugin in the master pom. Affects > *docbook processing* and profiles *build simple project binary assembly* and > *build OSGi bundle for annotator*. Docbook processing is probably not > required in Eclipse builds. I didn't fully investigate the purpose of the > plugin in the profiles, possibly it shouldn't even be in the OSGi profile > (see comments above on uimaj-ep-runtime). I don't really understand this :-)... However, it's a good thing to bypass lots of "build" processing with m2e, where there's no point (it just slows down import and setup). So, for example, building the docbooks is usually not of interest. When it is of interest, you can always do the maven command or in Eclipse, right-click on the project and choose run-as mvn install, etc. The m2e build should just be for things in the workspace which users would want always up-to-date rebuilt. > * Goals for plugins *maven-remote-resources-plugin* and > *uima-build-helper-maven-plugin* activated per m2e configuration in master > pom. This is probably not useful. These are there to follow legal release requirements. During local development, they would just slow things down a bit. -Marshall > > >> Eclipse m2e complains about unmapped maven plugins >> -------------------------------------------------- >> >> Key: UIMA-2560 >> URL: https://issues.apache.org/jira/browse/UIMA-2560 >> Project: UIMA >> Issue Type: Bug >> Components: Build, Packaging and Test >> Affects Versions: parent-pom-4 >> Reporter: Richard Eckart de Castilho >> Assignee: Richard Eckart de Castilho >> Fix For: parent-pom-5 >> >> >> Recent versions of Eclipse m2e complain about Maven plugins in the UIMA >> master pom not being covered by m2e lifecycle plugins: >> * uima-build-helper-maven-plugin >> * maven-dependency-plugin >> Add m2e metadata to the master POM to handle these. > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira >
