@Anders,
I've just done a huge commit for MMOCKRM-10, so you could give it a try.
For the catalog, it expects a archetype-catalog.xml in the root of the
repository, just as the real world.
Robert
Op Sat, 20 Apr 2013 17:20:04 +0200 schreef Robert Scholte
rfscho...@apache.org:
@Anders,
Thanks Robert!
/Anders
On Wed, May 15, 2013 at 12:35 PM, Robert Scholte rfscho...@apache.orgwrote:
@Anders,
I've just done a huge commit for MMOCKRM-10, so you could give it a try.
For the catalog, it expects a archetype-catalog.xml in the root of the
repository, just as the real world.
On Sunday, 21 April 2013, Barrie Treloar wrote:
On 21 April 2013 00:50, Robert Scholte rfscho...@apache.orgjavascript:;
wrote:
@Barrie,
http://mojo.codehaus.org/mrm-maven-plugin/examples/invoker-tests.htmlshould
give you a good start.
I'll add something about supported files and how to
The archetype for Maven plugins has been enriched with an example of an IT.
That should give developers a start on how to use the maven-invoker-plugin.
There's probably more room for improving documentation on how to make a
kickstart when writing maven-plugins, but that would only be useful if
@Anders, I'm almost ready with MMOCKRM-10, but I'm hitting a chicken-egg
problem: we both need to write IT's with a snapshot version of MRM and
with the adjusted maven-archetype-plugin.
I'll try to cover most with unittests and let's see what we want to
release first.
@Barrie,
On 21 April 2013 00:50, Robert Scholte rfscho...@apache.org wrote:
@Barrie,
http://mojo.codehaus.org/mrm-maven-plugin/examples/invoker-tests.html should
give you a good start.
I'll add something about supported files and how to setup your mockrepo. Is
there something else you'd like to see?
Currently, maven-archetype-plugin ignores the configured Maven
infrastructure when fetching the archetype-catalog. That is, it is
hard-coded to get the catalog from central. This causes problems in
environments where Internet access is restricted and a MRM is used. Also,
in cases where Internet is
+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
sounds good idea.
+1
2013/4/18 Anders Hammar and...@hammar.net:
Currently, maven-archetype-plugin ignores the configured Maven
infrastructure when fetching the archetype-catalog. That is, it is
hard-coded to get the catalog from central. This causes problems in
environments where Internet
+1
Vincent
2013/4/18 Olivier Lamy ol...@apache.org
sounds good idea.
+1
2013/4/18 Anders Hammar and...@hammar.net:
Currently, maven-archetype-plugin ignores the configured Maven
infrastructure when fetching the archetype-catalog. That is, it is
hard-coded to get the catalog from
+1
On 4/18/13 3:22 AM, Anders Hammar wrote:
Currently, maven-archetype-plugin ignores the configured Maven
infrastructure when fetching the archetype-catalog. That is, it is
hard-coded to get the catalog from central. This causes problems in
environments where Internet access is restricted and
+1
Regards,
Hervé
Le jeudi 18 avril 2013 10:22:38 Anders Hammar a écrit :
Currently, maven-archetype-plugin ignores the configured Maven
infrastructure when fetching the archetype-catalog. That is, it is
hard-coded to get the catalog from central. This causes problems in
environments where
You would be earning a lot of brownie points I am sure! There are a bunch
of open questions around this and the perception that the archetype system
is pretty much dead on stackoverflow and other places. This could fix a
lot of those concerns..
manfred
Currently, maven-archetype-plugin ignores
+1
I can help with MMOCKRM-10 and its integration for the ITs, I've done it
several times.
Robert
Op Thu, 18 Apr 2013 18:41:36 +0200 schreef Manfred Moser
manf...@simpligility.com:
You would be earning a lot of brownie points I am sure! There are a bunch
of open questions around this
I can help with MMOCKRM-10 and its integration for the ITs, I've done it
several times.
That would be awesome. It's actually what has made me postpone this for a
while.
/Anders
Robert
Op Thu, 18 Apr 2013 18:41:36 +0200 schreef Manfred Moser
manf...@simpligility.com:
You would be
Heck, we might even go v3.0 with this change and remove a lot of garbage
that I've found in the code. And delete the create goal. :-)
Maybe even require Maven 3.0+ to simplify the code. Or maybe that's taking
this a little bit to far?
/Anders
On Thu, Apr 18, 2013 at 6:41 PM, Manfred Moser
Moving fast would certainly different... but very good imho!
manfred
Heck, we might even go v3.0 with this change and remove a lot of garbage
that I've found in the code. And delete the create goal. :-)
Maybe even require Maven 3.0+ to simplify the code. Or maybe that's taking
this a little
+1.
Though I'd personally be inclined to just go m3+ directly, I suppose this
would be a bit more progressive for users to release a last m2 compatible
version before going m3+.
That'd be the occasion to state clearly this is the last m2-compatible in
the release notes.
Sure, this strategy is
On 19 April 2013 03:56, Anders Hammar and...@hammar.net wrote:
I can help with MMOCKRM-10 and its integration for the ITs, I've done it
several times.
That would be awesome. It's actually what has made me postpone this for a
while.
If you could update any docs with this information that
On 19/04/2013, at 4:29 AM, Anders Hammar and...@hammar.net wrote:
Heck, we might even go v3.0 with this change and remove a lot of garbage
that I've found in the code. And delete the create goal. :-)
Maybe even require Maven 3.0+ to simplify the code. Or maybe that's taking
this a little bit
20 matches
Mail list logo
