You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Tommy Svensson <to...@natusoft.se> on 2014/01/05 14:15:02 UTC

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 pom as parent of your project and thus inherit things you have no control over. 
- You are forced to have a SNAPSHOT version even if you have no use for such.
- You are forced at submission time to select a new version for your software even if you have no idea if it will be a minor, bugfix or new functionality at this point in time. 
- Your public repository (github, etc) which you are forced to point out in your pom are no longer yours to decide over. It will be updated during the submission process. 
- After running 3 different mvn commands you also need to login to Sonatypes nexus server and ”release” the artifacts before the become available. 

The idea of the maven repository that has grown larger than maven itself is a completely brilliant idea. It takes open source to a new level where anyone can just depend on other open source code and automatically download it on build. This is really good for the open source world (well, at least the Java/JVM part of it) . The fact that the release process to this central repository is far too complex, I see as a really great problem, inhibiting the easy sharing of open source work. I have often found open source tools and frameworks that are not available in maven central, and that is because not everyone is willing to put up with this, which now also includes myself. As I see it, either this procedure needs to be changed to provide a trivial release of binary artifacts without affecting your poms, or there need to be an alternative open repository providing ease of release, where it is trivial for anyone to share their binaries for easy access by others. I’m wondering if I’m alone in this view or if there are others who agree with me ? 

Tommy Svensson


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Jochen Wiedmann <jo...@gmail.com>.
On Sun, Jan 5, 2014 at 2:39 PM, Karl Heinz Marbaise <kh...@gmx.de>wrote:

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



>
>

Re: Maven Central Opinion

Posted by Karl Heinz Marbaise <kh...@gmx.de>.
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 where this "requirements" are comming from?

I know of the following:

https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

This is what i use...

http://search.maven.org/#artifactdetails%7Ccom.soebes.smpp%7Csmpp%7C0.6.3%7Cpom

I don't have Sontype pom as parent for example....

>
> - You are forced to set a Sonatype pom as parent of your project and thus inherit
 > things you have no control over.


> - You are forced to have a SNAPSHOT version even if you have no use for such.

> - You are forced at submission time to select a new version for your
 > software even if you have no idea if it will be
 >  a minor, bugfix or new functionality at this point in time.

This is the basic workflow with Maven release plugin.

> - Your public repository (github, etc) which you are forced to point
 >  out in your pom are no longer yours to decide over.
 >  It will be updated during the submission process.

Sure. During the release workflow a tag is created...

> - After running 3 different mvn commands you also need to
 >  login to Sonatypes nexus server and ”release” the artifacts before
 >  the become available.

Needed to promote the artifacts to Maven Central..

>
> The idea of the maven repository that has grown larger than maven itself
 >  is a completely brilliant idea. It takes open source to a new level
 > where anyone can just depend on other open source code and automatically
 > download it on build. This is really good for the open source world
 > (well, at least the Java/JVM part of it).

Do you have something which is not Java/JVM based ? Like 
Ruby/Python/Perl/Whatever ?

 > The
 > fact that the release process to this central repository
 >is far too complex, I see as a really great problem,
 >inhibiting the easy sharing of open source work.

The problem in earlier days where that it was too easy to put something 
on Maven central and the results have been:
bad quality, many arfitacts which are not signed,
containing repositories in the pom's which results in many problems and
other problems...

 > I have often found open source tools and frameworks that are not
 > available in maven central, and that is because not everyone
 >is willing to put up with this, which now also includes myself.

The point in this is: To hold a quality level inside of Maven central.

I think the price it's worth the effort. It's a real centralized area 
where everyone can get the artifacts from. If you use 
Maven/Gradle/BuildR/Ant+IVY/WhatEver etc.

 >  As I see it, either this procedure needs to be changed to provide
 >  a trivial release of binary artifacts without affecting your poms,

What do you mean by "without affecting you poms?" During the release 
process the versions of your artifacts are being changed from 
X.Y-SNAPSHOT to X.Y so the pom's must be changed.

May be i misundestand a thing here...

 >  or there need to be an alternative open repository providing ease
 >  of release, where it is trivial for anyone to share their binaries
 > for easy access by others.

Don't hesitate to make suggestions how to make it simpler and reliable 
too...

 >  I’m wondering if I’m alone in this
 >  view or if there are others who agree with me ?

Unfortunately I don't, cause i know the drawbacks of a simpler 
procedure...but i'm willing to learn to get things better...

Kind regards
Karl Heinz Marbaise

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Benson Margulies <bi...@gmail.com>.
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 the maven-release-plugin entirely.  You can either use
the maven-gpg-plugin to sign and deploy your artifacts or upload a
staging bundle.

