[GitHub] maven-surefire issue #141: SUREFIRE-1331: Bump version number for 3.0.0 rele...

[Tibor17]

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/141
  
No worries about the commit if it is messy.
I will pick up every single commit, make a patch and apply to master.

On Mon, Jun 5, 2017 at 10:30 AM, Benedikt Ritter 
wrote:

> @Tibor17  this and #146
>  a targeted at the
> 3.0-rc1 branch. So they won't interfere with the release of 2.20.1.
>
> Regarding junit5 support: it is currently pretty messy and I'm to blame
> for this. I'll write something together for the ML and will outline a plan
> on how to get things going again.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> 
,
> or mute the thread
> 

> .
>



-- 
Cheers
Tibor



---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven-surefire issue #146: SUREFIRE-1330: Fix module name in surefire-provid...

[Tibor17]

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/146
  
@britter 
@mgreau 
Done. 
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=70c8843e935882b0a78916894cb9f042964f2717


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven-surefire pull request #146: SUREFIRE-1330: Fix module name in surefire...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/maven-surefire/pull/146


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Looking for a collaborator to work on an experimental fork of the maven-dependency-plugin

[Paul Hammant]

Hi Plamen,

> Using GitHub as Maven repository?

Yup. At least to have it as a choice.

I'm imagining putting releases for my esoteric, long-tail ideas, on
Github *rather
than littering Maven Central.*  But also allowing Maven/Grade/Ivy projects
to source the deps from there directly.  The publishing binaries to Github
isn't the problem I'm trying to solve - it is the acquisition of deps as
builds needs them.  Want to take this offline ?

- Paul

On Mon, Jun 5, 2017 at 11:14 AM, Plamen Totev 
wrote:

> Hi,
>
> I think I had a similar idea. Could you please elaborate what you want to
> achieve? Using GitHub as Maven repository?
>
> I was looking at the matter myself. I didn't spend much time so I have only
> basic understanding of the problems involved and how to solve them.
> As far I know there are (even several) Maven plug-ins that allows you to
> publish Maven artifact to GitHub using the Releases API. But I didn't find
> a way to use GitHub Releases as Maven Repository.
>
> In any case I think the Wagon plug-in is the one that provides the
> transport
> and the one that should be extended in order to be able to reprieve
> artifacts from a new service, not the Dependency plug-in.
>
> Regards,
> Plamen Totev
>
> On Jun 4, 2017 14:23, "Paul Hammant"  wrote:
>
> > So I have 27 releases of XStream unzipped and pushed to
> > https://github.com/paul-hammant/mc-xs-classes
> >
> > (8.4M of Jars is now 2.4M of bare .git repo)
> >
> > All the jars are still available - here -
> > https://github.com/paul-hammant/mc-xs-classes/releases
> >
> > Perfect except:
> >
> >
> >1. .zip suffix instead of .jar
> >2. there's a pesky root folder inside the zip, that matches the tag
> name
> >(GitHub's policy I guess for downloads).
> >3. the signatures won't match those for the originals up on 'Central.
> >
> > I want to fork (experimentally) maven-dependency-plugin (it's in
> Subversion
> > now, but the fork should be on GitHub of course), and sprinkle in some
> > https://github.com/zeroturnaround/zt-zip in order to (1) rename the zip
> on
> > download from GitHub, and (2) remove the root folder inside the zip
> without
> > a mechanical unzip/rezip ... then put theresult in ~/.m2/repository/ as
> > normal.
> >
> > There's probably some pom.xml creativity needed too.
> >
> > Any takers?
> >
> > - Paul
> >
>

Re: Looking for a collaborator to work on an experimental fork of the maven-dependency-plugin

[Plamen Totev]

Hi,

I think I had a similar idea. Could you please elaborate what you want to
achieve? Using GitHub as Maven repository?

I was looking at the matter myself. I didn't spend much time so I have only
basic understanding of the problems involved and how to solve them.
As far I know there are (even several) Maven plug-ins that allows you to
publish Maven artifact to GitHub using the Releases API. But I didn't find
a way to use GitHub Releases as Maven Repository.

In any case I think the Wagon plug-in is the one that provides the transport
and the one that should be extended in order to be able to reprieve
artifacts from a new service, not the Dependency plug-in.

Regards,
Plamen Totev

On Jun 4, 2017 14:23, "Paul Hammant"  wrote:

> So I have 27 releases of XStream unzipped and pushed to
> https://github.com/paul-hammant/mc-xs-classes
>
> (8.4M of Jars is now 2.4M of bare .git repo)
>
> All the jars are still available - here -
> https://github.com/paul-hammant/mc-xs-classes/releases
>
> Perfect except:
>
>
>1. .zip suffix instead of .jar
>2. there's a pesky root folder inside the zip, that matches the tag name
>(GitHub's policy I guess for downloads).
>3. the signatures won't match those for the originals up on 'Central.
>
> I want to fork (experimentally) maven-dependency-plugin (it's in Subversion
> now, but the fork should be on GitHub of course), and sprinkle in some
> https://github.com/zeroturnaround/zt-zip in order to (1) rename the zip on
> download from GitHub, and (2) remove the root folder inside the zip without
> a mechanical unzip/rezip ... then put theresult in ~/.m2/repository/ as
> normal.
>
> There's probably some pom.xml creativity needed too.
>
> Any takers?
>
> - Paul
>

[GitHub] maven-surefire issue #141: SUREFIRE-1331: Bump version number for 3.0.0 rele...

[britter]

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/141
  
@Tibor17 this and #146 a targeted at the 3.0-rc1 branch. So they won't 
interfere with the release of 2.20.1.

Regarding junit5 support: it is currently pretty messy and I'm to blame for 
this. I'll write something together for the ML and will outline a plan on how 
to get things going again.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven-surefire issue #146: SUREFIRE-1330: Fix module name in surefire-provid...

[britter]

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/146
  
@Tibor17 I'm currently working on a `JUnitPlattformProviderInfo`. I have 
some issues with the ITs, which I will bring up on the ML.

In the mean time, I need you to merge this PR. The build in 3.0-rc1 branch 
is currently broken if we don't fix this, since the surefire-provider project 
references an unknown module. This is because the name of the module is wrong 
in surefire-provider pom.xml. So PLEASE, merge this!


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

issues deleting workspace

[Hervé BOUTEMY]

Hi,

We have some false positives in our Maven tests because Jenkins can't delete 
old apache-maven-dist/lib/jansi-native on some nodes [1] (H24 in this case)

Do any of our Jenkins masters here know how to force the delete on every 
nodes, so this issue from the past does not hit us?
Another idea would be to have Jenkins code try forcing the rm (like "rm -rf" 
does): I know this case of a code creating files with wrong permissions is 
rare, but add code to be permissions proof would be beneficial

I can also create an INFRA issue each time such a case is found, but this will 
be annoying for everybody...

Regards,

Hervé

[1] 
https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/job/maven-master-release-status-test-core-integration-testing-linux/229/console

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