Thanks, fixed, build passes in both maven 2 and 3.
Regards,
Stevo.
On Mon, Dec 7, 2009 at 2:36 PM, Benjamin Bentmann wrote:
> Stevo Slavić wrote:
>
> It seems 3.0-alpha-5 is not compatible with current 2.0-alpha-4 version of
>> maven-archetype-plugin - archetype:create-from-project mojo create
Stevo Slavić wrote:
It seems 3.0-alpha-5 is not compatible with current 2.0-alpha-4 version of
maven-archetype-plugin - archetype:create-from-project mojo creates
archetype project with packaging maven-archetype, but that packaging seems
not to be supported by / valid for 3.0-alpha-5
Try runni
this<https://issues.sonatype.org/browse/MNGECLIPSE-1920?focusedCommentId=107179&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_107179>Igor
Fedorenko's comment to a m2eclipse issue, showing error 3.0-alpha-5
prints when building projects with maven-arch
a bunch of archetypes so I will soon find out.
I apologise for not yet having an automatic test for it
Because the creator (at least before your commits)
creates the archetypes using the maven-archetype packaging
which was defined in this module.
Then the archetypes are installed against tha
before your commits)
> > creates the archetypes using the maven-archetype packaging
> > which was defined in this module.
> >
> > Then the archetypes are installed against that packaging.
> >
> > Raphaël
> >
> > 2007/9/20, [EMAIL PROTECTED] <[EMAIL
e, it pulls down the old
archetypeng-packaging which is why I didn't catch it. There is no
reference to the new "archetype-packaging" yet.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 20, 2007 7:07 AM
To: Maven Developers L
7:07 AM
To: Maven Developers List
Subject: Re: svn commit: r577620 -
/maven/sandbox/trunk/archetypeng/archetype-packaging/
On 20 Sep 07, at 2:34 AM 20 Sep 07, Raphaël Piéroni wrote:
> Hi
>
> I am not sure it is not used.
>
You should be sure :-)
Nothing in the tests exercised it, o
your commits)
creates the archetypes using the maven-archetype packaging
which was defined in this module.
Then the archetypes are installed against that packaging.
Raphaël
2007/9/20, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Author: jvanzyl
Date: Thu Sep 20 01:20:13 2007
New Revision: 577620
Hi
I am not sure it is not used.
Because the creator (at least before your commits)
creates the archetypes using the maven-archetype packaging
which was defined in this module.
Then the archetypes are installed against that packaging.
Raphaël
2007/9/20, [EMAIL PROTECTED] <[EMAIL PROTEC
ct metadata
- ask for the version found in the metadata (construct a list)
I would like to have a new maven-archetype packaging (currently working on)
Concerning the issue of packaging, metadata and archetype selection from
lists, i have some options:
- mimics the plugin metadatas (in groups) b
Hi,
That kind of metadata is not handled by packaging, but by the artifact manager.
What do you need this for?
If it's to automatically list all available archetypes, that would be great.
We should generalize that by having a special kind of metadata in special
groups,
like org/apache/mave
2007/5/13, Brett Porter <[EMAIL PROTECTED]>:
What will be contained in this metadata? For the plugins, it is to
link a plugin prefix to a plugin artifact ID - I don't see the
parallel concept in archetype.
For archetypes, the group metadata is used to prompt a list of archetypes in
a group fo
What will be contained in this metadata? For the plugins, it is to
link a plugin prefix to a plugin artifact ID - I don't see the
parallel concept in archetype.
Anyway, you can copy what plugin-plugin does: the plugin lifecycle
includes a goal in package for attaching the metadata, and it c
Hi
if i would create a new packaging for archetypes,
what is the way (i don't need doco link about lifecycle hook
of a mojo, i already know it ;) )
to have a specific metadata uploaded as long with the
artifact during the install and deploy phases.
My point is how to create metadata and how to
h
14 matches
Mail list logo
