Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

Hello I'm not sure if I can give any vote (even non-binding +1), but I tested several large OSGi projects using 3.5.0-alpha-1 without problems. regards Grzegorz Grzybek 2017-02-23 23:44 GMT+01:00 Stephen Connolly : > This is only an alpha, I'm not calling a halt

Escaping rules for filtering.

Hi, during testing various projects to build from inside a directory "Spaces & Special Char" I stumbled upon an issue also reported by users over the years. I'd like to know the status on this. Do we plan to implement any kind of escaping rules for filtering? Based on what? File extension? MIME

Re: maven-3.x-jenkinsfile/master - build #57 - null

the message "null" here still happens for a failed build: our Jenklinsfile does not look to be reliable when sending emails Regards, Hervé Le jeudi 23 février 2017, 18:55:11 CET Apache Jenkins Server a écrit : > See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/57/

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

This is only an alpha, I'm not calling a halt unless it is S1/S2, alpha-2 can follow next week On 23 February 2017 at 21:56, Christian Schulte wrote: > Can we have this patch included? I wanted to commit this to master > yesterday when the build job succeeded. This is just

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

Can we have this patch included? I wanted to commit this to master yesterday when the build job succeeded. This is just pending the Jenkins update to get the job succeed. I would just merge it to master now.

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

Am 02/23/17 um 19:20 schrieb Michael Osipov: > So guys, > > I took a different approach to provide Tibor more information about the > failures. First of all, I added another platform for the test which is > exotic: HP-UX 11.31. The VM comes directly from HPE which is a > repackaged Oracle JVM.

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

Hi, tested a larger number of apache maven plugins to build with the new version, tested also to build several plugins from mojohaus with the new version. No issues found yet. So +1 from me. Kind regards Karl Heinz Marbaise On 23/02/17 17:10, Stephen Connolly wrote: Hi, We solved 65

[GitHub] maven-archetype pull request #17: Fix spelling of rigorous

GitHub user danielcompton opened a pull request: https://github.com/apache/maven-archetype/pull/17 Fix spelling of rigorous You can merge this pull request into a Git repository by running: $ git pull https://github.com/danielcompton/maven-archetype fix-spelling-rigorous

Re: Recent issues found in Surefire master/Maven Clean Plugin 3.0.0 with Maven master

So guys, I took a different approach to provide Tibor more information about the failures. First of all, I added another platform for the test which is exotic: HP-UX 11.31. The VM comes directly from HPE which is a repackaged Oracle JVM. I started Git bisect and discovered some broken

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

+1 On Thu, Feb 23, 2017 at 5:43 PM, stephenconnolly [via Maven] < ml-node+s40175n5899782...@n5.nabble.com> wrote: > +1 > > Analyzer... > > stagingUrl: https://repository.apache.org/content/repositories/maven-1324 > groupId: org.apache.maven > artifactId: apache-maven > version: 3.5.0-alpha-1 > >

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

+1 Analyzer... stagingUrl: https://repository.apache.org/content/repositories/maven-1324 groupId: org.apache.maven artifactId: apache-maven version: 3.5.0-alpha-1 Source ZIP url exists.

[VOTE] Release Apache Maven 3.5.0-alpha-1

Hi, We solved 65 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12339664=Text There are still a couple of issues left in JIRA for 3.5.0, but I do not think any of those are blocking an alpha release:

[GitHub] maven-plugins pull request #104: MASSEMBLY-848 Do not attempt to resolve rea...

Github user io7m closed the pull request at: https://github.com/apache/maven-plugins/pull/104 --- 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

Re: maven-3.x-jenkinsfile/master - build #54 - null

https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/56/ we are back to a blue build! w00t! On 23 February 2017 at 12:48, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I pushed a different work-around in https://github.com/apache/ >

Re: maven-3.x-jenkinsfile/master - build #54 - null

I pushed a different work-around in https://github.com/apache/maven/commit/5cce371c8aee5d957d9b24e46cddc939a15aff40 This also adds the *magic* resolveScm step, so if you have an integration test branch with the same name as your maven core branch, then the branch should be automatically detected

Re: maven-3.x-jenkinsfile/master - build #54 - null

Am 02/23/17 um 09:07 schrieb Stephen Connolly: > Yes. Infra updated some Jenkins plugins and now the Windows path is too > long. > > I need them to upgrade to branch-api 2.0.7 (released yesterday) and set a > system property to resolve the issue Good to know. I updated various build jobs of the

Re: maven-3.x-jenkinsfile/master - build #54 - null

Yes. Infra updated some Jenkins plugins and now the Windows path is too long. I need them to upgrade to branch-api 2.0.7 (released yesterday) and set a system property to resolve the issue On Thu 23 Feb 2017 at 05:47, Christian Schulte wrote: > Am 02/23/17 um 06:18 schrieb