Re: 1.1 Package Upgrade List
The note I saw on our Jira said that commons-fileupload 1.1 requires commons-io 1.1 -- do you have a separate indication that commons-io 1.2 is needed? http://issues.apache.org/jira/browse/GERONIMO-1756 http://jakarta.apache.org/commons/fileupload/changes-report.html Thanks, Aaron On 5/9/06, Donald Woods <[EMAIL PROTECTED]> wrote: Moving to Commons-Fileupload 1.1 also requires upgrading to commons-io 1.2. Also, why are we upgrading to STAX 1.1.1, when all we need is just the STAX API? -Donald David Jencks wrote: > I've built locally using HOWL 1.0.1 and it seems to work fine with no > geronimo changes. I think the main problem will be getting it onto a > suitable maven repo: I haven't found it to be released anywhere. Is > pushing it into a m2 repo sufficient, are jars auto-backported into m1? > > thanks > david jencks > > On May 9, 2006, at 10:22 AM, Matt Hogstrom wrote: > >> You are correct Kevan. Thanks >> >> Kevan Miller wrote: >> >>> On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote: >>> Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload1.1-devto1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9to5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT >>> >>> We're already on Tomcat 5.5.15, but fine to keep it on the list. >>> I assume the final tranql and tranql-connector versions will be 1.3 >>> and 1.2. We'll use the SNAPSHOT versions until a new tranql release >>> is published (which will happen before we ship 1.1...). >>> I'll start testing these versions once we clean up a few problems. >>> --kevan >>> Keep 'em coming. Matt Aaron Mulder wrote: > That issue has a great list. > We definitely need to try updating commons-fileupload (from 1.1- > dev to > 1.1). I think there may even be a separate Jira for that. But the > old one occasionally hangs, so it's definitely worth trying the new > one. > Thanks, >Aaron > On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> Here are the packages I'm recommending for 1.1. If I missed one >> please chime in. >> >> Axis from 1.4-356167 to 1.4 >> jasper from 5.5.9 to 5.5.15 >> Jetty from 5.1.9 to 5.1.10 >> stax from 1.1.1-dev to 1.1.2 >> tranql from1.2.1 to 1.3-SNAPSHOT >> tranql-connector from 1.1 to 1.2-SNAPSHOT >> >> This is the list so far...I've updated >> http://opensource.atlassian.com/confluence/oss/display/GERONIMO/ >> Geronimo+Package+Tracking >> with this information. >> >> Was mentioned on the list: >> Howl- Researching this >> > > >
Re: 1.1 Package Upgrade List
On 5/10/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote: All work related to M2 was halted until the trunk was merged. M2 packaging plugin would require transferring all M2 work to 1.1. I do not think there are any plans to do it before the merge or at least the 1.1. release. I think using Maven1 will be best at this time. Let's hear from Jacek.. Well, the issue with the 1.1 branch has completely distracted me from the M2 migration and I've decided to wait patiently until Geronimo 1.1 is out. I don't know if it'd be worthwhile to go on with the migration on the trunk or start it off on the 1.1 branch. I don't want to make noise about it and am learning M2 tips and tricks so I'm better prepared for the task. I'll start another thread about our M2 migration and its place Anita Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: 1.1 Package Upgrade List
Someone hit me in the head about priorities (I think it was Prasad). If someone isn't working on 1.1 and has time this is excellent. Please don't let me distract you from 1.1 though :) Prasad Kashyap wrote: Hi Matt, Moving the M2 conversion work from the trunk to 1.1 should not be disruptive. It would have the following changes 1) add pom.xmls in all modules 2) add a few ant files in some modules 3) change *Test.java files in quite a few modules. I have no strong objections to it except that I'm afraid it might pull folks off of 1.1 while trying to do this. Cheers Prasad. On 5/11/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: I'd defer to Jacek to do the merging since he's familiar with it. If he's not available then I'd be happy to take a patch from you :) Also, if anyone has any objections re: getting this done then hollar now. anita kulshreshtha wrote: > > --- Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> Since the M2 conversion is independent of 1.1 what does the community >> think about starting that >> merge into 1.1 now? I think it would allow us to become more >> productive on 1.2 since the work would >> already be in place. For those working on the M2 conversion what do >> you think about starting that >> work and do you think we can do it without impacting 1.1? >We can safely transfer all the work from 1.2 to 1.1 without > impacting anything. What is the best way to do this? > > Thanks > Anita > >> anita kulshreshtha wrote: >>> All work related to M2 was halted until the trunk was merged. >> M2 >>> packaging plugin would require transferring all M2 work to 1.1. I >> do >>> not think there are any plans to do it before the merge or at least >> the >>> 1.1. release. I think using Maven1 will be best at this time. Let's >>> hear from Jacek.. >>> >>> Thanks >>> Anita >>> >>> --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: >>> I haven't seen any geronimo plugin for m2 in head. That whould be very usefull, especially because Geronimo plugins >> have to be in a m2 layout, but the only tools to create a car is a m1 >> plugin. Any idea ? Cheers, Guillaume Nodet Aaron Mulder wrote: > I'd rather handle the ApacheDS integration separately from the >> 1.1 > release. Fortunately, the plugins work with the Maven 2 repository, > so that issue should be easier. > > The main question is how to do the build and packaging. If the >> API is > unchanged, we can build our integration module using our Maven 1 > packaging plugin against ADS 0.9.2 and just have it apply the >> 1.0.x > JARs at installation time. If the API is different, it may make the > most sense to try to split out our directory integration and do >> the > build and packaging under Maven 2 (I'm assuming that Geronimo >> HEAD has > a Maven 2 packaging plugin, but if not, I guess we can work on one). > Thanks, >Aaron > > On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > >> ApacheDS0.9.2 to 1.0-RC2 ? >> I have a patch to port the Geronimo part to 1.0-RC2. However, >> currently ADS 1.0 jars propagated to maven2 repo only. >> >> 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: >>> Consolidated list so far is: >>> >>> Axis from 1.4-356167 to 1.4 >>> commons-fileupload 1.1-dev to 1.1 >>> jasper from 5.5.9 to 5.5.15 >>> Jetty from 5.1.9 to 5.1.10 >>> stax from 1.1.1-dev to 1.1.2 >>> Tomcat 5.5.9 to 5.5.15 >>> tranql from1.2.1 to 1.3-SNAPSHOT >>> tranql-connector from 1.1 to 1.2-SNAPSHOT >>> >>> Keep 'em coming. >>> >>> Matt >>> >>> Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from >> 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > Here are the packages I'm recommending for 1.1. If I missed one > please chime in. > > Axis from 1.4-356167 to 1.4 > jasper from 5.5.9 to 5.5.15 > Jetty from 5.1.9 to 5.1.10 > stax from 1.1.1-dev to 1.1.2 > tranql from1.2.1 to 1.3-SNAPSHOT > tranql-connector from 1.1 to 1.2-SNAPSHOT > > This is the list so far...I've updated > > http://opensource.atlassian.com/confluence/oss/display/GERO
Re: 1.1 Package Upgrade List
Ant files are used to do some custom things that jelly did in Maven 1. Eg: modules\installer-support\setup.xml The Test class names didn't change. Minor modifications to the code in the *Test.java were done. Sorry for the confusion. Cheers Prasad On 5/11/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: What are the ant files used for ? And why changing the test class names ? Surefire can be configured specifically if needed ... So this change could be delayed. Cheers, Guillaume Nodet Prasad Kashyap wrote: > Hi Matt, > > Moving the M2 conversion work from the trunk to 1.1 should not be > disruptive. It would have the following changes > 1) add pom.xmls in all modules > 2) add a few ant files in some modules > 3) change *Test.java files in quite a few modules. > > I have no strong objections to it except that I'm afraid it might pull > folks off of 1.1 while trying to do this. > > Cheers > Prasad. > > On 5/11/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> I'd defer to Jacek to do the merging since he's familiar with it. If >> he's not available then I'd be >> happy to take a patch from you :) >> >> Also, if anyone has any objections re: getting this done then hollar >> now. >> >> anita kulshreshtha wrote: >> > >> > --- Matt Hogstrom <[EMAIL PROTECTED]> wrote: >> > >> >> Since the M2 conversion is independent of 1.1 what does the community >> >> think about starting that >> >> merge into 1.1 now? I think it would allow us to become more >> >> productive on 1.2 since the work would >> >> already be in place. For those working on the M2 conversion what do >> >> you think about starting that >> >> work and do you think we can do it without impacting 1.1? >> >We can safely transfer all the work from 1.2 to 1.1 without >> > impacting anything. What is the best way to do this? >> > >> > Thanks >> > Anita >> > >> >> anita kulshreshtha wrote: >> >>> All work related to M2 was halted until the trunk was merged. >> >> M2 >> >>> packaging plugin would require transferring all M2 work to 1.1. I >> >> do >> >>> not think there are any plans to do it before the merge or at least >> >> the >> >>> 1.1. release. I think using Maven1 will be best at this time. Let's >> >>> hear from Jacek.. >> >>> >> >>> Thanks >> >>> Anita >> >>> >> >>> --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> >>> >> I haven't seen any geronimo plugin for m2 in head. >> That whould be very usefull, especially because Geronimo plugins >> >> have >> to >> be in a m2 layout, but the only tools to create a car is a m1 >> >> plugin. >> Any idea ? >> >> Cheers, >> Guillaume Nodet >> >> Aaron Mulder wrote: >> >> > I'd rather handle the ApacheDS integration separately from the >> >> 1.1 >> > release. Fortunately, the plugins work with the Maven 2 >> repository, >> > so that issue should be easier. >> > >> > The main question is how to do the build and packaging. If the >> >> API >> is >> > unchanged, we can build our integration module using our Maven 1 >> > packaging plugin against ADS 0.9.2 and just have it apply the >> >> 1.0.x >> > JARs at installation time. If the API is different, it may make >> the >> > most sense to try to split out our directory integration and do >> >> the >> > build and packaging under Maven 2 (I'm assuming that Geronimo >> >> HEAD >> has >> > a Maven 2 packaging plugin, but if not, I guess we can work on >> one). >> > Thanks, >> >Aaron >> > >> > On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: >> > >> >> ApacheDS0.9.2 to 1.0-RC2 ? >> >> I have a patch to port the Geronimo part to 1.0-RC2. However, >> >> currently ADS 1.0 jars propagated to maven2 repo only. >> >> >> >> 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: >> >>> Consolidated list so far is: >> >>> >> >>> Axis from 1.4-356167 to 1.4 >> >>> commons-fileupload 1.1-dev to 1.1 >> >>> jasper from 5.5.9 to 5.5.15 >> >>> Jetty from 5.1.9 to 5.1.10 >> >>> stax from 1.1.1-dev to 1.1.2 >> >>> Tomcat 5.5.9 to 5.5.15 >> >>> tranql from1.2.1 to 1.3-SNAPSHOT >> >>> tranql-connector from 1.1 to 1.2-SNAPSHOT >> >>> >> >>> Keep 'em coming. >> >>> >> >>> Matt >> >>> >> >>> Aaron Mulder wrote: >> That issue has a great list. >> >> We definitely need to try updating commons-fileupload (from >> >> 1.1-dev to >> 1.1). I think there may even be a separate Jira for that. >> But the >> old one occasionally hangs, so it's definitely worth trying >> the new >> one. >> >> Thanks, >> Aaron >> >> On 5/9/06, Matt Hogstrom <[EMAI
Re: 1.1 Package Upgrade List
What are the ant files used for ? And why changing the test class names ? Surefire can be configured specifically if needed ... So this change could be delayed. Cheers, Guillaume Nodet Prasad Kashyap wrote: Hi Matt, Moving the M2 conversion work from the trunk to 1.1 should not be disruptive. It would have the following changes 1) add pom.xmls in all modules 2) add a few ant files in some modules 3) change *Test.java files in quite a few modules. I have no strong objections to it except that I'm afraid it might pull folks off of 1.1 while trying to do this. Cheers Prasad. On 5/11/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: I'd defer to Jacek to do the merging since he's familiar with it. If he's not available then I'd be happy to take a patch from you :) Also, if anyone has any objections re: getting this done then hollar now. anita kulshreshtha wrote: > > --- Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> Since the M2 conversion is independent of 1.1 what does the community >> think about starting that >> merge into 1.1 now? I think it would allow us to become more >> productive on 1.2 since the work would >> already be in place. For those working on the M2 conversion what do >> you think about starting that >> work and do you think we can do it without impacting 1.1? >We can safely transfer all the work from 1.2 to 1.1 without > impacting anything. What is the best way to do this? > > Thanks > Anita > >> anita kulshreshtha wrote: >>> All work related to M2 was halted until the trunk was merged. >> M2 >>> packaging plugin would require transferring all M2 work to 1.1. I >> do >>> not think there are any plans to do it before the merge or at least >> the >>> 1.1. release. I think using Maven1 will be best at this time. Let's >>> hear from Jacek.. >>> >>> Thanks >>> Anita >>> >>> --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: >>> I haven't seen any geronimo plugin for m2 in head. That whould be very usefull, especially because Geronimo plugins >> have to be in a m2 layout, but the only tools to create a car is a m1 >> plugin. Any idea ? Cheers, Guillaume Nodet Aaron Mulder wrote: > I'd rather handle the ApacheDS integration separately from the >> 1.1 > release. Fortunately, the plugins work with the Maven 2 repository, > so that issue should be easier. > > The main question is how to do the build and packaging. If the >> API is > unchanged, we can build our integration module using our Maven 1 > packaging plugin against ADS 0.9.2 and just have it apply the >> 1.0.x > JARs at installation time. If the API is different, it may make the > most sense to try to split out our directory integration and do >> the > build and packaging under Maven 2 (I'm assuming that Geronimo >> HEAD has > a Maven 2 packaging plugin, but if not, I guess we can work on one). > Thanks, >Aaron > > On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > >> ApacheDS0.9.2 to 1.0-RC2 ? >> I have a patch to port the Geronimo part to 1.0-RC2. However, >> currently ADS 1.0 jars propagated to maven2 repo only. >> >> 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: >>> Consolidated list so far is: >>> >>> Axis from 1.4-356167 to 1.4 >>> commons-fileupload 1.1-dev to 1.1 >>> jasper from 5.5.9 to 5.5.15 >>> Jetty from 5.1.9 to 5.1.10 >>> stax from 1.1.1-dev to 1.1.2 >>> Tomcat 5.5.9 to 5.5.15 >>> tranql from1.2.1 to 1.3-SNAPSHOT >>> tranql-connector from 1.1 to 1.2-SNAPSHOT >>> >>> Keep 'em coming. >>> >>> Matt >>> >>> Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from >> 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > Here are the packages I'm recommending for 1.1. If I missed one > please chime in. > > Axis from 1.4-356167 to 1.4 > jasper from 5.5.9 to 5.5.15 > Jetty from 5.1.9 to 5.1.10 > stax from 1.1.1-dev to 1.1.2 > tranql from1.2.1 to 1.3-SNAPSHOT > tranql-connector from 1.1 to 1.2-SNAPSHOT > > This is the list so far...I've updated > > http://opensource.atlassian.com/confluence/oss/display/
Re: 1.1 Package Upgrade List
Hi Matt, Moving the M2 conversion work from the trunk to 1.1 should not be disruptive. It would have the following changes 1) add pom.xmls in all modules 2) add a few ant files in some modules 3) change *Test.java files in quite a few modules. I have no strong objections to it except that I'm afraid it might pull folks off of 1.1 while trying to do this. Cheers Prasad. On 5/11/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: I'd defer to Jacek to do the merging since he's familiar with it. If he's not available then I'd be happy to take a patch from you :) Also, if anyone has any objections re: getting this done then hollar now. anita kulshreshtha wrote: > > --- Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> Since the M2 conversion is independent of 1.1 what does the community >> think about starting that >> merge into 1.1 now? I think it would allow us to become more >> productive on 1.2 since the work would >> already be in place. For those working on the M2 conversion what do >> you think about starting that >> work and do you think we can do it without impacting 1.1? >We can safely transfer all the work from 1.2 to 1.1 without > impacting anything. What is the best way to do this? > > Thanks > Anita > >> anita kulshreshtha wrote: >>> All work related to M2 was halted until the trunk was merged. >> M2 >>> packaging plugin would require transferring all M2 work to 1.1. I >> do >>> not think there are any plans to do it before the merge or at least >> the >>> 1.1. release. I think using Maven1 will be best at this time. Let's >>> hear from Jacek.. >>> >>> Thanks >>> Anita >>> >>> --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: >>> I haven't seen any geronimo plugin for m2 in head. That whould be very usefull, especially because Geronimo plugins >> have to be in a m2 layout, but the only tools to create a car is a m1 >> plugin. Any idea ? Cheers, Guillaume Nodet Aaron Mulder wrote: > I'd rather handle the ApacheDS integration separately from the >> 1.1 > release. Fortunately, the plugins work with the Maven 2 repository, > so that issue should be easier. > > The main question is how to do the build and packaging. If the >> API is > unchanged, we can build our integration module using our Maven 1 > packaging plugin against ADS 0.9.2 and just have it apply the >> 1.0.x > JARs at installation time. If the API is different, it may make the > most sense to try to split out our directory integration and do >> the > build and packaging under Maven 2 (I'm assuming that Geronimo >> HEAD has > a Maven 2 packaging plugin, but if not, I guess we can work on one). > Thanks, >Aaron > > On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > >> ApacheDS0.9.2 to 1.0-RC2 ? >> I have a patch to port the Geronimo part to 1.0-RC2. However, >> currently ADS 1.0 jars propagated to maven2 repo only. >> >> 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: >>> Consolidated list so far is: >>> >>> Axis from 1.4-356167 to 1.4 >>> commons-fileupload 1.1-dev to 1.1 >>> jasper from 5.5.9 to 5.5.15 >>> Jetty from 5.1.9 to 5.1.10 >>> stax from 1.1.1-dev to 1.1.2 >>> Tomcat 5.5.9 to 5.5.15 >>> tranql from1.2.1 to 1.3-SNAPSHOT >>> tranql-connector from 1.1 to 1.2-SNAPSHOT >>> >>> Keep 'em coming. >>> >>> Matt >>> >>> Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from >> 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > Here are the packages I'm recommending for 1.1. If I missed one > please chime in. > > Axis from 1.4-356167 to 1.4 > jasper from 5.5.9 to 5.5.15 > Jetty from 5.1.9 to 5.1.10 > stax from 1.1.1-dev to 1.1.2 > tranql from1.2.1 to 1.3-SNAPSHOT > tranql-connector from 1.1 to 1.2-SNAPSHOT > > This is the list so far...I've updated > > http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > with this information. > > Was mentioned on the list: > Howl- Researching this >> -- >> Alexei Zakharov, >> Intel Middleware Produc
Re: 1.1 Package Upgrade List
I'd defer to Jacek to do the merging since he's familiar with it. If he's not available then I'd be happy to take a patch from you :) Also, if anyone has any objections re: getting this done then hollar now. anita kulshreshtha wrote: --- Matt Hogstrom <[EMAIL PROTECTED]> wrote: Since the M2 conversion is independent of 1.1 what does the community think about starting that merge into 1.1 now? I think it would allow us to become more productive on 1.2 since the work would already be in place. For those working on the M2 conversion what do you think about starting that work and do you think we can do it without impacting 1.1? We can safely transfer all the work from 1.2 to 1.1 without impacting anything. What is the best way to do this? Thanks Anita anita kulshreshtha wrote: All work related to M2 was halted until the trunk was merged. M2 packaging plugin would require transferring all M2 work to 1.1. I do not think there are any plans to do it before the merge or at least the 1.1. release. I think using Maven1 will be best at this time. Let's hear from Jacek.. Thanks Anita --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: I haven't seen any geronimo plugin for m2 in head. That whould be very usefull, especially because Geronimo plugins have to be in a m2 layout, but the only tools to create a car is a m1 plugin. Any idea ? Cheers, Guillaume Nodet Aaron Mulder wrote: I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: 1.1 Package Upgrade List
--- Matt Hogstrom <[EMAIL PROTECTED]> wrote: > Since the M2 conversion is independent of 1.1 what does the community > think about starting that > merge into 1.1 now? I think it would allow us to become more > productive on 1.2 since the work would > already be in place. For those working on the M2 conversion what do > you think about starting that > work and do you think we can do it without impacting 1.1? We can safely transfer all the work from 1.2 to 1.1 without impacting anything. What is the best way to do this? Thanks Anita > > anita kulshreshtha wrote: > > All work related to M2 was halted until the trunk was merged. > M2 > > packaging plugin would require transferring all M2 work to 1.1. I > do > > not think there are any plans to do it before the merge or at least > the > > 1.1. release. I think using Maven1 will be best at this time. Let's > > hear from Jacek.. > > > > Thanks > > Anita > > > > --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > >> I haven't seen any geronimo plugin for m2 in head. > >> That whould be very usefull, especially because Geronimo plugins > have > >> to > >> be in a m2 layout, but the only tools to create a car is a m1 > plugin. > >> Any idea ? > >> > >> Cheers, > >> Guillaume Nodet > >> > >> Aaron Mulder wrote: > >> > >>> I'd rather handle the ApacheDS integration separately from the > 1.1 > >>> release. Fortunately, the plugins work with the Maven 2 > >> repository, > >>> so that issue should be easier. > >>> > >>> The main question is how to do the build and packaging. If the > API > >> is > >>> unchanged, we can build our integration module using our Maven 1 > >>> packaging plugin against ADS 0.9.2 and just have it apply the > 1.0.x > >>> JARs at installation time. If the API is different, it may make > >> the > >>> most sense to try to split out our directory integration and do > the > >>> build and packaging under Maven 2 (I'm assuming that Geronimo > HEAD > >> has > >>> a Maven 2 packaging plugin, but if not, I guess we can work on > >> one). > >>> Thanks, > >>>Aaron > >>> > >>> On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > >>> > ApacheDS0.9.2 to 1.0-RC2 ? > I have a patch to port the Geronimo part to 1.0-RC2. However, > currently ADS 1.0 jars propagated to maven2 repo only. > > 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > > Consolidated list so far is: > > > > Axis from 1.4-356167 to 1.4 > > commons-fileupload 1.1-dev to 1.1 > > jasper from 5.5.9 to 5.5.15 > > Jetty from 5.1.9 to 5.1.10 > > stax from 1.1.1-dev to 1.1.2 > > Tomcat 5.5.9 to 5.5.15 > > tranql from1.2.1 to 1.3-SNAPSHOT > > tranql-connector from 1.1 to 1.2-SNAPSHOT > > > > Keep 'em coming. > > > > Matt > > > > Aaron Mulder wrote: > >> That issue has a great list. > >> > >> We definitely need to try updating commons-fileupload (from > 1.1-dev to > >> 1.1). I think there may even be a separate Jira for that. > >> But the > >> old one occasionally hangs, so it's definitely worth trying > >> the new > >> one. > >> > >> Thanks, > >>Aaron > >> > >> On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >>> Here are the packages I'm recommending for 1.1. If I missed > >> one > >>> please chime in. > >>> > >>> Axis from 1.4-356167 to 1.4 > >>> jasper from 5.5.9 to 5.5.15 > >>> Jetty from 5.1.9 to 5.1.10 > >>> stax from 1.1.1-dev to 1.1.2 > >>> tranql from1.2.1 to 1.3-SNAPSHOT > >>> tranql-connector from 1.1 to 1.2-SNAPSHOT > >>> > >>> This is the list so far...I've updated > >>> > > > http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > >>> with this information. > >>> > >>> Was mentioned on the list: > >>> Howl- Researching this > > -- > Alexei Zakharov, > Intel Middleware Product Division > > >>> > > > > > > __ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > > > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: 1.1 Package Upgrade List
Since the M2 conversion is independent of 1.1 what does the community think about starting that merge into 1.1 now? I think it would allow us to become more productive on 1.2 since the work would already be in place. For those working on the M2 conversion what do you think about starting that work and do you think we can do it without impacting 1.1? anita kulshreshtha wrote: All work related to M2 was halted until the trunk was merged. M2 packaging plugin would require transferring all M2 work to 1.1. I do not think there are any plans to do it before the merge or at least the 1.1. release. I think using Maven1 will be best at this time. Let's hear from Jacek.. Thanks Anita --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: I haven't seen any geronimo plugin for m2 in head. That whould be very usefull, especially because Geronimo plugins have to be in a m2 layout, but the only tools to create a car is a m1 plugin. Any idea ? Cheers, Guillaume Nodet Aaron Mulder wrote: I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: 1.1 Package Upgrade List
Let's address Directory in 1.2. Since its not core to CTS I think it would be pushing 1.1 out. It would be awesome to get this updated in 1.2 when we finally ship 1.1. Looking at the packages out there we are ut of date on several so one of the first things I'd like to do is get current on packages when we cut the new branch; Directory being one of them. Matt Alexei Zakharov wrote: FYI: ADS API has changed significantly since 0.9.2. 2006/5/10, Aaron Mulder <[EMAIL PROTECTED]>: I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > ApacheDS0.9.2 to 1.0-RC2 ? > I have a patch to port the Geronimo part to 1.0-RC2. However, > currently ADS 1.0 jars propagated to maven2 repo only. > > 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > > Consolidated list so far is: > > > > Axis from 1.4-356167 to 1.4 > > commons-fileupload 1.1-dev to 1.1 > > jasper from 5.5.9 to 5.5.15 > > Jetty from 5.1.9 to 5.1.10 > > stax from 1.1.1-dev to 1.1.2 > > Tomcat 5.5.9 to 5.5.15 > > tranql from1.2.1 to 1.3-SNAPSHOT > > tranql-connector from 1.1 to 1.2-SNAPSHOT > > > > Keep 'em coming. > > > > Matt > > > > Aaron Mulder wrote: > > > That issue has a great list. > > > > > > We definitely need to try updating commons-fileupload (from 1.1-dev to > > > 1.1). I think there may even be a separate Jira for that. But the > > > old one occasionally hangs, so it's definitely worth trying the new > > > one. > > > > > > Thanks, > > >Aaron > > > > > > On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > > >> Here are the packages I'm recommending for 1.1. If I missed one > > >> please chime in. > > >> > > >> Axis from 1.4-356167 to 1.4 > > >> jasper from 5.5.9 to 5.5.15 > > >> Jetty from 5.1.9 to 5.1.10 > > >> stax from 1.1.1-dev to 1.1.2 > > >> tranql from1.2.1 to 1.3-SNAPSHOT > > >> tranql-connector from 1.1 to 1.2-SNAPSHOT > > >> > > >> This is the list so far...I've updated > > >> http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > > >> > > >> with this information. > > >> > > >> Was mentioned on the list: > > >> Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division
Re: 1.1 Package Upgrade List
Gianny, TranQL 1.3 has several performance and feature fixes (thanks to you) that we've been planning on for 1.1. I didn't realize the changes to OpenEJB however. I'd like to get this release wrapped up the week after Java One if possible (end of the month). Can you guesstimate the potential impact? If its destabilizing then perhaps we should defer to G 1.2. What are your thoughts? Gianny Damour wrote: Kevan Miller wrote: On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload1.1-devto1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9to5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT We're already on Tomcat 5.5.15, but fine to keep it on the list. I assume the final tranql and tranql-connector versions will be 1.3 and 1.2. We'll use the SNAPSHOT versions until a new tranql release is published (which will happen before we ship 1.1...). As a matter of fact, an upgrade to TranQL 1.3 requires some code changes to OpenEJB (repackaging). Also, it would be nice to port dynamic queries from trunk to 1.1. If there is no objection, I propose to do that this week-end and ensure that this does not break the tck. Thanks, Gianny I'll start testing these versions once we clean up a few problems. --kevan
Re: 1.1 Package Upgrade List
Kevan Miller wrote: On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload1.1-devto1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9to5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT We're already on Tomcat 5.5.15, but fine to keep it on the list. I assume the final tranql and tranql-connector versions will be 1.3 and 1.2. We'll use the SNAPSHOT versions until a new tranql release is published (which will happen before we ship 1.1...). As a matter of fact, an upgrade to TranQL 1.3 requires some code changes to OpenEJB (repackaging). Also, it would be nice to port dynamic queries from trunk to 1.1. If there is no objection, I propose to do that this week-end and ensure that this does not break the tck. Thanks, Gianny I'll start testing these versions once we clean up a few problems. --kevan
Re: 1.1 Package Upgrade List
Comments inline... --- Aaron Mulder <[EMAIL PROTECTED]> wrote: > So my understanding of things is that we have the full set of G 1.1 > plugins for Maven 1, and it would be nice to also have at least a G > 1.1 packaging plugin for Maven 2 (though we'll need them all in due > course). > > For the Maven 1 plugin, it looks like we have some Jelly code and a > Java implementation class. > > For a Maven 2 plugin, I wonder if we could use the same (or a very > similar) Java class, and migrate the Jelly logic either into that > class or into some Ant code. I haven't done much plugin porting, but > superficially it doesn't seem like it should be that hard. These are the issues : 1. Maven1 allows use of properties in the dependency element, i.e. 2 . There are many such properties geronimo.reference, geronimo.dependency, geronimo.import etc being used. M2 does not allow properties! 2. The groupIds for basic configurations needed to do the packaging are of the form o.a.g.configs in M2. The new (M2 based) configuration store in 1.1. should be able to handle these. These ids have not been tried yet. Thanks Anita > > Thanks, > Aaron > > On 5/10/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > Plugins are quite independant of the build afaik (even if they are > used > > by the main build). > > They could be written for G 1.1 and updated for G 1.x and have > their > > lifecycle decorrelated from Geronimo. > > As they will be very useful for people creating plugins, I think it > > could be interesting to write them for 1.1 before of the m2 switch. > > Is there any beginning of implementation available somewhere ? > > > > Cheers, > > Guillaume Nodet > > > > > > anita kulshreshtha wrote: > > > > >All work related to M2 was halted until the trunk was merged. > M2 > > >packaging plugin would require transferring all M2 work to 1.1. I > do > > >not think there are any plans to do it before the merge or at > least the > > >1.1. release. I think using Maven1 will be best at this time. > Let's > > >hear from Jacek.. > > > > > >Thanks > > >Anita > > > > > >--- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > >>I haven't seen any geronimo plugin for m2 in head. > > >>That whould be very usefull, especially because Geronimo plugins > have > > >>to > > >>be in a m2 layout, but the only tools to create a car is a m1 > plugin. > > >>Any idea ? > > >> > > >>Cheers, > > >>Guillaume Nodet > > >> > > >>Aaron Mulder wrote: > > >> > > >> > > >> > > >>>I'd rather handle the ApacheDS integration separately from the > 1.1 > > >>>release. Fortunately, the plugins work with the Maven 2 > > >>> > > >>> > > >>repository, > > >> > > >> > > >>>so that issue should be easier. > > >>> > > >>>The main question is how to do the build and packaging. If the > API > > >>> > > >>> > > >>is > > >> > > >> > > >>>unchanged, we can build our integration module using our Maven 1 > > >>>packaging plugin against ADS 0.9.2 and just have it apply the > 1.0.x > > >>>JARs at installation time. If the API is different, it may make > > >>> > > >>> > > >>the > > >> > > >> > > >>>most sense to try to split out our directory integration and do > the > > >>>build and packaging under Maven 2 (I'm assuming that Geronimo > HEAD > > >>> > > >>> > > >>has > > >> > > >> > > >>>a Maven 2 packaging plugin, but if not, I guess we can work on > > >>> > > >>> > > >>one). > > >> > > >> > > >>>Thanks, > > >>> Aaron > > >>> > > >>>On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > >>> > > >>> > > >>> > > ApacheDS0.9.2 to 1.0-RC2 ? > > I have a patch to port the Geronimo part to 1.0-RC2. However, > > currently ADS 1.0 jars propagated to maven2 repo only. > > > > 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > > > > > > >Consolidated list so far is: > > > > > >Axis from 1.4-356167 to 1.4 > > >commons-fileupload 1.1-dev to 1.1 > > >jasper from 5.5.9 to 5.5.15 > > >Jetty from 5.1.9 to 5.1.10 > > >stax from 1.1.1-dev to 1.1.2 > > >Tomcat 5.5.9 to 5.5.15 > > >tranql from1.2.1 to 1.3-SNAPSHOT > > >tranql-connector from 1.1 to 1.2-SNAPSHOT > > > > > >Keep 'em coming. > > > > > >Matt > > > > > >Aaron Mulder wrote: > > > > > > > > >>That issue has a great list. > > >> > > >>We definitely need to try updating commons-fileupload (from > > >> > > >> > > 1.1-dev to > > > > > > >>1.1). I think there may even be a separate Jira for that. > > >> > > >> > > >>But the > > >> > > >> > > >>old one occasionally hangs, so it's definitely worth trying > > >> > > >> > > >>the new > > >> > > >> > > >>one. > > >> > > >>Thanks, > > >
Re: 1.1 Package Upgrade List
svn is still down... Thanks Anita --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Yes, please, upload your code. > I will try to update them for 1.1. > > Thanks, > Guillaume Nodet > > anita kulshreshtha wrote: > > >Comments inline.. > > > >--- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > > > > > >>Plugins are quite independant of the build afaik (even if they are > >>used > >>by the main build). > >>They could be written for G 1.1 and updated for G 1.x and have > their > >>lifecycle decorrelated from Geronimo. > >> > >> > > Usually they are and will be in the future... The change from > HEAD > >to 1.1 is so drastic that there was no point in continuing the > >development of packaging and other plugins in the HEAD. > > > > > >>As they will be very useful for people creating plugins, I think it > > >>could be interesting to write them for 1.1 before of the m2 switch. > >>Is there any beginning of implementation available somewhere ? > >> > >> > >I have some code for packaging plugin for 1.1 that compiles but > you > >would need M2 geronimo-* jars for that. There is no point using the > >HEAD for anything now. Please let me know if you want me upload a > patch > >to the jira. > > > >Thanks > >Anita > > > > > >>Cheers, > >>Guillaume Nodet > >> > >> > >>anita kulshreshtha wrote: > >> > >> > >> > >>> All work related to M2 was halted until the trunk was merged. > M2 > >>>packaging plugin would require transferring all M2 work to 1.1. I > do > >>>not think there are any plans to do it before the merge or at > least > >>> > >>> > >>the > >> > >> > >>>1.1. release. I think using Maven1 will be best at this time. > Let's > >>>hear from Jacek.. > >>> > >>>Thanks > >>>Anita > >>> > >>>--- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > >>> > >>> > I haven't seen any geronimo plugin for m2 in head. > That whould be very usefull, especially because Geronimo plugins > > > >>have > >> > >> > to > be in a m2 layout, but the only tools to create a car is a m1 > > > >>plugin. > >> > >> > Any idea ? > > Cheers, > Guillaume Nodet > > Aaron Mulder wrote: > > > > > > >I'd rather handle the ApacheDS integration separately from the > 1.1 > >release. Fortunately, the plugins work with the Maven 2 > > > > > > > > > repository, > > > > > >so that issue should be easier. > > > >The main question is how to do the build and packaging. If the > > > > > >>API > >> > >> > > > > > > > > > is > > > > > >unchanged, we can build our integration module using our Maven 1 > >packaging plugin against ADS 0.9.2 and just have it apply the > > > > > >>1.0.x > >> > >> > >JARs at installation time. If the API is different, it may make > > > > > > > > > the > > > > > >most sense to try to split out our directory integration and do > > > > > >>the > >> > >> > >build and packaging under Maven 2 (I'm assuming that Geronimo > HEAD > > > > > > > > > has > > > > > >a Maven 2 packaging plugin, but if not, I guess we can work on > > > > > > > > > one). > > > > > >Thanks, > > Aaron > > > >On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > >>ApacheDS0.9.2 to 1.0-RC2 ? > >>I have a patch to port the Geronimo part to 1.0-RC2. However, > >>currently ADS 1.0 jars propagated to maven2 repo only. > >> > >>2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > >> > >> > >> > >> > >>>Consolidated list so far is: > >>> > >>>Axis from 1.4-356167 to 1.4 > >>>commons-fileupload 1.1-dev to 1.1 > >>>jasper from 5.5.9 to 5.5.15 > >>>Jetty from 5.1.9 to 5.1.10 > >>>stax from 1.1.1-dev to 1.1.2 > >>>Tomcat 5.5.9 to 5.5.15 > === message truncated === __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: 1.1 Package Upgrade List
Yes, please, upload your code. I will try to update them for 1.1. Thanks, Guillaume Nodet anita kulshreshtha wrote: Comments inline.. --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: Plugins are quite independant of the build afaik (even if they are used by the main build). They could be written for G 1.1 and updated for G 1.x and have their lifecycle decorrelated from Geronimo. Usually they are and will be in the future... The change from HEAD to 1.1 is so drastic that there was no point in continuing the development of packaging and other plugins in the HEAD. As they will be very useful for people creating plugins, I think it could be interesting to write them for 1.1 before of the m2 switch. Is there any beginning of implementation available somewhere ? I have some code for packaging plugin for 1.1 that compiles but you would need M2 geronimo-* jars for that. There is no point using the HEAD for anything now. Please let me know if you want me upload a patch to the jira. Thanks Anita Cheers, Guillaume Nodet anita kulshreshtha wrote: All work related to M2 was halted until the trunk was merged. M2 packaging plugin would require transferring all M2 work to 1.1. I do not think there are any plans to do it before the merge or at least the 1.1. release. I think using Maven1 will be best at this time. Let's hear from Jacek.. Thanks Anita --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: I haven't seen any geronimo plugin for m2 in head. That whould be very usefull, especially because Geronimo plugins have to be in a m2 layout, but the only tools to create a car is a m1 plugin. Any idea ? Cheers, Guillaume Nodet Aaron Mulder wrote: I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: 1.1 Package Upgrade List
Comments inline.. --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Plugins are quite independant of the build afaik (even if they are > used > by the main build). > They could be written for G 1.1 and updated for G 1.x and have their > lifecycle decorrelated from Geronimo. Usually they are and will be in the future... The change from HEAD to 1.1 is so drastic that there was no point in continuing the development of packaging and other plugins in the HEAD. > As they will be very useful for people creating plugins, I think it > could be interesting to write them for 1.1 before of the m2 switch. > Is there any beginning of implementation available somewhere ? I have some code for packaging plugin for 1.1 that compiles but you would need M2 geronimo-* jars for that. There is no point using the HEAD for anything now. Please let me know if you want me upload a patch to the jira. Thanks Anita > > Cheers, > Guillaume Nodet > > > anita kulshreshtha wrote: > > >All work related to M2 was halted until the trunk was merged. M2 > >packaging plugin would require transferring all M2 work to 1.1. I do > >not think there are any plans to do it before the merge or at least > the > >1.1. release. I think using Maven1 will be best at this time. Let's > >hear from Jacek.. > > > >Thanks > >Anita > > > >--- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > > > > > >>I haven't seen any geronimo plugin for m2 in head. > >>That whould be very usefull, especially because Geronimo plugins > have > >>to > >>be in a m2 layout, but the only tools to create a car is a m1 > plugin. > >>Any idea ? > >> > >>Cheers, > >>Guillaume Nodet > >> > >>Aaron Mulder wrote: > >> > >> > >> > >>>I'd rather handle the ApacheDS integration separately from the 1.1 > >>>release. Fortunately, the plugins work with the Maven 2 > >>> > >>> > >>repository, > >> > >> > >>>so that issue should be easier. > >>> > >>>The main question is how to do the build and packaging. If the > API > >>> > >>> > >>is > >> > >> > >>>unchanged, we can build our integration module using our Maven 1 > >>>packaging plugin against ADS 0.9.2 and just have it apply the > 1.0.x > >>>JARs at installation time. If the API is different, it may make > >>> > >>> > >>the > >> > >> > >>>most sense to try to split out our directory integration and do > the > >>>build and packaging under Maven 2 (I'm assuming that Geronimo HEAD > >>> > >>> > >>has > >> > >> > >>>a Maven 2 packaging plugin, but if not, I guess we can work on > >>> > >>> > >>one). > >> > >> > >>>Thanks, > >>> Aaron > >>> > >>>On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > ApacheDS0.9.2 to 1.0-RC2 ? > I have a patch to port the Geronimo part to 1.0-RC2. However, > currently ADS 1.0 jars propagated to maven2 repo only. > > 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > > > >Consolidated list so far is: > > > >Axis from 1.4-356167 to 1.4 > >commons-fileupload 1.1-dev to 1.1 > >jasper from 5.5.9 to 5.5.15 > >Jetty from 5.1.9 to 5.1.10 > >stax from 1.1.1-dev to 1.1.2 > >Tomcat 5.5.9 to 5.5.15 > >tranql from1.2.1 to 1.3-SNAPSHOT > >tranql-connector from 1.1 to 1.2-SNAPSHOT > > > >Keep 'em coming. > > > >Matt > > > >Aaron Mulder wrote: > > > > > >>That issue has a great list. > >> > >>We definitely need to try updating commons-fileupload (from > >> > >> > 1.1-dev to > > > >>1.1). I think there may even be a separate Jira for that. > >> > >> > >>But the > >> > >> > >>old one occasionally hangs, so it's definitely worth trying > >> > >> > >>the new > >> > >> > >>one. > >> > >>Thanks, > >> Aaron > >> > >>On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> > >> > >>>Here are the packages I'm recommending for 1.1. If I missed > >>> > >>> > >>one > >> > >> > >>>please chime in. > >>> > >>>Axis from 1.4-356167 to 1.4 > >>>jasper from 5.5.9 to 5.5.15 > >>>Jetty from 5.1.9 to 5.1.10 > >>>stax from 1.1.1-dev to 1.1.2 > >>>tranql from1.2.1 to 1.3-SNAPSHOT > >>>tranql-connector from 1.1 to 1.2-SNAPSHOT > >>> > >>>This is the list so far...I've updated > >>> > >>> > >>> > >http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > > > > > >>>with this information. > >>
Re: 1.1 Package Upgrade List
So my understanding of things is that we have the full set of G 1.1 plugins for Maven 1, and it would be nice to also have at least a G 1.1 packaging plugin for Maven 2 (though we'll need them all in due course). For the Maven 1 plugin, it looks like we have some Jelly code and a Java implementation class. For a Maven 2 plugin, I wonder if we could use the same (or a very similar) Java class, and migrate the Jelly logic either into that class or into some Ant code. I haven't done much plugin porting, but superficially it doesn't seem like it should be that hard. Thanks, Aaron On 5/10/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: Plugins are quite independant of the build afaik (even if they are used by the main build). They could be written for G 1.1 and updated for G 1.x and have their lifecycle decorrelated from Geronimo. As they will be very useful for people creating plugins, I think it could be interesting to write them for 1.1 before of the m2 switch. Is there any beginning of implementation available somewhere ? Cheers, Guillaume Nodet anita kulshreshtha wrote: >All work related to M2 was halted until the trunk was merged. M2 >packaging plugin would require transferring all M2 work to 1.1. I do >not think there are any plans to do it before the merge or at least the >1.1. release. I think using Maven1 will be best at this time. Let's >hear from Jacek.. > >Thanks >Anita > >--- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > >>I haven't seen any geronimo plugin for m2 in head. >>That whould be very usefull, especially because Geronimo plugins have >>to >>be in a m2 layout, but the only tools to create a car is a m1 plugin. >>Any idea ? >> >>Cheers, >>Guillaume Nodet >> >>Aaron Mulder wrote: >> >> >> >>>I'd rather handle the ApacheDS integration separately from the 1.1 >>>release. Fortunately, the plugins work with the Maven 2 >>> >>> >>repository, >> >> >>>so that issue should be easier. >>> >>>The main question is how to do the build and packaging. If the API >>> >>> >>is >> >> >>>unchanged, we can build our integration module using our Maven 1 >>>packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x >>>JARs at installation time. If the API is different, it may make >>> >>> >>the >> >> >>>most sense to try to split out our directory integration and do the >>>build and packaging under Maven 2 (I'm assuming that Geronimo HEAD >>> >>> >>has >> >> >>>a Maven 2 packaging plugin, but if not, I guess we can work on >>> >>> >>one). >> >> >>>Thanks, >>> Aaron >>> >>>On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: >>> >>> >>> ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: >Consolidated list so far is: > >Axis from 1.4-356167 to 1.4 >commons-fileupload 1.1-dev to 1.1 >jasper from 5.5.9 to 5.5.15 >Jetty from 5.1.9 to 5.1.10 >stax from 1.1.1-dev to 1.1.2 >Tomcat 5.5.9 to 5.5.15 >tranql from1.2.1 to 1.3-SNAPSHOT >tranql-connector from 1.1 to 1.2-SNAPSHOT > >Keep 'em coming. > >Matt > >Aaron Mulder wrote: > > >>That issue has a great list. >> >>We definitely need to try updating commons-fileupload (from >> >> 1.1-dev to >>1.1). I think there may even be a separate Jira for that. >> >> >>But the >> >> >>old one occasionally hangs, so it's definitely worth trying >> >> >>the new >> >> >>one. >> >>Thanks, >> Aaron >> >>On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: >> >> >>>Here are the packages I'm recommending for 1.1. If I missed >>> >>> >>one >> >> >>>please chime in. >>> >>>Axis from 1.4-356167 to 1.4 >>>jasper from 5.5.9 to 5.5.15 >>>Jetty from 5.1.9 to 5.1.10 >>>stax from 1.1.1-dev to 1.1.2 >>>tranql from1.2.1 to 1.3-SNAPSHOT >>>tranql-connector from 1.1 to 1.2-SNAPSHOT >>> >>>This is the list so far...I've updated >>> >>> >>> >http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > > >>>with this information. >>> >>>Was mentioned on the list: >>>Howl- Researching this >>> >>> -- Alexei Zakharov, Intel Middleware Product Division >>> >>> > > >__ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com > > > >
Re: 1.1 Package Upgrade List
Plugins are quite independant of the build afaik (even if they are used by the main build). They could be written for G 1.1 and updated for G 1.x and have their lifecycle decorrelated from Geronimo. As they will be very useful for people creating plugins, I think it could be interesting to write them for 1.1 before of the m2 switch. Is there any beginning of implementation available somewhere ? Cheers, Guillaume Nodet anita kulshreshtha wrote: All work related to M2 was halted until the trunk was merged. M2 packaging plugin would require transferring all M2 work to 1.1. I do not think there are any plans to do it before the merge or at least the 1.1. release. I think using Maven1 will be best at this time. Let's hear from Jacek.. Thanks Anita --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: I haven't seen any geronimo plugin for m2 in head. That whould be very usefull, especially because Geronimo plugins have to be in a m2 layout, but the only tools to create a car is a m1 plugin. Any idea ? Cheers, Guillaume Nodet Aaron Mulder wrote: I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: 1.1 Package Upgrade List
All work related to M2 was halted until the trunk was merged. M2 packaging plugin would require transferring all M2 work to 1.1. I do not think there are any plans to do it before the merge or at least the 1.1. release. I think using Maven1 will be best at this time. Let's hear from Jacek.. Thanks Anita --- Guillaume Nodet <[EMAIL PROTECTED]> wrote: > I haven't seen any geronimo plugin for m2 in head. > That whould be very usefull, especially because Geronimo plugins have > to > be in a m2 layout, but the only tools to create a car is a m1 plugin. > Any idea ? > > Cheers, > Guillaume Nodet > > Aaron Mulder wrote: > > > I'd rather handle the ApacheDS integration separately from the 1.1 > > release. Fortunately, the plugins work with the Maven 2 > repository, > > so that issue should be easier. > > > > The main question is how to do the build and packaging. If the API > is > > unchanged, we can build our integration module using our Maven 1 > > packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x > > JARs at installation time. If the API is different, it may make > the > > most sense to try to split out our directory integration and do the > > build and packaging under Maven 2 (I'm assuming that Geronimo HEAD > has > > a Maven 2 packaging plugin, but if not, I guess we can work on > one). > > > > Thanks, > >Aaron > > > > On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > > >> ApacheDS0.9.2 to 1.0-RC2 ? > >> I have a patch to port the Geronimo part to 1.0-RC2. However, > >> currently ADS 1.0 jars propagated to maven2 repo only. > >> > >> 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > >> > Consolidated list so far is: > >> > > >> > Axis from 1.4-356167 to 1.4 > >> > commons-fileupload 1.1-dev to 1.1 > >> > jasper from 5.5.9 to 5.5.15 > >> > Jetty from 5.1.9 to 5.1.10 > >> > stax from 1.1.1-dev to 1.1.2 > >> > Tomcat 5.5.9 to 5.5.15 > >> > tranql from1.2.1 to 1.3-SNAPSHOT > >> > tranql-connector from 1.1 to 1.2-SNAPSHOT > >> > > >> > Keep 'em coming. > >> > > >> > Matt > >> > > >> > Aaron Mulder wrote: > >> > > That issue has a great list. > >> > > > >> > > We definitely need to try updating commons-fileupload (from > >> 1.1-dev to > >> > > 1.1). I think there may even be a separate Jira for that. > But the > >> > > old one occasionally hangs, so it's definitely worth trying > the new > >> > > one. > >> > > > >> > > Thanks, > >> > >Aaron > >> > > > >> > > On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> > >> Here are the packages I'm recommending for 1.1. If I missed > one > >> > >> please chime in. > >> > >> > >> > >> Axis from 1.4-356167 to 1.4 > >> > >> jasper from 5.5.9 to 5.5.15 > >> > >> Jetty from 5.1.9 to 5.1.10 > >> > >> stax from 1.1.1-dev to 1.1.2 > >> > >> tranql from1.2.1 to 1.3-SNAPSHOT > >> > >> tranql-connector from 1.1 to 1.2-SNAPSHOT > >> > >> > >> > >> This is the list so far...I've updated > >> > >> > >> > http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > > >> > >> > >> > >> > >> with this information. > >> > >> > >> > >> Was mentioned on the list: > >> > >> Howl- Researching this > >> > >> > >> -- > >> Alexei Zakharov, > >> Intel Middleware Product Division > >> > > > > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: 1.1 Package Upgrade List
FYI: ADS API has changed significantly since 0.9.2. 2006/5/10, Aaron Mulder <[EMAIL PROTECTED]>: I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > ApacheDS0.9.2 to 1.0-RC2 ? > I have a patch to port the Geronimo part to 1.0-RC2. However, > currently ADS 1.0 jars propagated to maven2 repo only. > > 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > > Consolidated list so far is: > > > > Axis from 1.4-356167 to 1.4 > > commons-fileupload 1.1-dev to 1.1 > > jasper from 5.5.9 to 5.5.15 > > Jetty from 5.1.9 to 5.1.10 > > stax from 1.1.1-dev to 1.1.2 > > Tomcat 5.5.9 to 5.5.15 > > tranql from1.2.1 to 1.3-SNAPSHOT > > tranql-connector from 1.1 to 1.2-SNAPSHOT > > > > Keep 'em coming. > > > > Matt > > > > Aaron Mulder wrote: > > > That issue has a great list. > > > > > > We definitely need to try updating commons-fileupload (from 1.1-dev to > > > 1.1). I think there may even be a separate Jira for that. But the > > > old one occasionally hangs, so it's definitely worth trying the new > > > one. > > > > > > Thanks, > > >Aaron > > > > > > On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > > >> Here are the packages I'm recommending for 1.1. If I missed one > > >> please chime in. > > >> > > >> Axis from 1.4-356167 to 1.4 > > >> jasper from 5.5.9 to 5.5.15 > > >> Jetty from 5.1.9 to 5.1.10 > > >> stax from 1.1.1-dev to 1.1.2 > > >> tranql from1.2.1 to 1.3-SNAPSHOT > > >> tranql-connector from 1.1 to 1.2-SNAPSHOT > > >> > > >> This is the list so far...I've updated > > >> http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > > >> > > >> with this information. > > >> > > >> Was mentioned on the list: > > >> Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division
Re: 1.1 Package Upgrade List
I haven't seen any geronimo plugin for m2 in head. That whould be very usefull, especially because Geronimo plugins have to be in a m2 layout, but the only tools to create a car is a m1 plugin. Any idea ? Cheers, Guillaume Nodet Aaron Mulder wrote: I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > Consolidated list so far is: > > Axis from 1.4-356167 to 1.4 > commons-fileupload 1.1-dev to 1.1 > jasper from 5.5.9 to 5.5.15 > Jetty from 5.1.9 to 5.1.10 > stax from 1.1.1-dev to 1.1.2 > Tomcat 5.5.9 to 5.5.15 > tranql from1.2.1 to 1.3-SNAPSHOT > tranql-connector from 1.1 to 1.2-SNAPSHOT > > Keep 'em coming. > > Matt > > Aaron Mulder wrote: > > That issue has a great list. > > > > We definitely need to try updating commons-fileupload (from 1.1-dev to > > 1.1). I think there may even be a separate Jira for that. But the > > old one occasionally hangs, so it's definitely worth trying the new > > one. > > > > Thanks, > >Aaron > > > > On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> Here are the packages I'm recommending for 1.1. If I missed one > >> please chime in. > >> > >> Axis from 1.4-356167 to 1.4 > >> jasper from 5.5.9 to 5.5.15 > >> Jetty from 5.1.9 to 5.1.10 > >> stax from 1.1.1-dev to 1.1.2 > >> tranql from1.2.1 to 1.3-SNAPSHOT > >> tranql-connector from 1.1 to 1.2-SNAPSHOT > >> > >> This is the list so far...I've updated > >> http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > >> > >> with this information. > >> > >> Was mentioned on the list: > >> Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division
Re: 1.1 Package Upgrade List
I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: > Consolidated list so far is: > > Axis from 1.4-356167 to 1.4 > commons-fileupload 1.1-dev to 1.1 > jasper from 5.5.9 to 5.5.15 > Jetty from 5.1.9 to 5.1.10 > stax from 1.1.1-dev to 1.1.2 > Tomcat 5.5.9 to 5.5.15 > tranql from1.2.1 to 1.3-SNAPSHOT > tranql-connector from 1.1 to 1.2-SNAPSHOT > > Keep 'em coming. > > Matt > > Aaron Mulder wrote: > > That issue has a great list. > > > > We definitely need to try updating commons-fileupload (from 1.1-dev to > > 1.1). I think there may even be a separate Jira for that. But the > > old one occasionally hangs, so it's definitely worth trying the new > > one. > > > > Thanks, > >Aaron > > > > On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > >> Here are the packages I'm recommending for 1.1. If I missed one > >> please chime in. > >> > >> Axis from 1.4-356167 to 1.4 > >> jasper from 5.5.9 to 5.5.15 > >> Jetty from 5.1.9 to 5.1.10 > >> stax from 1.1.1-dev to 1.1.2 > >> tranql from1.2.1 to 1.3-SNAPSHOT > >> tranql-connector from 1.1 to 1.2-SNAPSHOT > >> > >> This is the list so far...I've updated > >> http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > >> > >> with this information. > >> > >> Was mentioned on the list: > >> Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division
Re: 1.1 Package Upgrade List
ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT Keep 'em coming. Matt Aaron Mulder wrote: > That issue has a great list. > > We definitely need to try updating commons-fileupload (from 1.1-dev to > 1.1). I think there may even be a separate Jira for that. But the > old one occasionally hangs, so it's definitely worth trying the new > one. > > Thanks, >Aaron > > On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: >> Here are the packages I'm recommending for 1.1. If I missed one >> please chime in. >> >> Axis from 1.4-356167 to 1.4 >> jasper from 5.5.9 to 5.5.15 >> Jetty from 5.1.9 to 5.1.10 >> stax from 1.1.1-dev to 1.1.2 >> tranql from1.2.1 to 1.3-SNAPSHOT >> tranql-connector from 1.1 to 1.2-SNAPSHOT >> >> This is the list so far...I've updated >> http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking >> >> with this information. >> >> Was mentioned on the list: >> Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division
Re: 1.1 Package Upgrade List
Moving to Commons-Fileupload 1.1 also requires upgrading to commons-io 1.2. Also, why are we upgrading to STAX 1.1.1, when all we need is just the STAX API? -Donald David Jencks wrote: I've built locally using HOWL 1.0.1 and it seems to work fine with no geronimo changes. I think the main problem will be getting it onto a suitable maven repo: I haven't found it to be released anywhere. Is pushing it into a m2 repo sufficient, are jars auto-backported into m1? thanks david jencks On May 9, 2006, at 10:22 AM, Matt Hogstrom wrote: You are correct Kevan. Thanks Kevan Miller wrote: On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload1.1-devto1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9to5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT We're already on Tomcat 5.5.15, but fine to keep it on the list. I assume the final tranql and tranql-connector versions will be 1.3 and 1.2. We'll use the SNAPSHOT versions until a new tranql release is published (which will happen before we ship 1.1...). I'll start testing these versions once we clean up a few problems. --kevan Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1- dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/ Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this smime.p7s Description: S/MIME Cryptographic Signature
Re: 1.1 Package Upgrade List
I've built locally using HOWL 1.0.1 and it seems to work fine with no geronimo changes. I think the main problem will be getting it onto a suitable maven repo: I haven't found it to be released anywhere. Is pushing it into a m2 repo sufficient, are jars auto-backported into m1? thanks david jencks On May 9, 2006, at 10:22 AM, Matt Hogstrom wrote: You are correct Kevan. Thanks Kevan Miller wrote: On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload1.1-devto1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9to5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT We're already on Tomcat 5.5.15, but fine to keep it on the list. I assume the final tranql and tranql-connector versions will be 1.3 and 1.2. We'll use the SNAPSHOT versions until a new tranql release is published (which will happen before we ship 1.1...). I'll start testing these versions once we clean up a few problems. --kevan Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1- dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/ Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this
Re: 1.1 Package Upgrade List
You are correct Kevan. Thanks Kevan Miller wrote: On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload1.1-devto1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9to5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT We're already on Tomcat 5.5.15, but fine to keep it on the list. I assume the final tranql and tranql-connector versions will be 1.3 and 1.2. We'll use the SNAPSHOT versions until a new tranql release is published (which will happen before we ship 1.1...). I'll start testing these versions once we clean up a few problems. --kevan Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this
Re: 1.1 Package Upgrade List
On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT We're already on Tomcat 5.5.15, but fine to keep it on the list. I assume the final tranql and tranql-connector versions will be 1.3 and 1.2. We'll use the SNAPSHOT versions until a new tranql release is published (which will happen before we ship 1.1...). I'll start testing these versions once we clean up a few problems. --kevan Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1- dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/ Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this
Re: 1.1 Package Upgrade List
Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this
Re: 1.1 Package Upgrade List
That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this
Re: 1.1 Package Upgrade List
Chime! TC - 5.5.15 Matt Hogstrom wrote: > Here are the packages I'm recommending for 1.1. If I missed one please > chime in. > > Axis from 1.4-356167to 1.4 > jasper from 5.5.9to5.5.15 > Jetty from5.1.9to5.1.10 > stax from1.1.1-devto1.1.2 > tranqlfrom1.2.1to1.3-SNAPSHOT > tranql-connector from1.1to1.2-SNAPSHOT > > This is the list so far...I've updated > http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking > > with this information. > > Was mentioned on the list: > Howl- Researching this
1.1 Package Upgrade List
Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this
