You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Joe Bohn <jo...@earthlink.net> on 2008/11/12 00:04:02 UTC
2.2 (trunk) bucket-o-snapshots
It has been mentioned several times that we should be looking to release
Geronimo 2.2 before the end of the year (preferrably mid-December).
Before we can consider a release there are a large number of snapshots
that need to be removed/replaced in our project. Can anybody shed any
light on these (or others that I may have missed)?
OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
October. However, the trunk version was never updated and some
additional changes have been included. Recent changes in Geronimo trunk
now require this snapshot that is actually newer than the 3.1 release.
IMO we should revert the trunk change and attempt to work with the
released OpenEJB 3.1.
Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
correctly we need to get an Axis2 release before we can consider a
Geronimo 2.2 release. Does anybody know how close we are to getting an
Axis2 release?
Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
required by Axis2 ... so if Axis2 is released then they will have to get
Axiom released as well (and we can pick up the released version).
-xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it
must be)? In branches/2.1 we're still using 3.3. It looks like the
latest released version is 3.4.3. I'll give that a shot if I don't hear
from anybody that we really need 3.5.
-wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it must
be)? In branches/2.1 we're using 2.0. What function requires
2.1-SNAPSHOT and is can somebody directly involved with wadi provide an
estimate on when this might be released?
-geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point
where we can release this spec or do we need to wait until we verify tck?
- geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we can
release this spec or do we need to wait until we verify tck?
- geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where we
can release this spec or do we need to wait until we verify tck?
- geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How
close is this to being able to be released?
- geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to being
able to be released?
- XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is also
related to Axis2 dependencies and will have to be resolved by Axis2 as
they release.
- woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to
be resolved for an Axis2 release so we will pull in whatever they require.
- selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled
this in trying to resolve the FF3 issues. It's not clear to me if we
would have to remove this SNAPSHOT prior to a release but I think it
would be best to ensure that the tagged release can always be built and
run with tests - therefore I think we should remove it. Any other opinions?
- jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know?
We should remove it.
- jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this was
updated either. In branches/2.1 we updated the maven plugin (above) but
not the compiler but in trunk both were updated to the alpha-2-SNAPSHOT.
Anybody know why?
- ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the new
legal file processing. Is there a released version we can use instead
of the SNAPSHOT or do we need to get a release here are well?
Joe
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Joe Bohn <jo...@earthlink.net>.
Updated information below on our snapshots (and some more
questions/requests).
Joe Bohn wrote:
> It has been mentioned several times that we should be looking to release
> Geronimo 2.2 before the end of the year (preferrably mid-December).
>
>
> Before we can consider a release there are a large number of snapshots
> that need to be removed/replaced in our project. Can anybody shed any
> light on these (or others that I may have missed)?
>
>
> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
> October. However, the trunk version was never updated and some
> additional changes have been included. Recent changes in Geronimo trunk
> now require this snapshot that is actually newer than the 3.1 release.
> IMO we should revert the trunk change and attempt to work with the
> released OpenEJB 3.1.
- udpated to OpenEJB 3.1.1-SNAPSHOT. Once it looks like we have clean
tck runs with OpenEJB we need to push for a release.
>
> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
> correctly we need to get an Axis2 release before we can consider a
> Geronimo 2.2 release. Does anybody know how close we are to getting an
> Axis2 release?
- Jarek is looking into this and related dependencies
>
> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
> required by Axis2 ... so if Axis2 is released then they will have to get
> Axiom released as well (and we can pick up the released version).
- related to Axis2
>
> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it
> must be)? In branches/2.1 we're still using 3.3. It looks like the
> latest released version is 3.4.3. I'll give that a shot if I don't hear
> from anybody that we really need 3.5.
David Jencks indicated it was required that we use 3.5. Can somebody
with commit rights on xBean start to push for a release?
>
> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it must
> be)? In branches/2.1 we're using 2.0. What function requires
> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide an
> estimate on when this might be released?
- Gianny is going to start a release around 11/29/08.
>
> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point
> where we can release this spec or do we need to wait until we verify tck?
- David Jencks indicated that we should be able to release a 1.0-EA
version prior to the spec being final. Should I start looking into that
release David or are you planning to do it?
>
> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we can
> release this spec or do we need to wait until we verify tck?
- David Jencks indicated that the spec was complete but we don't yet
have a tck. Have you already asked Geir for one or should I?
>
> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where we
> can release this spec or do we need to wait until we verify tck?
- Another question for David Jencks ... should I start looking into a
release of this?
>
> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How
> close is this to being able to be released?
- and another for David Jencks ... are you closer to a decision on if
this is ready for a release?
>
> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to being
> able to be released?
- I think Jarek is looking into releasing this as something like 1.0-EA
given that it is not yet final.
>
> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is also
> related to Axis2 dependencies and will have to be resolved by Axis2 as
> they release.
- related to Axis2
>
> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to
> be resolved for an Axis2 release so we will pull in whatever they require.
- related to Axis2
>
> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled
> this in trying to resolve the FF3 issues. It's not clear to me if we
> would have to remove this SNAPSHOT prior to a release but I think it
> would be best to ensure that the tagged release can always be built and
> run with tests - therefore I think we should remove it. Any other
> opinions?
- I'm looking into this still
>
> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
> updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know? We
> should remove it.
- I moved us to 2.0-alpha-2
>
> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this was
> updated either. In branches/2.1 we updated the maven plugin (above) but
> not the compiler but in trunk both were updated to the alpha-2-SNAPSHOT.
> Anybody know why?
- I moved us to 2.0-alpha-2
>
> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the new
> legal file processing. Is there a released version we can use instead
> of the SNAPSHOT or do we need to get a release here are well?
- I moved us to 1.0-alpha-1
>
>
> Joe
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Joe Bohn <jo...@earthlink.net>.
Jarek Gawor wrote:
> On Tue, Dec 2, 2008 at 11:53 AM, Joe Bohn <jo...@earthlink.net> wrote:
>> Hi Jarek,
>>
>> It looks like the Axis2 1.5 release didn't happen yet. Is there a new
>> target?
>
> No, not that I can see but there is some progress on the dependencies.
> Looks like we don't need a new release of Neethi and XmlSchema 1.4.3
> is being voted on right now.
>
>> Also, my offer still stands to help with the concurrent spec release if you
>> want. Let me know.
>
> Yes, thanks! I can't decide if the version should be named 1.0-EA or
> if the spec/module name should be renamed to have EA in it since there
> is no 1.0 spec yet. Any opinions on that?
I could go along with either choice but it seems a bit more correct tome
if we have EA associated with the spec version rather than our version
since it is the spec that is not yet complete. However, I can see
issues with that as well (might be confusing and our users would have to
change the artifact name rather than just the version when it is final).
It looks like David has been including EA in our version number for the
servlet spec and I'm a big fan of consistency ... so perhaps we should
go with that.
David Jencks, - Are you planning to stick with your 1.0-EA version or
were you thinking of changing it? I think we should be consistent.
Joe
Re: 2.2 (trunk) bucket-o-snapshots
Posted by David Jencks <da...@yahoo.com>.
On Dec 3, 2008, at 8:29 AM, Jarek Gawor wrote:
> On Tue, Dec 2, 2008 at 11:53 AM, Joe Bohn <jo...@earthlink.net>
> wrote:
>> Hi Jarek,
>>
>> It looks like the Axis2 1.5 release didn't happen yet. Is there a
>> new
>> target?
>
> No, not that I can see but there is some progress on the dependencies.
> Looks like we don't need a new release of Neethi and XmlSchema 1.4.3
> is being voted on right now.
>
>> Also, my offer still stands to help with the concurrent spec
>> release if you
>> want. Let me know.
>
> Yes, thanks! I can't decide if the version should be named 1.0-EA or
> if the spec/module name should be renamed to have EA in it since there
> is no 1.0 spec yet. Any opinions on that?
I strongly recommend putting the EA in the version. IIUC you expect
this code to be the 1.0 spec release not the 1.0-EA spec release.
This is what I've done with servlet 3, connector 1.6, and jpa 2.0.
thanks
david jencks
>
>
> Jarek
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Jarek Gawor <jg...@gmail.com>.
On Tue, Dec 2, 2008 at 11:53 AM, Joe Bohn <jo...@earthlink.net> wrote:
> Hi Jarek,
>
> It looks like the Axis2 1.5 release didn't happen yet. Is there a new
> target?
No, not that I can see but there is some progress on the dependencies.
Looks like we don't need a new release of Neethi and XmlSchema 1.4.3
is being voted on right now.
> Also, my offer still stands to help with the concurrent spec release if you
> want. Let me know.
Yes, thanks! I can't decide if the version should be named 1.0-EA or
if the spec/module name should be renamed to have EA in it since there
is no 1.0 spec yet. Any opinions on that?
Jarek
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Joe Bohn <jo...@earthlink.net>.
Hi Jarek,
It looks like the Axis2 1.5 release didn't happen yet. Is there a new
target?
Also, my offer still stands to help with the concurrent spec release if
you want. Let me know.
Thanks,
Joe
Jarek Gawor wrote:
> Axiom, XmlSchema, and Woden are all dependencies of Axis2. There is a
> plan for Axis2 release at the end of this month but I'm not sure if
> it's going to happen with all these dependencies. So getting Axis2
> release might be an issue to us.
>
> As to geronimo-concurrent_1.0_spec 1.0-SNAPSHOT, we can get that
> released now. I have no pending updates for it.
>
> Jarek
>
> On Tue, Nov 11, 2008 at 6:04 PM, Joe Bohn <jo...@earthlink.net> wrote:
>> It has been mentioned several times that we should be looking to release
>> Geronimo 2.2 before the end of the year (preferrably mid-December).
>>
>>
>> Before we can consider a release there are a large number of snapshots that
>> need to be removed/replaced in our project. Can anybody shed any light on
>> these (or others that I may have missed)?
>>
>>
>> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late October.
>> However, the trunk version was never updated and some additional changes
>> have been included. Recent changes in Geronimo trunk now require this
>> snapshot that is actually newer than the 3.1 release. IMO we should revert
>> the trunk change and attempt to work with the released OpenEJB 3.1.
>>
>> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC correctly
>> we need to get an Axis2 release before we can consider a Geronimo 2.2
>> release. Does anybody know how close we are to getting an Axis2 release?
>>
>> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is required by
>> Axis2 ... so if Axis2 is released then they will have to get Axiom released
>> as well (and we can pick up the released version).
>>
>> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it must
>> be)? In branches/2.1 we're still using 3.3. It looks like the latest
>> released version is 3.4.3. I'll give that a shot if I don't hear from
>> anybody that we really need 3.5.
>>
>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it must
>> be)? In branches/2.1 we're using 2.0. What function requires 2.1-SNAPSHOT
>> and is can somebody directly involved with wadi provide an estimate on when
>> this might be released?
>>
>> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point where
>> we can release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we can
>> release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where we can
>> release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How close
>> is this to being able to be released?
>>
>> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to being
>> able to be released?
>>
>> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is also
>> related to Axis2 dependencies and will have to be resolved by Axis2 as they
>> release.
>>
>> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to be
>> resolved for an Axis2 release so we will pull in whatever they require.
>>
>> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled this in
>> trying to resolve the FF3 issues. It's not clear to me if we would have to
>> remove this SNAPSHOT prior to a release but I think it would be best to
>> ensure that the tagged release can always be built and run with tests -
>> therefore I think we should remove it. Any other opinions?
>>
>> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is updated
>> (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know? We should
>> remove it.
>>
>> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this was
>> updated either. In branches/2.1 we updated the maven plugin (above) but not
>> the compiler but in trunk both were updated to the alpha-2-SNAPSHOT.
>> Anybody know why?
>>
>> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the new
>> legal file processing. Is there a released version we can use instead of
>> the SNAPSHOT or do we need to get a release here are well?
>>
>>
>> Joe
>>
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Joe Bohn <jo...@earthlink.net>.
Jarek,
Thanks for the information. I know that you are still spending a lot of
time on Axis2 so let me know if you want help getting the concurrent
spec out for vote.
If Axis2 and it's dependencies aren't released in time we may have to
consider a private build :-( (or a later release of 2.2).
Joe
Jarek Gawor wrote:
> Axiom, XmlSchema, and Woden are all dependencies of Axis2. There is a
> plan for Axis2 release at the end of this month but I'm not sure if
> it's going to happen with all these dependencies. So getting Axis2
> release might be an issue to us.
>
> As to geronimo-concurrent_1.0_spec 1.0-SNAPSHOT, we can get that
> released now. I have no pending updates for it.
>
> Jarek
>
> On Tue, Nov 11, 2008 at 6:04 PM, Joe Bohn <jo...@earthlink.net> wrote:
>> It has been mentioned several times that we should be looking to release
>> Geronimo 2.2 before the end of the year (preferrably mid-December).
>>
>>
>> Before we can consider a release there are a large number of snapshots that
>> need to be removed/replaced in our project. Can anybody shed any light on
>> these (or others that I may have missed)?
>>
>>
>> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late October.
>> However, the trunk version was never updated and some additional changes
>> have been included. Recent changes in Geronimo trunk now require this
>> snapshot that is actually newer than the 3.1 release. IMO we should revert
>> the trunk change and attempt to work with the released OpenEJB 3.1.
>>
>> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC correctly
>> we need to get an Axis2 release before we can consider a Geronimo 2.2
>> release. Does anybody know how close we are to getting an Axis2 release?
>>
>> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is required by
>> Axis2 ... so if Axis2 is released then they will have to get Axiom released
>> as well (and we can pick up the released version).
>>
>> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it must
>> be)? In branches/2.1 we're still using 3.3. It looks like the latest
>> released version is 3.4.3. I'll give that a shot if I don't hear from
>> anybody that we really need 3.5.
>>
>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it must
>> be)? In branches/2.1 we're using 2.0. What function requires 2.1-SNAPSHOT
>> and is can somebody directly involved with wadi provide an estimate on when
>> this might be released?
>>
>> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point where
>> we can release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we can
>> release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where we can
>> release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How close
>> is this to being able to be released?
>>
>> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to being
>> able to be released?
>>
>> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is also
>> related to Axis2 dependencies and will have to be resolved by Axis2 as they
>> release.
>>
>> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to be
>> resolved for an Axis2 release so we will pull in whatever they require.
>>
>> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled this in
>> trying to resolve the FF3 issues. It's not clear to me if we would have to
>> remove this SNAPSHOT prior to a release but I think it would be best to
>> ensure that the tagged release can always be built and run with tests -
>> therefore I think we should remove it. Any other opinions?
>>
>> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is updated
>> (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know? We should
>> remove it.
>>
>> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this was
>> updated either. In branches/2.1 we updated the maven plugin (above) but not
>> the compiler but in trunk both were updated to the alpha-2-SNAPSHOT.
>> Anybody know why?
>>
>> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the new
>> legal file processing. Is there a released version we can use instead of
>> the SNAPSHOT or do we need to get a release here are well?
>>
>>
>> Joe
>>
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Jarek Gawor <jg...@gmail.com>.
Axiom, XmlSchema, and Woden are all dependencies of Axis2. There is a
plan for Axis2 release at the end of this month but I'm not sure if
it's going to happen with all these dependencies. So getting Axis2
release might be an issue to us.
As to geronimo-concurrent_1.0_spec 1.0-SNAPSHOT, we can get that
released now. I have no pending updates for it.
Jarek
On Tue, Nov 11, 2008 at 6:04 PM, Joe Bohn <jo...@earthlink.net> wrote:
> It has been mentioned several times that we should be looking to release
> Geronimo 2.2 before the end of the year (preferrably mid-December).
>
>
> Before we can consider a release there are a large number of snapshots that
> need to be removed/replaced in our project. Can anybody shed any light on
> these (or others that I may have missed)?
>
>
> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late October.
> However, the trunk version was never updated and some additional changes
> have been included. Recent changes in Geronimo trunk now require this
> snapshot that is actually newer than the 3.1 release. IMO we should revert
> the trunk change and attempt to work with the released OpenEJB 3.1.
>
> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC correctly
> we need to get an Axis2 release before we can consider a Geronimo 2.2
> release. Does anybody know how close we are to getting an Axis2 release?
>
> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is required by
> Axis2 ... so if Axis2 is released then they will have to get Axiom released
> as well (and we can pick up the released version).
>
> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it must
> be)? In branches/2.1 we're still using 3.3. It looks like the latest
> released version is 3.4.3. I'll give that a shot if I don't hear from
> anybody that we really need 3.5.
>
> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it must
> be)? In branches/2.1 we're using 2.0. What function requires 2.1-SNAPSHOT
> and is can somebody directly involved with wadi provide an estimate on when
> this might be released?
>
> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point where
> we can release this spec or do we need to wait until we verify tck?
>
> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we can
> release this spec or do we need to wait until we verify tck?
>
> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where we can
> release this spec or do we need to wait until we verify tck?
>
> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How close
> is this to being able to be released?
>
> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to being
> able to be released?
>
> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is also
> related to Axis2 dependencies and will have to be resolved by Axis2 as they
> release.
>
> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to be
> resolved for an Axis2 release so we will pull in whatever they require.
>
> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled this in
> trying to resolve the FF3 issues. It's not clear to me if we would have to
> remove this SNAPSHOT prior to a release but I think it would be best to
> ensure that the tagged release can always be built and run with tests -
> therefore I think we should remove it. Any other opinions?
>
> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is updated
> (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know? We should
> remove it.
>
> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this was
> updated either. In branches/2.1 we updated the maven plugin (above) but not
> the compiler but in trunk both were updated to the alpha-2-SNAPSHOT.
> Anybody know why?
>
> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the new
> legal file processing. Is there a released version we can use instead of
> the SNAPSHOT or do we need to get a release here are well?
>
>
> Joe
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Joe Bohn <jo...@earthlink.net>.
Gianny Damour wrote:
> On 13/11/2008, at 5:13 AM, Joe Bohn wrote:
>
>> Gianny Damour wrote:
>>> On 12/11/2008, at 10:04 AM, Joe Bohn wrote:
>>>> It has been mentioned several times that we should be looking to
>>>> release Geronimo 2.2 before the end of the year (preferrably
>>>> mid-December).
>>>>
>>>>
>>>> Before we can consider a release there are a large number of
>>>> snapshots that need to be removed/replaced in our project. Can
>>>> anybody shed any light on these (or others that I may have missed)?
>>>>
>>>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
>>>> must be)? In branches/2.1 we're using 2.0. What function requires
>>>> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide
>>>> an estimate on when this might be released?
>>> I will release WADI 2.1 whenever a release version is required for
>>> Geronimo.
>>
>> Thanks Gianny. Is there any reason to avoid pursuing a release now?
>> Are you anticipating more changes from Geronimo or other projects
>> soon? Any snapshot dependencies that we can quickly remove will help
>> us more keenly focus on those that require a bit more effort.
>
> Well, I am working on and off on WADI cache, which will provide a
> distributed, replicated and transactional cache. Have a look here
>
> https://svn.codehaus.org/wadi/trunk/wadi/wadi-cache/src/test/java/org/codehaus/wadi/cache/demo/Main.java
>
>
> if you want to see a sample. Obviously, if people are interested to
> help, then please ping me.
>
>
> I understand where you are coming from. Rest assure that the cut of a
> WADI release is not a severe dependency for Geronimo 2.2. What do you
> think of me cutting a release end November, say the week-end of November
> 29th?
>
> Thanks,
> Gianny
Thanks for the information. The end of November is great! I'm just
trying to eliminate as many unknowns as possible. You have been very
responsive and helpful - much thanks!
Joe
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Gianny Damour <gi...@optusnet.com.au>.
On 13/11/2008, at 5:13 AM, Joe Bohn wrote:
> Gianny Damour wrote:
>> On 12/11/2008, at 10:04 AM, Joe Bohn wrote:
>>> It has been mentioned several times that we should be looking to
>>> release Geronimo 2.2 before the end of the year (preferrably mid-
>>> December).
>>>
>>>
>>> Before we can consider a release there are a large number of
>>> snapshots that need to be removed/replaced in our project. Can
>>> anybody shed any light on these (or others that I may have missed)?
>>>
>>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume
>>> it must be)? In branches/2.1 we're using 2.0. What function
>>> requires 2.1-SNAPSHOT and is can somebody directly involved with
>>> wadi provide an estimate on when this might be released?
>> I will release WADI 2.1 whenever a release version is required for
>> Geronimo.
>
> Thanks Gianny. Is there any reason to avoid pursuing a release
> now? Are you anticipating more changes from Geronimo or other
> projects soon? Any snapshot dependencies that we can quickly
> remove will help us more keenly focus on those that require a bit
> more effort.
Well, I am working on and off on WADI cache, which will provide a
distributed, replicated and transactional cache. Have a look here
https://svn.codehaus.org/wadi/trunk/wadi/wadi-cache/src/test/java/org/
codehaus/wadi/cache/demo/Main.java
if you want to see a sample. Obviously, if people are interested to
help, then please ping me.
I understand where you are coming from. Rest assure that the cut of a
WADI release is not a severe dependency for Geronimo 2.2. What do you
think of me cutting a release end November, say the week-end of
November 29th?
Thanks,
Gianny
>
> Thanks,
> Joe
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Joe Bohn <jo...@earthlink.net>.
Gianny Damour wrote:
> On 12/11/2008, at 10:04 AM, Joe Bohn wrote:
>
>> It has been mentioned several times that we should be looking to
>> release Geronimo 2.2 before the end of the year (preferrably
>> mid-December).
>>
>>
>> Before we can consider a release there are a large number of snapshots
>> that need to be removed/replaced in our project. Can anybody shed any
>> light on these (or others that I may have missed)?
>>
>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
>> must be)? In branches/2.1 we're using 2.0. What function requires
>> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide
>> an estimate on when this might be released?
>
>
> I will release WADI 2.1 whenever a release version is required for
> Geronimo.
Thanks Gianny. Is there any reason to avoid pursuing a release now?
Are you anticipating more changes from Geronimo or other projects soon?
Any snapshot dependencies that we can quickly remove will help us more
keenly focus on those that require a bit more effort.
Thanks,
Joe
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Gianny Damour <gi...@optusnet.com.au>.
On 12/11/2008, at 10:04 AM, Joe Bohn wrote:
> It has been mentioned several times that we should be looking to
> release Geronimo 2.2 before the end of the year (preferrably mid-
> December).
>
>
> Before we can consider a release there are a large number of
> snapshots that need to be removed/replaced in our project. Can
> anybody shed any light on these (or others that I may have missed)?
>
> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
> must be)? In branches/2.1 we're using 2.0. What function requires
> 2.1-SNAPSHOT and is can somebody directly involved with wadi
> provide an estimate on when this might be released?
I will release WADI 2.1 whenever a release version is required for
Geronimo.
Thanks,
Gianny
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Donald Woods <dw...@apache.org>.
and Rev724890
Donald Woods wrote:
> Removed duplicate xpp3/xpp3 depend and only include xpp3/xpp3_min now as
> of Rev724871.
>
>
> -Donald
>
> Donald Woods wrote:
>> We also have multiple versions of some depends getting pulled into the
>> assemblies right now, that needs to get fixed:
>>
>> commons-logging - 1.0.3 and 1.0.4
>> xpp3 and xpp3_min
>> org.apache.ws.commons.schema.XmlSchema - 1.4.2 and SNAPSHOT
>>
>>
>> Some new/questionable depends:
>> com.envoisolutions.sxc.sxc-jaxb and sxc-runtime
>> org.jvnet.staxex
>> quartz.quartz
>>
>> And backport-util-concurrent is still in the distro...
>>
>> Also, can we remove com/sun/xml/ws/jaxws-rt and jaxws-tools, now that
>> we are using CXF for wsgen?
>>
>>
>> -Donald
>>
>>
>> Joe Bohn wrote:
>>> It has been mentioned several times that we should be looking to
>>> release Geronimo 2.2 before the end of the year (preferrably
>>> mid-December).
>>>
>>>
>>> Before we can consider a release there are a large number of
>>> snapshots that need to be removed/replaced in our project. Can
>>> anybody shed any light on these (or others that I may have missed)?
>>>
>>>
>>> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
>>> October. However, the trunk version was never updated and some
>>> additional changes have been included. Recent changes in Geronimo
>>> trunk now require this snapshot that is actually newer than the 3.1
>>> release. IMO we should revert the trunk change and attempt to work
>>> with the released OpenEJB 3.1.
>>>
>>> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
>>> correctly we need to get an Axis2 release before we can consider a
>>> Geronimo 2.2 release. Does anybody know how close we are to getting
>>> an Axis2 release?
>>>
>>> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
>>> required by Axis2 ... so if Axis2 is released then they will have to
>>> get Axiom released as well (and we can pick up the released version).
>>>
>>> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it
>>> must be)? In branches/2.1 we're still using 3.3. It looks like the
>>> latest released version is 3.4.3. I'll give that a shot if I don't
>>> hear from anybody that we really need 3.5.
>>>
>>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
>>> must be)? In branches/2.1 we're using 2.0. What function requires
>>> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide
>>> an estimate on when this might be released?
>>>
>>> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point
>>> where we can release this spec or do we need to wait until we verify
>>> tck?
>>>
>>> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we
>>> can release this spec or do we need to wait until we verify tck?
>>>
>>> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where
>>> we can release this spec or do we need to wait until we verify tck?
>>>
>>> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component.
>>> How close is this to being able to be released?
>>>
>>> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to
>>> being able to be released?
>>>
>>> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is
>>> also related to Axis2 dependencies and will have to be resolved by
>>> Axis2 as they release.
>>>
>>> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have
>>> to be resolved for an Axis2 release so we will pull in whatever they
>>> require.
>>>
>>> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled
>>> this in trying to resolve the FF3 issues. It's not clear to me if we
>>> would have to remove this SNAPSHOT prior to a release but I think it
>>> would be best to ensure that the tagged release can always be built
>>> and run with tests - therefore I think we should remove it. Any
>>> other opinions?
>>>
>>> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
>>> updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know?
>>> We should remove it.
>>>
>>> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this
>>> was updated either. In branches/2.1 we updated the maven plugin
>>> (above) but not the compiler but in trunk both were updated to the
>>> alpha-2-SNAPSHOT. Anybody know why?
>>>
>>> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the
>>> new legal file processing. Is there a released version we can use
>>> instead of the SNAPSHOT or do we need to get a release here are well?
>>>
>>>
>>> Joe
>>>
>>
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Donald Woods <dw...@apache.org>.
Removed duplicate xpp3/xpp3 depend and only include xpp3/xpp3_min now as
of Rev724871.
-Donald
Donald Woods wrote:
> We also have multiple versions of some depends getting pulled into the
> assemblies right now, that needs to get fixed:
>
> commons-logging - 1.0.3 and 1.0.4
> xpp3 and xpp3_min
> org.apache.ws.commons.schema.XmlSchema - 1.4.2 and SNAPSHOT
>
>
> Some new/questionable depends:
> com.envoisolutions.sxc.sxc-jaxb and sxc-runtime
> org.jvnet.staxex
> quartz.quartz
>
> And backport-util-concurrent is still in the distro...
>
> Also, can we remove com/sun/xml/ws/jaxws-rt and jaxws-tools, now that we
> are using CXF for wsgen?
>
>
> -Donald
>
>
> Joe Bohn wrote:
>> It has been mentioned several times that we should be looking to
>> release Geronimo 2.2 before the end of the year (preferrably
>> mid-December).
>>
>>
>> Before we can consider a release there are a large number of snapshots
>> that need to be removed/replaced in our project. Can anybody shed any
>> light on these (or others that I may have missed)?
>>
>>
>> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
>> October. However, the trunk version was never updated and some
>> additional changes have been included. Recent changes in Geronimo
>> trunk now require this snapshot that is actually newer than the 3.1
>> release. IMO we should revert the trunk change and attempt to work
>> with the released OpenEJB 3.1.
>>
>> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
>> correctly we need to get an Axis2 release before we can consider a
>> Geronimo 2.2 release. Does anybody know how close we are to getting
>> an Axis2 release?
>>
>> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
>> required by Axis2 ... so if Axis2 is released then they will have to
>> get Axiom released as well (and we can pick up the released version).
>>
>> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it
>> must be)? In branches/2.1 we're still using 3.3. It looks like the
>> latest released version is 3.4.3. I'll give that a shot if I don't
>> hear from anybody that we really need 3.5.
>>
>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
>> must be)? In branches/2.1 we're using 2.0. What function requires
>> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide
>> an estimate on when this might be released?
>>
>> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point
>> where we can release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we
>> can release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where
>> we can release this spec or do we need to wait until we verify tck?
>>
>> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How
>> close is this to being able to be released?
>>
>> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to
>> being able to be released?
>>
>> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is
>> also related to Axis2 dependencies and will have to be resolved by
>> Axis2 as they release.
>>
>> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to
>> be resolved for an Axis2 release so we will pull in whatever they
>> require.
>>
>> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled
>> this in trying to resolve the FF3 issues. It's not clear to me if we
>> would have to remove this SNAPSHOT prior to a release but I think it
>> would be best to ensure that the tagged release can always be built
>> and run with tests - therefore I think we should remove it. Any other
>> opinions?
>>
>> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
>> updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know?
>> We should remove it.
>>
>> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this
>> was updated either. In branches/2.1 we updated the maven plugin
>> (above) but not the compiler but in trunk both were updated to the
>> alpha-2-SNAPSHOT. Anybody know why?
>>
>> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the
>> new legal file processing. Is there a released version we can use
>> instead of the SNAPSHOT or do we need to get a release here are well?
>>
>>
>> Joe
>>
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Donald Woods <dw...@apache.org>.
Yep, looks like the activemq-broker is pulling in at least one of the
commons-logging versions. I'll take a look at it today.
-Donald
Jason Dillon wrote:
> Commons-logging should not be included at all, we are using the slf4j
> adapters.
>
> --jason
>
>
> On Dec 10, 2008, at 2:18 AM, Donald Woods wrote:
>
>> We also have multiple versions of some depends getting pulled into the
>> assemblies right now, that needs to get fixed:
>>
>> commons-logging - 1.0.3 and 1.0.4
>> xpp3 and xpp3_min
>> org.apache.ws.commons.schema.XmlSchema - 1.4.2 and SNAPSHOT
>>
>>
>> Some new/questionable depends:
>> com.envoisolutions.sxc.sxc-jaxb and sxc-runtime
>> org.jvnet.staxex
>> quartz.quartz
>>
>> And backport-util-concurrent is still in the distro...
>>
>> Also, can we remove com/sun/xml/ws/jaxws-rt and jaxws-tools, now that
>> we are using CXF for wsgen?
>>
>>
>> -Donald
>>
>>
>> Joe Bohn wrote:
>>> It has been mentioned several times that we should be looking to
>>> release Geronimo 2.2 before the end of the year (preferrably
>>> mid-December).
>>> Before we can consider a release there are a large number of
>>> snapshots that need to be removed/replaced in our project. Can
>>> anybody shed any light on these (or others that I may have missed)?
>>> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
>>> October. However, the trunk version was never updated and some
>>> additional changes have been included. Recent changes in Geronimo
>>> trunk now require this snapshot that is actually newer than the 3.1
>>> release. IMO we should revert the trunk change and attempt to work
>>> with the released OpenEJB 3.1.
>>> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
>>> correctly we need to get an Axis2 release before we can consider a
>>> Geronimo 2.2 release. Does anybody know how close we are to getting
>>> an Axis2 release?
>>> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
>>> required by Axis2 ... so if Axis2 is released then they will have to
>>> get Axiom released as well (and we can pick up the released version).
>>> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it
>>> must be)? In branches/2.1 we're still using 3.3. It looks like the
>>> latest released version is 3.4.3. I'll give that a shot if I don't
>>> hear from anybody that we really need 3.5.
>>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
>>> must be)? In branches/2.1 we're using 2.0. What function requires
>>> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide
>>> an estimate on when this might be released?
>>> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point
>>> where we can release this spec or do we need to wait until we verify
>>> tck?
>>> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we
>>> can release this spec or do we need to wait until we verify tck?
>>> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where
>>> we can release this spec or do we need to wait until we verify tck?
>>> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component.
>>> How close is this to being able to be released?
>>> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to
>>> being able to be released?
>>> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is
>>> also related to Axis2 dependencies and will have to be resolved by
>>> Axis2 as they release.
>>> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have
>>> to be resolved for an Axis2 release so we will pull in whatever they
>>> require.
>>> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled
>>> this in trying to resolve the FF3 issues. It's not clear to me if we
>>> would have to remove this SNAPSHOT prior to a release but I think it
>>> would be best to ensure that the tagged release can always be built
>>> and run with tests - therefore I think we should remove it. Any
>>> other opinions?
>>> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
>>> updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know?
>>> We should remove it.
>>> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this
>>> was updated either. In branches/2.1 we updated the maven plugin
>>> (above) but not the compiler but in trunk both were updated to the
>>> alpha-2-SNAPSHOT. Anybody know why?
>>> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the
>>> new legal file processing. Is there a released version we can use
>>> instead of the SNAPSHOT or do we need to get a release here are well?
>>> Joe
>
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Jason Dillon <ja...@planet57.com>.
Commons-logging should not be included at all, we are using the slf4j
adapters.
--jason
On Dec 10, 2008, at 2:18 AM, Donald Woods wrote:
> We also have multiple versions of some depends getting pulled into
> the assemblies right now, that needs to get fixed:
>
> commons-logging - 1.0.3 and 1.0.4
> xpp3 and xpp3_min
> org.apache.ws.commons.schema.XmlSchema - 1.4.2 and SNAPSHOT
>
>
> Some new/questionable depends:
> com.envoisolutions.sxc.sxc-jaxb and sxc-runtime
> org.jvnet.staxex
> quartz.quartz
>
> And backport-util-concurrent is still in the distro...
>
> Also, can we remove com/sun/xml/ws/jaxws-rt and jaxws-tools, now
> that we are using CXF for wsgen?
>
>
> -Donald
>
>
> Joe Bohn wrote:
>> It has been mentioned several times that we should be looking to
>> release Geronimo 2.2 before the end of the year (preferrably mid-
>> December).
>> Before we can consider a release there are a large number of
>> snapshots that need to be removed/replaced in our project. Can
>> anybody shed any light on these (or others that I may have missed)?
>> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
>> October. However, the trunk version was never updated and some
>> additional changes have been included. Recent changes in Geronimo
>> trunk now require this snapshot that is actually newer than the 3.1
>> release. IMO we should revert the trunk change and attempt to work
>> with the released OpenEJB 3.1.
>> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
>> correctly we need to get an Axis2 release before we can consider a
>> Geronimo 2.2 release. Does anybody know how close we are to
>> getting an Axis2 release?
>> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
>> required by Axis2 ... so if Axis2 is released then they will have
>> to get Axiom released as well (and we can pick up the released
>> version).
>> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume
>> it must be)? In branches/2.1 we're still using 3.3. It looks like
>> the latest released version is 3.4.3. I'll give that a shot if I
>> don't hear from anybody that we really need 3.5.
>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
>> must be)? In branches/2.1 we're using 2.0. What function requires
>> 2.1-SNAPSHOT and is can somebody directly involved with wadi
>> provide an estimate on when this might be released?
>> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a
>> point where we can release this spec or do we need to wait until we
>> verify tck?
>> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we
>> can release this spec or do we need to wait until we verify tck?
>> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point
>> where we can release this spec or do we need to wait until we
>> verify tck?
>> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component.
>> How close is this to being able to be released?
>> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to
>> being able to be released?
>> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is
>> also related to Axis2 dependencies and will have to be resolved by
>> Axis2 as they release.
>> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have
>> to be resolved for an Axis2 release so we will pull in whatever
>> they require.
>> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we
>> pulled this in trying to resolve the FF3 issues. It's not clear to
>> me if we would have to remove this SNAPSHOT prior to a release but
>> I think it would be best to ensure that the tagged release can
>> always be built and run with tests - therefore I think we should
>> remove it. Any other opinions?
>> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
>> updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody
>> know? We should remove it.
>> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why
>> this was updated either. In branches/2.1 we updated the maven
>> plugin (above) but not the compiler but in trunk both were updated
>> to the alpha-2-SNAPSHOT. Anybody know why?
>> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support
>> the new legal file processing. Is there a released version we can
>> use instead of the SNAPSHOT or do we need to get a release here are
>> well?
>> Joe
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Donald Woods <dw...@apache.org>.
We also have multiple versions of some depends getting pulled into the
assemblies right now, that needs to get fixed:
commons-logging - 1.0.3 and 1.0.4
xpp3 and xpp3_min
org.apache.ws.commons.schema.XmlSchema - 1.4.2 and SNAPSHOT
Some new/questionable depends:
com.envoisolutions.sxc.sxc-jaxb and sxc-runtime
org.jvnet.staxex
quartz.quartz
And backport-util-concurrent is still in the distro...
Also, can we remove com/sun/xml/ws/jaxws-rt and jaxws-tools, now that we
are using CXF for wsgen?
-Donald
Joe Bohn wrote:
> It has been mentioned several times that we should be looking to release
> Geronimo 2.2 before the end of the year (preferrably mid-December).
>
>
> Before we can consider a release there are a large number of snapshots
> that need to be removed/replaced in our project. Can anybody shed any
> light on these (or others that I may have missed)?
>
>
> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
> October. However, the trunk version was never updated and some
> additional changes have been included. Recent changes in Geronimo trunk
> now require this snapshot that is actually newer than the 3.1 release.
> IMO we should revert the trunk change and attempt to work with the
> released OpenEJB 3.1.
>
> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
> correctly we need to get an Axis2 release before we can consider a
> Geronimo 2.2 release. Does anybody know how close we are to getting an
> Axis2 release?
>
> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
> required by Axis2 ... so if Axis2 is released then they will have to get
> Axiom released as well (and we can pick up the released version).
>
> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it
> must be)? In branches/2.1 we're still using 3.3. It looks like the
> latest released version is 3.4.3. I'll give that a shot if I don't hear
> from anybody that we really need 3.5.
>
> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it must
> be)? In branches/2.1 we're using 2.0. What function requires
> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide an
> estimate on when this might be released?
>
> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point
> where we can release this spec or do we need to wait until we verify tck?
>
> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we can
> release this spec or do we need to wait until we verify tck?
>
> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where we
> can release this spec or do we need to wait until we verify tck?
>
> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How
> close is this to being able to be released?
>
> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to being
> able to be released?
>
> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is also
> related to Axis2 dependencies and will have to be resolved by Axis2 as
> they release.
>
> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to
> be resolved for an Axis2 release so we will pull in whatever they require.
>
> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled
> this in trying to resolve the FF3 issues. It's not clear to me if we
> would have to remove this SNAPSHOT prior to a release but I think it
> would be best to ensure that the tagged release can always be built and
> run with tests - therefore I think we should remove it. Any other
> opinions?
>
> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
> updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know? We
> should remove it.
>
> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this was
> updated either. In branches/2.1 we updated the maven plugin (above) but
> not the compiler but in trunk both were updated to the alpha-2-SNAPSHOT.
> Anybody know why?
>
> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the new
> legal file processing. Is there a released version we can use instead
> of the SNAPSHOT or do we need to get a release here are well?
>
>
> Joe
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by Joe Bohn <jo...@earthlink.net>.
Thanks David. I'm not familiar with nexus but I did find this other
handy site that has been useful:
http://mvnrepository.com/
Is nexus similar?
Joe
David Jencks wrote:
>
> On Nov 11, 2008, at 3:04 PM, Joe Bohn wrote:
>
>> It has been mentioned several times that we should be looking to
>> release Geronimo 2.2 before the end of the year (preferrably
>> mid-December).
>>
>>
>> Before we can consider a release there are a large number of snapshots
>> that need to be removed/replaced in our project. Can anybody shed any
>> light on these (or others that I may have missed)?
>>
>>
>> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
>> October. However, the trunk version was never updated and some
>> additional changes have been included. Recent changes in Geronimo
>> trunk now require this snapshot that is actually newer than the 3.1
>> release. IMO we should revert the trunk change and attempt to work
>> with the released OpenEJB 3.1.
>>
>> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
>> correctly we need to get an Axis2 release before we can consider a
>> Geronimo 2.2 release. Does anybody know how close we are to getting
>> an Axis2 release?
>>
>> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
>> required by Axis2 ... so if Axis2 is released then they will have to
>> get Axiom released as well (and we can pick up the released version).
>>
>> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it
>> must be)? In branches/2.1 we're still using 3.3. It looks like the
>> latest released version is 3.4.3. I'll give that a shot if I don't
>> hear from anybody that we really need 3.5.
>
> xbean-naming 3.5 is required. Normally we release all xbean modules at
> once.
>>
>>
>> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
>> must be)? In branches/2.1 we're using 2.0. What function requires
>> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide
>> an estimate on when this might be released?
>>
>> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point
>> where we can release this spec or do we need to wait until we verify tck?
>
> I wish I knew. I guess we could release any number of x.y-EA followed
> by 1.0 after the spec is final and we get the tck.
>
>>
>>
>> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we
>> can release this spec or do we need to wait until we verify tck?
>
> Here at least the spec is done. I guess we need to ask geir to look for
> a tck for it.
>
>>
>>
>> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where
>> we can release this spec or do we need to wait until we verify tck?
>
> Same as connector 1.6 although probably less stable.
>>
>>
>> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How
>> close is this to being able to be released?
>
> Let me think about this a bit.... probably close to releasable.
>
>>
>>
>> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to
>> being able to be released?
>>
>> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is
>> also related to Axis2 dependencies and will have to be resolved by
>> Axis2 as they release.
>>
>> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to
>> be resolved for an Axis2 release so we will pull in whatever they
>> require.
>>
>> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled
>> this in trying to resolve the FF3 issues. It's not clear to me if we
>> would have to remove this SNAPSHOT prior to a release but I think it
>> would be best to ensure that the tagged release can always be built
>> and run with tests - therefore I think we should remove it. Any other
>> opinions?
>
> We should remove it. I think they tagged a working version, don't
> recall the situation regarding publishing the result.... dont see it in
> the nexus index, but may not have the correct repo.
>>
>>
>> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
>> updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know?
>> We should remove it.
>>
>> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this
>> was updated either. In branches/2.1 we updated the maven plugin
>> (above) but not the compiler but in trunk both were updated to the
>> alpha-2-SNAPSHOT. Anybody know why?
>>
>> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the
>> new legal file processing. Is there a released version we can use
>> instead of the SNAPSHOT or do we need to get a release here are well?
>
> There's a 1.0-alpha-1 version published.
>
> I strongly recommend nexus.... it really helps investigating these
> questions (this one took about 3 seconds).
>
> IMO we should use genesis 2.0 which I think already uses ianal and has
> all the needed configuration for it.
>
>>
>>
>
> thanks
> david jencks
>
>>
>> Joe
>
>
Re: 2.2 (trunk) bucket-o-snapshots
Posted by David Jencks <da...@yahoo.com>.
On Nov 11, 2008, at 3:04 PM, Joe Bohn wrote:
> It has been mentioned several times that we should be looking to
> release Geronimo 2.2 before the end of the year (preferrably mid-
> December).
>
>
> Before we can consider a release there are a large number of
> snapshots that need to be removed/replaced in our project. Can
> anybody shed any light on these (or others that I may have missed)?
>
>
> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late
> October. However, the trunk version was never updated and some
> additional changes have been included. Recent changes in Geronimo
> trunk now require this snapshot that is actually newer than the 3.1
> release. IMO we should revert the trunk change and attempt to work
> with the released OpenEJB 3.1.
>
> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC
> correctly we need to get an Axis2 release before we can consider a
> Geronimo 2.2 release. Does anybody know how close we are to getting
> an Axis2 release?
>
> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is
> required by Axis2 ... so if Axis2 is released then they will have to
> get Axiom released as well (and we can pick up the released version).
>
> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it
> must be)? In branches/2.1 we're still using 3.3. It looks like the
> latest released version is 3.4.3. I'll give that a shot if I don't
> hear from anybody that we really need 3.5.
xbean-naming 3.5 is required. Normally we release all xbean modules
at once.
>
>
> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it
> must be)? In branches/2.1 we're using 2.0. What function requires
> 2.1-SNAPSHOT and is can somebody directly involved with wadi provide
> an estimate on when this might be released?
>
> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a
> point where we can release this spec or do we need to wait until we
> verify tck?
I wish I knew. I guess we could release any number of x.y-EA followed
by 1.0 after the spec is final and we get the tck.
>
>
> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we
> can release this spec or do we need to wait until we verify tck?
Here at least the spec is done. I guess we need to ask geir to look
for a tck for it.
>
>
> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point
> where we can release this spec or do we need to wait until we verify
> tck?
Same as connector 1.6 although probably less stable.
>
>
> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component.
> How close is this to being able to be released?
Let me think about this a bit.... probably close to releasable.
>
>
> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to
> being able to be released?
>
> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is
> also related to Axis2 dependencies and will have to be resolved by
> Axis2 as they release.
>
> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have
> to be resolved for an Axis2 release so we will pull in whatever they
> require.
>
> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled
> this in trying to resolve the FF3 issues. It's not clear to me if
> we would have to remove this SNAPSHOT prior to a release but I think
> it would be best to ensure that the tagged release can always be
> built and run with tests - therefore I think we should remove it.
> Any other opinions?
We should remove it. I think they tagged a working version, don't
recall the situation regarding publishing the result.... dont see it
in the nexus index, but may not have the correct repo.
>
>
> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is
> updated (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody
> know? We should remove it.
>
> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this
> was updated either. In branches/2.1 we updated the maven plugin
> (above) but not the compiler but in trunk both were updated to the
> alpha-2-SNAPSHOT. Anybody know why?
>
> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the
> new legal file processing. Is there a released version we can use
> instead of the SNAPSHOT or do we need to get a release here are well?
There's a 1.0-alpha-1 version published.
I strongly recommend nexus.... it really helps investigating these
questions (this one took about 3 seconds).
IMO we should use genesis 2.0 which I think already uses ianal and has
all the needed configuration for it.
>
>
thanks
david jencks
>
> Joe