Re: Maven Plugin that provides alternative repository

[Christoph Laeubrich]

Hi,

thanks for your reply. I'd like to make artifacts avaiable to maven
via  that are located in a repository with a format that
maven does not understand.
Even though if I would have the group+artifactid+version I can locate
that artifact there.
So the idea is to add a plugin to the build that gets asked whenever
maven does not find an artifact in any of its default sources so I can
give it a try to find it in my special repro.

Even though it might be possible to convert the other repro to a maven
structure, this means I have to download all artifacts from this,
upload them again and repeat the stepp an each change, thats why I'd
like to find a way to use the repro directly.

2017-10-12 18:48 GMT+02:00 Karl Heinz Marbaise :
> Hi,
>
> On 12/10/17 16:28, Christoph Laeubrich wrote:
>>
>> Hi,
>>
>> I'd like to create a plugin that gets notified if maven tries to
>> download an artifact but does not find it in any of its configured
>> repositories. Is this possible to archive by a maven plugin? If yes
>> what is the best starting point for this?
>
>
> My first question is: What is the background of this question? Means what
> are you trying to solve? What kind of problem do you have?
>
>
>>
>> My own search for this have not revelead any usefull information
>> beside basic maven plugin tutorials that do not cover this specific
>> case.
>>
>
> Kind regards
> Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Reporting Exec version 1.4

[Arnaud Héritier]

+1

On Sun, Oct 15, 2017 at 5:54 PM, Robert Scholte 
wrote:

> +1
>
>
> On Fri, 13 Oct 2017 02:09:58 +0200, Hervé BOUTEMY 
> wrote:
>
> Hi,
>>
>> We solved 3 issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12317922=12338621
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1372
>> https://repository.apache.org/content/repositories/maven-1372/org/apache/
>> maven/reporting/maven-reporting-exec/1.4/maven-reporting-exec-1.4-source-
>> release.zip
>>
>> Source release checksum(s):
>> maven-reporting-exec-1.4-source-release.zip sha1:
>> c1f3c12a24ec4513f5adbb4152ec6a314f0c4a2b
>>
>> Staging site:
>> http://maven.apache.org/shared-archives/maven-reporting-exec-LATEST/
>> Guide to testing staged releases:
>> https://maven.apache.org/guides/development/guide-testing-releases.html
>> Vote open for at least 72 hours.
>>[ ] +1
>> [ ] +0
>> [ ] -1
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Re: [VOTE] Release Apache Maven Reporting Exec version 1.4

[Robert Scholte]

+1

On Fri, 13 Oct 2017 02:09:58 +0200, Hervé BOUTEMY   
wrote:



Hi,

We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12317922=12338621

Staging repo:
https://repository.apache.org/content/repositories/maven-1372
https://repository.apache.org/content/repositories/maven-1372/org/apache/
maven/reporting/maven-reporting-exec/1.4/maven-reporting-exec-1.4-source-
release.zip

Source release checksum(s):
maven-reporting-exec-1.4-source-release.zip sha1:
c1f3c12a24ec4513f5adbb4152ec6a314f0c4a2b

Staging site:
http://maven.apache.org/shared-archives/maven-reporting-exec-LATEST/
Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for at least 72 hours.
   [ ] +1
[ ] +0
[ ] -1

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Surefire and JUnit 5

[Tibor Digana]

Hi Benedikt,

I am fine now after my illness, thx.
I am finishing branch SUREFIRE-1262_2. Just to add few more tests and then
I will cut a release. I want to add a fix for SUREFIRE-1374 which would be
fast to do.
Then I am ready for you and JUnit5.

I have questions regarding our JUnit 5 Surefire Provider implemented in
Surefire.

Is it implemented exactly in the same like the origin by junit5 team?
I am asking because I saw the implementation made by junit5 team and it is
not like our *JUnitCoreProvider*. This means that they do not map method
<-> Thread in *RunListener *and thus the provider would not associate test
report logs and Thread properly and logs will be mixed.

