james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject Re: svn commit: r1134885 - /james/server/trunk/container-spring/pom.xml
Date Mon, 13 Jun 2011 14:53:12 GMT
2011/6/13 Eric Charles <eric@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:

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:

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).


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message