Hello,
I'm trying to follow the procedure for manual upload as described on
this page:
http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/
I've set up my GPG key and it seems to work mostly well, except that the
.asc file produced by this is
On 08/06/10 15:24, Bruno Harbulot wrote:
I'm trying to follow the procedure for manual upload as described on
this page:
http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/
I've set up my GPG key and it seems to work mostly well, except
On 08/06/10 16:52, Bruno Harbulot wrote:
On 08/06/10 15:24, Bruno Harbulot wrote:
I'm trying to follow the procedure for manual upload as described on
this page:
http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/
I've set up my GPG key
Hi,
I've just submitted this issue: http://jira.codehaus.org/browse/MNG-4680
However, I'm told this wasn't the right place to submit. I'm not sure.
To me, one of the key features of Apache Maven (if not the main feature)
is its repository mechanism. This makes the redistribution of software
On 18/05/2010 18:25, Justin Edelson wrote:
I thought it was well-established that you should include the license
inside binary and source artifacts.
What exactly is your reason for
thinking this isn't a good idea? Saying that it isn't obvious doesn't
really count IMHO as this is highly
On 18/05/2010 18:33, Ron Wheeler wrote:
1) If people are distributing their own software in violation of their
own licensing, it is their problem.
2) If people are distributing other people's software in violation of
the licencing, they should stop.
Hard to see how this is a Maven problem or
On 18/05/2010 20:45, Ron Wheeler wrote:
On 18/05/2010 2:52 PM, Bruno Harbulot wrote:
But how is a repository to know
1) Who is allowed to upload?
2) What, if any, license scheme the person uses. I can make up my own
license and I don't think that copyright or any law depends on a copy
On 19/05/2010 00:41, Brian Fox wrote:
The MAVENUPLOAD issue you refer to was processed by hand. This is
something we've worked to stop and automate, so it's not really
relevant what happened it was 2 years ago.
That said, I don't know if LICENSE.txt inside the new bundle format
would be
On 15/05/2010 21:56, Benson Margulies wrote:
I think that perhaps there's an important distinction being missed
here. Central doesn't vacuum up artifacts from unsuspecting authors.
Other people put them there. If the authors of code choose to deposit
jar files on central, then it's not central
On 16/05/2010 02:00, Brian Fox wrote:
On Sat, May 15, 2010 at 4:56 PM, Benson Marguliesbimargul...@gmail.com wrote:
Yes, these are good ideas.
Well, I'm not sure this is just about good ideas, it sounds more like
a legal requirement. This being said, I'm not a lawyer, it's just the
way I
:
Usually this is handled by inserting NOTICE and LICENSE into the jar
files themselves. In theory you could attach the license file to the
main artifact using the license classifier but normally this isn't
done.
On Fri, May 14, 2010 at 7:20 PM, Bruno Harbulot
bruno.harbu...@manchester.ac.uk 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
, 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
Hello,
Is there a way to provide a jar file that is not available in a Maven
repository as part of a multi-module project?
For example, if in a multi-module project
(groupId=example,artifactId=exampleroot), a sub-module
(groupId=example,artifactId=mainapp) depends on a jar that's not
14 matches
Mail list logo
