Patch applied

I rescheduled all the issues that awaited fixes out of 2.0-a-5.

It is important to note that NOW the archetype plugin search its
catalog in http://repo1.maven.org/maven2/archetype-catalog.xml

Alas that catalog is not deployed YET. Some solutions are possible to
have that file :
1. run the crawl mojo against the central repo (physically. it is a FS mojo)
2. have the catalog generated by a nexus. I know Tamas has created a
nexus addon that can do that.

If the central catalog is not found. The plugin defaults on the
internal catalog. That catalog is created (i have a test case for it)
just before i call a vote against the latest version of the MAVENUSER
page listing the archetypes.
Obviously the testcase tries each the archetypes form the mavenuser
page and keeps only those that can be used to generate a project with.

Brian. What do you think of putting a catalog at root of central? How
do you think this could be done?


Regards.

Raphaël

Le 24 mars 2009 09:06, Raphaël Piéroni <raphaelpier...@gmail.com> a écrit :
> I applied the archetype-234 patch on the trunk at home,
> but didn't comitted yet on apache svn.
>
> I run the build with the patch and it is not broken ;-)
>
> I think i will commit it tonite (still morning now).
>
> I will also reshedule the issues for the next 2.0-a-5 and call for a vote.
>
> I was a little absorbed since last release by rewriting the plugin in
> groovy as one
> feature, i dunno how to implement in java. (having nested archetypes)
>
> If your insterested, i uploaded my groovy experiment in a branch las nite.
>
>
> Regards,
>
> Raphaël
>
>
> I nearly forgotten that i MUST also work on the default behaviour for
> archetype selection.
> Since i changed in the code from using a catalog on repo instead of an
> internal catalog.
> But i should roll back since repo1 don't expose yet a catalog of all 
> archetypes.
>
>
>
> 2009/3/24 Brett Porter <br...@apache.org>:
>> I think I can set aside some time later this week/early next week to work
>> through patches for the plugin and any issues important for the next
>> release.
>>
>> Raphaël, do you have any time to sync up on this?
>>
>> Cheers,
>> Brett
>>
>> On 24/03/2009, at 11:59 AM, djrobo wrote:
>>
>>>
>>> My team is also badly in need of the new archetype plugin to be released.
>>> Clearly development on the archetype plugin has been put on the
>>> back-burner
>>> lately, but it would be nice if the current fixes could be made available
>>> in
>>> the mean time.
>>>
>>>
>>> Jason Voegele wrote:
>>>>
>>>> We have a few archetypes that rely on features of the new
>>>> maven-archetype-
>>>> plugin version 2.0-alpha-4.  In fact, right now these archetypes only
>>>> work
>>>> using a locally patched version of maven-archetype-plugin.  Our patch
>>>> (for
>>>> ARCHETYPE-110) has already been applied to maven-archetype in trunk, but
>>>> there
>>>> has not been a new release of maven-archetype since that time.  Would it
>>>> be
>>>> possible to release the 2.0-alpha-5 version any time soon?
>>>>
>>>> I have also submitted another patch for ARCHETYPE-234 that would be
>>>> extremely
>>>> useful to us.  Any chance this patch could be applied and incorporated
>>>> into
>>>> the 2.0-alpha-5 release?
>>>>
>>>> Thanks for any help you can provide.
>>>>
>>>> --
>>>> Jason Voegele
>>>> If society fits you comfortably enough, you call it freedom.
>>>>                -- Robert Frost
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Release-for-maven-archetype-plugin-tp22667328p22672498.html
>>> Sent from the Maven Developers mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>> --
>> Brett Porter
>> br...@apache.org
>> http://blogs.exist.com/bporter/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to