[
https://issues.apache.org/jira/browse/UIMA-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047503#comment-13047503
]
Richard Eckart de Castilho commented on UIMA-1967:
--------------------------------------------------
It would be really nice if the pom.xml would be on the top level, because that
way one can do a "Check out as maven project..." in Eclipse. There is the
downside of having the folders appear twice, but I don't think that really
hurts. Practically all of my Eclipse projects are Maven projects and most of
them are multi-module projects, some even using multiple levels of nested
modules. It works fine, you just have to be aware of what is happening behind
the scenes when you delete something or work with subversion. I think people
that employ m2eclipse are quite aware of what happens. For the adventurous
there is an option "Hide folders of phyiscally nested modules" in the m2eclipse
preferences which is marked "experimental" - I never tried it out.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