On Sun, Jan 5, 2014 at 11:29 AM, 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. This is the instructions I've followed:
>
>         https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
>
> Are there better, clearer instructions somewhere else ? 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. So is the above page completely wrong ? Are there other "mvn release:*" goals to run ?
>
> I also don't buy the argument that release complexity gives better quality.
>
> Many of the responses to my mail have also indicated that the update of my github repository is a totally obvious thing. I simply do not accept that. When I update my repository and what I update it with is my and only my decision! I went around this problem by making a copy repository before going through the release steps, and then deleted the copy afterwards, keeping my original intact. It was already in the state I wanted it before releasing to maven central. The only thing I want to release to maven central is binaries! My repository should not be touched. So if there is no way around that happening I guess I have released my first and last code to maven central.
>
> Anyhow, my question have been answered very clearly.
>
> Tommy
>
>
> 5 jan 2014 kl. 16:18 skrev Markus Karg <ka...@quipsy.de>:
>
>> 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 have to use SNAPSHOTs. You can simply upload a prebuilt JAR file. The only "hard" requirements are a "good" POM, signing the JAR with GPG, uploading it to the OSS nexus instance, then closing and releasing it. This it at-most simple and done in minutes. If you need help, feel free to contact me at markus@headcrashing.eu, I can guide you.
>>
>> -----Original Message-----
>> From: Tommy Svensson [mailto:tommy@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 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 inherit things you have no control over.
>> - You are forced to have a SNAPSHOT version even if you have no use for such.
>> - You are forced at submission time to select a new version for your software even if you have no idea if it will be a minor, bugfix or new functionality at this point in time.
>> - Your public repository (github, etc) which you are forced to point out in your pom are no longer yours to decide over. It will be updated during the submission process.
>> - After running 3 different mvn commands you also need to login to Sonatypes nexus server and "release" the artifacts before the become available.
>>
>> The idea of the maven repository that has grown larger than maven itself is a completely brilliant idea. It takes open source to a new level where anyone can just depend on other open source code and automatically download it on build. This is really good for the open source world (well, at least the Java/JVM part of it) . The fact that the release process to this central repository is far too complex, I see as a really great problem, inhibiting the easy sharing of open source work. I have often found open source tools and frameworks that are not available in maven central, and that is because not everyone is willing to put up with this, which now also includes myself. As I see it, either this procedure needs to be changed to provide a trivial release of binary artifacts without affecting your poms, or there need to be an alternative open repository providing ease of release, where it is trivial for anyone to share their binaries for easy access by others. I'm wondering if I'm alone in this view or if there are others who agree with me ?
>>
>> Tommy Svensson
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Barrie Treloar <ba...@gmail.com>.
On 6 January 2014 06:48, Curtis Rueden <ct...@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 troubleshooting this problem,
> so... my guess is that you have a SNAPSHOT dependency in your dependency
> hierarchy. You cannot cut a release unless it only depends on releases.
> Otherwise, the behavior of the release could change out from under you
> if/when that SNAPSHOT version is updated.
>
> If you share the exact error message you received, others can assist in
> more detail.

Tommy originally said "- You are forced to have a SNAPSHOT version
even if you have no use for such."
So I believe that the release plugin is failing because he doesn't
have a -SNAPSHOT in his pom.
The release plugin checks that your artifact has a -SNAPSHOT version
before it starts the workflow.
If there is no -SNAPSHOT it assumes the artifact is already released
and so stops.

As others have already said, if that is not your workflow you need to
do the stuff manually instead.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Curtis Rueden <ct...@wisc.edu>.
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 SNAPSHOT dependency in your dependency
hierarchy. You cannot cut a release unless it only depends on releases.
Otherwise, the behavior of the release could change out from under you
if/when that SNAPSHOT version is updated.

If you share the exact error message you received, others can assist in
more detail.

Regards,
Curtis


On Sun, Jan 5, 2014 at 10:29 AM, 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. This is
> the instructions I've followed:
>
>
> https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
>
> Are there better, clearer instructions somewhere else ? 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. So is the above page completely wrong ? Are there other "mvn
> release:*" goals to run ?
>
> I also don't buy the argument that release complexity gives better quality.
>
> Many of the responses to my mail have also indicated that the update of my
> github repository is a totally obvious thing. I simply do not accept that.
> When I update my repository and what I update it with is my and only my
> decision! I went around this problem by making a copy repository before
> going through the release steps, and then deleted the copy afterwards,
> keeping my original intact. It was already in the state I wanted it before
> releasing to maven central. The only thing I want to release to maven
> central is binaries! My repository should not be touched. So if there is no
> way around that happening I guess I have released my first and last code to
> maven central.
>
> Anyhow, my question have been answered very clearly.
>
> Tommy
>
>
> 5 jan 2014 kl. 16:18 skrev Markus Karg <ka...@quipsy.de>:
>
> > 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 have to use SNAPSHOTs. You can simply upload a prebuilt JAR file.
> The only "hard" requirements are a "good" POM, signing the JAR with GPG,
> uploading it to the OSS nexus instance, then closing and releasing it. This
> it at-most simple and done in minutes. If you need help, feel free to
> contact me at markus@headcrashing.eu, I can guide you.
> >
> > -----Original Message-----
> > From: Tommy Svensson [mailto:tommy@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 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 inherit things you have no control over.
> > - You are forced to have a SNAPSHOT version even if you have no use for
> such.
> > - You are forced at submission time to select a new version for your
> software even if you have no idea if it will be a minor, bugfix or new
> functionality at this point in time.
> > - Your public repository (github, etc) which you are forced to point out
> in your pom are no longer yours to decide over. It will be updated during
> the submission process.
> > - After running 3 different mvn commands you also need to login to
> Sonatypes nexus server and "release" the artifacts before the become
> available.
> >
> > The idea of the maven repository that has grown larger than maven itself
> is a completely brilliant idea. It takes open source to a new level where
> anyone can just depend on other open source code and automatically download
> it on build. This is really good for the open source world (well, at least
> the Java/JVM part of it) . The fact that the release process to this
> central repository is far too complex, I see as a really great problem,
> inhibiting the easy sharing of open source work. I have often found open
> source tools and frameworks that are not available in maven central, and
> that is because not everyone is willing to put up with this, which now also
> includes myself. As I see it, either this procedure needs to be changed to
> provide a trivial release of binary artifacts without affecting your poms,
> or there need to be an alternative open repository providing ease of
> release, where it is trivial for anyone to share their binaries for easy
> access by others. I'm wondering if I'm alone in this view or if there are
> others who agree with me ?
> >
> > Tommy Svensson
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: Maven Central Opinion

Posted by Thomas Broyer <t....@gmail.com>.
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 is based on snapshots and releases, with
releases that cannot change once published (if you messed up with your 1.0,
you have to release a 1.0.1 (or whatever version you want))
That doesn't mean you *have* to publish snapshots, and that doesn't even
mean you have to use snapshot versions in your POM.
But consider the pros and cons of not using snapshots: if your POM doesn't
use a snapshot version, then anyone cloning your repo and doing a "mvn
install" will have in its local repo the artifact it just built, and then
when you publish that release yourself, that developer won't see it
(because Maven won't check for a more recent version: non-snapshot versions
do not change from Maven point of view – OK, it might no longer be true
with recent versions of Maven, where the version is tied to the repo it
comes from, IIRC).

I agree the doc is strongly biased towards using sonatype-parent though,
but as others pointed out, this is not a requirement (see
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement
)

I think the doc is for people who don't really know what they're doing and
don't really want to know and just want to proceed, and sonatype-parent and
the maven-release-plugin make it really easier for them.
If you don't want to use the sonatype-parent parent, then you'll have to
invest time into understanding what you have to do ("Central Sync
Requirement") and how to configure your POM to achieve it.
Similarly if you don't want to use the maven-release-plugin.

Are there better, clearer instructions somewhere else ? 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. So is the above page completely wrong ? Are there other "mvn
> release:*" goals to run ?
>

The maven-release-plugin is *one* way (the preferred way) to release
artifacts, but it's actually only a big workflow that calls into other
plugins: update the POMs with a non-snapshot version, verify that it
builds, commit the change and tag the commit, deploy to the remote repo,
then change the POMs to a snapshot version, verify that it builds, and
commit the change.
You're not forced to use the maven-release-plugin to release artifacts, you
can do some or all of the above steps "by hand", and you could use
non-snapshot versions all the time (but then you *cannot* use the
maven-release-plugin).

Again, the maven-release-plugin makes it simpler if you follow the rules
(use snapshot versions) and accept the conditions; you're not forced to use
it but you'll have to invest time into understanding what it does (that is
mandatory or optional) and how to do (some of) it by other means.

As I said in a previous message, deploying to the remote repo is just a
matter of "mvn deploy", using either the maven-deploy-plugin (by default)
or the nexus-staging-maven-plugin.
You'll have to configure the GPG plugin to sign your artifacts though, as
it's a requirement to deploy to Central.

I bet you'll find many blogs online about how to do releases without the
maven-release-plugin, and how to then deploy to Central.


> Many of the responses to my mail have also indicated that the update of my
> github repository is a totally obvious thing. I simply do not accept that.
> When I update my repository and what I update it with is my and only my
> decision! I went around this problem by making a copy repository before
> going through the release steps, and then deleted the copy afterwards,
> keeping my original intact. It was already in the state I wanted it before
> releasing to maven central. The only thing I want to release to maven
> central is binaries! My repository should not be touched. So if there is no
> way around that happening I guess I have released my first and last code to
> maven central.
>

The maven-release-plugin has many configuration properties related to SCM:
whether to push changes, tag changes, etc.
http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html

Note, I never tried it but you could apparently just do "mvn
release:perform -DconnectionUrl=…" (or creating a release.properties file
and then using "mvn release:perform"):
http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html

Re: Maven Central Opinion

Posted by Tommy Svensson <to...@natusoft.se>.
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: 

	https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

Are there better, clearer instructions somewhere else ? 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. So is the above page completely wrong ? Are there other "mvn release:*" goals to run ? 

I also don't buy the argument that release complexity gives better quality. 

Many of the responses to my mail have also indicated that the update of my github repository is a totally obvious thing. I simply do not accept that. When I update my repository and what I update it with is my and only my decision! I went around this problem by making a copy repository before going through the release steps, and then deleted the copy afterwards, keeping my original intact. It was already in the state I wanted it before releasing to maven central. The only thing I want to release to maven central is binaries! My repository should not be touched. So if there is no way around that happening I guess I have released my first and last code to maven central.

Anyhow, my question have been answered very clearly.

Tommy


5 jan 2014 kl. 16:18 skrev Markus Karg <ka...@quipsy.de>:

> 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 have to use SNAPSHOTs. You can simply upload a prebuilt JAR file. The only "hard" requirements are a "good" POM, signing the JAR with GPG, uploading it to the OSS nexus instance, then closing and releasing it. This it at-most simple and done in minutes. If you need help, feel free to contact me at markus@headcrashing.eu, I can guide you.
> 
> -----Original Message-----
> From: Tommy Svensson [mailto:tommy@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 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 inherit things you have no control over. 
> - You are forced to have a SNAPSHOT version even if you have no use for such.
> - You are forced at submission time to select a new version for your software even if you have no idea if it will be a minor, bugfix or new functionality at this point in time. 
> - Your public repository (github, etc) which you are forced to point out in your pom are no longer yours to decide over. It will be updated during the submission process. 
> - After running 3 different mvn commands you also need to login to Sonatypes nexus server and "release" the artifacts before the become available. 
> 
> The idea of the maven repository that has grown larger than maven itself is a completely brilliant idea. It takes open source to a new level where anyone can just depend on other open source code and automatically download it on build. This is really good for the open source world (well, at least the Java/JVM part of it) . The fact that the release process to this central repository is far too complex, I see as a really great problem, inhibiting the easy sharing of open source work. I have often found open source tools and frameworks that are not available in maven central, and that is because not everyone is willing to put up with this, which now also includes myself. As I see it, either this procedure needs to be changed to provide a trivial release of binary artifacts without affecting your poms, or there need to be an alternative open repository providing ease of release, where it is trivial for anyone to share their binaries for easy access by others. I'm wondering if I'm alone in this view or if there are others who agree with me ? 
> 
> Tommy Svensson
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Maven Central Opinion

Posted by Markus Karg <ka...@quipsy.de>.
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 have to use SNAPSHOTs. You can simply upload a prebuilt JAR file. The only "hard" requirements are a "good" POM, signing the JAR with GPG, uploading it to the OSS nexus instance, then closing and releasing it. This it at-most simple and done in minutes. If you need help, feel free to contact me at markus@headcrashing.eu, I can guide you.

-----Original Message-----
From: Tommy Svensson [mailto:tommy@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 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 inherit things you have no control over. 
- You are forced to have a SNAPSHOT version even if you have no use for such.
- You are forced at submission time to select a new version for your software even if you have no idea if it will be a minor, bugfix or new functionality at this point in time. 
- Your public repository (github, etc) which you are forced to point out in your pom are no longer yours to decide over. It will be updated during the submission process. 
- After running 3 different mvn commands you also need to login to Sonatypes nexus server and "release" the artifacts before the become available. 

The idea of the maven repository that has grown larger than maven itself is a completely brilliant idea. It takes open source to a new level where anyone can just depend on other open source code and automatically download it on build. This is really good for the open source world (well, at least the Java/JVM part of it) . The fact that the release process to this central repository is far too complex, I see as a really great problem, inhibiting the easy sharing of open source work. I have often found open source tools and frameworks that are not available in maven central, and that is because not everyone is willing to put up with this, which now also includes myself. As I see it, either this procedure needs to be changed to provide a trivial release of binary artifacts without affecting your poms, or there need to be an alternative open repository providing ease of release, where it is trivial for anyone to share their binaries for easy access by others. I'm wondering if I'm alone in this view or if there are others who agree with me ? 

Tommy Svensson


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Ron Wheeler <rw...@artifact-software.com>.
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 
incorporating into my app.

In that case, I would like you to follow the Maven "Best Practices" for 
deploying to Central.

Using the Release plug-in may save you some steps if you do not already 
have a private repo for releasing software internally.
It seems to me that if you are already "releasing" to your own repo 
prior to trying to upload it to Central, you are probably going to find 
that the Release plug-in is not the "best practice".
We would be in the same situation if we ever decided to put some of our 
utilities into Maven Central. We have already done the release and our 
SCM is in the state in which we want it.
We would probably have to look at our parent POM/child POM structure to 
be sure that it met Maven Central requirements.

I think that you did the right thing by raising your concerns here and I 
think that you got some very good advice and concrete suggestions.

This is a very good group that is usually well-mannered when approached 
in the way that you did.
You were very clear about what you wanted to do and you raised very 
specified issues that you wanted to discuss.
You also reacted to the advice in a positive way that encouraged a 
factual discussion rather than a personal attack.

Ron

On 06/01/2014 7:49 AM, Tommy Svensson wrote:
> 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 but also some I do react to.
>
> 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. What is really bothering me however is the argument that if you don't have your things in the way we think they should be, you are not serious enough. It hasn't been said straight out but implied. The word that pops into my head here is "Moralizing"! I take my work very seriously and I take my open source work even more seriously (since in that case I'm allowed the time for it :-)). That if I have one file that is not up to someones liking I'm not taking releasing of my software seriously is just absurd.
> _______
>
>  From one of the replies:
>> As I said in a previous message, deploying to the remote repo is just a
>> matter of "mvn deploy", using either the maven-deploy-plugin (by default)
>> or the nexus-staging-maven-plugin.
> That is good, that is how easy it should be!
>
>> You'll have to configure the GPG plugin to sign your artifacts though, as
>> it's a requirement to deploy to Central.
> No problem!
>
> I'm going to go though the documentation again and solve the "easy" way to do it :-).  And If I can't find a page that explains this clearly I will create such! I have gotten very much information here to go on.
>
> Someone also pointed out that local webserver repositories are good enough for "small" projects. I basically agree with that. I only considered maven central since someone asked me. But it is easier to have things in central and not have to add multiple repository specifications in your pom/settings. OK, you can use nexus to merge several repositories into one and then use that. But if submission to central can be made easy then it is worth to do it. Software does not have to be large apache projects to be useful. There are some truly useful software out there that comes from single individuals.
> ________
>
> Here is my view of how I would want a maven repository to be:
>
> - No requirements of javadoc or sources. If you want to include those, no problem, but if you don't  it is up to you. Personally I like to have sources available in the repository for the third party software I'm using so I would also submit sources to my software, but that is entirely up to me.
>
> - Tags on submitted software (not required - can be empty).
>
> - Searchable data in addition to group and artifact:
>    - Tags
>    - Descriptions
>
> - A browsable (navigable) web gui, not just searches.
>
> - A standardized documentation zip containing PDFs and/or markdown.
>
> - Quality indication:
>    - The possibility to star artifacts just like you can star repos in github. Also for group level.
>    - Download statistics (filtered on ip-address, multiple downloads from the same ip-address only count as one).
>    - A quality value based on these two as sorting order for search results.
>
> - When an artifact or group is selected in the web gui the following should be displayed:
>    - Dependency tags for the artifact (obviously :-))
>    - Pom information like description, web url, developers, scm url, etc.
>    - Stars and download stats.
>    - Any submitted docs.
>
> With so much software available in one place it would be very nice to have it more searchable and on more useful criteria, and also to have the ability to get more details on the software at the same place.
>
> Tommy
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Adam Retter <ad...@googlemail.com>.
> 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 describing in small detail
software releases. By ensuring that this is consistent, it ensures
that the quality of searching for artifacts in Maven central is
maintained, it also ensures that when someone finds an artifact they
can look at the pom to see what it does and who to contact should they
have a problem. I consider that a small investment.


-- 
Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Tommy Svensson <to...@natusoft.se>.
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 rather
> say Central enforces quality of "metadata" (ie. POM properly "filled in",
> using proper and proven/owned groupId, sane artifactId, etc, minimal set of
> fields are given, file signatures, checksums are present, no update of
> already deployed stuff happens [ie. your deploy request would overwrite
> something in Cenral] etc).
> 
> Still, you can deploy a jar full of zeroes to Central if you wish, all
> until you use proper GA, the checksums and signatures matches, and POM
> fulfills minimal requirements :)

And I think that is a good thing! It would be rather stupid to do that, but that is beside the point :-).

> 
> 
> My 5 cents


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by 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 rather
say Central enforces quality of "metadata" (ie. POM properly "filled in",
using proper and proven/owned groupId, sane artifactId, etc, minimal set of
fields are given, file signatures, checksums are present, no update of
already deployed stuff happens [ie. your deploy request would overwrite
something in Cenral] etc).

Still, you can deploy a jar full of zeroes to Central if you wish, all
until you use proper GA, the checksums and signatures matches, and POM
fulfills minimal requirements :)


