headers
Thilo Goetz | 1 Apr 18:01
Picon
Picon

Hotfix build process, was: [VOTE] [HOTFIX] release hot fix Eclipse plugin for UIMA CDE tool

Marshall Schor wrote:
> Michael Baessler wrote:
>> Marshall Schor wrote:
>>> One other issue I just remembered - this artifact is not "signed".  I 
>>> don't have the time right
>>> now due to other pressing things, so this looks like it will slip 
>>> into next week.
>> I absolutely agree with Thilo, we should fix and tag this in the 2.1.0 
>> branch. I think we should do things as good as we can to make it 
>> understandable
>> for all users. And providing hot fixes for a release that is based on 
>> trunk seems to me a little bit confusing.
>>
>> If there is there anything I can help with, please let me know.
> 
> Ok.  Please check this process.
> 
> 1) extract into a new workspace: uimaj / branches / uimaj-2.1.0
> 
> 3) put in the hot fix changes and build the uimaj-ep-configurator 
> project (only) and test in the workspace.
>    Check in to the SVN under the uimaj-2.1.0 branch
> 
> 3) "tag" the 2.1.0 branch with the hotfix as uimaj-2.1.0-hotfix-1-RC1
> 
> 4) sign the zip file (which is the release artifact)
> 
> 5) add my key to the SVN uima-distr/src/main/readme/KEYS (and publish to 
> a public key server).  It won't be "countersigned" by anybody - is that 
> OK for now?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 2 Apr 21:49

[VOTE][HOTFIX] [RETRY1] release hot fix Eclipse plugin for UIMA CDE tool

In this retry, the following has changed:
1) The artifact (the zip file which is the Eclipse plugin) now includes 
the standard DISCLAIMER, LICENSE, and NOTICES files.

2) A README-HOTFIX-1 was added and appears in the Zip file when unzipped. 

2) The artifact is signed; the website has the signature keys

3) The changes are made on top of the SVN 2.1.0 branch.

==========

The CDE fix in Jira: http://issues.apache.org/jira/browse/UIMA-364 has 
been packaged into a hotfix.

The hotfix consists only of one Eclipse Plugin project; this project 
(uimaj-ep-configurator) was tagged in SVN:

https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-ep-configurator-2.1.0-hotfix-1-RC1/uimaj-ep-configurator 

The artifact is located in 
http://people.apache.org/~schor/org.apache.uima.desceditor.2.1.0.incubating-hotfix-1.zip; 
this is a "binary" deployable object usable by UIMA users directly, 
after unzipping into the Eclipse plugins directory.

Please cast your vote on releasing:  
org.apache.uima.desceditor.2.1.0.incubating-hotfix-1.zip and
including a reference to the source at: 
https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-ep-configurator-2.1.0-hotfix-1-RC1/uimaj-ep-configurator
Note: I don't plan to zip up this source further into a release
(Continue reading)

Permalink | Reply | 3 comments |
headers
Adam Lally | 2 Apr 23:38
Picon
Gravatar

Re: [VOTE][HOTFIX] [RETRY1] release hot fix Eclipse plugin for UIMA CDE tool

On 4/2/07, Marshall Schor <msa@...> wrote:
> In this retry, the following has changed:
> 1) The artifact (the zip file which is the Eclipse plugin) now includes
> the standard DISCLAIMER, LICENSE, and NOTICES files.
>
> 2) A README-HOTFIX-1 was added and appears in the Zip file when unzipped.
>
> 2) The artifact is signed; the website has the signature keys
>
> 3) The changes are made on top of the SVN 2.1.0 branch.
>
> ==========
>
> The CDE fix in Jira: http://issues.apache.org/jira/browse/UIMA-364 has
> been packaged into a hotfix.
>
> The hotfix consists only of one Eclipse Plugin project; this project
> (uimaj-ep-configurator) was tagged in SVN:
> https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-ep-configurator-2.1.0-hotfix-1-RC1/uimaj-ep-configurator
>
>
> The artifact is located in
> http://people.apache.org/~schor/org.apache.uima.desceditor.2.1.0.incubating-hotfix-1.zip;
> this is a "binary" deployable object usable by UIMA users directly,
> after unzipping into the Eclipse plugins directory.
>
> Please cast your vote on releasing:
> org.apache.uima.desceditor.2.1.0.incubating-hotfix-1.zip and
> including a reference to the source at:
> https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-ep-configurator-2.1.0-hotfix-1-RC1/uimaj-ep-configurator
(Continue reading)

