[ http://issues.apache.org/jira/browse/GERONIMO-1466?page=comments#action_12362774 ]
David Jencks commented on GERONIMO-1466: ---------------------------------------- I don't understand your question. We have fixed a bug in geronimo (jetty security problem, requiring changing jetty version number) therefore we need a new geronimo version, currently 1.0.1-SNAPSHOT. Since openejb depends on geronimo, we have to up the openejb version number also. What other choice do we have? If we had version ranges in our dependencies we could avoid changing the openejb version number until we changed openejb code, but we don't at this point. If we had version ranges we wouldn't need 1.0.1 for the jetty version change either. > Preparing 1.0 branch for development of 1.0.1 > --------------------------------------------- > > Key: GERONIMO-1466 > URL: http://issues.apache.org/jira/browse/GERONIMO-1466 > Project: Geronimo > Type: Improvement > Environment: All > Reporter: Matt Hogstrom > Assignee: David Jencks > Fix For: 1.0.1 > > Update the 1.0 Branch with the changes to prepare it for 1.0.1 > This JIRA will be used to track all changes required to version for 1.0.1 so > moving from SNAPSHOT to a release will be a bit simpler. -- 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
