Re: [VOTE] Approve release Apache UIMA 2.2.2-incubating
Hi Niall, Niall Pemberton wrote: Firstly, I'm +1 on this release. I have a few minor comments/suggestions which you may want to consider for the next release (or not!) 1) Theres a parent pom for apache which if you make the parent of the uimaj pom means you don't have to duplicate the license and organization details in your poms: http://repo1.maven.org/maven2/org/apache/apache/ sounds good, we'll look into it. 2) The source distro unzips to directory uimaj-2.2.2-incubating and the binary distro to apache-uima - which is inconsistent. I don't recall if there was a reason for this, but I agree, seems odd. We'll follow up on uima-dev. 3) IMO its better if the jars include the version number - which they do for the maven repo, but not the ones in the binary distro I personally agree with you, but we had a long discussion about this and the no version numbers in jar names faction carried the day. I believe the main reason is that it makes upgrading to a new version easier, or switching between versions for testing purposes. --Thilo Niall
Re: Cas Editor build script
Jörn Kottmann wrote: On Apr 23, 2008, at 9:34 AM, Michael Baessler wrote: Jörn Kottmann wrote: On Apr 8, 2008, at 10:00 AM, Michael Baessler wrote: Jörn Kottmann wrote: - The source Package cannot be compiled since the UIMA core plugins cannot be copied (not available in the source package). I'm currently not sure how to solve this issue. The current source package cannot be reproduced since the dependencies can change. Does anyone has another idea than copying the used jars to the CasEditor project? How does it works in the other sandbox components ? They need the doc packages to be build, are they included in the source build ? Yes, they are included and specially tagged. Ok, then I have todo this too. It would be possible to get the runtime plugin in either from the core plugin project or make it mandatory plugin for the eclipse installation which is used to build the cas editor. The build script could check if the user did provide the correct version of the runtime plugin. To make the build reproducible we also have to enforce that the user is using the same eclipse version as we used for the release build. Should we checkin this too ? Maybe this is a good workaround. Ok, I will do it this way for now. Please give me more details. Maybe thats a sign that the build on your machine is still failing, could you start the cas editor ? I can't start the CasEditor, still some ClassNotFound exceptions. Seems that the CasEditor build doesn't work properly for me. I uploaded the ant build output to my home directory. I think there is still a problem with your eclipse installation. Can you please download eclipse 3.3.2, then install the EMF stuff and the delta package. This should work fine. I am sorry for this one. Sorry I'm still not able to build the CasEditor release. I used the eclipse 3.3.2 version with EMF 2.3.2, delta package 3.3.2 and the UIMA plulgins version 2.2.2. I got no build errors, but the CasEditor plugin jar is not created. I also still see the source code in the binary package. Not sure what is wrong on my machine. Maybe someone else can try to build and check if it works. I tested this with mac os and ubuntu linux. I guess you use windows. I will test it too on windows tonight or tomorrow night. Maybe there lies the problem. Yes, I did my tests on windows. -- Michael
[jira] Assigned: (UIMA-880) Make PEAR installation path configurable in web.xml
[ https://issues.apache.org/jira/browse/UIMA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Baessler reassigned UIMA-880: - Assignee: Michael Baessler (was: Thilo Goetz) Make PEAR installation path configurable in web.xml --- Key: UIMA-880 URL: https://issues.apache.org/jira/browse/UIMA-880 Project: UIMA Issue Type: New Feature Components: Sandbox-SimpleServer Reporter: Thilo Goetz Assignee: Michael Baessler -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-880) Make PEAR installation path configurable in web.xml
[ https://issues.apache.org/jira/browse/UIMA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Baessler resolved UIMA-880. --- Resolution: Fixed Fix Version/s: 2.3S Assignee: Thilo Goetz (was: Michael Baessler) implemented and tested Make PEAR installation path configurable in web.xml --- Key: UIMA-880 URL: https://issues.apache.org/jira/browse/UIMA-880 Project: UIMA Issue Type: New Feature Components: Sandbox-SimpleServer Reporter: Thilo Goetz Assignee: Thilo Goetz Fix For: 2.3S -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-880) Make PEAR installation path configurable in web.xml
[ https://issues.apache.org/jira/browse/UIMA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Baessler reopened UIMA-880: --- Assignee: Michael Baessler (was: Thilo Goetz) Try to implement additionally the servlet spec, using servlet context temp directory. Make PEAR installation path configurable in web.xml --- Key: UIMA-880 URL: https://issues.apache.org/jira/browse/UIMA-880 Project: UIMA Issue Type: New Feature Components: Sandbox-SimpleServer Reporter: Thilo Goetz Assignee: Michael Baessler Fix For: 2.3S -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Cas Editor build script
Michael Baessler wrote: Jörn Kottmann wrote: On Apr 23, 2008, at 9:34 AM, Michael Baessler wrote: [...] Sorry I'm still not able to build the CasEditor release. I used the eclipse 3.3.2 version with EMF 2.3.2, delta package 3.3.2 and the UIMA plulgins version 2.2.2. I got no build errors, but the CasEditor plugin jar is not created. I also still see the source code in the binary package. Not sure what is wrong on my machine. Maybe someone else can try to build and check if it works. I tried this, too, and get the same results as Michael. Also windows. I tested this with mac os and ubuntu linux. I guess you use windows. I will test it too on windows tonight or tomorrow night. Maybe there lies the problem. Yes, I did my tests on windows. -- Michael
Re: [VOTE] Approve release Apache UIMA 2.2.2-incubating
Thilo Goetz wrote: snip 3) IMO its better if the jars include the version number - which they do for the maven repo, but not the ones in the binary distro I personally agree with you, but we had a long discussion about this and the no version numbers in jar names faction carried the day. I believe the main reason is that it makes upgrading to a new version easier, or switching between versions for testing purposes. An other reason is due to not implementing yet Jira http://issues.apache.org/jira/browse/UIMA-857 -Marshall
Re: [VOTE] Approve release Apache UIMA 2.2.2-incubating
Marshall Schor wrote: Thilo Goetz wrote: snip 3) IMO its better if the jars include the version number - which they do for the maven repo, but not the ones in the binary distro I personally agree with you, but we had a long discussion about this and the no version numbers in jar names faction carried the day. I believe the main reason is that it makes upgrading to a new version easier, or switching between versions for testing purposes. An other reason is due to not implementing yet Jira http://issues.apache.org/jira/browse/UIMA-857 -Marshall I don't understand the stripping part. We don't have version info in our jar file names, so where are we stripping anything? --Thilo
[jira] Closed: (UIMA-880) Make PEAR installation path configurable in web.xml
[ https://issues.apache.org/jira/browse/UIMA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Baessler closed UIMA-880. - Resolution: Fixed Make PEAR installation path configurable in web.xml --- Key: UIMA-880 URL: https://issues.apache.org/jira/browse/UIMA-880 Project: UIMA Issue Type: New Feature Components: Sandbox-SimpleServer Reporter: Thilo Goetz Assignee: Michael Baessler Fix For: 2.3S -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1010) uima-as release process not capturing a known level of core uima
uima-as release process not capturing a known level of core uima Key: UIMA-1010 URL: https://issues.apache.org/jira/browse/UIMA-1010 Project: UIMA Issue Type: Improvement Components: Async Scaleout, Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.2.2AS The current uima-as release process does not tag a level of the core uima used to supply its lib/jars; it uses whatever is in the builder's local maven repository, which may be in some unknown state. Attaching the right source to these jars is difficult, if not impossible (impossible if there were local uncommitted changes in the builder's system, that were used to build the local repo, but never checked in.) The release process needs to tag the version of core uima that uima-as is based on, and extract that and build it before building uima-as. The source distribution for uima-as should include a pointer to the tag in svn (the source distr for core uima is large mainly due to documentation, doc tooling, and tests). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Approve release Apache UIMA 2.2.2-incubating
On Wed, Apr 23, 2008 at 7:24 AM, Marshall Schor [EMAIL PROTECTED] wrote: Thilo Goetz wrote: 3) IMO its better if the jars include the version number - which they do for the maven repo, but not the ones in the binary distro I personally agree with you, but we had a long discussion about this and the no version numbers in jar names faction carried the day. I believe the main reason is that it makes upgrading to a new version easier, or switching between versions for testing purposes. We actually have a Jira issue that may address this, for the next release: http://issues.apache.org/jira/browse/UIMA-857 Among the UIMA committers, I'm the main proponent of the no version numbers in jar names. Jar file names that change in each version have always driven me crazy because they force users to update their classpaths when they upgrade their UIMA version. A lot of tools just don't handle this well - Eclipse is one example, AFAIK it doesn't give you any way to use wildcards in classpath so as to pick up any version. I don't see UIMA-857 as a solution, because UIMA is an embeddable component and people want to take our jar files and add them to their classpaths using typical Java means. I personally wouldn't be happy relying on some special UIMA mechanism for finding its jar files. -Adam
Incubation administrivia
Reminder to all committers on the UIMA project: You are reponsible for ensuring that you have authorisation to work on the code from your employer or anyone else who might have rights to or interests in your contributions. If this requires a CCLA (corporate contribution licensing agreement, see http://www.apache.org/licenses/#clas), then you are responsible for ensuring that you are listed on it. We now return you to your regular activities, already in progress. :-) -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp!
Re: [VOTE] Approve release Apache UIMA 2.2.2-incubating
Adam Lally wrote: On Wed, Apr 23, 2008 at 7:24 AM, Marshall Schor [EMAIL PROTECTED] wrote: Thilo Goetz wrote: 3) IMO its better if the jars include the version number - which they do for the maven repo, but not the ones in the binary distro I personally agree with you, but we had a long discussion about this and the no version numbers in jar names faction carried the day. I believe the main reason is that it makes upgrading to a new version easier, or switching between versions for testing purposes. We actually have a Jira issue that may address this, for the next release: http://issues.apache.org/jira/browse/UIMA-857 Among the UIMA committers, I'm the main proponent of the no version numbers in jar names. Jar file names that change in each version have always driven me crazy because they force users to update their classpaths when they upgrade their UIMA version. A lot of tools just don't handle this well - Eclipse is one example, AFAIK it doesn't give you any way to use wildcards in classpath so as to pick up any version. I don't see UIMA-857 as a solution, because UIMA is an embeddable component and people want to take our jar files and add them to their classpaths using typical Java means. I personally wouldn't be happy relying on some special UIMA mechanism for finding its jar files. Me neither. If it's just for the command line tooling, that's fine with me (I never use it anyway ;-). Even then, it's just one more thing that can go wrong. I don't want version numbers in jar file names that bad :-) --Thilo -Adam
[jira] Commented: (UIMA-1010) uima-as release process not capturing a known level of core uima
[ https://issues.apache.org/jira/browse/UIMA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591648#action_12591648 ] Marshall Schor commented on UIMA-1010: -- If the version of core uima that this uima-as release is based on is officially released, then this tagging is not needed, I think. For instance, consider the inclusion in uima-as of a particular version of the Spring framework. We do not tag the source for the spring frame work; users wanting that can get it from the Spring website for that officially released version. This need to tag things only occurs, I think, when the uima-as build is building upon a not-yet-officially-released version of core uima. Note that the assembly for uima-as binary specifies the version of uima being built upon, in the POM for the uima-as-distr project. uima-as release process not capturing a known level of core uima Key: UIMA-1010 URL: https://issues.apache.org/jira/browse/UIMA-1010 Project: UIMA Issue Type: Improvement Components: Async Scaleout, Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.2.2AS The current uima-as release process does not tag a level of the core uima used to supply its lib/jars; it uses whatever is in the builder's local maven repository, which may be in some unknown state. Attaching the right source to these jars is difficult, if not impossible (impossible if there were local uncommitted changes in the builder's system, that were used to build the local repo, but never checked in.) The release process needs to tag the version of core uima that uima-as is based on, and extract that and build it before building uima-as. The source distribution for uima-as should include a pointer to the tag in svn (the source distr for core uima is large mainly due to documentation, doc tooling, and tests). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1010) uima-as release process not capturing a known level of core uima
[ https://issues.apache.org/jira/browse/UIMA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591652#action_12591652 ] Marshall Schor commented on UIMA-1010: -- Eddie points out that the build process can be fixed more simply, by instructing the builder to pull down the tagged version of core uima and build it, and then do the same for uima-as. We probably need to document in the Release Notes the tag of the core uima used for the build, if that was what is being used (as opposed to an official release). Based on that, I do not think it is necessary to tag the core uima source for uima-as. uima-as release process not capturing a known level of core uima Key: UIMA-1010 URL: https://issues.apache.org/jira/browse/UIMA-1010 Project: UIMA Issue Type: Improvement Components: Async Scaleout, Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.2.2AS The current uima-as release process does not tag a level of the core uima used to supply its lib/jars; it uses whatever is in the builder's local maven repository, which may be in some unknown state. Attaching the right source to these jars is difficult, if not impossible (impossible if there were local uncommitted changes in the builder's system, that were used to build the local repo, but never checked in.) The release process needs to tag the version of core uima that uima-as is based on, and extract that and build it before building uima-as. The source distribution for uima-as should include a pointer to the tag in svn (the source distr for core uima is large mainly due to documentation, doc tooling, and tests). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: some redo of the Website to support additional things being released
Overall, sounds good. Note that there is a sandbox page already. Your sandbox links should go there, I think. --Thilo Marshall Schor wrote: Because we're releasing lots of new stuff, I think our webpages need some updating. Here's a proposal: 1) home page: add short paragraphs for uima-as, annotators, tools (CasEditor), simple-server - the set of things in the sandbox we're releasing this time around (this might be done over time, as things get released) To keep the initial view small, add a summary paragraph / list to show as the first thing at the top, with links to these paragraphs. 2) documentation page: make a table to concisely show docs - rows would be for different things being released, columns would be for things like pdf, html, apidocs, etc. 3) download page: make a table to concisely show links to download - same rows as above, but columns would be for things like current vs link to archives, binary, source, link to eclipse update site, gpg/md5/sha1 verifications (maybe, not sure...) 4) updates to the Project Team page - list more people, especially the contributors of annotators, and uima-as components (with their permission). Names only, no links/emails (for respecting privacy) unless specifically wanted. (Thilo links his to home page on Apache). Other opinions? -Marshall
Re: some redo of the Website to support additional things being released
Marshall Schor wrote: Because we're releasing lots of new stuff, I think our webpages need some updating. Here's a proposal: 1) home page: add short paragraphs for uima-as, annotators, tools (CasEditor), simple-server - the set of things in the sandbox we're releasing this time around (this might be done over time, as things get released) To keep the initial view small, add a summary paragraph / list to show as the first thing at the top, with links to these paragraphs. 2) documentation page: make a table to concisely show docs - rows would be for different things being released, columns would be for things like pdf, html, apidocs, etc. 3) download page: make a table to concisely show links to download - same rows as above, but columns would be for things like current vs link to archives, binary, source, link to eclipse update site, gpg/md5/sha1 verifications (maybe, not sure...) 4) updates to the Project Team page - list more people, especially the contributors of annotators, and uima-as components (with their permission). Names only, no links/emails (for respecting privacy) unless specifically wanted. (Thilo links his to home page on Apache). Another thing to add: the how to do a release for the various sub-projects. For now, I suggest just adding this to the main how-to-do-a-release. For instance, to release the uima-as requires a build process which includes running the tag script and then extracting/building the base uima before doing the uima-as build (because it depends on the local repository having the proper build of the base). -Marshall
[jira] Created: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[ https://issues.apache.org/jira/browse/UIMA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1011: --- Attachment: UIMA-1011-DDE-04-23-2008-Patch-2-of-2.txt UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt, UIMA-1011-DDE-04-23-2008-Patch-2-of-2.txt Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[ https://issues.apache.org/jira/browse/UIMA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin reassigned UIMA-1011: -- Assignee: Marshall Schor (was: Tong Fin) Need help from Marshall to verify and apply the patches. [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt, UIMA-1011-DDE-04-23-2008-Patch-2-of-2.txt Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[ https://issues.apache.org/jira/browse/UIMA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1011: --- Attachment: (was: UIMA-1011-DDE-04-23-2008-Patch-2-of-2.txt) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[ https://issues.apache.org/jira/browse/UIMA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1011: --- Attachment: UIMA-1011-DDE-04-23-2008-Patch-2-of-2-VERSION2.txt Re-create the patch to include the border problem in Linux for the Env Variable table [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt, UIMA-1011-DDE-04-23-2008-Patch-2-of-2-VERSION2.txt Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1010) uima-as release process not capturing a known level of core uima
[ https://issues.apache.org/jira/browse/UIMA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1010. Resolution: Fixed uima-as release process not capturing a known level of core uima Key: UIMA-1010 URL: https://issues.apache.org/jira/browse/UIMA-1010 Project: UIMA Issue Type: Improvement Components: Async Scaleout, Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.2.2AS The current uima-as release process does not tag a level of the core uima used to supply its lib/jars; it uses whatever is in the builder's local maven repository, which may be in some unknown state. Attaching the right source to these jars is difficult, if not impossible (impossible if there were local uncommitted changes in the builder's system, that were used to build the local repo, but never checked in.) The release process needs to tag the version of core uima that uima-as is based on, and extract that and build it before building uima-as. The source distribution for uima-as should include a pointer to the tag in svn (the source distr for core uima is large mainly due to documentation, doc tooling, and tests). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
uima-as release candidate 02 on people.a.o
in schor/uima-release-candidates/uima-as/02 This should be identical to the 01 release, except that the base uima build for 02 is exactly the uima-2.2.2-05 release candidate ( see https://issues.apache.org/jira/browse/UIMA-1010). -Marshall
