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/07 18:15:47 UTC
Re: Release artifacts
Hi Folks,
This is my understanding of how the release artifacts should be structured.
Mentors, if u guys see anything wrong please shout :)
We need to do a binary and a source distribution as per the release
guidelines posted by apache.
Here is the proposed naming strucute for the jars for qpid.
apache-qpid-common-M1.jar
apache-qpid-broker-M1.jar
apache-qpid-client-M1.jar
apache-qpid-management-M1.jar
apache-qpid-src-M1.zip and a apache-qpid-src-M1.tar.gz for source
apache-qpid-std-bin-M1.zip and a apache-qpid-std-bin-M1.tar.gz
Ant tasks or maven goals
--------------------------------------
Ant or maven we need to provide a way for people who download the src and
for us to build these release artifacts.
So we need to create two ant tasks (or maven goals) called std-src-dist and
stad-bin-dist which will create the above release artifacts.
Source distribtuion
-----------------------------
a) A compilable source tree from the tagged version which is used for the
binary release.
b) We need to have NOTICE.txt, README.txt, LICENSE.txt and release_notes in
the top level directory
c) We need to get the licensing for all dependencies as we are currently
using ant and have a static repo
Standard Binary distribution
----------------------------------------
release_notes, README, NOTICE and LICENSE files should be at the top level
directory.
So for std bin distribtution here is the structure.
The idea is to have it running out of the box.
|-- (all these text files)
|
|-- bin (contains all scripts)
|
|-- doc (java doc and some basic docs)
|
|-- conf
|
|-- log
|
|-- lib (with licenses, this will include our jars as well)
Regards,
Rajith
Re: Release artifacts
Posted by Gordon Sim <gs...@redhat.com>.
Rajith Attapattu wrote:
> Here is the proposed naming strucute for the jars for qpid.
>
> apache-qpid-common-M1.jar
> apache-qpid-broker-M1.jar
> apache-qpid-client-M1.jar
> apache-qpid-management-M1.jar
>
> apache-qpid-src-M1.zip and a apache-qpid-src-M1.tar.gz for source
> apache-qpid-std-bin-M1.zip and a apache-qpid-std-bin-M1.tar.gz
We probably need to include the language in the tars (e.g. java). Do we
also want to differentiate between client only and broker + client
distributions, or is only the latter required?
Fwd: Release artifacts
Posted by Rajith Attapattu <ra...@gmail.com>.
Thanks Dan, I totaly missed that part and thanks for reminding about the
disclamer that goes into the META-INF.
So as part of the build we need to ensure that we slip in the NOTICE and
LICENSE goes in to META-INF for all of qpid jars.
It is also recomended to add the minumum java version as an entry in the
manifest
So something like X-Compile-Source-JDK: 1.4 .
This maybe important bcos AFIK for broker the minimum is 1.5 and for client
it's 1.4
Regards,
Rajith
On 11/7/06, Daniel Kulp <daniel.kulp@iona.com > wrote:
> On Tuesday November 07 2006 12:15 pm, Rajith Attapattu wrote:
> > Here is the proposed naming strucute for the jars for qpid.
> >
> > apache-qpid-common-M1.jar
> > apache-qpid-broker-M1.jar
> > apache-qpid-client-M1.jar
> > apache-qpid-management-M1.jar
>
> I would HIGHLY suggest naming them like they would be named if built from
> maven to ease the transition later. Thus:
>
> apache-qpid-common-1.0-incubator-M1.jar
>
> That would be artifact id of apache-qpid-common and version number of
> 1.0-incubator-M1 .
>
>
> > apache-qpid-src-M1.zip and a apache-qpid-src-M1.tar.gz for source
> > apache-qpid-std-bin-M1.zip and a apache-qpid-std-bin-M1.tar.gz
>
> Again, use the full version number of 1.0-incubator-M1.
>
> The incubator folks will complain if the artifacts don't say "incubator"
> in them someplace. Yoko, Tuscany, CXF, and others have all gone with a
> version number of "#.#-incubator[-M#]" scheme. Being consistent is
> probably good.
>
>
> > Ant tasks or maven goals
> > --------------------------------------
> > Ant or maven we need to provide a way for people who download the src
> > and for us to build these release artifacts.
> > So we need to create two ant tasks (or maven goals) called std-src-dist
> > and stad-bin-dist which will create the above release artifacts.
> >
> > Source distribtuion
> > -----------------------------
> > a) A compilable source tree from the tagged version which is used for
> > the binary release.
> > b) We need to have NOTICE.txt, README.txt, LICENSE.txt and
> > release_notes in the top level directory
> > c) We need to get the licensing for all dependencies as we are
> > currently using ant and have a static repo
> >
> > Standard Binary distribution
> > ----------------------------------------
> > release_notes, README, NOTICE and LICENSE files should be at the top
> > level directory.
>
> In the META-INF dir of each jar, you also need to have a DISCLAIMER
> (incubator disclaimer thing), the NOTICE, and the LICENSE file.
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> daniel.kulp@iona.com
>
Re: Release artifacts
Posted by Daniel Kulp <da...@iona.com>.
On Tuesday November 07 2006 12:15 pm, Rajith Attapattu wrote:
> Here is the proposed naming strucute for the jars for qpid.
>
> apache-qpid-common-M1.jar
> apache-qpid-broker-M1.jar
> apache-qpid-client-M1.jar
> apache-qpid-management-M1.jar
I would HIGHLY suggest naming them like they would be named if built from
maven to ease the transition later. Thus:
apache-qpid-common-1.0-incubator-M1.jar
That would be artifact id of apache-qpid-common and version number of
1.0-incubator-M1.
> apache-qpid-src-M1.zip and a apache-qpid-src-M1.tar.gz for source
> apache-qpid-std-bin-M1.zip and a apache-qpid-std-bin-M1.tar.gz
Again, use the full version number of 1.0-incubator-M1.
The incubator folks will complain if the artifacts don't say "incubator"
in them someplace. Yoko, Tuscany, CXF, and others have all gone with a
version number of "#.#-incubator[-M#]" scheme. Being consistent is
probably good.
> Ant tasks or maven goals
> --------------------------------------
> Ant or maven we need to provide a way for people who download the src
> and for us to build these release artifacts.
> So we need to create two ant tasks (or maven goals) called std-src-dist
> and stad-bin-dist which will create the above release artifacts.
>
> Source distribtuion
> -----------------------------
> a) A compilable source tree from the tagged version which is used for
> the binary release.
> b) We need to have NOTICE.txt, README.txt, LICENSE.txt and
> release_notes in the top level directory
> c) We need to get the licensing for all dependencies as we are
> currently using ant and have a static repo
>
> Standard Binary distribution
> ----------------------------------------
> release_notes, README, NOTICE and LICENSE files should be at the top
> level directory.
In the META-INF dir of each jar, you also need to have a DISCLAIMER
(incubator disclaimer thing), the NOTICE, and the LICENSE file.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com