My 5 cents

Re: Maven Central Opinion

Posted by Tommy Svensson <to...@natusoft.se>.
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 but also some I do react to.  

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. What is really bothering me however is the argument that if you don't have your things in the way we think they should be, you are not serious enough. It hasn't been said straight out but implied. The word that pops into my head here is "Moralizing"! I take my work very seriously and I take my open source work even more seriously (since in that case I'm allowed the time for it :-)). That if I have one file that is not up to someones liking I'm not taking releasing of my software seriously is just absurd. 
_______

From one of the replies:
> As I said in a previous message, deploying to the remote repo is just a
> matter of "mvn deploy", using either the maven-deploy-plugin (by default)
> or the nexus-staging-maven-plugin.

That is good, that is how easy it should be!

> You'll have to configure the GPG plugin to sign your artifacts though, as
> it's a requirement to deploy to Central.

No problem!

I'm going to go though the documentation again and solve the "easy" way to do it :-).  And If I can't find a page that explains this clearly I will create such! I have gotten very much information here to go on. 

Someone also pointed out that local webserver repositories are good enough for "small" projects. I basically agree with that. I only considered maven central since someone asked me. But it is easier to have things in central and not have to add multiple repository specifications in your pom/settings. OK, you can use nexus to merge several repositories into one and then use that. But if submission to central can be made easy then it is worth to do it. Software does not have to be large apache projects to be useful. There are some truly useful software out there that comes from single individuals.
________

Here is my view of how I would want a maven repository to be:

- No requirements of javadoc or sources. If you want to include those, no problem, but if you don't  it is up to you. Personally I like to have sources available in the repository for the third party software I'm using so I would also submit sources to my software, but that is entirely up to me.

- Tags on submitted software (not required - can be empty). 

- Searchable data in addition to group and artifact:
  - Tags
  - Descriptions

- A browsable (navigable) web gui, not just searches. 

- A standardized documentation zip containing PDFs and/or markdown.

- Quality indication:
  - The possibility to star artifacts just like you can star repos in github. Also for group level.
  - Download statistics (filtered on ip-address, multiple downloads from the same ip-address only count as one).
  - A quality value based on these two as sorting order for search results.

- When an artifact or group is selected in the web gui the following should be displayed:
  - Dependency tags for the artifact (obviously :-))
  - Pom information like description, web url, developers, scm url, etc.
  - Stars and download stats.
  - Any submitted docs.

