What I can add: is that when I was developing archetypes a few years back, the
archetypes I developed did appear in that file. (my memory may be wrong), but I
do not ever remember adding them manually to the file.
Ate there hooks in install/deploy or the archetype plugin to do that?
Just a stab
Le vendredi 19 avril 2013 15:17:44 Stuart McCulloch a écrit :
> > The other change which breaks tycho is aether moved to the org.eclipse
> > package namespace. Looks like for aether users it's a simple "organize
> > imports"; no API changes other than package rename, right? As there seems
> > to be
On 19 Apr 2013, at 14:49, Sievers, Jan wrote:
> Hi,
>
> I tried adapting tycho to maven 3.1.0-alpha-1, see [1].
>
> One thing I noticed is that maven now brings asm-3.3.1 as part of its core
> classloader.
> This breaks a build plugin in tycho (binary mismach errors at runtime) which
> happens
Hi,
I tried adapting tycho to maven 3.1.0-alpha-1, see [1].
One thing I noticed is that maven now brings asm-3.3.1 as part of its core
classloader.
This breaks a build plugin in tycho (binary mismach errors at runtime) which
happens to use asm-4.0.
Am I right that shipping asm with maven core m
ARCHETYPE-433 filed to track this.
/Anders
On Fri, Apr 19, 2013 at 12:25 PM, Hervé BOUTEMY wrote:
> I did some cleanup a few years ago when stabilizing the plugin, and
> experience
> showed that there is dead code that require investigation to really see if
> it's dead or not. I missed this one
I did some cleanup a few years ago when stabilizing the plugin, and experience
showed that there is dead code that require investigation to really see if
it's dead or not. I missed this one, but there are AFAIK sufficient unit and
integration tests to remove and check if it breaks something (tha
Ah, it was removed in favour of -Darchetype.properties=
http://jira.codehaus.org/browse/ARCHETYPE-112
http://svn.apache.org/viewvc?view=revision&revision=635711
So it looks like the local archetype registry file is no longer relevant.
On 19 Apr 2013, at 10:04, Anders Hammar wrote
Right, and I've traced it to ArchetypeRegistryManager. The problem is that
I can't see that it is ever used in the code, at least not for the registry
stuff.
/Anders
On Fri, Apr 19, 2013 at 10:42 AM, Stuart McCulloch wrote:
>
> http://maven.apache.org/archetype/archetype-models/archetype-regist
http://maven.apache.org/archetype/archetype-models/archetype-registry/archetype-registry.html
AFAICT it's related to which files get filtered when creating a project from
the archetype
On 19 Apr 2013, at 08:24, Anders Hammar wrote:
> Does anyone know what a archetype registry file is? It's poss
Not sure, but I've just logged
https://bugs.eclipse.org/bugs/show_bug.cgi?id=406056 in the Tycho project so
it's at least tracked.
On 19 Apr 2013, at 07:53, Anders Hammar wrote:
> Does anyone (Igor?) know if there is work going on to make Tycho work with
> this?
>
> /Anders
>
>
> On Fri, Apr
Does anyone know what a archetype registry file is? It's possible to
specify this for the create-from-project goal of the archetype plugin and
the default location is "${user.home}/.m2/archetype.xml". Can't see it's
being used anywhere though...
/Anders
Does anyone (Igor?) know if there is work going on to make Tycho work with
this?
/Anders
On Fri, Apr 19, 2013 at 8:16 AM, Hervé BOUTEMY wrote:
> back to the vote
> +1
>
> - maven-report-exec 1.1 makes m-site-p work with this release: no need to
> wait
> for m-site-p 3.3, we can add instructions
12 matches
Mail list logo
