GitHub user soiff opened a pull request:
https://github.com/apache/maven-scm/pull/52
add --chache option for git rm
For newer git release, command `git rm` will remove files definitely and
it's not possible to add it again by command `git add`. In this scenario,
option `--cache` sh
On Sat, 10 Sep 2016 17:15:49 +0200, Karl Heinz Marbaise
wrote:
Hi Robert,
On 10/09/16 16:54, Robert Scholte wrote:
Hi Karl Heinz,
when looking at Aether it is not aware of a MavenProject. Instead it is
transferring Files.
Yes I know..
My idea was to have a thin layer on top op (Sonatyp
Hi Robert,
On 10/09/16 16:54, Robert Scholte wrote:
Hi Karl Heinz,
when looking at Aether it is not aware of a MavenProject. Instead it is
transferring Files.
Yes I know..
My idea was to have a thin layer on top op (Sonatype/Eclipse) Aether and
to avoid too much Maven Core mixin.
Yes I ha
Hi Karl Heinz,
when looking at Aether it is not aware of a MavenProject. Instead it is
transferring Files.
My idea was to have a thin layer on top op (Sonatype/Eclipse) Aether and
to avoid too much Maven Core mixin.
But it did cross my mind to use the MavenProject as the entity instead of
F
Hi,
so after using the maven-artifact-transfer a time I have realized there
seemed to be some lack of funcionality from my point of view...
My extension[1] will deploy all projects at the end of the session and I
had to write down a lot of code to deploy a project...the same meaning
for inst
GitHub user britter opened a pull request:
https://github.com/apache/maven-surefire/pull/120
Add convinient method to check for the currently used Java Version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/britter/maven-surefir
Hi,
I'm currently a bit stuck with the JUnit 5 integration, because I don't
really know where it should be going. At first I thought we should just
merge the Integration tests I'm about to write directly to master. But
maybe that's not the best idea. But I don't want to implement the whole
thing i
Hello Tibor,
that file does not seem to work with IntelliJ 2016.2 :-( I think I will
have to configure the code style myself.
Benedikt
Tibor Digana schrieb am Fr., 9. Sep. 2016 um
15:00 Uhr:
> Sorry I did not get notice this email. You need to configure your IDE for
> you pending PR in GitHub,
GitHub user britter opened a pull request:
https://github.com/apache/maven-surefire/pull/119
Make JUnit4VersionsIT acutally use the versions set by the test code
As discussed on the ML.
You can merge this pull request into a Git repository by running:
$ git pull https://github.
Le 10 sept. 2016 12:57, "Hervé BOUTEMY" a écrit :
>
> Le vendredi 9 septembre 2016 10:49:54 Tibor Digana a écrit :
> > @Herve What do you think about Romain's concept: --color-info=blue
> > --color-error=red --color-warning=yellow-bold
> > @Romain In MVN 3.4 you can override the colors via system
Le vendredi 9 septembre 2016 10:49:54 Tibor Digana a écrit :
> @Herve What do you think about Romain's concept: --color-info=blue
> --color-error=red --color-warning=yellow-bold
> @Romain In MVN 3.4 you can override the colors via system properties, e.g.
> -Dstyle.info=bold,blue
see
http://maven.a
Hi,
you know that failsafe is intended for integration tests which are
usually not parallelizable...
Apart from that maven-eclipse-plugin is retired and shouldn't be part of
your build any more...
Furthermore without an exmple which shows the behaviour it's hard to
guess what might be wron
Hi,
Using Maven 3.3.9, maven-eclipse-plugin 2.9, failsafe 2.19.1, surefire
2.19.1.
I'm using FailSafe parallel = method and threadCount ={5,10,50,100} to
execute a bunch of test classes with forkCount = {2,3,4,5}. The
integration-test phase is completing sometimes and getting stuck for long
the o
13 matches
Mail list logo
