Re: maven-archiver build on Jenkins - Test Failures

2017-12-27 Thread Sylwester Lachiewicz
Ok, after more tests i found that error exists when project was executed in
path with @ char that was encoded to %402 -
https://issues.apache.org/jira/browse/SUREFIRE-1312

Sylwester

śr., 27 gru 2017 o 13:31 użytkownik Karl Heinz Marbaise 
napisał:

> Hi,
>
> On 27/12/17 13:01, Sylwester Lachiewicz wrote:
> > Build fails with long directory name - also on windows.
> > Upgrade maven-surefire-plugin to 2.20.1 fixes test error.
>
> Hm..this is a little bit confusing, cause the length for windows are
> about 141 characters (already thought about something similar) but the
> upgrade changes the situation completely ...Thanks for that hint..
>
>
> Just one test cases is failing...
>
> Kidn regards
> Karl Heinz Marbaise
>
> >
> >
> > śr., 27 gru 2017 o 08:49 użytkownik Plamen Totev <
> plamen.iv.to...@gmail.com>
> > napisał:
> >
> >> And if this could help (I know it's obvious but may safe time) it
> >> looks the reason for the failing tests is the same. The following code
> >> fails with assertion error:
> >>
> >>  final Manifest manifest = getJarFileManifest( jarFile );
> >>  String classPath = manifest.getMainAttributes().getValue(
> >> Attributes.Name.CLASS_PATH );
> >>  assertNotNull( classPath );
> >>
> >> The NullPointerExceptions from the rest of the tests are coming from
> >> the same expression (`manifest.getMainAttributes().getValue(
> >> "Class-Path" ).getBytes()`).
> >>
> >> On Wed, Dec 27, 2017 at 9:39 AM, Plamen Totev <
> plamen.iv.to...@gmail.com>
> >> wrote:
> >>> Hi,
> >>>
> >>> On Tue, Dec 26, 2017 at 9:01 PM, Karl Heinz Marbaise <
> khmarba...@gmx.de>
> >> wrote:
> >>>
>  Is someone out there who can check the current state of maven-archiver
> >> git
>  repo on Windows and can reproduce the issue ?
> >>>
> >>> I ran the build a couple of times(just in case) on Windows 10, Maven
> >>> 3.5.2, JDK 9.0.1 and everything is ok. And it looks like the build is
> >>> failing on Linux JDK 9 and Windows JDK 8 as well, so if there is a bug
> >>> (and not a problem with the build) then it is probably not a Windows
> >>> or JDK 9 related.
> >>>
> >>> Regards,
> >>> Plamen Totev
>


Re: Questions regarding improving the Apache Commons release process.

2017-12-27 Thread Rob Tompkins
Stephen,

I can’t thank you enough for your reply. I’ll take your suggestions and 
continue to sandbox around using the maven-release-plugin as a guideline.

All the best and happy holidays,
-Rob

> On Dec 26, 2017, at 5:27 AM, Stephen Connolly 
>  wrote:
> 
> On Tue 26 Dec 2017 at 03:10, Rob Tompkins  > wrote:
> 
>> Hello all,
>> 
>> Pardon, maybe this should have gone to your @user list, but why not ping
>> the dev crew. I’ve been playing around the ideas surrounding our fairly
>> manual release process for the components in Commons, and I was hoping for
>> some insights.
>> 
>> Scripting the version changes isn’t really that big of a deal for us, and
>> that I can manage. But, when it comes to publishing our artifacts to the
>> apache nexus repository, and then separately publishing our -src and -bin
>> assemblies to the dev dist subversion repository (and consequently deleting
>> those artifacts from nexus as they’re “attached” for the purpose of gpg
>> signing), I feel it a tad cumbersome.
>> 
>> I’ve fiddled around a little with the idea of detaching the -src and -bin
>> assemblies after gpg signing with some success, but then I have to delve
>> into the mechanics of publishing those up to the subversion repository, and
>> clearly that problem has already been solved.
> 
> 
> Is your problem you don’t want those going to Nexus staging but only to
> dist? Or is it that you want them *also* going to dist.
> 
> Personally... I see no reason to remove them from going to Nexus staging
> (in fact I have a background plan to add secondary signing support to
> staging... i’m Waiting to see the Nexus 3 staging APIs before attempting
> though. That would mean that the PMC would be able to *add* their GPG
> signature to the staged artifacts as part of the voting... in which case
> you’d want to hold off uploading to dist until *after* the vote so you get
> the full set of signatures)
> 
> If you want to upload a subset of attached artifacts to dist as part of the
> release, that seems much more tenable... just a derivative of the
> scm-publish plugin from what I can see.
> 
> So I find myself in the space of trying to shoehorn our process into its
>> the main maven-release-plugin, which I’ve found a tad difficult, versus
>> writing our own release plugin, which feels like I would be duplicating
>> tons of code (which I don’t want to do).
> 
> 
> So the release plugin is really two parts:
> 
> 1. A toolkit for writing release plugins
> 
> 2. An example that does the job for the requirements of the Maven TLP and
> has seemed “sufficient” for a lot of other people.
> 
> As such, if you have different needs, do not feel bad about having to
> encode differently... hopefully the toolkit half of the codebase is
> sufficient for you.
> 
>> 
>> 
>> I’m curious if you guys have any thoughts on the matter as I’ve been
>> playing around in the space for a little while now.
>> 
>> Cheers and happy holidays from UTC-5,
>> -Rob
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@maven.apache.org 
>> 
>> 
>> --
> Sent from my phone



Re: [VOTE] Release Apache Maven Doxia Sitetools version 1.8

2017-12-27 Thread Karl Heinz Marbaise

Hi,

tested with the following:
jdk1.7.0_79.jdk
  apache-maven-3.0.5..Unpacking done.Building fine.
  apache-maven-3.1.1..Unpacking done.Building fine.
  apache-maven-3.2.5..Unpacking done.Building fine.
  apache-maven-3.3.1..Unpacking done.Building fine.
  apache-maven-3.3.9..Unpacking done.Building fine.
  apache-maven-3.5.0..Unpacking done.Building fine.
  apache-maven-3.5.2..Unpacking done.Building fine.
jdk1.8.0_131.jdk
  apache-maven-3.0.5..Unpacking done.Building fine.
  apache-maven-3.1.1..Unpacking done.Building fine.
  apache-maven-3.2.5..Unpacking done.Building fine.
  apache-maven-3.3.1..Unpacking done.Building fine.
  apache-maven-3.3.9..Unpacking done.Building fine.
  apache-maven-3.5.0..Unpacking done.Building fine.
  apache-maven-3.5.2..Unpacking done.Building fine.
jdk1.8.0_144.jdk
  apache-maven-3.0.5..Unpacking done.Building fine.
  apache-maven-3.1.1..Unpacking done.Building fine.
  apache-maven-3.2.5..Unpacking done.Building fine.
  apache-maven-3.3.1..Unpacking done.Building fine.
  apache-maven-3.3.9..Unpacking done.Building fine.
  apache-maven-3.5.0..Unpacking done.Building fine.
  apache-maven-3.5.2..Unpacking done.Building fine.
jdk-9.0.1.jdk
  apache-maven-3.0.5..Unpacking done.Building fine.
  apache-maven-3.1.1..Unpacking done.Building fine.
  apache-maven-3.2.5..Unpacking donBuilding fine...
  apache-maven-3.3.1..Unpacking done.Building fine.
  apache-maven-3.3.9..Unpacking done.Building fine.
  apache-maven-3.5.0..Unpacking done.Building fine.
  apache-maven-3.5.2..Unpacking done.Building fine.

No issues found.

So +1 from me.

Kind regards
Karl Heinz Marbaise

On 21/12/17 23:31, Hervé BOUTEMY wrote:

Hi,
 
We solved 7 issues:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12317320=12339613=Text
 
There are still a couple of issues left in JIRA:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20DOXIASITETOOLS
%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
 
Staging repo:

https://repository.apache.org/content/repositories/maven-1384/
https://repository.apache.org/content/repositories/maven-1384/org/apache/
maven/doxia/doxia-sitetools/1.8/doxia-sitetools-1.8-source-release.zip
 
Source release checksum(s):

doxia-sitetools-1.8-source-release.zip sha1:
0051af3da2ba632a9e0f753b0ffbc15358986ccd
 
Staging site:

http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-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



Re: [VOTE] Release Apache Maven PDF Plugin version 1.4

2017-12-27 Thread Karl Heinz Marbaise

Hi,

tested like this:

jdk1.7.0_79.jdk
  apache-maven-3.0.5..Unpacking done.Building fine.
  apache-maven-3.1.1..Unpacking done.Building fine.
  apache-maven-3.2.5..Unpacking done.Building fine.
  apache-maven-3.3.1..Unpacking done.Building fine.
  apache-maven-3.3.9..Unpacking done.Building fine.
  apache-maven-3.5.0..Unpacking done.Building fine.
  apache-maven-3.5.2..Unpacking done.Building fine.
jdk1.8.0_131.jdk
  apache-maven-3.0.5..Unpacking done.Building fine.
  apache-maven-3.1.1..Unpacking done.Building fine.
  apache-maven-3.2.5..Unpacking done.Building fine.
  apache-maven-3.3.1..Unpacking done.Building fine.
  apache-maven-3.3.9..Unpacking done.Building fine.
  apache-maven-3.5.0..Unpacking done.Building fine.
  apache-maven-3.5.2..Unpacking done.Building fine.
jdk1.8.0_144.jdk
  apache-maven-3.0.5..Unpacking done.Building fine.
  apache-maven-3.1.1..Unpacking done.Building fine.
  apache-maven-3.2.5..Unpacking done.Building fine.
  apache-maven-3.3.1..Unpacking done.Building fine.
  apache-maven-3.3.9..Unpacking done.Building fine.
  apache-maven-3.5.0..Unpacking done.Building fine.
  apache-maven-3.5.2..Unpacking done.Building fine.
jdk-9.0.1.jdk
  apache-maven-3.0.5..Unpacking done.Building fine.
  apache-maven-3.1.1..Unpacking done.Building fine.
  apache-maven-3.2.5..Unpacking done.Building fine.
  apache-maven-3.3.1..Unpacking done.Building fine.
  apache-maven-3.3.9..Unpacking done.Building fine.
  apache-maven-3.5.0..Unpacking done.Building fine.
  apache-maven-3.5.2..Unpacking done.Building fine.

No issues found..

So +1 from me.

Kind regards
Karl Heinz Marbaise
On 22/12/17 10:11, Hervé BOUTEMY wrote:

Hi,
 
We solved 12 issues:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12317620=1238=Text
 
There are still a couple of issues left in JIRA:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPDF%20AND%20status
%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
 
Staging repo:

https://repository.apache.org/content/repositories/maven-1385/
https://repository.apache.org/content/repositories/maven-1385/org/apache/
maven/plugins/maven-pdf-plugin/1.4/maven-pdf-plugin-1.4-source-release.zip
 
Source release checksum(s):

maven-pdf-plugin-1.4-source-release.zip sha1:
88d2d254e674938b197df6b37b54c75ec817fcf4
 
Staging site:

https://maven.apache.org/plugins-archives/maven-pdf-plugin-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



Re: maven-archiver build on Jenkins - Test Failures

2017-12-27 Thread Karl Heinz Marbaise

Hi,

On 27/12/17 13:01, Sylwester Lachiewicz wrote:

Build fails with long directory name - also on windows.
Upgrade maven-surefire-plugin to 2.20.1 fixes test error.


Hm..this is a little bit confusing, cause the length for windows are 
about 141 characters (already thought about something similar) but the 
upgrade changes the situation completely ...Thanks for that hint..



Just one test cases is failing...

Kidn regards
Karl Heinz Marbaise




śr., 27 gru 2017 o 08:49 użytkownik Plamen Totev 
napisał:


And if this could help (I know it's obvious but may safe time) it
looks the reason for the failing tests is the same. The following code
fails with assertion error:

 final Manifest manifest = getJarFileManifest( jarFile );
 String classPath = manifest.getMainAttributes().getValue(
Attributes.Name.CLASS_PATH );
 assertNotNull( classPath );

The NullPointerExceptions from the rest of the tests are coming from
the same expression (`manifest.getMainAttributes().getValue(
"Class-Path" ).getBytes()`).

On Wed, Dec 27, 2017 at 9:39 AM, Plamen Totev 
wrote:

Hi,

On Tue, Dec 26, 2017 at 9:01 PM, Karl Heinz Marbaise 

wrote:



Is someone out there who can check the current state of maven-archiver

git

repo on Windows and can reproduce the issue ?


I ran the build a couple of times(just in case) on Windows 10, Maven
3.5.2, JDK 9.0.1 and everything is ok. And it looks like the build is
failing on Linux JDK 9 and Windows JDK 8 as well, so if there is a bug
(and not a problem with the build) then it is probably not a Windows
or JDK 9 related.

Regards,
Plamen Totev


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



Re: [VOTE] Release Apache Maven Doxia Sitetools version 1.8

2017-12-27 Thread Michael Osipov

Am 2017-12-21 um 23:31 schrieb Hervé BOUTEMY:

Hi,
 
We solved 7 issues:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12317320=12339613=Text
 
There are still a couple of issues left in JIRA:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20DOXIASITETOOLS
%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
 
Staging repo:

https://repository.apache.org/content/repositories/maven-1384/
https://repository.apache.org/content/repositories/maven-1384/org/apache/
maven/doxia/doxia-sitetools/1.8/doxia-sitetools-1.8-source-release.zip
 
Source release checksum(s):

doxia-sitetools-1.8-source-release.zip sha1:
0051af3da2ba632a9e0f753b0ffbc15358986ccd
 
Staging site:

http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-LATEST/
 
Guide to testing staged releases:

https://maven.apache.org/guides/development/guide-testing-releases.html
 
Vote open for at least 72 hours.


+1


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



Re: [VOTE] Release Apache Maven Doxia Sitetools version 1.8

2017-12-27 Thread Robert Scholte

+1

On Thu, 21 Dec 2017 23:31:14 +0100, Hervé BOUTEMY   
wrote:



Hi,
We solved 7 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12317320=12339613=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20DOXIASITETOOLS
%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-1384/
https://repository.apache.org/content/repositories/maven-1384/org/apache/
maven/doxia/doxia-sitetools/1.8/doxia-sitetools-1.8-source-release.zip
Source release checksum(s):
doxia-sitetools-1.8-source-release.zip sha1:
0051af3da2ba632a9e0f753b0ffbc15358986ccd
Staging site:
http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-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: [VOTE] Release Apache Maven PDF Plugin version 1.4

2017-12-27 Thread Robert Scholte

+1

On Fri, 22 Dec 2017 10:11:32 +0100, Hervé BOUTEMY   
wrote:



Hi,
We solved 12 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12317620=1238=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPDF%20AND%20status
%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-1385/
https://repository.apache.org/content/repositories/maven-1385/org/apache/
maven/plugins/maven-pdf-plugin/1.4/maven-pdf-plugin-1.4-source-release.zip
Source release checksum(s):
maven-pdf-plugin-1.4-source-release.zip sha1:
88d2d254e674938b197df6b37b54c75ec817fcf4
Staging site:
https://maven.apache.org/plugins-archives/maven-pdf-plugin-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-archiver build on Jenkins - Test Failures

2017-12-27 Thread Sylwester Lachiewicz
Build fails with long directory name - also on windows.
Upgrade maven-surefire-plugin to 2.20.1 fixes test error.


śr., 27 gru 2017 o 08:49 użytkownik Plamen Totev 
napisał:

> And if this could help (I know it's obvious but may safe time) it
> looks the reason for the failing tests is the same. The following code
> fails with assertion error:
>
> final Manifest manifest = getJarFileManifest( jarFile );
> String classPath = manifest.getMainAttributes().getValue(
> Attributes.Name.CLASS_PATH );
> assertNotNull( classPath );
>
> The NullPointerExceptions from the rest of the tests are coming from
> the same expression (`manifest.getMainAttributes().getValue(
> "Class-Path" ).getBytes()`).
>
> On Wed, Dec 27, 2017 at 9:39 AM, Plamen Totev 
> wrote:
> > Hi,
> >
> > On Tue, Dec 26, 2017 at 9:01 PM, Karl Heinz Marbaise 
> wrote:
> >
> >> Is someone out there who can check the current state of maven-archiver
> git
> >> repo on Windows and can reproduce the issue ?
> >
> > I ran the build a couple of times(just in case) on Windows 10, Maven
> > 3.5.2, JDK 9.0.1 and everything is ok. And it looks like the build is
> > failing on Linux JDK 9 and Windows JDK 8 as well, so if there is a bug
> > (and not a problem with the build) then it is probably not a Windows
> > or JDK 9 related.
> >
> > Regards,
> > Plamen Totev
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>