[jira] Created: (SM-435) VFS ftp writer makes a connection in the init() method, but this causes the component to stay connected throughout the lifetime of the ESB (instead of reconnecting each time)
VFS ftp writer makes a connection in the init() method, but this causes the component to stay connected throughout the lifetime of the ESB (instead of reconnecting each time) -- Key: SM-435 URL: https://issues.apache.org/activemq/browse/SM-435 Project: ServiceMix Type: Bug Components: servicemix-components Versions: 3.0 Reporter: Jeff Puro -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2045) Plugin prerequisites: for DB pools, support DB type/version and table validation
Plugin prerequisites: for DB pools, support DB type/version and table validation Key: GERONIMO-2045 URL: http://issues.apache.org/jira/browse/GERONIMO-2045 Project: Geronimo Type: Improvement Security: public (Regular issues) Components: Plugins Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.2 More robust database pool prerequisites for plugins: - check that one of a specific set of RDBMS name/version combinations is set for a connection pool prerequisite - check the schema somehow -- e.g. that some table exists, or some query returns an expected value -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-81) Not able to build server from trunk ,
Not able to build server from trunk , -- Key: GERONIMODEVTOOLS-81 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-81 Project: Geronimo-Devtools Type: Bug Versions: 1.0.0 Environment: Win2k , java1.4_08, maven1.02, svn 1.3 client Reporter: Mansoor 1. Checked out the lastest code from trunk using below command : svn co http://svn.apache.org/repos/asf/geronimo/trunk geronimo 2.Tried building the server .. Results : I cann't build the server due to lot of dependencies not getting downloaded. ERRORS : --- Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-20030902.160215.jar]: java.io.IOException: Unknown error downl oading; status code was: 302 150K downloaded Attempting to download commons-jelly-tags-jsl-20030211.143151.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-tags-jsl-20030211.143151.jar]: java.io.IOException: Unknown er ror downloading; status code was: 302 14K downloaded Attempting to download commons-jelly-tags-log-20030211.142821.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-tags-log-20030211.142821.jar]: java.io.IOException: Unknown er ror downloading; status code was: 302 8K downloaded Attempting to download commons-jelly-tags-velocity-20030303.205659.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-tags-velocity-20030303.205659.jar]: java.io.IOException: Unkno wn error downloading; status code was: 302 7K downloaded Attempting to download commons-jelly-tags-xml-20040613.030723.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-tags-xml-20040613.030723.jar]: java.io.IOException: Unknown er ror downloading; status code was: 302 33K downloaded Attempting to download commons-logging-1.0.3.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-logging /jars/commons-logging-1.0.3.jar]: java.io.IOException: Unknown error downloading ; status code was: 302 30K downloaded Attempting to download velocity-1.4-dev.jar. Error retrieving artifact from [http://cvs.apache.org/repository/velocity/jars/v elocity-1.4-dev.jar]: java.io.IOException: Unknown error downloading; status cod e was: 302 505K downloaded Attempting to download velocity-dvsl-0.45.jar. Error retrieving artifact from [http://cvs.apache.org/repository/velocity-dvsl/j ars/velocity-dvsl-0.45.jar]: java.io.IOException: Unknown error downloading; sta tus code was: 302 25K downloaded Attempting to download xml-apis-1.0.b2.jar. Error retrieving artifact from [http://cvs.apache.org/repository/xml-apis/jars/x ml-apis-1.0.b2.jar]: java.io.IOException: Unknown error downloading; status code was: 302 106K downloaded Attempting to download isorelax-20030108.jar. Error retrieving artifact from [http://cvs.apache.org/repository/isorelax/jars/i sorelax-20030108.jar]: java.io.IOException: Unknown error downloading; status co de was: 302 188K downloaded Attempting to download jing-20030619.jar. Error retrieving artifact from [http://cvs.apache.org/repository/thaiopensource/ jars/jing-20030619.jar]: java.io.IOException: Unknown error downloading; status code was: 302 475K downloaded Attempting to download xerces-2.4.0.jar. Error retrieving artifact from [http://cvs.apache.org/repository/xerces/jars/xer ces-2.4.0.jar]: java.io.IOException: Unknown error downloading; status code was: 302 874K downloaded Attempting to download commons-io-20030203.000550.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-io/jars /commons-io-20030203.000550.jar]: java.io.IOException: Unknown error downloading ; status code was: 302 59K downloaded Attempting to download commons-net-1.1.0.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-net/jar s/commons-net-1.1.0.jar]: java.io.IOException: Unknown error downloading; status code was: 302 139K downloaded Attempting to download commons-httpclient-2.0.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-httpcli ent/jars/commons-httpclient-2.0.jar]: java.io.IOException: Unknown error downloa ding; status code was: 302 217K downloaded Attempting to download commons-lang-2.0.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-lang/ja rs/commons-lang-2.0.jar]: java.io.IOException: Unknown error downloading; status code was: 302 165K downloaded Attempting to download jsch-0.1.5.jar. Error retrieving artifact from [http://cvs.apache.org/repository/jsch/jars/jsch- 0.1.5.jar]: java.io.IOException: Unknown error downloading; status code was: 302 79K downloaded build:start: new: new0: m:tranql: new00: m:tranql2: new1: m:geronimo:core: build:start: multiproject:install-callback: [echo] Running
[jira] Assigned: (GERONIMO-1759) getConsoleFrameworkServletPath broken
[ http://issues.apache.org/jira/browse/GERONIMO-1759?page=all ] David Jencks reassigned GERONIMO-1759: -- Assign To: Aaron Mulder (was: Paul McMahan) I can't see where the problem is pre-patch, could aaron or Paul provide better instructions for seeing the defect this fixes? (or aaron just apply the patch) getConsoleFrameworkServletPath broken - Key: GERONIMO-1759 URL: http://issues.apache.org/jira/browse/GERONIMO-1759 Project: Geronimo Type: Bug Security: public(Regular issues) Components: console Versions: 1.0 Reporter: Aaron Mulder Assignee: Aaron Mulder Fix For: 1.1, 1.2 Attachments: GERONIMO-1759.patch This function is used by the portlets to calculate the correct context path to the portal so they can refer to images bundled with the portal WAR (as opposed to bundled with the portlet WAR). It works fine on pages where you click a navigation link and land there. It does not seem to work if one portlet page has a form that submits to another portlet page and the destination calls the function. In my case, it was looking for an occurance of: /Security/Security_keystores/_st_Security_keystores_row1_col1_p1/normal/_rp_Security_keystores_row1_col1_p1_mode/1_list/_ps_Security_keystores_row1_col1_p1/normal/_pm_Security_keystores_row1_col1_p1/view/_pid/Security_keystores_row1_col1_p1/_md_Security_keystores_row1_col1_p1/view in /console/portal/Security/Security_keystores/_st_Security_keystores_row1_col1_p1/normal/_ps_Security_keystores_row1_col1_p1/normal/_pm_Security_keystores_row1_col1_p1/view/_pid/Security_keystores_row1_col1_p1/_md_Security_keystores_row1_col1_p1/view And (if you look carefully) there is clearly none there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1740) Plugin migration to Maven 2: geronimo-packaging-plugin
[ http://issues.apache.org/jira/browse/GERONIMO-1740?page=comments#action_12412667 ] Jacek Laskowski commented on GERONIMO-1740: --- Am I correct that you want the patches to be applied to 1.1 branch? Other questions: Ad1. It would be good to inform a user/developer that the tests are skipped, e.g. by executing antrun plugin and printing out a message: TODO: Enable the tests. Ad 2. What version of xmlbeans plugin are you reffering to? Could we build the latest SNAPSHOT version from the sources to work it around? Ad 3. If tests need to be forked per test, does it mean that they don't clean up after themselves? Wouldn't once work fine? Thanks for going on with the migration! Plugin migration to Maven 2: geronimo-packaging-plugin -- Key: GERONIMO-1740 URL: http://issues.apache.org/jira/browse/GERONIMO-1740 Project: Geronimo Type: Sub-task Security: public(Regular issues) Components: buildsystem Versions: 1.x Reporter: Jacek Laskowski Assignee: Anita Kulshreshtha Attachments: configs.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, m2-plugins.patch, modules.patch, pom.patch It's a task to keep track of the progress of the plugin build migration to Maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (GERONIMO-1740) Plugin migration to Maven 2: geronimo-packaging-plugin
Jacek, Thnaks! --- Jacek Laskowski (JIRA) dev@geronimo.apache.org wrote: [ http://issues.apache.org/jira/browse/GERONIMO-1740?page=comments#action_12412667 ] Jacek Laskowski commented on GERONIMO-1740: --- Am I correct that you want the patches to be applied to 1.1 branch? yes, with your and Prasad's blessing! Other questions: Ad1. It would be good to inform a user/developer that the tests are skipped, e.g. by executing antrun plugin and printing out a message: TODO: Enable the tests. These 3 tests are failing - 1. org.apache.geronimo.connector.deployment.jsr88.Connector15DCBTest 2. org.apache.geronimo.system.plugin.PluginInstallerTest 3. org.apache.geronimo.system.serverinfo.ServerInfoTest This is only temporary, and need Prasad's sharp eyes ;) Ad 2. What version of xmlbeans plugin are you reffering to? Could we build the latest SNAPSHOT version from the sources to work it around? The schemaLocation was supposed to be available in 2.0.1. I do not see it in any of the repos. http://jira.codehaus.org/browse/MXMLBEANS-3#action_63274 Ad 3. If tests need to be forked per test, does it mean that they don't clean up after themselves? Wouldn't once work fine? Two tests in security module were failing, changing the forkmode to pertest made the problem go way. Only the security module uses pertest mode, all the other modules use 'once'. I needed all the m2 jars to test the packaging plugin, hence I took these shortcuts :). Thanks Anita Thanks for going on with the migration! Plugin migration to Maven 2: geronimo-packaging-plugin -- Key: GERONIMO-1740 URL: http://issues.apache.org/jira/browse/GERONIMO-1740 Project: Geronimo Type: Sub-task Security: public(Regular issues) Components: buildsystem Versions: 1.x Reporter: Jacek Laskowski Assignee: Anita Kulshreshtha Attachments: configs.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, m2-plugins.patch, modules.patch, pom.patch It's a task to keep track of the progress of the plugin build migration to Maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[jira] Created: (XBEAN-12) Change POM's version to 2.4-SNAPSHOT
Change POM's version to 2.4-SNAPSHOT Key: XBEAN-12 URL: http://issues.apache.org/jira/browse/XBEAN-12 Project: XBean Type: Task Reporter: Alan Cabrera Assigned to: Alan Cabrera Fix For: 2.4 We need to do this so that all the POMs are consistent. One may think that there is no point in updating the versions of ALL the POMs, especially since most have not changed. This is not so. Since we store the dependencies version in the root POM, there can be subtle version mismatches in the jars. End users/developers will apreciate the simplicity of this release paradigm since they will not be forced to cherry pick consistent versions of XBean components. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (XBEAN-12) Change POM's version to 2.4-SNAPSHOT
[ http://issues.apache.org/jira/browse/XBEAN-12?page=all ] Alan Cabrera resolved XBEAN-12: --- Resolution: Fixed Change POM's version to 2.4-SNAPSHOT Key: XBEAN-12 URL: http://issues.apache.org/jira/browse/XBEAN-12 Project: XBean Type: Task Reporter: Alan Cabrera Assignee: Alan Cabrera Fix For: 2.4 We need to do this so that all the POMs are consistent. One may think that there is no point in updating the versions of ALL the POMs, especially since most have not changed. This is not so. Since we store the dependencies version in the root POM, there can be subtle version mismatches in the jars. End users/developers will apreciate the simplicity of this release paradigm since they will not be forced to cherry pick consistent versions of XBean components. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-81) Not able to build server from trunk ,
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-81?page=comments#action_12412680 ] Donald Woods commented on GERONIMODEVTOOLS-81: -- All references to repository cvs.apache.org need to be updated to people.apche.org for the 1.0.0 tag and Trunk. Not able to build server from trunk , - Key: GERONIMODEVTOOLS-81 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-81 Project: Geronimo-Devtools Type: Bug Versions: 1.0.0 Environment: Win2k , java1.4_08, maven1.02, svn 1.3 client Reporter: Mansoor 1. Checked out the lastest code from trunk using below command : svn co http://svn.apache.org/repos/asf/geronimo/trunk geronimo 2.Tried building the server .. Results : I cann't build the server due to lot of dependencies not getting downloaded. ERRORS : --- Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-20030902.160215.jar]: java.io.IOException: Unknown error downl oading; status code was: 302 150K downloaded Attempting to download commons-jelly-tags-jsl-20030211.143151.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-tags-jsl-20030211.143151.jar]: java.io.IOException: Unknown er ror downloading; status code was: 302 14K downloaded Attempting to download commons-jelly-tags-log-20030211.142821.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-tags-log-20030211.142821.jar]: java.io.IOException: Unknown er ror downloading; status code was: 302 8K downloaded Attempting to download commons-jelly-tags-velocity-20030303.205659.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-tags-velocity-20030303.205659.jar]: java.io.IOException: Unkno wn error downloading; status code was: 302 7K downloaded Attempting to download commons-jelly-tags-xml-20040613.030723.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-jelly/j ars/commons-jelly-tags-xml-20040613.030723.jar]: java.io.IOException: Unknown er ror downloading; status code was: 302 33K downloaded Attempting to download commons-logging-1.0.3.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-logging /jars/commons-logging-1.0.3.jar]: java.io.IOException: Unknown error downloading ; status code was: 302 30K downloaded Attempting to download velocity-1.4-dev.jar. Error retrieving artifact from [http://cvs.apache.org/repository/velocity/jars/v elocity-1.4-dev.jar]: java.io.IOException: Unknown error downloading; status cod e was: 302 505K downloaded Attempting to download velocity-dvsl-0.45.jar. Error retrieving artifact from [http://cvs.apache.org/repository/velocity-dvsl/j ars/velocity-dvsl-0.45.jar]: java.io.IOException: Unknown error downloading; sta tus code was: 302 25K downloaded Attempting to download xml-apis-1.0.b2.jar. Error retrieving artifact from [http://cvs.apache.org/repository/xml-apis/jars/x ml-apis-1.0.b2.jar]: java.io.IOException: Unknown error downloading; status code was: 302 106K downloaded Attempting to download isorelax-20030108.jar. Error retrieving artifact from [http://cvs.apache.org/repository/isorelax/jars/i sorelax-20030108.jar]: java.io.IOException: Unknown error downloading; status co de was: 302 188K downloaded Attempting to download jing-20030619.jar. Error retrieving artifact from [http://cvs.apache.org/repository/thaiopensource/ jars/jing-20030619.jar]: java.io.IOException: Unknown error downloading; status code was: 302 475K downloaded Attempting to download xerces-2.4.0.jar. Error retrieving artifact from [http://cvs.apache.org/repository/xerces/jars/xer ces-2.4.0.jar]: java.io.IOException: Unknown error downloading; status code was: 302 874K downloaded Attempting to download commons-io-20030203.000550.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-io/jars /commons-io-20030203.000550.jar]: java.io.IOException: Unknown error downloading ; status code was: 302 59K downloaded Attempting to download commons-net-1.1.0.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-net/jar s/commons-net-1.1.0.jar]: java.io.IOException: Unknown error downloading; status code was: 302 139K downloaded Attempting to download commons-httpclient-2.0.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-httpcli ent/jars/commons-httpclient-2.0.jar]: java.io.IOException: Unknown error downloa ding; status code was: 302 217K downloaded Attempting to download commons-lang-2.0.jar. Error retrieving artifact from [http://cvs.apache.org/repository/commons-lang/ja
goopen.org images in site
One teeny thing. The Confluence icons are still coming from goopen.org. Can we fix the HTML generator to replace those w/ local images? Regards, Alan
Re: 1.1 Status
Matt Hogstrom wrote: All, We're still waiting for the Codehaus Repo to go writeable. I just checked their web site and there was no prognosis on the date yet. I have some uncommitted performance changes and I believe others have changes as well. Gianny was also completing some work on TranQL I believe. At this point I want to release a candidate early next week based on Codehaus' situation. Then release 1.1 by the end of May. Any questions / comments reply back to this note. Matt Can we make the *real* 1.1 branch so that I can start putting in my code for 1.2? Any bug fixes will then need to be done in the new trunk and 1.1 branch. This will have the added good effect of discouraging people from jamming in new stuff into the 1.1 frozen release. Regards, Alan
Re: 1.1 Status
I'll start this discussion on Monday / Tuesday. We already have the real 1.1 branch. Were missing the real trunk :) Alan D. Cabrera wrote: Matt Hogstrom wrote: All, We're still waiting for the Codehaus Repo to go writeable. I just checked their web site and there was no prognosis on the date yet. I have some uncommitted performance changes and I believe others have changes as well. Gianny was also completing some work on TranQL I believe. At this point I want to release a candidate early next week based on Codehaus' situation. Then release 1.1 by the end of May. Any questions / comments reply back to this note. Matt Can we make the *real* 1.1 branch so that I can start putting in my code for 1.2? Any bug fixes will then need to be done in the new trunk and 1.1 branch. This will have the added good effect of discouraging people from jamming in new stuff into the 1.1 frozen release. Regards, Alan
Change to commit model for Apache Geronimo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Due to concerns about how some changes have been getting made in the codebase, I am changing the commit model for the time being. Effective immediately, the development model for Apache Geronimo is changed from Commit-Then-Review to Review-Then-Commit. This means that all code changes that aren't for documentation or a specific bug fix need to be submitted as patches to the dev@geronimo.apache.org list before getting committed. They can get applied after three other committers have voted +1 -- which in this mode means 'I have applied this patch and tested it and found it good' -- and no committers have vetoed it. I'm doing this to put to rest widespread concerns that development in Geronimo *isn't* being done entirely in the open. It's a drastic step, but those concerns have been around for a while and just don't seem to be going away. This also means that everyone needs to take interest in the changes being proposed for the code. Everyone knowing more about what everyone else is doing isn't a bad thing, and cooperating more to get them made isn't a bad thing either. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRHD+TZrNPMCpn3XdAQJ9FwQAlwe2L+SvgffPyPSvXi0GjefJBSN/DZtQ CPE/OPkJrC8QxKegPsu4wRmYJK0HkilWkojglPYSZkKEP94fOIEA+R3Nh+IByo+D q8LF12qpkvxI9RjsEMEqa3+awNt7uag0GT0WgMDEX3VMupPRq3X52V7XiSzATqmp rwb0h13AQlc= =LjSH -END PGP SIGNATURE-
Re: Change to commit model for Apache Geronimo
What concerns about changes are you speaking of? I have so far seen no such concerns. Can you please elaborate. --jason On May 21, 2006, at 4:57 PM, Rodent of Unusual Size wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Due to concerns about how some changes have been getting made in the codebase, I am changing the commit model for the time being. Effective immediately, the development model for Apache Geronimo is changed from Commit-Then-Review to Review-Then-Commit. This means that all code changes that aren't for documentation or a specific bug fix need to be submitted as patches to the dev@geronimo.apache.org list before getting committed. They can get applied after three other committers have voted +1 -- which in this mode means 'I have applied this patch and tested it and found it good' -- and no committers have vetoed it. I'm doing this to put to rest widespread concerns that development in Geronimo *isn't* being done entirely in the open. It's a drastic step, but those concerns have been around for a while and just don't seem to be going away. This also means that everyone needs to take interest in the changes being proposed for the code. Everyone knowing more about what everyone else is doing isn't a bad thing, and cooperating more to get them made isn't a bad thing either. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRHD+TZrNPMCpn3XdAQJ9FwQAlwe2L+SvgffPyPSvXi0GjefJBSN/DZtQ CPE/OPkJrC8QxKegPsu4wRmYJK0HkilWkojglPYSZkKEP94fOIEA+R3Nh+IByo+D q8LF12qpkvxI9RjsEMEqa3+awNt7uag0GT0WgMDEX3VMupPRq3X52V7XiSzATqmp rwb0h13AQlc= =LjSH -END PGP SIGNATURE-
Moving on from 1.1
I would like to make the following changes to the dev tree for Geronimo. Assuming there is concurrence and no objections I would like to: move geronimo/trunk to geronimo/branches/oldtrunk copy geronimo/branches/1.1 to geronimo/trunk Update trunk to version 1.3. I think 1.3 is a better choice to avoid any confusion over our old 1.2 I'll plan to do this on Wednesday morning at 0300 PT. Other thoughts welcome. Matt
Re: Change to commit model for Apache Geronimo
Does this apply only to the geronimo code base or all subprojects as well? (XBean, DevTools, GBuild, etc...)? - sachin On May 21, 2006, at 7:57 PM, Rodent of Unusual Size wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Due to concerns about how some changes have been getting made in the codebase, I am changing the commit model for the time being. Effective immediately, the development model for Apache Geronimo is changed from Commit-Then-Review to Review-Then-Commit. This means that all code changes that aren't for documentation or a specific bug fix need to be submitted as patches to the dev@geronimo.apache.org list before getting committed. They can get applied after three other committers have voted +1 -- which in this mode means 'I have applied this patch and tested it and found it good' -- and no committers have vetoed it. I'm doing this to put to rest widespread concerns that development in Geronimo *isn't* being done entirely in the open. It's a drastic step, but those concerns have been around for a while and just don't seem to be going away. This also means that everyone needs to take interest in the changes being proposed for the code. Everyone knowing more about what everyone else is doing isn't a bad thing, and cooperating more to get them made isn't a bad thing either. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRHD+TZrNPMCpn3XdAQJ9FwQAlwe2L+SvgffPyPSvXi0GjefJBSN/DZtQ CPE/OPkJrC8QxKegPsu4wRmYJK0HkilWkojglPYSZkKEP94fOIEA+R3Nh+IByo+D q8LF12qpkvxI9RjsEMEqa3+awNt7uag0GT0WgMDEX3VMupPRq3X52V7XiSzATqmp rwb0h13AQlc= =LjSH -END PGP SIGNATURE- -sachin
Re: Moving on from 1.1
+1 from me. -- dims On 5/21/06, Matt Hogstrom [EMAIL PROTECTED] wrote: I would like to make the following changes to the dev tree for Geronimo. Assuming there is concurrence and no objections I would like to: move geronimo/trunk to geronimo/branches/oldtrunk copy geronimo/branches/1.1 to geronimo/trunk Update trunk to version 1.3. I think 1.3 is a better choice to avoid any confusion over our old 1.2 I'll plan to do this on Wednesday morning at 0300 PT. Other thoughts welcome. Matt -- Davanum Srinivas : http://wso2.com/blogs/
Re: Moving on from 1.1
+1 Anita --- Davanum Srinivas [EMAIL PROTECTED] wrote: +1 from me. -- dims On 5/21/06, Matt Hogstrom [EMAIL PROTECTED] wrote: I would like to make the following changes to the dev tree for Geronimo. Assuming there is concurrence and no objections I would like to: move geronimo/trunk to geronimo/branches/oldtrunk copy geronimo/branches/1.1 to geronimo/trunk Update trunk to version 1.3. I think 1.3 is a better choice to avoid any confusion over our old 1.2 I'll plan to do this on Wednesday morning at 0300 PT. Other thoughts welcome. Matt -- Davanum Srinivas : http://wso2.com/blogs/ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Change to commit model for Apache Geronimo
Do revolution rules still apply or have they been suspended by fiat also? -dain On May 21, 2006, at 4:57 PM, Rodent of Unusual Size wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Due to concerns about how some changes have been getting made in the codebase, I am changing the commit model for the time being. Effective immediately, the development model for Apache Geronimo is changed from Commit-Then-Review to Review-Then-Commit. This means that all code changes that aren't for documentation or a specific bug fix need to be submitted as patches to the dev@geronimo.apache.org list before getting committed. They can get applied after three other committers have voted +1 -- which in this mode means 'I have applied this patch and tested it and found it good' -- and no committers have vetoed it. I'm doing this to put to rest widespread concerns that development in Geronimo *isn't* being done entirely in the open. It's a drastic step, but those concerns have been around for a while and just don't seem to be going away. This also means that everyone needs to take interest in the changes being proposed for the code. Everyone knowing more about what everyone else is doing isn't a bad thing, and cooperating more to get them made isn't a bad thing either. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRHD+TZrNPMCpn3XdAQJ9FwQAlwe2L+SvgffPyPSvXi0GjefJBSN/DZtQ CPE/OPkJrC8QxKegPsu4wRmYJK0HkilWkojglPYSZkKEP94fOIEA+R3Nh+IByo+D q8LF12qpkvxI9RjsEMEqa3+awNt7uag0GT0WgMDEX3VMupPRq3X52V7XiSzATqmp rwb0h13AQlc= =LjSH -END PGP SIGNATURE-
Re: Moving on from 1.1
+1 -dain On May 21, 2006, at 6:53 PM, Matt Hogstrom wrote: I would like to make the following changes to the dev tree for Geronimo. Assuming there is concurrence and no objections I would like to: move geronimo/trunk to geronimo/branches/oldtrunk copy geronimo/branches/1.1 to geronimo/trunk Update trunk to version 1.3. I think 1.3 is a better choice to avoid any confusion over our old 1.2 I'll plan to do this on Wednesday morning at 0300 PT. Other thoughts welcome. Matt