Permalink | Reply | 1 comment |
headers
Michael Baessler | 3 Apr 13:17
Picon

Re: [VOTE][HOTFIX] [RETRY1] release hot fix Eclipse plugin for UIMA CDE tool

Adam Lally wrote:
> On 4/2/07, Marshall Schor <msa@...> wrote:
>> In this retry, the following has changed:
>> 1) The artifact (the zip file which is the Eclipse plugin) now includes
>> the standard DISCLAIMER, LICENSE, and NOTICES files.
>>
>> 2) A README-HOTFIX-1 was added and appears in the Zip file when 
>> unzipped.
>>
>> 2) The artifact is signed; the website has the signature keys
>>
>> 3) The changes are made on top of the SVN 2.1.0 branch.
>>
>> ==========
>>
>> The CDE fix in Jira: http://issues.apache.org/jira/browse/UIMA-364 has
>> been packaged into a hotfix.
>>
>> The hotfix consists only of one Eclipse Plugin project; this project
>> (uimaj-ep-configurator) was tagged in SVN:
>>
https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-ep-configurator-2.1.0-hotfix-1-RC1/uimaj-ep-configurator 
>>
>>
>>
>> The artifact is located in
>>
http://people.apache.org/~schor/org.apache.uima.desceditor.2.1.0.incubating-hotfix-1.zip; 
>>
>> this is a "binary" deployable object usable by UIMA users directly,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thilo Goetz | 3 Apr 16:01
Picon
Picon

Re: [VOTE][HOTFIX] [RETRY1] release hot fix Eclipse plugin for UIMA CDE tool

Marshall Schor wrote:
> In this retry, the following has changed:
> 1) The artifact (the zip file which is the Eclipse plugin) now includes 
> the standard DISCLAIMER, LICENSE, and NOTICES files.
> 
> 2) A README-HOTFIX-1 was added and appears in the Zip file when unzipped.
> 2) The artifact is signed; the website has the signature keys
> 
> 3) The changes are made on top of the SVN 2.1.0 branch.
> 
> ==========
> 
> The CDE fix in Jira: http://issues.apache.org/jira/browse/UIMA-364 has 
> been packaged into a hotfix.
> 
> The hotfix consists only of one Eclipse Plugin project; this project 
> (uimaj-ep-configurator) was tagged in SVN: 
>
https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-ep-configurator-2.1.0-hotfix-1-RC1/uimaj-ep-configurator 
> 
> 
> The artifact is located in 
> http://people.apache.org/~schor/org.apache.uima.desceditor.2.1.0.incubating-hotfix-1.zip; 
> this is a "binary" deployable object usable by UIMA users directly, 
> after unzipping into the Eclipse plugins directory.
> 
> Please cast your vote on releasing:  
> org.apache.uima.desceditor.2.1.0.incubating-hotfix-1.zip and
> including a reference to the source at: 
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thilo Goetz | 3 Apr 16:34
Picon
Picon

2.1.0 branch with hotfix

Marshall, I see that you changed the POM file of uimaj-ep-configurator 
so that the resulting artifact has a new name.  Are we going to leave it 
like this?  What should happen when we build another hotfix, say in 
another component: do we change the name again, or do we leave it like 
that?  I don't really have an opinion at this point, just asking.

--Thilo
Permalink | Reply | 1 comment |
headers
Marshall Schor | 3 Apr 17:05

Re: 2.1.0 branch with hotfix

