Change in behavior of maven-archetype-plugin

View: New views
9 Messages — Rating Filter:   Alert me  

Change in behavior of maven-archetype-plugin

by Wendy Smoak-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

The Archetype plugin has lost the ability to "package" non-Java
resources.  It looks like this happened with the addition of 'sub
packages' for Java sources.

For example, you might want to place App.properties in
src/main/resources/com/example/App.properties in the generated app, as
a companion to src/main/java/com/example/App.java.

Brett, (since it was your change,) can you please take a look at
http://jira.codehaus.org/browse/ARCHETYPE-65 ?  Is there a way to
package both source and resources, without losing the 'sub-package'
feature?

(I'll take a look at the mojo-sandbox project also, I assume it's this one:
http://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/maven-archetypeng/ )

--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Change in behavior of maven-archetype-plugin

by Wendy Smoak-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 3/4/07, Wendy Smoak <wsmoak@...> wrote:

> The Archetype plugin has lost the ability to "package" non-Java
> resources.  It looks like this happened with the addition of 'sub
> packages' for Java sources.

ping. Any thoughts on whether the problem with "packaging" resources
should be fixed in the existing archetype code or whether
maven-archetypeng will be ready soon?

It's http://jira.codehaus.org/browse/ARCHETYPE-65 .

--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Change in behavior of maven-archetype-plugin

by brettporter :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

It seems apparent now that we should push forward with the ng stuff.  
I was going to test if it is at least equivalent to trunk and then  
propose bringing it in to replace trunk and start to plan out 1.0  
from there.

Does anyone have any bandwidth to help with that?

Thanks,
Brett

On 09/04/2007, at 12:37 PM, Wendy Smoak wrote:

> On 3/4/07, Wendy Smoak <wsmoak@...> wrote:
>
>> The Archetype plugin has lost the ability to "package" non-Java
>> resources.  It looks like this happened with the addition of 'sub
>> packages' for Java sources.
>
> ping. Any thoughts on whether the problem with "packaging" resources
> should be fixed in the existing archetype code or whether
> maven-archetypeng will be ready soon?
>
> It's http://jira.codehaus.org/browse/ARCHETYPE-65 .
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Change in behavior of maven-archetype-plugin

by Jason van Zyl-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On 8 Apr 07, at 10:41 PM 8 Apr 07, Brett Porter wrote:

> It seems apparent now that we should push forward with the ng  
> stuff. I was going to test if it is at least equivalent to trunk  
> and then propose bringing it in to replace trunk and start to plan  
> out 1.0 from there.
>

It doesn't work the same yet, the mojos are just stubbed out and I  
have yet to get it to create an archetype though the tests are pretty  
good so far.

> Does anyone have any bandwidth to help with that?

I will walk through the code in its entirety but not until next week.

Jason.

>
> Thanks,
> Brett
>
> On 09/04/2007, at 12:37 PM, Wendy Smoak wrote:
>
>> On 3/4/07, Wendy Smoak <wsmoak@...> wrote:
>>
>>> The Archetype plugin has lost the ability to "package" non-Java
>>> resources.  It looks like this happened with the addition of 'sub
>>> packages' for Java sources.
>>
>> ping. Any thoughts on whether the problem with "packaging" resources
>> should be fixed in the existing archetype code or whether
>> maven-archetypeng will be ready soon?
>>
>> It's http://jira.codehaus.org/browse/ARCHETYPE-65 .
>>
>> --
>> Wendy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Change in behavior of maven-archetype-plugin

by Raphaël :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2007/4/9, Jason van Zyl <jason@...>:

>
> On 8 Apr 07, at 10:41 PM 8 Apr 07, Brett Porter wrote:
>
> > It seems apparent now that we should push forward with the ng
> > stuff. I was going to test if it is at least equivalent to trunk
> > and then propose bringing it in to replace trunk and start to plan
> > out 1.0 from there.
> >
>
> It doesn't work the same yet, the mojos are just stubbed out and I
> have yet to get it to create an archetype though the tests are pretty
> good so far.

Really please to ear ;)

I will, starting from next week, refactor the descriptor as proposed.

Raphaël


