headers
Michael Baessler | 2 Jan 08:16
Picon

Re: Where to put large generated things for our website to access

Robert Burrell Donkin wrote:
> subversion really is the way to go for release documentation
>   
OK, so as far as I understand we go with the documentation the same way 
as with the previous Apache UIMA releases. We check in the documentation
to SVN and provide a download similar to release 2.2.0-incubating:

http://incubator.apache.org/uima/downloads/releaseDocs/2.2.0-incubating/docs/html/index.html

The JavaDocs will also go to SVN in both versions, HTML and zip.

I can do the necessary changes, if all agree on that.

-- Michael
Permalink | Reply | 6 comments |
headers
Michael Baessler | 2 Jan 08:24
Picon

Re: [Fwd: Re: [schor] incubator/uima/eclipseUpdateSite/]

I think we should add some information to the UIMA website about the new 
UIMA eclipse update site and mention it in the "News" section.

I give it a try and all works fine for me.

-- Michael

Marshall Schor wrote:
> -------- Original Message --------
> Subject: 	Re: [schor] incubator/uima/eclipseUpdateSite/
> Date: 	Sat, 29 Dec 2007 07:35:24 +0100 (CET)
> From: 	Henk P. Penning <henkp@...>
> To: 	Marshall Schor <msa@...>
> References: 	<20071224113235.31563.qmail@...>
> <4775E57F.6020800@...>
>
>
>
> On Sat, 29 Dec 2007, Marshall Schor wrote:
>
>   
>> Date: Sat, 29 Dec 2007 01:13:19 -0500
>> From: Marshall Schor <msa@...>
>> To: Henk Penning <henkp@...>, uima-dev <uima-dev@...>
>> Subject: Re: [schor] incubator/uima/eclipseUpdateSite/
>>     
>
>
>   
>> This has now been done - the signature and hash sums (MD5 and SHA1) are
(Continue reading)

