You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jason Dillon <ja...@planet57.com> on 2007/04/05 02:10:46 UTC
Re: [vote] Release openejb-2.3-incubating
<note>
Copying g list because the same problem is relevant to the g 1.2
release.
</note>
This is still using some artifacts which are only in snapshot
repositories:
* xmlbeans-maven-plugin 2.0.1-20060627.031204-7
* maven-deploy-plugin 2.3-20061210.174233-3
* maven-gpg-plugin 1.0-alpha-2-20061214.035657-1
While the version does not have SNAPSHOT in it... don't let that
trick you into thinking these are not SNAPSHOTS, because they are.
While the release plugin will let you roll something out like this,
use of these pinned snapshots will limit the build-ability of this
tree in the future.
While there is no real guarantee that any artifact in any repo (snap
or not) will really be around in the future (short or long term),
there is a high possibility that artifacts in a snap repo will not be
around for very long. And even when using a pinned snapshot the fact
still remains that the storage of that artifact is transient and will
almost certainly not be available at some time in the future, which
will cause this tree (and the G 1.2 tree) to be unbuildable w/o
source changes.
The main problem here is the xmlbeans-maven-plugin
2.0.1-20060627.031204-7, which affects the G 1.2 build as well. The
others are for release support and are in a profile which is not
enabled by default.
* * *
I mention this not to derail the release... because I really want
this to get out so we can get G 1.2 out. But we would really be in a
much better position to support the ongoing build-ability of this
tree if we did not have *any* artifacts which are required to build
that are only available in a transient snapshot repository.
If its a pain to get a release release from the mojo folks working on
the xmlbeans-maven-plugin, then we need to add these artifacts (and
any snaps which it may be depending on, I didn't look), into a local
repository that is checked into svn, just like G does (ie. http://
svn.apache.org/repos/asf/geronimo/server/branches/1.2/repository/ ).
--jason
On Apr 4, 2007, at 4:52 PM, Dain Sundstrom wrote:
> All,
>
> The release is cut and awaiting your vote! All the files are
> available in a staging area in my home dir on people.
>
> http://people.apache.org/~dain/stage/org/apache/openejb/
>
> itests-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
> modules-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
> openejb-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
> openejb-axis-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
> openejb-builder-2.3-incubating (jar,source,javadoc,pom)
> {asc,md4,sha1}
> openejb-corba-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
> openejb-corba-builder-2.3-incubating (jar,source,javadoc,pom)
> {asc,md4,sha1}
> openejb-core-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
> openejb-itests-core-2.3-incubating (jar,source,javadoc,pom)
> {asc,md4,sha1}
> openejb-pkgen-builder-2.3-incubating (jar,source,javadoc,pom)
> {asc,md4,sha1}
> openejb-yoko-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>
> All jars contain DISCLAIMER, LICENSE, and NOTICE. Each binary jar
> is also accompanied by source, javadoc, pom and all are signed, md5-
> ed, and secure-hashed. Keys file available here:
>
> http://people.apache.org/repo/m2-incubating-repository/org/
> apache/openejb/KEYS
>
> Svn tag is here:
>
> http://svn.apache.org/repos/asf/incubator/openejb/tags/openejb-2.3/
>
> Here's my +1!
>
> -dain
>
>
Re: [vote] Release openejb-2.3-incubating
Posted by Jason Dillon <ja...@planet57.com>.
This does address my concerns, though while we should still not use
pinned snapshots in a release, having this repo available will allow
the tree to have a higher chance of being build-able in the future.
I think we should probably considering making this a standard of
sorts when making a release, to include the dependency artifacts in a
tar.bz2 along with the *-src.* bits. As long as we don't include the
artifacts we are building then the size should be relatively small...
and thats a small price to pay for having a tree build build-able in
the future.
I think we really need to hold on to the artifacts in the dist tree
just like we do for the src, because with out one or the other, your
chances of having a successful build are going to vary widely.
I think that we should think this over and then consider making this
a policy, at least for now until we have a better story on the
longevity of our m2 builds.
--jason
On Apr 4, 2007, at 5:45 PM, Dain Sundstrom wrote:
> Jason and I chatted on irc and decided there isn't much we can do
> about these, or the fact that the repos aren't as reliable as we'd
> like. To address this, I have saved off the repository used to
> create the release here:
>
> http://people.apache.org/~dain/dist/geronimo-1.2-build-
> repository.tar.bz
>
> This way we will *always* have everything maven needs to rebuild
> the server from source.
>
> -dain
>
> On Apr 4, 2007, at 5:10 PM, Jason Dillon wrote:
>
>> <note>
>> Copying g list because the same problem is relevant to the g 1.2
>> release.
>> </note>
>>
>> This is still using some artifacts which are only in snapshot
>> repositories:
>>
>> * xmlbeans-maven-plugin 2.0.1-20060627.031204-7
>> * maven-deploy-plugin 2.3-20061210.174233-3
>> * maven-gpg-plugin 1.0-alpha-2-20061214.035657-1
>>
>> While the version does not have SNAPSHOT in it... don't let that
>> trick you into thinking these are not SNAPSHOTS, because they
>> are. While the release plugin will let you roll something out
>> like this, use of these pinned snapshots will limit the build-
>> ability of this tree in the future.
>>
>> While there is no real guarantee that any artifact in any repo
>> (snap or not) will really be around in the future (short or long
>> term), there is a high possibility that artifacts in a snap repo
>> will not be around for very long. And even when using a pinned
>> snapshot the fact still remains that the storage of that artifact
>> is transient and will almost certainly not be available at some
>> time in the future, which will cause this tree (and the G 1.2
>> tree) to be unbuildable w/o source changes.
>>
>> The main problem here is the xmlbeans-maven-plugin
>> 2.0.1-20060627.031204-7, which affects the G 1.2 build as well.
>> The others are for release support and are in a profile which is
>> not enabled by default.
>>
>> * * *
>>
>> I mention this not to derail the release... because I really want
>> this to get out so we can get G 1.2 out. But we would really be
>> in a much better position to support the ongoing build-ability of
>> this tree if we did not have *any* artifacts which are required to
>> build that are only available in a transient snapshot repository.
>>
>> If its a pain to get a release release from the mojo folks working
>> on the xmlbeans-maven-plugin, then we need to add these artifacts
>> (and any snaps which it may be depending on, I didn't look), into
>> a local repository that is checked into svn, just like G does (ie.
>> http://svn.apache.org/repos/asf/geronimo/server/branches/1.2/
>> repository/ ).
>>
>> --jason
>>
>>
>> On Apr 4, 2007, at 4:52 PM, Dain Sundstrom wrote:
>>
>>> All,
>>>
>>> The release is cut and awaiting your vote! All the files are
>>> available in a staging area in my home dir on people.
>>>
>>> http://people.apache.org/~dain/stage/org/apache/openejb/
>>>
>>> itests-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> modules-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> openejb-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> openejb-axis-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-corba-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-corba-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-core-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-itests-core-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-pkgen-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-yoko-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>>
>>> All jars contain DISCLAIMER, LICENSE, and NOTICE. Each binary
>>> jar is also accompanied by source, javadoc, pom and all are
>>> signed, md5-ed, and secure-hashed. Keys file available here:
>>>
>>> http://people.apache.org/repo/m2-incubating-repository/org/
>>> apache/openejb/KEYS
>>>
>>> Svn tag is here:
>>>
>>> http://svn.apache.org/repos/asf/incubator/openejb/tags/
>>> openejb-2.3/
>>>
>>> Here's my +1!
>>>
>>> -dain
>>>
>>>
>>
>
Re: [vote] Release openejb-2.3-incubating
Posted by Jason Dillon <ja...@planet57.com>.
This does address my concerns, though while we should still not use
pinned snapshots in a release, having this repo available will allow
the tree to have a higher chance of being build-able in the future.
I think we should probably considering making this a standard of
sorts when making a release, to include the dependency artifacts in a
tar.bz2 along with the *-src.* bits. As long as we don't include the
artifacts we are building then the size should be relatively small...
and thats a small price to pay for having a tree build build-able in
the future.
I think we really need to hold on to the artifacts in the dist tree
just like we do for the src, because with out one or the other, your
chances of having a successful build are going to vary widely.
I think that we should think this over and then consider making this
a policy, at least for now until we have a better story on the
longevity of our m2 builds.
--jason
On Apr 4, 2007, at 5:45 PM, Dain Sundstrom wrote:
> Jason and I chatted on irc and decided there isn't much we can do
> about these, or the fact that the repos aren't as reliable as we'd
> like. To address this, I have saved off the repository used to
> create the release here:
>
> http://people.apache.org/~dain/dist/geronimo-1.2-build-
> repository.tar.bz
>
> This way we will *always* have everything maven needs to rebuild
> the server from source.
>
> -dain
>
> On Apr 4, 2007, at 5:10 PM, Jason Dillon wrote:
>
>> <note>
>> Copying g list because the same problem is relevant to the g 1.2
>> release.
>> </note>
>>
>> This is still using some artifacts which are only in snapshot
>> repositories:
>>
>> * xmlbeans-maven-plugin 2.0.1-20060627.031204-7
>> * maven-deploy-plugin 2.3-20061210.174233-3
>> * maven-gpg-plugin 1.0-alpha-2-20061214.035657-1
>>
>> While the version does not have SNAPSHOT in it... don't let that
>> trick you into thinking these are not SNAPSHOTS, because they
>> are. While the release plugin will let you roll something out
>> like this, use of these pinned snapshots will limit the build-
>> ability of this tree in the future.
>>
>> While there is no real guarantee that any artifact in any repo
>> (snap or not) will really be around in the future (short or long
>> term), there is a high possibility that artifacts in a snap repo
>> will not be around for very long. And even when using a pinned
>> snapshot the fact still remains that the storage of that artifact
>> is transient and will almost certainly not be available at some
>> time in the future, which will cause this tree (and the G 1.2
>> tree) to be unbuildable w/o source changes.
>>
>> The main problem here is the xmlbeans-maven-plugin
>> 2.0.1-20060627.031204-7, which affects the G 1.2 build as well.
>> The others are for release support and are in a profile which is
>> not enabled by default.
>>
>> * * *
>>
>> I mention this not to derail the release... because I really want
>> this to get out so we can get G 1.2 out. But we would really be
>> in a much better position to support the ongoing build-ability of
>> this tree if we did not have *any* artifacts which are required to
>> build that are only available in a transient snapshot repository.
>>
>> If its a pain to get a release release from the mojo folks working
>> on the xmlbeans-maven-plugin, then we need to add these artifacts
>> (and any snaps which it may be depending on, I didn't look), into
>> a local repository that is checked into svn, just like G does (ie.
>> http://svn.apache.org/repos/asf/geronimo/server/branches/1.2/
>> repository/ ).
>>
>> --jason
>>
>>
>> On Apr 4, 2007, at 4:52 PM, Dain Sundstrom wrote:
>>
>>> All,
>>>
>>> The release is cut and awaiting your vote! All the files are
>>> available in a staging area in my home dir on people.
>>>
>>> http://people.apache.org/~dain/stage/org/apache/openejb/
>>>
>>> itests-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> modules-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> openejb-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> openejb-axis-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-corba-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-corba-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-core-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-itests-core-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-pkgen-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-yoko-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>>
>>> All jars contain DISCLAIMER, LICENSE, and NOTICE. Each binary
>>> jar is also accompanied by source, javadoc, pom and all are
>>> signed, md5-ed, and secure-hashed. Keys file available here:
>>>
>>> http://people.apache.org/repo/m2-incubating-repository/org/
>>> apache/openejb/KEYS
>>>
>>> Svn tag is here:
>>>
>>> http://svn.apache.org/repos/asf/incubator/openejb/tags/
>>> openejb-2.3/
>>>
>>> Here's my +1!
>>>
>>> -dain
>>>
>>>
>>
>
Re: plugin releases (was: [vote] Release openejb-2.3-incubating)
Posted by Jason Dillon <ja...@planet57.com>.
On Apr 4, 2007, at 5:56 PM, Brett Porter wrote:
> Seems like a reasonable workaround, though it'll be hard to retain
> that location over time?
I was thinking of just including this repo.tar.bz2 in the dist dir
next to the srcs, so it gets preserved for all time.
> Just to throw out other options:
> - check these in to your own scm (maybe under /vendor) and change
> the groupId, then release them as 2.3-geronimo-1.2 or similar. Then
> you have both the source and binaries you rely on.
Yup, this is one option too, which I do like have that repo.tar.bz2,
though adding big files like that will hinder tools like svk2 :-(
> - kick the developers of those plugins (I see no reason we couldn't
> work on releasing the 2 maven ones over there, and Jason should be
> able to release xmlbeans?). I understand this introduces lag for
> you though.
Problem is that no one really knows if the current xmlbeans-maven-
plugin works or will cause problems, and I don't know what rev this
snap is from so I can't branch and release the code that we use now.
I think we switched to this pinned snapshot a while ago due to
problems with newer snapshots, but then it worked and no one looked
into it anymore. And the pinned snapshot is hard to find cause it
doesn't appear to be a snap, but it is.
I'm happy with the repo.tar.bz2 for now though.... and really I think
we may need to keep a hold of the dependency artifacts for release
builds to ensure that future builds of the released sources will
work... cause no matter what anyone says... eventually something on a
public repo will be lost causing builds to break.
--jason
Re: plugin releases (was: [vote] Release openejb-2.3-incubating)
Posted by Brett Porter <br...@apache.org>.
Seems like a reasonable workaround, though it'll be hard to retain
that location over time?
Just to throw out other options:
- check these in to your own scm (maybe under /vendor) and change the
groupId, then release them as 2.3-geronimo-1.2 or similar. Then you
have both the source and binaries you rely on.
- kick the developers of those plugins (I see no reason we couldn't
work on releasing the 2 maven ones over there, and Jason should be
able to release xmlbeans?). I understand this introduces lag for you
though.
Cheers,
Brett
On 05/04/2007, at 10:50 AM, Dain Sundstrom wrote:
> Based on Jason's recommendation, I renamed the file to:
>
> http://people.apache.org/~dain/dist/geronimo-1.2-build-
> repository.tar.bz2
>
> -dain
>
> On Apr 4, 2007, at 5:45 PM, Dain Sundstrom wrote:
>
>> Jason and I chatted on irc and decided there isn't much we can do
>> about these, or the fact that the repos aren't as reliable as we'd
>> like. To address this, I have saved off the repository used to
>> create the release here:
>>
>> http://people.apache.org/~dain/dist/geronimo-1.2-build-
>> repository.tar.bz
>>
>> This way we will *always* have everything maven needs to rebuild
>> the server from source.
>>
>> -dain
>>
>> On Apr 4, 2007, at 5:10 PM, Jason Dillon wrote:
>>
>>> <note>
>>> Copying g list because the same problem is relevant to the g 1.2
>>> release.
>>> </note>
>>>
>>> This is still using some artifacts which are only in snapshot
>>> repositories:
>>>
>>> * xmlbeans-maven-plugin 2.0.1-20060627.031204-7
>>> * maven-deploy-plugin 2.3-20061210.174233-3
>>> * maven-gpg-plugin 1.0-alpha-2-20061214.035657-1
>>>
>>> While the version does not have SNAPSHOT in it... don't let that
>>> trick you into thinking these are not SNAPSHOTS, because they
>>> are. While the release plugin will let you roll something out
>>> like this, use of these pinned snapshots will limit the build-
>>> ability of this tree in the future.
>>>
>>> While there is no real guarantee that any artifact in any repo
>>> (snap or not) will really be around in the future (short or long
>>> term), there is a high possibility that artifacts in a snap repo
>>> will not be around for very long. And even when using a pinned
>>> snapshot the fact still remains that the storage of that artifact
>>> is transient and will almost certainly not be available at some
>>> time in the future, which will cause this tree (and the G 1.2
>>> tree) to be unbuildable w/o source changes.
>>>
>>> The main problem here is the xmlbeans-maven-plugin
>>> 2.0.1-20060627.031204-7, which affects the G 1.2 build as well.
>>> The others are for release support and are in a profile which is
>>> not enabled by default.
>>>
>>> * * *
>>>
>>> I mention this not to derail the release... because I really want
>>> this to get out so we can get G 1.2 out. But we would really be
>>> in a much better position to support the ongoing build-ability of
>>> this tree if we did not have *any* artifacts which are required
>>> to build that are only available in a transient snapshot repository.
>>>
>>> If its a pain to get a release release from the mojo folks
>>> working on the xmlbeans-maven-plugin, then we need to add these
>>> artifacts (and any snaps which it may be depending on, I didn't
>>> look), into a local repository that is checked into svn, just
>>> like G does (ie. http://svn.apache.org/repos/asf/geronimo/server/
>>> branches/1.2/repository/ ).
>>>
>>> --jason
>>>
>>>
>>> On Apr 4, 2007, at 4:52 PM, Dain Sundstrom wrote:
>>>
>>>> All,
>>>>
>>>> The release is cut and awaiting your vote! All the files are
>>>> available in a staging area in my home dir on people.
>>>>
>>>> http://people.apache.org/~dain/stage/org/apache/openejb/
>>>>
>>>> itests-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>>> modules-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>>> openejb-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>>> openejb-axis-2.3-incubating (jar,source,javadoc,pom)
>>>> {asc,md4,sha1}
>>>> openejb-builder-2.3-incubating (jar,source,javadoc,pom)
>>>> {asc,md4,sha1}
>>>> openejb-corba-2.3-incubating (jar,source,javadoc,pom)
>>>> {asc,md4,sha1}
>>>> openejb-corba-builder-2.3-incubating (jar,source,javadoc,pom)
>>>> {asc,md4,sha1}
>>>> openejb-core-2.3-incubating (jar,source,javadoc,pom)
>>>> {asc,md4,sha1}
>>>> openejb-itests-core-2.3-incubating (jar,source,javadoc,pom)
>>>> {asc,md4,sha1}
>>>> openejb-pkgen-builder-2.3-incubating (jar,source,javadoc,pom)
>>>> {asc,md4,sha1}
>>>> openejb-yoko-2.3-incubating (jar,source,javadoc,pom)
>>>> {asc,md4,sha1}
>>>>
>>>> All jars contain DISCLAIMER, LICENSE, and NOTICE. Each binary
>>>> jar is also accompanied by source, javadoc, pom and all are
>>>> signed, md5-ed, and secure-hashed. Keys file available here:
>>>>
>>>> http://people.apache.org/repo/m2-incubating-repository/org/
>>>> apache/openejb/KEYS
>>>>
>>>> Svn tag is here:
>>>>
>>>> http://svn.apache.org/repos/asf/incubator/openejb/tags/
>>>> openejb-2.3/
>>>>
>>>> Here's my +1!
>>>>
>>>> -dain
>>>>
>>>>
>>>
>>
Re: [vote] Release openejb-2.3-incubating
Posted by Dain Sundstrom <da...@iq80.com>.
Based on Jason's recommendation, I renamed the file to:
http://people.apache.org/~dain/dist/geronimo-1.2-build-
repository.tar.bz2
-dain
On Apr 4, 2007, at 5:45 PM, Dain Sundstrom wrote:
> Jason and I chatted on irc and decided there isn't much we can do
> about these, or the fact that the repos aren't as reliable as we'd
> like. To address this, I have saved off the repository used to
> create the release here:
>
> http://people.apache.org/~dain/dist/geronimo-1.2-build-
> repository.tar.bz
>
> This way we will *always* have everything maven needs to rebuild
> the server from source.
>
> -dain
>
> On Apr 4, 2007, at 5:10 PM, Jason Dillon wrote:
>
>> <note>
>> Copying g list because the same problem is relevant to the g 1.2
>> release.
>> </note>
>>
>> This is still using some artifacts which are only in snapshot
>> repositories:
>>
>> * xmlbeans-maven-plugin 2.0.1-20060627.031204-7
>> * maven-deploy-plugin 2.3-20061210.174233-3
>> * maven-gpg-plugin 1.0-alpha-2-20061214.035657-1
>>
>> While the version does not have SNAPSHOT in it... don't let that
>> trick you into thinking these are not SNAPSHOTS, because they
>> are. While the release plugin will let you roll something out
>> like this, use of these pinned snapshots will limit the build-
>> ability of this tree in the future.
>>
>> While there is no real guarantee that any artifact in any repo
>> (snap or not) will really be around in the future (short or long
>> term), there is a high possibility that artifacts in a snap repo
>> will not be around for very long. And even when using a pinned
>> snapshot the fact still remains that the storage of that artifact
>> is transient and will almost certainly not be available at some
>> time in the future, which will cause this tree (and the G 1.2
>> tree) to be unbuildable w/o source changes.
>>
>> The main problem here is the xmlbeans-maven-plugin
>> 2.0.1-20060627.031204-7, which affects the G 1.2 build as well.
>> The others are for release support and are in a profile which is
>> not enabled by default.
>>
>> * * *
>>
>> I mention this not to derail the release... because I really want
>> this to get out so we can get G 1.2 out. But we would really be
>> in a much better position to support the ongoing build-ability of
>> this tree if we did not have *any* artifacts which are required to
>> build that are only available in a transient snapshot repository.
>>
>> If its a pain to get a release release from the mojo folks working
>> on the xmlbeans-maven-plugin, then we need to add these artifacts
>> (and any snaps which it may be depending on, I didn't look), into
>> a local repository that is checked into svn, just like G does (ie.
>> http://svn.apache.org/repos/asf/geronimo/server/branches/1.2/
>> repository/ ).
>>
>> --jason
>>
>>
>> On Apr 4, 2007, at 4:52 PM, Dain Sundstrom wrote:
>>
>>> All,
>>>
>>> The release is cut and awaiting your vote! All the files are
>>> available in a staging area in my home dir on people.
>>>
>>> http://people.apache.org/~dain/stage/org/apache/openejb/
>>>
>>> itests-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> modules-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> openejb-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>> openejb-axis-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-corba-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-corba-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-core-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-itests-core-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-pkgen-builder-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>> openejb-yoko-2.3-incubating (jar,source,javadoc,pom)
>>> {asc,md4,sha1}
>>>
>>> All jars contain DISCLAIMER, LICENSE, and NOTICE. Each binary
>>> jar is also accompanied by source, javadoc, pom and all are
>>> signed, md5-ed, and secure-hashed. Keys file available here:
>>>
>>> http://people.apache.org/repo/m2-incubating-repository/org/
>>> apache/openejb/KEYS
>>>
>>> Svn tag is here:
>>>
>>> http://svn.apache.org/repos/asf/incubator/openejb/tags/
>>> openejb-2.3/
>>>
>>> Here's my +1!
>>>
>>> -dain
>>>
>>>
>>
>
Re: [vote] Release openejb-2.3-incubating
Posted by Dain Sundstrom <da...@iq80.com>.
Jason and I chatted on irc and decided there isn't much we can do
about these, or the fact that the repos aren't as reliable as we'd
like. To address this, I have saved off the repository used to
create the release here:
http://people.apache.org/~dain/dist/geronimo-1.2-build-
repository.tar.bz
This way we will *always* have everything maven needs to rebuild the
server from source.
-dain
On Apr 4, 2007, at 5:10 PM, Jason Dillon wrote:
> <note>
> Copying g list because the same problem is relevant to the g 1.2
> release.
> </note>
>
> This is still using some artifacts which are only in snapshot
> repositories:
>
> * xmlbeans-maven-plugin 2.0.1-20060627.031204-7
> * maven-deploy-plugin 2.3-20061210.174233-3
> * maven-gpg-plugin 1.0-alpha-2-20061214.035657-1
>
> While the version does not have SNAPSHOT in it... don't let that
> trick you into thinking these are not SNAPSHOTS, because they are.
> While the release plugin will let you roll something out like this,
> use of these pinned snapshots will limit the build-ability of this
> tree in the future.
>
> While there is no real guarantee that any artifact in any repo
> (snap or not) will really be around in the future (short or long
> term), there is a high possibility that artifacts in a snap repo
> will not be around for very long. And even when using a pinned
> snapshot the fact still remains that the storage of that artifact
> is transient and will almost certainly not be available at some
> time in the future, which will cause this tree (and the G 1.2 tree)
> to be unbuildable w/o source changes.
>
> The main problem here is the xmlbeans-maven-plugin
> 2.0.1-20060627.031204-7, which affects the G 1.2 build as well.
> The others are for release support and are in a profile which is
> not enabled by default.
>
> * * *
>
> I mention this not to derail the release... because I really want
> this to get out so we can get G 1.2 out. But we would really be in
> a much better position to support the ongoing build-ability of this
> tree if we did not have *any* artifacts which are required to build
> that are only available in a transient snapshot repository.
>
> If its a pain to get a release release from the mojo folks working
> on the xmlbeans-maven-plugin, then we need to add these artifacts
> (and any snaps which it may be depending on, I didn't look), into a
> local repository that is checked into svn, just like G does (ie.
> http://svn.apache.org/repos/asf/geronimo/server/branches/1.2/
> repository/ ).
>
> --jason
>
>
> On Apr 4, 2007, at 4:52 PM, Dain Sundstrom wrote:
>
>> All,
>>
>> The release is cut and awaiting your vote! All the files are
>> available in a staging area in my home dir on people.
>>
>> http://people.apache.org/~dain/stage/org/apache/openejb/
>>
>> itests-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> modules-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-axis-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-corba-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-corba-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-core-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-itests-core-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-pkgen-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-yoko-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>
>> All jars contain DISCLAIMER, LICENSE, and NOTICE. Each binary jar
>> is also accompanied by source, javadoc, pom and all are signed,
>> md5-ed, and secure-hashed. Keys file available here:
>>
>> http://people.apache.org/repo/m2-incubating-repository/org/
>> apache/openejb/KEYS
>>
>> Svn tag is here:
>>
>> http://svn.apache.org/repos/asf/incubator/openejb/tags/
>> openejb-2.3/
>>
>> Here's my +1!
>>
>> -dain
>>
>>
>
Re: [vote] Release openejb-2.3-incubating
Posted by Dain Sundstrom <da...@iq80.com>.
Jason and I chatted on irc and decided there isn't much we can do
about these, or the fact that the repos aren't as reliable as we'd
like. To address this, I have saved off the repository used to
create the release here:
http://people.apache.org/~dain/dist/geronimo-1.2-build-
repository.tar.bz
This way we will *always* have everything maven needs to rebuild the
server from source.
-dain
On Apr 4, 2007, at 5:10 PM, Jason Dillon wrote:
> <note>
> Copying g list because the same problem is relevant to the g 1.2
> release.
> </note>
>
> This is still using some artifacts which are only in snapshot
> repositories:
>
> * xmlbeans-maven-plugin 2.0.1-20060627.031204-7
> * maven-deploy-plugin 2.3-20061210.174233-3
> * maven-gpg-plugin 1.0-alpha-2-20061214.035657-1
>
> While the version does not have SNAPSHOT in it... don't let that
> trick you into thinking these are not SNAPSHOTS, because they are.
> While the release plugin will let you roll something out like this,
> use of these pinned snapshots will limit the build-ability of this
> tree in the future.
>
> While there is no real guarantee that any artifact in any repo
> (snap or not) will really be around in the future (short or long
> term), there is a high possibility that artifacts in a snap repo
> will not be around for very long. And even when using a pinned
> snapshot the fact still remains that the storage of that artifact
> is transient and will almost certainly not be available at some
> time in the future, which will cause this tree (and the G 1.2 tree)
> to be unbuildable w/o source changes.
>
> The main problem here is the xmlbeans-maven-plugin
> 2.0.1-20060627.031204-7, which affects the G 1.2 build as well.
> The others are for release support and are in a profile which is
> not enabled by default.
>
> * * *
>
> I mention this not to derail the release... because I really want
> this to get out so we can get G 1.2 out. But we would really be in
> a much better position to support the ongoing build-ability of this
> tree if we did not have *any* artifacts which are required to build
> that are only available in a transient snapshot repository.
>
> If its a pain to get a release release from the mojo folks working
> on the xmlbeans-maven-plugin, then we need to add these artifacts
> (and any snaps which it may be depending on, I didn't look), into a
> local repository that is checked into svn, just like G does (ie.
> http://svn.apache.org/repos/asf/geronimo/server/branches/1.2/
> repository/ ).
>
> --jason
>
>
> On Apr 4, 2007, at 4:52 PM, Dain Sundstrom wrote:
>
>> All,
>>
>> The release is cut and awaiting your vote! All the files are
>> available in a staging area in my home dir on people.
>>
>> http://people.apache.org/~dain/stage/org/apache/openejb/
>>
>> itests-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> modules-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-axis-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-corba-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-corba-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-core-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-itests-core-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-pkgen-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-yoko-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>
>> All jars contain DISCLAIMER, LICENSE, and NOTICE. Each binary jar
>> is also accompanied by source, javadoc, pom and all are signed,
>> md5-ed, and secure-hashed. Keys file available here:
>>
>> http://people.apache.org/repo/m2-incubating-repository/org/
>> apache/openejb/KEYS
>>
>> Svn tag is here:
>>
>> http://svn.apache.org/repos/asf/incubator/openejb/tags/
>> openejb-2.3/
>>
>> Here's my +1!
>>
>> -dain
>>
>>
>
Re: [vote] Release openejb-2.3-incubating
Posted by Matt Hogstrom <ma...@hogstrom.org>.
>
+1
Downloaded several of the jars and the legal items look good.
.asc signatures verify
I tested the functionality as embedded in Geronimo using DayTrader
and the performance looks good (at a quick check :) and
functionality seems to be there.
> On Apr 4, 2007, at 4:52 PM, Dain Sundstrom wrote:
>
>> All,
>>
>> The release is cut and awaiting your vote! All the files are
>> available in a staging area in my home dir on people.
>>
>> http://people.apache.org/~dain/stage/org/apache/openejb/
>>
>> itests-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> modules-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-axis-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-corba-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-corba-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-core-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>> openejb-itests-core-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-pkgen-builder-2.3-incubating (jar,source,javadoc,pom)
>> {asc,md4,sha1}
>> openejb-yoko-2.3-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>>
>> All jars contain DISCLAIMER, LICENSE, and NOTICE. Each binary jar
>> is also accompanied by source, javadoc, pom and all are signed,
>> md5-ed, and secure-hashed. Keys file available here:
>>
>> http://people.apache.org/repo/m2-incubating-repository/org/
>> apache/openejb/KEYS
>>
>> Svn tag is here:
>>
>> http://svn.apache.org/repos/asf/incubator/openejb/tags/
>> openejb-2.3/
>>
>> Here's my +1!
>>
>> -dain
>>
>>
>
>