[
https://issues.apache.org/jira/browse/UIMA-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968826#action_12968826
]
Marshall Schor commented on UIMA-1967:
--------------------------------------
I tried once moving the uimaj/pom.xml and README to the top level in SVN. When
checked out, they were of course in the same position in the working copy.
When then imported into Eclipse using m2eclipse, the project created for this
top level POM and README also had embedded folders for all the other projects
(duplicates of these were also created as top level Eclipse projects).
This is why I decided not to go with the suggested alternative. But perhaps I
did something wrong? Is there a way to have Eclipse play more "nicely" with
this hierarchical organization?
> 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.
