OK, got it :)
The tar.gz mention is here
<groupId>tanukisoft</groupId><artifactId>wrapper-delta-pack</artifactId><version>3.2.3</version><type>tar.gz</type>
in
http://repo1.maven.org/maven2/org/codehaus/mojo/appassembler-maven-plugin/1.1.1/appassembler-maven-plugin-1.1.1.pom
So maven central shouts it depends on wrapper-delta-pack 3.2.3
which has been republished by Stefano because of the right in the licence
" to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sub-license, and/or
sell copies of the Software, and to permit persons to whom the
Software is furnished to do so,"
To my understanding, we don't rely on any current Tanuki license, but
simply on the one we have modified "without limitation".
Tks,
- Eric
On 13/06/11 17:11, Eric Charles wrote:
We don't reference the tar.gz in the container-spring pom.
We simply ask appassembler-maven-plugin to generate daemons.
Do you mean the appassembler-maven-plugin will fetch the tar.gz ?
But I don't see mention of that in
http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/dependency-convergence.html
Tks,
- Eric
On 13/06/11 16:53, Stefano Bagnara wrote:
2011/6/13 Eric Charles<e...@apache.org>:
On 13/06/11 15:49, Stefano Bagnara wrote:
Anyone who has a public license could republish the artifact under
that public license. There would be no problems then using that
instance.
So at least we have a way out as I can redistribute it, but I hope we
don't even need this (I don't want to fight with maven central
managers in order to have a second identical copy of the artifact
published in their tree and I don't know where to publish it as apache
doesn't want to publish third party software).
As temporary workaround (if other options don't find concretization),
we can
setup a public folder on a developer home folder on people.apache.org
and
put the redistributed artificat there (and add that link in
the<repository>
tag of our pom).
I don't still agree with Robert point (IMO he misunderstood what
artifacts we use and how), anyway I just published my MIT licensed
copy of 3.2.3 wrapper here:
http://people.apache.org/~bago/third-party/
I checked it is bit-per-bit identical to the one in the maven central
and also identical to the one that can be obtained on the official
sourceforge repository:
http://sourceforge.net/projects/wrapper/files/wrapper/Wrapper_3.2.3_20061016/
In order to use it we'd have to include people.apache.org as a
repository (and to publish it in a maven repository layout structure,
not legacy as maven 3 doesn't support legacy anymore, AFAIK). This
will also prevent publishing james artifacts in central as central
doesn't allow pom's with external repositories. So I think we should
simply use the tar.gz from central as it contains a valid and
compatible license and Robert concerns are invalid in our real
use-case (Robert said he reviewed the jar and the pom, and not the
artifact we use: the tar.gz).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
