Getting artifacts scheduled for inclusion into the main repo is actually
not that problematic. It's slow, apparently, to get set up but syncs
regularly (nightly?) once that's setup. And it can sync from any url
publicly visible. The bigger question in my mind is the political one
of moving outside of the Sun "sanctioned" java.net ecosystem. That'll
probably be the biggest hurdle. The technical questions are doable.
Jason Lee wrote:
> On Mar 3, 2009, at 8:58 AM, Jeanfrancois Arcand wrote:
>
>> Slaut,
>>
>> Oleksiy Stashok wrote:
>>> I'm not sure moving to Kenai will help us a lot. Currently the
>>> biggest problem for project I see - is problem with uploading
>>> artifacts to the m2 maven repository. If we will move to Kenai, will
>>> we move to different maven repository?
>>
>> Yes...that's why we need to make sure we take the right decision :-)
>
>
> Yes, and, currently, kenai doesn't offer a maven repo. I've found
> with my two projects on there, though, that the infrastructure to be
> easier, faster and more stable. :) And, for my projects, I didn't
> have such a large user base to worry about. :P
>
> Jason Lee
> Senior Java Developer
> GlassFish Administration Console
>
> Sun Microsystems, Inc.
> Phone x31197/+1 405-343-1964
> Email jasondlee_at_sun.com
> Blog http://blogs.sun.com/jasondlee
> Blog http://blogs.steeplesoft.com
>
>