Re: Maven resolver branch consolidation

2017-11-22 Thread Stephen Connolly 
On Thu 23 Nov 2017 at 04:20, Manfred Moser  wrote:

> Status update and questions:
>
> - demos are all now in master and part of the multi module build
> - no changes on the ant tasks for now
>
> Questions:
>
> 1. Can I delete the demos branch now or do we wait until next release? I
> would prefer to delete the branch and close the ticket to be honest.
>
> 2. I like the idea of promoting the ant task from being hidden in the
> branch into their own repo. All we would have to do is to copy the existing
> repo somehow into a new repo in apache git. Then we can dDelete all the
> branches apart from the ant-task branch and make that the master. Done. I
> am happy to do that in terms of the branches and so on but how do I go
> about getting the repo copied into a new repo named
> maven-resolver-ant-tasks?


I like that solution too

>
>
> Thanks
>
> Manfred
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

[GitHub] maven-surefire issue #168: [SUREFIRE-1424] javax.transaction.TransactionMana...

2017-11-22 Thread eolivelli 
Github user eolivelli commented on the issue:

https://github.com/apache/maven-surefire/pull/168
  
Ok will do asap


---

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

Re: Maven resolver branch consolidation

2017-11-22 Thread Manfred Moser 
Status update and questions:

- demos are all now in master and part of the multi module build
- no changes on the ant tasks for now

Questions:

1. Can I delete the demos branch now or do we wait until next release? I would 
prefer to delete the branch and close the ticket to be honest. 

2. I like the idea of promoting the ant task from being hidden in the branch 
into their own repo. All we would have to do is to copy the existing repo 
somehow into a new repo in apache git. Then we can dDelete all the branches 
apart from the ant-task branch and make that the master. Done. I am happy to do 
that in terms of the branches and so on but how do I go about getting the repo 
copied into a new repo named maven-resolver-ant-tasks? 

Thanks

Manfred

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

[GitHub] maven-surefire issue #170: [SUREFIRE-1448] Clarified specifying multiple cat...

2017-11-22 Thread Tibor17 
Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/170
  
Sorry, I mean the commit message. We have one standard of naming 
conventions in git history.


---

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

[GitHub] maven-scm issue #56: [SCM-739] Use shallow clones when cloning a git repo

2017-11-22 Thread olamy 
Github user olamy commented on the issue:

https://github.com/apache/maven-scm/pull/56
  
Good idea!! but the change is not backward compat so IMHO we need something 
configurable. 
Default clone must a complete per default and we can add a new parameter 
for this (release plugin must be changed to use the new parameter)
WDYT?


---

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

[GitHub] maven-surefire issue #168: [SUREFIRE-1424] javax.transaction.TransactionMana...

2017-11-22 Thread Tibor17 
Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/168
  
@eolivelli 
I have finished my changes in master. Can you continue?


---

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

[GitHub] maven-scm pull request #56: [SCM-739] Use shallow clones when cloning a git ...

2017-11-22 Thread arteam 
GitHub user arteam opened a pull request:

https://github.com/apache/maven-scm/pull/56

[SCM-739] Use shallow clones when cloning a git repo

For `maven-release-plugin` we don't need the whole history, but only the 
top commit. Using `--depth 1` allows to perform releases much faster on 
repositories with a long history.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/arteam/maven-scm git-clone-shallow

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-scm/pull/56.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #56


commit c041868bf8c543cecb34c8f002f02438e6f81b52
Author: Artem Prigoda 
Date:   2017-11-22T15:52:00Z

[SCM-739] Use shallow clones when cloning a git repo

For `maven-release-plugin` we don't need the whole history, but
only the top commit. Using `--depth 1` allows to perform releases
much faster on repositories with a long history.




---

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

Re: FYI INFRA-15524 created for the better Jenkins UX

2017-11-22 Thread Stephen Connolly 
Scheduled for the November 26th upgrade:
https://cwiki.apache.org/confluence/display/INFRA/Jenkins+Plugin+Upgrades

On 21 November 2017 at 14:46, Arnaud Héritier  wrote:

> yeah !!
>
> On Tue, Nov 21, 2017 at 2:10 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > https://issues.apache.org/jira/browse/INFRA-15524
> >
> > Hervé it is nearly time to party!
> >
>
>
>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>

[GitHub] maven-archetype pull request #18: Update JUnit dependency version.

2017-11-22 Thread luankevinferreira 
GitHub user luankevinferreira opened a pull request:

https://github.com/apache/maven-archetype/pull/18

Update JUnit dependency version.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/luankevinferreira/maven-archetype patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-archetype/pull/18.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #18


commit 3835e395c7ca8575f4a671f9e5c9ec661156fb57
Author: Luan Kevin Ferreira 
Date:   2017-11-22T09:44:16Z

Update JUnit dependency version.




---

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