With so much software available in one place it would be very nice to have it more searchable and on more useful criteria, and also to have the ability to get more details on the software at the same place.

Tommy



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Stuart McCulloch <mc...@sonatype.com>.
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 the requirements below are actually more recommendations / effects of the maven-release-plugin workflow, so maybe we need to clarify this on the wiki.

> 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 inherit things you have no control over. 

The wiki recommends a parent pom with the relevant distributionManagement (so Maven knows where to deploy artifacts) plus some release configuration for adding sources, javadoc, signatures, etc.

You can always use a different parent pom and copy the distributionManagement section across - feel free to ask for help with this, and we can always add a section to the wiki if others would find this useful

> - You are forced to have a SNAPSHOT version even if you have no use for such.

This is the standard Maven release workflow - you don’t strictly need this if you’re just uploading releases, just go to the existing tagged release and use “mvn deploy”

(you’ll need override the deploy properties on the command line ie. http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#altDeploymentRepository if your pom doesn’t point to OSSRH)

> - You are forced at submission time to select a new version for your software even if you have no idea if it will be a minor, bugfix or new functionality at this point in time. 

As above, you can always deploy an existing release - either with “mvn deploy” or by packaging it up as a bundle and uploading it using the UI:

    https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-UploadStagingBundle

However, once you have released an artifact to central its content should never change

> - Your public repository (github, etc) which you are forced to point out in your pom are no longer yours to decide over. It will be updated during the submission process. 

That’s the Maven release plugin - it updates the released pom so it points to the right tagged release, then changes it back for development

Some projects do releases differently by using the versions plugin to update the poms, tagging the release manually, then finally using “mvn deploy"

> - After running 3 different mvn commands you also need to login to Sonatypes nexus server and ”release” the artifacts before the become available. 

That’s so you can check the uploaded artifacts before they get distributed to central, mirrors, and from there to developers machines - because once a release is on central its content should never change

If you want to skip this step then you can by configuring the nexus-staging-maven-plugin which can help manage the staging workflow:

    http://books.sonatype.com/nexus-book/reference/staging-sect-deployment.html#staging-sect-deployment-nexus-staging-maven-plugin

    <plugin>
      <groupId>org.sonatype.plugins</groupId>
      <artifactId>nexus-staging-maven-plugin</artifactId>
      <extensions>true</extensions>
      <configuration>
        <releaseAfterClose>true</releaseAfterClose>
      </configuration>
    </plugin>

You can also use this plugin to access the same staging commands available to you through the Nexus UI (or you could even use the underlying REST API if you wish)

Finally depending on your project there are alternative routes to central, such as http://www.apache.org/dev/publishing-maven-artifacts.html for Apache projects, or the new https://bintray.com/ service. 

> The idea of the maven repository that has grown larger than maven itself is a completely brilliant idea. It takes open source to a new level where anyone can just depend on other open source code and automatically download it on build. This is really good for the open source world (well, at least the Java/JVM part of it) . The fact that the release process to this central repository is far too complex, I see as a really great problem, inhibiting the easy sharing of open source work. I have often found open source tools and frameworks that are not available in maven central, and that is because not everyone is willing to put up with this, which now also includes myself. As I see it, either this procedure needs to be changed to provide a trivial release of binary artifacts without affecting your poms, or there need to be an alternative open repository providing ease of release, where it is trivial for anyone to share their binaries for easy access by others. I’m wondering if I’m alone in this view or if there are others who agree with me ? 
> 
> Tommy Svensson
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Adam Retter <ad...@googlemail.com>.
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 means that artifacts that are released are
well thought about and that their pom's provided a minimum of useful
information.

If you want to release something and you care about it, then I will
assume that it is of good quality, then I would ask the question "Why
should you care less about a high quality release than the code?"

On 5 January 2014 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.
>
> 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 inherit things you have no control over.
> - You are forced to have a SNAPSHOT version even if you have no use for such.
> - You are forced at submission time to select a new version for your software even if you have no idea if it will be a minor, bugfix or new functionality at this point in time.
> - Your public repository (github, etc) which you are forced to point out in your pom are no longer yours to decide over. It will be updated during the submission process.
> - After running 3 different mvn commands you also need to login to Sonatypes nexus server and ”release” the artifacts before the become available.
>
> The idea of the maven repository that has grown larger than maven itself is a completely brilliant idea. It takes open source to a new level where anyone can just depend on other open source code and automatically download it on build. This is really good for the open source world (well, at least the Java/JVM part of it) . The fact that the release process to this central repository is far too complex, I see as a really great problem, inhibiting the easy sharing of open source work. I have often found open source tools and frameworks that are not available in maven central, and that is because not everyone is willing to put up with this, which now also includes myself. As I see it, either this procedure needs to be changed to provide a trivial release of binary artifacts without affecting your poms, or there need to be an alternative open repository providing ease of release, where it is trivial for anyone to share their binaries for easy access by others. I’m wondering if I’m alone in this view or if there are others who agree with me ?
>
> Tommy Svensson
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>



-- 
Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Markus Malkusch <ma...@malkusch.de>.
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 releasing is.

> - You are forced to set a Sonatype pom as parent of your project and
> thus inherit things you have no control over.

I don't think that's a requirement. I think it's more a help to make
releasing more easy for you.

> - You are forced at submission time to select a new version for your
> software even if you have no idea if it will be a minor, bugfix or new
> functionality at this point in time.

I always go the proposed minor version change. If I later decide to make 
a
major change nobody prevents me to change the version at any time.

> - Your public repository (github, etc) which you are forced to point
> out in your pom are no longer yours to decide over. It will be updated
> during the submission process.

Yeah and that's really great. Without the release plugin I had to tag it
myself. But AFAIK that's not a requirement for submitting a release to
Maven Central.

> - After running 3 different mvn commands you also need to login to
> Sonatypes nexus server and ”release” the artifacts before the become
> available.

You can configure the nexus-staging-maven-plugin to do that for you.
autoReleaseAfterClose does that trick.

My projects use a common parent pom (which itself uses the sonatype 
parent)
where a typical release is done with two mvn commands and nothing more:
mvn release:prepare and mvn release:perform. This releases to sonatype,
tags a new version in vcs and makes a site-deploy to github. I'm really
impressed how smooth things are.

I understand that the process might look very complicated as first
impression. But if you don't want to go it, you might ask the guy who
opened the ticket to put your project into Maven Central:
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository

Markus

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Thomas Broyer <t....@gmail.com>.
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:
>
> - You are forced to set a Sonatype pom as parent of your project and thus
> inherit things you have no control over.
>

Wrong. That POM only helps you having things setup properly, by configuring
everything for you to fulfill the requirements without even thinking about
it.


> - You are forced to have a SNAPSHOT version even if you have no use for
> such.
>

Wrong (see notes below about the maven-release-plugin and "the Maven Way™").


> - You are forced at submission time to select a new version for your
> software even if you have no idea if it will be a minor, bugfix or new
> functionality at this point in time.
>

If by "submission time" you mean "mvn release:prepare release:perform",
then, well, you're releasing stuff so you'd better know how you want to
call it "at that point in time".


> - Your public repository (github, etc) which you are forced to point out
> in your pom are no longer yours to decide over. It will be updated during
> the submission process.
>

Wrong. This is a result of the maven-release-plugin and "the Maven Way™",
but you're not forced to use it to release your artifacts. Some people just
put non-SNAPSHOT version in their POM and then use "mvn deploy" to deploy
to a Maven repo (such as Sonatype OSS); see
https://github.com/resteasy/Resteasy/tree/master/jaxrs, they don't use
snapshots.


> - After running 3 different mvn commands you also need to login to
> Sonatypes nexus server and ”release” the artifacts before the become
> available.
>

Yes, that's how it goes. The idea I think is that the artifacts are
temporarily published in a special repository (this is called "staging") so
you can update your POMs and test those artifacts before actually releasing
them / pushing them to Central. Some people use that to make "release
candidates": their stage artifacts, announce it on their project's mailing
list and have people test the new thing, and after a few days, if nobody
reported a blocking issue, they can just push the "release" button. I
believe the Apache Foundation works that way (where people vote +1/0/-1 on
the staged artifacts during a couple days to a week)
I believe many other people just push the release button right away.
Note that you can use the nexus-staging-maven-plugin in your POM to
automatically close the staging repository (make it read-only) and even
automatically release it afterwards:
http://books.sonatype.com/nexus-book/reference/staging-sect-deployment.html#staging-sect-deployment-nexus-staging-maven-plugin


> The idea of the maven repository that has grown larger than maven itself
> is a completely brilliant idea. It takes open source to a new level where
> anyone can just depend on other open source code and automatically download
> it on build. This is really good for the open source world (well, at least
> the Java/JVM part of it) . The fact that the release process to this
> central repository is far too complex, I see as a really great problem,
> inhibiting the easy sharing of open source work.


Before going further, have you ever deployed artifacts to a repository?
More than half of what you're ranting about is about releasing artifacts
with Maven and deploying them to a repository, and more specifically about
the maven-release-plugin (and many people hate it); only a couple points
are about Sonatype OSS and Central.

-- 
Thomas Broyer
/tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>

Re: Maven Central Opinion

Posted by Kevin Krumwiede <kj...@gmail.com>.
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 Margulies <bi...@gmail.com> wrote:
> On Sun, Jan 5, 2014 at 11:55 AM, Graham Leggett <mi...@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
>> consistent methodology, and these standards are enforced in central. If
>> you pick and choose to ignore standards, you put the quality level of
>> central at risk.
>>
>> Snapshots and releases are a fundamental part of maven, the maven system
>> doesn't work without it. It is entirely right that central should block
>> projects that refuse to follow the rules.
>
> All well and good, but there _is no such rule_, and SNAPSHOT versus
> release isn't really all that 'central'. To post up to central, you
> have to own the group ID, provide source, sign the artfacts. That's
> about it. If you don't want to use -SNAPSHOT, don't use -SNAPSHOT. If
> you don't want to use the m-r-p, don't. (I happen to be partial to the
> jgitflow alternative, myself.) No one will know. Heck, you can wear a
> tutu while pushing your bundle to central, too.
>
> To give a concrete example: we push some rather large data resources
> to our internal Maven repo at work. We don't use snapshots. We don't
> use the release plugin. A script assembles the tarball and shoves it
> to the repo with deploy:deploy-file. -SNAPSHOTs are a solution to a
> need -- a common need when building code into binaries, but not a
> universal need.
>
>>
>> Regards,
>> Graham
>> --
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Benson Margulies <bi...@gmail.com>.
On Sun, Jan 5, 2014 at 11:55 AM, Graham Leggett <mi...@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 consistent methodology, and these standards are enforced in central. If you pick and choose to ignore standards, you put the quality level of central at risk.
>
> Snapshots and releases are a fundamental part of maven, the maven system doesn't work without it. It is entirely right that central should block projects that refuse to follow the rules.

All well and good, but there _is no such rule_, and SNAPSHOT versus
release isn't really all that 'central'. To post up to central, you
have to own the group ID, provide source, sign the artfacts. That's
about it. If you don't want to use -SNAPSHOT, don't use -SNAPSHOT. If
you don't want to use the m-r-p, don't. (I happen to be partial to the
jgitflow alternative, myself.) No one will know. Heck, you can wear a
tutu while pushing your bundle to central, too.

To give a concrete example: we push some rather large data resources
to our internal Maven repo at work. We don't use snapshots. We don't
use the release plugin. A script assembles the tarball and shoves it
to the repo with deploy:deploy-file. -SNAPSHOTs are a solution to a
need -- a common need when building code into binaries, but not a
universal need.

>
> Regards,
> Graham
> --
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Central Opinion

Posted by Graham Leggett <mi...@sharp.fm>.
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 and choose to ignore standards, you put the quality level of central at risk.

Snapshots and releases are a fundamental part of maven, the maven system doesn't work without it. It is entirely right that central should block projects that refuse to follow the rules.

Regards,
Graham
--


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org