uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: [jira] Commented: (UIMA-1716) UIMA Sandbox components in tag 2.2.2 are 2.3.0-SNAPSHOT
Date Fri, 08 Jan 2010 22:35:32 GMT


Richard Eckart de Castilho (JIRA) wrote:
>     [ 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?
>   

I think the sandbox artifacts for 2.2.2 were not uploaded to any 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.
>   

I tried this.  I opened a pom having some modules, and in the "Overview"
panel, I clicked the "create" button on the "Modules" segment - it added
a module named "?", and allowed me to overtype that with a new module
name.  However, nothing else happened, even after I saved.  I expected
from your comment that some wizard with pop up to let me create the new
module itself...  but perhaps I misunderstood.

Now I see what I did wrong.  Instead of using the POM editor (editing
the parent POM and adding a new module), I used the Eclipse "New"
Wizard, and found it had a setting for creating a new Maven "Module". 
That worked.   It put the new "module" not in the Eclipse workspace but
rather under the parent pom's directory.  (The parent pom is not in the
workspace, because I "imported" it from its place on my local disk into
the workspace).
> 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.
>   

I tried importing some of the uimaj projects using a nested structure,
using the maven - import choice, and eventually got things more or less
working, including the eclipse plugins.
> 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.
>   

I'm trying to understand why just right clicking on the view of this in
the parent POM project (not the other view of this as a top level
Eclipse project) and saying Team -> commit, and then maybe just hitting
"refresh" on the other view where it is a project, doesn't work.  
(Note: I haven't tried this).
> 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.
>
>   

Thanks for that tip...

I also see there's a project, Tycho, which addresses making building
Eclipse plugins and osgi components work better with this setup (see
http://www.sonatype.com/people/2008/11/building-eclipse-plugins-with-maven-tycho/
).  We're currently using Apache Felix's "bundle" maven plugin for
this.  Do you have any experience with Tycho?  It looks like it might
not quite be ready for general use (from the release number).

-Marshall

Mime
View raw message