[
https://issues.apache.org/jira/browse/SUREFIRE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430852#comment-15430852
]
Tibor Digana commented on SUREFIRE-1273:
----------------------------------------
[~jodi.cur...@gmail.com]
You maybe expect {code:xml}<argLine>${argLine}
-Dfile.encoding=${project.build.sourceEncoding}</argLine>{code}
to become {code:xml}<argLine>
-Dfile.encoding=${project.build.sourceEncoding}</argLine>{code}
and ${argLine} as an empty string, but this has nothing to do with surefire
nothing but another project Maven (MNG).
AFAIK this is just normal behavior in Maven and maybe controversial.
> Adding plugin inside Maven profile breaks mvn:build on project
> --------------------------------------------------------------
>
> Key: SUREFIRE-1273
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1273
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19.1
> Environment: Windows 10 x64 Professional version 6.3
> Netbeans 8.1 Release
> Maven v3.0.5
> OracleJDKx64 v1.8.0_11
> Reporter: Jodi
> Labels: newbie, windows
> Attachments: pom-jacoco.xml, pom.xml,
> surefire-plugin-success-jacoco.log, surefire-profiles-error.log
>
>
> ##Conditions which led to the issue
> Prior to the issue occurring, jacoco-maven-plugin OR maven-surefire-plugin
> failed to work consistently when using docker-maven-plugin, this is an issue
> which is to be followed up next.
> ##Maven configuration
> After:
> 1. Opening a project POM which hasn't yet been migrated to docker
> 2. Disabling jacoco-maven-plugin
> 3. Moving maven-surefire-plugin to a "test" profile
> 4. Setting plugin version to 2.19.1 in POM
> 5. Switching to "test" profile
> 6. Run mvn:build from Netbeans
> ##Outcome
> maven-surefire-plugin fails during a normal build command - see attachments
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
