Olivier Lamy wrote:
> 2013/4/19 Brett Porter :
[snip]
>> - we're used 'retired' instead of 'archived' in the past. Though I'm not
>> sure if we need to do that for SVN, particularly since it breaks tags. We
>> could just put a big warning in the directory?
> agree.
... or simple move the trunks
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 on how to use p-site-p 3.x + maven-
report-exec 1.1 like http://svn.apache.org/r1467751
- maven-dependency-tree 2.1-SNAPSHOT makes dependency:tree, shade an
2013/4/19 Brett Porter :
>
> On 19/04/2013, at 10:56 AM, Olivier Lamy wrote:
>
>> 2013/4/19 Brett Porter :
>>> I'd just make it "no longer supported".
>> done.
>>>
>>> A couple of other things:
>>> - page title is still Tomcat instead of Maven
>> fixed.
>>> - we're used 'retired' instead of 'archi
On 19/04/2013, at 10:56 AM, Olivier Lamy wrote:
> 2013/4/19 Brett Porter :
>> I'd just make it "no longer supported".
> done.
>>
>> A couple of other things:
>> - page title is still Tomcat instead of Maven
> fixed.
>> - we're used 'retired' instead of 'archived' in the past. Though I'm not
>>
2013/4/19 Brett Porter :
> I'd just make it "no longer supported".
done.
>
> A couple of other things:
> - page title is still Tomcat instead of Maven
fixed.
> - we're used 'retired' instead of 'archived' in the past. Though I'm not sure
> if we need to do that for SVN, particularly since it break
I'd just make it "no longer supported".
A couple of other things:
- page title is still Tomcat instead of Maven
- we're used 'retired' instead of 'archived' in the past. Though I'm not sure
if we need to do that for SVN, particularly since it breaks tags. We could just
put a big warning in the d
On 19/04/2013, at 4:29 AM, Anders Hammar 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 to far?
This
On 19 April 2013 03:56, Anders Hammar 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 would be hel
+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 onl
Great!
A point of detail: " is no longer officially supported"
Though quite similar, shouldn't it be more "is officially no longer
supported" instead?
As I'm not an english native speaker, I'll let others choose anyway.
My 2 cents.
Cheers
2013/4/18 Lennart Jörelid
> Uhm ... I presume you mea
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 lit
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 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.
/Anders
>
> Robert
>
> Op Thu, 18 Apr 2013 18:41:36 +0200 schreef Manfred Moser <
> manf...@simpligility.com>:
>
>
> Yo
+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
:
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 th
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
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 whe
+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 a
+1
Vincent
2013/4/18 Olivier Lamy
> sounds good idea.
> +1
>
> 2013/4/18 Anders Hammar :
> > 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 problem
Uhm ... I presume you mean
http://maven.apache.org/maven-1.x-eol.html
instead, Olivier?
2013/4/18 Stephen Connolly
> seriously, the url is tomcat-1.x-eol
>
>
> On 18 April 2013 12:15, Olivier Lamy wrote:
>
> > draft available here: http://maven.apache.org/tomcat-1.x-eol.html
> >
> > --
> >
gloups
fixed http://maven.apache.org/maven-1.x-eol.html
2013/4/18 Stephen Connolly :
> seriously, the url is tomcat-1.x-eol
>
>
> On 18 April 2013 12:15, Olivier Lamy wrote:
>
>> draft available here: http://maven.apache.org/tomcat-1.x-eol.html
>>
>> --
>> Olivier
>>
>> 2013/4/8 Hervé BOUTEMY :
>
seriously, the url is tomcat-1.x-eol
On 18 April 2013 12:15, Olivier Lamy wrote:
> draft available here: http://maven.apache.org/tomcat-1.x-eol.html
>
> --
> Olivier
>
> 2013/4/8 Hervé BOUTEMY :
> > for the moment, I'm on releases around Maven 3.1-alpha-1, but after
> that, if
> > nobody else w
draft available here: http://maven.apache.org/tomcat-1.x-eol.html
--
Olivier
2013/4/8 Hervé BOUTEMY :
> for the moment, I'm on releases around Maven 3.1-alpha-1, but after that, if
> nobody else wants to do it, I can
>
> Regards,
>
> Hervé
>
> Le dimanche 7 avril 2013 19:58:28 Olivier Lamy a écri
sounds good idea.
+1
2013/4/18 Anders Hammar :
> 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 restric
+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
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
25 matches
Mail list logo
