[
https://issues.apache.org/jira/browse/UIMA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796929#action_12796929
]
Richard Eckart de Castilho commented on UIMA-1716:
--------------------------------------------------
Regarding the release: I have been looking around in Maven archives, but I can
only find the UIMA-J artifacts, no released UIMA sandbox artifacts in any Maven
repository I know of. If they have been released, have they also been uploaded
to a Maven repository?
Regarding m2eclipse: Yes, that is quite different from the maven eclipse
plugin, since it is not a maven plugin, but an eclipse plugin. I am using the
latest developer snapshot version 0.9.9.200912160759 which has come a long long
way since the last official release. I have been using their stable releases
for quite some time and successfully used the latest 2-3 developer snapshots.
1) Creating a nested module is quite straight forward: in the included POM
editor, just add a new module. A wizard will guide you through the rest.
2) To manually import an existing nested module into Eclipse not quite as
intuitive, but also straight forward: select the parent project, which contains
the module and select "Import -> Existing Maven projects". A wizard will show
all the nested modules that are registered as modules in the POM and offer to
import them. They will become Eclipse projects then.
3) To add a new nested module to SVN is unfortunately not straight foreward - I
hope this will be facilitated in future: Create the module as said before in
1). Then close the module project in Eclipse, then delete it from the workspace
(not from disk). Go to the parent project and add the nested module to SVN, add
the usual suspects (.settings, etc.) to svn:ignore and commit. Then use 2) to
add the nested module back to Eclipse.
It takes a moment to become comfortable with the fact that the nested Maven
structure is shown as a flat project structure in Eclipse and that file
actually occur multiple times in the workspace (once nested in the parent
project and once in the actual module project). M2eclipse seems to offer an
experimental feature to actually hide the folders of nested projects to avoid
this duplication, but I didn't try that so far.
Given the three points listed above, I am very happy with m2eclipse. In
particular it has a great POM editor and supports access to Nexus indexes,
which allows for name completion features in the POM XML and form-based POM
editor etc. In my opinion it's definitely worth an in-depth try.
For our research group, we have a development setup using Eclipse with
m2eclipse, Artifactory (an alternative to Nexus) and Hudson for all our UIMA
component projects.
The m2eclipse update site to use is: http://m2eclipse.sonatype.org/update-dev/
Make sure you install all the listed plugins - you may leave out the WTP
project configurator if you don't plan to use WTP.
Ah: 4) if something seems odd in a project use Maven->Update project
configuration to have m2eclipse regenerator the project metadata (.settings,
.project, .classpath) from the POM - that usually fixes things.
> UIMA Sandbox components in tag 2.2.2 are 2.3.0-SNAPSHOT
> -------------------------------------------------------
>
> Key: UIMA-1716
> URL: https://issues.apache.org/jira/browse/UIMA-1716
> Project: UIMA
> Issue Type: Bug
> Components: Sandbox
> Affects Versions: 2.2.2
> Reporter: Richard Eckart de Castilho
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> All the POMs in the UIMA Sandbox tag 2.2.2-incubating claim that they are
> 2.3.0-incubating-SNAPSHOT. I know that tags should not be changed, but I
> would still vote for fixing those versions and also have them depend on UIMA
> 2.2.2-incubating if possible. Obviously Marshall Schor has changed this after
> the tagging as part of UIMA-1461 in revision 798670, which unfortunately
> lacks any explanation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
