What constitutes "a release" in the eyes of Eclipse?
I've had a hard time with this philosophical difference in opinion between
Eclipse and Maven.
Eclipse apparently doesn't have a "not ready yet" or "unstable" version
indicator.
>From what I can tell, every build is "a release" in the Eclipse world.
Within maven, there are 2 levels of release.
The lowest level being SNAPSHOT, which indicates actively being developed
code.
A SNAPSHOT has no other implied meaning other than "being developed".
SNAPSHOT artifacts are deployed onto an artifact repository designated for
SNAPSHOT quality code only [1].
To progress out from SNAPSHOT you implement the maven release process [2],
using the maven-release-plugin [3].
The release process, simply stated, fixes a SNAPSHOT in time with a fixed
version indicator, and deploys it to an artifact repository designated for
RELEASE quality code.
However, this fixed version indicator can be anything, including verbiage
such as "alpha", "beta", "milestone", "rc", etc.
These keywords are not standardized, nor have any meaning to maven or other
projects wanting to use the dependency, it is simply a decision by the
project to use those keywords.
In the case of maven projects, these keywords are ultimately meaningless, as
the code has already gone through the release process with a fixed in time
quality of code and binary.
NOTE: The release process updates all versions to the one chosen during the
release process by the release coordinator. This version is then used
internally in all metadata and source code, as well as for source code
control tagging, and automated release notes generation from the bug
tracking system.
My question is then, if a release is made, using the maven-release-plugin,
using the maven release process, which in turn releases the code in question
to an artifact repository designated for release quality code, with a
release tag in source control, and a full set of release notes, is this code
now considered "a release" in the eyes of Eclipse.org?
[1]
http://people.apache.org/repo/m2-snapshot-repository/
[2]
http://maven.apache.org/developers/release/releasing.html
[3]
http://maven.apache.org/plugins/maven-release-plugin/
- Joakim Erdfelt
On Wed, Dec 10, 2008 at 8:34 AM, Wayne Beaton <
wayne@xxxxxxxxxxx> wrote:
Any idea how far away the maven embedder is from a real release?
Wayne
Abel Muiño wrote:
Hello PMC,
The IAM (http://www.eclipse.org/iam) team would like to request pmc
approval
and guidance for declaring a pre-req dependency on the maven embedder.
The maven embedder is a set of libraries that allow the use of maven from
a
host application (in this case, IAM).
The maven embedder is still under development (i.e. not released) so we
are
asking for a pre-req dependency to be able to use snapshots of current
development. Our goal will be to process CQs for the embedder components
once they reach the beta or release status, as adviced by the IP team.
The maven embedder is part of maven 3.0 and developed at the apache
foundation. Its dependencies are either ASL or MIT licensed.
The packaging of the embedder components as an eclipse bundle (and
feature)
is currently done on a non-eclipse project at googlecode (
http://q4e.googlecode.com). Another packaging is also available from the
m2e
project (also outside of eclipse).
------------------------------------------------------------------------
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev
