Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
Hi guys, we have to report by Wednesday, I can take care of it. We can share in this thread all the stuff we want to report. Cheers. Tommaso 2010/1/1 Marvin mar...@apache.org Dear UIMA Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 January 2010, 2 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/January2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities
[ https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798629#action_12798629 ] Tommaso Teofili commented on UIMA-1717: --- a big +1 for me Use Apache Hudson and Nexus repository facilities - Key: UIMA-1717 URL: https://issues.apache.org/jira/browse/UIMA-1717 Project: UIMA Issue Type: Wish Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Original Estimate: 0h Remaining Estimate: 0h The ASF seems to provide a continuous integration facility (c.f. http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f. http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA would make use of these facilities, allowing for better testing as well as access to fresh snapshot artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on their private Hudson instances. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
Hi, I'm going to add - 2.3.0-RC9 is out for testing - UIMA and Semantic Search presentation at IKS 2nd workshop (see http://wiki.iks-project.eu/index.php/2nd_Workshop) - new incubating project Clerezza planning to integrate with UIMA Tommaso 2010/1/11 Tommaso Teofili tommaso.teof...@gmail.com Hi guys, we have to report by Wednesday, I can take care of it. We can share in this thread all the stuff we want to report. Cheers. Tommaso 2010/1/1 Marvin mar...@apache.org Dear UIMA Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 January 2010, 2 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/January2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
Thanks, Tommaso. Other item to add: New committer voted in (Bhavani Iyer). -Marshall Tommaso Teofili wrote: Hi, I'm going to add - 2.3.0-RC9 is out for testing - UIMA and Semantic Search presentation at IKS 2nd workshop (see http://wiki.iks-project.eu/index.php/2nd_Workshop) - new incubating project Clerezza planning to integrate with UIMA Tommaso 2010/1/11 Tommaso Teofili tommaso.teof...@gmail.com Hi guys, we have to report by Wednesday, I can take care of it. We can share in this thread all the stuff we want to report. Cheers. Tommaso 2010/1/1 Marvin mar...@apache.org Dear UIMA Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 January 2010, 2 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/January2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
Would it be appropriate to say something like getting ready for a graduation vote very soon so the Board knows we're getting there and doesn't worry about us too much? --Thilo On 1/11/2010 10:52, Tommaso Teofili wrote: Hi, I'm going to add - 2.3.0-RC9 is out for testing - UIMA and Semantic Search presentation at IKS 2nd workshop (see http://wiki.iks-project.eu/index.php/2nd_Workshop) - new incubating project Clerezza planning to integrate with UIMA Tommaso 2010/1/11 Tommaso Teofili tommaso.teof...@gmail.com Hi guys, we have to report by Wednesday, I can take care of it. We can share in this thread all the stuff we want to report. Cheers. Tommaso 2010/1/1 Marvin mar...@apache.org Dear UIMA Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 January 2010, 2 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/January2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
2010/1/11 Thilo Goetz twgo...@gmx.de Would it be appropriate to say something like getting ready for a graduation vote very soon so the Board knows we're getting there and doesn't worry about us too much? +1 Tommaso
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
Hi, On Mon, Jan 11, 2010 at 1:36 PM, Thilo Goetz twgo...@gmx.de wrote: Would it be appropriate to say something like getting ready for a graduation vote very soon so the Board knows we're getting there and doesn't worry about us too much? Repeating from the October report: UIMA is ready to graduate, and plans to start the graduation process after the current release activity is finished. :-) As far as I'm concerned (with my mentor hat on) there's no need to wait for the release before graduating, and graduating now would also make the release process easier. BR, Jukka Zitting
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
Jukka Zitting wrote: Hi, On Mon, Jan 11, 2010 at 1:36 PM, Thilo Goetz twgo...@gmx.de wrote: Would it be appropriate to say something like getting ready for a graduation vote very soon so the Board knows we're getting there and doesn't worry about us too much? Repeating from the October report: UIMA is ready to graduate, and plans to start the graduation process after the current release activity is finished. :-) As far as I'm concerned (with my mentor hat on) there's no need to wait for the release before graduating, and graduating now would also make the release process easier. If we vote to graduate, and then want to do a release, I think there's a lot of work to accomplish before the release such as: a) moving the project out of the incubator - including changing the svn, mailing lists, and our web-site b) changing our build process to remove the incubating disclaimer Is this correct? If so, I think it would delay our release, probably. So unless we could release just as we are now, (I'm about to call for the release vote for RC 9) I would favor releasing first, and then trying to graduate. Also, graduation is not a for-sure thing - there might be an extended discussion regarding whether or not we have enough diversity. But I am glad that one of our mentors thinks it's likely to go through, easily ! -Marshall BR, Jukka Zitting
[VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schor has hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall
[jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities
[ https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798706#action_12798706 ] Marshall Schor commented on UIMA-1717: -- +1 to set up CI of some kind. Can someone explain the pros/cons of using the Apache Nexus repository? Use Apache Hudson and Nexus repository facilities - Key: UIMA-1717 URL: https://issues.apache.org/jira/browse/UIMA-1717 Project: UIMA Issue Type: Wish Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Original Estimate: 0h Remaining Estimate: 0h The ASF seems to provide a continuous integration facility (c.f. http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f. http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA would make use of these facilities, allowing for better testing as well as access to fresh snapshot artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on their private Hudson instances. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
Marshall Schor wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schor has hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall +1 -Marshall
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
+1 Tommaso 2010/1/11 Marshall Schor m...@schor.com Marshall Schor wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schorhttp://people.apache.org/%7Eschorhas hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/http://people.apache.org/%7Eschor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall +1 -Marshall
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
+1 Tong On Mon, Jan 11, 2010 at 11:27 AM, Marshall Schor m...@schor.com wrote: Marshall Schor wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schorhttp://people.apache.org/%7Eschorhas hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/http://people.apache.org/%7Eschor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall +1 -Marshall
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
On Mon, Jan 11, 2010 at 11:18 AM, Marshall Schor m...@schor.com wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schor has hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... +1 Adam
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
+1 -- Michael On 1/11/2010 5:18 PM, Marshall Schor wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schor has hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall
[jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities
[ https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798715#action_12798715 ] Tommaso Teofili commented on UIMA-1717: --- in my experience Nexus is good because you can control dependencies (selecting which are got from central and which are hosted), moreover I think is good for the release process (deploy-staging-release i.e.: no more private spaces for hosting RCs required) and finally for the fact that having a Nexus snapshot repo you can let users download for example a 2.3.0-incubating-SNAPSHOT without having to build it from sources. my 2 cents Use Apache Hudson and Nexus repository facilities - Key: UIMA-1717 URL: https://issues.apache.org/jira/browse/UIMA-1717 Project: UIMA Issue Type: Wish Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Original Estimate: 0h Remaining Estimate: 0h The ASF seems to provide a continuous integration facility (c.f. http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f. http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA would make use of these facilities, allowing for better testing as well as access to fresh snapshot artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on their private Hudson instances. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities
[ https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798717#action_12798717 ] Richard Eckart de Castilho commented on UIMA-1717: -- Hudson can directly deploy snapshots to Nexus when the build is successful (compiles, all tests are fine), so Nexus can always have the latest snapshots without any manual effort. I haven't used the staging capabilities yet - afaik those are only available on the commercial Nexus. I don't know if Apache has access to the commercial features. Use Apache Hudson and Nexus repository facilities - Key: UIMA-1717 URL: https://issues.apache.org/jira/browse/UIMA-1717 Project: UIMA Issue Type: Wish Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Original Estimate: 0h Remaining Estimate: 0h The ASF seems to provide a continuous integration facility (c.f. http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f. http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA would make use of these facilities, allowing for better testing as well as access to fresh snapshot artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on their private Hudson instances. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
+1 On Mon, Jan 11, 2010 at 11:33 AM, Michael Baessler m...@michael-baessler.dewrote: +1 -- Michael On 1/11/2010 5:18 PM, Marshall Schor wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schor has hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall
[jira] Commented: (UIMA-1722) CDE is very slow to open an aggregate containing a remote UIMA-AS component
[ https://issues.apache.org/jira/browse/UIMA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798728#action_12798728 ] Marshall Schor commented on UIMA-1722: -- I've prototyped a fix for this, and will attend to it after the 2.3.0 release is done. There are 2 parts to the fix. # change the CDE so that when it creates Resource Managers and sets their class loaders, that it reuses the exact same class loader as before (unless, of course, there was some change in the user's build path for the project). This will prevent multiple loading of classes (existing ones will be re-used) due to switching classloaders. \\ \\ Use-case reminder: Custom Resource Specifiers, which are specifying the inclusion of uima-as because they're being used for uima-as remote services. \\ \\ The class loader should be cached using a Java soft reference, so it can eventually be cleaned up as space is needed (if it is not being used). \\ \\ # change the CasCreationUtils utility method which gets the metadata for a descriptor or collection of these (getMetaDataList) to cache its results and re-use that if: ** the arguments are such that the same result would be returned (except for a remote AE becoming available or not) ** if the previous try at getting metadata partially failed due to some remote not responding, use the cache only for a short time (say 30 seconds); after that, try again to see if the remote has become available CDE is very slow to open an aggregate containing a remote UIMA-AS component --- Key: UIMA-1722 URL: https://issues.apache.org/jira/browse/UIMA-1722 Project: UIMA Issue Type: Improvement Components: Async Scaleout, Eclipse plugins Affects Versions: 2.3 Reporter: Adam Lally I have an aggregate containing 3 remote UIMA-AS components. It takes about a minute (maybe more) to open this in the CDE, which makes it very cumbersome to use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities
[ https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798729#action_12798729 ] Jukka Zitting commented on UIMA-1717: - I don't know if Apache has access to the commercial features. We have. Use Apache Hudson and Nexus repository facilities - Key: UIMA-1717 URL: https://issues.apache.org/jira/browse/UIMA-1717 Project: UIMA Issue Type: Wish Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Original Estimate: 0h Remaining Estimate: 0h The ASF seems to provide a continuous integration facility (c.f. http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f. http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA would make use of these facilities, allowing for better testing as well as access to fresh snapshot artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on their private Hudson instances. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
+1 Jörn Marshall Schor wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schor has hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall
[jira] Commented: (UIMA-1714) Message Bundles not visible when loaded under a UIMA Resource Manager class loader
[ https://issues.apache.org/jira/browse/UIMA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798772#action_12798772 ] Marshall Schor commented on UIMA-1714: -- After some more investigation, I think a better fix is to change the way the resource bundles are looked up for error messages. Right now, the logic is spread across multiple classes. For instance, for the JSR47 logger, part is in JSR47Logger_impl, in the method getExtensionClassLoader which returns the ResourceManager's extension class loader or null if there is none. Then, the I18nUtil.localizeMessage method has logic to use the passed-in extensionClassLoader (which might be null) and if it is null, it uses the class loader that loaded the I18nUtil class or the system classloader if it gets null for I18nUtil.class.getClassLoader() call. I think that a better strategy would be to, in essence, try a series of class loaders, until one succeeds, or all of them fail. The order would go something like: # ResourceManager's extension class loader # the thread's contextClassLoader # the class loader that loaded the I18nUtil class # the class loader that loaded the caller of the localizeMessage method # the class loader that loaded the 2nd previous caller # the class loader that loaded the 3rd previous caller etc. Of course, you would only try a class loader if it was different from one already tried. This approach allows frameworks to find and load resources they cannot see with their own class loaders, but which belong with class-loader-isolated components. Here's one article that tries to explain why this is a good idea: http://www.javaworld.com/javaworld/javaqa/2003-06/01-qa-0606-load.html Another similar approach is used by the Eclipse plugin mechanism when it is trying to find classes or resources to load that might belong to user code - sets up a ContextClassLoader to do the work of running up the chain of callers, as above, trying them to see if they can load the thing requested. See http://wiki.eclipse.org/Context_Class_Loader_Enhancements. Eclipse defines a new class loader which implements this kind of algorithm - see Java has a method which returns the set of classes on the call stack, in order: aSecurityManagerInstance.getClassContext(). Message Bundles not visible when loaded under a UIMA Resource Manager class loader -- Key: UIMA-1714 URL: https://issues.apache.org/jira/browse/UIMA-1714 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.3 Reporter: Marshall Schor UIMA-AS has message bundles. When uima-as classes are loaded under a resource manager class loader, the message bundle is not visible when logging occurs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
+1 On Mon, Jan 11, 2010 at 11:18 AM, Marshall Schor m...@schor.com wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schor has hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall
