Re: Hotfix or next release

[Danai Wiriyayanyongsuk <da...@gmail.com>]

Guys,

Either hotfix or plain release, it'd be very helpful to have the fix for
https://issues.apache.org/jira/browse/UIMA-583.

If it's going to be a release, adding the feature in the following link
will be a tremendous help:
http://cwiki.apache.org/confluence/display/UIMA/UIMA+Requirements?showComments=true#comments


Best,
Danai Wiriyayanyongsuk



On 9/27/07, Thilo Goetz <tw...@gmx.de> wrote:
>
> Yes, but I haven't seen any complaints.  Is it really
> worth doing another release?  Go through all the testing
> and stuff?
>
> Adam Lally wrote:
> > On 9/27/07, Thilo Goetz <tw...@gmx.de> wrote:
> >> What's so urgent that requires a hotfix or release
> >> immediately?  I don't see anything that couldn't wait
> >> another couple of months, IMHO.  People can always
> >> build from source if there is a fix they must have.
> >>
> >
> > This one's pretty ugly:
> > http://issues.apache.org/jira/browse/UIMA-547
> >
> > -Adam
>

Re: Hotfix or next release

[Danai Wiriyayanyongsuk <da...@gmail.com>]

I think that https://issues.apache.org/jira/browse/UIMA-583 contains many
issues. I'm wondering if the first issue "if a PEAR file (pear descriptor)
is added to an aggregate AE the configuration parameters of the PEAR file
cannot be overridden by the aggregate AE." could cause issues with other
deployed PEARs. If not, it'd be great to have it fixed.

My two cents,
Danai Wiriyayanyongsuk


On 10/2/07, Michael Baessler <mb...@michael-baessler.de> wrote:
>
> Danai Wiriyayanyongsuk wrote:
> > Guys,
> >
> > Either hotfix or plain release, it'd be very helpful to have the fix for
> > https://issues.apache.org/jira/browse/UIMA-583
> From my point of view, we will just document the points raised in issue
> UIMA-583 and we will not provide a fix in the implementation.
> PEAR archives are currently a kind of black box components. Some users
> may don't know the details about the PEAR content and they just want to
> run it.
> If a PEAR file automatically can share resources this can cause issues
> with other deployed PEARs.
>
> The improvements suggested in issue UIMA-583 are absolutely correct and
> should be implemented in the future,
> but I think there are some other points to consider.  So for example the
> PEAR component descriptor used for a PEAR maybe has $main_root
> variables that are replaced when the PEAR file is installed. If that is
> the case the same component descriptor cannot be used before the
> component is
> packages as PEAR. You have to maintain two descriptors. I think these
> are all requirements that should be discussed and solved for the next
> PEAR generation.
>
> -- Michael
>
>

Re: Hotfix or next release

[Michael Baessler <mb...@michael-baessler.de>]

Danai Wiriyayanyongsuk wrote:
> Guys,
>
> Either hotfix or plain release, it'd be very helpful to have the fix for
> https://issues.apache.org/jira/browse/UIMA-583
 From my point of view, we will just document the points raised in issue 
UIMA-583 and we will not provide a fix in the implementation.
PEAR archives are currently a kind of black box components. Some users 
may don't know the details about the PEAR content and they just want to 
run it.
If a PEAR file automatically can share resources this can cause issues 
with other deployed PEARs.

The improvements suggested in issue UIMA-583 are absolutely correct and 
should be implemented in the future,
but I think there are some other points to consider.  So for example the 
PEAR component descriptor used for a PEAR maybe has $main_root
variables that are replaced when the PEAR file is installed. If that is 
the case the same component descriptor cannot be used before the 
component is
packages as PEAR. You have to maintain two descriptors. I think these 
are all requirements that should be discussed and solved for the next 
PEAR generation.

-- Michael