[
https://issues.apache.org/jira/browse/UIMA-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531536#comment-13531536
]
Marshall Schor commented on UIMA-2523:
--------------------------------------
I'll have to dredge my memory for why we went with separation of the <modules>
(aggregation) and sharing (parent-pom). IIRC, if you make the aggregation pom
and the sharing pom the same, then, if the aggregation pom has any builds to do
of its own, these can get (unintentionally) inherited by other things. See
http://stackoverflow.com/questions/1992213/maven-parent-pom-vs-modules-pom. I
think we had our top pom have longer-running kinds of things to build the
release, do the assemblies, javadocs, etc., and found it hard to not have
these inherited by others (if they used that same POM as their parent).
http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html
also discusses this from a best practices viewpoint.
> Rename module folders
> ---------------------
>
> Key: UIMA-2523
> URL: https://issues.apache.org/jira/browse/UIMA-2523
> Project: UIMA
> Issue Type: Bug
> Components: Sandbox-uimafit
> Reporter: Richard Eckart de Castilho
> Priority: Minor
>
> The module folders in uimaFIT do not match the artifactIds. The module
> folders use the capitalization "uimaFIT" while the artifactIds use "uimafit".
> The folders should be renamed to use the lower-case variant and the module
> section of the aggregator POM should be adjusted accordingly.
> The currently different capitalization might cause problems in Eclipse when
> patches are applied, as Eclipse uses the artifactId as the project name and
> consequently workspace locations have different names than their respective
> directories on the file system (cf. UIMA-2522).
--
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
