Bintray seems quite interesting. I signed up directly! I see that it is still a
beta and there are some bugs, and a bit of confusion signing up. It refused to
work signing up with my google account, but after signing upp directly I can
stil login with my google account.
That you can
Hello again,
OK, I suspected that I get a lot of replies on this :-).
From experience in other forums I also expected to have people tell me to go
screw myself, but that has not happened. There are apparently only
professionals here! That said, there some very good replies and explanations
I'll start with the latter. The arguments about quality I just don't buy. We
are only talking poms here. Whatever is in the poms says nothing about the
quality of the software itself.
I agree the pom says nothing about the quality of the software.
However, having a standard mechanism for
The arguments about quality I just don't buy. We are only talking poms
here. Whatever is in the poms says nothing about the quality of the
software itself.
Quality of metadata. POM serve as metadata in this case, so, I'd rather
say Central enforces quality of metadata (ie. POM properly
6 jan 2014 kl. 14:10 skrev Tamás Cservenák ta...@cservenak.net:
The arguments about quality I just don't buy. We are only talking poms
here. Whatever is in the poms says nothing about the quality of the
software itself.
Quality of metadata. POM serve as metadata in this case, so, I'd
I am assuming that you are putting this in Central so I can easily use
it without having to worry about the effect on my build process or
without having to get into your sources and dependencies to build my app
and I have appropriate license agreements included so I know what I am
Hi Tommy et al,
here's another option for you:
You can leverage bintray.com to sync to Maven Central from there. For
starter, you'll just get your artifacts to Maven Central in more sane way -
no parent poms, no maven-release-plugin, no 20 pages guides. Just get your
artifacts to Bintray,
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
at
mar...@headcrashing.eu, I can guide you.
-Original Message-
From: Tommy Svensson [mailto:to...@natusoft.se]
Sent: Sonntag, 5. Januar 2014 14:15
To: Maven Users List
Subject: Maven Central Opinion
I was asked to submit one of my opensource tools at github to maven central.
This turned out
help, feel free to contact
me at mar...@headcrashing.eu, I can guide you.
-Original Message-
From: Tommy Svensson [mailto:to...@natusoft.se]
Sent: Sonntag, 5. Januar 2014 14:15
To: Maven Users List
Subject: Maven Central Opinion
I was asked to submit one of my opensource tools
guide you.
-Original Message-
From: Tommy Svensson [mailto:to...@natusoft.se]
Sent: Sonntag, 5. Januar 2014 14:15
To: Maven Users List
Subject: Maven Central Opinion
I was asked to submit one of my opensource tools at github to maven central.
This turned out to be a rather complex
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
List
Subject: Maven Central Opinion
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
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
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
23 matches
Mail list logo