Stripes

Request for uploading Stripes 1.5.3 on http://repo1.maven.org/

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: Release 1.5.3
  • Fix Version/s: Release 1.5.3
  • Component/s: None
  • Labels:
    None

Description

We have some projects depending from Stripes 1.5.3 but this version is not yet avalaible on the repo1.maven.org repository.

Because we have deployed on a local server the version 1.5.3, we have files:

  • stripes-1.5.3-sources.jar
  • stripes-1.5.3-sources.jar.md5
  • stripes-1.5.3-sources.jar.sha1
  • stripes-1.5.3.jar
  • stripes-1.5.3.jar.md5
  • stripes-1.5.3.jar.sha1
  • stripes-1.5.3.pom
  • stripes-1.5.3.pom.md5
  • stripes-1.5.3.pom.sha1
    needed to uploading the artifacts to the official repository. If you want, we can give you this files.

I hope you can upload soon your library becuase we need it on the official repository.

Thanks,

Manuela

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Timothy Stone added a comment - 03/May/10 9:03 AM

One option is to sync to Central via the OSS Repository Host available from Sonatype. The Sonatype "Forge" is an authorized repository that syncs to central.

Details are here: https://docs.sonatype.com/display/NX/OSS+Repository+Hosting

Show
Timothy Stone added a comment - 03/May/10 9:03 AM One option is to sync to Central via the OSS Repository Host available from Sonatype. The Sonatype "Forge" is an authorized repository that syncs to central. Details are here: https://docs.sonatype.com/display/NX/OSS+Repository+Hosting
Hide
Permalink
Nikolaos added a comment - 03/May/10 10:26 AM

There are simpler workarounds IMO however they are ALL workarounds. If all other versions of Stripes made it to repo1 I can't see why 1.5.3 isn't being pushed up to it as well regardless of the mechanism.

What we did is simply add 1.5.3 to our local maven repository which was dirt simple to setup:

  • Unpack Tomcat and setup a JDK
  • Create a folder say "m2" under webapps
  • Under the following folder structure place these two files:
    m2/other/net/sourceforge/stripes/stripes/1.5.3/stripes-1.5.3.pom
    m2/other/net/sourceforge/stripes/stripes/1.5.3/stripes-1.5.3.jar
    NOTE: stripes-1.5.3.pom is simply the 1.5.2 pom with the version changed to 1.5.3 (if you pointed to 1.5.2 before then dig under your ~/.m2 subfolders for 1.5.2 pom)
  • Add your local maven repository to your pom

With that said - the BEST option would still be to have it uploaded to central because even if the above is simple the simplest thing would be changing the version in your pom dependency to 1.5.3 and clicking a button or running a command. Anything else is going to negatively affect the adoption of Stripes... PERIOD... b/c most developers will see this as a weakness and a "we do not care" attitude from what is already a small developer / user community.

Show
Nikolaos added a comment - 03/May/10 10:26 AM There are simpler workarounds IMO however they are ALL workarounds. If all other versions of Stripes made it to repo1 I can't see why 1.5.3 isn't being pushed up to it as well regardless of the mechanism. What we did is simply add 1.5.3 to our local maven repository which was dirt simple to setup:
  • Unpack Tomcat and setup a JDK
  • Create a folder say "m2" under webapps
  • Under the following folder structure place these two files: m2/other/net/sourceforge/stripes/stripes/1.5.3/stripes-1.5.3.pom m2/other/net/sourceforge/stripes/stripes/1.5.3/stripes-1.5.3.jar NOTE: stripes-1.5.3.pom is simply the 1.5.2 pom with the version changed to 1.5.3 (if you pointed to 1.5.2 before then dig under your ~/.m2 subfolders for 1.5.2 pom)
  • Add your local maven repository to your pom
With that said - the BEST option would still be to have it uploaded to central because even if the above is simple the simplest thing would be changing the version in your pom dependency to 1.5.3 and clicking a button or running a command. Anything else is going to negatively affect the adoption of Stripes... PERIOD... b/c most developers will see this as a weakness and a "we do not care" attitude from what is already a small developer / user community.
Hide
Permalink
Timothy Stone added a comment - 03/May/10 11:43 AM

I agree with Nikolaos' sentiment that without Central syncing, Stripes, regardless of anyone's evangelism, will not be taking seriously.

The Stripes' stewards would be best advised to get the project syncing automatically to Maven Central. The "dirt simple" way of doing this is to go to a "forge". Maven Central authorizes only four (4) forges for automatic syncing:

  • Apache (open to Apache Projects)
  • Codehaus (open to Codehaus Projects)
  • Sonatype Forge (open to any OSS Project)
  • Fusesource Forge (Focused on FUSE related projects)

Stripes could start immediate syncing to Central for existing releases by opening a ticket as described above in my earlier comment with Sonatype. Sonatype snapshot hosting is also supported (consider snapshots of trunk) by calling them out the local settings.xml or the POM directly.

Show
Timothy Stone added a comment - 03/May/10 11:43 AM I agree with Nikolaos' sentiment that without Central syncing, Stripes, regardless of anyone's evangelism, will not be taking seriously. The Stripes' stewards would be best advised to get the project syncing automatically to Maven Central. The "dirt simple" way of doing this is to go to a "forge". Maven Central authorizes only four (4) forges for automatic syncing:
  • Apache (open to Apache Projects)
  • Codehaus (open to Codehaus Projects)
  • Sonatype Forge (open to any OSS Project)
  • Fusesource Forge (Focused on FUSE related projects)
Stripes could start immediate syncing to Central for existing releases by opening a ticket as described above in my earlier comment with Sonatype. Sonatype snapshot hosting is also supported (consider snapshots of trunk) by calling them out the local settings.xml or the POM directly.
Hide
Permalink
Ben Gunter added a comment - 18/May/10 1:07 PM

In case you missed my note on the mailing list the other day, I'm working on getting this going through Sonatype. I'll resolve this issue when it's done.

Show
Ben Gunter added a comment - 18/May/10 1:07 PM In case you missed my note on the mailing list the other day, I'm working on getting this going through Sonatype. I'll resolve this issue when it's done.
Hide
Permalink
Janne Jalkanen added a comment - 23/Sep/10 5:30 AM

Just bumping this one up - what's going on?

Show
Janne Jalkanen added a comment - 23/Sep/10 5:30 AM Just bumping this one up - what's going on?
Hide
Permalink
Marcus Kraßmann added a comment - 23/Sep/10 6:57 AM

Actually Remi Vankeisbelck "mavenized" Stripes yesterday. It just needs some testing, but then it hopefully allows automatic synchronization with Sonatype.

Keep your fingers crossed

Show
Marcus Kraßmann added a comment - 23/Sep/10 6:57 AM Actually Remi Vankeisbelck "mavenized" Stripes yesterday. It just needs some testing, but then it hopefully allows automatic synchronization with Sonatype. Keep your fingers crossed
Hide
Permalink
Janne Jalkanen added a comment - 24/Sep/10 8:37 AM

Confirming fixed; Ivy found it immediately. Thanks!

Show
Janne Jalkanen added a comment - 24/Sep/10 8:37 AM Confirming fixed; Ivy found it immediately. Thanks!

People

Vote (7)
Watch (2)

Dates

  • Created:
    09/Feb/10 4:57 AM
    Updated:
    04/Jan/11 1:28 PM
    Resolved:
    24/Sep/10 8:26 AM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for Stripes Framework. Try JIRA - bug tracking software for your team.