You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Rajith Attapattu <ra...@gmail.com> on 2006/11/15 20:45:17 UTC
[ANN] The M1 Release Candidates are available for download
Hi All,
The M1 release candidates are available for download at the following
location.
http://people.apache.org/~rajith/qpid-release/
Regards,
Rajith Attapattu
Re: [ANN] The M1 Release Candidates are available for download
Posted by Rajith Attapattu <ra...@gmail.com>.
Martin,
Please make all changes on the branch as well.
We are making the release from the branch.
Regards,
Rajith
On 11/16/06, Martin Ritchie <ri...@apache.org> wrote:
>
> The updated build.xml is now in the trunk and should address both
> points 1 and 5 of Brian's email.
>
> On 16/11/06, Martin Ritchie <ri...@apache.org> wrote:
> > Thanks Gordon I just realised that was what Brian was referring to.
> >
> > I also realised that windows has been creating the initial directory
> > for me. I thought the files were all included in a directory so I have
> > adjusted that aswell.
> >
> > On 16/11/06, Gordon Sim <gs...@redhat.com> wrote:
> > > Martin Ritchie wrote:
> > > > Brian,
> > > >
> > > > What version of ant were you using? I just checked out M1 and did
> > > > ant
> > > > ant std-release
> > > > and everything worked fine.
> > > > I'm using ant 1.6.5 with java 1.5.0_08 on XP.
> > > > I don't believe I have any local peculiarities that would impact the
> > > > builds.
> > > >
> > > > My only thoughts are that the systests where not checked out for
> some
> > > > reason. Can you do an svn update and try again for us.
> > >
> > > I believe the point is that the released source tarball doesn't build
> > > (i.e. it is not an issue of building from svn). I get the same error.
> > >
> > > It looks like the systests aren't part of the released source, but
> they
> > > are still referred to by the build file (i.e. the 'preparereleasesrc'
> > > copies only broker, client, common & cluster, but the build target
> > > iterates over all the listed modules of which systests is one).
> > >
> > > I'm not sure whether the intention is to ship systests, or whether we
> > > need to ensure that the shipped build file can cope without it being
> there.
> > >
> >
> >
> > --
> > Martin Ritchie
> >
>
>
> --
> Martin Ritchie
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Martin Ritchie <ri...@apache.org>.
The updated build.xml is now in the trunk and should address both
points 1 and 5 of Brian's email.
On 16/11/06, Martin Ritchie <ri...@apache.org> wrote:
> Thanks Gordon I just realised that was what Brian was referring to.
>
> I also realised that windows has been creating the initial directory
> for me. I thought the files were all included in a directory so I have
> adjusted that aswell.
>
> On 16/11/06, Gordon Sim <gs...@redhat.com> wrote:
> > Martin Ritchie wrote:
> > > Brian,
> > >
> > > What version of ant were you using? I just checked out M1 and did
> > > ant
> > > ant std-release
> > > and everything worked fine.
> > > I'm using ant 1.6.5 with java 1.5.0_08 on XP.
> > > I don't believe I have any local peculiarities that would impact the
> > > builds.
> > >
> > > My only thoughts are that the systests where not checked out for some
> > > reason. Can you do an svn update and try again for us.
> >
> > I believe the point is that the released source tarball doesn't build
> > (i.e. it is not an issue of building from svn). I get the same error.
> >
> > It looks like the systests aren't part of the released source, but they
> > are still referred to by the build file (i.e. the 'preparereleasesrc'
> > copies only broker, client, common & cluster, but the build target
> > iterates over all the listed modules of which systests is one).
> >
> > I'm not sure whether the intention is to ship systests, or whether we
> > need to ensure that the shipped build file can cope without it being there.
> >
>
>
> --
> Martin Ritchie
>
--
Martin Ritchie
Re: [ANN] The M1 Release Candidates are available for download
Posted by Martin Ritchie <ri...@apache.org>.
Thanks Gordon I just realised that was what Brian was referring to.
I also realised that windows has been creating the initial directory
for me. I thought the files were all included in a directory so I have
adjusted that aswell.
On 16/11/06, Gordon Sim <gs...@redhat.com> wrote:
> Martin Ritchie wrote:
> > Brian,
> >
> > What version of ant were you using? I just checked out M1 and did
> > ant
> > ant std-release
> > and everything worked fine.
> > I'm using ant 1.6.5 with java 1.5.0_08 on XP.
> > I don't believe I have any local peculiarities that would impact the
> > builds.
> >
> > My only thoughts are that the systests where not checked out for some
> > reason. Can you do an svn update and try again for us.
>
> I believe the point is that the released source tarball doesn't build
> (i.e. it is not an issue of building from svn). I get the same error.
>
> It looks like the systests aren't part of the released source, but they
> are still referred to by the build file (i.e. the 'preparereleasesrc'
> copies only broker, client, common & cluster, but the build target
> iterates over all the listed modules of which systests is one).
>
> I'm not sure whether the intention is to ship systests, or whether we
> need to ensure that the shipped build file can cope without it being there.
>
--
Martin Ritchie
Re: [ANN] The M1 Release Candidates are available for download
Posted by Gordon Sim <gs...@redhat.com>.
Martin Ritchie wrote:
> Brian,
>
> What version of ant were you using? I just checked out M1 and did
> ant
> ant std-release
> and everything worked fine.
> I'm using ant 1.6.5 with java 1.5.0_08 on XP.
> I don't believe I have any local peculiarities that would impact the
> builds.
>
> My only thoughts are that the systests where not checked out for some
> reason. Can you do an svn update and try again for us.
I believe the point is that the released source tarball doesn't build
(i.e. it is not an issue of building from svn). I get the same error.
It looks like the systests aren't part of the released source, but they
are still referred to by the build file (i.e. the 'preparereleasesrc'
copies only broker, client, common & cluster, but the build target
iterates over all the listed modules of which systests is one).
I'm not sure whether the intention is to ship systests, or whether we
need to ensure that the shipped build file can cope without it being there.
Re: [ANN] The M1 Release Candidates are available for download
Posted by Martin Ritchie <ri...@apache.org>.
Brian,
What version of ant were you using? I just checked out M1 and did
ant
ant std-release
and everything worked fine.
I'm using ant 1.6.5 with java 1.5.0_08 on XP.
I don't believe I have any local peculiarities that would impact the builds.
My only thoughts are that the systests where not checked out for some
reason. Can you do an svn update and try again for us.
Regards
--
Martin Ritchie
On 15/11/06, Rajith Attapattu <ra...@gmail.com> wrote:
> Hi Brian,,
>
> Thank you very much for the quick feedback, I really appreciate it.
>
> Regards,
>
> Rajith
>
> On 11/15/06, Brian McCallister <br...@apache.org> wrote:
> >
> > Some suggestions and potential issues when it hits the incubator PMC
> > vote:
> >
> > (looking at the source tarball)
> >
> > 1) Consider putting all the parts in a directory rather than have the
> > tarball unpack into the current working directory
> >
> > 2) Consider explaining about the incubation status in the README.
> > Generally we like the status to be prominent for users, in this case
> >
> > brianm@golem:/tmp/qpid$ grep -ir incubat *
> > RELEASE_NOTES.txt:Apache Incubator Qpid Java M1 Release Notes
> > src/java/build.properties:build.release.name=incubator
> > brianm@golem:/tmp/qpid$
> >
> > it isn't very prominent.
> >
> > 3) The Exolab JMS Compliance Test Suite might not be okay to include
> > in the distro as it is listed as (c) and all rights reserved. There
> > is a file in src/java/client/test/lib/jmscts/license.jmscts.txt which
> > implies that not all rights are, in fact reserved.
> >
> > 4) Where is the Jython license? (not referenced in LICENSE.txt like
> > others) It may not be relevant as I don't see Jython anywhere in the
> > actual distro, but it is listed as included in the NOTICE.txt
> >
> > 5) The build failed for me:
> > brianm@golem:/tmp/qpid/src/java$ ant
> > ... snipped ...
> > dist-bin:
> > [copy] Warning: /private/tmp/qpid/src/java/cluster/bin not
> > found.
> > [copy] Warning: /private/tmp/qpid/src/java/cluster/etc not
> > found.
> >
> > BUILD FAILED
> > /private/tmp/qpid/src/java/build.xml:46: The following error
> > occurred while executing this line:
> > /private/tmp/qpid/src/java/build.xml:38: Invalid file: /private/
> > tmp/qpid/src/java/systests
> >
> >
> > Glad to see a release candidate so soon!
> >
> > -Brian
> >
> > On Nov 15, 2006, at 11:45 AM, Rajith Attapattu wrote:
> >
> > > Hi All,
> > >
> > > The M1 release candidates are available for download at the following
> > > location.
> > >
> > > http://people.apache.org/~rajith/qpid-release/
> > >
> > > Regards,
> > >
> > > Rajith Attapattu
> >
> >
>
>
--
Martin Ritchie
Re: [ANN] The M1 Release Candidates are available for download
Posted by Marnie McCormack <ma...@googlemail.com>.
Hi All,
On the jython front - I'll remove the entry in notice for it as since the
management modules were removed last night it is (as Brian spotted) no
longer in use !
Thanks,
Marnie
On 11/16/06, Marnie McCormack <ma...@googlemail.com> wrote:
>
> Hi Rajith & Brian,
>
> I don't *think* there is anything in the CTS license that is an issue. I
> hadn't appreciated that the 'All Rights Reserved' line in the copyright was
> an issue for us ?
>
> Cliff - could you kindly take a look and advise for us please - the
> license info is at:
>
> http://jmscts.sourceforge.net/license.html
>
> Thanks in advance,
> Marnie
>
>
> On 11/15/06, Rajith Attapattu <ra...@gmail.com> wrote:
> >
> > Hi Brian,,
> >
> > Thank you very much for the quick feedback, I really appreciate it.
> >
> > Regards,
> >
> > Rajith
> >
> > On 11/15/06, Brian McCallister <br...@apache.org> wrote:
> > >
> > > Some suggestions and potential issues when it hits the incubator PMC
> > > vote:
> > >
> > > (looking at the source tarball)
> > >
> > > 1) Consider putting all the parts in a directory rather than have the
> > > tarball unpack into the current working directory
> > >
> > > 2) Consider explaining about the incubation status in the README.
> > > Generally we like the status to be prominent for users, in this case
> > >
> > > brianm@golem:/tmp/qpid$ grep -ir incubat *
> > > RELEASE_NOTES.txt:Apache Incubator Qpid Java M1 Release Notes
> > > src/java/build.properties:build.release.name=incubator
> > > brianm@golem:/tmp/qpid$
> > >
> > > it isn't very prominent.
> > >
> > > 3) The Exolab JMS Compliance Test Suite might not be okay to include
> > > in the distro as it is listed as (c) and all rights reserved. There
> > > is a file in src/java/client/test/lib/jmscts/license.jmscts.txt which
> > > implies that not all rights are, in fact reserved.
> > >
> > > 4) Where is the Jython license? (not referenced in LICENSE.txt like
> > > others) It may not be relevant as I don't see Jython anywhere in the
> > > actual distro, but it is listed as included in the NOTICE.txt
> > >
> > > 5) The build failed for me:
> > > brianm@golem:/tmp/qpid/src/java$ ant
> > > ... snipped ...
> > > dist-bin:
> > > [copy] Warning: /private/tmp/qpid/src/java/cluster/bin not
> > > found.
> > > [copy] Warning: /private/tmp/qpid/src/java/cluster/etc not
> > > found.
> > >
> > > BUILD FAILED
> > > /private/tmp/qpid/src/java/build.xml:46: The following error
> > > occurred while executing this line:
> > > /private/tmp/qpid/src/java/build.xml:38: Invalid file: /private/
> > > tmp/qpid/src/java/systests
> > >
> > >
> > > Glad to see a release candidate so soon!
> > >
> > > -Brian
> > >
> > > On Nov 15, 2006, at 11:45 AM, Rajith Attapattu wrote:
> > >
> > > > Hi All,
> > > >
> > > > The M1 release candidates are available for download at the
> > following
> > > > location.
> > > >
> > > > http://people.apache.org/~rajith/qpid-release/
> > > >
> > > > Regards,
> > > >
> > > > Rajith Attapattu
> > >
> > >
> >
> >
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Rajith Attapattu <ra...@gmail.com>.
Marnie,
the thread on "[ANN] Release Candidate"
--rajith
On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> Hi Rajith,
>
> Can you point me at the thread you want to use please ?
>
> Marnie
>
>
> On 11/21/06, Rajith Attapattu <ra...@gmail.com> wrote:
> >
> > Marnie,
> >
> > Cliff has a list of items in about legal stuff on a different thread.
> > Lets continue the disscussion there.
> >
> > Regards,
> >
> > Rajith
> >
> > On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> > > Great - I thought/hoped it was ok.
> > >
> > > Thanks Cliff.
> > >
> > > Rajith - can you close this point please ? Thanks !
> > >
> > > Marnie
> > >
> > >
> > > On 11/21/06, Cliff Schmidt <cl...@gmail.com> wrote:
> > > >
> > > > On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> > > > > Steve,
> > > > >
> > > > > FYI I asked Cliff to look at this from a legal standpoint.
> > > >
> > > > Carl's answer quoted below was exactly right.
> > > >
> > > > Cliff
> > > >
> > > > > On 11/17/06, Carl Trieloff <cc...@redhat.com> wrote:
> > > > > > > These additions don't seem onerous but IANAL. Point 4 doesn't
> > apply
> > > > as
> > > > > > > we are not deriving from it, only using it. Point 5 would be
> > > > satisfied
> > > > > > > by a prominent thank you note in our README file or on our Wiki
> > I
> > > > > > > imagine. Note that the Exolab project no longer exists...
> > > > > > >
> > > > > > Point 5 should be able to be handled by NOTICE.txt. - checked and
> > it
> > > > is
> > > > > > in there.
> > > >
> > >
> > >
> >
>
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Marnie McCormack <ma...@googlemail.com>.
Hi Rajith,
Can you point me at the thread you want to use please ?
Marnie
On 11/21/06, Rajith Attapattu <ra...@gmail.com> wrote:
>
> Marnie,
>
> Cliff has a list of items in about legal stuff on a different thread.
> Lets continue the disscussion there.
>
> Regards,
>
> Rajith
>
> On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> > Great - I thought/hoped it was ok.
> >
> > Thanks Cliff.
> >
> > Rajith - can you close this point please ? Thanks !
> >
> > Marnie
> >
> >
> > On 11/21/06, Cliff Schmidt <cl...@gmail.com> wrote:
> > >
> > > On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> > > > Steve,
> > > >
> > > > FYI I asked Cliff to look at this from a legal standpoint.
> > >
> > > Carl's answer quoted below was exactly right.
> > >
> > > Cliff
> > >
> > > > On 11/17/06, Carl Trieloff <cc...@redhat.com> wrote:
> > > > > > These additions don't seem onerous but IANAL. Point 4 doesn't
> apply
> > > as
> > > > > > we are not deriving from it, only using it. Point 5 would be
> > > satisfied
> > > > > > by a prominent thank you note in our README file or on our Wiki
> I
> > > > > > imagine. Note that the Exolab project no longer exists...
> > > > > >
> > > > > Point 5 should be able to be handled by NOTICE.txt. - checked and
> it
> > > is
> > > > > in there.
> > >
> >
> >
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Rajith Attapattu <ra...@gmail.com>.
Marnie,
Cliff has a list of items in about legal stuff on a different thread.
Lets continue the disscussion there.
Regards,
Rajith
On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> Great - I thought/hoped it was ok.
>
> Thanks Cliff.
>
> Rajith - can you close this point please ? Thanks !
>
> Marnie
>
>
> On 11/21/06, Cliff Schmidt <cl...@gmail.com> wrote:
> >
> > On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> > > Steve,
> > >
> > > FYI I asked Cliff to look at this from a legal standpoint.
> >
> > Carl's answer quoted below was exactly right.
> >
> > Cliff
> >
> > > On 11/17/06, Carl Trieloff <cc...@redhat.com> wrote:
> > > > > These additions don't seem onerous but IANAL. Point 4 doesn't apply
> > as
> > > > > we are not deriving from it, only using it. Point 5 would be
> > satisfied
> > > > > by a prominent thank you note in our README file or on our Wiki I
> > > > > imagine. Note that the Exolab project no longer exists...
> > > > >
> > > > Point 5 should be able to be handled by NOTICE.txt. - checked and it
> > is
> > > > in there.
> >
>
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Marnie McCormack <ma...@googlemail.com>.
Great - I thought/hoped it was ok.
Thanks Cliff.
Rajith - can you close this point please ? Thanks !
Marnie
On 11/21/06, Cliff Schmidt <cl...@gmail.com> wrote:
>
> On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> > Steve,
> >
> > FYI I asked Cliff to look at this from a legal standpoint.
>
> Carl's answer quoted below was exactly right.
>
> Cliff
>
> > On 11/17/06, Carl Trieloff <cc...@redhat.com> wrote:
> > > > These additions don't seem onerous but IANAL. Point 4 doesn't apply
> as
> > > > we are not deriving from it, only using it. Point 5 would be
> satisfied
> > > > by a prominent thank you note in our README file or on our Wiki I
> > > > imagine. Note that the Exolab project no longer exists...
> > > >
> > > Point 5 should be able to be handled by NOTICE.txt. - checked and it
> is
> > > in there.
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Cliff Schmidt <cl...@gmail.com>.
On 11/21/06, Marnie McCormack <ma...@googlemail.com> wrote:
> Steve,
>
> FYI I asked Cliff to look at this from a legal standpoint.
Carl's answer quoted below was exactly right.
Cliff
> On 11/17/06, Carl Trieloff <cc...@redhat.com> wrote:
> > > These additions don't seem onerous but IANAL. Point 4 doesn't apply as
> > > we are not deriving from it, only using it. Point 5 would be satisfied
> > > by a prominent thank you note in our README file or on our Wiki I
> > > imagine. Note that the Exolab project no longer exists...
> > >
> > Point 5 should be able to be handled by NOTICE.txt. - checked and it is
> > in there.
Re: [ANN] The M1 Release Candidates are available for download
Posted by Marnie McCormack <ma...@googlemail.com>.
Steve,
FYI I asked Cliff to look at this from a legal standpoint.
Marnie
On 11/17/06, Carl Trieloff <cc...@redhat.com> wrote:
>
>
>
>
> >
> > These additions don't seem onerous but IANAL. Point 4 doesn't apply as
> > we are not deriving from it, only using it. Point 5 would be satisfied
> > by a prominent thank you note in our README file or on our Wiki I
> > imagine. Note that the Exolab project no longer exists...
> >
> Point 5 should be able to be handled by NOTICE.txt. - checked and it is
> in there.
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Carl Trieloff <cc...@redhat.com>.
>
> These additions don't seem onerous but IANAL. Point 4 doesn't apply as
> we are not deriving from it, only using it. Point 5 would be satisfied
> by a prominent thank you note in our README file or on our Wiki I
> imagine. Note that the Exolab project no longer exists...
>
Point 5 should be able to be handled by NOTICE.txt. - checked and it is
in there.
Re: [ANN] The M1 Release Candidates are available for download
Posted by Steven Shaw <st...@gmail.com>.
On 16/11/06, Marnie McCormack <ma...@googlemail.com> wrote:
> http://jmscts.sourceforge.net/license.html
That's a very slightly modified "New BSD" license which is allowed on
http://www.apache.org/legal/3party.html
which points to the definition here:
http://opensource.org/licenses/bsd-license.php
The "All rights reserved" is not a modification! It's a standard part
of the BSD license.
The additions are points (4) and (5):
==begin===
4. Products derived from this Software may not be called "Exolab"
nor may "Exolab" appear in their names without prior written
permission of Exoffice Technologies. Exolab is a registered
trademark of Exoffice Technologies.
5. Due credit should be given to the Exolab Project
(http://www.exolab.org/).
===end===
These additions don't seem onerous but IANAL. Point 4 doesn't apply as
we are not deriving from it, only using it. Point 5 would be satisfied
by a prominent thank you note in our README file or on our Wiki I
imagine. Note that the Exolab project no longer exists...
Regards,
Steve.
Re: [ANN] The M1 Release Candidates are available for download
Posted by Marnie McCormack <ma...@googlemail.com>.
Hi Rajith & Brian,
I don't *think* there is anything in the CTS license that is an issue. I
hadn't appreciated that the 'All Rights Reserved' line in the copyright was
an issue for us ?
Cliff - could you kindly take a look and advise for us please - the license
info is at:
http://jmscts.sourceforge.net/license.html
Thanks in advance,
Marnie
On 11/15/06, Rajith Attapattu <ra...@gmail.com> wrote:
>
> Hi Brian,,
>
> Thank you very much for the quick feedback, I really appreciate it.
>
> Regards,
>
> Rajith
>
> On 11/15/06, Brian McCallister <br...@apache.org> wrote:
> >
> > Some suggestions and potential issues when it hits the incubator PMC
> > vote:
> >
> > (looking at the source tarball)
> >
> > 1) Consider putting all the parts in a directory rather than have the
> > tarball unpack into the current working directory
> >
> > 2) Consider explaining about the incubation status in the README.
> > Generally we like the status to be prominent for users, in this case
> >
> > brianm@golem:/tmp/qpid$ grep -ir incubat *
> > RELEASE_NOTES.txt:Apache Incubator Qpid Java M1 Release Notes
> > src/java/build.properties:build.release.name=incubator
> > brianm@golem:/tmp/qpid$
> >
> > it isn't very prominent.
> >
> > 3) The Exolab JMS Compliance Test Suite might not be okay to include
> > in the distro as it is listed as (c) and all rights reserved. There
> > is a file in src/java/client/test/lib/jmscts/license.jmscts.txt which
> > implies that not all rights are, in fact reserved.
> >
> > 4) Where is the Jython license? (not referenced in LICENSE.txt like
> > others) It may not be relevant as I don't see Jython anywhere in the
> > actual distro, but it is listed as included in the NOTICE.txt
> >
> > 5) The build failed for me:
> > brianm@golem:/tmp/qpid/src/java$ ant
> > ... snipped ...
> > dist-bin:
> > [copy] Warning: /private/tmp/qpid/src/java/cluster/bin not
> > found.
> > [copy] Warning: /private/tmp/qpid/src/java/cluster/etc not
> > found.
> >
> > BUILD FAILED
> > /private/tmp/qpid/src/java/build.xml:46: The following error
> > occurred while executing this line:
> > /private/tmp/qpid/src/java/build.xml:38: Invalid file: /private/
> > tmp/qpid/src/java/systests
> >
> >
> > Glad to see a release candidate so soon!
> >
> > -Brian
> >
> > On Nov 15, 2006, at 11:45 AM, Rajith Attapattu wrote:
> >
> > > Hi All,
> > >
> > > The M1 release candidates are available for download at the following
> > > location.
> > >
> > > http://people.apache.org/~rajith/qpid-release/
> > >
> > > Regards,
> > >
> > > Rajith Attapattu
> >
> >
>
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Rajith Attapattu <ra...@gmail.com>.
Hi Brian,,
Thank you very much for the quick feedback, I really appreciate it.
Regards,
Rajith
On 11/15/06, Brian McCallister <br...@apache.org> wrote:
>
> Some suggestions and potential issues when it hits the incubator PMC
> vote:
>
> (looking at the source tarball)
>
> 1) Consider putting all the parts in a directory rather than have the
> tarball unpack into the current working directory
>
> 2) Consider explaining about the incubation status in the README.
> Generally we like the status to be prominent for users, in this case
>
> brianm@golem:/tmp/qpid$ grep -ir incubat *
> RELEASE_NOTES.txt:Apache Incubator Qpid Java M1 Release Notes
> src/java/build.properties:build.release.name=incubator
> brianm@golem:/tmp/qpid$
>
> it isn't very prominent.
>
> 3) The Exolab JMS Compliance Test Suite might not be okay to include
> in the distro as it is listed as (c) and all rights reserved. There
> is a file in src/java/client/test/lib/jmscts/license.jmscts.txt which
> implies that not all rights are, in fact reserved.
>
> 4) Where is the Jython license? (not referenced in LICENSE.txt like
> others) It may not be relevant as I don't see Jython anywhere in the
> actual distro, but it is listed as included in the NOTICE.txt
>
> 5) The build failed for me:
> brianm@golem:/tmp/qpid/src/java$ ant
> ... snipped ...
> dist-bin:
> [copy] Warning: /private/tmp/qpid/src/java/cluster/bin not
> found.
> [copy] Warning: /private/tmp/qpid/src/java/cluster/etc not
> found.
>
> BUILD FAILED
> /private/tmp/qpid/src/java/build.xml:46: The following error
> occurred while executing this line:
> /private/tmp/qpid/src/java/build.xml:38: Invalid file: /private/
> tmp/qpid/src/java/systests
>
>
> Glad to see a release candidate so soon!
>
> -Brian
>
> On Nov 15, 2006, at 11:45 AM, Rajith Attapattu wrote:
>
> > Hi All,
> >
> > The M1 release candidates are available for download at the following
> > location.
> >
> > http://people.apache.org/~rajith/qpid-release/
> >
> > Regards,
> >
> > Rajith Attapattu
>
>
Re: [ANN] The M1 Release Candidates are available for download
Posted by Brian McCallister <br...@apache.org>.
Some suggestions and potential issues when it hits the incubator PMC
vote:
(looking at the source tarball)
1) Consider putting all the parts in a directory rather than have the
tarball unpack into the current working directory
2) Consider explaining about the incubation status in the README.
Generally we like the status to be prominent for users, in this case
brianm@golem:/tmp/qpid$ grep -ir incubat *
RELEASE_NOTES.txt:Apache Incubator Qpid Java M1 Release Notes
src/java/build.properties:build.release.name=incubator
brianm@golem:/tmp/qpid$
it isn't very prominent.
3) The Exolab JMS Compliance Test Suite might not be okay to include
in the distro as it is listed as (c) and all rights reserved. There
is a file in src/java/client/test/lib/jmscts/license.jmscts.txt which
implies that not all rights are, in fact reserved.
4) Where is the Jython license? (not referenced in LICENSE.txt like
others) It may not be relevant as I don't see Jython anywhere in the
actual distro, but it is listed as included in the NOTICE.txt
5) The build failed for me:
brianm@golem:/tmp/qpid/src/java$ ant
... snipped ...
dist-bin:
[copy] Warning: /private/tmp/qpid/src/java/cluster/bin not
found.
[copy] Warning: /private/tmp/qpid/src/java/cluster/etc not
found.
BUILD FAILED
/private/tmp/qpid/src/java/build.xml:46: The following error
occurred while executing this line:
/private/tmp/qpid/src/java/build.xml:38: Invalid file: /private/
tmp/qpid/src/java/systests
Glad to see a release candidate so soon!
-Brian
On Nov 15, 2006, at 11:45 AM, Rajith Attapattu wrote:
> Hi All,
>
> The M1 release candidates are available for download at the following
> location.
>
> http://people.apache.org/~rajith/qpid-release/
>
> Regards,
>
> Rajith Attapattu