On 23/05/2007, at 9:55 PM, Raphaël Piéroni wrote:

Could that point  should be marked as a non mandatory backward
incompatibility ?
Because i dunno how to forbid prompting behaviour unless the usage of this
option.

For the old goal names, we can use the default as false instead of relying on ${settings.interactivity}

>
> * after selecting values I get "Confirm archetype
>> selection:org.apache.maven.archetypes/null".
>
> Can i have the full trace please?

It wasn't a trace - that was the output on the line after selection.


Sory i meant which are the steps for me to reproduce?

mvn archetypeng:create -DarchetypeArtifactId=maven-archetype-webapp

Choose version:
1: 1.0-alpha-4
2: 1.0
Choose a number:  (1/2): 3

Confirm archetype selection:
org.apache.maven.archetypes/null
(Y/N) Y: :


(though I did get an IOException in the middle:
IOExceptionjava.io.IOException: The META-INF/maven/archetype.xml
descriptor cannot be found.)

The descriptor is first searched there, maybe the Exception should not be
visible.

Agreed.

* Is the archetype descriptor required to do anything, or is it
>> optional?
>
> The META-INF/maven/archetype.xml is mandatory

Aren't there conventions that can be followed that would mean the
archetype descriptor can be generated with sensible defaults? I think
that would be a good way to go.


Do you mean some use case like this?
an archetype project without the descriptor
where the descriptor is generated before package phase.
But only when the descriptor is absent.

If I look at the 'maven-archetypeng-start' archetype, I think you could assume *.java are templates, with src/main being the main group and src/test being the test group, so you can 'guess' all the archetype descriptor settings from the defaults. Does that make sense?

The descriptor which reside in the archetype's artifact is used
for generating a project from that archetype.

The descriptor is created by the create-from-project goal
(or by hand)

During the time the archetype is created from a project (or by hand)
and the time it is uploaded as a jar, the descriptor is only a resource.

I hope this answer your question (if not, maybe i don't have understood the
question)


I think I may be confused too - I'll take a look at the implementation and let you know if I still think there's a problem :)

Probably easiest to look at some existing Maven code and try
reformatting it, then adjusting your settings until the reformat
keeps it as it was :) If you could share the netbeans settings for
that, that'd be great!

Netbeans settings can't be shared, the formatting for xml is poor enough
just the tab vs space and space size of indent.

Thought they'd fixed that in more recent versions :(

Nope move the list in the "registry"
the file at ~/.m2/archetype.xml is what i call the registry.
It currently holds the list of archetype groups, the list of repositories
wher to find archetypes,
the list of languages and the list of filtered extensions.

Isn't that a problem if two different people with different settings files try to use the goal in the same way and get different results?


So just take the code, i will not do anything untill tomorrow.
Then i will use svn switch...

Process is a bit longer than that - but we'll move towards that.

Cheers,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to