[archetypes] future features

[Raphaël Piéroni <ra...@gmail.com>]

Hi Folks,

Here i come to talk a little about the next features of the archetype plugin.


First I would like to have some samples updated to the new archetype
way of doing. For this step, i will need some sample projects to start
from. This is an unshamed ask for pepople to provide some simple
project :-)
Here is the list of projects i will add for the next release:
- quickstart
- mojo
- webapp
- jee

quickstart will be a mono module hello world library.
mojo will provide a mono module hello wolrd goal.
webapp will be a mono module hello world servlet.
jee will be a multi module complete jee5 stack. with a library, an
ejb, a servlet. Can someone give me this kind of project based on
glassfish v3?
I have the ability to create the 3 first samples ;-)

I also plan to give some partial archetypes samples:
- site
- jnlp
- izpack

site will add a simple site on an existing maven project.
jnlp will add the usage of the jnlp plugin (hoping it exists) on an
existing maven project. Can anyone provide me a simple project for
this ?
izpack will add the usage of the izpack installer on top of a maven project.
I have the ability to create site and izpack, but dunno anything on jnlp.

Please provide me any advice on the way to achieve this...


Second, I would like to have a programmatic way to call a maven goal
on another project from inside a goal run from a project. For example,
calling the deploy phase on a newly created archetype at the end of
create-from-project.
Of course, such a deploy should have to find the deployment
information outside of the newly created archetype.
Can anyone tell me where the release plugin works in calling the spawn
maven build on the checkouted project.


Thanks in advance for any advice/help.

Regards,

Raphaël

Re: [archetypes] future features

[Benjamin Bentmann <be...@udo.edu>]

Raphaël Piéroni wrote:

> Second, I would like to have a programmatic way to call a maven goal
> on another project from inside a goal run from a project. [...]
> Can anyone tell me where the release plugin works in calling the spawn
> maven build on the checkouted project.

There is a shared component called maven-invoker [0] that should handle 
this task. It's the basis for the InvokerMavenExecutor in the 
maven-release-manager, the SimpleInvoker in the Maven Reactor Plugin and 
of course the InvokerMojo of the Maven Invoker Plugin.


Benjamin


[0] http://maven.apache.org/shared/maven-invoker/

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

Re: [archetypes] future features

[Raphaël Piéroni <ra...@gmail.com>]

If you think so, i'll agree.
To be honest, i don't have any preference.

Raphaël

2008/10/16 Brett Porter <br...@apache.org>:
> Actually, perhaps the archetypes should be separate now, like the plugins?
> So /archetypes/trunk.
>
> Cheers,
> Brett
>
> On 16/10/2008, at 5:24 PM, Raphaël Piéroni wrote:
>
>> 2008/10/15 Brett Porter <br...@apache.org>:
>>>
>>> On 13/10/2008, at 2:04 AM, Raphaël Piéroni wrote:
>>>
>>>> Hi Folks,
>>>>
>>>> Here i come to talk a little about the next features of the archetype
>>>> plugin.
>>>>
>>>>
>>>> First I would like to have some samples updated to the new archetype
>>>> way of doing. For this step, i will need some sample projects to start
>>>> from. This is an unshamed ask for pepople to provide some simple
>>>> project :-)
>>>> Here is the list of projects i will add for the next release:
>>>> - quickstart
>>>> - mojo
>>>> - webapp
>>>> - jee
>>>
>>> Updating all the existing ones (or deleting them if they aren't really
>>> that
>>> relevant) would be good. Which begs the question - what happened to them?
>>
>> They are in the archetype-1.x branch
>>
>>> I
>>> can't find them on trunk any more... I think even in the old format they
>>> are
>>> still valid.
>>>
>>> I saw you started to add them under "archetype-samples". I wouldn't say
>>> these are samples - they are just "archetypes" :)
>>
>> I needed a name and all the modules started with archetype.
>> Please feel free to propose a better name.
>>
>>>
>>> - Brett
>>>
>>> --
>>> Brett Porter
>>> brett@apache.org
>>> http://blogs.exist.com/bporter/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: [archetypes] future features

[Brett Porter <br...@apache.org>]

Actually, perhaps the archetypes should be separate now, like the  
plugins? So /archetypes/trunk.

Cheers,
Brett

On 16/10/2008, at 5:24 PM, Raphaël Piéroni wrote:

