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: >> >>>>> >> >>>>>> ApacheDS 0.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 from 1.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 from 1.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 >> > >> > >> > >> > >
