I was asked to submit one of my opensource tools at github to maven central.
This turned out to be a rather complex procedure.
Sonatype puts the following requirements on anyone wanting to submit to maven
central:
- You are forced to set a Sonatype pom as parent of your project and thus
Hi Tommy,
I was asked to submit one of my opensource tools
at github to maven central.
So just create a ticket on JIRA ...
This turned out to be a rather complex procedure.
Sonatype puts the following requirements on anyone wanting to submit to maven
central:
Can you give a hint from
On the flip side - I would argue that the process is not too
difficult. It is well documented and easy to understand, it can also
be automated if you wish.
You need not necessarily inherit the Sonatype pom, and if you do you
can override whatever you like anyway.
I think the current process
On Sun, Jan 5, 2014 at 2:15 PM, Tommy Svensson to...@natusoft.se wrote:
I was asked to submit one of my opensource tools at github to maven
central. This turned out to be a rather complex procedure.
Sonatype puts the following requirements on anyone wanting to submit to
maven central:
-
Tommy Svensson:
I was asked to submit one of my opensource tools at github to maven
central. This turned out to be a rather complex procedure.
That was my first impression as well. But after reading the excellent
documentation and setting everything properly up, I'm impressed how
smooth
I uploaded lots of not-even-Mavenized prebuilt JARs to Maven Central and can
tell you that you simply misunderstood these terms as essential requirements
-- in fact most of them are only best practices. You do neither need to have
the Sonatype POM, it will just make things easier, nor do you
Well, I guess I have my answer, I am alone :-).
Many people are telling me that both the sonatype super pom and SNAPSHOTs are
optional. I obviously have been reading the wrong instructions. This is the
instructions I've followed:
Read section 7b of the page you link, it addresses your desires
directly. I quote:
You don't have to go through steps 7.a.1. through 7.a.3. if your
artifacts have already been released or if you've generated your
artifacts using something other than Maven. The steps below allow you
to skip using
On 05 Jan 2014, at 3:15 PM, Tommy Svensson to...@natusoft.se wrote:
- You are forced to have a SNAPSHOT version even if you have no use for such.
Maven works because there is a consistent level of standards and a consistent
methodology, and these standards are enforced in central. If you pick
On Sun, Jan 5, 2014 at 11:55 AM, Graham Leggett minf...@sharp.fm wrote:
On 05 Jan 2014, at 3:15 PM, Tommy Svensson to...@natusoft.se wrote:
- You are forced to have a SNAPSHOT version even if you have no use for such.
Maven works because there is a consistent level of standards and a
IMO, while uploading to Maven Central is ideal, it is sufficient for a
small OSS project to provide Maven artifacts *somewhere*. And you
don't need a repository manager for this. You can automatically
deploy your artifacts via SCP to a cheap shared host. That's what I
do.
On 1/5/14, Benson
On Sun, Jan 5, 2014 at 2:39 PM, Karl Heinz Marbaise khmarba...@gmx.dewrote:
I was asked to submit one of my opensource tools
at github to maven central.
So just create a ticket on JIRA ...
I understand that we aren't talking about an ASF release her, are we?
Jochen
On Sun, Jan 5, 2014 at 5:29 PM, Tommy Svensson to...@natusoft.se wrote:
Well, I guess I have my answer, I am alone :-).
Many people are telling me that both the sonatype super pom and SNAPSHOTs
are optional. I obviously have been reading the wrong instructions.
Maven dependency versionning
Hi Tommy,
One of the mvn release:* commands (dont rember which ) failed if I
did not have a SNAPSHOT version and told me the problem was that I did
not have a SNAPSHOT version.
I did not notice any other reply specifically troubleshooting this problem,
so... my guess is that you have a
On 6 January 2014 06:48, Curtis Rueden ctrue...@wisc.edu wrote:
Hi Tommy,
One of the mvn release:* commands (dont rember which ) failed if I
did not have a SNAPSHOT version and told me the problem was that I did
not have a SNAPSHOT version.
I did not notice any other reply specifically
Great to see them all in one place.
I like maven-12
my 2p
timp
On 3 January 2014 15:12, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I have created a wiki page to track the logo contest...
https://cwiki.apache.org/confluence/display/MAVEN/Logo+contest
On 2 January 2014
Hi I am using maven3
I want to execute my bat file from pom but it is not working please guide me
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
I think that the associations of a raven are too dark also
http://www.youtube.com/watch?v=mBmExt184vc
The moose and beaver are also laden.
Maybe this is why Maven has been logo free for so long?
Feels really weird to add a logo to a 13? year old project.
cheers
Timp
On 2 January 2014 15:48,
On 5 Jan 2014, at 13:15, Tommy Svensson to...@natusoft.se wrote:
I was asked to submit one of my opensource tools at github to maven central.
This turned out to be a rather complex procedure.
[ disclaimer: I work at Sonatype ]
Any suggestions for improving the process are welcome - most of
I'm favouring maven-15 here, the maven raven! Ok, it's not a raven, but maybe
it should be :) heh.
The bird can quite easily stand alone from the text, and be usable - overlaid,
underlaid, watermarked etc better than the others IMHO ( except 14 ).
I like maven-12
signature.asc
Description:
On 5 January 2014 11:34, rajiv rajivkumarnandv...@gmail.com wrote:
Hi I am using maven3
I want to execute my bat file from pom but it is not working please guide me
[del]
i used following commands
mvn target:run
mvn verify
mvn run
mvn exe:run
mvn package
only build success but bat file not
Date: Sat, 4 Jan 2014 16:11:02 -0800
Subject: Re: Topologically sorted list of Artifacts for use by a plugin?
From: ljnel...@gmail.com
To: users@maven.apache.org
On Fri, Jan 3, 2014 at 6:17 PM, Martin Gainty mgai...@hotmail.com wrote:
MGso I would say you are definitely on the right
Hello; suppose I have a CollectionArtifact in my left hand, all elements
of which are not resolved.
(As it happens, I got these indirectly from a DependencyGraphBuilder
invocation.)
What is the Maven Way™ to resolve these Artifacts?
I know that these Artifacts are unresolved, because each of
On Sun, Jan 5, 2014 at 3:56 PM, Laird Nelson ljnel...@gmail.com wrote:
What is the Maven Way™ to resolve these Artifacts?
For completeness, I also looked at
http://maven.apache.org/guides/introduction/introduction-to-artifact-resolution.htmlbut
this didn't seem to have ever been completed.
24 matches
Mail list logo
