Re: [VOTE] 2.0-M4 Binaries available (rc1)
What do we do for anyone else who wants to build? Maybe we should release the binaries only? Regards, Alan On Apr 3, 2007, at 9:03 AM, Matt Hogstrom wrote: Did you want the repo so you can build ? 1335571863 Apr 1 06:00 geronimo-2.0-M4-repository.tar.gz I can make it available on people if you like. It has the correct SNAPSHOT versions for dependencies. On Apr 3, 2007, at 11:31 AM, Alan D. Cabrera wrote: -1 (non-veto) since it does not build. Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
Did you want the repo so you can build ? 1335571863 Apr 1 06:00 geronimo-2.0-M4-repository.tar.gz I can make it available on people if you like. It has the correct SNAPSHOT versions for dependencies. On Apr 3, 2007, at 11:31 AM, Alan D. Cabrera wrote: -1 (non-veto) since it does not build. Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
-1 (non-veto) since it does not build. Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
+1 Jacek On 4/1/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks! -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: [VOTE] 2.0-M4 Binaries available (rc1)
On Apr 2, 2007, at 6:50 PM, Joe Bohn wrote: David, Very true. I had just assumed that the minimal tomcat config.xml must have included Jasper ... but I see that it doesn't. I did verify again that I can deploy the war on tomcat minimal and it works. When I list-modules I see the jasper config listed and started but not the jasper-deployer. Looking a little further I see that tomcat6 includes a dependency in its pom on jasper with a comment stating that it is "required because tomcat and jasper share the LifeCycleProvider interface, or AnnotationProcessor". Jetty doesn't include this same dependency and so it is not included. Ah, hoist by my own petard or something like that :-). I may be able to fix this in my next tomcat proposal. thanks david jencks Joe David Jencks wrote: if jsps work on tomcat without the jasper and jasper-deployer configs then something is wrong :-) Can you double check this? I don't have a real problem including jasper with both jetty and tomcat, but I would prefer to know _how_ its getting included :-) thanks david jencks On Apr 2, 2007, at 3:11 PM, Joe Bohn wrote: To maintain backward compatibility and consistency with the minimal tomcat assembly (I only had this problem with Jetty) I think we need to add Jasper & Jasper-Deployer into the assembly. I'll give it a try. JSF is another story. It wasn't included in earlier minimal assemblies so we're not regressing any function if we choose to not include it. I don't have a strong opinion on it one way or the other. Joe David Jencks wrote: ya, I think I figured "minimal" meant "no jsps" which no one except greg wilkins might agree with :-). How about jsf? (maybe I'm exaggerating his distaste for jsps) for jsps we need to add the jasper and jasper-builder configs. for jsf we need to add myfaces and myfaces-builder configs. the builder configs need to be loaded, the others can have load="false": any such config needs to be in the pom (yes, I had to build the tomcat-ee config about 4-6 times while I sorted out which went where) thanks david jencks On Apr 2, 2007, at 2:36 PM, Joe Bohn wrote: Joe Bohn wrote: geronimo-jetty6-minimal: - Deploying a simple JSP war resulted in an UnavailableException for org.apache.jasper.servlet.JspServlet from the application classloader and failures attempting to start the GBean. I'll open a JIRA for this issue. I suspect that we're not including the correct jasper item in the classloader of the web app. I think we can push this milestone out even with this error given that people can work with the jetty and the jee5 assembly until this issue is resolved in a subsequent milestone. Created https://issues.apache.org/jira/browse/GERONIMO-3057 Joe
Re: [VOTE] 2.0-M4 Binaries available (rc1)
+1 On Apr 1, 2007, at 5:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
David, Very true. I had just assumed that the minimal tomcat config.xml must have included Jasper ... but I see that it doesn't. I did verify again that I can deploy the war on tomcat minimal and it works. When I list-modules I see the jasper config listed and started but not the jasper-deployer. Looking a little further I see that tomcat6 includes a dependency in its pom on jasper with a comment stating that it is "required because tomcat and jasper share the LifeCycleProvider interface, or AnnotationProcessor". Jetty doesn't include this same dependency and so it is not included. Joe David Jencks wrote: if jsps work on tomcat without the jasper and jasper-deployer configs then something is wrong :-) Can you double check this? I don't have a real problem including jasper with both jetty and tomcat, but I would prefer to know _how_ its getting included :-) thanks david jencks On Apr 2, 2007, at 3:11 PM, Joe Bohn wrote: To maintain backward compatibility and consistency with the minimal tomcat assembly (I only had this problem with Jetty) I think we need to add Jasper & Jasper-Deployer into the assembly. I'll give it a try. JSF is another story. It wasn't included in earlier minimal assemblies so we're not regressing any function if we choose to not include it. I don't have a strong opinion on it one way or the other. Joe David Jencks wrote: ya, I think I figured "minimal" meant "no jsps" which no one except greg wilkins might agree with :-). How about jsf? (maybe I'm exaggerating his distaste for jsps) for jsps we need to add the jasper and jasper-builder configs. for jsf we need to add myfaces and myfaces-builder configs. the builder configs need to be loaded, the others can have load="false": any such config needs to be in the pom (yes, I had to build the tomcat-ee config about 4-6 times while I sorted out which went where) thanks david jencks On Apr 2, 2007, at 2:36 PM, Joe Bohn wrote: Joe Bohn wrote: geronimo-jetty6-minimal: - Deploying a simple JSP war resulted in an UnavailableException for org.apache.jasper.servlet.JspServlet from the application classloader and failures attempting to start the GBean. I'll open a JIRA for this issue. I suspect that we're not including the correct jasper item in the classloader of the web app. I think we can push this milestone out even with this error given that people can work with the jetty and the jee5 assembly until this issue is resolved in a subsequent milestone. Created https://issues.apache.org/jira/browse/GERONIMO-3057 Joe
Re: [VOTE] 2.0-M4 Binaries available (rc1)
if jsps work on tomcat without the jasper and jasper-deployer configs then something is wrong :-) Can you double check this? I don't have a real problem including jasper with both jetty and tomcat, but I would prefer to know _how_ its getting included :-) thanks david jencks On Apr 2, 2007, at 3:11 PM, Joe Bohn wrote: To maintain backward compatibility and consistency with the minimal tomcat assembly (I only had this problem with Jetty) I think we need to add Jasper & Jasper-Deployer into the assembly. I'll give it a try. JSF is another story. It wasn't included in earlier minimal assemblies so we're not regressing any function if we choose to not include it. I don't have a strong opinion on it one way or the other. Joe David Jencks wrote: ya, I think I figured "minimal" meant "no jsps" which no one except greg wilkins might agree with :-). How about jsf? (maybe I'm exaggerating his distaste for jsps) for jsps we need to add the jasper and jasper-builder configs. for jsf we need to add myfaces and myfaces-builder configs. the builder configs need to be loaded, the others can have load="false": any such config needs to be in the pom (yes, I had to build the tomcat-ee config about 4-6 times while I sorted out which went where) thanks david jencks On Apr 2, 2007, at 2:36 PM, Joe Bohn wrote: Joe Bohn wrote: geronimo-jetty6-minimal: - Deploying a simple JSP war resulted in an UnavailableException for org.apache.jasper.servlet.JspServlet from the application classloader and failures attempting to start the GBean. I'll open a JIRA for this issue. I suspect that we're not including the correct jasper item in the classloader of the web app. I think we can push this milestone out even with this error given that people can work with the jetty and the jee5 assembly until this issue is resolved in a subsequent milestone. Created https://issues.apache.org/jira/browse/GERONIMO-3057 Joe
Re: [VOTE] 2.0-M4 Binaries available (rc1)
To maintain backward compatibility and consistency with the minimal tomcat assembly (I only had this problem with Jetty) I think we need to add Jasper & Jasper-Deployer into the assembly. I'll give it a try. JSF is another story. It wasn't included in earlier minimal assemblies so we're not regressing any function if we choose to not include it. I don't have a strong opinion on it one way or the other. Joe David Jencks wrote: ya, I think I figured "minimal" meant "no jsps" which no one except greg wilkins might agree with :-). How about jsf? (maybe I'm exaggerating his distaste for jsps) for jsps we need to add the jasper and jasper-builder configs. for jsf we need to add myfaces and myfaces-builder configs. the builder configs need to be loaded, the others can have load="false": any such config needs to be in the pom (yes, I had to build the tomcat-ee config about 4-6 times while I sorted out which went where) thanks david jencks On Apr 2, 2007, at 2:36 PM, Joe Bohn wrote: Joe Bohn wrote: geronimo-jetty6-minimal: - Deploying a simple JSP war resulted in an UnavailableException for org.apache.jasper.servlet.JspServlet from the application classloader and failures attempting to start the GBean. I'll open a JIRA for this issue. I suspect that we're not including the correct jasper item in the classloader of the web app. I think we can push this milestone out even with this error given that people can work with the jetty and the jee5 assembly until this issue is resolved in a subsequent milestone. Created https://issues.apache.org/jira/browse/GERONIMO-3057 Joe
Re: [VOTE] 2.0-M4 Binaries available (rc1)
ya, I think I figured "minimal" meant "no jsps" which no one except greg wilkins might agree with :-). How about jsf? (maybe I'm exaggerating his distaste for jsps) for jsps we need to add the jasper and jasper-builder configs. for jsf we need to add myfaces and myfaces-builder configs. the builder configs need to be loaded, the others can have load="false": any such config needs to be in the pom (yes, I had to build the tomcat-ee config about 4-6 times while I sorted out which went where) thanks david jencks On Apr 2, 2007, at 2:36 PM, Joe Bohn wrote: Joe Bohn wrote: geronimo-jetty6-minimal: - Deploying a simple JSP war resulted in an UnavailableException for org.apache.jasper.servlet.JspServlet from the application classloader and failures attempting to start the GBean. I'll open a JIRA for this issue. I suspect that we're not including the correct jasper item in the classloader of the web app. I think we can push this milestone out even with this error given that people can work with the jetty and the jee5 assembly until this issue is resolved in a subsequent milestone. Created https://issues.apache.org/jira/browse/GERONIMO-3057 Joe
Re: [VOTE] 2.0-M4 Binaries available (rc1)
Joe Bohn wrote: geronimo-jetty6-minimal: - Deploying a simple JSP war resulted in an UnavailableException for org.apache.jasper.servlet.JspServlet from the application classloader and failures attempting to start the GBean. I'll open a JIRA for this issue. I suspect that we're not including the correct jasper item in the classloader of the web app. I think we can push this milestone out even with this error given that people can work with the jetty and the jee5 assembly until this issue is resolved in a subsequent milestone. Created https://issues.apache.org/jira/browse/GERONIMO-3057 Joe
Re: [VOTE] 2.0-M4 Binaries available (rc1)
Joe Bohn wrote: geronimo-jetty6-jee5: - I received a ton of WARNing messages when I deployed a simple war. All the messages were complaining about not being able to read a jar file and it appears it was going thru each jar in our repository. I'll open a JIRA for this problem. Created JIRA: https://issues.apache.org/jira/browse/GERONIMO-3056 Joe
Re: [VOTE] 2.0-M4 Binaries available (rc1)
Joe Bohn wrote: geronimo-jetty6-jee5: - Terminating the server from the admin console resulted in some SQL exceptions because there was no longer a current connection. I think this may be a know problem (sounds familiar) ... if not I'll open a JIRA for this one too. geronimo-tomcat6-jee5: - Terminating the server had the same SQLExceptions as with Jetty. Looks like the termination issue was reported on 2.0-M2 ... https://issues.apache.org/jira/browse/GERONIMO-2835 Joe
Re: [VOTE] 2.0-M4 Binaries available (rc1)
+1 David On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
+1 -dain On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
They don't build. There's a problem with missing CXF classes. Regards, Alan On Apr 1, 2007, at 12:39 PM, Matt Hogstrom wrote: See the reply to Alan on the sources. Regarding the assemblies no, I won't be publishing them per the earlier discussion. On Apr 1, 2007, at 3:33 PM, Jason Dillon wrote: Matt are you still deploying assemblies? This looks like the work of the release plugin trying to make source archives out of the module... this isn't really a -src assembly which contains the entire src of the project. --jason On Apr 1, 2007, at 12:12 PM, Alan D. Cabrera wrote: The sources seem to be missing. Is there any reason why they're in jars and not zip/tgz? Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http:// people.apache.org/~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
[X] +1 - Release these binaries with some comments: - embedded derby databases not accessible GERONIMO-3051 - SQL errors while shutting down both Jetty and Tomcat - config-substitutions.properties missing in Tomcat dist GERONIMO-2941 Only tested jee5 on windows. Cheers! Hernan Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
[X] +1 - Release these binaries I downloaded all 4 assemblies, did some minimal poking around the admin console for the JEE5 assemblies, and deployed a simple web app with a single JSP on each. There are some issues but I think this is good enough for another milestone release. Here are the problems that I noticed: geronimo-jetty6-jee5: - I received a ton of WARNing messages when I deployed a simple war. All the messages were complaining about not being able to read a jar file and it appears it was going thru each jar in our repository. I'll open a JIRA for this problem. - Terminating the server from the admin console resulted in some SQL exceptions because there was no longer a current connection. I think this may be a know problem (sounds familiar) ... if not I'll open a JIRA for this one too. geronimo-tomcat6-jee5: - The deploy went fine with no WARNing messages. - Terminating the server had the same SQLExceptions as with Jetty. I also decided to try out the minimal assemblies although I'm not sure anybody would really be using those for this milestone given that we're trying to get more meaty JEE5 functions out. geronimo-tomcat6-minimal: - Deploying a simple war worked fine with no unexpected warning messages and I was able to access the web app. geronimo-jetty6-minimal: - Deploying a simple JSP war resulted in an UnavailableException for org.apache.jasper.servlet.JspServlet from the application classloader and failures attempting to start the GBean. I'll open a JIRA for this issue. I suspect that we're not including the correct jasper item in the classloader of the web app. I think we can push this milestone out even with this error given that people can work with the jetty and the jee5 assembly until this issue is resolved in a subsequent milestone. Joe Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
[DISCUSS] 2.0-M4 artifacts (was Re: [VOTE] 2.0-M4 Binaries available (rc1))
Two issues I think we're discussing. First, the *-sources should not be on people and were copied as part of a script I had to grab the assemblies. They have been removed. The *-sources have been replaced with the SVN export of the tree used to build the artifacts and are the *-src.[tar.gz | .zip] files folks are used to; sorry for the confusion. When I mentioned not deploying the assemblies I was referring to the SNAPSHOT repo which is a different issue and when deploying G for SNAPSHOTs I'll make sure that I don't include the assemblies in that process.
Re: [VOTE] 2.0-M4 Binaries available (rc1)
So why are there *-sources.jar* bits in there then? --jason On Apr 1, 2007, at 12:39 PM, Matt Hogstrom wrote: See the reply to Alan on the sources. Regarding the assemblies no, I won't be publishing them per the earlier discussion. On Apr 1, 2007, at 3:33 PM, Jason Dillon wrote: Matt are you still deploying assemblies? This looks like the work of the release plugin trying to make source archives out of the module... this isn't really a -src assembly which contains the entire src of the project. --jason On Apr 1, 2007, at 12:12 PM, Alan D. Cabrera wrote: The sources seem to be missing. Is there any reason why they're in jars and not zip/tgz? Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http:// people.apache.org/~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
See the reply to Alan on the sources. Regarding the assemblies no, I won't be publishing them per the earlier discussion. On Apr 1, 2007, at 3:33 PM, Jason Dillon wrote: Matt are you still deploying assemblies? This looks like the work of the release plugin trying to make source archives out of the module... this isn't really a -src assembly which contains the entire src of the project. --jason On Apr 1, 2007, at 12:12 PM, Alan D. Cabrera wrote: The sources seem to be missing. Is there any reason why they're in jars and not zip/tgz? Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
Hi Alan, Thanks for the reminder (it was a bit early / late). I'm commting the final changes to svn and will put the source files out there in gz / zip form. I'll be uploading the sources you are looking for in a few minutes. The other sources you see are produced by Maven as part of the build process. On Apr 1, 2007, at 3:12 PM, Alan D. Cabrera wrote: The sources seem to be missing. Is there any reason why they're in jars and not zip/tgz? Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
Matt are you still deploying assemblies? This looks like the work of the release plugin trying to make source archives out of the module... this isn't really a -src assembly which contains the entire src of the project. --jason On Apr 1, 2007, at 12:12 PM, Alan D. Cabrera wrote: The sources seem to be missing. Is there any reason why they're in jars and not zip/tgz? Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
Re: [VOTE] 2.0-M4 Binaries available (rc1)
The sources seem to be missing. Is there any reason why they're in jars and not zip/tgz? Regards, Alan On Apr 1, 2007, at 2:54 AM, Matt Hogstrom wrote: I have placed the 2.0-M4 binaries out on http://people.apache.org/ ~hogstrom/2.0-M4-rc1 for you to take a look at. (They are uploading as I write this). I have done some testing with DayTrader. There is an issue in connecting with he MDB container which still needs to be worked out so the application will not deploy as is. However, given the scopwe of function DayTrader covers as well as all the late code drops I don't see an issue with that. Smaller samples should be ok and tests look good. Given that we're in the final stages of testing I'd like to get this Milestone on the wire as is and fix issues in trunk. Users that pull this binary and report issues will help us in the Drive to 5. Other than that limitation I think this Milestone looks ready to go. After reviewing the content please cast your vote. [ ] +1 - Release these binaries [ ] 0 [ ] -1 Do not release these binaries (provide reason) This vote will conclude on April 4th at 0600 Eastern. Thanks!