> 2008/10/15 Brett Porter <br...@apache.org>:
>>
>> On 13/10/2008, at 2:04 AM, Raphaël Piéroni wrote:
>>
>>> Hi Folks,
>>>
>>> Here i come to talk a little about the next features of the  
>>> archetype
>>> plugin.
>>>
>>>
>>> First I would like to have some samples updated to the new archetype
>>> way of doing. For this step, i will need some sample projects to  
>>> start
>>> from. This is an unshamed ask for pepople to provide some simple
>>> project :-)
>>> Here is the list of projects i will add for the next release:
>>> - quickstart
>>> - mojo
>>> - webapp
>>> - jee
>>
>> Updating all the existing ones (or deleting them if they aren't  
>> really that
>> relevant) would be good. Which begs the question - what happened to  
>> them?
>
> They are in the archetype-1.x branch
>
>> I
>> can't find them on trunk any more... I think even in the old format  
>> they are
>> still valid.
>>
>> I saw you started to add them under "archetype-samples". I wouldn't  
>> say
>> these are samples - they are just "archetypes" :)
>
> I needed a name and all the modules started with archetype.
> Please feel free to propose a better name.
>
>>
>> - Brett
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://blogs.exist.com/bporter/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


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

Re: [archetypes] future features

[Raphaël Piéroni <ra...@gmail.com>]

2008/10/15 Brett Porter <br...@apache.org>:
>
> On 13/10/2008, at 2:04 AM, Raphaël Piéroni wrote:
>
>> Hi Folks,
>>
>> Here i come to talk a little about the next features of the archetype
>> plugin.
>>
>>
>> First I would like to have some samples updated to the new archetype
>> way of doing. For this step, i will need some sample projects to start
>> from. This is an unshamed ask for pepople to provide some simple
>> project :-)
>> Here is the list of projects i will add for the next release:
>> - quickstart
>> - mojo
>> - webapp
>> - jee
>
> Updating all the existing ones (or deleting them if they aren't really that
> relevant) would be good. Which begs the question - what happened to them?

They are in the archetype-1.x branch

> I
> can't find them on trunk any more... I think even in the old format they are
> still valid.
>
> I saw you started to add them under "archetype-samples". I wouldn't say
> these are samples - they are just "archetypes" :)

I needed a name and all the modules started with archetype.
Please feel free to propose a better name.

>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: [archetypes] future features

[Brett Porter <br...@apache.org>]

On 13/10/2008, at 2:04 AM, Raphaël Piéroni wrote:

> Hi Folks,
>
> Here i come to talk a little about the next features of the  
> archetype plugin.
>
>
> First I would like to have some samples updated to the new archetype
> way of doing. For this step, i will need some sample projects to start
> from. This is an unshamed ask for pepople to provide some simple
> project :-)
> Here is the list of projects i will add for the next release:
> - quickstart
> - mojo
> - webapp
> - jee

Updating all the existing ones (or deleting them if they aren't really  
that relevant) would be good. Which begs the question - what happened  
to them? I can't find them on trunk any more... I think even in the  
old format they are still valid.

I saw you started to add them under "archetype-samples". I wouldn't  
say these are samples - they are just "archetypes" :)

- Brett

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


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

Re: [archetypes] future features

[Raphaël Piéroni <ra...@gmail.com>]

Hello Eugene,

About the upgrade of the dependencies (not only velocity):
i started to upgrade each dependency to newer versions,
wherever this didn't break the build.
But don't worry, i plan to replace velocity with groovy
templates ;-)

About Jdom vs Dom4j, i don't remember exactly, maybe i use
two libraries that each call one. About standadization, If
anyone is interested to provide a patch on the whole archetype
sources...

Regards,

Raphaël


