Hi John!
I'll try to get through it while on the train to $dayjob. Maybe we can dump
this into a Wiki page as 'under construction'?
txs and LieGrue,
strub
--- On Tue, 7/19/11, John Casey wrote:
> From: John Casey
> Subject: Re: [DISCUSS] Repository routing for Maven 3
> To: "Maven Developers
The maven installation instructions [1] explicitly mention the M2_HOME
variable (and not MAVEN_HOME), is this obsolete?
-Lukas
[1] http://maven.apache.org/download.html#Installation
On 07/19/2011 08:26 AM, Stephen Connolly wrote:
I run m2 and m3 on the same machine at the same time (but fr
I run m2 and m3 on the same machine at the same time (but from different
windows)... no issues at all for me.
http://javaadventure.blogspot.com/2011/03/my-magic-maven-and-ant-version.html
just don't use M2_HOME at all, use MAVEN_HOME both versions pick it up quite
successfully the M2_HOME was onl
Doing this stops maven 2 and maven 3 being able to run on the same machine.
It also makes no sense.
Cheers,
Peter
On Tue, Jul 19, 2011 at 12:41 PM, John Casey wrote:
> This has been a long time coming, and I apologize for the delay. I've been
> trying to clear enough time to work on some last touches to the
> implementation before writing this, to make sure the description agrees with
> the code.
>
> The code
heh, hit send to fast...
On 7/18/11 11:11 PM, John Casey wrote:
This has been a long time coming, and I apologize for the delay. I've
been trying to clear enough time to work on some last touches to the
implementation before writing this, to make sure the description agrees
with the code.
The c
This has been a long time coming, and I apologize for the delay. I've
been trying to clear enough time to work on some last touches to the
implementation before writing this, to make sure the description agrees
with the code.
The code for this discussion is in the mirror-group-routing branch o
On Jul 17, 2011, at 2:08 PM, Mark Struberg wrote:
> Hi Jason!
>
> Eclipse doesn't have problems with consuming ALv2 dependencies because ALv2
> explicitly allows sublicensing - but EPL doesn't!
> So this is an unidirectional way and exactly the reason why we imo cannot do
> this.
>
The EPL
On 7/18/11 5:23 PM, Hervé BOUTEMY wrote:
I worked on Aether to extract Maven specific parts (into maven-aether-
provider): AFAIK, we are completely free to change anything in the formats
used by Maven, either for POM or repositories.
About licensing, I don't have any concern about EPL at Eclip
On 7/17/11 12:08 PM, Benson Margulies wrote:
I think you are going to have to. Mark isn't the only one who has expressed the
sentiment. Some of the discussions I've seen on changing the relationship Maven
has with repository managers would surely require changes at the Aether layer.
I don'
I worked on Aether to extract Maven specific parts (into maven-aether-
provider): AFAIK, we are completely free to change anything in the formats
used by Maven, either for POM or repositories.
About licensing, I don't have any concern about EPL at Eclipse. The initial
announced intend was to mov
Sure.
On Mon, Jul 18, 2011 at 9:18 AM, Lukas Theussl wrote:
>
> an alternative is to give it maven-plugins as parent, but leave it inside
> jxr, (like scm is doing). WDYT?
>
> -Lukas
>
>
> On 07/18/2011 02:50 PM, Benson Margulies wrote:
>>
>> There's a lot of common stuff in the parent of the plu
an alternative is to give it maven-plugins as parent, but leave it
inside jxr, (like scm is doing). WDYT?
-Lukas
On 07/18/2011 02:50 PM, Benson Margulies wrote:
There's a lot of common stuff in the parent of the plugins:
announcements, changes, site config. Without mixins :-) we can't take
I'm writing a plugin that is executed for each module in a multi-module
build. I want to inject the same instance of a custom class into each mojo
invocation so that I can share the resource. How is this done? I create the
custom class and tried injecting it into my mojo class with the following
an
There's a lot of common stuff in the parent of the plugins:
announcements, changes, site config. Without mixins :-) we can't take
advantage of that. In short, I claim that the maven-jxr-plugin has
more in common with the rest of the plugins than it has with jxr. It's
only connection to JXR is one
1.12 is EPL only :
https://github.com/sonatype/sonatype-aether/blob/aether-1.12/README.md
On Mon, Jul 18, 2011 at 12:45 PM, Mark Derricutt wrote:
> Just reading this thread and was surprised as I wasn't aware Aether had
> gone EPL only.
>
> I was about to start a thread around getting a Maven 3.
Just reading this thread and was surprised as I wasn't aware Aether had
gone EPL only.
I was about to start a thread around getting a Maven 3.0.4 release
pushed out using Aether 1.12 which solves a, IMHO -MAJOR- bug in Maven
that prevents artifacts from being resolved properly when they come
I do and I can't. The PMC chair (who's that, at the moment?) should
have karma to fix, if not I can ask Infra for help.
On Mon, Jul 18, 2011 at 4:23 AM, Mark Struberg wrote:
> humm, it tells me that there are no restrictions setup for that very page. So
> once you have an account you should imo
humm, it tells me that there are no restrictions setup for that very page. So
once you have an account you should imo be able to edit that page.
LieGrue,
strub
--- On Mon, 7/18/11, Arnaud Héritier wrote:
> From: Arnaud Héritier
> Subject: Re: the pom compatibility threads
> To: "Maven Develop
I think it is common usus in maven land to keep plugins inside their
respective projects (see eg maven-archetype-plugin,
maven-enforcer-plugin, maven-scm-plugin, maven-surefire-plugin,...), the
main advantage being that they are released together and kept in sync
and up-to date with the main
On Tue, 12 Jul 2011 13:55:31 +0200
Lukas Theussl wrote:
>
>
> Tony Chemit wrote:
> > On Thu, 7 Jul 2011 21:22:43 +0200
> > Hervé BOUTEMY wrote:
> >
> >> I forgot we had this great Jenkins instance with lots of OSes and
> >> configuration combinations, and improved ITs to cover a lot of
> >> ca
FYI: Dennis has had similar problems at the last release:
http://maven.40175.n5.nabble.com/VOTE-Release-Maven-JXR-version-2-2-td216534.html
but I'd have guessed that this was fixed since then.
There is still something else wrong with the cobertura report: the main
index page
http://maven.ap
22 matches
Mail list logo
