[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [iam-dev] Advice on how to request pre-req dependency for the Maven Embedder
|
+1
Wayne
Abel Muiño Vizcaino wrote:
My understanding from the public conversations in the past days is
that a "gold version" is whatever that we (IAM) will ship for the 1.0
release.
Advice from the ip team in november (private e-mail) was a bit different:
Regarding the last point of delaying the submission of CQs for Maven
components (29 source/binary dependencies), we typically do not
review alpha or beta code unless there are extenuating circumstances
involved which are dealt with on a case by case basis. However, if
any of the components are in RC stages, we would recommend that you
enter the CQs now as the NonEpl due diligence queue is quite long.
For third party code where a full release is imminent, you can enter
the CQ now with the latest version and update the CQ when the code is
fully released as long as the CQ has not yet been reviewed – this
will ensure you are in the queue.
Anyway, since the embedder is entering the RC stage (with alpha-1), I
think it is the right time for submitting the CQs, and valid whatever
the interpretation of "Gold version" is.
We can update the code attached to CQs while we are waiting for full
review if we need to.
My suggestion would be to finish the work on repackaging the embedder
that's currently going on and update it with alpha-1. Then submit CQs
for all the jars involved and move it all to eclipse upon preliminary
IP approval (which is usually quite fast).
Opinions?
El 11/12/2008, a las 21:19, Joakim Erdfelt escribió:
Narrowing down the ambiguity significantly.
What constitutes a "Gold version"?
Is that something that the 3rd party project owners (PMC if it
exists) decides? Or something that Eclipse decides?
(read on, only if you care about the rationale)
It can't be based off of the version specified on the artifact,
otherwise several entries in the Orbit DB wouldn't be valid.
Using
http://download.eclipse.org/tools/orbit/downloads/drops/R20080807152315/
The following already approved (in orbit) jars have not had a 1.0
release yet.
com.jcraft.jsch 0.1.31
java_cup.runtime 0.10.0
org.apache.commons.discovery 0.2.0
org.apache.ws.jaxme 0.5.1
The way I would take "Gold version" is whatever the project owner
(PMC) says is stable for mass consumption.
- Joakim
On Thu, Dec 11, 2008 at 12:53 PM, Wayne Beaton <wayne@xxxxxxxxxxx>
wrote:
I've consulted with the IP Due Diligence team on this issue. Here's
their response:
It seems in this case, the project can only continue development if
the Maven Embedder is checked into the Eclipse repository.
If this is true, the project may go ahead and raise the CQ. We will
check licensing compatibility as well as provenance. If those two
pass, the CQ can be approved for checkin based on Parallel IP with
the understanding that full due diligence will not be completed until
a Gold version is released and attached at a later date to the CQ.
We have noted that the project is also referring to Maven Embedder
dependencies which do not appear to be Apache hosted. As such, there
may be a requirement for multiple CQs in this case.
Of course, the project will have to realize they cannot release with
any code that has not been fully reviewed and approved.
Does this make sense?
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).
------------------------------------------------------------------------
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev
------------------------------------------------------------------------
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev