[jira] (MNG-5568) ComparableVersion's breaks contract for Comparable, in some edgecases the comparisons are not transitive
[
https://jira.codehaus.org/browse/MNG-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358304#comment-358304
]
Michael Osipov commented on MNG-5568:
-
Hervé, do you think it is wise to use a for loop with index instead of an
iterator? The {{get(int)}} method might introduce an {{O(n²)}} execution time
dependending on the list implementation. In genereal, it is not recommended to
go it in this fashion, rather use an iterator with remove.
> ComparableVersion's breaks contract for Comparable, in some edgecases the
> comparisons are not transitive
>
>
> Key: MNG-5568
> URL: https://jira.codehaus.org/browse/MNG-5568
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.5
>Reporter: Milos Kleint
>Assignee: Herve Boutemy
>Priority: Critical
> Fix For: 3.2.4
>
> Attachments: ComparableVersion.patch
>
>
> if ComparableVersion A > B and B > C, then it's required that A > C. In the
> attached test patch, I'm demonstrating a case where it's failing. Please note
> that the situation is not that rare, please see issues
> https://netbeans.org/bugzilla/show_bug.cgi?id=226100 and
> https://netbeans.org/bugzilla/show_bug.cgi?id=240845 at netbeans.org and
> https://jira.codehaus.org/browse/MPIR-247
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5568) ComparableVersion's breaks contract for Comparable, in some edgecases the comparisons are not transitive
[
https://jira.codehaus.org/browse/MNG-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MNG-5568.
--
Resolution: Fixed
Fix Version/s: 3.2.4
Assignee: Herve Boutemy
fixed in [14e4885d|http://git-wip-us.apache.org/repos/asf/maven/commit/14e4885d]
now, {{6.1.0rc3 < 6.1H.5-beta}}
> ComparableVersion's breaks contract for Comparable, in some edgecases the
> comparisons are not transitive
>
>
> Key: MNG-5568
> URL: https://jira.codehaus.org/browse/MNG-5568
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.5
>Reporter: Milos Kleint
>Assignee: Herve Boutemy
>Priority: Critical
> Fix For: 3.2.4
>
> Attachments: ComparableVersion.patch
>
>
> if ComparableVersion A > B and B > C, then it's required that A > C. In the
> attached test patch, I'm demonstrating a case where it's failing. Please note
> that the situation is not that rare, please see issues
> https://netbeans.org/bugzilla/show_bug.cgi?id=226100 and
> https://netbeans.org/bugzilla/show_bug.cgi?id=240845 at netbeans.org and
> https://jira.codehaus.org/browse/MPIR-247
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5568) ComparableVersion's breaks contract for Comparable, in some edgecases the comparisons are not transitive
[
https://jira.codehaus.org/browse/MNG-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358301#comment-358301
]
Herve Boutemy edited comment on MNG-5568 at 11/30/14 4:19 PM:
--
made maven-artifact.jar executable to test version parsing and comparison in
MNG-5730
we can now analyze the bug more easily:
{code}$ java -jar maven-artifact-3.2.4-SNAPSHOT.jar 6.1.0 6.1.0rc3 6.1H.5-beta
6.1.0
Display parameters as parsed by Maven, and comparison result:
1. 6.1.0 == 6.1
6.1.0 > 6.1.0rc3
2. 6.1.0rc3 == 6.1.0.rc.3
6.1.0rc3 > 6.1H.5-beta
3. 6.1H.5-beta == 6.1.h.5.beta
6.1H.5-beta > 6.1.0
4. 6.1.0 == 6.1{code}
the bug is that {{6.1.0rc3 > 6.1H.5-beta}}: should be the contrary
was (Author: hboutemy):
made maven-artifact.jar executable to test version parsing and comparison in
MNG-5730
we can now analyze the bug more easily:
{code}$ java -jar maven-artifact-3.2.4-SNAPSHOT.jar 6.1.0 6.1.0rc3 6.1H.5-beta
6.1.0
Display parameters as parsed by Maven, and comparison result:
1. 6.1.0 == 6.1
6.1.0 > 6.1.0rc3
2. 6.1.0rc3 == 6.1.0.rc.3
6.1.0rc3 > 6.1H.5-beta
3. 6.1H.5-beta == 6.1.h.5.beta
6.1H.5-beta > 6.1.0
4. 6.1.0 == 6.1{code}
> ComparableVersion's breaks contract for Comparable, in some edgecases the
> comparisons are not transitive
>
>
> Key: MNG-5568
> URL: https://jira.codehaus.org/browse/MNG-5568
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.5
>Reporter: Milos Kleint
>Priority: Critical
> Attachments: ComparableVersion.patch
>
>
> if ComparableVersion A > B and B > C, then it's required that A > C. In the
> attached test patch, I'm demonstrating a case where it's failing. Please note
> that the situation is not that rare, please see issues
> https://netbeans.org/bugzilla/show_bug.cgi?id=226100 and
> https://netbeans.org/bugzilla/show_bug.cgi?id=240845 at netbeans.org and
> https://jira.codehaus.org/browse/MPIR-247
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5568) ComparableVersion's breaks contract for Comparable, in some edgecases the comparisons are not transitive
[
https://jira.codehaus.org/browse/MNG-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358301#comment-358301
]
Herve Boutemy edited comment on MNG-5568 at 11/30/14 3:20 PM:
--
made maven-artifact.jar executable to test version parsing and comparison in
MNG-5730
we can now analyze the bug more easily:
{code}$ java -jar maven-artifact-3.2.4-SNAPSHOT.jar 6.1.0 6.1.0rc3 6.1H.5-beta
6.1.0
Display parameters as parsed by Maven, and comparison result:
1. 6.1.0 == 6.1
6.1.0 > 6.1.0rc3
2. 6.1.0rc3 == 6.1.0.rc.3
6.1.0rc3 > 6.1H.5-beta
3. 6.1H.5-beta == 6.1.h.5.beta
6.1H.5-beta > 6.1.0
4. 6.1.0 == 6.1{code}
was (Author: hboutemy):
made maven-artifact.jar executable to test version parsing and comparison
we can now analyze the bug more easily:
{code}$ java -jar maven-artifact-3.2.4-SNAPSHOT.jar 6.1.0 6.1.0rc3 6.1H.5-beta
6.1.0
Display parameters as parsed by Maven, and comparison result:
1. 6.1.0 == 6.1
6.1.0 > 6.1.0rc3
2. 6.1.0rc3 == 6.1.0.rc.3
6.1.0rc3 > 6.1H.5-beta
3. 6.1H.5-beta == 6.1.h.5.beta
6.1H.5-beta > 6.1.0
4. 6.1.0 == 6.1{code}
> ComparableVersion's breaks contract for Comparable, in some edgecases the
> comparisons are not transitive
>
>
> Key: MNG-5568
> URL: https://jira.codehaus.org/browse/MNG-5568
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.5
>Reporter: Milos Kleint
>Priority: Critical
> Attachments: ComparableVersion.patch
>
>
> if ComparableVersion A > B and B > C, then it's required that A > C. In the
> attached test patch, I'm demonstrating a case where it's failing. Please note
> that the situation is not that rare, please see issues
> https://netbeans.org/bugzilla/show_bug.cgi?id=226100 and
> https://netbeans.org/bugzilla/show_bug.cgi?id=240845 at netbeans.org and
> https://jira.codehaus.org/browse/MPIR-247
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5568) ComparableVersion's breaks contract for Comparable, in some edgecases the comparisons are not transitive
[
https://jira.codehaus.org/browse/MNG-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358301#comment-358301
]
Herve Boutemy commented on MNG-5568:
made maven-artifact.jar executable to test version parsing and comparison
we can now analyze the bug more easily:
{code}$ java -jar maven-artifact-3.2.4-SNAPSHOT.jar 6.1.0 6.1.0rc3 6.1H.5-beta
6.1.0
Display parameters as parsed by Maven, and comparison result:
1. 6.1.0 == 6.1
6.1.0 > 6.1.0rc3
2. 6.1.0rc3 == 6.1.0.rc.3
6.1.0rc3 > 6.1H.5-beta
3. 6.1H.5-beta == 6.1.h.5.beta
6.1H.5-beta > 6.1.0
4. 6.1.0 == 6.1{code}
> ComparableVersion's breaks contract for Comparable, in some edgecases the
> comparisons are not transitive
>
>
> Key: MNG-5568
> URL: https://jira.codehaus.org/browse/MNG-5568
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.5
>Reporter: Milos Kleint
>Priority: Critical
> Attachments: ComparableVersion.patch
>
>
> if ComparableVersion A > B and B > C, then it's required that A > C. In the
> attached test patch, I'm demonstrating a case where it's failing. Please note
> that the situation is not that rare, please see issues
> https://netbeans.org/bugzilla/show_bug.cgi?id=226100 and
> https://netbeans.org/bugzilla/show_bug.cgi?id=240845 at netbeans.org and
> https://jira.codehaus.org/browse/MPIR-247
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5730) Provide a tool to test Maven version parsing and comparison
[ https://jira.codehaus.org/browse/MNG-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5730. -- Resolution: Fixed Fix Version/s: 3.2.4 Assignee: Herve Boutemy done in [09d64bdf|http://git-wip-us.apache.org/repos/asf/maven/commit/09d64bdf] > Provide a tool to test Maven version parsing and comparison > --- > > Key: MNG-5730 > URL: https://jira.codehaus.org/browse/MNG-5730 > Project: Maven > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 3.2.3 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.2.4 > > > At the moment, when someone thinks there is a problem, the only way to > investigate is to write new unit tests in ComparableVersionTest > a little CLI tool to display the parsed version (in its canonical form) and > comparing arguments would be useful -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-197) Update dependencies and resolve minor Java warnings
[ https://jira.codehaus.org/browse/MPMD-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPMD-197. --- Resolution: Fixed Fix Version/s: 3.4 Fixed with [r1642605|http://svn.apache.org/r1642605]. > Update dependencies and resolve minor Java warnings > --- > > Key: MPMD-197 > URL: https://jira.codehaus.org/browse/MPMD-197 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 3.3 >Reporter: Jeremy Landis >Assignee: Michael Osipov >Priority: Trivial > Fix For: 3.4 > > > Bring various dependencies in pmd plugin current to more recent changes in > the maven ecosystem. > maven-site-plugin to 3.4 > maven-plugin-testing-harness to 1.3 > animal-sniffer-maven-plugin to 1.12 > java16 signature to 1.1 > plexus-utils to 3.0.21 > remove modello-maven-plugin version as it is overriding parent unnecessarily. > Update maven-plugins parent to 27 and remove maven-compiler-plugin and TODO > as it is part of this updated parent. > Remove unnecessary 'unchecked' suppress warnings, add java 6 requested > @Overrides, and give types to lists. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5730) Provide a tool to test Maven version parsing and comparison
Herve Boutemy created MNG-5730: -- Summary: Provide a tool to test Maven version parsing and comparison Key: MNG-5730 URL: https://jira.codehaus.org/browse/MNG-5730 Project: Maven Issue Type: Improvement Components: Artifacts and Repositories Affects Versions: 3.2.3 Reporter: Herve Boutemy At the moment, when someone thinks there is a problem, the only way to investigate is to write new unit tests in ComparableVersionTest a little CLI tool to display the parsed version (in its canonical form) and comparing arguments would be useful -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-197) Update dependencies and resolve minor Java warnings
[ https://jira.codehaus.org/browse/MPMD-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPMD-197: Summary: Update dependencies and resolve minor Java warnings (was: Bring Dependencies current and Resolve Minor Java Warnings) > Update dependencies and resolve minor Java warnings > --- > > Key: MPMD-197 > URL: https://jira.codehaus.org/browse/MPMD-197 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 3.3 >Reporter: Jeremy Landis >Priority: Trivial > > Bring various dependencies in pmd plugin current to more recent changes in > the maven ecosystem. > maven-site-plugin to 3.4 > maven-plugin-testing-harness to 1.3 > animal-sniffer-maven-plugin to 1.12 > java16 signature to 1.1 > plexus-utils to 3.0.21 > remove modello-maven-plugin version as it is overriding parent unnecessarily. > Update maven-plugins parent to 27 and remove maven-compiler-plugin and TODO > as it is part of this updated parent. > Remove unnecessary 'unchecked' suppress warnings, add java 6 requested > @Overrides, and give types to lists. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-197) Update dependencies and resolve minor Java warnings
[ https://jira.codehaus.org/browse/MPMD-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPMD-197: --- Assignee: Michael Osipov > Update dependencies and resolve minor Java warnings > --- > > Key: MPMD-197 > URL: https://jira.codehaus.org/browse/MPMD-197 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 3.3 >Reporter: Jeremy Landis >Assignee: Michael Osipov >Priority: Trivial > > Bring various dependencies in pmd plugin current to more recent changes in > the maven ecosystem. > maven-site-plugin to 3.4 > maven-plugin-testing-harness to 1.3 > animal-sniffer-maven-plugin to 1.12 > java16 signature to 1.1 > plexus-utils to 3.0.21 > remove modello-maven-plugin version as it is overriding parent unnecessarily. > Update maven-plugins parent to 27 and remove maven-compiler-plugin and TODO > as it is part of this updated parent. > Remove unnecessary 'unchecked' suppress warnings, add java 6 requested > @Overrides, and give types to lists. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-197) Bring Dependencies current and Resolve Minor Java Warnings
Jeremy Landis created MPMD-197: -- Summary: Bring Dependencies current and Resolve Minor Java Warnings Key: MPMD-197 URL: https://jira.codehaus.org/browse/MPMD-197 Project: Maven PMD Plugin Issue Type: Improvement Components: PMD Affects Versions: 3.3 Reporter: Jeremy Landis Priority: Trivial Bring various dependencies in pmd plugin current to more recent changes in the maven ecosystem. maven-site-plugin to 3.4 maven-plugin-testing-harness to 1.3 animal-sniffer-maven-plugin to 1.12 java16 signature to 1.1 plexus-utils to 3.0.21 remove modello-maven-plugin version as it is overriding parent unnecessarily. Update maven-plugins parent to 27 and remove maven-compiler-plugin and TODO as it is part of this updated parent. Remove unnecessary 'unchecked' suppress warnings, add java 6 requested @Overrides, and give types to lists. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-238) Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
[
https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MPIR-238:
---
Attachment: (was: MPIR-238-ReactorReader.patch)
> Dependency File Details section of the dependencies report shows
> 'target/classes' for reactor artifacts.
>
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.4
>Reporter: Christian Schulte
>Priority: Minor
>
> Generating the dependencies report in a multi-module project leads to
> incorrect entries in the 'Dependency File Details' section of the
> dependencies report. For example, the [Maven Release Plugin Dependency File
> Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details]
> report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory),
> the correct entries are shown.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-238) Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
[
https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MPIR-238:
---
Attachment: (was: MPIR-238-ReactorReader.patch)
> Dependency File Details section of the dependencies report shows
> 'target/classes' for reactor artifacts.
>
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.4
>Reporter: Christian Schulte
>Priority: Minor
>
> Generating the dependencies report in a multi-module project leads to
> incorrect entries in the 'Dependency File Details' section of the
> dependencies report. For example, the [Maven Release Plugin Dependency File
> Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details]
> report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory),
> the correct entries are shown.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-238) Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
[
https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MPIR-238:
---
Attachment: (was: MPIR-238.patch)
> Dependency File Details section of the dependencies report shows
> 'target/classes' for reactor artifacts.
>
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.4
>Reporter: Christian Schulte
>Priority: Minor
> Attachments: MPIR-238-ReactorReader.patch,
> MPIR-238-ReactorReader.patch
>
>
> Generating the dependencies report in a multi-module project leads to
> incorrect entries in the 'Dependency File Details' section of the
> dependencies report. For example, the [Maven Release Plugin Dependency File
> Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details]
> report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory),
> the correct entries are shown.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-238) Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
[
https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358296#comment-358296
]
Christian Schulte commented on MPIR-238:
I am going to delete the patches. This issue needs more discussion. In Maven 3,
the core got changed to fall back to loose class files from {{target/classes}}
directories to solve various issues. However, this leads to issues with
projects where the content of the {{target/classes}} directory does not match
the content of e.g. the {{jar}} file the project produces. A project using the
{{maven-shade-plugin}} may produce a {{jar}} with totally different content
than the content of the {{target/classes}} directory. The {{maven-jar-plugin}}
may be configured to exclude various files from the {{target/classes}}
directory. The {{clirr-maven-plugin}} must not compare the content of the
{{target/classes}} directory with the {{jar}} of the previous version etc. My
suggestion is to fall back to loose class files only if falling back really is
the only way to not fail the build. If the packaged artifact is available,
there is no need to fall back to anything, in my opinion. Also, I don't think
{{hasLifecyclePhase}} should be backing this decision since you cannot tell
how a project performs its packaging.
> Dependency File Details section of the dependencies report shows
> 'target/classes' for reactor artifacts.
>
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.4
>Reporter: Christian Schulte
>Priority: Minor
> Attachments: MPIR-238-ReactorReader.patch,
> MPIR-238-ReactorReader.patch
>
>
> Generating the dependencies report in a multi-module project leads to
> incorrect entries in the 'Dependency File Details' section of the
> dependencies report. For example, the [Maven Release Plugin Dependency File
> Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details]
> report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory),
> the correct entries are shown.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-308) fails with java 8 (caused by BCEL)
[ https://jira.codehaus.org/browse/MPIR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358295#comment-358295 ] Michael Osipov commented on MPIR-308: - This bug resides in BCEL and is used by Maven Shared JAR. Please file an issue with MSHARED JAR and make this one a depend upon. Can you meanwhile update to BCEL 6.0-SNAPSHOT and see whether it works with Java 8? > fails with java 8 (caused by BCEL) > -- > > Key: MPIR-308 > URL: https://jira.codehaus.org/browse/MPIR-308 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.7 > Environment: Windows 7 / java 8 >Reporter: Mickaël VERA > Attachments: maven.output.log > > > The build finishes with success but there is a stack trace is logged. > The log file is attached. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-387) Upgrade plexus-archiver from 2.8.1 to 2.9
[ https://jira.codehaus.org/browse/MSHARED-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed MSHARED-387. -- Resolution: Fixed Fix Version/s: maven-archiver-2.7 Assignee: Kristian Rosenvold 2.9 in r1642594 https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md > Upgrade plexus-archiver from 2.8.1 to 2.9 > -- > > Key: MSHARED-387 > URL: https://jira.codehaus.org/browse/MSHARED-387 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: maven-archiver-2.7 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-387) Upgrade plexus-archiver from 2.8.1 to 2.9
Kristian Rosenvold created MSHARED-387: -- Summary: Upgrade plexus-archiver from 2.8.1 to 2.9 Key: MSHARED-387 URL: https://jira.codehaus.org/browse/MSHARED-387 Project: Maven Shared Components Issue Type: Improvement Components: maven-archiver Reporter: Kristian Rosenvold -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-238) Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
[
https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358293#comment-358293
]
Michael Osipov commented on MPIR-238:
-
Christian, is the patch still valid? If yes, retest please otherwise delete it
right away.
> Dependency File Details section of the dependencies report shows
> 'target/classes' for reactor artifacts.
>
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.4
>Reporter: Christian Schulte
>Priority: Minor
> Attachments: MPIR-238.patch, MPIR-238-ReactorReader.patch,
> MPIR-238-ReactorReader.patch
>
>
> Generating the dependencies report in a multi-module project leads to
> incorrect entries in the 'Dependency File Details' section of the
> dependencies report. For example, the [Maven Release Plugin Dependency File
> Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details]
> report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory),
> the correct entries are shown.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-238) Dependency File Details section of the dependencies report shows 'target/classes' for reactor artifacts.
[
https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-238:
Comment: was deleted
(was: Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.)
> Dependency File Details section of the dependencies report shows
> 'target/classes' for reactor artifacts.
>
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.4
>Reporter: Christian Schulte
>Priority: Minor
> Attachments: MPIR-238.patch, MPIR-238-ReactorReader.patch,
> MPIR-238-ReactorReader.patch
>
>
> Generating the dependencies report in a multi-module project leads to
> incorrect entries in the 'Dependency File Details' section of the
> dependencies report. For example, the [Maven Release Plugin Dependency File
> Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details]
> report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory),
> the correct entries are shown.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-417) Update version of plexus-archive from 2.5 to 2.9
[ https://jira.codehaus.org/browse/MJAVADOC-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MJAVADOC-417: Summary: Update version of plexus-archive from 2.5 to 2.9 (was: Update version of plexus-archive from 2.5 to 2.8) > Update version of plexus-archive from 2.5 to 2.9 > > > Key: MJAVADOC-417 > URL: https://jira.codehaus.org/browse/MJAVADOC-417 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.11 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.11 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-417) Update version of plexus-archive from 2.5 to 2.8
[ https://jira.codehaus.org/browse/MJAVADOC-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MJAVADOC-417: Description: https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md (was: Release Notes - Plexus Components - Version plexus-archiver-2.7 ** Bug * [PLXCOMP-252] - Tar archivers cannot roundtrip own archives on windows, UTF8 bug ** Improvement * [PLXCOMP-253] - Switch default encoding to UTF-8 Release Notes - Plexus Components - Version plexus-archiver-2.6.4 ** Bug * [PLXCOMP-45] - ignoreWebXML flag use is opposite of what the name implies. * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . * [PLXCOMP-234] - plexus archiver TarOptions setDirMode and setMode do not do anything unless TarArchiver.setOptions is called ** Improvement * [PLXCOMP-250] - Upgrade maven-enforcer-plugin to 1.3.1 ) Summary: Update version of plexus-archive from 2.5 to 2.8 (was: Update version of plexus-archiver to 2.7) > Update version of plexus-archive from 2.5 to 2.8 > > > Key: MJAVADOC-417 > URL: https://jira.codehaus.org/browse/MJAVADOC-417 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.11 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.11 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-417) Update version of plexus-archive from 2.5 to 2.9
[ https://jira.codehaus.org/browse/MJAVADOC-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358292#comment-358292 ] Kristian Rosenvold commented on MJAVADOC-417: - 2.9 in r1642583 > Update version of plexus-archive from 2.5 to 2.9 > > > Key: MJAVADOC-417 > URL: https://jira.codehaus.org/browse/MJAVADOC-417 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.11 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.11 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-263) Add parameter 'targetJavaVersion' and inject ${maven.compiler.target}
[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-263.
---
Resolution: Fixed
Followup fixes [r1642237|http://svn.apache.org/r1642237] and
[r1642582|http://svn.apache.org/r1642582].
> Add parameter 'targetJavaVersion' and inject ${maven.compiler.target}
> -
>
> Key: MPIR-263
> URL: https://jira.codehaus.org/browse/MPIR-263
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: summary
>Affects Versions: 2.6
> Environment: Maven 2.2.1 and 3.0.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.8
>
>
> If you define {{maven.compiler.target}} in the {{}} section or
> per command line, that value is not taken into account in report generation.
> The source and target version are retrieved from the static model.
> If someone could use an interpolated model that would solve the issue. At
> least this should be in the FAQ list.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MECLIPSE-754) UPdate plexus-archiver to 2.9,plexus-utils to 3.0.18 and maven-archiver to 2.5
[ https://jira.codehaus.org/browse/MECLIPSE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MECLIPSE-754: Description: https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md 2.9 in r1642579 Updated to 2.6.1 in r1628095 2.5 release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630 2.6 release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639 2.6.1 release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656 was: Updated to 2.6.1 in r1628095 2.5 release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630 2.6 release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639 2.6.1 release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656 Summary: UPdate plexus-archiver to 2.9,plexus-utils to 3.0.18 and maven-archiver to 2.5 (was: UPdate plexus-archiver to 2.6.1,plexus-utils to 3.0.18 and maven-archiver to 2.5) > UPdate plexus-archiver to 2.9,plexus-utils to 3.0.18 and maven-archiver to 2.5 > -- > > Key: MECLIPSE-754 > URL: https://jira.codehaus.org/browse/MECLIPSE-754 > Project: Maven Eclipse Plugin > Issue Type: Improvement >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: 2.10 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md > 2.9 in r1642579 > Updated to 2.6.1 in r1628095 > 2.5 release notes: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630 > 2.6 release notes: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639 > 2.6.1 release notes: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRAR-40) Update version of plexus-archiver to 2.9
[ https://jira.codehaus.org/browse/MRAR-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MRAR-40: --- Description: https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md (was: Release Notes - Plexus Components - Version plexus-archiver-2.7.1 Bug PLXCOMP-256 - Several archivers leaks file handles Improvement PLXCOMP-257 - Inconsistent buffering Release Notes - Plexus Components - Version plexus-archiver-2.7 ** Bug * [PLXCOMP-252] - Tar archivers cannot roundtrip own archives on windows, UTF8 bug ** Improvement * [PLXCOMP-253] - Switch default encoding to UTF-8 Release Notes - Plexus Components - Version plexus-archiver-2.6.4 ** Bug * [PLXCOMP-45] - ignoreWebXML flag use is opposite of what the name implies. * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . * [PLXCOMP-234] - plexus archiver TarOptions setDirMode and setMode do not do anything unless TarArchiver.setOptions is called ** Improvement * [PLXCOMP-250] - Upgrade maven-enforcer-plugin to 1.3.1 ) Summary: Update version of plexus-archiver to 2.9 (was: Update version of plexus-archiver to 2.7.1) > Update version of plexus-archiver to 2.9 > > > Key: MRAR-40 > URL: https://jira.codehaus.org/browse/MRAR-40 > Project: Maven Rar Plugin > Issue Type: Improvement >Affects Versions: next-release >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: next-release > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-263) Add parameter 'targetJavaVersion' and inject ${maven.compiler.target}
[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MPIR-263:
-
New parameter must only be known to {{ProjectSummaryReport}}.
> Add parameter 'targetJavaVersion' and inject ${maven.compiler.target}
> -
>
> Key: MPIR-263
> URL: https://jira.codehaus.org/browse/MPIR-263
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: summary
>Affects Versions: 2.6
> Environment: Maven 2.2.1 and 3.0.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.8
>
>
> If you define {{maven.compiler.target}} in the {{}} section or
> per command line, that value is not taken into account in report generation.
> The source and target version are retrieved from the static model.
> If someone could use an interpolated model that would solve the issue. At
> least this should be in the FAQ list.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-242) Incorrect translations list for GPL v3 (illegible letters for Catalan and Arabic)
[ https://jira.codehaus.org/browse/MPIR-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-242. --- Resolution: Fixed Fix Version/s: 2.8 Fixed with [r1642577|http://svn.apache.org/r1642577]. > Incorrect translations list for GPL v3 (illegible letters for Catalan and > Arabic) > - > > Key: MPIR-242 > URL: https://jira.codehaus.org/browse/MPIR-242 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: license >Affects Versions: 2.4 > Environment: Apache Maven 3.0.3 > (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200) > Maven home: /usr/local/apache-maven/apache-maven-3.0.3 > Java version: 1.6.0_18, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: de_DE, platform encoding: UTF-8 > OS name: "linux", version: "2.6.18-028stab092.1", arch: "amd64", family: > "unix" >Reporter: Heinrich Schuchardt >Assignee: Michael Osipov >Priority: Minor > Fix For: 2.8 > > Attachments: license.html, pom.xml, pom.xml, screenshot2.png > > > Dear maintainer, > the license report for GPL v3 contains a translation list. This translation > list contains illegible letters for languages Catalan and Arabic: > Skip translations list > English [en] > çÄùñèÊé [ar] > català [ca] > Deutsch [de] > Use appended pom.xml for testing. > Best regards > Heinrich Schuchardt -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-21) Upgrade from plexus-archiver 2.4.4 to 2.9
[ https://jira.codehaus.org/browse/MACR-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold resolved MACR-21. Resolution: Fixed Fix Version/s: 1.2 > Upgrade from plexus-archiver 2.4.4 to 2.9 > - > > Key: MACR-21 > URL: https://jira.codehaus.org/browse/MACR-21 > Project: Maven ACR Plugin > Issue Type: Improvement >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: 1.2 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-21) Upgrade from plexus-archiver 2.4.4 to 2.9
[ https://jira.codehaus.org/browse/MACR-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed MACR-21. -- Resolution: Fixed Assignee: Kristian Rosenvold > Upgrade from plexus-archiver 2.4.4 to 2.9 > - > > Key: MACR-21 > URL: https://jira.codehaus.org/browse/MACR-21 > Project: Maven ACR Plugin > Issue Type: Improvement >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-21) Upgrade from plexus-archiver 2.4.4 to 2.9
[ https://jira.codehaus.org/browse/MACR-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold reopened MACR-21: > Upgrade from plexus-archiver 2.4.4 to 2.9 > - > > Key: MACR-21 > URL: https://jira.codehaus.org/browse/MACR-21 > Project: Maven ACR Plugin > Issue Type: Improvement >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: 1.2 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-21) Upgrade from plexus-archiver 2.4.4 to 2.9
Kristian Rosenvold created MACR-21: -- Summary: Upgrade from plexus-archiver 2.4.4 to 2.9 Key: MACR-21 URL: https://jira.codehaus.org/browse/MACR-21 Project: Maven ACR Plugin Issue Type: Improvement Reporter: Kristian Rosenvold https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MREPOSITORY-36) Update version of plexus-archiver from 2.6.3 to 2.9
[ https://jira.codehaus.org/browse/MREPOSITORY-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358288#comment-358288 ] Kristian Rosenvold commented on MREPOSITORY-36: --- 2.9 in r1642574 > Update version of plexus-archiver from 2.6.3 to 2.9 > --- > > Key: MREPOSITORY-36 > URL: https://jira.codehaus.org/browse/MREPOSITORY-36 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MREPOSITORY-36) Update version of plexus-archiver from 2.6.3 to 2.9
[ https://jira.codehaus.org/browse/MREPOSITORY-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MREPOSITORY-36: -- Description: https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md (was: Release Notes - Plexus Components - Version plexus-archiver-2.7 ** Bug * [PLXCOMP-252] - Tar archivers cannot roundtrip own archives on windows, UTF8 bug ** Improvement * [PLXCOMP-253] - Switch default encoding to UTF-8 Release Notes - Plexus Components - Version plexus-archiver-2.6.4 ** Bug * [PLXCOMP-45] - ignoreWebXML flag use is opposite of what the name implies. * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . * [PLXCOMP-234] - plexus archiver TarOptions setDirMode and setMode do not do anything unless TarArchiver.setOptions is called ** Improvement * [PLXCOMP-250] - Upgrade maven-enforcer-plugin to 1.3.1 ) > Update version of plexus-archiver from 2.6.3 to 2.9 > --- > > Key: MREPOSITORY-36 > URL: https://jira.codehaus.org/browse/MREPOSITORY-36 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MREPOSITORY-36) Update version of plexus-archiver from 2.6.3 to 2.9
[ https://jira.codehaus.org/browse/MREPOSITORY-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MREPOSITORY-36: -- Summary: Update version of plexus-archiver from 2.6.3 to 2.9 (was: Update version of plexus-archiver to 2.7) > Update version of plexus-archiver from 2.6.3 to 2.9 > --- > > Key: MREPOSITORY-36 > URL: https://jira.codehaus.org/browse/MREPOSITORY-36 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Release Notes - Plexus Components - Version plexus-archiver-2.7 > ** Bug > * [PLXCOMP-252] - Tar archivers cannot roundtrip own archives on windows, > UTF8 bug > ** Improvement > * [PLXCOMP-253] - Switch default encoding to UTF-8 > Release Notes - Plexus Components - Version plexus-archiver-2.6.4 > ** Bug > * [PLXCOMP-45] - ignoreWebXML flag use is opposite of what the name > implies. > * [PLXCOMP-107] - Fail to unzip archive, which contains file with name > 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . > * [PLXCOMP-234] - plexus archiver TarOptions setDirMode and setMode do > not do anything unless TarArchiver.setOptions is called > ** Improvement > * [PLXCOMP-250] - Upgrade maven-enforcer-plugin to 1.3.1 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-73) Update version of plexus-archiver from 2.4.4 to 2.9
[ https://jira.codehaus.org/browse/MEJB-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358287#comment-358287 ] Kristian Rosenvold commented on MEJB-73: 2.9 in r1642573 > Update version of plexus-archiver from 2.4.4 to 2.9 > --- > > Key: MEJB-73 > URL: https://jira.codehaus.org/browse/MEJB-73 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-73) Update version of plexus-archiver from 2.4.4 to 2.9
[ https://jira.codehaus.org/browse/MEJB-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MEJB-73: --- Description: https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md (was: Release Notes - Plexus Components - Version plexus-archiver-2.7 ** Bug * [PLXCOMP-252] - Tar archivers cannot roundtrip own archives on windows, UTF8 bug ** Improvement * [PLXCOMP-253] - Switch default encoding to UTF-8 Release Notes - Plexus Components - Version plexus-archiver-2.6.4 ** Bug * [PLXCOMP-45] - ignoreWebXML flag use is opposite of what the name implies. * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . * [PLXCOMP-234] - plexus archiver TarOptions setDirMode and setMode do not do anything unless TarArchiver.setOptions is called ** Improvement * [PLXCOMP-250] - Upgrade maven-enforcer-plugin to 1.3.1 ) Summary: Update version of plexus-archiver from 2.4.4 to 2.9 (was: Update version of plexus-archiver to 2.7) > Update version of plexus-archiver from 2.4.4 to 2.9 > --- > > Key: MEJB-73 > URL: https://jira.codehaus.org/browse/MEJB-73 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-465) Update version of plexus-archiver from 2.4.4 to 2.9
[ https://jira.codehaus.org/browse/MDEP-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MDEP-465: Description: Release notes for archiver can be found at: https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md was: Release Notes - Plexus Components - Version plexus-archiver-2.7.1 Bug PLXCOMP-256 - Several archivers leaks file handles Improvement PLXCOMP-257 - Inconsistent buffering Release Notes - Plexus Components - Version plexus-archiver-2.7 ** Bug * [PLXCOMP-252] - Tar archivers cannot roundtrip own archives on windows, UTF8 bug ** Improvement * [PLXCOMP-253] - Switch default encoding to UTF-8 Release Notes - Plexus Components - Version plexus-archiver-2.6.4 ** Bug * [PLXCOMP-45] - ignoreWebXML flag use is opposite of what the name implies. * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . * [PLXCOMP-234] - plexus archiver TarOptions setDirMode and setMode do not do anything unless TarArchiver.setOptions is called ** Improvement * [PLXCOMP-250] - Upgrade maven-enforcer-plugin to 1.3.1 Release Notes - Plexus Components - Version plexus-archiver-2.6.3 ** Bug * [PLXCOMP-247] - Bug with windows AND java5 [Release Notes plexus-archiver 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] * Bugs: ** [PLXCOMP-238] - CRC Failure if compress=false ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux Release Notes - Plexus Components - Version plexus-archiver-2.6.1 ** Bug * [PLXCOMP-243] - Restore JDK1.5 compatibility Release Notes - Plexus Components - Version plexus-archiver-2.6 ** Bug * [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to fix) ** Improvement * [PLXCOMP-64] - add symlink support to tar unarchiver * [PLXCOMP-117] - add symbolic links managment Release Notes - Plexus Components - Version plexus-archiver-2.5 ** Bug * [PLXCOMP-13] - Plexus Archiver fails on certain Jars * [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags * [PLXCOMP-216] - Unarchiver extracts files into wrong directory * [PLXCOMP-232] - Failures to unpack .tar.gz files * [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** Improvement * [PLXCOMP-153] - TarUnArchiver does not support includes/excludes * [PLXCOMP-240] - Convert everything to commons-compress > Update version of plexus-archiver from 2.4.4 to 2.9 > --- > > Key: MDEP-465 > URL: https://jira.codehaus.org/browse/MDEP-465 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.10 > > > Release notes for archiver can be found at: > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-465) Update version of plexus-archiver from 2.4.4 to 2.9
[ https://jira.codehaus.org/browse/MDEP-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358285#comment-358285 ] Kristian Rosenvold commented on MDEP-465: - Updated to 2.9 in r1642572 > Update version of plexus-archiver from 2.4.4 to 2.9 > --- > > Key: MDEP-465 > URL: https://jira.codehaus.org/browse/MDEP-465 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.10 > > > Release Notes - Plexus Components - Version plexus-archiver-2.7.1 > Bug > PLXCOMP-256 - Several archivers leaks file handles > Improvement > PLXCOMP-257 - Inconsistent buffering > Release Notes - Plexus Components - Version plexus-archiver-2.7 > ** Bug > * [PLXCOMP-252] - Tar archivers cannot roundtrip own archives on windows, > UTF8 bug > ** Improvement > * [PLXCOMP-253] - Switch default encoding to UTF-8 > Release Notes - Plexus Components - Version plexus-archiver-2.6.4 > ** Bug > * [PLXCOMP-45] - ignoreWebXML flag use is opposite of what the name > implies. > * [PLXCOMP-107] - Fail to unzip archive, which contains file with name > 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . > * [PLXCOMP-234] - plexus archiver TarOptions setDirMode and setMode do > not do anything unless TarArchiver.setOptions is called > ** Improvement > * [PLXCOMP-250] - Upgrade maven-enforcer-plugin to 1.3.1 > Release Notes - Plexus Components - Version plexus-archiver-2.6.3 > ** Bug > * [PLXCOMP-247] - Bug with windows AND java5 > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux > Release Notes - Plexus Components - Version plexus-archiver-2.6.1 > ** Bug > * [PLXCOMP-243] - Restore JDK1.5 compatibility > Release Notes - Plexus Components - Version plexus-archiver-2.6 > ** Bug > * [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to > fix) > ** Improvement > * [PLXCOMP-64] - add symlink support to tar unarchiver > * [PLXCOMP-117] - add symbolic links managment > Release Notes - Plexus Components - Version plexus-archiver-2.5 > ** Bug > * [PLXCOMP-13] - Plexus Archiver fails on certain Jars > * [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > * [PLXCOMP-216] - Unarchiver extracts files into wrong directory > * [PLXCOMP-232] - Failures to unpack .tar.gz files > * [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** Improvement > * [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > * [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-465) Update version of plexus-archiver from 2.4.4 to 2.9
[ https://jira.codehaus.org/browse/MDEP-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MDEP-465: Summary: Update version of plexus-archiver from 2.4.4 to 2.9 (was: Update version of plexus-archiver from 2.4.4 to 2.7.1) > Update version of plexus-archiver from 2.4.4 to 2.9 > --- > > Key: MDEP-465 > URL: https://jira.codehaus.org/browse/MDEP-465 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.10 > > > Release Notes - Plexus Components - Version plexus-archiver-2.7.1 > Bug > PLXCOMP-256 - Several archivers leaks file handles > Improvement > PLXCOMP-257 - Inconsistent buffering > Release Notes - Plexus Components - Version plexus-archiver-2.7 > ** Bug > * [PLXCOMP-252] - Tar archivers cannot roundtrip own archives on windows, > UTF8 bug > ** Improvement > * [PLXCOMP-253] - Switch default encoding to UTF-8 > Release Notes - Plexus Components - Version plexus-archiver-2.6.4 > ** Bug > * [PLXCOMP-45] - ignoreWebXML flag use is opposite of what the name > implies. > * [PLXCOMP-107] - Fail to unzip archive, which contains file with name > 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . > * [PLXCOMP-234] - plexus archiver TarOptions setDirMode and setMode do > not do anything unless TarArchiver.setOptions is called > ** Improvement > * [PLXCOMP-250] - Upgrade maven-enforcer-plugin to 1.3.1 > Release Notes - Plexus Components - Version plexus-archiver-2.6.3 > ** Bug > * [PLXCOMP-247] - Bug with windows AND java5 > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux > Release Notes - Plexus Components - Version plexus-archiver-2.6.1 > ** Bug > * [PLXCOMP-243] - Restore JDK1.5 compatibility > Release Notes - Plexus Components - Version plexus-archiver-2.6 > ** Bug > * [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to > fix) > ** Improvement > * [PLXCOMP-64] - add symlink support to tar unarchiver > * [PLXCOMP-117] - add symbolic links managment > Release Notes - Plexus Components - Version plexus-archiver-2.5 > ** Bug > * [PLXCOMP-13] - Plexus Archiver fails on certain Jars > * [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > * [PLXCOMP-216] - Unarchiver extracts files into wrong directory > * [PLXCOMP-232] - Failures to unpack .tar.gz files > * [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** Improvement > * [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > * [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-855) Allow failsafe to use actual jar file instead of target/classes
[ https://jira.codehaus.org/browse/SUREFIRE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358284#comment-358284 ] Tibor Digana commented on SUREFIRE-855: --- @Robert thx. Don't worry this is not final. I am running the tests... > Allow failsafe to use actual jar file instead of target/classes > --- > > Key: SUREFIRE-855 > URL: https://jira.codehaus.org/browse/SUREFIRE-855 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin >Affects Versions: 2.12 >Reporter: Benson Margulies >Assignee: Tibor Digana >Priority: Critical > > I've got some code that calls Class.getPackage() to see the manifest. I want > to test it. A seemingly logical scheme here would be to have failsafe put the > actual packaged jar into the classpath instead of the unpacked directory -- > or some way to get the manifest copied across. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINSTALL-102) installAtEnd does not install artifacts for multi-module with packaging maven-archetype
[ https://jira.codehaus.org/browse/MINSTALL-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358283#comment-358283 ] Robert Scholte commented on MINSTALL-102: - [~joerg.sesterhenn], yes please: create one for maven-deploy-plugin as well. But I don't think there are much improvements possible within the scope of the plugins. If Maven thinks that the execution requires multiple ClassLoaderContexts, then there's not much we can do to fix it at this level. You'll have to wait for MNG-5666 and MNG-5667, which will overrule these options in the plugins. > installAtEnd does not install artifacts for multi-module with packaging > maven-archetype > --- > > Key: MINSTALL-102 > URL: https://jira.codehaus.org/browse/MINSTALL-102 > Project: Maven Install Plugin > Issue Type: Bug > Components: install:install >Affects Versions: 2.5.1, 2.5.2 > Environment: Windows 7 / SLES11 >Reporter: Jörg Sesterhenn >Assignee: Robert Scholte > Attachments: test2.zip, test.zip > > > InstallAtEnd does not install any artifacts for multi-module maven-archetype. > See attached minimal example (test.zip). > Same error occurs for deployPlugin! -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-855) Allow failsafe to use actual jar file instead of target/classes
[
https://jira.codehaus.org/browse/SUREFIRE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358282#comment-358282
]
Robert Scholte commented on SUREFIRE-855:
-
[~tibor17], it's much safer to use {{MavenProject.getArtifact().getFile()}}
which is the file being installed/deployed in the end.
> Allow failsafe to use actual jar file instead of target/classes
> ---
>
> Key: SUREFIRE-855
> URL: https://jira.codehaus.org/browse/SUREFIRE-855
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin
>Affects Versions: 2.12
>Reporter: Benson Margulies
>Assignee: Tibor Digana
>Priority: Critical
>
> I've got some code that calls Class.getPackage() to see the manifest. I want
> to test it. A seemingly logical scheme here would be to have failsafe put the
> actual packaged jar into the classpath instead of the unpacked directory --
> or some way to get the manifest copied across.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5626) Avoid negative durations or handle them correctly
[
https://jira.codehaus.org/browse/MNG-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5626:
Assignee: (was: Michael Osipov)
> Avoid negative durations or handle them correctly
> -
>
> Key: MNG-5626
> URL: https://jira.codehaus.org/browse/MNG-5626
> Project: Maven
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.2.1
>Reporter: Christian Jung
>Priority: Minor
>
> In issue MNG-5623 we reported an exception when printing the reactor summary
> if one of the times was negative.
> I saw in one case, that the overall maven build time, as measured from
> outside (i.e. by our QuickBuild system) was -10.8 seconds. The corresponding
> reactor summary was:
> {code}
> 13:55:25,184 INFO - Reactor Summary:
> 13:55:25,184 INFO -
> 13:55:25,184 INFO - module1 ...
> SUCCESS [ 5.911 s]
> 13:55:25,184 INFO - module2 ...
> SUCCESS [ 0.255 s]
> 13:55:25,184 INFO - gpPlaygroundBase-lnx-x64-gcc4 .
> SUCCESS [-27.-64 s]
> 13:55:25,185 INFO -
>
> 13:55:25,185 INFO - BUILD SUCCESS
> 13:55:25,185 INFO -
>
> 13:55:25,185 INFO - Total time: -20.-73 s
> 13:55:25,185 INFO - Finished at: 2014-04-28T13:55:25+01:00
> 13:55:25,572 INFO - Final Memory: 32M/439M
> 13:55:25,572 INFO -
>
> {code}
> The thing is quite hard to reproduce, the machines were virtual machines that
> have been running for quite a long time.
> Our administrators suspected that just at this point, the local clock was
> synchronized with some outer source.
> We should check if such negative durations can be avoided, and if not, they
> should be handled correctly.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-855) Allow failsafe to use actual jar file instead of target/classes
[ https://jira.codehaus.org/browse/SUREFIRE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358281#comment-358281 ] Tibor Digana commented on SUREFIRE-855: --- @Benson @Robert I have opened the GitHub PR for this issue. I guess we would be happy not using any additional ClassLoaders. https://github.com/apache/maven-surefire/pull/72 > Allow failsafe to use actual jar file instead of target/classes > --- > > Key: SUREFIRE-855 > URL: https://jira.codehaus.org/browse/SUREFIRE-855 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin >Affects Versions: 2.12 >Reporter: Benson Margulies >Assignee: Tibor Digana >Priority: Critical > > I've got some code that calls Class.getPackage() to see the manifest. I want > to test it. A seemingly logical scheme here would be to have failsafe put the > actual packaged jar into the classpath instead of the unpacked directory -- > or some way to get the manifest copied across. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-129) Maven PMD plugin does not have suppressMarker property that is available in PMD itself
[ https://jira.codehaus.org/browse/MPMD-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPMD-129. --- Resolution: Fixed Fix Version/s: 3.4 Fixed with [r1642540|http://svn.apache.org/r1642540]. > Maven PMD plugin does not have suppressMarker property that is available in > PMD itself > -- > > Key: MPMD-129 > URL: https://jira.codehaus.org/browse/MPMD-129 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Svetlomira Manova >Assignee: Michael Osipov > Fix For: 3.4 > > Attachments: maven-pmd-patch.zip, mychanges.patch > > > Hi all, > I am trying to change the string that is used to suppress warnings in PMD > report(the default one is NOPMD). I found out that for doing this in PMD > itself i have to use "excludemarker" input param with the custom string. At > the moment i think there is not such property in Maven PMD plugin. > Best regards, > Svetlomira -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-129) Maven PMD plugin does not have suppressMarker property that is available in PMD itself
[ https://jira.codehaus.org/browse/MPMD-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPMD-129: Summary: Maven PMD plugin does not have suppressMarker property that is available in PMD itself (was: Maven PMD plug-in does not have "excludemarker" property that is available in PMD itself.) > Maven PMD plugin does not have suppressMarker property that is available in > PMD itself > -- > > Key: MPMD-129 > URL: https://jira.codehaus.org/browse/MPMD-129 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Svetlomira Manova >Assignee: Michael Osipov > Attachments: maven-pmd-patch.zip, mychanges.patch > > > Hi all, > I am trying to change the string that is used to suppress warnings in PMD > report(the default one is NOPMD). I found out that for doing this in PMD > itself i have to use "excludemarker" input param with the custom string. At > the moment i think there is not such property in Maven PMD plugin. > Best regards, > Svetlomira -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-196) Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT)
[ https://jira.codehaus.org/browse/MPMD-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPMD-196: Issue Type: Task (was: Improvement) > Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT) > --- > > Key: MPMD-196 > URL: https://jira.codehaus.org/browse/MPMD-196 > Project: Maven PMD Plugin > Issue Type: Task > Components: CPD, PMD >Affects Versions: 3.3 >Reporter: Michael Osipov > > See detailed explanation here: > http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-196) Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT)
[ https://jira.codehaus.org/browse/MPMD-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPMD-196: Priority: Minor (was: Major) > Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT) > --- > > Key: MPMD-196 > URL: https://jira.codehaus.org/browse/MPMD-196 > Project: Maven PMD Plugin > Issue Type: Task > Components: CPD, PMD >Affects Versions: 3.3 >Reporter: Michael Osipov >Priority: Minor > > See detailed explanation here: > http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-683) Xref link generation regression with Maven 3
[ https://jira.codehaus.org/browse/SUREFIRE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358275#comment-358275 ] Michael Osipov commented on SUREFIRE-683: - I have reopened it to be conformant with the link issues and this is, I think, one of those bugs which needs to remain open and has been accidentially closed by my blunk cleanup. > Xref link generation regression with Maven 3 > > > Key: SUREFIRE-683 > URL: https://jira.codehaus.org/browse/SUREFIRE-683 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.7.1 > Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) > Java version: 1.6.0_20 > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-27-generic" arch: "i386" Family: "unix" >Reporter: Marc Rohlfs >Priority: Minor > Attachments: SUREFIRE-683_sample.zip > > > When the site reports are created with Maven 3, the this plugin doesn't > generate the links to the Source Xref pages, when the JXR Plugin hasn't been > executed before. > The plugin looks for the xrefLocation directory and if it doesn't exist, it > checks if the JXR plugin is configured for the project (see > http://maven.apache.org/plugins/maven-surefire-report-plugin/xref/org/apache/maven/plugins/surefire/report/SurefireReportMojo.html#203). > To properly generate the Xref links when the report is created with Maven 3, > the plugin should also check the reportPlugins paramerter of the Site plugin > configuration. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-683) Xref link generation regression with Maven 3
[ https://jira.codehaus.org/browse/SUREFIRE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358275#comment-358275 ] Michael Osipov edited comment on SUREFIRE-683 at 11/30/14 5:46 AM: --- I have reopened it to be conformant with the link issues and this is, I think, one of those bugs which needs to remain open and has been accidentially closed by my bulk cleanup. was (Author: michael-o): I have reopened it to be conformant with the link issues and this is, I think, one of those bugs which needs to remain open and has been accidentially closed by my blunk cleanup. > Xref link generation regression with Maven 3 > > > Key: SUREFIRE-683 > URL: https://jira.codehaus.org/browse/SUREFIRE-683 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.7.1 > Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) > Java version: 1.6.0_20 > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-27-generic" arch: "i386" Family: "unix" >Reporter: Marc Rohlfs >Priority: Minor > Attachments: SUREFIRE-683_sample.zip > > > When the site reports are created with Maven 3, the this plugin doesn't > generate the links to the Source Xref pages, when the JXR Plugin hasn't been > executed before. > The plugin looks for the xrefLocation directory and if it doesn't exist, it > checks if the JXR plugin is configured for the project (see > http://maven.apache.org/plugins/maven-surefire-report-plugin/xref/org/apache/maven/plugins/surefire/report/SurefireReportMojo.html#203). > To properly generate the Xref links when the report is created with Maven 3, > the plugin should also check the reportPlugins paramerter of the Site plugin > configuration. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-683) Xref link generation regression with Maven 3
[ https://jira.codehaus.org/browse/SUREFIRE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358274#comment-358274 ] Tibor Digana commented on SUREFIRE-683: --- @Michael You have reopened this bug. Is it in your interest to retest it or resolve? > Xref link generation regression with Maven 3 > > > Key: SUREFIRE-683 > URL: https://jira.codehaus.org/browse/SUREFIRE-683 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.7.1 > Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) > Java version: 1.6.0_20 > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-27-generic" arch: "i386" Family: "unix" >Reporter: Marc Rohlfs >Priority: Minor > Attachments: SUREFIRE-683_sample.zip > > > When the site reports are created with Maven 3, the this plugin doesn't > generate the links to the Source Xref pages, when the JXR Plugin hasn't been > executed before. > The plugin looks for the xrefLocation directory and if it doesn't exist, it > checks if the JXR plugin is configured for the project (see > http://maven.apache.org/plugins/maven-surefire-report-plugin/xref/org/apache/maven/plugins/surefire/report/SurefireReportMojo.html#203). > To properly generate the Xref links when the report is created with Maven 3, > the plugin should also check the reportPlugins paramerter of the Site plugin > configuration. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1057) Surefire doesn't detect TestNG test method which fails because of exception in @DataProvider method
[ https://jira.codehaus.org/browse/SUREFIRE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1057: -- Assignee: Tibor Digana > Surefire doesn't detect TestNG test method which fails because of exception > in @DataProvider method > --- > > Key: SUREFIRE-1057 > URL: https://jira.codehaus.org/browse/SUREFIRE-1057 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.16 >Reporter: Christoph Kutzinski >Assignee: Tibor Digana >Priority: Critical > Attachments: test.zip > > > If you've a TestNG test which fails with exception in a @DataProvider method, > surefire only reports a skipped test, while testng-results.xml clearly shows > a FAIL -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1057) Surefire doesn't detect TestNG test method which fails because of exception in @DataProvider method
[ https://jira.codehaus.org/browse/SUREFIRE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1057: --- Fix Version/s: (was: 2.19) > Surefire doesn't detect TestNG test method which fails because of exception > in @DataProvider method > --- > > Key: SUREFIRE-1057 > URL: https://jira.codehaus.org/browse/SUREFIRE-1057 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.16 >Reporter: Christoph Kutzinski >Assignee: Tibor Digana >Priority: Critical > Attachments: test.zip > > > If you've a TestNG test which fails with exception in a @DataProvider method, > surefire only reports a skipped test, while testng-results.xml clearly shows > a FAIL -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-683) Xref link generation regression with Maven 3
[ https://jira.codehaus.org/browse/SUREFIRE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SUREFIRE-683: Comment: was deleted (was: Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.) > Xref link generation regression with Maven 3 > > > Key: SUREFIRE-683 > URL: https://jira.codehaus.org/browse/SUREFIRE-683 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.7.1 > Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) > Java version: 1.6.0_20 > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-27-generic" arch: "i386" Family: "unix" >Reporter: Marc Rohlfs >Priority: Minor > Attachments: SUREFIRE-683_sample.zip > > > When the site reports are created with Maven 3, the this plugin doesn't > generate the links to the Source Xref pages, when the JXR Plugin hasn't been > executed before. > The plugin looks for the xrefLocation directory and if it doesn't exist, it > checks if the JXR plugin is configured for the project (see > http://maven.apache.org/plugins/maven-surefire-report-plugin/xref/org/apache/maven/plugins/surefire/report/SurefireReportMojo.html#203). > To properly generate the Xref links when the report is created with Maven 3, > the plugin should also check the reportPlugins paramerter of the Site plugin > configuration. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-683) Xref link generation regression with Maven 3
[ https://jira.codehaus.org/browse/SUREFIRE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened SUREFIRE-683: - > Xref link generation regression with Maven 3 > > > Key: SUREFIRE-683 > URL: https://jira.codehaus.org/browse/SUREFIRE-683 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.7.1 > Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) > Java version: 1.6.0_20 > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-27-generic" arch: "i386" Family: "unix" >Reporter: Marc Rohlfs >Priority: Minor > Attachments: SUREFIRE-683_sample.zip > > > When the site reports are created with Maven 3, the this plugin doesn't > generate the links to the Source Xref pages, when the JXR Plugin hasn't been > executed before. > The plugin looks for the xrefLocation directory and if it doesn't exist, it > checks if the JXR plugin is configured for the project (see > http://maven.apache.org/plugins/maven-surefire-report-plugin/xref/org/apache/maven/plugins/surefire/report/SurefireReportMojo.html#203). > To properly generate the Xref links when the report is created with Maven 3, > the plugin should also check the reportPlugins paramerter of the Site plugin > configuration. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-187) Report is generated even when skip is true
[ https://jira.codehaus.org/browse/MPMD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPMD-187. --- Resolution: Fixed Fix Version/s: 3.4 Fixed with [r1642536|http://svn.apache.org/r1642536]. > Report is generated even when skip is true > -- > > Key: MPMD-187 > URL: https://jira.codehaus.org/browse/MPMD-187 > Project: Maven PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 3.1 >Reporter: Ryan Heinen >Assignee: Michael Osipov > Fix For: 3.4 > > > When pmd.skip is true, the XML and/or HTML reports are still generated. Even > though they are empty, generating these files actually takes significant > portion of overall build time time because a velocity engine must be > instantiated. skipEmptyReports doesn't seem to avoid the cost of initializing > the velocity engine. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-187) Report is generated even when skip is true
[
https://jira.codehaus.org/browse/MPMD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358260#comment-358260
]
Michael Osipov edited comment on MPMD-187 at 11/30/14 4:44 AM:
---
[~rheinen],
bq. skipEmptyReports doesn't seem to avoid the cost of initializing the
velocity engine.
if that is the case, then {{skipEmptyReport}} is incorrectly implemented.
Please file another issue for that.
was (Author: michael-o):
Ryan,
bq. skipEmptyReports doesn't seem to avoid the cost of initializing the
velocity engine.
if that is the case, then {{skipEmptyReport}} is incorrectly implemented.
Please file another issue for that.
> Report is generated even when skip is true
> --
>
> Key: MPMD-187
> URL: https://jira.codehaus.org/browse/MPMD-187
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.1
>Reporter: Ryan Heinen
>Assignee: Michael Osipov
>
> When pmd.skip is true, the XML and/or HTML reports are still generated. Even
> though they are empty, generating these files actually takes significant
> portion of overall build time time because a velocity engine must be
> instantiated. skipEmptyReports doesn't seem to avoid the cost of initializing
> the velocity engine.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPMD-196) Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT)
Michael Osipov created MPMD-196: --- Summary: Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT) Key: MPMD-196 URL: https://jira.codehaus.org/browse/MPMD-196 Project: Maven PMD Plugin Issue Type: Improvement Components: CPD, PMD Affects Versions: 3.3 Reporter: Michael Osipov See detailed explanation here: http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-171) Rule properties are ignored when run under MPMD
[
https://jira.codehaus.org/browse/MPMD-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-171.
---
Resolution: Fixed
Fix Version/s: 3.3
3.4
Fixed with [r1642534|http://svn.apache.org/r1642534].
> Rule properties are ignored when run under MPMD
> ---
>
> Key: MPMD-171
> URL: https://jira.codehaus.org/browse/MPMD-171
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.0.1
> Environment: Linux
>Reporter: Johannes Wienke
>Assignee: Michael Osipov
> Fix For: 3.4, 3.3
>
>
> For our project I have defined a custom ruleset for PMD in an XML file [1].
> This ruleset defines properties for some of the standard PMD rules using this
> syntax:
> {noformat}
>
>
>
>
>
> {noformat}
> When I execute PMD using a parallel ant file we maintain, these custom
> properties are respected correctly. However, when executing PMD through
> maven, the properties are completely ignored.
> The pom.xml we are using is available at [2].
> [1]
> https://code.cor-lab.org/projects/rsb/repository/rsb-java/revisions/7e71d4d3e6d57c8529111a7f7143edeb48ddec59/entry/codecheck/pmd-rules.xml
> [2]
> https://code.cor-lab.org/projects/rsb/repository/rsb-java/revisions/ff17c0dd008697f70dad27bd0319f4475ab87712/entry/pom.xml
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MWAR-167) Final manifest not written to exploded location
[ https://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358271#comment-358271 ] Saponenko Denis commented on MWAR-167: -- That's right, decompress the assembly must be identical war. Our version dependencies are displayed in the project and extremely uncomfortable, that they are not in a folder. > Final manifest not written to exploded location > --- > > Key: MWAR-167 > URL: https://jira.codehaus.org/browse/MWAR-167 > Project: Maven WAR Plugin > Issue Type: Bug > Components: manifest >Affects Versions: 2.1-alpha-1 >Reporter: Paul Benedict > Fix For: waiting-for-feedback > > Attachments: mvn167-with-it.diff, patch.diff > > > When I open up my generated WAR file, the Manifest file contains all the > entries I specified. This is correct. However, when I look into the exploded > location, it's just the file I had in my project to begin with. > The exploded Manifest should be updated with the final contents. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-167) Final manifest not written to exploded location
[ https://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358270#comment-358270 ] Karl-Heinz Marbaise commented on MWAR-167: -- Good to hear. Thanks for the feedback. > Final manifest not written to exploded location > --- > > Key: MWAR-167 > URL: https://jira.codehaus.org/browse/MWAR-167 > Project: Maven WAR Plugin > Issue Type: Bug > Components: manifest >Affects Versions: 2.1-alpha-1 >Reporter: Paul Benedict > Fix For: waiting-for-feedback > > Attachments: mvn167-with-it.diff, patch.diff > > > When I open up my generated WAR file, the Manifest file contains all the > entries I specified. This is correct. However, when I look into the exploded > location, it's just the file I had in my project to begin with. > The exploded Manifest should be updated with the final contents. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
