uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-1501) more refactoring and updating - parent POMs
Date Mon, 24 Aug 2009 14:27:59 GMT

    [ https://issues.apache.org/jira/browse/UIMA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746894#action_12746894

Marshall Schor commented on UIMA-1501:

Several projects which have test code were putting the test resources into the build jar.
 I've moved these (by changing the <build>   -> <resources> ... to <build>
-> <testResources>...

Sometimes, the "documentation" (or README file) was suggesting that these same resources serve
as examples; for these, added a note to the docs to point to the test folders.  This keeps
the Jars that are built to holding only that which is needed by the runtime.
Most projects were duplicating standard boilerplate.  This is being factored via using <parent>
pom links specific to our UIMA projects. See http://cwiki.apache.org/UIMA/maven-tips.html
on our wiki for a summary of the factoring.

A side effect of factoring is that the parent POMs must be built & installed first (if
working on unreleased versions - for released versions, they will be found in the maven repos).
 These can be built & installed without triggering the build of all the modules (in some
of them) by using the -N parm on the mvn command.
Version info is in most POM in 2 places: as part of its ID, and as part of the <parent>
Version info for common components that are part of UIMA are mostly factored up into the uimaj
POM, and need be updated only there.  The other POMs will inherit these versions.

> more refactoring and updating - parent POMs
> -------------------------------------------
>                 Key: UIMA-1501
>                 URL: https://issues.apache.org/jira/browse/UIMA-1501
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
> use pluginManagement and dependencyManagement to refactor additional items.  Update to
javadoc plugin 2.5 (the current level - what the superPom specifies).

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

View raw message