[jira] (SUREFIRE-1121) java.lang.NullPointerException org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
[
https://jira.codehaus.org/browse/SUREFIRE-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358770#comment-358770
]
Stephan Schroevers commented on SUREFIRE-1121:
--
It's very nice to see this issue fixed. Are there any plans to release a
version 2.18.1 with this fix? My experience so far is that this issue makes
Surefire 2.18 unusable for projects that run forked tests is parallel. (In our
case the NPE is triggered 25%-50% of the time.)
> java.lang.NullPointerException
> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
> -
>
> Key: SUREFIRE-1121
> URL: https://jira.codehaus.org/browse/SUREFIRE-1121
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.18
> Environment: Apache Maven 3.2.3
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_71, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_71\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Tibor Digana
>Priority: Blocker
> Fix For: 2.19
>
> Attachments: effective.pom
>
>
> git clone http://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> Check out Log4j 2 commit {{d033a71eb0047ca35ec1582f0eab73abe3e04919}}. This
> is currently the latest.
> Run: {{mvn -e clean test}}
> I get:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 0.566
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 26.239
> s]
> [INFO] Apache Log4j Core .. SUCCESS [05:09
> min]
> [INFO] Apache Log4j 1.x Compatibility API . SUCCESS [ 9.233
> s]
> [INFO] Apache Log4j SLF4J Binding . SUCCESS [ 8.507
> s]
> [INFO] Apache Log4j to SLF4J Adapter .. FAILURE [ 5.781
> s]
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 06:02 min
> [INFO] Finished at: 2014-12-01T10:51:31-05:00
> [INFO] Final Memory: 34M/266M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project log4j-to-slf4j: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed.
> NullPointerExc
> eption -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
> on project log4j-to-slf4j: Execution default-test of goal
> org.apache.maven.plugins:maven-
> surefire-plugin:2.18:test failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethr
[jira] (SUREFIRE-1121) java.lang.NullPointerException org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
[
https://jira.codehaus.org/browse/SUREFIRE-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358772#comment-358772
]
Tibor Digana commented on SUREFIRE-1121:
Our intention was to fix bugs and later on introduce features and release 2.19
by the EO January 2015.
Hopefully no new feature was introduced yet, thus we may have chance to release
2.18.1, which I was thinking about too.
I will open a discussion in Maven and we should make some decision about that.
> java.lang.NullPointerException
> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
> -
>
> Key: SUREFIRE-1121
> URL: https://jira.codehaus.org/browse/SUREFIRE-1121
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.18
> Environment: Apache Maven 3.2.3
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_71, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_71\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Tibor Digana
>Priority: Blocker
> Fix For: 2.19
>
> Attachments: effective.pom
>
>
> git clone http://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> Check out Log4j 2 commit {{d033a71eb0047ca35ec1582f0eab73abe3e04919}}. This
> is currently the latest.
> Run: {{mvn -e clean test}}
> I get:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 0.566
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 26.239
> s]
> [INFO] Apache Log4j Core .. SUCCESS [05:09
> min]
> [INFO] Apache Log4j 1.x Compatibility API . SUCCESS [ 9.233
> s]
> [INFO] Apache Log4j SLF4J Binding . SUCCESS [ 8.507
> s]
> [INFO] Apache Log4j to SLF4J Adapter .. FAILURE [ 5.781
> s]
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 06:02 min
> [INFO] Finished at: 2014-12-01T10:51:31-05:00
> [INFO] Final Memory: 34M/266M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project log4j-to-slf4j: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed.
> NullPointerExc
> eption -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
> on project log4j-to-slf4j: Execution default-test of goal
> org.apache.maven.plugins:maven-
> surefire-plugin:2.18:test failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.buil
[jira] (SUREFIRE-1122) When running failsafe with -Dfailsafe.rerunFailingTestsCount and parallel all, the reports are not generated correctly
[
https://jira.codehaus.org/browse/SUREFIRE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358774#comment-358774
]
Roy Arnon commented on SUREFIRE-1122:
-
@Tibor I checkout out the source for failsafe to see if I could maybe submit a
patch.
>From what I saw, it seems that report is generated twice - once when the first
>run of all tests is complete, and then again after the flaky test is completed.
So the file is generated twice, the second time containing only the test that
was run again.
The line that is called twice is in ForkClient.java:
{code:java}
case ForkingRunListener.BOOTERCODE_TESTSET_COMPLETED:
getOrCreateReporter( channelNumber ).testSetCompleted( createReportEntry(
remaining ) );
break;
{code}
No idea how to fix this though, as this seems like a difficult issue - the
testSetCompleted event I'm assuming should only be fired once per test run no?
> When running failsafe with -Dfailsafe.rerunFailingTestsCount and parallel
> all, the reports are not generated correctly
> --
>
> Key: SUREFIRE-1122
> URL: https://jira.codehaus.org/browse/SUREFIRE-1122
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.18
>Reporter: Roy Arnon
>Assignee: Tibor Digana
> Attachments: invalid.xml, test.zip, valid.xml
>
>
> Hi,
> I just tried the new feature -Dfailsafe.rerunFailingTestsCount on our
> failsafe build.
> Unfortunately, when running the build using parallel=all, it seems the junit
> xml files are not generated correctly.
> I've tried running it multiple different ways, including classedAndMethods,
> and all, but it seems to generate an incorrect xml file either way.
> I've attached both files here.
> I can provide a pom and java test case if required.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1121) java.lang.NullPointerException org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
[
https://jira.codehaus.org/browse/SUREFIRE-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358778#comment-358778
]
Stephan Schroevers commented on SUREFIRE-1121:
--
Great. I can confirm that for us 2.19-SNAPSHOT fixes the issue. Previously the
following command would eventually trigger the NPE, and now it no longer
terminates:
{noformat}
while mvn clean install; do echo "Another round"; done
{noformat}
> java.lang.NullPointerException
> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
> -
>
> Key: SUREFIRE-1121
> URL: https://jira.codehaus.org/browse/SUREFIRE-1121
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.18
> Environment: Apache Maven 3.2.3
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_71, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_71\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Tibor Digana
>Priority: Blocker
> Fix For: 2.19
>
> Attachments: effective.pom
>
>
> git clone http://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> Check out Log4j 2 commit {{d033a71eb0047ca35ec1582f0eab73abe3e04919}}. This
> is currently the latest.
> Run: {{mvn -e clean test}}
> I get:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 0.566
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 26.239
> s]
> [INFO] Apache Log4j Core .. SUCCESS [05:09
> min]
> [INFO] Apache Log4j 1.x Compatibility API . SUCCESS [ 9.233
> s]
> [INFO] Apache Log4j SLF4J Binding . SUCCESS [ 8.507
> s]
> [INFO] Apache Log4j to SLF4J Adapter .. FAILURE [ 5.781
> s]
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 06:02 min
> [INFO] Finished at: 2014-12-01T10:51:31-05:00
> [INFO] Final Memory: 34M/266M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project log4j-to-slf4j: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed.
> NullPointerExc
> eption -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
> on project log4j-to-slf4j: Execution default-test of goal
> org.apache.maven.plugins:maven-
> surefire-plugin:2.18:test failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(Si
[jira] (MANTRUN-190) Upgrade Ant to 1.9.x
[ https://jira.codehaus.org/browse/MANTRUN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358780#comment-358780 ] Ion Savin commented on MANTRUN-190: --- Hi [~khmarbaise], any estimate for the release date of 1.8? Thanks! > Upgrade Ant to 1.9.x > > > Key: MANTRUN-190 > URL: https://jira.codehaus.org/browse/MANTRUN-190 > Project: Maven Antrun Plugin > Issue Type: New Feature >Affects Versions: 1.7 >Reporter: Ion Savin >Assignee: Karl-Heinz Marbaise > Fix For: 1.8 > > Attachments: MANTRUN-190.patch > > > Upgrade the underlying Ant dependency fro, 1.8.2 to 1.9.4 (latest). > The new version resolves slow external process execution issues: > https://issues.apache.org/bugzilla/show_bug.cgi?id=54128 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-193) CPD's sourceEncoding not set since PMD 5.1.1 is used
[ https://jira.codehaus.org/browse/MPMD-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358799#comment-358799 ] Andreas Dangel commented on MPMD-193: - Only one call is necessary. I would prefer "setSourceEncoding", as this more accurately describes the usage of this property (instead of just "encoding"). > CPD's sourceEncoding not set since PMD 5.1.1 is used > > > Key: MPMD-193 > URL: https://jira.codehaus.org/browse/MPMD-193 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.2, 3.3, 3.4 >Reporter: Tweea Tang >Assignee: Michael Osipov > Fix For: 3.4 > > Attachments: CpdReport.java.patch, > CpdReport.java(setSourceEncoding).patch > > > Since PMD 5.1.1, CPDConfiguration adds a method postContruct(). > This method is used to set the sourceEncoding property used to read source > files in PMD. > If the sourceEncoding not set, CPD will use the platform default encoding to > read the source files and maven-pmd-plugin's encoding has no effects. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MANTRUN-190) Upgrade Ant to 1.9.x
[ https://jira.codehaus.org/browse/MANTRUN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358804#comment-358804 ] Karl-Heinz Marbaise commented on MANTRUN-190: - I can think of a release to start with on the week end...if a have little bit more time for it... > Upgrade Ant to 1.9.x > > > Key: MANTRUN-190 > URL: https://jira.codehaus.org/browse/MANTRUN-190 > Project: Maven Antrun Plugin > Issue Type: New Feature >Affects Versions: 1.7 >Reporter: Ion Savin >Assignee: Karl-Heinz Marbaise > Fix For: 1.8 > > Attachments: MANTRUN-190.patch > > > Upgrade the underlying Ant dependency fro, 1.8.2 to 1.9.4 (latest). > The new version resolves slow external process execution issues: > https://issues.apache.org/bugzilla/show_bug.cgi?id=54128 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-288) Add a skipEmptyReport option
[ https://jira.codehaus.org/browse/MPIR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-288. --- Resolution: Fixed Fixed with [r1643888|http://svn.apache.org/r1643888] and [r1643913|http://svn.apache.org/r1643913]. > Add a skipEmptyReport option > > > Key: MPIR-288 > URL: https://jira.codehaus.org/browse/MPIR-288 > Project: Maven Project Info Reports Plugin > Issue Type: New Feature >Affects Versions: 2.7 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 2.8 > > > Similar to MPMD-168, it should be possible to skip generation of empty > reports which do not contain any valuable information. > Some canditates are dependencies, cim, scm, issues, mailinglist, etc. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-313) url and name are mandatory for a license but this is not validated
[
https://jira.codehaus.org/browse/MPIR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358808#comment-358808
]
Michael Osipov commented on MPIR-313:
-
Have you thought about a viable approach? I'd like to roll this release in a
week.
> url and name are mandatory for a license but this is not validated
> --
>
> Key: MPIR-313
> URL: https://jira.codehaus.org/browse/MPIR-313
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Constantino Cronemberger
>Priority: Minor
> Labels: exception
> Attachments: exception.txt, pom.xml
>
>
> In an internal project we had a license defined in the pom.xml but without
> url and name.
> This causes an exception which does not say anything about the fact that
> these required elements are missing. See attached file with the complete
> exception.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project
> jee-util: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed: Anchor name
> cannot be null! -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on
> project jee-util: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed: Anchor name
> cannot be null!
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHARED-390) Add startSection method AbstractMavenReportRenderer where anchor != name
Michael Osipov created MSHARED-390: -- Summary: Add startSection method AbstractMavenReportRenderer where anchor != name Key: MSHARED-390 URL: https://jira.codehaus.org/browse/MSHARED-390 Project: Maven Shared Components Issue Type: Improvement Components: maven-reporting-impl Affects Versions: maven-reporting-impl-2.3 Reporter: Michael Osipov Sometimes it is necessary to provide a custom anchor name instead of using the text as an anchor. This could be a synthetic achnor or a language-independent one. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-293) On the team list report the "picUrl" property appears in the table, although no other properties are set for that team member
[
https://jira.codehaus.org/browse/MPIR-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-293:
Assignee: Stephen Connolly
> On the team list report the "picUrl" property appears in the table, although
> no other properties are set for that team member
> -
>
> Key: MPIR-293
> URL: https://jira.codehaus.org/browse/MPIR-293
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Anghel Botos
>Assignee: Stephen Connolly
>Priority: Minor
> Fix For: 2.8
>
> Attachments: HasPicUrlFix.patch
>
>
> On the team list report the "picUrl" property appears in the table, although
> no other properties are set for that team member.
> Given the following team list in the pom.xml:
> {code:xml}
>
>
> abotos
> Anghel Botos
> anghel.bo...@someemailprovider.com
>
> images/avatars/abotos.png
>
>
>
> {code}
> Due to the following lines of code in TeamListReport.java:
> {code:title=TeamListReport.java|borderStyle=solid}
> Properties properties = unit.getProperties();
> boolean hasPicUrl = properties.contains( "picUrl" );
> if ( hasPicUrl )
> {
> requiredHeaders.put( IMAGE, Boolean.TRUE );
> }
> boolean isJustAnImageProperty = properties.size() == 1 &&
> hasPicUrl;
> if ( !isJustAnImageProperty && !properties.isEmpty() )
> {
> requiredHeaders.put( PROPERTIES, Boolean.TRUE );
> }
> {code}
> {{hasPicUrl}} evaluates to {{false}} because the check is done using
> {{contains}} not {{containsKey}}, and thus {{isJustAnImageProperty}}
> evaluates also to {{false}} leading to the Properties column being added to
> the team members table and the {{picUrl}} property being displayed in that
> column in the table, although the Properties column should not be present for
> this case.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRELEASE-206) its not possible to pass MAVEN_OPTS to the forked release build
[ https://jira.codehaus.org/browse/MRELEASE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358809#comment-358809 ] Dan Armbrust commented on MRELEASE-206: --- I can try at some point - but I don't have an environment set up for building / testing maven tooling at the moment... will take me a bit to set things up to be able to test the patch properly. I got past my immediate issue, so I likely won't get to it real soon. I'm not entirely sure myself how the inherited vs specific options are interacting at the moment - I was hoping an expert was still hanging around getting e-mail on this thread, who could have just said yes - now that plexus-utils is much newer than it was 6 years ago... we can just add this line. I'd have to dig in and test to answer questions like that. > its not possible to pass MAVEN_OPTS to the forked release build > --- > > Key: MRELEASE-206 > URL: https://jira.codehaus.org/browse/MRELEASE-206 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-3, 2.0-beta-4 >Reporter: brianfox brianfox > Labels: contributers-welcome > > I need to increase my jvm size for my build. The forked release doesn't get > the maven_opts. I tried the -Darguments: > mvn release:prepare -DdryRun=true -Darguments=-Xmx1024m > gets me this: >[INFO] Invalid task 'mx1024m': you must specify a valid lifecycle phase, > or > a goal in the format plugin:goal or > pluginGroupId:pluginArtifactId:pluginVersion > :goal -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-193) CPD's sourceEncoding not set since PMD 5.1.1 is used
[ https://jira.codehaus.org/browse/MPMD-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358812#comment-358812 ] Michael Osipov edited comment on MPMD-193 at 12/9/14 1:04 AM: -- Changed with [r1643992|http://svn.apache.org/r1643992]. Thank you Andreas. was (Author: michael-o): Changed with [r1643992|http://svn.apache.org/r1643992]. Thanks you Andreas. > CPD's sourceEncoding not set since PMD 5.1.1 is used > > > Key: MPMD-193 > URL: https://jira.codehaus.org/browse/MPMD-193 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.2, 3.3, 3.4 >Reporter: Tweea Tang >Assignee: Michael Osipov > Fix For: 3.4 > > Attachments: CpdReport.java.patch, > CpdReport.java(setSourceEncoding).patch > > > Since PMD 5.1.1, CPDConfiguration adds a method postContruct(). > This method is used to set the sourceEncoding property used to read source > files in PMD. > If the sourceEncoding not set, CPD will use the platform default encoding to > read the source files and maven-pmd-plugin's encoding has no effects. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-193) CPD's sourceEncoding not set since PMD 5.1.1 is used
[ https://jira.codehaus.org/browse/MPMD-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358812#comment-358812 ] Michael Osipov commented on MPMD-193: - Changed with [r1643992|http://svn.apache.org/r1643992]. Thanks you Andreas. > CPD's sourceEncoding not set since PMD 5.1.1 is used > > > Key: MPMD-193 > URL: https://jira.codehaus.org/browse/MPMD-193 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.2, 3.3, 3.4 >Reporter: Tweea Tang >Assignee: Michael Osipov > Fix For: 3.4 > > Attachments: CpdReport.java.patch, > CpdReport.java(setSourceEncoding).patch > > > Since PMD 5.1.1, CPDConfiguration adds a method postContruct(). > This method is used to set the sourceEncoding property used to read source > files in PMD. > If the sourceEncoding not set, CPD will use the platform default encoding to > read the source files and maven-pmd-plugin's encoding has no effects. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-737) Generated WAR file does not contain the same default manifest entries as created by the Maven WAR Plugin
[
https://jira.codehaus.org/browse/MASSEMBLY-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated MASSEMBLY-737:
-
Fix Version/s: (was: 2.5.3)
> Generated WAR file does not contain the same default manifest entries as
> created by the Maven WAR Plugin
>
>
> Key: MASSEMBLY-737
> URL: https://jira.codehaus.org/browse/MASSEMBLY-737
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: manifest, maven-archiver
>Affects Versions: 2.5.2
>Reporter: Michael Osipov
> Attachments: massembly-737.zip
>
>
> I am repackaging a WAR file with some files exchanged. The original fiel
> contains following manifest entries:
> {noformat}
> Manifest-Version: 1.0
> Built-By: osipovmi
> Build-Jdk: 1.7.0_55
> Created-By: Apache Maven 3.2.2
> Archiver-Version: Plexus Archiver
> {noformat}
> The {{MANIFEST.MF}} generated by this plugin looks like:
> {noformat}
> Manifest-Version: 1.0
> Created-By: 24.55-b03 (Oracle Corporation)
> Archiver-Version: Plexus Archiver
> {noformat}
> while the descriptor looks very simple:
> {code}
>
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
> http://maven.apache.org/xsd/assembly-1.1.2.xsd";>
> deployable
>
> war
>
> false
>
>
> true
> false
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
