[jira] (SUREFIRE-1007) Inconsisten encoding with large standard output
[ https://jira.codehaus.org/browse/SUREFIRE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331209#comment-331209 ] Yves Langisch commented on SUREFIRE-1007: - Just did some testing with 2.16 and 2.17-SNAPSHOT. They show the same behavior. The switch of the encoding in the middle of the output seems to be fixed :). But as a new behavior I noticed that the file.encoding property is completely ignored. The output in the XML is always UTF-8. With versions 2.16 that property was honored. What's the correct behavior? Inconsisten encoding with large standard output --- Key: SUREFIRE-1007 URL: https://jira.codehaus.org/browse/SUREFIRE-1007 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin, xml generation Affects Versions: 2.14.1, 2.15 Reporter: Yves Langisch Attachments: ibm-jdk7.log, ora-jdk7.log, surefire-encoding-test.zip, TEST-net.test.surefireencodingtest.EncodingTest.xml When having a lot of standard output in a failing test, the encoding of the resulting surefire-report XML is not consistent. The attached project shows that the encoding in 'TEST-net.test.surefireencodingtest.EncodingTest.xml' in the element system-out suddenly switches from UTF-8 to ISO-8859-1. Any workaround is highly appreciated... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1007) Inconsisten encoding with large standard output
[ https://jira.codehaus.org/browse/SUREFIRE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331210#comment-331210 ] Kristian Rosenvold commented on SUREFIRE-1007: -- The xml file should always be UTF-8 (regardless of file.encoding), so previous versions were buggy. The txt file should respect file.encoding. Inconsisten encoding with large standard output --- Key: SUREFIRE-1007 URL: https://jira.codehaus.org/browse/SUREFIRE-1007 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin, xml generation Affects Versions: 2.14.1, 2.15 Reporter: Yves Langisch Attachments: ibm-jdk7.log, ora-jdk7.log, surefire-encoding-test.zip, TEST-net.test.surefireencodingtest.EncodingTest.xml When having a lot of standard output in a failing test, the encoding of the resulting surefire-report XML is not consistent. The attached project shows that the encoding in 'TEST-net.test.surefireencodingtest.EncodingTest.xml' in the element system-out suddenly switches from UTF-8 to ISO-8859-1. Any workaround is highly appreciated... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1007) Inconsisten encoding with large standard output
[
https://jira.codehaus.org/browse/SUREFIRE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331211#comment-331211
]
Andreas Gudian commented on SUREFIRE-1007:
--
The correct behavior is UTF-8 in the XML file (as stated in the processor
directive in the first line of the file). The output file with stdout and
stderr of the test should be in {{file.encoding}}.
Inconsisten encoding with large standard output
---
Key: SUREFIRE-1007
URL: https://jira.codehaus.org/browse/SUREFIRE-1007
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Report Plugin, xml generation
Affects Versions: 2.14.1, 2.15
Reporter: Yves Langisch
Attachments: ibm-jdk7.log, ora-jdk7.log, surefire-encoding-test.zip,
TEST-net.test.surefireencodingtest.EncodingTest.xml
When having a lot of standard output in a failing test, the encoding of the
resulting surefire-report XML is not consistent. The attached project shows
that the encoding in 'TEST-net.test.surefireencodingtest.EncodingTest.xml' in
the element system-out suddenly switches from UTF-8 to ISO-8859-1.
Any workaround is highly appreciated...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1007) Inconsisten encoding with large standard output
[ https://jira.codehaus.org/browse/SUREFIRE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331212#comment-331212 ] Andreas Gudian commented on SUREFIRE-1007: -- Kristian was faster ;). @Yves: I guess we can close this issue now, right? Inconsisten encoding with large standard output --- Key: SUREFIRE-1007 URL: https://jira.codehaus.org/browse/SUREFIRE-1007 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin, xml generation Affects Versions: 2.14.1, 2.15 Reporter: Yves Langisch Attachments: ibm-jdk7.log, ora-jdk7.log, surefire-encoding-test.zip, TEST-net.test.surefireencodingtest.EncodingTest.xml When having a lot of standard output in a failing test, the encoding of the resulting surefire-report XML is not consistent. The attached project shows that the encoding in 'TEST-net.test.surefireencodingtest.EncodingTest.xml' in the element system-out suddenly switches from UTF-8 to ISO-8859-1. Any workaround is highly appreciated... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1007) Inconsisten encoding with large standard output
[ https://jira.codehaus.org/browse/SUREFIRE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331213#comment-331213 ] Yves Langisch commented on SUREFIRE-1007: - Yes, you can close the issue. Thanks! Inconsisten encoding with large standard output --- Key: SUREFIRE-1007 URL: https://jira.codehaus.org/browse/SUREFIRE-1007 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin, xml generation Affects Versions: 2.14.1, 2.15 Reporter: Yves Langisch Attachments: ibm-jdk7.log, ora-jdk7.log, surefire-encoding-test.zip, TEST-net.test.surefireencodingtest.EncodingTest.xml When having a lot of standard output in a failing test, the encoding of the resulting surefire-report XML is not consistent. The attached project shows that the encoding in 'TEST-net.test.surefireencodingtest.EncodingTest.xml' in the element system-out suddenly switches from UTF-8 to ISO-8859-1. Any workaround is highly appreciated... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1007) Inconsisten encoding with large standard output
[ https://jira.codehaus.org/browse/SUREFIRE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-1007: Assignee: Andreas Gudian Inconsisten encoding with large standard output --- Key: SUREFIRE-1007 URL: https://jira.codehaus.org/browse/SUREFIRE-1007 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin, xml generation Affects Versions: 2.14.1, 2.15 Reporter: Yves Langisch Assignee: Andreas Gudian Attachments: ibm-jdk7.log, ora-jdk7.log, surefire-encoding-test.zip, TEST-net.test.surefireencodingtest.EncodingTest.xml When having a lot of standard output in a failing test, the encoding of the resulting surefire-report XML is not consistent. The attached project shows that the encoding in 'TEST-net.test.surefireencodingtest.EncodingTest.xml' in the element system-out suddenly switches from UTF-8 to ISO-8859-1. Any workaround is highly appreciated... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1007) Inconsisten encoding with large standard output
[ https://jira.codehaus.org/browse/SUREFIRE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1007. Resolution: Fixed Fix Version/s: 2.16 Inconsisten encoding with large standard output --- Key: SUREFIRE-1007 URL: https://jira.codehaus.org/browse/SUREFIRE-1007 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin, xml generation Affects Versions: 2.14.1, 2.15 Reporter: Yves Langisch Assignee: Andreas Gudian Fix For: 2.16 Attachments: ibm-jdk7.log, ora-jdk7.log, surefire-encoding-test.zip, TEST-net.test.surefireencodingtest.EncodingTest.xml When having a lot of standard output in a failing test, the encoding of the resulting surefire-report XML is not consistent. The attached project shows that the encoding in 'TEST-net.test.surefireencodingtest.EncodingTest.xml' in the element system-out suddenly switches from UTF-8 to ISO-8859-1. Any workaround is highly appreciated... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-304) WAR plugin ignores attached artifacts from previous plugins
[
https://jira.codehaus.org/browse/MWAR-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331133#comment-331133
]
Jörg Schaible edited comment on MWAR-304 at 8/21/13 2:18 AM:
-
Attach means that the resulting artifact is an additional project result and
will be installed/deployed to the repository on its own. It is certainly not
meant to be included automatically into the main artifact. Such a behavior
would break quite a lot of existing projects.
If you want to add it to the war, simply set the proper target directory for
this attached artifact (into
{noformat}${project.build.directory}/${project.build.finalName}/WEB-INF/lib{noformat}).
was (Author: joehni):
Attach means that the resulting artifact is an additional project result
and will be installed/deployed to the repository on its own. It is certainly
not meant to be included automatically into the main artifact. Such a behavior
would break quite a lot of existing projects.
If you want to add it to the war, simply set the proper target directory for
this attached artifact (into
${project.build.directory}/${project.build.finalName}/WEB-INF/lib).
WAR plugin ignores attached artifacts from previous plugins
---
Key: MWAR-304
URL: https://jira.codehaus.org/browse/MWAR-304
Project: Maven WAR Plugin
Issue Type: Bug
Components: overlay
Affects Versions: 2.4
Environment: any
Reporter: Richard Sand
If my maven project includes a plugin that attaches an artifact to the
project, the war plugin will not process the artifact for inclusion in the
results
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-304) WAR plugin ignores attached artifacts from previous plugins
[ https://jira.codehaus.org/browse/MWAR-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331217#comment-331217 ] Jörg Schaible commented on MWAR-304: Well, the concept of attached artifacts is global, you can have those in each project. Therefore it is at least for me out of scope to have it automatically included. Additionally you would then have to offer similar functionality for other project types (ear, zip, ...) and what about jar if e.g. the attached artifact is a text file? IMHO the different concerns should stay separated :) WAR plugin ignores attached artifacts from previous plugins --- Key: MWAR-304 URL: https://jira.codehaus.org/browse/MWAR-304 Project: Maven WAR Plugin Issue Type: Bug Components: overlay Affects Versions: 2.4 Environment: any Reporter: Richard Sand If my maven project includes a plugin that attaches an artifact to the project, the war plugin will not process the artifact for inclusion in the results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-212) maven-compiler-plugin:3.1:testCompile throws compilation error for class org.junit.Assume
Adina Moldovan created MCOMPILER-212:
Summary: maven-compiler-plugin:3.1:testCompile throws compilation
error for class org.junit.Assume
Key: MCOMPILER-212
URL: https://jira.codehaus.org/browse/MCOMPILER-212
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /usr/share/maven
Java version: 1.6.0_45, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac
Reporter: Adina Moldovan
Steps:
1. Write the following class in your tests package:
package com.adinnaplus.automation.tests;
import org.junit.Assume;
import org.junit.Test;
public class MyTest {
@Test
public void failingTest() {
boolean condition = false;
Assume.assumeFalse(condition);
// test follows here
}
}
2. Go to terminal and run mvn clean test in the path where your project's pom
is
Expected: compilation successful (junit Assume is a very important feature for
our project)
Actual: $ mvn clean test
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Adinnaplus BDD Automation 1.1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
AdinnaplusAutomation ---
[INFO] Deleting
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target
[INFO]
[INFO] --- xmlbeans-maven-plugin:2.3.3:xmlbeans (default) @
AdinnaplusAutomation ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
AdinnaplusAutomation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO] Copying 37 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
AdinnaplusAutomation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 53 source files to
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target/classes
[WARNING] Note:
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/main/java/com/tve/automation/services/helpers/CredentialLoader.java
uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @
AdinnaplusAutomation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
AdinnaplusAutomation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 87 source files to
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target/test-classes
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING] Note:
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/steps/AssertionSteps.java
uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 2 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/tests/MyTest.java:[11,15]
cannot find symbol
symbol : method assumeFalse(boolean)
location: class org.junit.Assume
[INFO] 1 error
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 58.111s
[INFO] Finished at: Wed Aug 21 10:45:12 EEST 2013
[INFO] Final Memory: 22M/81M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile
(default-testCompile) on project AdinnaplusAutomation: Compilation failure
[ERROR]
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/tests/MyTest.java:[11,15]
cannot find symbol
[ERROR] symbol : method assumeFalse(boolean)
[jira] (MCOMPILER-212) maven-compiler-plugin:3.1:testCompile throws compilation error for class org.junit.Assume
[
https://jira.codehaus.org/browse/MCOMPILER-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331223#comment-331223
]
SebbASF commented on MCOMPILER-212:
---
Have you included junit.jar in the classpath?
You need to include the appropriate version of JUnit as a test dependency.
maven-compiler-plugin:3.1:testCompile throws compilation error for class
org.junit.Assume
-
Key: MCOMPILER-212
URL: https://jira.codehaus.org/browse/MCOMPILER-212
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /usr/share/maven
Java version: 1.6.0_45, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac
Reporter: Adina Moldovan
Steps:
1. Write the following class in your tests package:
package com.adinnaplus.automation.tests;
import org.junit.Assume;
import org.junit.Test;
public class MyTest {
@Test
public void failingTest() {
boolean condition = false;
Assume.assumeFalse(condition);
// test follows here
}
}
2. Go to terminal and run mvn clean test in the path where your project's
pom is
Expected: compilation successful (junit Assume is a very important feature
for our project)
Actual: $ mvn clean test
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Adinnaplus BDD Automation 1.1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
AdinnaplusAutomation ---
[INFO] Deleting
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target
[INFO]
[INFO] --- xmlbeans-maven-plugin:2.3.3:xmlbeans (default) @
AdinnaplusAutomation ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
AdinnaplusAutomation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO] Copying 37 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
AdinnaplusAutomation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 53 source files to
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target/classes
[WARNING] Note:
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/main/java/com/tve/automation/services/helpers/CredentialLoader.java
uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources)
@ AdinnaplusAutomation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
AdinnaplusAutomation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 87 source files to
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target/test-classes
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING] Note:
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/steps/AssertionSteps.java
uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 2 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/tests/MyTest.java:[11,15]
cannot find symbol
symbol : method assumeFalse(boolean)
location: class org.junit.Assume
[INFO] 1 error
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 58.111s
[INFO] Finished at: Wed Aug 21 10:45:12 EEST 2013
[INFO] Final Memory:
[jira] (MCOMPILER-212) maven-compiler-plugin:3.1:testCompile throws compilation error for class org.junit.Assume
[
https://jira.codehaus.org/browse/MCOMPILER-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331259#comment-331259
]
Adina Moldovan commented on MCOMPILER-212:
--
Hi SebbASF,
I am using a test framework called thucydides-junit, which has junit embedded
as a dependency.
Though, when I overwritten it in my pom.xml (same version as in thucydides), it
compiled successfully.
Thanks a lot for your input!
Adina
maven-compiler-plugin:3.1:testCompile throws compilation error for class
org.junit.Assume
-
Key: MCOMPILER-212
URL: https://jira.codehaus.org/browse/MCOMPILER-212
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /usr/share/maven
Java version: 1.6.0_45, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac
Reporter: Adina Moldovan
Steps:
1. Write the following class in your tests package:
package com.adinnaplus.automation.tests;
import org.junit.Assume;
import org.junit.Test;
public class MyTest {
@Test
public void failingTest() {
boolean condition = false;
Assume.assumeFalse(condition);
// test follows here
}
}
2. Go to terminal and run mvn clean test in the path where your project's
pom is
Expected: compilation successful (junit Assume is a very important feature
for our project)
Actual: $ mvn clean test
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Adinnaplus BDD Automation 1.1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
AdinnaplusAutomation ---
[INFO] Deleting
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target
[INFO]
[INFO] --- xmlbeans-maven-plugin:2.3.3:xmlbeans (default) @
AdinnaplusAutomation ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
AdinnaplusAutomation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO] Copying 37 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
AdinnaplusAutomation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 53 source files to
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target/classes
[WARNING] Note:
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/main/java/com/tve/automation/services/helpers/CredentialLoader.java
uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources)
@ AdinnaplusAutomation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
AdinnaplusAutomation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 87 source files to
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target/test-classes
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING] Note:
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/steps/AssertionSteps.java
uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 2 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/tests/MyTest.java:[11,15]
cannot find symbol
symbol : method assumeFalse(boolean)
location: class org.junit.Assume
[INFO] 1 error
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[jira] (MCOMPILER-212) maven-compiler-plugin:3.1:testCompile throws compilation error for class org.junit.Assume
[
https://jira.codehaus.org/browse/MCOMPILER-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adina Moldovan closed MCOMPILER-212.
Resolution: Not A Bug
closing the issue as not a bug
maven-compiler-plugin:3.1:testCompile throws compilation error for class
org.junit.Assume
-
Key: MCOMPILER-212
URL: https://jira.codehaus.org/browse/MCOMPILER-212
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /usr/share/maven
Java version: 1.6.0_45, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac
Reporter: Adina Moldovan
Steps:
1. Write the following class in your tests package:
package com.adinnaplus.automation.tests;
import org.junit.Assume;
import org.junit.Test;
public class MyTest {
@Test
public void failingTest() {
boolean condition = false;
Assume.assumeFalse(condition);
// test follows here
}
}
2. Go to terminal and run mvn clean test in the path where your project's
pom is
Expected: compilation successful (junit Assume is a very important feature
for our project)
Actual: $ mvn clean test
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Adinnaplus BDD Automation 1.1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
AdinnaplusAutomation ---
[INFO] Deleting
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target
[INFO]
[INFO] --- xmlbeans-maven-plugin:2.3.3:xmlbeans (default) @
AdinnaplusAutomation ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
AdinnaplusAutomation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO] Copying 37 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
AdinnaplusAutomation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 53 source files to
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target/classes
[WARNING] Note:
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/main/java/com/tve/automation/services/helpers/CredentialLoader.java
uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources)
@ AdinnaplusAutomation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
AdinnaplusAutomation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 87 source files to
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/target/test-classes
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING] Note:
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/steps/AssertionSteps.java
uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 2 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/Users/adinamoldovan/Documents/git/Adinnaplus/AdinnaplusAutomation/src/test/java/com/tve/automation/tests/MyTest.java:[11,15]
cannot find symbol
symbol : method assumeFalse(boolean)
location: class org.junit.Assume
[INFO] 1 error
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 58.111s
[INFO] Finished at: Wed Aug 21 10:45:12 EEST 2013
[INFO] Final Memory: 22M/81M
[INFO]
[ERROR]
[jira] (MWAR-304) WAR plugin ignores attached artifacts from previous plugins
[ https://jira.codehaus.org/browse/MWAR-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Sand closed MWAR-304. - Resolution: Not A Bug Ok I follow, thanks for explaining the architectural principle to it. WAR plugin ignores attached artifacts from previous plugins --- Key: MWAR-304 URL: https://jira.codehaus.org/browse/MWAR-304 Project: Maven WAR Plugin Issue Type: Bug Components: overlay Affects Versions: 2.4 Environment: any Reporter: Richard Sand If my maven project includes a plugin that attaches an artifact to the project, the war plugin will not process the artifact for inclusion in the results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MASFRES-8) Include assembly descriptor in the produced jar file
[ https://issues.apache.org/jira/browse/MASFRES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13746729#comment-13746729 ] Dennis Lundberg commented on MASFRES-8: --- I'm not sure what kind of configuration you have in place in your project, but Maven does not build a JAR with source code or dependencies by default. That is done through various plugins other than the JAR Plugin, using some configuration. Include assembly descriptor in the produced jar file Key: MASFRES-8 URL: https://issues.apache.org/jira/browse/MASFRES-8 Project: Apache Maven Resource Bundles Issue Type: Wish Reporter: Maysam Yabandeh Priority: Minor Many assembly descriptors conservatively include many jar dependencies in the final jar file, resulting into fat jar problem. If the assembly descriptor file was included by default, each framework could disassemble the fat jar on demand and reassemble it having the known, available jar files excluded. Issues like hadoop-9639 can benefit from this feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-132) Copying of files with permissions broken
[
https://jira.codehaus.org/browse/MRESOURCES-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331281#comment-331281
]
Eric Haszlakiewicz commented on MRESOURCES-132:
---
I don't know about the status of the maven-resources-plugin, but if you're
trying to use the assembly plugin be sure to take a look at MASSEMBLY-238.
According to that, you'll need at least version 2.2-beta-3 of the assembly
plugin to preserve the permissions properly.
Copying of files with permissions broken
Key: MRESOURCES-132
URL: https://jira.codehaus.org/browse/MRESOURCES-132
Project: Maven Resources Plugin
Issue Type: Bug
Components: copy
Affects Versions: 2.4.3
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 22:16:01+0300)
Java version: 1.6.0_19
Java home: /java/jdk1.6.0_19/jre
Default locale: en_US, platform encoding: ISO-8859-1
OS name: linux version: 2.6.28.5 arch: i386 Family: unix
Reporter: Martin Todorov
Files with permissions are not copied with the permissions as illustrated
below:
{noformat}
root@carlspring:/java/opensource/build-force/zipper-plugin# ls -al `find .
-name *perm*`
-rwxr--r-- 1 root root 8 2010-12-09 20:48
./src/test/resources/zip/file.with.permission.sh*
-rw-r--r-- 1 root root 8 2010-12-09 22:56
./target/test-classes/zip/file.with.permission.sh
{noformat}
Notice the 'x' permission missing from the copied file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-661) Assembly plugin looses permissions when using fileSets
Eric Haszlakiewicz created MASSEMBLY-661: Summary: Assembly plugin looses permissions when using fileSets Key: MASSEMBLY-661 URL: https://jira.codehaus.org/browse/MASSEMBLY-661 Project: Maven Assembly Plugin Issue Type: Bug Components: permissions Affects Versions: 2.4 Environment: RHEL5, Maven 2.2.1 Reporter: Eric Haszlakiewicz Attachments: pom.xml When using an assembly descriptor that uses fileSets to include files the permissions of the files from the file system are not preserved in the tarballs. This can be reproduced by creating a file with the executable bit set in the src directory, then trying to use the pre-defined src descriptorRef to create a tarball. See the attached pom file for an example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-661) Assembly plugin looses permissions when using fileSets
[ https://jira.codehaus.org/browse/MASSEMBLY-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331282#comment-331282 ] Eric Haszlakiewicz commented on MASSEMBLY-661: -- Note that there are other issues that talk about similar problems, but not quite the same as what I'm talking about here. MASSEMBLY-238 (refers to depdencySets instead of fileSets) MASSEMBLY-379 (marked as a dup of 238) MASSEMBLY-423 (talks about repeated use of permissions) Assembly plugin looses permissions when using fileSets -- Key: MASSEMBLY-661 URL: https://jira.codehaus.org/browse/MASSEMBLY-661 Project: Maven Assembly Plugin Issue Type: Bug Components: permissions Affects Versions: 2.4 Environment: RHEL5, Maven 2.2.1 Reporter: Eric Haszlakiewicz Attachments: pom.xml When using an assembly descriptor that uses fileSets to include files the permissions of the files from the file system are not preserved in the tarballs. This can be reproduced by creating a file with the executable bit set in the src directory, then trying to use the pre-defined src descriptorRef to create a tarball. See the attached pom file for an example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
