[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [technology-pmc] All the IAM CQs
|
Eugene is part of m2e development team and, AFAIK, their position is to wait some more time.
These CQs can not go into Orbit until they get full review and, as Wayne has already reported, that will take some time. Anyway, Eclipse projects are allowed to reuse deliverables produced by mature projects, so if IAM can cut a 1.0 release, all those artifacts will be available for m2e too.
And they can also piggyback on those CQs so they can save some time.
On Tue, Feb 24, 2009 at 5:35 PM, Jeff McAffer
<jeff@xxxxxxxxxxxxxxxxx> wrote:
as a point of interest, doesn't m2e have many of the same/similar requirements? What are they doing? Is this stuff in Orbit?
Jeff
Wayne Beaton wrote:
Abel, the IP team, and I discussed this over several weeks and have decided that this is the best way for the project to proceed. Of course, we didn't realize that there'd be 40 bajillion CQs, but maybe we should have asked that question...
FWIW, the backlog with IP DD is such that these CQs will not get a full review for some time.
Wayne
Eugene Kuleshov wrote:
Abel,
Number of those dependencies will either change or go away all together,
so it is premature to process them for any IP issues, because it will cause
unnecessary overhead to PMC and the legal team.
regards,
Eugene
On Tue, Feb 24, 2009 at 3:38 AM, Abel Muiño <amuino@xxxxxxxxx> wrote:
I'm responding in behalf of Allan as IAM project lead.
The CQs being filed are all dependencies of the maven embedder and yes, we
intend to redistribute them. For simplicity, them all will be required.
We have no current plans for getting the packages into Orbit. The embedder
has complex classloading issues so we have not settled on a bundle packaging
just yet (probably all the embedder dependencies will go on a single bundle,
but that's not set on stone yet... we need to test what works best for us
and other projects).
Maybe this dependency tree will help in clearing things out. We can file a
"meta-CQ" with this information if needed (if you see it as garbage, try
using a fixed-width font).
\- org.apache.maven:maven-embedder:jar:3.0-alpha-2:compile
+- org.apache.maven:maven-core:jar:3.0-alpha-2:compile
| +- org.apache.maven:maven-lifecycle:jar:3.0-alpha-2:compile
| +- org.apache.maven:maven-reporting-api:jar:3.0-alpha-2:compile
| | \- org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-9:compile
| +- org.apache.maven:maven-model:jar:3.0-alpha-2:compile
| +- org.apache.maven:maven-compat:jar:3.0-alpha-2:compile
| +- org.apache.maven:maven-plugin-api:jar:3.0-alpha-2:compile
| +- org.apache.maven:maven-project-builder:jar:3.0-alpha-2:compile
| +-
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-6:compile
| +- org.codehaus.plexus:plexus-interpolation:jar:1.1:compile
| +- org.codehaus.plexus:plexus-utils:jar:1.5.6:compile
| +- org.codehaus.plexus:plexus-classworlds:jar:1.3:compile
| +-
org.codehaus.plexus:plexus-component-annotations:jar:1.0-beta-3.0.5:compile
| +- org.sonatype.plexus:plexus-plugin-manager:jar:1.0-alpha-1:compile
| | +-
org.apache.maven.mercury:mercury-plexus:jar:1.0.0-alpha-2:compile
| | | +-
org.apache.maven.mercury:mercury-repo-remote-m2:jar:1.0.0-alpha-2:compile
| | | | +-
org.apache.maven.mercury:mercury-repo-api:jar:1.0.0-alpha-2:compile
| | | | | \-
org.apache.maven.mercury:mercury-transport-api:jar:1.0.0-alpha-2:compile
| | | | | \-
org.apache.maven.mercury:mercury-crypto-api:jar:1.0.0-alpha-2:compile
| | | | +-
org.apache.maven.mercury:mercury-transport-http:jar:1.0.0-alpha-2:compile
| | | | | +- org.mortbay.jetty:jetty-client:jar:6.1.12:compile
| | | | | | +-
org.mortbay.jetty:jetty-sslengine:jar:6.1.12:compile
| | | | | | +- org.mortbay.jetty:jetty:jar:6.1.12:compile
| | | | | | \- org.mortbay.jetty:jetty-util:jar:6.1.12:compile
| | | | | +- org.mortbay.jetty:servlet-api-2.5:jar:6.1.12:compile
| | | | | \-
org.apache.maven.mercury:mercury-crypto-basic:jar:1.0.0-alpha-2:compile
| | | | | +- bouncycastle:bcprov-jdk15:jar:140:compile
| | | | | \- bouncycastle:bcpg-jdk15:jar:140:compile
| | | | +-
org.apache.maven.mercury:mercury-md-shared:jar:1.0.0-alpha-2:compile
| | | | | \-
org.apache.maven.mercury:mercury-util:jar:1.0.0-alpha-2:compile
| | | | \-
org.apache.maven.mercury:mercury-repo-local-m2:jar:1.0.0-alpha-2:compile
| | | +-
org.apache.maven.mercury:mercury-repo-virtual:jar:1.0.0-alpha-2:compile
| | | | \-
org.apache.maven.mercury:mercury-repo-cache-fs:jar:1.0.0-alpha-2:compile
| | | +-
org.apache.maven.mercury:mercury-md-sat:jar:1.0.0-alpha-2:compile
| | | | +- org.sat4j:org.sat4j.core:jar:2.0.4:compile
| | | | +- org.sat4j:org.sat4j.pb:jar:2.0.4:compile
| | | | \-
org.apache.maven.mercury:mercury-event:jar:1.0.0-alpha-2:compile
| | | +-
org.apache.maven.mercury:mercury-logging:jar:1.0.0-alpha-2:compile
| | | \- org.codehaus.plexus:plexus-lang:jar:1.1:compile
| | \- org.slf4j:slf4j-jdk14:jar:1.5.3:compile
| | \- org.slf4j:slf4j-api:jar:1.5.3:compile
| +- org.apache.maven:maven-mercury:jar:3.0-alpha-2:compile
| | +-
org.apache.maven.mercury:mercury-artifact:jar:1.0.0-alpha-2:compile
| | \-
org.apache.maven.mercury:mercury-external:jar:1.0.0-alpha-2:compile
| \- org.sonatype.spice:model-builder:jar:1.3:compile
| \- stax:stax-api:jar:1.0.1:compile
+- org.apache.maven:maven-project:jar:3.0-alpha-2:compile
| \- org.codehaus.woodstox:wstx-asl:jar:3.2.6:compile
+- org.apache.maven:maven-toolchain:jar:3.0-alpha-2:compile
+-
org.codehaus.plexus:plexus-container-default:jar:1.0-beta-3.0.5:compile
| +- org.apache.xbean:xbean-reflect:jar:3.4:compile
| | +- log4j:log4j:jar:1.2.12:compile
| | \- commons-logging:commons-logging-api:jar:1.1:compile
| +-
com.google.code.google-collections:google-collect:jar:snapshot-20080530:compile
| \- junit:junit:jar:3.8.2:compile
+- commons-cli:commons-cli:jar:1.0:compile
+- org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-beta-4:compile
| +- org.apache.maven.wagon:wagon-http-shared:jar:1.0-beta-4:compile
| | +- nekohtml:xercesMinimal:jar:1.9.6.2:compile
| | \- nekohtml:nekohtml:jar:1.9.6.2:compile
| \- org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-4:compile
+- org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-4:compile
| +- com.jcraft:jsch:jar:0.1.38:compile
| \- org.apache.maven.wagon:wagon-ssh-common:jar:1.0-beta-4:compile
+- org.apache.maven.wagon:wagon-ssh-external:jar:1.0-beta-4:compile
\- org.apache.maven.wagon:wagon-file:jar:1.0-beta-4:compile
On Tue, Feb 24, 2009 at 8:21 AM, Gunnar Wagenknecht <
gunnar@xxxxxxxxxxxxxxx> wrote:
Hi Allan,
I started looking at some of the CQs you filed. Can you explain a bit
more on the CQs? Do you want to redistribute all those packages? Are
that optional dependencies? What kind of dependency do you intend? Do
you want to bring those packages into Orbit as well, etc....
The description for all CQs reads: "One of the maven components required
by the maven embedder on top of which IAM is built." It's hard for me to
understand the full intent from that description.
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
--
Abel Muiño - http://ramblingabout.wordpress.com/
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
------------------------------------------------------------------------
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
--
Abel Muiño -
http://ramblingabout.wordpress.com/
