Thanks for the link. Perhaps someone could put it on this page:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Nevertheless, this doesn't really answer my question. The point I was
making was that, with the current model, licences are missing in most
projects as far as I can tell. There's often at best a URL to a licence
file hosted elsewhere than the repository.
Most OSS licences are fairly clear: the licence must be distributed
along with the software, whether in binary or source form (depending on
the content of the licence).
The fact that "Sonatype will perform some due diligence to make sure
that the artifact has a license compatible with unrestricted
distribution, and we will then promote the uploaded artifacts to the
Central Maven repository." [from your link] doesn't make the text of
those licences appear from thin air, and the bundling process doesn't
seem to bundle those files.
'<license><name>BSD</name></license>' often doesn't refer to the actual
same licence for example. The copyright holder will be different from
one project to another, and redistributing software released under such
a licence, but without it, is effectively in breach of this licence (and
there are plenty of those in the central repository). One of the main
point of OSS licences is to acknowledge the copyright holders, at the
very least.
I suppose one way to solve it would be to put the actual text within the
<description/> element of the <license/> element in the POM file that's
with the jars in the repository.
I'm just suggesting there should be, along with the POM file and the
jars, a place for a LICENSE.txt (and perhaps NOTICE.txt as some licences
use) to make this clearer. (Downloading them along with the artifacts
would be a plus, again, for the sake of abiding by these licences.)
Does this mechanism already exist? How is it done?
Best wishes,
Bruno.
On 14/05/2010 22:39, Brian Fox wrote:
http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/
On Fri, May 14, 2010 at 11:46 AM, Bruno Harbulot
<[email protected]> wrote:
Hello,
Is there a way to prepare a bundle to be uploaded to the central repository
so that it also contains the licence file?
Ideally, I'd like a licence file along these files, for example:
http://repo1.maven.org/maven2/org/jsslutils/jsslutils/0.5.1/
My POM contains this:
<licenses>
<license>
<name>BSD</name>
<url>LICENSE.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
The licence file is next to the POM in the source tree, but it's never
included in the bundle or any of its inner jar files. I guess it could be an
absolute URL that points to it, but it would be good to have a licence file
bundled and uploaded with the other files, at least to respect the terms of
the licence itself.
Best wishes,
Bruno.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
