Deploy Artifacts to Maven Central about tomcat-slf4j-logback HOT 5 CLOSED

I have created this issue on sonatype to get access to load the artifact(s) we produce.

from tomcat-slf4j-logback.

In thinking about how we will release these, I'm thinking we break this down into a multi-module project so we can separate out the profiles making the release an all at once rather than running per type. Then we would end up with maven entries out in central like this in one go.

<groupId>org.grgrzybek</groupId>
<artifactId>tomcat-slf4j-logback-6.0.43</artifactId>
<version>1.0.0</version>

<groupId>org.grgrzybek</groupId>
<artifactId>tomcat-slf4j-logback-7.0.61</artifactId>
<version>1.0.0</version>

<groupId>org.grgrzybek</groupId>
<artifactId>tomcat-slf4j-logback-8.0.21</artifactId>
<version>1.0.0</version>

<groupId>org.grgrzybek</groupId>
<artifactId>tomcat-embed-slf4j-logback-6.0.43</artifactId>
<version>1.0.0</version>

<groupId>org.grgrzybek</groupId>
<artifactId>tomcat-embed-slf4j-logback-7.0.61</artifactId>
<version>1.0.0</version>

<groupId>org.grgrzybek</groupId>
<artifactId>tomcat-embed-slf4j-logback-8.0.21</artifactId>
<version>1.0.0</version>

Our underlying logging usage is fully defined in the manifest. So essentially we are just targetting a new release of tomcat. Each new release would start at version 1.0.0. Increases would be for slf4j, logback, or bug fixes. While this makes it less than clean for plugins such as the version plugin when checking for new releases, it makes it work well with the multi-module approach.

Any thoughts to this?

from tomcat-slf4j-logback.

Sonatype 'com.github.grgrzybek' has been created. If you request access on the issue I opened over there (earlier comment on this thread), I can grant you access as well. Next step is to decide how exactly to get these out there. I have also switched the group id over on the project for this purpose and tied the pom into sonatype setup.

from tomcat-slf4j-logback.

Tried to perform a release to see if it would work. Sourceforge won't let me upload for some reason so seemed like a good time. At the moment this fails for two following issues. So if we can solve those would should be able to release.

Event: Failed: Signature Validation
Tuesday, July 28, 2015 22:39:28 EST (GMT-0400)
typeId signature-staging
failureMessage Missing Signature: '/com/github/grgrzybek/tomcat-slf4j-logback/1.2.2/tomcat-slf4j-logback-1.2.2-7.0.63-slf4j-1.7.12-logback-1.1.3.zip.asc' does not exist for 'tomcat-slf4j-logback-1.2.2-7.0.63-slf4j-1.7.12-logback-1.1.3.zip'.

Event: Failed: Javadoc Validation
Tuesday, July 28, 2015 22:39:29 EST (GMT-0400)
typeId javadoc-staging
failureMessage Missing: no javadoc jar found in folder '/com/github/grgrzybek/tomcat-slf4j-logback/1.2.2'

from tomcat-slf4j-logback.

To release, source jar and zip need deleted on distribution. This will be noted on the README as notes are being placed there. For reference, maven distribution is really intended for developers that build tomcat distributions to make it easy to grab a copy of this binary the maven way.

from tomcat-slf4j-logback.