>
> > Does anyone have any bandwidth to help with that?
>
> I will walk through the code in its entirety but not until next week.
>
> Jason.
>
> >
> > Thanks,
> > Brett
> >
> > On 09/04/2007, at 12:37 PM, Wendy Smoak wrote:
> >
> >> On 3/4/07, Wendy Smoak <wsmoak@...> wrote:
> >>
> >>> The Archetype plugin has lost the ability to "package" non-Java
> >>> resources.  It looks like this happened with the addition of 'sub
> >>> packages' for Java sources.
> >>
> >> ping. Any thoughts on whether the problem with "packaging" resources
> >> should be fixed in the existing archetype code or whether
> >> maven-archetypeng will be ready soon?
> >>
> >> It's http://jira.codehaus.org/browse/ARCHETYPE-65 .
> >>
> >> --
> >> Wendy
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@...
> >> For additional commands, e-mail: dev-help@...
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

Re: Change in behavior of maven-archetype-plugin

by franz see :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Btw, what is the proposed new descriptor format? :-)

On 4/13/07, Raphaël Piéroni <raphaelpieroni@...> wrote:

> 2007/4/9, Jason van Zyl <jason@...>:
> >
> > On 8 Apr 07, at 10:41 PM 8 Apr 07, Brett Porter wrote:
> >
> > > It seems apparent now that we should push forward with the ng
> > > stuff. I was going to test if it is at least equivalent to trunk
> > > and then propose bringing it in to replace trunk and start to plan
> > > out 1.0 from there.
> > >
> >
> > It doesn't work the same yet, the mojos are just stubbed out and I
> > have yet to get it to create an archetype though the tests are pretty
> > good so far.
>
> Really please to ear ;)
>
> I will, starting from next week, refactor the descriptor as proposed.
>
> Raphaël
>
>
> >
> > > Does anyone have any bandwidth to help with that?
> >
> > I will walk through the code in its entirety but not until next week.
> >
> > Jason.
> >
> > >
> > > Thanks,
> > > Brett
> > >
> > > On 09/04/2007, at 12:37 PM, Wendy Smoak wrote:
> > >
> > >> On 3/4/07, Wendy Smoak <wsmoak@...> wrote:
> > >>
> > >>> The Archetype plugin has lost the ability to "package" non-Java
> > >>> resources.  It looks like this happened with the addition of 'sub
> > >>> packages' for Java sources.
> > >>
> > >> ping. Any thoughts on whether the problem with "packaging" resources
> > >> should be fixed in the existing archetype code or whether
> > >> maven-archetypeng will be ready soon?
> > >>
> > >> It's http://jira.codehaus.org/browse/ARCHETYPE-65 .
> > >>
> > >> --
> > >> Wendy
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@...
> > >> For additional commands, e-mail: dev-help@...
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@...
> > > For additional commands, e-mail: dev-help@...
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Change in behavior of maven-archetype-plugin

by Raphaël :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Sorry,

you can see in the sources
in the first comment of the archetype-descriptor-new.xml in
the archetypeng-archetype-descriptor project.

It has been commented in the "plugin proposition" mail thread.

I copy here:
        <archetype id="archetype-artifact-id" partial="true|false" >
           <requiredProperties>
               <requiredProperty key="propKey" defaultValue="string to
