Dain, I fixed GERONIMO-2270 (redeploy when module ID includes version but not type) but this did not fix GERONIMO-2269 (redeploy with resource-ref when module ID includes artifact only). There's a stack trace in the Jira -- any suggestions on how to pursue it?
http://issues.apache.org/jira/browse/GERONIMO-2269 Matt, I was assuming the point of branches and RC builds was to test for obvious problems, and I think the deploy tool is fairly central to the user experience, and since we appear to have some TCK issues anyway... Well, whatever, I attached the patch to GERONIMO-2270 and you can apply it or not as you see fit. Thanks, Aaron On 8/3/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
Aaron, I missed the cut off for 1.1.1 on the three JIRA's I had. I'll move the remaining 1.1.1s to 1.1.2 and then we'll cut a 1.1.2 a few weeks after 1.1.1. Perhaps this is the start of the fast and furious release cycle that Hiram loves so much :) Dain Sundstrom wrote: > On Aug 3, 2006, at 9:18 AM, Aaron Mulder wrote: > >> I think this is a blocker. >> >> I tried redeploying a web application, both with and without a version >> in the module ID. It failed both ways, though differently for each. >> >> Matt, do you mind if we work on this in the 1.1.1 branch? > > I'd say it should be worked on in 1.1.2. > >> Dain or David Jencks, any chance you could look at the "without a >> version in the module ID" case? It complained about a dead proxy when >> Spring accessed a JDBC pool at java:comp/env/jdbc/DataSource during >> startup of the new version (GERONIMO-2269) >> >> Thanks, >> Aaron >> >> http://issues.apache.org/jira/browse/GERONIMO-2269 > > My guess is this one is a side effect of the next one, so I'd fix 2270 > first and rerun this test case. > >> http://issues.apache.org/jira/browse/GERONIMO-2270 > > Didn't you write the redeploy code? > > -dain > > > >