Next question is regarding the feature re-run. It also exists in
*JUnitCoreProvider
*and *JUnit4Provider*. Does it exist in our provider too.
Also we need to have a feature where JUnit execution is stopped which can
be configured by *skipAfterFailureCount *in POM. We have implementation in
Surefire provider:

notifier.asFailFast( isFailFast() );

Regarding logger in forked provider, which has to do with parallel exec, I
think the logs go to the dump file instead of reports file, because STDOUT
is not wrapped in JUnit5's implementation and this should be called:

startCapture( listener )


See my questions in https://github.com/xwiki/xwiki-platform/commit/
5258a22301977a7d1ee7276cdd81af7641f4f5ac

Do we have integration tests for these features?


Cheers
Tibor



On Sat, Sep 30, 2017 at 10:34 AM, Benedikt Ritter 
wrote:

> Hello,
>
> for over a year now I’m trying to help getting JUnit 5 support into Maven
> Surefire. This has been hard since Tibor seems to be the only one
> maintaining Maven Surefire and he had to come with other things.
>
> For this reason I’d like to ask other Maven maintainers to help with the
> JUnit 5 support. I’m happy to do the work, but I’m constantly blocked by
> obscure build failures which I’m unable to resolve myself or by lack of
> code review und merge of changes.
>
> - Work on JUnit5 support is currently done in the junit5 branch.
> - I have drafted a Provider Lookup implementation in the junit5 branch,
> but I don’t know whether it works because I can’t get the integration tests
> running
> - There is an open PR to merge the master branch back into junit5 branch,
> but it has build failures I don’t understand [1]
>
> Please help!
> Cheers,
> Benedikt
>
> [1] https://github.com/apache/maven-surefire/pull/165
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven 3.5.1

[Karl Heinz Marbaise]

Hi,

On 12/10/17 08:21, Stephen Connolly wrote:

Ok as release manager I am cancelling this vote. I’ll see about spinning
3.5.2


could we make such thing a little bit more obvious like prefixing the 
subject with "[CANCELED]..." so it becomes more clear that the VOTE has 
been canceled...it's better to identify in the thread view


Kind regards
Karl Heinz Marbaise



On Thu 12 Oct 2017 at 02:51, Hervé BOUTEMY  wrote:


Le mercredi 11 octobre 2017, 23:47:54 CEST Robert Scholte a écrit :

I think the conclusion is: 3.5.1 is not correct

it should either be:
3.5.2 without the 2 classloader related issues.

ideally with an option to activate the classloader changes (for people
knowing
what they are doing or wanting to test mode more widely)


or
3.6.0 including the classloader related issues, but probably improved

with

a system property to switch back to the 3.5.0-behavior. We also need to
improve ITs and documentation.

Since we need to make a new release anyway I would like to suggest to go
for the first option, because some claim 3.5.0 is corrupt and the related
issue is already fixed for quite some time.

+1 (sadly)

Regards,

Hervé


This should give us more time have a better look at these classloader
issues.

Robert

On Wed, 11 Oct 2017 09:46:25 +0200, Stephen Connolly

 wrote:

I’d really like if somebody could draft the release notes for the two
different classloader changes. It will make it easier to decide whether
to
roll with this or bump minor with (if I recall correctly) the
corresponding
drop of Java 7 per our policy on JVMs with minor version bump

On Wed 11 Oct 2017 at 07:33, Hervé BOUTEMY 

wrote:

+1
eventually adding a flag or system property to activate the new
behaviour

this remembers me of the idea regarding flags to support new beta
features

Regards,

Hervé

Le mercredi 11 octobre 2017, 08:13:13 CEST Anders Hammar a écrit :

I'm feeling stronger and stronger about not having this change in a


bugfix


release. Why not go for v3.6.0 if we decide that the class loading


change


is the way to go? And keep bugfix releases for just bugfixes.

