Github user krmahadevan commented on the issue:
https://github.com/apache/maven-surefire/pull/166
ping @Tibor17 - This PR basically addresses only the *TestNG* portion of
the bug https://github.com/cbeust/testng/issues/1563
---
---
GitHub user krmahadevan opened a pull request:
https://github.com/apache/maven-surefire/pull/166
Support filtering of tests from Base Class (TestNG)
User has two test classes
1. An abstract base class called âBaseTestâ which
contains an @Test method called âtestMethodFr
I don't really understand these answers: a demo, please
Regards,
Hervé
Le dimanche 8 octobre 2017, 20:32:29 CEST Robert Scholte a écrit :
> On Sun, 08 Oct 2017 20:27:17 +0200, Stephen Connolly
>
> wrote:
> > On Sun 8 Oct 2017 at 18:28, Hervé BOUTEMY wrote:
> >> I don't get the technical detai
On Sun, 08 Oct 2017 20:27:17 +0200, Stephen Connolly
wrote:
On Sun 8 Oct 2017 at 18:28, Hervé BOUTEMY wrote:
I don't get the technical details
but IIUC, you're able to do a PoC with our available git repositories of
Jenkins job maintenance (easy job creation + easy Jenkinsfile
maintenanc
On Sun 8 Oct 2017 at 18:28, Hervé BOUTEMY wrote:
> I don't get the technical details
> but IIUC, you're able to do a PoC with our available git repositories of
> Jenkins job maintenance (easy job creation + easy Jenkinsfile maintenance),
Job created automatically once there is a git repo with
any git expert available to tell us if submodules are what we're looking for?
And will permit something like svn trunks [1], ie use each submodule to commit
independantly, while having easy full code clone or pull.
IIUC, we'll have to learn new git commands, since it's not as transparent as
svn
I don't get the technical details
but IIUC, you're able to do a PoC with our available git repositories of
Jenkins job maintenance (easy job creation + easy Jenkinsfile maintenance), and
you're confident that it can scale to the size we're expecting when we're
splitting the current aggregator sv
On Sun 8 Oct 2017 at 03:55, Hervé BOUTEMY wrote:
> TLDR; =
> Perhaps we can start with 2 proofs of concept:
> 1. full git clone + Jenkins jobs for the 7 existing git repos (with 6
> additional ones in 2 days)
> 2. git split of one of the aggregator svn trunk: skins or doxia-tools can
> be
> easy
The Apache Maven team is pleased to announce the release of the Apache
Maven Doxia Sitetools, version 1.7.5
Doxia Sitetools is an extension of base Doxia component that generates
either HTML sites, consisting of decoration and content that was generated
by Doxia, or documents like RTF or PD
Hi,
The vote has passed with the following result:
+1 : Robert Scholte, Michael Osipov, Karl Heinz Marbaise, Hervé BOUTEMY
PMC quorum: reached
I will promote the artifacts to the central repo.
On Tue, 26 Sep 2017 20:51:11 +0200, Robert Scholte
wrote:
Hi,
We solved 5 issues:
https://iss
Le dimanche 8 octobre 2017, 15:37:54 CEST Benedikt Ritter a écrit :
> Hello Hervé
>
> > Then I added a pluginManagement section to select version 3.0.2 and re-ran
> > the test: you'll see the output is completely different.
> >
> > And there is no issue any more
>
> Thank you so much, you took t
Hello Tibor
> Am 06.10.2017 um 01:18 schrieb Tibor Digana :
>
> Hi Benedikt,
>
> Would you agree with this plan.
> Since we try to release version 2.21.0 with Jigsaw modularity which is Java 9
> related feature, we can make the same compromise with JUnit5 in next version
> 2.22.0. Altough Suri
Hello Hervé
> Am 04.10.2017 um 01:01 schrieb Hervé BOUTEMY :
>
> trying my chance, because you prepared a perfect demo then we should be able
> to find where the issue is...
>
> Here are my findings:
> mvn depencendy:go-offline output for maven-resources-plugin:
>
> [INFO] Plugin Resolved: mav
The Apache Maven team is pleased to announce the release of the
Apache Maven WAR Plugin, version 3.2.0.
The WAR Plugin is responsible for collecting all artifact dependencies, classes
and resources of the web application and packaging them into a web application
archive.
http://maven.apache.org/
Now I have found out that GitHub has submodules. This does not introduce an
intermediate path in URL but it would introduce a kind of groupper repo
folder. For instance maven-clean-plugin would be submodule inside repo
maven-plugins.
References:
https://stackoverflow.com/questions/35043733/how-do-i
I fear this is not an option today, but ideally, that would be a perfectly
visible grouping
we need to find another way of grouping, for people who do care about Maven
general structure: people who just work on an artifact just don't care
and they don't care that git repos are flat even at Apach
Would we need to have the URLs like these?
github/apache/***/repo
https://github.com/apache/*maven-plugins*/maven-clean-plugin/
https://github.com/apache/*maven-shared*/maven-shared-utils/
On Sun, Oct 8, 2017 at 4:55 AM, Hervé BOUTEMY wrote:
> TLDR; =
> Perhaps we can start with 2 proofs of co
17 matches
Mail list logo
