[
https://issues.apache.org/jira/browse/UIMA-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969741#action_12969741
]
Jukka Zitting commented on UIMA-1967:
-------------------------------------
I've found that there's little downside to having m2eclipse import both the
top-level folder and sub-folders as separate projects. They're just two logical
views on the same physical data (there's also an experimental "Hide folders of
physically nested modules" option in the m2eclipse configuration, but I've
never tried that). The only time I've had some inconvenience with such setups
is with Mylyn that then unnecessarily notices updates to the same files in two
different projects.
If we want to keep the uimaj aggregate POM in a subfolder, then how about still
introducing a minimal top-level POM that simply lists uimaj as the only module.
That way a checkout could be easily built from the top level but people could
still use the uimaj POM when importing to Eclipse.
> UIMAJ build from the top level
> ------------------------------
>
> Key: UIMA-1967
> URL: https://issues.apache.org/jira/browse/UIMA-1967
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Affects Versions: 2.3.1
> Reporter: Jukka Zitting
> Priority: Minor
>
> The uimaj 2.3.1 source release package is a bit misleading in that it places
> a copy of the uimaj/README file in the top level directory even though the
> advertised "mvn install" build command doesn't work from there.
> Instead of fixing that problem, it would seem like a good idea to actually
> move the uimaj/pom.xml and uimaj/README files directly to the top level
> directory in svn.
> As a potential further simplification, it seems to me like it would be
> possible to merge also the uimaj-distr/* and aggregate-uimaj/pom.xml files to
> the top level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