/Anders

On Wed, Oct 11, 2017 at 3:43 AM, Hervé BOUTEMY <

herve.bout...@free.fr>


wrote:

perhaps we should create a Wiki page for


java.lang.ClassNotFoundException


and
list the plugins with known issues and minimum fixed version

to be added in




https://cwiki.apache.org/confluence/display/MAVEN/Errors+and+Solutions



Regards,

Hervé

Le mercredi 11 octobre 2017, 02:52:53 CEST Hervé BOUTEMY a écrit :

IIUC, it's MDEPLOY-221 about


net.flexmojos.oss:flexmojos-maven-plugin


https://issues.apache.org/jira/browse/MDEPLOY-221

Regards,

Hervé

Le mardi 10 octobre 2017, 20:48:13 CEST Robert Scholte a écrit :

FYI, MDEPLOY-121 mentions another plugin being hit by the


classloader


changes.

Robert


On Tue, 03 Oct 2017 20:22:18 +0200, Arnaud Héritier <


aherit...@gmail.com>


wrote:

Thanks Stephen

On Tue, Oct 3, 2017 at 8:18 PM, Stephen Connolly <

stephen.alan.conno...@gmail.com> wrote:

I am hoping I can find some time to do a final round of


experiments


and


then close the vote with success and publish.

On Tue 3 Oct 2017 at 11:13, Arnaud Héritier <


aherit...@gmail.com>


wrote:

@Stephen What should we do now ?


On Tue, Sep 19, 2017 at 3:14 AM, Olivier Lamy <


ol...@apache.org>


wrote:

Hi
Sorry a bit out of time ATM for testing this.
Well I trust Arnaud testing that especially if this


improve
the


performance
of this very great/awesome/users oriented plugin :P

On 13 September 2017 at 22:19, Arnaud Héritier


wrote:

Damned, can't we be anonymous on Github ?
I maintain it is a big word, I'm trying to fix more

bugs


than


I
add


new


ones
I added Oleg in the loop as he contributed a lot on it


too


I did a quick test to build on Jenkins 2.60.3 our

maven


core


with


the


Evil


Maven plugin 2.17 on a local SSH agent and it is ok
But it is really a quick test ...

Cheers



On Wed, Sep 13, 2017 at 10:07 AM, Stephen Connolly <

stephen.alan.conno...@gmail.com> wrote:

On 13 September 2017 at 01:05, Stephen Connolly <

stephen.alan.conno...@gmail.com> wrote:

On 13 September 2017 at 00:26, Anders Hammar



wrote:

On Tue, Sep 12, 2017 at 8:54 PM, Stephen Connolly

<


stephen.alan.conno...@gmail.com> wrote:

Have we got any feedback from the embedder


integrations


yet?


I haven't heard anything from the m2e people.

Maybe


we


need to


ping


them


directly. I can contact Fred Bricon.

/Anders


Please do, also if anyone has a contact in netbeans


or


intellij


and


could


let them know we'd like either feedback or "we're

ok


if


MNG-6275


makes


trouble for us, go ahead and release". I'd like to


close


the


vote
on


Friday


13:00 UTC.


Olivier / Arnaud, have either of you had a chance to


test


this


with


the


evil project type[1] as you two seem to be the

Re: improvements for Maven 3.5.2

[Hervé BOUTEMY]

merged, thank you

Le samedi 14 octobre 2017, 18:11:52 CEST Stephen Connolly a écrit :
> +1
> 
> On Sat 14 Oct 2017 at 16:30, Hervé BOUTEMY  wrote:
> > I'd like to merge to master following issues, with corresponding code
> > ready in
> > their branches:
> > - MNG-6242 No color for maven on Cygwin
> > - MNG-6196 Update slf4j and simplify its color integration
> > 
> > Are there seconders?
> > 
> > Regards,
> > 
> > Hervé
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> > --
> 
> Sent from my phone



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org