Thilo Goetz wrote:
> Marshall, I see that you changed the POM file of uimaj-ep-configurator 
> so that the resulting artifact has a new name.  Are we going to leave 
> it like this?  What should happen when we build another hotfix, say in 
> another component: do we change the name again, or do we leave it like 
> that?  I don't really have an opinion at this point, just asking.
>
> --Thilo
>
>

Just to be clear, I only built and packaged for release the one 
"project" - not the whole build.  If another hot-fix is needed in 
another component, we could perhaps build / release just that 
component.  So the fact that the ep-config project has a pom with 
hotfix-1 as part of the name would not be relevant.

I think the feeling in the incubator is that each release should be as 
clear as possible from these naming conventions as to what's in it, and 
in particular, not to put out something under the same name which is 
different.

So as long as the base names for this level is 2.1.0, I think the 
preference would be to keep the hot-fix-1 name. 

Hopefully we won't have any additional work on this level, in any case, 
unless another hot fix comes along....

-M
(Continue reading)

Permalink | Reply | 0 comments |
headers
Adam Lally (JIRA | 5 Apr 15:42
Picon
Favicon

[jira] Created: (UIMA-367) Deadlock can occur in MultiprocessingAnalysisEngine_impl.setResultSpecification

Deadlock can occur in MultiprocessingAnalysisEngine_impl.setResultSpecification
-------------------------------------------------------------------------------

                 Key: UIMA-367
                 URL: https://issues.apache.org/jira/browse/UIMA-367
             Project: UIMA
          Issue Type: Bug
          Components: Core Java Framework
    Affects Versions: 2.1
            Reporter: Adam Lally
         Assigned To: Adam Lally
             Fix For: 2.2

User reports unit test frequently hangs at the following location:
----------------
Thread [Thread-1] (Suspended)
   Object.wait(long) line: not available [native method]
   ResourcePool.getResource(long) line: 166
   AnalysisEnginePool.setResultSpecification(ResultSpecification) line:
155

MultiprocessingAnalysisEngine_impl.setResultSpecification(ResultSpecification)
line: 122

MultiprocessingAnalysisEngine_impl(AnalysisEngineImplBase).process(CAS,
ResultSpecification) line: 200
   MultiprocessingAnalysisEngine_implTest$ProcessThread.run() line: 363
-------------------

I took a look at the code for
(Continue reading)

Permalink | Reply | 2 comments |
headers
Adam Lally (JIRA | 6 Apr 00:13
Picon
Favicon

[jira] Created: (UIMA-368) Allow setting logger config file and other JVM system properties in scripts/bat files

Allow setting logger config file and other JVM system properties in scripts/bat files
-------------------------------------------------------------------------------------

                 Key: UIMA-368
                 URL: https://issues.apache.org/jira/browse/UIMA-368
             Project: UIMA
          Issue Type: Improvement
          Components: Build, Packaging and Test
            Reporter: Adam Lally
         Assigned To: Adam Lally
            Priority: Minor
             Fix For: 2.2

It would be nice if users didn't have to edit our script files to do things like set the logger config file or
set the Java heap size.
I recommend we make the scripts check for a UIMA_LOGGER_CONFIG_FILE env var and use that if specified.
We can also add a catch all UIMA_JVM_OPTS env var for arbitrary other VM args (e.g. -Xmx).

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 3 comments |
headers
Eddie Epstein (JIRA | 6 Apr 16:47
Picon
Favicon

[jira] Created: (UIMA-369) Use same test data as Java project

Use same test data as Java project
----------------------------------

                 Key: UIMA-369
                 URL: https://issues.apache.org/jira/browse/UIMA-369
             Project: UIMA
          Issue Type: Task
          Components: C++ Framework
    Affects Versions: 2.1
            Reporter: Eddie Epstein
         Assigned To: Eddie Epstein
             Fix For: 2.2

The example CAS data and type systems changed in Java ... use the same ones

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 4 comments |

Gmane