Github user mfriedenhagen commented on the pull request:
https://github.com/apache/maven/pull/31#issuecomment-71979108
@ananich: #35 should take care oft this and even tackles the other start
scripts. Since I think Mavericks Mountain Lion, a JDK is not installed by
default, so the fir
Seems that entire surefire.forkNumber feature does not work on MVN 2.2.1
since for working directory expansion variables that are not yet defined
during initial plug-in execution are set to 'null' value. Later on both
baseDir and current working directory will be invalid, other parts of the
plug-in
+1
Regards,
Hervé
Le samedi 24 janvier 2015 23:25:37 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 34 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=194
> 20
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=proj
I reopened MCOMPILER-120. The story turns out to be this:
true
__suppresses__ printing the warning(s) that cause the compilation to
fail. That flag seems to be entirely read by plexus compiler, so I
guess that's my next place to visit. Anyone care to offer hints?
Hello,
Ping? The mails still nag me. Maybe it is enough to clean the workspace
for this job? Who should be responsible, so I can contact them directly?
Gruss
Bernd
Am Tue, 27 Jan 2015 21:46:12 +0100
schrieb Bernd Eckenfels :
> Hello,
>
> the core-it-maven-3-win are failing because of some get
I use a similar approach to Dan's. I just have
~/lib/apache-mavem-VERSION and symlink the mvn shell script to
~/bin/mvnVERSION_WITHOUT_DOTS.
Works flawlessly.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bit
Hi Igor,
That confirms the need to deprecate M2_HOME, I will remove it from
installation doc first. Will need to talk to Sonatype to remove it from its
book
Thanks
-Dan
On Wed, Jan 28, 2015 at 11:58 AM, Igor Fedorenko
wrote:
> I see. Yes, this would be a problem. And I think there is already
I see. Yes, this would be a problem. And I think there is already
similar incompatibility between maven 2.x and 3.x scripts (launcher
class name changed in 3.x). Personally, I never use M2_HOME to switch
between maven versions, so I wouldn't mind if it was removed completely.
If we want M2_HOME to
Hi,
here is missing a binding VOTE ?
Thanks.
On 1/27/15 9:01 PM, Karl Heinz Marbaise wrote:
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
+1
I think you need to deprecate something like that and not just yank it, but
removing the doco is a good first step. I have M2_HOME set even through I
don't technically need it but that's how I switch versions of Maven. I have
M2_HOME set, it's a symlink, and i just flip the symlink to chang
So I guess the consensus is to remove M2_HOME from installation
instructions and doc the specific usage of M2_HOME at FAQ?
Thanks
-D
On Wed, Jan 28, 2015 at 9:02 AM, Baptiste Mathus wrote:
> @Robert yup my bad for being somehow unclear.
> The -1 was answering to the fact that M2_HOME may be us
@Robert yup my bad for being somehow unclear.
The -1 was answering to the fact that M2_HOME may be useful in some cases.
So I'm indeed +1 for removing it from the docs.
Cheers
Le 27 janv. 2015 19:14, "Robert Scholte" a écrit :
> @Baptiste, so I guess your vote is actually +1 to remove it from
>
Yes, will do that shortly. I would like to aggregate fixes for unit and
integration test in one pull request, the link was only to show the
progress.
NW
On Wed, Jan 28, 2015 at 8:51 AM, Andreas Gudian
wrote:
> Thanks, Norbert!
>
> Could you also create a new Pull-Request for it? Then I can fetc
13 matches
Mail list logo
