An alternative would be to setup a custom repository - that way, the only
step that's necessary but wouldn't be when synching to Maven central is
adding that repository to the POM file (a really small nuisance if you ask
me). Of course, if a synch with the default repository is possible, that
would be superior - even then, setting up a custom repository (which is not
hard to do) might be an intermediate solution.
Another point - should Stripes change its build system, I think Gradle (
http://gradle.org) would be a much nicer choice than Maven. It does
everything Maven can do (including pom.xml generation, uploading etc.), but
in a more elegant, more concise, *more Stripesy* way ;) More and more
projects consider moving over to Gradle (Groovy, Grails, Hibernate to name a
few). Note that I am in no way affiliated with Gradle, I'm just a happy user
:)
2010/9/3 Stone, Timothy <[email protected]>
> List,
>
> The intense interest in the future of Stripes is exciting.
>
> I’ve lost the specific email, but I want to touch on the Maven-ization of
> the 1.5 and 1.6 release lines.
>
> Should this be completed by the project leads, instead of hosting a project
> Maven repos (and the overhead involved), consider the OSSRH project by the
> Nexus team.
>
> Two immediate reasons Stripes leads want to do this:
>
>
> 1. The Nexus hosted OSSRH project is an approved forge for syncing to
> Maven Central. Want adoption?
>
>
> Stripes *must* have Maven Central availability. I would call any Stripes
> Maven-ization effort that did not have Maven Central availability a
> non-starter.
>
> 2. The Maven Central is many times the only approved repository in large
> organizations for mirroring though internal Nexus and Artifactory maven
> repos.
>
> Without Maven Central syncs then updates to the library become manual.
> Anything that can be automated, and is not, is weight on adoption rates.
>
> (sorry for spamming the list... Fat fingered the short cut for sending
> email trying to line break my numbered list).
>
> Regards,
> Tim
> --
> Timothy Stone | Director, Application Developer Technical Lead
> Barclaycard | Business Technology Group, Solutions Delivery
> 125 S. West Street | Wilmington, DE | 19801
> USA | www.barclaycardus.com
> +1 302 255 8044 direct | +1 410 441 9450 cell
>
> COMPANY CONFIDENTIAL
>
> P Before printing this e-mail, or any other document, ask yourself whether
> you need a hard copy
>
>
>
> _______________________________________________________
>
> Barclays
> www.barclaycardus.com
> _______________________________________________________
>
> This e-mail and any files transmitted with it may contain confidential
> and/or proprietary information. It is intended solely for the use of the
> individual or entity who is the intended recipient. Unauthorized use of this
> information is prohibited. If you have received this in error, please
> contact the sender by replying to this message and delete this material from
> any system it may be on.
>
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Stripes-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
>
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
