[jira] (MDEP-109) Dependency plugin looses file permissions when unpacking or copying artifact items
[
https://jira.codehaus.org/browse/MDEP-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306401#comment-306401
]
Tim Moore commented on MDEP-109:
I think this is fixed in version 2.5.
Dependency plugin looses file permissions when unpacking or copying artifact
items
--
Key: MDEP-109
URL: https://jira.codehaus.org/browse/MDEP-109
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: copy, copy-dependencies, unpack, unpack-dependencies
Affects Versions: 2.0-alpha-4
Reporter: Vincent Massol
Assignee: Brian Fox
I have to add the following ugly config in my pom.xml to overcome this:
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseprepare-package/phase
goals
goalrun/goal
/goals
configuration
tasks
!-- Dependency plugin discards file permissions so we need
to set them back manually --
chmod
file=${project.build.directory}/dependency/bin/windres perm=ugo+rx/
chmod file=${project.build.directory}/dependency/bin/ld
perm=ugo+rx/
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5330) properties not substituted on dependency resolution
Alexander Kudrevatykh created MNG-5330: -- Summary: properties not substituted on dependency resolution Key: MNG-5330 URL: https://jira.codehaus.org/browse/MNG-5330 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.4, 3.0.3 Environment: Windows 7, jdk1.7.0_01 Reporter: Alexander Kudrevatykh Attachments: test.zip I have project dependency with classifier, setted by property. This property not substituted on dependency resolution. sample project attached. mvn clean install -Ptest2 fails with maven 3.0.4 and succeed with maven 2.2.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-109) Dependency plugin looses file permissions when unpacking or copying artifact items
[
https://jira.codehaus.org/browse/MDEP-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306415#comment-306415
]
Gili commented on MDEP-109:
---
Tim,
Last I checked bugs don't magically fix themselves ;)
Someone needs to confirm they can reproduce the bug before 2.5 but not after
it. For all we know, your testcase could be flawed in some way.
Dependency plugin looses file permissions when unpacking or copying artifact
items
--
Key: MDEP-109
URL: https://jira.codehaus.org/browse/MDEP-109
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: copy, copy-dependencies, unpack, unpack-dependencies
Affects Versions: 2.0-alpha-4
Reporter: Vincent Massol
Assignee: Brian Fox
I have to add the following ugly config in my pom.xml to overcome this:
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseprepare-package/phase
goals
goalrun/goal
/goals
configuration
tasks
!-- Dependency plugin discards file permissions so we need
to set them back manually --
chmod
file=${project.build.directory}/dependency/bin/windres perm=ugo+rx/
chmod file=${project.build.directory}/dependency/bin/ld
perm=ugo+rx/
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-904) Categorization of tests results in running first tests without categorization,then tests run based on category
Ronal Bashirov created SUREFIRE-904:
---
Summary: Categorization of tests results in running first tests
without categorization,then tests run based on category
Key: SUREFIRE-904
URL: https://jira.codehaus.org/browse/SUREFIRE-904
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.12.2
Environment: maven 3.0.4
junit 4.8.1
maven surefire pluign 2.12.2
Reporter: Ronal Bashirov
Attachments: mavenproject2.zip
I am separate my tests using junit categories.
So I have some test:
@Test
@Category(UnitTest.class)
public void testApp1() {
System.out.println( UnitTest );
assertTrue(true);
}
@Test
@Category(ComponentTest.class)
public void testApp2() {
System.out.println( ComponentTest );
assertTrue(true);
}
@Test
@Category(SystemTest.class)
public void testApp3() {
System.out.println( SystemTest );
assertTrue(true);
}
Then I am trying to run them separately
plugin
artifactIdmaven-surefire-plugin/artifactId
version2.12.2/version
executions
execution
idunit-tests/id
goals
goaltest/goal
/goals
configuration
groupscom.mycompany.mavenproject2.UnitTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/unit/reportsDirectory
/configuration
/execution
execution
idcomp-tests/id
goals
goaltest/goal
/goals
configuration
groupscom.mycompany.mavenproject2.ComponentTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/comp/reportsDirectory
/configuration
/execution
execution
idsys-tests/id
goals
goaltest/goal
/goals
configuration
groupscom.mycompany.mavenproject2.SystemTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/sys/reportsDirectory
/configuration
/execution
/executions
/plugin
As result I am getting
---
T E S T S
---
Running com.mycompany.mavenproject2.AppTest
UnitTest
ComponentTest
SystemTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
Results :
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
[surefire:test]
Surefire report directory:
C:\Users\mz\Documents\NetBeansProjects\mavenproject2\target\surefire-reports\unit
---
T E S T S
---
Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2,
useUnlimitedThreads=false
Running com.mycompany.mavenproject2.AppTest
UnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[surefire:test]
Surefire report directory:
C:\Users\mz\Documents\NetBeansProjects\mavenproject2\target\surefire-reports\comp
---
T E S T S
---
Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2,
useUnlimitedThreads=false
Running com.mycompany.mavenproject2.AppTest
ComponentTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[surefire:test]
Surefire report directory:
C:\Users\mz\Documents\NetBeansProjects\mavenproject2\target\surefire-reports\sys
---
T E S T S
---
Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2,
useUnlimitedThreads=false
Running com.mycompany.mavenproject2.AppTest
SystemTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
--
This message is automatically generated by JIRA.
If you think it was sent
[jira] (MASSEMBLY-624) Multiple attachments with reused assembly descriptor - classifier for attach should be configurable in maven-assembly-plugin execution configuration
Sven Ludwig created MASSEMBLY-624: - Summary: Multiple attachments with reused assembly descriptor - classifier for attach should be configurable in maven-assembly-plugin execution configuration Key: MASSEMBLY-624 URL: https://jira.codehaus.org/browse/MASSEMBLY-624 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Affects Versions: 2.3 Reporter: Sven Ludwig It should be possible to create multiple assembly products with different classifiers using only one assembly-descriptor. Currently, the configuration property classifier is deprecated (and apparently also not honored), and instead, the assembly ID is used as the classifier. I suggest to reactivate the classifier property in a way that it becomes possible to define the classifier within the configuration of an execution and thus multiple assembly products may be attached using only one reused assembly-descriptor. More about the problem: If there is more than one execution with attach true, there will be the warning message artifact 2already attached to project, ignoring duplicate. See: http://stackoverflow.com/questions/8734706/maven-assembly-plugin-uploading-the-right-zip-file Citation: Even if you have given the zips different finalName values, they still inherit the classifier from the ID in the assembly descriptor. http://stackoverflow.com/questions/1326527/maven-assembly-plugin-custom-jar-filenames (answer by Rich Seller, scroll down a bit) Note that it is not possible to have a variing assembly ID for one assembly-descriptor inside a pom.xml (e.g. it is not possibly to define the assembly ID as a property that has a different value for each execution). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-905) Surefore report plugin only executed tests once.Junit Categorization is not possibel
Ronal Bashirov created SUREFIRE-905:
---
Summary: Surefore report plugin only executed tests once.Junit
Categorization is not possibel
Key: SUREFIRE-905
URL: https://jira.codehaus.org/browse/SUREFIRE-905
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Report Plugin
Affects Versions: 2.12.2
Environment: maven 3.0.4
junit 4.8.1
Reporter: Ronal Bashirov
Attachments: mavenproject2.zip
When I am trying to run categorized junit tests ,
maven surefire pluing run only first group. All other groups are skipped.
pom.xml
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-report-plugin/artifactId
version2.12.2/version
reportSets
reportSet
idunit/id
configuration
groupscom.mycompany.mavenproject2.UnitTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/unit /reportsDirectory
outputNamesurefire-report-unit/outputName
reportNameSuffixUNIT/reportNameSuffix
/configuration
reports
reportreport/report
/reports
/reportSet
reportSet
idcomp/id
configuration
groupscom.mycompany.mavenproject2.ComponentTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/comp/reportsDirectory
reportNameSuffixCOMPONENT/reportNameSuffix
outputNamesurefire-report-comp/outputName
/configuration
reports
reportreport/report
/reports
/reportSet
reportSet
idsys/id
configuration
groupscom.mycompany.mavenproject2.SystemTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/sys/reportsDirectory
reportNameSuffixSYSTEM/reportNameSuffix
outputNamesurefire-report-sys/outputName
/configuration
reports
reportreport/report
/reports
/reportSet
/reportSets
/plugin
With output
T E S T S
---
Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2,
useUnlimitedThreads=false
Running com.mycompany.mavenproject2.AppTest
UnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[surefire:test]
Skipping execution of surefire because it has already been run for this
configuration
[surefire:test]
Skipping execution of surefire because it has already been run for this
configuration
[surefire:test]
Skipping execution of surefire because it has already been run for this
configuration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-109) Dependency plugin looses file permissions when unpacking or copying artifact items
[
https://jira.codehaus.org/browse/MDEP-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306421#comment-306421
]
Tim Moore commented on MDEP-109:
It isn't magical, the dependency on plexus-archiver was updated to a version
that runs chmod on each file it unpacks. I discovered this because it caused a
massive performance regression in our builds! (I'll file a bug report with a
patch for that on Monday.)
I don't have an actual test case, I was more intending to prompt the original
reporter to give it a try with 2.5.
Dependency plugin looses file permissions when unpacking or copying artifact
items
--
Key: MDEP-109
URL: https://jira.codehaus.org/browse/MDEP-109
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: copy, copy-dependencies, unpack, unpack-dependencies
Affects Versions: 2.0-alpha-4
Reporter: Vincent Massol
Assignee: Brian Fox
I have to add the following ugly config in my pom.xml to overcome this:
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseprepare-package/phase
goals
goalrun/goal
/goals
configuration
tasks
!-- Dependency plugin discards file permissions so we need
to set them back manually --
chmod
file=${project.build.directory}/dependency/bin/windres perm=ugo+rx/
chmod file=${project.build.directory}/dependency/bin/ld
perm=ugo+rx/
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-280) Big performance hit in overlay
[
https://jira.codehaus.org/browse/MWAR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306423#comment-306423
]
Simone Bordet commented on MWAR-280:
-
You can build this: https://github.com/cometd/cometd-tutorials-skeleton, but it
happens with any WAR.
Big performance hit in overlay
--
Key: MWAR-280
URL: https://jira.codehaus.org/browse/MWAR-280
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Components: overlay
Affects Versions: 2.2
Reporter: Simone Bordet
Here is the output of version 2.1.1 of the maven war plugin when overlaying
org.cometd.javascript:cometd-javascript-dojo:
{code}
[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ tutorials-skeleton ---
[INFO] Packaging webapp
[INFO] Assembling webapp [tutorials-skeleton] in
[/home/simon/opensource/cometd/tutorials-skeleton/target/tutorials-skeleton-1.0.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources
[/home/simon/opensource/cometd/tutorials-skeleton/src/main/webapp]
[INFO] Processing overlay [ id org.cometd.javascript:cometd-javascript-dojo]
[INFO] Webapp assembled in [7026 msecs]
{code}
Note how it took 7026 ms.
This is the output for the same project, but using version 2.2 of the maven
war plugin:
{code}
[INFO] --- maven-war-plugin:2.2:war (default-war) @ tutorials-skeleton ---
[INFO] Packaging webapp
[INFO] Assembling webapp [tutorials-skeleton] in
[/home/simon/opensource/cometd/tutorials-skeleton/target/tutorials-skeleton-1.0.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources
[/home/simon/opensource/cometd/tutorials-skeleton/src/main/webapp]
[INFO] Processing overlay [ id org.cometd.javascript:cometd-javascript-dojo]
[INFO] Webapp assembled in [24151 msecs]
{code}
Note how it took 24151 ms, i.e. a 3-4 times performance hit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-906) Sometimes get NullPointerException in forked process
Christopher Mosher created SUREFIRE-906: --- Summary: Sometimes get NullPointerException in forked process Key: SUREFIRE-906 URL: https://jira.codehaus.org/browse/SUREFIRE-906 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.13.0 Environment: Arch linux Reporter: Christopher Mosher (This is using the latest 2.13-SNAPSHOT) Using forkMode=perthread, the child processes sometimes abort with this exception: java.lang.NullPointerException at java.io.File.init(File.java:251) at org.apache.maven.surefire.booter.BooterDeserializer.deserialize(BooterDeserializer.java:61) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:63) It only happens sometimes. Using -X keeps the temp files, and looking at the file that's supposed to pass the properties, I see that the file is truncated midway, causing the exception. Possibly the parent process needs to *flush* the file after it writes to it before is closes it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-906) Sometimes get NullPointerException in forked process
[ https://jira.codehaus.org/browse/SUREFIRE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306442#comment-306442 ] Kristian Rosenvold commented on SUREFIRE-906: - Interesting how the flush method on FileOutputStream does nothign Sometimes get NullPointerException in forked process Key: SUREFIRE-906 URL: https://jira.codehaus.org/browse/SUREFIRE-906 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.13.0 Environment: Arch linux Reporter: Christopher Mosher (This is using the latest 2.13-SNAPSHOT) Using forkMode=perthread, the child processes sometimes abort with this exception: java.lang.NullPointerException at java.io.File.init(File.java:251) at org.apache.maven.surefire.booter.BooterDeserializer.deserialize(BooterDeserializer.java:61) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:63) It only happens sometimes. Using -X keeps the temp files, and looking at the file that's supposed to pass the properties, I see that the file is truncated midway, causing the exception. Possibly the parent process needs to *flush* the file after it writes to it before is closes it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-906) Sometimes get NullPointerException in forked process
[ https://jira.codehaus.org/browse/SUREFIRE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306445#comment-306445 ] Christopher Mosher commented on SUREFIRE-906: - Maybe out.getFD().sync() ? Sometimes get NullPointerException in forked process Key: SUREFIRE-906 URL: https://jira.codehaus.org/browse/SUREFIRE-906 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.13.0 Environment: Arch linux Reporter: Christopher Mosher (This is using the latest 2.13-SNAPSHOT) Using forkMode=perthread, the child processes sometimes abort with this exception: java.lang.NullPointerException at java.io.File.init(File.java:251) at org.apache.maven.surefire.booter.BooterDeserializer.deserialize(BooterDeserializer.java:61) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:63) It only happens sometimes. Using -X keeps the temp files, and looking at the file that's supposed to pass the properties, I see that the file is truncated midway, causing the exception. Possibly the parent process needs to *flush* the file after it writes to it before is closes it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-906) Sometimes get NullPointerException in forked process
[ https://jira.codehaus.org/browse/SUREFIRE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Mosher updated SUREFIRE-906: Attachment: SUREFIRE-906-0001.patch I was able to fix it with the attached patch. It did not have to do with the output files. Instead it was a non-thread-safe issue with the properties object. Multiple threads in the parent (forking) process were accessing the same properties... the clone() call that was there must not have been enough to ensure thread safety. Sometimes get NullPointerException in forked process Key: SUREFIRE-906 URL: https://jira.codehaus.org/browse/SUREFIRE-906 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.13.0 Environment: Arch linux Reporter: Christopher Mosher Attachments: SUREFIRE-906-0001.patch (This is using the latest 2.13-SNAPSHOT) Using forkMode=perthread, the child processes sometimes abort with this exception: java.lang.NullPointerException at java.io.File.init(File.java:251) at org.apache.maven.surefire.booter.BooterDeserializer.deserialize(BooterDeserializer.java:61) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:63) It only happens sometimes. Using -X keeps the temp files, and looking at the file that's supposed to pass the properties, I see that the file is truncated midway, causing the exception. Possibly the parent process needs to *flush* the file after it writes to it before is closes it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-906) Sometimes get NullPointerException in forked process
[ https://jira.codehaus.org/browse/SUREFIRE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-906. --- Resolution: Fixed Fix Version/s: 2.13.0 Assignee: Kristian Rosenvold Fixed with a slightly different patch in r1374556, thanks for testing the solution. Sometimes get NullPointerException in forked process Key: SUREFIRE-906 URL: https://jira.codehaus.org/browse/SUREFIRE-906 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.13.0 Environment: Arch linux Reporter: Christopher Mosher Assignee: Kristian Rosenvold Fix For: 2.13.0 Attachments: SUREFIRE-906-0001.patch (This is using the latest 2.13-SNAPSHOT) Using forkMode=perthread, the child processes sometimes abort with this exception: java.lang.NullPointerException at java.io.File.init(File.java:251) at org.apache.maven.surefire.booter.BooterDeserializer.deserialize(BooterDeserializer.java:61) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:63) It only happens sometimes. Using -X keeps the temp files, and looking at the file that's supposed to pass the properties, I see that the file is truncated midway, causing the exception. Possibly the parent process needs to *flush* the file after it writes to it before is closes it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-904) Categorization of tests results in running first tests without categorization,then tests run based on category
[
https://jira.codehaus.org/browse/SUREFIRE-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306465#comment-306465
]
Kristian Rosenvold commented on SUREFIRE-904:
-
You configured the plugin to run 4 times (default + 3 executions), and it does
just that. Since you did not specify any groups for the default execution it
runs everything. Exactly what is the proplem here?
Categorization of tests results in running first tests without
categorization,then tests run based on category
--
Key: SUREFIRE-904
URL: https://jira.codehaus.org/browse/SUREFIRE-904
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.12.2
Environment: maven 3.0.4
junit 4.8.1
maven surefire pluign 2.12.2
Reporter: Ronal Bashirov
Attachments: mavenproject2.zip
I am separate my tests using junit categories.
So I have some test:
@Test
@Category(UnitTest.class)
public void testApp1() {
System.out.println( UnitTest );
assertTrue(true);
}
@Test
@Category(ComponentTest.class)
public void testApp2() {
System.out.println( ComponentTest );
assertTrue(true);
}
@Test
@Category(SystemTest.class)
public void testApp3() {
System.out.println( SystemTest );
assertTrue(true);
}
Then I am trying to run them separately
plugin
artifactIdmaven-surefire-plugin/artifactId
version2.12.2/version
executions
execution
idunit-tests/id
goals
goaltest/goal
/goals
configuration
groupscom.mycompany.mavenproject2.UnitTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/unit/reportsDirectory
/configuration
/execution
execution
idcomp-tests/id
goals
goaltest/goal
/goals
configuration
groupscom.mycompany.mavenproject2.ComponentTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/comp/reportsDirectory
/configuration
/execution
execution
idsys-tests/id
goals
goaltest/goal
/goals
configuration
groupscom.mycompany.mavenproject2.SystemTest/groups
reportsDirectory
${project.build.directory}/surefire-reports/sys/reportsDirectory
/configuration
/execution
/executions
/plugin
As result I am getting
---
T E S T S
---
Running com.mycompany.mavenproject2.AppTest
UnitTest
ComponentTest
SystemTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
Results :
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
[surefire:test]
Surefire report directory:
C:\Users\mz\Documents\NetBeansProjects\mavenproject2\target\surefire-reports\unit
---
T E S T S
---
Concurrency config is parallel='none', perCoreThreadCount=true,
threadCount=2, useUnlimitedThreads=false
Running com.mycompany.mavenproject2.AppTest
UnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[surefire:test]
Surefire report directory:
C:\Users\mz\Documents\NetBeansProjects\mavenproject2\target\surefire-reports\comp
---
T E S T S
---
Concurrency config is parallel='none', perCoreThreadCount=true,
threadCount=2, useUnlimitedThreads=false
Running com.mycompany.mavenproject2.AppTest
ComponentTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[surefire:test]
Surefire report
[jira] (MSOURCES-62) An API incompatibility was encountered.
Christian Schulte created MSOURCES-62:
-
Summary: An API incompatibility was encountered.
Key: MSOURCES-62
URL: https://jira.codehaus.org/browse/MSOURCES-62
Project: Maven 2.x Source Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Reporter: Christian Schulte
Priority: Blocker
The plugin fails when using custom 'manifestEntries' throwing the following
exception:
{code}
[...]
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
at
org.apache.maven.archiver.MavenArchiver.getManifest(MavenArchiver.java:102)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:513)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:288)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:240)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:209)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-62) An API incompatibility was encountered.
[
https://jira.codehaus.org/browse/MSOURCES-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MSOURCES-62:
--
Attachment: MSOURCES-62.zip
Example project demonstrating the issue.
An API incompatibility was encountered.
---
Key: MSOURCES-62
URL: https://jira.codehaus.org/browse/MSOURCES-62
Project: Maven 2.x Source Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Reporter: Christian Schulte
Priority: Blocker
Attachments: MSOURCES-62.zip
The plugin fails when using custom 'manifestEntries' throwing the following
exception:
{code}
[...]
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
at
org.apache.maven.archiver.MavenArchiver.getManifest(MavenArchiver.java:102)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:513)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:288)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:240)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:209)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-62) An API incompatibility was encountered.
[
https://jira.codehaus.org/browse/MSOURCES-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306467#comment-306467
]
Christian Schulte commented on MSOURCES-62:
---
{code}
Script started on Sat Aug 18 00:21:29 2012
$ mvn -e package
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building 62 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 62 ---
[debug] execute contextualize
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 62 ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @
62 ---
[debug] execute contextualize
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory /tmp/MSOURCES-62/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 62
---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ 62 ---
[INFO] No tests to run.
[INFO] Surefire report directory: /tmp/MSOURCES-62/target/surefire-reports
---
T E S T S
---
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ 62 ---
[INFO] Building jar: /tmp/MSOURCES-62/target/62-1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-source-plugin:2.2:jar-no-fork (default) @ 62 ---
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.051s
[INFO] Finished at: Sat Aug 18 00:21:43 CEST 2012
[INFO] Final Memory: 6M/15M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-source-plugin:2.2:jar-no-fork (default) on
project 62: Execution default of goal
org.apache.maven.plugins:maven-source-plugin:2.2:jar-no-fork failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-source-plugin:2.2:jar-no-fork:
java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
[ERROR] -
[ERROR] realm =pluginorg.apache.maven.plugins:maven-source-plugin:2.2
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/home/schulte/.m2/central/org/apache/maven/plugins/maven-source-plugin/2.2/maven-source-plugin-2.2.jar
[ERROR] urls[1] =
file:/home/schulte/.m2/central/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[2] =
file:/home/schulte/.m2/central/org/apache/maven/maven-archiver/2.4.1/maven-archiver-2.4.1.jar
[ERROR] urls[3] =
file:/home/schulte/.m2/central/org/codehaus/plexus/plexus-interpolation/1.13/plexus-interpolation-1.13.jar
[ERROR] urls[4] =
file:/home/schulte/.m2/central/org/codehaus/plexus/plexus-archiver/2.1.2/plexus-archiver-2.1.2.jar
[ERROR] urls[5] =
file:/home/schulte/.m2/central/org/codehaus/plexus/plexus-io/2.0.4/plexus-io-2.0.4.jar
[ERROR] urls[6] =
file:/home/schulte/.m2/central/org/codehaus/plexus/plexus-utils/3.0.1/plexus-utils-3.0.1.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -
[ERROR] - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-source-plugin:2.2:jar-no-fork (default) on
project 62: Execution default of goal
org.apache.maven.plugins:maven-source-plugin:2.2:jar-no-fork failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-source-plugin:2.2:jar-no-fork:
java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
-
realm =pluginorg.apache.maven.plugins:maven-source-plugin:2.2
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
urls[0] =
file:/home/schulte/.m2/central/org/apache/maven/plugins/maven-source-plugin/2.2/maven-source-plugin-2.2.jar
urls[1] = file:/home/schulte/.m2/central/junit/junit/3.8.1/junit-3.8.1.jar
urls[2]
[jira] (SUREFIRE-906) Sometimes get NullPointerException in forked process
[ https://jira.codehaus.org/browse/SUREFIRE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306470#comment-306470 ] Christopher Mosher commented on SUREFIRE-906: - Your fix is confirmed. Thanks for your quick response, Kristian. Note that the revision is actually r1374456. Sometimes get NullPointerException in forked process Key: SUREFIRE-906 URL: https://jira.codehaus.org/browse/SUREFIRE-906 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.13.0 Environment: Arch linux Reporter: Christopher Mosher Assignee: Kristian Rosenvold Fix For: 2.13.0 Attachments: SUREFIRE-906-0001.patch (This is using the latest 2.13-SNAPSHOT) Using forkMode=perthread, the child processes sometimes abort with this exception: java.lang.NullPointerException at java.io.File.init(File.java:251) at org.apache.maven.surefire.booter.BooterDeserializer.deserialize(BooterDeserializer.java:61) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:63) It only happens sometimes. Using -X keeps the temp files, and looking at the file that's supposed to pass the properties, I see that the file is truncated midway, causing the exception. Possibly the parent process needs to *flush* the file after it writes to it before is closes it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
