[technology-pmc] [CQ 5629] plexus-component-annotations Version: 1.5.5 (

[emo-ip-team@xxxxxxxxxxx]

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=5629





--- Comment #5 from Benjamin Bentmann <bentmann@xxxxxxxxxxxx>  2011-09-28 15:21:42 ---
(In reply to comment #4)
> Do you intend to distribute the JAR with the project downloads?

No.

At Sonatype, there were no project downloads for Aether other than the JARs and
a complete source distribution that got uploaded to the central repository,
i.e. http://repo1.maven.org/maven2/org/sonatype/aether/. Users were expected to
either use Maven and a POM to fetch the desired Aether JARs automatically or to
manually grab the desired JARs from the mentioned URLs for inclusion in their
lib directories or such.

Aether (core) is not an Eclipse plugin with bundled JARs, nor an application
with a binary ZIP that gets unpacked and then run. It is a library/framework
that has no immediate value to end users but targets primarily integrators that
wish to employ dependency resolution. I consider it similar in nature to say
commons-mail from Apache. While commons-mail has 3rd party dependencies
(javax.mail, javax.activation) those are not included in their project
downloads. So while I imagine that Eclipse policy requires us to offer some
kind of project download, my current thinking is to offer a ZIP that only
includes the Aether JARs themselves, i.e. the output of Aether's build and not
its dependencies.

While writing this, I remembered the Aether Ant tasks. For ease of use, those
are usually distributed in a JAR that physically includes/aggregates its 3rd
party dependencies (like sisu-inject-bean). I will review the existing CQs to
check whether the "workswith" classification still holds in the context of the
Aether Ant tasks.

> Given that the library has already been approved, I'm not sure that this is
> worth the approval go-around that's required to declare a workswith.

I am completely unaware of the efforts involved here. All I tried was to give
as accurate information as possible, trying to facilitate a similar dependency
overview to
http://velocity.apache.org/engine/releases/velocity-1.7/jar-dependencies.html
where uses can see when/what dependencies are required. Given we have no
separate IP log for Aether core, the Ant tasks and the demos, this might have
been a half-baken attempt and we're likely better off tracking the details
manually.

So again, all I tried was to help with the creation of an accurate IP log. If
this distinction between works-with and prerequisite is not overly important
and works-with requires more work, I'm fine to declare everything a
prerequisite.


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.