replace" />
           </requiredProperties>
           <fileSets>
               <fileSet filtered="true|false" packaged="true|false" />
                   <directory>src/main/java</directory>
                   <includes>
                       <include>**/*.java</include>
                   </includes>
                   <excludes>
                       <exclude>Main.java</exclude>
                   </excludes>
               </fileSet>
           </file-sets>
           <modules>
               <module id="module-artifact-id">
                   <fileSets/>
                   <modules/>
               </module>
           </modules>
        </archetype>

2007/4/15, Franz Allan Valencia See <franz.see@...>:

> Btw, what is the proposed new descriptor format? :-)
>
> On 4/13/07, Raphaël Piéroni <raphaelpieroni@...> wrote:
> > 2007/4/9, Jason van Zyl <jason@...>:
> > >
> > > On 8 Apr 07, at 10:41 PM 8 Apr 07, Brett Porter wrote:
> > >
> > > > It seems apparent now that we should push forward with the ng
> > > > stuff. I was going to test if it is at least equivalent to trunk
> > > > and then propose bringing it in to replace trunk and start to plan
> > > > out 1.0 from there.
> > > >
> > >
> > > It doesn't work the same yet, the mojos are just stubbed out and I
> > > have yet to get it to create an archetype though the tests are pretty
> > > good so far.
> >
> > Really please to ear ;)
> >
> > I will, starting from next week, refactor the descriptor as proposed.
> >
> > Raphaël
> >
> >
> > >
> > > > Does anyone have any bandwidth to help with that?
> > >
> > > I will walk through the code in its entirety but not until next week.
> > >
> > > Jason.
> > >
> > > >
> > > > Thanks,
> > > > Brett
> > > >
> > > > On 09/04/2007, at 12:37 PM, Wendy Smoak wrote:
> > > >
> > > >> On 3/4/07, Wendy Smoak <wsmoak@...> wrote:
> > > >>
> > > >>> The Archetype plugin has lost the ability to "package" non-Java
> > > >>> resources.  It looks like this happened with the addition of 'sub
> > > >>> packages' for Java sources.
> > > >>
> > > >> ping. Any thoughts on whether the problem with "packaging" resources
> > > >> should be fixed in the existing archetype code or whether
> > > >> maven-archetypeng will be ready soon?
> > > >>
> > > >> It's http://jira.codehaus.org/browse/ARCHETYPE-65 .
> > > >>
> > > >> --
> > > >> Wendy
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@...
> > > >> For additional commands, e-mail: dev-help@...
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@...
> > > > For additional commands, e-mail: dev-help@...
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@...
> > > For additional commands, e-mail: dev-help@...
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

Re: Change in behavior of maven-archetype-plugin

by Raphaël :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I pasted the whole modello file here http://rafb.net/p/E4CXrv28.html

Regards,


Raphaël

2007/4/15, Raphaël Piéroni <raphaelpieroni@...>:

> Sorry,
>
> you can see in the sources
> in the first comment of the archetype-descriptor-new.xml in
> the archetypeng-archetype-descriptor project.
>
> It has been commented in the "plugin proposition" mail thread.
>
> I copy here:
>         <archetype id="archetype-artifact-id" partial="true|false" >
>            <requiredProperties>
>                <requiredProperty key="propKey" defaultValue="string to
> replace" />
>            </requiredProperties>
>            <fileSets>
>                <fileSet filtered="true|false" packaged="true|false" />
>                    <directory>src/main/java</directory>
>                    <includes>
>                        <include>**/*.java</include>
>                    </includes>
>                    <excludes>
>                        <exclude>Main.java</exclude>
>                    </excludes>
>                </fileSet>
>            </file-sets>
>            <modules>
>                <module id="module-artifact-id">
>                    <fileSets/>
>                    <modules/>
>                </module>
>            </modules>
>         </archetype>
>
> 2007/4/15, Franz Allan Valencia See <franz.see@...>:
> > Btw, what is the proposed new descriptor format? :-)
> >
> > On 4/13/07, Raphaël Piéroni <raphaelpieroni@...> wrote:
> > > 2007/4/9, Jason van Zyl <jason@...>:
> > > >
> > > > On 8 Apr 07, at 10:41 PM 8 Apr 07, Brett Porter wrote:
> > > >
> > > > > It seems apparent now that we should push forward with the ng
> > > > > stuff. I was going to test if it is at least equivalent to trunk
> > > > > and then propose bringing it in to replace trunk and start to plan
> > > > > out 1.0 from there.
> > > > >
> > > >
> > > > It doesn't work the same yet, the mojos are just stubbed out and I
> > > > have yet to get it to create an archetype though the tests are pretty
> > > > good so far.
> > >
> > > Really please to ear ;)
> > >
> > > I will, starting from next week, refactor the descriptor as proposed.
> > >
> > > Raphaël
> > >
> > >
> > > >
> > > > > Does anyone have any bandwidth to help with that?
> > > >
> > > > I will walk through the code in its entirety but not until next week.
> > > >
> > > > Jason.
> > > >
> > > > >
> > > > > Thanks,
> > > > > Brett
> > > > >
> > > > > On 09/04/2007, at 12:37 PM, Wendy Smoak wrote:
> > > > >
> > > > >> On 3/4/07, Wendy Smoak <wsmoak@...> wrote:
> > > > >>
> > > > >>> The Archetype plugin has lost the ability to "package" non-Java
> > > > >>> resources.  It looks like this happened with the addition of 'sub
> > > > >>> packages' for Java sources.
> > > > >>
> > > > >> ping. Any thoughts on whether the problem with "packaging" resources
> > > > >> should be fixed in the existing archetype code or whether
> > > > >> maven-archetypeng will be ready soon?
> > > > >>
> > > > >> It's http://jira.codehaus.org/browse/ARCHETYPE-65 .
> > > > >>
> > > > >> --
> > > > >> Wendy
> > > > >>
> > > > >> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: dev-unsubscribe@...
> > > > >> For additional commands, e-mail: dev-help@...
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@...
> > > > > For additional commands, e-mail: dev-help@...
> > > > >
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@...
> > > > For additional commands, e-mail: dev-help@...
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
>