2008/10/13 Eugene Kuleshov <eu...@md.pp.ru>:
>
> Raphaël,
>
>  May I ask what was the reason to update velocity version used by
> archetype-common from 1.4 to 1.5? Is there some known issues or the only
> reason is to use the latest version? Velocity 1.5 is bigger and it have more
> dependencies. We will have to submit separate IP review for each 3rd party
> library required for Maven integration for Eclipse and it would be great to
> minimize those dependencies.
>
>  I also wonder why archetype-common need both jdom and dom4j libraries? It
> is really odd to have two different xml framework. Generally I think it
> would be a great idea to standardize on xml framework across all Maven
> projects/plugins, at least those hosted at Apache and perhaps Codehaus Mojo
> project
>
>  What do you think?
>
>  Eugene
>
>
>
> Raphaël wrote:
>>
>> Here i come to talk a little about the next features of the archetype
>> plugin.
>>
>> First I would like to have some samples updated to the new archetype
>> way of doing. For this step, i will need some sample projects to start
>> from. This is an unshamed ask for pepople to provide some simple
>> project :-)
>> Here is the list of projects i will add for the next release:
>> - quickstart
>> - mojo
>> - webapp
>> - jee
>>
>> quickstart will be a mono module hello world library.
>> mojo will provide a mono module hello wolrd goal.
>> webapp will be a mono module hello world servlet.
>> jee will be a multi module complete jee5 stack. with a library, an
>> ejb, a servlet. Can someone give me this kind of project based on
>> glassfish v3?
>> I have the ability to create the 3 first samples ;-)
>>
>> I also plan to give some partial archetypes samples:
>> - site
>> - jnlp
>> - izpack
>>
>> site will add a simple site on an existing maven project.
>> jnlp will add the usage of the jnlp plugin (hoping it exists) on an
>> existing maven project. Can anyone provide me a simple project for
>> this ?
>> izpack will add the usage of the izpack installer on top of a maven
>> project.
>> I have the ability to create site and izpack, but dunno anything on jnlp.
>>
>> Please provide me any advice on the way to achieve this...
>>
>>
>> Second, I would like to have a programmatic way to call a maven goal
>> on another project from inside a goal run from a project. For example,
>> calling the deploy phase on a newly created archetype at the end of
>> create-from-project.
>> Of course, such a deploy should have to find the deployment
>> information outside of the newly created archetype.
>> Can anyone tell me where the release plugin works in calling the spawn
>> maven build on the checkouted project.
>>
>> Thanks in advance for any advice/help.
>>
>> Regards,
>>
>> Raphaël
>>
>
> --
> View this message in context: http://www.nabble.com/-archetypes--future-features-tp19942462p19948184.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: [archetypes] future features

[Eugene Kuleshov <eu...@md.pp.ru>]

Raphaël,

  May I ask what was the reason to update velocity version used by
archetype-common from 1.4 to 1.5? Is there some known issues or the only
reason is to use the latest version? Velocity 1.5 is bigger and it have more
dependencies. We will have to submit separate IP review for each 3rd party
library required for Maven integration for Eclipse and it would be great to
minimize those dependencies.

  I also wonder why archetype-common need both jdom and dom4j libraries? It
is really odd to have two different xml framework. Generally I think it
would be a great idea to standardize on xml framework across all Maven
projects/plugins, at least those hosted at Apache and perhaps Codehaus Mojo
project

  What do you think?

  Eugene



Raphaël wrote:
> 
> Here i come to talk a little about the next features of the archetype
> plugin.
> 
> First I would like to have some samples updated to the new archetype
> way of doing. For this step, i will need some sample projects to start
> from. This is an unshamed ask for pepople to provide some simple
> project :-)
> Here is the list of projects i will add for the next release:
> - quickstart
> - mojo
> - webapp
> - jee
> 
> quickstart will be a mono module hello world library.
> mojo will provide a mono module hello wolrd goal.
> webapp will be a mono module hello world servlet.
> jee will be a multi module complete jee5 stack. with a library, an
> ejb, a servlet. Can someone give me this kind of project based on
> glassfish v3?
> I have the ability to create the 3 first samples ;-)
> 
> I also plan to give some partial archetypes samples:
> - site
> - jnlp
> - izpack
> 
> site will add a simple site on an existing maven project.
> jnlp will add the usage of the jnlp plugin (hoping it exists) on an
> existing maven project. Can anyone provide me a simple project for
> this ?
> izpack will add the usage of the izpack installer on top of a maven
> project.
> I have the ability to create site and izpack, but dunno anything on jnlp.
> 
> Please provide me any advice on the way to achieve this...
> 
> 
> Second, I would like to have a programmatic way to call a maven goal
> on another project from inside a goal run from a project. For example,
> calling the deploy phase on a newly created archetype at the end of
> create-from-project.
> Of course, such a deploy should have to find the deployment
> information outside of the newly created archetype.
> Can anyone tell me where the release plugin works in calling the spawn
> maven build on the checkouted project.
> 
> Thanks in advance for any advice/help.
> 
> Regards,
> 
> Raphaël
> 

-- 
View this message in context: http://www.nabble.com/-archetypes--future-features-tp19942462p19948184.html
Sent from the Maven Developers mailing list archive at Nabble.com.


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