Hi
It seems, i have reached the alpha release point with
revision 4046.
Regards,
Raphaël
2007/4/25, Brett Porter <[EMAIL PROTECTED]>:
Well, it sounds like you've got some more working happening now. What
I'd suggest is that you get it to the point where you think it is
ready for an alpha rele
Well, it sounds like you've got some more working happening now. What
I'd suggest is that you get it to the point where you think it is
ready for an alpha release - that would be a good point to replace
the existing code.
- Brett
On 13/04/2007, at 7:57 PM, Raphaël Piéroni wrote:
Hi,
fee
Hi,
feel free to steal the code from mojo.
but please, let me be informed as i could still contribute with patches.
Raphaël
2007/4/9, Brett Porter <[EMAIL PROTECTED]>:
I think we should continue to use ARCHETYPE and start planning
towards a 1.0 with the new code base. The current JIRA will nee
I think we should continue to use ARCHETYPE and start planning
towards a 1.0 with the new code base. The current JIRA will need a
clean up to see what issues are still relevant in the new code base,
of course.
- Brett
On 09/04/2007, at 5:02 AM, Franz Allan Valencia See wrote:
Curious,..
Curious,..
Where is the jira issue(s) for this? ..Can't seem to find them :-)
Thanks,
Franz
On 4/1/07, Milos Kleint <[EMAIL PROTECTED]> wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 1 Apr 07, at 6:49 AM 1 Apr 07, Milos Kleint wrote:
>
> >>
> >
> > exactly this is a showsto
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 6:49 AM 1 Apr 07, Milos Kleint wrote:
>>
>
> exactly this is a showstopper for me in the current archetype when I
> attempted to create an archetype for netbeans module development. I
> need to place Bundle.properties and layer
On 1 Apr 07, at 6:49 AM 1 Apr 07, Milos Kleint wrote:
exactly this is a showstopper for me in the current archetype when I
attempted to create an archetype for netbeans module development. I
need to place Bundle.properties and layer.xml file in resources into
the proper package.
That's fi
Hi,
I didn't expected so many answers :)
for archetype, there is two process:
- generation of a project from an archetype
- creation of an archetype from a project
The generation reads the descriptor and files in jar to
generate the project's files. The required properties
are used as extra con
On 3/31/07, Heinrich Nirschl <[EMAIL PROTECTED]> wrote:
On 3/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 31 Mar 07, at 12:08 PM 31 Mar 07, Heinrich Nirschl wrote:
>
> > On 3/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >>
> >> On 31 Mar 07, at 10:07 AM 31 Mar 07, Raphaël Piéroni w
On 3/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 31 Mar 07, at 12:08 PM 31 Mar 07, Heinrich Nirschl wrote:
> On 3/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>>
>> On 31 Mar 07, at 10:07 AM 31 Mar 07, Raphaël Piéroni wrote:
>>
>> > Hi here comes a new proposition for the future descr
On 31 Mar 07, at 12:08 PM 31 Mar 07, Heinrich Nirschl wrote:
On 3/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 31 Mar 07, at 10:07 AM 31 Mar 07, Raphaël Piéroni wrote:
> Hi here comes a new proposition for the future descriptor.
>
> I made it the most simpler i can think.
>
> Please co
On 3/31/07, Raphaël Piéroni <[EMAIL PROTECTED]> wrote:
Hi here comes a new proposition for the future descriptor.
I made it the most simpler i can think.
Please comment it.
Regards,
Raphaël
Why not make the properties just like they ar
On 3/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 31 Mar 07, at 10:07 AM 31 Mar 07, Raphaël Piéroni wrote:
> Hi here comes a new proposition for the future descriptor.
>
> I made it the most simpler i can think.
>
> Please comment it.
>
I think it duplicates too much that's in the POM. T
On 31 Mar 07, at 10:07 AM 31 Mar 07, Raphaël Piéroni wrote:
Hi here comes a new proposition for the future descriptor.
I made it the most simpler i can think.
Please comment it.
I think it duplicates too much that's in the POM. The POM should be
the model that used for Archetype wherever
Hi here comes a new proposition for the future descriptor.
I made it the most simpler i can think.
Please comment it.
Regards,
Raphaël
src/main/java
**/*.java
Hi,
Refactored to use almost the same behaviour as archetype-1.0-alpha-4.
The ones made are:
- goals names create and create-from-project,
- propagate on old code when resolving to an old archetype during create goal.
What is not backward compatible:
- the ${remoteRepositories} property is not u
On 24/03/2007, at 4:24 AM, Raphaël Piéroni wrote:
This looks very good. The only thing I noticed was that the goal
names were still the same, which I think in the earlier mail we were
going to change?
Exactly, but i wanted to first document. The complete refactor of the
names implies the refa
Hi
Answers inlined.
2007/3/23, Brett Porter <[EMAIL PROTECTED]>:
Hi,
Sorry for being sluggish :)
On 21/03/2007, at 8:41 AM, Raphaël Piéroni wrote:
> Hi,
>
> Do any one had the time to comment the sources and/or the first doco
> http://mojo.codehaus.org/maven-archetypeng ?
This looks very goo
Hi,
Sorry for being sluggish :)
On 21/03/2007, at 8:41 AM, Raphaël Piéroni wrote:
Hi,
Do any one had the time to comment the sources and/or the first doco
http://mojo.codehaus.org/maven-archetypeng ?
This looks very good. The only thing I noticed was that the goal
names were still the sam
Hi,
Do any one had the time to comment the sources and/or the first doco
http://mojo.codehaus.org/maven-archetypeng ?
Here is a proposition of refactored descriptor which attemps
to introduce: the use of attributes, the possibility to copy files,
and customised template groups (root, 1->3° level
Awesome!
Incidentally does your plugin have the ability to evaluate the maven name
element when it processes the archetype templates?
There is a patch for the current archetype plugin here:
http://jira.codehaus.org/browse/ARCHETYPE-55
But if yours does it already, I'm skipping the patching and
Hi,
I added it on my todo list.
Raphaël
2007/3/19, Ole Ersoy <[EMAIL PROTECTED]>:
Hi Raphael,
Sounds like you are doing some terrific work.
If you have time, could you please take a look at this bug:
http://jira.codehaus.org/browse/MNG-2856
When the current archetype plugin processes png i
Hi Raphael,
Sounds like you are doing some terrific work.
If you have time, could you please take a look at this bug:
http://jira.codehaus.org/browse/MNG-2856
When the current archetype plugin processes png images, it changes them,
and makes the unreadable.
I think if we add a element (pos
The first draft of the doco is updated (same place) with explains on mojos
and internal design.
But this doesn't prevent from reading the sources :-) (for more design
information).
My next step is now sorting the todo list and enhance with suggestions.
Jason gave me karma on the current archety
A late addition.
I just commited a start of doco. which could be seen at
http://mojo.codehaus.org/maven-archetypeng/
Raphael
Answers inlined.
Raphaël
2007/3/13, Brett Porter <[EMAIL PROTECTED]>:
On 12/03/2007, at 3:36 AM, Raphaël Piéroni wrote:
> Is backward compatibility for archetype only the recognition of the
> old
> descriptor and pathes resolution ?
yes, if you generate from an old archetype you get the sam
On 12/03/2007, at 3:36 AM, Raphaël Piéroni wrote:
Is backward compatibility for archetype only the recognition of the
old
descriptor and pathes resolution ?
yes, if you generate from an old archetype you get the same thing as
if you create now.
The selection step of the proposition can
Oups,
I forgotten to say that archetypes is the first foot a developper starts for
using maven.
This is why i'm concerned about archetypes.
I also see archetypes a examples of using maven (for example the axistools)
Raphaël
2007/3/12, Raphaël Piéroni <[EMAIL PROTECTED]>:
My current task is no
My current task is now to document what i have done so far.
Answers and questions inlined.
Raphaël
2007/3/12, Brett Porter <[EMAIL PROTECTED]>:
My basic feedback would be similar to Jason's.
Key requirements:
- backwards compatibility with existing archetypes is a definite
requirement
Is
My basic feedback would be similar to Jason's.
Key requirements:
- backwards compatibility with existing archetypes is a definite
requirement
- existing goal names need to continue to work, even if they are
deprecated
- if it's being designed from the ground up, it should have new
standards
On 8 Mar 07, at 10:54 AM 8 Mar 07, Raphaël Piéroni wrote:
Hi all,
Here is the resent of a mail i sent on [EMAIL PROTECTED]
I would like to introduce the work i have done so far concerning
archetypes.
I have improved the current archetype mecanism by adding
- the interactive selection of th
Hi all,
Here is the resent of a mail i sent on [EMAIL PROTECTED]
I would like to introduce the work i have done so far concerning archetypes.
I have improved the current archetype mecanism by adding
- the interactive selection of the archetype to create a project from
- the interactive configura
32 matches
Mail list logo