Permalink | Reply | 501 comments |
headers
Michael Baessler (JIRA | 2 Jan 10:01
Picon
Favicon

[jira] Commented: (UIMA-681) change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT


    [
https://issues.apache.org/jira/browse/UIMA-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555274#action_12555274
] 

Michael Baessler commented on UIMA-681:
---------------------------------------

I tried to work with the Maven properties without success. As you know we have a Project structure with one
parent POM and many child POMs. 
In defined some properties in the parent POM but I was not able to access them in the child POMs.

The other issue is that in each child POM I have to specify settings of the parent POM and also the version of
the parent POM :-( . So this can't work with inherited variables. 

So what else can we do:
If we remove the <version> tags from the child POM it inherits automatically the version from the parent
POM. So what does this mean. 
- We don't have to change the version number for the child POMs
- We still have to change the parent POM settings (version number) for each child POM
- All child POMs have dependencies to other UIMA artifacts with the current artifact version. This can be
replaced with ${project.version}.
This approach works for all child POMs except the plugin projects since these have a different version
style. Some of the referred UIMA artifacts can be handled with 
${parent.project.version} but the POMs still have an own version that must be updated manually.

Another approach would be to try to load a Maven property from an external source to all POMs. In that case we
have external dependencies for the build. 
I haven't tried that way, so I'm also not sure if it works.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Baessler (JIRA | 2 Jan 10:43
Picon
Favicon

[jira] Closed: (UIMA-682) update Sandbox components to work on the new uimaj-2.2.1-incubating release


     [
https://issues.apache.org/jira/browse/UIMA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Baessler closed UIMA-682.
---------------------------------

    Resolution: Fixed

changed all Sandbox components to use the latest UIMA version (2.2.1-incubating) from the Maven
incubator repository

> update Sandbox components to work on the new uimaj-2.2.1-incubating release
> ---------------------------------------------------------------------------
>
>                 Key: UIMA-682
>                 URL: https://issues.apache.org/jira/browse/UIMA-682
>             Project: UIMA
>          Issue Type: Task
>          Components: Sandbox
>            Reporter: Michael Baessler
>

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 0 comments |
headers
Michael Baessler (JIRA | 2 Jan 10:48
Picon
Favicon

[jira] Created: (UIMA-684) update website with "How to do a release"

update website with "How to do a release" 
------------------------------------------

                 Key: UIMA-684
                 URL: https://issues.apache.org/jira/browse/UIMA-684
             Project: UIMA
          Issue Type: Improvement
          Components: Website
            Reporter: Michael Baessler
            Assignee: Michael Baessler

--

-- 
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
Thilo Goetz (JIRA | 2 Jan 12:02
Picon
Favicon

[jira] Created: (UIMA-685) Create documentation for SimpleServer

Create documentation for SimpleServer
-------------------------------------

                 Key: UIMA-685
                 URL: https://issues.apache.org/jira/browse/UIMA-685
             Project: UIMA
          Issue Type: New Feature
          Components: Sandbox-SimpleServer
    Affects Versions: 2.3
            Reporter: Thilo Goetz
            Assignee: Thilo Goetz
             Fix For: 2.3

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 5 comments |
headers
Michael Baessler | 2 Jan 12:04
Picon

Re: Updating our web-site with info in dev section on how-to-do-a-release

Marshall Schor wrote:
> It would be great if the past and present release managers could add a
> page to our web-site under the developers area, describing how to do a
> release.
>
> We have some parts, already - like how to sign a release.
>
> What's missing are all the other steps a release manager does, such as
> 1) making the release notes from the Jira reporting
> 2) how to find the current level of RAT, how to run RAT, what to do with
> the reports (how to annotate them), etc.
>   -- by the way, can RAT be run in a mode that only shows differences
> with the previous release?  This might be helpful to anyone reviewing
> the release...
>
> 3) how to do the vote
>
> 4) After the vote passes, what to do, including: base release, docs
> update, archiving older ones, where the release "goes", what to do with
> the Eclipse update site, etc.
>
> I'm sure there are parts I've omitted - so I would suggest that we get a
> web page started which we can incrementally update and improve.
>
> Do others agree?
>
> -Marshall
>
>
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Marshall Schor (JIRA | 2 Jan 14:31
Picon
Favicon

[jira] Created: (UIMA-686) Collection Processing shutdown tests fail intermittantly - hanging

Collection Processing shutdown tests fail intermittantly - hanging
------------------------------------------------------------------

                 Key: UIMA-686
                 URL: https://issues.apache.org/jira/browse/UIMA-686
             Project: UIMA
          Issue Type: Bug
          Components: Collection Processing
    Affects Versions: 2.2.1
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor

Three testers running the CPM tests on multi-core linux platforms or using special concurrancy testing
tools have reported occasional hangs while running the CPM shutdown tests.

--

-- 
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
Marshall Schor | 2 Jan 14:31

Re: Where to put large generated things for our website to access

Michael Baessler wrote:
> Robert Burrell Donkin wrote:
>> subversion really is the way to go for release documentation
>>   
> OK, so as far as I understand we go with the documentation the same
> way as with the previous Apache UIMA releases. We check in the
> documentation
> to SVN and provide a download similar to release 2.2.0-incubating:
>   
> http://incubator.apache.org/uima/downloads/releaseDocs/2.2.0-incubating/docs/html/index.html
>
>
> The JavaDocs will also go to SVN in both versions, HTML and zip.
>
> I can do the necessary changes, if all agree on that.
>
> -- Michael
>
>
>
+1.

Also - remove the docs from /dist/incubator/uima

-Marshall
Permalink | Reply | 5 comments |
headers
Marshall Schor (JIRA | 2 Jan 14:40
Picon
Favicon

[jira] Updated: (UIMA-686) Deadlocks in CPM tests:CPM shutdown tests failing (hanging) intermittantly


     [
https://issues.apache.org/jira/browse/UIMA-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor updated UIMA-686:
--------------------------------

    Description: 
Three testers running the CPM tests on multi-core linux platforms or using special concurrancy testing
tools have reported occasional hangs while running the CPM shutdown tests.

Mail thread: http://www.mail-archive.com/uima-dev-d1GL8uUpDdXTxqt0kkDzDmD2FQJk+8+b <at> public.gmane.org/msg04530.html

  was:Three testers running the CPM tests on multi-core linux platforms or using special concurrancy
testing tools have reported occasional hangs while running the CPM shutdown tests.

        Summary: Deadlocks in CPM tests:CPM shutdown tests failing (hanging) intermittantly  (was: Collection
Processing shutdown tests fail intermittantly - hanging)

> Deadlocks in CPM tests:CPM shutdown tests failing (hanging) intermittantly
> --------------------------------------------------------------------------
>
>                 Key: UIMA-686
>                 URL: https://issues.apache.org/jira/browse/UIMA-686
>             Project: UIMA
>          Issue Type: Bug
>          Components: Collection Processing
>    Affects Versions: 2.2.1
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
(Continue reading)

Permalink | Reply | 0 comments |

Gmane