Github user cbeust commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164237025
@Tibor17 Yes, @juherr is a committer.
---
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
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164238142
@cdeneux
@juherr
I am thinking about asking and introducing @juherr committer in Maven ASF.
---
If your project is set up for it, you can reply to
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164237916
@juherr I am running the build in command line.
This is the command I use `mvn -P run-its install`.
This means the build result should be same in your
Hi Olivier,
have you started the build from maven root folder (cause the gist looks
different (Or i'm mistaken something):
maven-core olamy$ mvn -DdistributionTargetFolder="$M2_HOME" clean
package -DskipTests..
?
Which Maven version do you use?
Kind regards
Karl Heinz
pom?
On Saturday 12 December 2015, Benson Margulies
wrote:
> Sometimes, we want to declare a dependency without changing a classpath.
>
> Project A builds an OSGi bundle and a Karaf feature (classifier
> 'feature', type 'xml').
>
> Project B wants to consume the feature.
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164237383
5.14.4 is not supposed to fail and excluding the bad dependency worked for
me.
I'll try again with an up2date maven. Which one are you using?
---
If your
I read the FM :-) and I found something similar mvn
-DdistributionTargetFolder="$M2_HOME" clean package -DskipTests
I run it once without failure then I got a long exception stack :
maven-core olamy$ mvn -DdistributionTargetFolder="$M2_HOME" clean package
-DskipTests
[WARNING] Error
The first time I heard about JDK9s Jigsaw having a classpath and a
modulepath, which can be used at the same time AND both containing jars, I
had a big "OH NO!". We can't change the pom, so the first thing that
came to my mind was indeed using the scope for this. But that'll have a
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164236954
I was about to push your commit and start the release Vote.
Please run the ITs. I found a problem in IT
Tests in error:
testNgListenerReporter[4:
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164236988
@juherr Are you a committer at TestNG project?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164238653
@juherr @cbeust
Yeasterday I made big refactoring on TestNG provider. This is old project
which started in Codehaus and the provider contained unused code,
Hi
I used to simply do a one line cli to simply replace a current local maven
with a fresh build from the trunk.
Just using "ant -DskipTests=true -Dmaven.home.exists.continue=true" and
voila a new maven version was installed locally from last sources.
What is the new simple one line option now?
Am 2015-12-11 um 22:01 schrieb Christian Schulte:
Am 12/11/15 um 20:18 schrieb Robert Scholte:
Hi Christian,
first of all: welcome!
about this commit: It took a while before I understood the term 'ssi'.
ssi is an abbreviation, not that clear and IMHO it suggest that this page
includes dynamic
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164262422
> committer in Maven ASF
I'm open :)
> Tests in error
I confirm it is working for me with maven 3.3.9 and 3.2.5.
```
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164274018
@juherr Please try to test with official Version Maven 3.0.5 which should
be used in Surefire project. I used 3.2.1. I will try with 3.0.5 as well and
let you
On Dec 13, 2015 3:25 AM, "Stephen Connolly"
wrote:
> pom?
>
1. The feature descriptor is xml
2. I believe that this still adds transitive dependencies to the dependency
graph.
>
> On Saturday 12 December 2015, Benson Margulies
>
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164299962
After deleting both repositories and using maven 3.3.9 still bad result in
On Sun, Dec 13, 2015 at 3:59 PM, Robert Scholte wrote:
> Op Sun, 13 Dec 2015 21:23:16 +0100 schreef Andreas Gudian
> :
>
>
>> 2015-12-13 12:05 GMT+01:00 Robert Scholte :
>>
>>> The first time I heard about JDK9s Jigsaw having a
On Sun, Dec 13, 2015 at 9:40 AM, Benson Margulies wrote:
> On Dec 13, 2015 3:25 AM, "Stephen Connolly"
> wrote:
>>
>> pom?
>
>
> 1. The feature descriptor is xml
>
> 2. I believe that this still adds transitive dependencies to the
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164288512
`com/beust/jcommander/ParameterException` comes from jcommander which is a
TestNG dependency. If it is missing, that means the dependency resolution is
falling.
Hi Kristian,
can you please give me push-access to the plexus-compiler repository?
I'm working on an old MCOMPILER issue and need to change stuff over there
as well...
Thanks,
Andreas
2015-02-09 18:13 GMT+01:00 Kristian Rosenvold :
> They are now all at
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164294388
I've just followed your process and it's working well for me with `maven
3.0.5` and `Oracle JDK 1.8.0_66` on `Linux Mint 17.2 Rafaela`.
I tried on 2 different
Hi,
Sorry for coming in late to the discussion...
Personally I would prefer to stay on Java 7 for a bit longer. Java 9
looks like its going to be delayed for 6 months:
http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-December/003149.html
As always the opinion of those who work on the code
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164301074
> Do you have this path?
Yes
> I use Java 7 which is maybe the only one difference.
Ok. But it is working well on my side with `openjdk
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164299087
I use Maven 3.3.9 like you use.
Do you have this path
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164302567
Yes.
I tried first by removing testng from local repo + full it-repo.
Then I tried by removing full local repo + full it-repo.
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164279434
I have reproduced the issue and the error is really true because the
`testng-5.14.4.jar` really does not contain the class
2015-12-13 19:04 GMT+01:00 Benson Margulies :
> On Sun, Dec 13, 2015 at 9:40 AM, Benson Margulies
> wrote:
> > On Dec 13, 2015 3:25 AM, "Stephen Connolly"
> > wrote:
> >>
> >> pom?
> >
> >
> > 1. The feature
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164301644
Did you delete both repositories?
1. Maven local repository
2. surefire-setup-integration-tests/target/it-repo
---
If your project is set up for it, you
Hi Hervé,
Apologies for the delayed reply.
Regarding Jenkins and SDKMAN, they really operate very differently.
Unfortunately, I currently have no plans to make SDKMAN more like Jenkins.
Jenkins is a CI server, and SDKMAN is a package manager.
SDKMAN has a client side tool (bash CLI) that calls
2015-12-13 12:05 GMT+01:00 Robert Scholte :
> The first time I heard about JDK9s Jigsaw having a classpath and a
> modulepath, which can be used at the same time AND both containing jars, I
> had a big "OH NO!". We can't change the pom, so the first thing that
> came to
Op Sun, 13 Dec 2015 21:23:16 +0100 schreef Andreas Gudian
:
2015-12-13 12:05 GMT+01:00 Robert Scholte :
The first time I heard about JDK9s Jigsaw having a classpath and a
modulepath, which can be used at the same time AND both containing
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621=12332973
There are still a couple of issues left in JIRA:
Adrien or Robert, when you have some time, can you please test my example
and confirm my findings?
Cheers,
Paul
On Thu, Dec 10, 2015 at 10:50 AM, Paul Benedict
wrote:
> Here is the POM:
>
> http://maven.apache.org/POM/4.0.0;
>
i agree with stephenc that major version change = API change.
>> the longer we put off updating the baseline JDK *in core* the worse the
pain will be in 2-3 years for us when developing and maintaining our plugins
We can always open a Vote but then some users may loose a fix been
important for
Hi
On 13 December 2015 at 23:11, Karl Heinz Marbaise wrote:
> Hi Olivier,
>
> have you started the build from maven root folder (cause the gist looks
> different (Or i'm mistaken something):
>
With "maven root folder" do you mean maven core sources? Yes definitely
because
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164317823
@juherr
How did you solve
https://github.com/apache/maven-surefire/pull/107#issuecomment-160169598 ?
It's the same problem with the exception I have
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164302659
@agudian
Hi Andreas,
We have here different test result. After I launched
`CheckTestNgListenerReporterIT` in your environment? You should make this
Hi Paul,
with your pom.xml I get 2.10 as expected, with both G:A:goal and
prefix:goal.
Tested with M3.0.5 and M3.1.1 and 3.3.3
Sorry, can't reproduce.
Robert
Op Thu, 10 Dec 2015 17:50:39 +0100 schreef Paul Benedict
:
Here is the POM:
When you specify type=pom you are depending on the pom which puts an
inter-project dependency (i.e. forces the reactor order) but does not put
on the classpath... at least from what I recall...
other than that you could create a custom packaging and say that the custom
packaging is not added to
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164324781
@juherr
Do you have this file on your file system?
`/Users/cbeust/java/testng/target/checkout/lib-supplied/guice-2.0.jar`
I guess you have it and
GitHub user akacme opened a pull request:
https://github.com/apache/maven/pull/73
[MNG-5947] dependencyManagement import section does not resolve
dependencies using "nearest" definition
dependencies using "nearest" definition
o DepenencyManagement model updated to contain
Github user akacme closed the pull request at:
https://github.com/apache/maven/pull/73
---
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
GitHub user akacme opened a pull request:
https://github.com/apache/maven/pull/74
[MNG-5947] dependencyManagement import section does not resolve
dependencies using "nearest" definition
o DepenencyManagement model updated to contain declared dependencies
and imported
Hi Marco,
I think there is a misunderstanding - no-one is proposing that you should
create another CI-Server (like Jenkins)…
All we are saying is, that the backend/server site of SDKMAN should have a
crawler component which does a daily check of a page like this:
45 matches
Mail list logo