Re: UIMA sandbox component build

2006-12-13 Thread Adam Lally

On 12/13/06, Michael Baessler [EMAIL PROTECTED] wrote:

- To package a analysis component as pear file we have to use eclipse,
since we do not have a pear packager outside of eclipse. So users have
to use eclipse if they want to package an analysis component.


Hmmm.. how hard would it be to have a pear packager that runs outside
of Eclipse?  It does seem like a poor dependency to have since we
claim UIMA doesn't require Eclipse.


- To package the analysis component correctly we have to put the
resource and the code to the directories specified in the pear
description (UIMA nature) layout but this layout does not match the
Maven layout.



I thought the default PEAR directory layout was optional.  It would be
nice if the Maven layout were supported.

-Adam


Re: UIMA sandbox component build

2006-12-13 Thread Michael Baessler

Adam Lally wrote:

Hmmm.. how hard would it be to have a pear packager that runs outside
of Eclipse?  It does seem like a poor dependency to have since we
claim UIMA doesn't require Eclipse.
So in that case we can also think about creating a pear package during 
the build.
I will check if it is possible to redesign the code to have an API to 
build a pear package and

maybe to create a pear package during the build.

I thought the default PEAR directory layout was optional.  It would be
nice if the Maven layout were supported.
I don't think the UIMA nature is optional. Some of the directories must 
exist but maybe we can change that...


So our goal is to have a Maven based structure for the sandbox 
components and spend time to adapt the pear utilities on this.

Again, let me check how expensive this is...

-- Michael


Re: UIMA sandbox component build

2006-12-13 Thread Adam Lally

On 12/13/06, Michael Baessler [EMAIL PROTECTED] wrote:

 I thought the default PEAR directory layout was optional.  It would be
 nice if the Maven layout were supported.
I don't think the UIMA nature is optional. Some of the directories must
exist but maybe we can change that...



I think only the .metadata directory is actually required... but we
should check with Lev.


So our goal is to have a Maven based structure for the sandbox
components and spend time to adapt the pear utilities on this.
Again, let me check how expensive this is...



For the record, I don't know if it's critical to do this immediately.
I could be OK with a non-Maven build to start.  But it is an issue if
our PEAR Packager is not flexible enough to work with Maven, and we
should address that eventually.

-Adam