Re: Change in behavior of maven-archetype-plugin

by franz see :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I see, thanks :-) ..Sorry, I got lost in that thread as to which
descriptor was final :-)

On 4/15/07, Raphaël Piéroni <raphaelpieroni@...> wrote:

> I pasted the whole modello file here http://rafb.net/p/E4CXrv28.html
>
> Regards,
>
>
> Raphaël
>
> 2007/4/15, Raphaël Piéroni <raphaelpieroni@...>:
> > Sorry,
> >
> > you can see in the sources
> > in the first comment of the archetype-descriptor-new.xml in
> > the archetypeng-archetype-descriptor project.
> >
> > It has been commented in the "plugin proposition" mail thread.
> >
> > I copy here:
> >         <archetype id="archetype-artifact-id" partial="true|false" >
> >            <requiredProperties>
> >                <requiredProperty key="propKey" defaultValue="string to
> > replace" />
> >            </requiredProperties>
> >            <fileSets>
> >                <fileSet filtered="true|false" packaged="true|false" />
> >                    <directory>src/main/java</directory>
> >                    <includes>
> >                        <include>**/*.java</include>
> >                    </includes>
> >                    <excludes>
> >                        <exclude>Main.java</exclude>
> >                    </excludes>
> >                </fileSet>
> >            </file-sets>
> >            <modules>
> >                <module id="module-artifact-id">
> >                    <fileSets/>
> >                    <modules/>
> >                </module>
> >            </modules>
> >         </archetype>
> >
> > 2007/4/15, Franz Allan Valencia See <franz.see@...>:
> > > Btw, what is the proposed new descriptor format? :-)
> > >
> > > On 4/13/07, Raphaël Piéroni <raphaelpieroni@...> wrote:
> > > > 2007/4/9, Jason van Zyl <jason@...>:
> > > > >
> > > > > On 8 Apr 07, at 10:41 PM 8 Apr 07, Brett Porter wrote:
> > > > >
> > > > > > It seems apparent now that we should push forward with the ng
> > > > > > stuff. I was going to test if it is at least equivalent to trunk
> > > > > > and then propose bringing it in to replace trunk and start to plan
> > > > > > out 1.0 from there.
> > > > > >
> > > > >
> > > > > It doesn't work the same yet, the mojos are just stubbed out and I
> > > > > have yet to get it to create an archetype though the tests are pretty
> > > > > good so far.
> > > >
> > > > Really please to ear ;)
> > > >
> > > > I will, starting from next week, refactor the descriptor as proposed.
> > > >
> > > > Raphaël
> > > >
> > > >
> > > > >
> > > > > > Does anyone have any bandwidth to help with that?
> > > > >
> > > > > I will walk through the code in its entirety but not until next week.
> > > > >
> > > > > Jason.
> > > > >
> > > > > >
> > > > > > Thanks,
> > > > > > Brett
> > > > > >
> > > > > > On 09/04/2007, at 12:37 PM, Wendy Smoak wrote:
> > > > > >
> > > > > >> On 3/4/07, Wendy Smoak <wsmoak@...> wrote:
> > > > > >>
> > > > > >>> The Archetype plugin has lost the ability to "package" non-Java
> > > > > >>> resources.  It looks like this happened with the addition of 'sub
> > > > > >>> packages' for Java sources.
> > > > > >>
> > > > > >> ping. Any thoughts on whether the problem with "packaging" resources
> > > > > >> should be fixed in the existing archetype code or whether
> > > > > >> maven-archetypeng will be ready soon?
> > > > > >>
> > > > > >> It's http://jira.codehaus.org/browse/ARCHETYPE-65 .
> > > > > >>
> > > > > >> --
> > > > > >> Wendy
> > > > > >>
> > > > > >> ---------------------------------------------------------------------
> > > > > >> To unsubscribe, e-mail: dev-unsubscribe@...
> > > > > >> For additional commands, e-mail: dev-help@...
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@...
> > > > > > For additional commands, e-mail: dev-help@...
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@...
> > > > > For additional commands, e-mail: dev-help@...
> > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@...
> > > For additional commands, e-mail: dev-help@...
> > >
> > >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...