Yes! That should be fine. For now we will take an on-demand approach anyway.
Edell. -----Original Message----- From: Rick McGuire [mailto:[EMAIL PROTECTED] Sent: 22 September 2006 14:36 To: Nolan, Edell Subject: Re: Yoko maven artifacts... Nolan, Edell wrote: > Hi, > > When you say frequently - do you mean once a week or would you require > it more than that. > Once a week would probably be fine. I'd hope we could also have an on-demand process as well in case there's a situation where coordinated changes between yoko and the consuming project (e.g., harmony or geronimo) are required. Rick > Hopefully we could automate some process to do this. > > Edell. > > > > > -----Original Message----- > From: Rick McGuire [mailto:[EMAIL PROTECTED] > Sent: 22 September 2006 14:25 > To: yoko-dev@incubator.apache.org > Subject: Re: Yoko maven artifacts... > > Nolan, Edell wrote: > >> Hi, >> >> Its only been done a few times. So we havn't got a process in place. >> Hopefully when we get milestone 1 out then we can have a formal place >> To pick up the distributions and when we update the distributions >> then >> > > >> maybe The snapshots could be updated at the sametime. >> >> I guess it depends on how much people want them updated. >> >> > I think since Alexey is working on Harmony integration, and I'm > working on adding it to Geronimo, my preference is for "frequently"! > > Rick > > >> Edell. >> >> -----Original Message----- >> From: Alexey Petrenko [mailto:[EMAIL PROTECTED] >> Sent: 22 September 2006 14:08 >> To: yoko-dev@incubator.apache.org; Mosur Ravi, Balaji >> Subject: Yoko maven artifacts... >> >> Guys, >> >> How often do we post Yoko maven artifacts on >> http://people.apache.org/maven-snapshot-repository/? And who is >> responsible for that? >> >> Is there any time estimations on updated artifacts? >> >> I'm going to update Apache Harmony to use yoko-rmi jar. And getting >> it >> > > >> from the well-known place will be the best option. >> >> Thanks in advance. >> >> SY, Alexey >> >> -- >> Alexey A. Petrenko >> Intel Middleware Products Division >> >> >> >> >> > > > > >
