IMO, M2_HOME is no longer a required env starting 2.2.1, and there for it
is used mainly for the exact use case that Manfred mentioned. I myself use
a set a wrapper scripts ( mvn221, mvn311, etc) since it is much easier to
remember.
I also got bitten a number of times where user had M2_HOME set,
-1 it's a problematic variable, removing it is a good idea IMO, and
changing mvn version is indeed just a matter of updating your path.
I've been hit many a time by an updated PATH pointing to a different mvn
version than the one referenced by M2_HOME, which ends with
NoClassDefFoundError or somet
Github user makigumo commented on the pull request:
https://github.com/apache/maven/pull/24#issuecomment-71620924
fixed in fbd6e53e838d3c77d689adeae19fa6de6ecc050f
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your p
Github user makigumo closed the pull request at:
https://github.com/apache/maven/pull/24
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
I know of two cases where it comes up.
1: some of our own ITs. Those aren't a reason for comprehensive doc.
2: an application I wrote for Aether :-)
On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus wrote:
> -1 it's a problematic variable, removing it is a good idea IMO, and
> changing mvn ver
Hi,
Anyone who has every tried, or is considering trying, developing a Maven
plugin, extension, or feature will want to have a look at our Eclipse Tools for
Maven Development[1]. It basically allows you to run and debug anything related
to Maven from within the Eclipse workspace without having
Hi,
here i my +1...
here we need at least two binding VOTE's ...
Kind regards
Karl Heinz Marbaise
On 1/24/15 11:25 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 34 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19420
There are still a couple of issues left
@Baptiste, so I guess your vote is actually +1 to remove it from
documentation, right?
M2_HOME is automatically set by the shell or batch script.
The M2_HOME variable is here used to easily switch between different Maven
distributions. But with this name this can indeed cause
NoClassDefFoun
Hi Benson,
What is your verdict?
Thanks
-D
On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies
wrote:
> I know of two cases where it comes up.
>
> 1: some of our own ITs. Those aren't a reason for comprehensive doc.
>
> 2: an application I wrote for Aether :-)
>
>
>
> On Tue, Jan 27, 2015 at 4
On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran wrote:
> Hi Benson,
>
> What is your verdict?
I vote for removing it from the publically facing doc. is there also a
thought of removing it from the code? I guess if someone makes sure
that all our many tests pass without it, fine with me.
I should expl
Hi Benson
By "many tests" are you refer to the incident at release plugin 2.5.1, or
maven-core IT
Thanks
-D
On Tue, Jan 27, 2015 at 10:28 AM, Benson Margulies
wrote:
> On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran wrote:
> > Hi Benson,
> >
> > What is your verdict?
>
> I vote for removing it f
On Tue, Jan 27, 2015 at 2:10 PM, Dan Tran wrote:
> Hi Benson
>
> By "many tests" are you refer to the incident at release plugin 2.5.1, or
> maven-core IT
I'm guessing that the M-R-P integration tests are not the only plugin
integration tests that care. I'm pretty sure I've run into this
before.
Hi,
The vote has passed with the following result:
+1 (binding): Jason van Zyl, Rober Scholte, Karl Heinz Marbaise
+1 (non binding): Anders Hammar
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
---
Strange I don't have a problem with maven-release build running with
-Prun-its
-D
On Tue, Jan 27, 2015 at 11:20 AM, Benson Margulies
wrote:
> On Tue, Jan 27, 2015 at 2:10 PM, Dan Tran wrote:
> > Hi Benson
> >
> > By "many tests" are you refer to the incident at release plugin 2.5.1,
> or
> >
Hi,
just a single binding VOTE...;-)
Kind regards
Karl Heinz Marbaise
On 1/27/15 6:54 PM, Karl Heinz Marbaise wrote:
Hi,
here i my +1...
here we need at least two binding VOTE's ...
Kind regards
Karl Heinz Marbaise
On 1/24/15 11:25 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 34 issues:
Hello,
the core-it-maven-3-win are failing because of some get setup problem
(it seems). The job sent a lot of failed mail messages. It looks like I
do get a copy because one of my patches was commited meanwhile.
Can somebody have a look?
Gruss
Bernd
--
Datum: Mon, 26 Jan 2015 23:27:07 + (U
Just see this change [1] at Maven core where the 'mvn' script get altered.
Not sure about the impact of this change when using M2_HOME to support
multiple is distributions.
-Dan
[1]
https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commitdiff;h=0a76e91b
On Tue, Jan 27, 2015 at 11:38 AM,
The Apache Maven team is pleased to announce the release of the
Apache Maven Dependecy Plugin, version 2.10
The dependency plugin provides the capability to manipulate artifacts. It can
copy and/or unpack artifacts from local or remote repositories to a specified
location.
http://maven.apache.or
You sure you linked the right commit? The commit you linked is from my
experimental branch and it does not change how mvn* scripts use M2_HOME
environment variable.
--
Regards,
Igor
On 2015-01-27 16:26, Dan Tran wrote:
Just see this change [1] at Maven core where the 'mvn' script get altered.
My bad, it is not obvious it is from an experimental branch. However, even
if this gets committed master, the configuration changes in that script may
impact other distribution using M2_HOME.
Sorry, I am a little side track here.
-D
On Tue, Jan 27, 2015 at 2:07 PM, Igor Fedorenko wrote:
> You
On 2015-01-27 17:35, Dan Tran wrote:
My bad, it is not obvious it is from an experimental branch. However, even
if this gets committed master, the configuration changes in that script may
impact other distribution using M2_HOME.
Can you explain how changes on that branch can impact other
di
If your changes are specific to 3.2.6, however If user has M2_HOME point to
an older version MAVEN, would that be a problem?
Thanks
-D
On Tue, Jan 27, 2015 at 3:01 PM, Igor Fedorenko wrote:
>
>
> On 2015-01-27 17:35, Dan Tran wrote:
>
>> My bad, it is not obvious it is from an experimental bra
I switch between versions all the time; this is useful.
Sent from my iPhone
On 27/01/2015, at 4:47 PM, "Manfred Moser" wrote:
> I would still suggest to make sure its documented somewhere. I find it
> incredibly useful to just change M2_HOME to simply switch Maven versions.
>
> manfred
>
>
Hi Tibor / Andreas,
I found a time to address problem with unit test, will take a look at
integration test tomorrow.
https://github.com/norbertwnuk/maven-surefire/commit/44b6ffaddc93c34c3e76abd4ea5fd3b8d837a130
NW
On Sun, Jan 25, 2015 at 1:32 AM, Tibor Digana
wrote:
> Hi Norbert,
> I have updaa
Link after pushing amended commit -
https://github.com/norbertwnuk/maven-surefire/commit/d6a8af593fc03e12ecf2dc8047669472f7ca263b
On Wed, Jan 28, 2015 at 3:10 AM, Norbert Wnuk wrote:
> Hi Tibor / Andreas,
> I found a time to address problem with unit test, will take a look at
> integration test
Thanks, Norbert!
Could you also create a new Pull-Request for it? Then I can fetch it more
easily :-)
Am Mittwoch, 28. Januar 2015 schrieb Norbert Wnuk :
> Link after pushing amended commit -
>
> https://github.com/norbertwnuk/maven-surefire/commit/d6a8af593fc03e12ecf2dc8047669472f7ca263b
>
> O
26 matches
Mail list logo
