[jira] (SUREFIRE-1080) Use parallel and fork together run some tests multiple times
[ https://jira.codehaus.org/browse/SUREFIRE-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352072#comment-352072 ] Tibor Digana commented on SUREFIRE-1080: @Qingzhou Luo It works if you set reuseForks=false which makes more sense to me in parallel exec of processes. Anyway it is a bug. I will try to fix it in 2.18. Use parallel and fork together run some tests multiple times Key: SUREFIRE-1080 URL: https://jira.codehaus.org/browse/SUREFIRE-1080 Project: Maven Surefire Issue Type: Bug Environment: Apache Maven 3.2.2-SNAPSHOT Surefire 2.18-SNAPSHOT JUnit 4.11 Reporter: Qingzhou Luo Attachments: test.tgz There are 9 tests in total in the attached project, and mvn test will show 9 tests run. When I use the command mvn test -Dparallel=classes -DforkCount=2 -DuseUnlimitedThreads=true, it shows 13 tests run (and sometimes 16), and some tests are run more than once. If I remove forkCount, or parallel, everything will be fine. But it is problematic when combining together. Apache Maven 3.2.2-SNAPSHOT Surefire 2.18-SNAPSHOT JUnit 4.11 Thanks! -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-38) removeExistingSignatures recompressing all files (major problem with android)
Yannick Menager created MJARSIGNER-38: - Summary: removeExistingSignatures recompressing all files (major problem with android) Key: MJARSIGNER-38 URL: https://jira.codehaus.org/browse/MJARSIGNER-38 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.2 Environment: maven 3 Reporter: Yannick Menager When removeExistingSignatures is set to true, it seem to recompress all file. So if the flag is set to false, i get 7532 Stored 7532 0% 08-31-14 16:23 bbd535df res/drawable-xxhdpi/connect.png If it is set to true, i get 2954 Defl:N 2959 -0% 08-31-14 16:24 d8342319 res/drawable-hdpi/connect.png Defl:N meaning that it's compressed, and Stored that it isn't. This is a MAJOR problem for android apps that use it (and I wouldn't be surprised if nowadays android devs are the primary users of this plugin), since certain resources CAN'T be compressed, or the app will break totally -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-38) removeExistingSignatures recompressing all files (major problem with android)
[ https://jira.codehaus.org/browse/MJARSIGNER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yannick Menager updated MJARSIGNER-38: -- Description: When removeExistingSignatures is set to true, it seem to recompress all file. So if the flag is set to false, i get 7532 Stored 7532 0% 08-31-14 16:23 bbd535df res/drawable-xxhdpi/connect.png If it is set to true, i get 2954 Defl:N 2959 -0% 08-31-14 16:24 d8342319 res/drawable-hdpi/connect.png Defl:N meaning that it's compressed, and Stored that it isn't. This is a MAJOR problem for android apps that use it (and I wouldn't be surprised if nowadays android devs are the primary users of this plugin), since certain resources CAN'T be compressed, or the app will break was: When removeExistingSignatures is set to true, it seem to recompress all file. So if the flag is set to false, i get 7532 Stored 7532 0% 08-31-14 16:23 bbd535df res/drawable-xxhdpi/connect.png If it is set to true, i get 2954 Defl:N 2959 -0% 08-31-14 16:24 d8342319 res/drawable-hdpi/connect.png Defl:N meaning that it's compressed, and Stored that it isn't. This is a MAJOR problem for android apps that use it (and I wouldn't be surprised if nowadays android devs are the primary users of this plugin), since certain resources CAN'T be compressed, or the app will break totally removeExistingSignatures recompressing all files (major problem with android) - Key: MJARSIGNER-38 URL: https://jira.codehaus.org/browse/MJARSIGNER-38 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.2 Environment: maven 3 Reporter: Yannick Menager When removeExistingSignatures is set to true, it seem to recompress all file. So if the flag is set to false, i get 7532 Stored 7532 0% 08-31-14 16:23 bbd535df res/drawable-xxhdpi/connect.png If it is set to true, i get 2954 Defl:N 2959 -0% 08-31-14 16:24 d8342319 res/drawable-hdpi/connect.png Defl:N meaning that it's compressed, and Stored that it isn't. This is a MAJOR problem for android apps that use it (and I wouldn't be surprised if nowadays android devs are the primary users of this plugin), since certain resources CAN'T be compressed, or the app will break -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-709) When assembling a zip on windows duplicate files are added to the assembly
[
https://jira.codehaus.org/browse/MASSEMBLY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352077#comment-352077
]
Karl-Heinz Marbaise commented on MASSEMBLY-709:
---
I have to acknowledge the wrong behaviour with version 2.4.1 as well.
When assembling a zip on windows duplicate files are added to the assembly
--
Key: MASSEMBLY-709
URL: https://jira.codehaus.org/browse/MASSEMBLY-709
Project: Maven Assembly Plugin
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.4
Environment: Apache Maven 3.0.5
(r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 05:51:28-0800)
Maven home: C:\bin\apache-maven-3.0.5
Java version: 1.7.0_60, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_60\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows server 2008 r2, version: 6.1, arch: amd64, family:
windows
Reporter: Jason Lemay
Attachments: sample.zip
When assembling a zip where duplicate files are copied to the output
directory the default behavior is for the first file to copy and the
remaining ones to be skipped. When building a project on windows this is not
the behavior. On Windows all the duplicate files are added to the final zip
assembly.
This was tested on OSX, CentOS, and Windows Server 2009 R2.
Using OSX with these settings:
{code}
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
05:51:28-0800)
Maven home: /usr/local/Cellar/maven30/3.0.5/libexec
Java version: 1.7.0_60, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.4, arch: x86_64, family: mac
{code}
Running the mvn build as such:
{code}
mvn -X clean install
{code}
You end up with this logged to the console:
{code}
[INFO] Building zip: /Users/jasonl/Desktop/sample/target/sample.zip
[DEBUG] adding directory sample/
[DEBUG] adding directory sample/conf/
[DEBUG] adding entry sample/conf/ConfFile.txt
[DEBUG] adding entry sample/file.txt
[DEBUG] sample/conf/ConfFile.txt already added, skipping
{code}
When the final zip is examined there are no duplicate files. The plugin
worked as intended. The same results were obtained in the CentOS test.
The problem arises when you build on windows.
Building with these settings:
{code}
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
05:51:28-0800)
Maven home: C:\bin\apache-maven-3.0.5
Java version: 1.7.0_60, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_60\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows server 2008 r2, version: 6.1, arch: amd64, family:
windows
{code}
And running the same mvn command:
{code}
mvn -X clean install
{code}
The following is output to the console:
{code}
[INFO] Building zip: C:\Users\Administrator\Desktop\sample\target\sample.zip
[DEBUG] adding directory sample/
[DEBUG] adding directory sample/conf/
[DEBUG] adding entry sample/conf/ConfFile.txt
[DEBUG] adding entry sample/file.txt
[DEBUG] adding entry sample/conf/ConfFile.txt
{code}
As you can see the assembly did not skip the second ConfFile.txt addition.
When the final zip assembly is examined there is infact 2 ConfFile.txt files
under the conf directory.
Attached is the sample I used.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-234) group rules by category
[ https://jira.codehaus.org/browse/MCHECKSTYLE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MCHECKSTYLE-234. - Resolution: Fixed Assignee: Herve Boutemy done in [r1621644|http://svn.apache.org/r1621644] group rules by category --- Key: MCHECKSTYLE-234 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-234 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.12.1 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: 2.13 [Checkstyle site|http://checkstyle.sourceforge.net] has a nice grouping of rules into categories: * Standard Checks ** Annotations ** Block Checks ** Class Design ** Coding ** Duplicate Code ** Headers ** Imports ** Javadoc Comments ** Metrics ** Miscellaneous ** Modifiers ** Naming Conventions ** Regexp ** Size Violations ** Whitespace Having these categories in the report, when listing rules, would give useful organization -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-13) signing in multi-module project fails on windows
[
https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352083#comment-352083
]
Jason Pyeron commented on MJARSIGNER-13:
Link to FAQ: http://maven.apache.org/plugins/maven-jarsigner-plugin/faq.html
signing in multi-module project fails on windows
Key: MJARSIGNER-13
URL: https://jira.codehaus.org/browse/MJARSIGNER-13
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows XP, android sdk
Reporter: Anna Gadomska
Assignee: Tony Chemit
Fix For: 1.3
Attachments: pom.xml
I got multi-module (6 modules) android project with .pom file and sign
profile defined. When I execute with 'sign' profile:
- in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
(mv goal -rf) it signs another 3 modules and fails again. The reason for
failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
failed.
- in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
error code 1
However, I tried the same .pom - everything works perfectly in Linux
(Ubuntu).
I was afraid that it might be the issue with spaces, so I hardcoded the paths
- the error I got from maven than was:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
MyProject: Failed executing 'cmd.exe /X /C
C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
C:\tmp\debug.keystore -storepass '*' -keypass '*' xxx.jar
'*'debugkey' - exitcode 1 - [Help 1]
{noformat}
Attaching pom file which I am using.
Please help?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJARSIGNER-13) signing in multi-module project fails on windows
[
https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352084#comment-352084
]
Jason Pyeron commented on MJARSIGNER-13:
E.g.
{code}
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jarsigner-plugin/artifactId
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
/plugin
/plugins
/build
{code}
signing in multi-module project fails on windows
Key: MJARSIGNER-13
URL: https://jira.codehaus.org/browse/MJARSIGNER-13
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows XP, android sdk
Reporter: Anna Gadomska
Assignee: Tony Chemit
Fix For: 1.3
Attachments: pom.xml
I got multi-module (6 modules) android project with .pom file and sign
profile defined. When I execute with 'sign' profile:
- in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
(mv goal -rf) it signs another 3 modules and fails again. The reason for
failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
failed.
- in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
error code 1
However, I tried the same .pom - everything works perfectly in Linux
(Ubuntu).
I was afraid that it might be the issue with spaces, so I hardcoded the paths
- the error I got from maven than was:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
MyProject: Failed executing 'cmd.exe /X /C
C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
C:\tmp\debug.keystore -storepass '*' -keypass '*' xxx.jar
'*'debugkey' - exitcode 1 - [Help 1]
{noformat}
Attaching pom file which I am using.
Please help?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
