[jira] (MNG-5686) mvn cannot execute /usr/libexec/java_home/bin/java on OS X.
[
https://jira.codehaus.org/browse/MNG-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed MNG-5686.
---
Resolution: Fixed
Fix Version/s: 3.2.4
Fixed in 44d06d890fd56ce28d9b8eab6d3f3d3d51a9eb94
thanks for the patch !
mvn cannot execute /usr/libexec/java_home/bin/java on OS X.
---
Key: MNG-5686
URL: https://jira.codehaus.org/browse/MNG-5686
Project: Maven
Issue Type: Bug
Components: Command Line
Affects Versions: 3.2.3
Environment: Mac OS X 10.9.4
Reporter: Takayoshi Fujiki
Assignee: Kristian Rosenvold
Fix For: 3.2.4
Attachments: 0001-Fix-whitespace-bashisms-in-mvn-shell-scripts.patch,
0001-Fix-whitespace-bashisms-in-mvn-shell-scripts.v2.patch,
0002-MNG-5686-detect-JAVA_HOME-on-newer-OSX-again.patch, maven-bin-mvn.patch
From 3.2.3, mvn cannot start and outputs the following error.
{code}
$ ./apache-maven-3.2.3/bin/mvn -version
Error: JAVA_HOME is not defined correctly.
We cannot execute /usr/libexec/java_home/bin/java
{code}
3.2.2 doesn't have this problem.
{code}
$ ./apache-maven-3.2.2/bin/mvn -version
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T22:51:42+09:00)
Maven home: /Users/xxx/tmp/apache-maven-3.2.2
Java version: 1.8.0_11, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_11.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.4, arch: x86_64, family: mac
{code}
When I modified {{bin/mvn}} like the following, this problem was gone.
{code}
--- bin/mvn.orig 2014-09-10 03:33:52.0 +0900
+++ bin/mvn 2014-09-10 03:34:18.0 +0900
@@ -83,7 +83,7 @@
#
# Apple JDKs
#
- export JAVA_HOME=/usr/libexec/java_home
+ export JAVA_HOME=`/usr/libexec/java_home`
fi
;;
esac
{code}
Maybe MNG-5658 is related to this problem. {{/usr/libexec/java_home}} is a
command([java_home(1)|https://developer.apple.com/library/mac/documentation/Darwin/Reference/Manpages/man1/java_home.1.html]),
and {{$(command)}} is a style of [Command
Substitution|http://www.tldp.org/LDP/abs/html/commandsub.html] (Another(old)
style is {{`command`}}).
So removing $() breaks the JAVA_HOME detection on OS X.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPMD-174) Using a permalink from sonar as a ruleset does not work
[ https://jira.codehaus.org/browse/MPMD-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359027#comment-359027 ] Michael Osipov commented on MPMD-174: - I will do that as soon as the update of PMD has happened. Using a permalink from sonar as a ruleset does not work --- Key: MPMD-174 URL: https://jira.codehaus.org/browse/MPMD-174 Project: Maven PMD Plugin Issue Type: Bug Reporter: Cremers stijn Assignee: Michael Osipov Fix For: 3.4 Attachments: MPMD-174.patch, MPMD-174.patch, Sonar's main page.jpg I am trying to use a permalink from sonar with the pmd configuration from sonar as a rulest in the maven-pmd-plugin. This is my maven configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version3.0.1/version configuration rulesets rulesethttp://my-tools.mycompany.com/sonar/profiles/export?format=pmdamp;language=javaamp;name=MyProfile/ruleset /rulesets /configuration executions execution idpmd/id goalsgoalcheck/goal/goals /execution /executions /plugin But i get the following error when i run mvn clean install: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-pmd-plugin:3.0.1:pmd (pmd) on project my-pmd: An error has occurred in PMD Report report generation. Could not find resource 'rulesets/http://my/tools.mycompany.com/sonar/profiles.xml'. - [Help 1] I have tried to use the link from the sonar demo site: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version3.0.1/version configuration rulesets rulesethttp://nemo.sonarqube.org/profiles/export?format=pmdamp;language=javaamp;name=Nemo/ruleset /rulesets /configuration executions execution idpmd/id goalsgoalcheck/goal/goals /execution /executions /plugin But then i get the following error: [INFO] --- maven-pmd-plugin:3.0.1:pmd (pmd) @ my-pmd --- [WARNING] Unable to locate Source XRef to link to - DISABLED [WARNING] Failure executing PMD: Couldn't find the class White spaces are required between publicId and systemId. java.lang.RuntimeException: Couldn't find the class White spaces are required between publicId and systemId. at net.sourceforge.pmd.RuleSetFactory.classNotFoundProblem(RuleSetFactory.java:244) at net.sourceforge.pmd.RuleSetFactory.parseRuleSetNode(RuleSetFactory.java:238) at net.sourceforge.pmd.RuleSetFactory.createRuleSet(RuleSetFactory.java:161) at net.sourceforge.pmd.RuleSetFactory.createRuleSets(RuleSetFactory.java:126) at net.sourceforge.pmd.RuleSetFactory.createRuleSets(RuleSetFactory.java:111) at net.sourceforge.pmd.processor.AbstractPMDProcessor.createRuleSets(AbstractPMDProcessor.java:56) at net.sourceforge.pmd.processor.MonoThreadProcessor.processFiles(MonoThreadProcessor.java:41) at net.sourceforge.pmd.PMD.processFiles(PMD.java:271) at org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:296) at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:194) at org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:168) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:99) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) 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.MojoExecutor.executeForkedExecutions(MojoExecutor.java:364) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:198) 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:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at
[jira] (SUREFIRE-1084) Surefire-report stack traces appear on a single line.
[
https://jira.codehaus.org/browse/SUREFIRE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=358963#comment-358963
]
Ulli Hafner edited comment on SUREFIRE-1084 at 12/13/14 5:44 AM:
-
I think the Surefire site report does not show newlines for stacktraces *and*
assertion messages. Here is an example project (branch assignments5):
https://github.com/uhafner/karatest/tree/assignments5
When you run {{mvn clean test -Dmaven.test.failure.ignore=true site}} then the
Surefire report shows the assertion message in a single line. Should I provide
a screenshot or is the project sufficient to reproduce?
was (Author: ulli):
I think the Surefire site report does not show new lines for stacktraces *and*
assertion messages. Here is an example project (branch assignments5):
https://github.com/uhafner/karatest/tree/assignments5
When you run {{mvn clean test -Dmaven.test.failure.ignore=true site}} then the
Surefire report shows the assertion message in a single line. Should I provide
a screenshot or is the project sufficient to reproduce?
Surefire-report stack traces appear on a single line.
-
Key: SUREFIRE-1084
URL: https://jira.codehaus.org/browse/SUREFIRE-1084
Project: Maven Surefire
Issue Type: Bug
Reporter: Josh Eversmann
Priority: Minor
Attachments: Screen Shot 2014-06-30 at 6.40.32 PM.png
The pre tags and line breaks used by SurefireReportGenerator
.constructFailureDetails do not correctly format the stack trace in the
generated page.
Related PR: https://github.com/apache/maven-surefire/pull/41
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5724) Upgrade to last Wagon 2.8
[ https://jira.codehaus.org/browse/MNG-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5724: --- Fix Version/s: 3.2.4 Upgrade to last Wagon 2.8 - Key: MNG-5724 URL: https://jira.codehaus.org/browse/MNG-5724 Project: Maven Issue Type: Improvement Components: Dependencies Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 3.2.4, 3.2.5 h4. Release Notes - Maven Wagon - Version 2.7 h5. Bug * [WAGON-407] - wagon-maven-plugin ITs fail with missing class: org.apache.commons.io.IOUtils * [WAGON-418] - Changes from WAGON-388 broke the WebDAV Wagon * [WAGON-419] - HTTP wagons incorrectly encode blank space in URLs causing resources to be uploaded/looked up with a + sign h5. New Feature * [WAGON-420] - Implements RFC 6585 (return code 429: too many requests) h4. Release Notes - Maven Wagon - Version 2.8 h5. Bug * [WAGON-416] - Lightweight HTTP Wagon doesn't set Proxy-Authorization header * [WAGON-422] - HTTP wagon AuthScope is not definable from settings -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-219) Added m2e mapping
Karl-Heinz Marbaise created MENFORCER-219: - Summary: Added m2e mapping Key: MENFORCER-219 URL: https://jira.codehaus.org/browse/MENFORCER-219 Project: Maven Enforcer Plugin Issue Type: Improvement Components: Plugin Affects Versions: 1.4 Reporter: Karl-Heinz Marbaise Priority: Minor Just adding a simple mapping just to ignore the plugin seemed to be a good choice. Currently m2e itself has a hard coded ignore rule. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-219) Added m2e mapping
[ https://jira.codehaus.org/browse/MENFORCER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MENFORCER-219: -- Fix Version/s: 1.4 Added m2e mapping - Key: MENFORCER-219 URL: https://jira.codehaus.org/browse/MENFORCER-219 Project: Maven Enforcer Plugin Issue Type: Improvement Components: Plugin Affects Versions: 1.4 Reporter: Karl-Heinz Marbaise Priority: Minor Fix For: 1.4 Just adding a simple mapping just to ignore the plugin seemed to be a good choice. Currently m2e itself has a hard coded ignore rule. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-278) Actual Time (GMT) column is all kinds of broken: times wrong, time zones wrong, time zone stretches screen in Firefox
[ https://jira.codehaus.org/browse/MPIR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331862#comment-331862 ] Michael Osipov edited comment on MPIR-278 at 12/13/14 2:11 PM: --- Nicholas, I fully agree that algorithm and display is simply broken. Though, I am not a native speaker, this column should first of all say Current Time and nothing more. The values should be in ISO 8601 format. One could argue whether it is necessary to add tz information to the datetime stamp because the zone is already indicated in the left-hand column. Moment.js would be a perfect solution. There are a few points which need to be considered: 1. Supplying a number instead of a TZ id may lead to shift during DST. 2. Do other devs agree with a third party dep and does the license permit redistribution with ASL? Can we even add dependencies from a report? Do we need to change the site.vm, etc.? 3. What happens when TZ information changes and the page is still up? Wrong calculcation. I would actually like to use Moment.js here and make that column optional during the rendering phase. A dev can still enable it in the POM. WDYT? EDIT: I just double-checked my private projects. My TZ was provided as Europe/Berlin, the report turned that to +1 and there is not an offset of one hour due to DST. So this **is** already broken. was (Author: michael-o): Nicholas, I fully agree that algorithm and display is simply broken. Though, I am not a native speaker, this column should first of all say Current Time and nothing more. The values should be in ISO8601 format. One could argue whether it is necessary to add tz information to the datetime stamp because the zone is already indicated in the left-hand column. Moment.js would be a perfect solution. There are a few points which need to be considered: 1. Supplying a number instead of a TZ id may lead to shift during DST. 2. Do other devs agree with a third party dep and does the license permit redistribution with ASL? Can we even add dependencies from a report? Do we need to change the site.vm, etc.? 3. What happens when TZ information changes and the page is still up? Wrong calculcation. I would actually like to use Moment.js here and make that column optional during the rendering phase. A dev can still enable it in the POM. WDYT? EDIT: I just double-checked my private projects. My TZ was provided as Europe/Berlin, the report turned that to +1 and there is not an offset of one hour due to DST. So this **is** already broken. Actual Time (GMT) column is all kinds of broken: times wrong, time zones wrong, time zone stretches screen in Firefox - Key: MPIR-278 URL: https://jira.codehaus.org/browse/MPIR-278 Project: Maven Project Info Reports Plugin Issue Type: Bug Components: project-team Affects Versions: 2.6 Environment: Chrome, Safari, FireFox, Internet Explorer Reporter: Nicholas Williams Attachments: screenshot.png There are some serious issues with the Actual Time (GMT) column on the generated Project Team page. I describe both issues in detail below, and then analyze and provide a possible solution. These issues all stem from how the JavaScript init() and offsetDate() functions are written. *Problem 1: Dates/Times are not correct* See the attached screenshot for reference. This screenshot was taken on Monday, May 13 at 12:10:32 Central Time. This is 13:10 Eastern Time, 10:10 Pacific Time, and Tuesday 2:10 Tokyo Time. However, the screenshot shows the Central Time row time as 11:10 (an hour behind), the Eastern Time row as 12:10 (an hour behind), and the Pacific Time rows as 9:10 (an hour behind). If this is near the midnight boundary, the dates will be wrong, too. Only the Tokyo Time row is correct. This is a Daylight Savings Time bug. *Problem 2: Time zones are not correct, stretch the screen, and are unnecessary* Even though (with the exception of two) all rows are in different time zones, they all display GMT-0500 (CDT). This is the browser time. If you view this page on a computer in a different time zone, it displays that time zone. This is how it displays in Chrome and Safari. In Internet Explorer, the time zone does not display at all (just date and time). In FireFox, it's worse: GMT-0500 (Central Daylight Time). This last one stretches the screen horizontally and causes other columns to scrunch up, which is not desirable. Really, the time zone isn't even necessary here. There's already a Time Zone column on the page, and it is always displayed when Actual Time (GMT) is displayed. The fact that it's wrong and conflicts with the Time Zone column is confusing. The fact that it
[jira] (MNG-5724) Upgrade to last Wagon 2.8
[ https://jira.codehaus.org/browse/MNG-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5724. -- Resolution: Fixed Fix Version/s: (was: 3.2.5) I just checked in Maven 3.2.3 distribution: jsoup, commons-lang, commons-io and wagon-http-shared were already there so it's not a question for this upgrade from wagon 2.6 to 2.8 if removing libraries from distribution is an issue, please open another Jira issue Upgrade to last Wagon 2.8 - Key: MNG-5724 URL: https://jira.codehaus.org/browse/MNG-5724 Project: Maven Issue Type: Improvement Components: Dependencies Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 3.2.4 h4. Release Notes - Maven Wagon - Version 2.7 h5. Bug * [WAGON-407] - wagon-maven-plugin ITs fail with missing class: org.apache.commons.io.IOUtils * [WAGON-418] - Changes from WAGON-388 broke the WebDAV Wagon * [WAGON-419] - HTTP wagons incorrectly encode blank space in URLs causing resources to be uploaded/looked up with a + sign h5. New Feature * [WAGON-420] - Implements RFC 6585 (return code 429: too many requests) h4. Release Notes - Maven Wagon - Version 2.8 h5. Bug * [WAGON-416] - Lightweight HTTP Wagon doesn't set Proxy-Authorization header * [WAGON-422] - HTTP wagon AuthScope is not definable from settings -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-321) Disable dev/contrib current time generation because it is broken
Michael Osipov created MPIR-321: --- Summary: Disable dev/contrib current time generation because it is broken Key: MPIR-321 URL: https://jira.codehaus.org/browse/MPIR-321 Project: Maven Project Info Reports Plugin Issue Type: Sub-task Components: project-team Affects Versions: 2.7 Reporter: Michael Osipov Currently, the entire current time generation suffers from a design flaw and is most of the time confusing or simply incorrect. MPIR-278 describes it in all glory. We should disable the generation of this column until MPIR-278 is resolved. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-3458) Add Toolchain Requirements to Project Model
[
https://jira.codehaus.org/browse/MNG-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-3458:
---
Description:
Currently, the toolchain plugin will read information from its plugin
configuration
{code:xml} configuration
toolchains
dotnet
vendorMICROSOFT/vendor
frameworkVersion3.0/frameworkVersion
/dotnet
/toolchains
/configuration{code}
This is fine for building but not useful for resolving dependent artifacts from
a repository based on the build platform capabilities. There should be a way to
place the artifact requirements into the project model.
was:
Currently, the toolchain plugin will read information from its plugin
configuration
configuration
toolchains
dotnet
vendorMICROSOFT/vendor
frameworkVersion3.0/frameworkVersion
/dotnet
/toolchains
/configuration
This is fine for building but not useful for resolving dependent artifacts from
a repository based on the build platform capabilities. There should be a way to
place the artifact requirements into the project model.
Add Toolchain Requirements to Project Model
---
Key: MNG-3458
URL: https://jira.codehaus.org/browse/MNG-3458
Project: Maven
Issue Type: Improvement
Components: POM, Toolchains
Affects Versions: 3.0-alpha-1
Reporter: Shane Isbell
Priority: Minor
Fix For: Issues to be reviewed for 3.x
Currently, the toolchain plugin will read information from its plugin
configuration
{code:xml} configuration
toolchains
dotnet
vendorMICROSOFT/vendor
frameworkVersion3.0/frameworkVersion
/dotnet
/toolchains
/configuration{code}
This is fine for building but not useful for resolving dependent artifacts
from a repository based on the build platform capabilities. There should be a
way to place the artifact requirements into the project model.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5724) Upgrade to last Wagon 2.8
[ https://jira.codehaus.org/browse/MNG-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359032#comment-359032 ] Herve Boutemy edited comment on MNG-5724 at 12/13/14 2:45 PM: -- I just checked in Maven 3.2.1 to 3.2.3 distribution: jsoup, commons-lang, commons-io and wagon-http-shared were already there so it's not a question for this upgrade from wagon 2.6 to 2.8: it seems it was an issue with the upgrade from 2.4 to 2.6 done for Maven 3.2.1 if removing libraries from distribution is an issue, please open another Jira issue was (Author: hboutemy): I just checked in Maven 3.2.3 distribution: jsoup, commons-lang, commons-io and wagon-http-shared were already there so it's not a question for this upgrade from wagon 2.6 to 2.8 if removing libraries from distribution is an issue, please open another Jira issue Upgrade to last Wagon 2.8 - Key: MNG-5724 URL: https://jira.codehaus.org/browse/MNG-5724 Project: Maven Issue Type: Improvement Components: Dependencies Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 3.2.4 h4. Release Notes - Maven Wagon - Version 2.7 h5. Bug * [WAGON-407] - wagon-maven-plugin ITs fail with missing class: org.apache.commons.io.IOUtils * [WAGON-418] - Changes from WAGON-388 broke the WebDAV Wagon * [WAGON-419] - HTTP wagons incorrectly encode blank space in URLs causing resources to be uploaded/looked up with a + sign h5. New Feature * [WAGON-420] - Implements RFC 6585 (return code 429: too many requests) h4. Release Notes - Maven Wagon - Version 2.8 h5. Bug * [WAGON-416] - Lightweight HTTP Wagon doesn't set Proxy-Authorization header * [WAGON-422] - HTTP wagon AuthScope is not definable from settings -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5724) Upgrade to last Wagon 2.8
[ https://jira.codehaus.org/browse/MNG-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359032#comment-359032 ] Herve Boutemy edited comment on MNG-5724 at 12/13/14 2:47 PM: -- I just checked in Maven 3.2.1 to 3.2.3 distribution: jsoup, commons-lang, commons-io and wagon-http-shared were already there so it's not a question for this upgrade from wagon 2.6 to 2.8: it seems it was an issue with the upgrade from 2.4 to 2.6 done for Maven 3.2.1 in MNG-5559 if removing libraries from distribution is an issue, please open another Jira issue was (Author: hboutemy): I just checked in Maven 3.2.1 to 3.2.3 distribution: jsoup, commons-lang, commons-io and wagon-http-shared were already there so it's not a question for this upgrade from wagon 2.6 to 2.8: it seems it was an issue with the upgrade from 2.4 to 2.6 done for Maven 3.2.1 if removing libraries from distribution is an issue, please open another Jira issue Upgrade to last Wagon 2.8 - Key: MNG-5724 URL: https://jira.codehaus.org/browse/MNG-5724 Project: Maven Issue Type: Improvement Components: Dependencies Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 3.2.4 h4. Release Notes - Maven Wagon - Version 2.7 h5. Bug * [WAGON-407] - wagon-maven-plugin ITs fail with missing class: org.apache.commons.io.IOUtils * [WAGON-418] - Changes from WAGON-388 broke the WebDAV Wagon * [WAGON-419] - HTTP wagons incorrectly encode blank space in URLs causing resources to be uploaded/looked up with a + sign h5. New Feature * [WAGON-420] - Implements RFC 6585 (return code 429: too many requests) h4. Release Notes - Maven Wagon - Version 2.8 h5. Bug * [WAGON-416] - Lightweight HTTP Wagon doesn't set Proxy-Authorization header * [WAGON-422] - HTTP wagon AuthScope is not definable from settings -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5559) upgrade to last wagon 2.6
[ https://jira.codehaus.org/browse/MNG-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5559: --- Description: Release Notes - Maven Wagon - Version 2.5 ** Bug * [WAGON-381] - Both Maven 2 and 3 fail to retrieve a dependency that is larger than Integer.MAX_VALUE * [WAGON-384] - Maven fails to download artifacts larger than 2 GB * [WAGON-394] - upgrade commons-logging to 1.1.2 * [WAGON-395] - intermittent ProtocolException: The server failed to respond with a valid HTTP response * [WAGON-399] - Fix for SFTP on windows machine ** Improvement * [WAGON-388] - remove wagon-http-shared4 dependency on httpclient Release Notes - Maven Wagon - Version 2.6 ** Improvement * [WAGON-401] - Access Denied due to missing User-Agent * [WAGON-402] - Upgrade Apache HttpClient based wagon provider to HttpClient 4.3 * [WAGON-403] - SSH agent support for wagon-ssh upgrade to last wagon 2.6 - Key: MNG-5559 URL: https://jira.codehaus.org/browse/MNG-5559 Project: Maven Issue Type: Bug Components: Dependencies Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 3.2.1 Release Notes - Maven Wagon - Version 2.5 ** Bug * [WAGON-381] - Both Maven 2 and 3 fail to retrieve a dependency that is larger than Integer.MAX_VALUE * [WAGON-384] - Maven fails to download artifacts larger than 2 GB * [WAGON-394] - upgrade commons-logging to 1.1.2 * [WAGON-395] - intermittent ProtocolException: The server failed to respond with a valid HTTP response * [WAGON-399] - Fix for SFTP on windows machine ** Improvement * [WAGON-388] - remove wagon-http-shared4 dependency on httpclient Release Notes - Maven Wagon - Version 2.6 ** Improvement * [WAGON-401] - Access Denied due to missing User-Agent * [WAGON-402] - Upgrade Apache HttpClient based wagon provider to HttpClient 4.3 * [WAGON-403] - SSH agent support for wagon-ssh -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5430) use wagon 2.4
[ https://jira.codehaus.org/browse/MNG-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5430: --- Description: Release Notes - Maven Wagon - Version 2.3 ** Bug * [WAGON-367] - Very large number of temporary files http-wagon.*.tmp if wagon is used in a long time running JVM (like a CI server) * [WAGON-369] - wagon http doesn't follow HTTP 302 redirects for PUT * [WAGON-370] - Adding additional wagon provider as dependency does not work * [WAGON-371] - for security reason preemptive must be off by default for GET * [WAGON-379] - webdav site deployement fail with mvn 2.2.1 ** Improvement * [WAGON-368] - Support NTLM authentication in webdav * [WAGON-380] - webdav wagon 1.6 requires Release Notes - Maven Wagon - Version 2.4 ** Bug * [WAGON-372] - SSL client-side certificates stopped working in maven 3.0.4 * [WAGON-383] - Regression for SSLv3 * [WAGON-385] - some securities check are disabled per default (change the off per default) * [WAGON-386] - build failure with jdk 1.7 * [WAGON-387] - Remove default easy ssl mode use wagon 2.4 - Key: MNG-5430 URL: https://jira.codehaus.org/browse/MNG-5430 Project: Maven Issue Type: Bug Components: Dependencies Affects Versions: 3.0.4 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Blocker Fix For: 3.0.5, 3.1.0-alpha-1 Release Notes - Maven Wagon - Version 2.3 ** Bug * [WAGON-367] - Very large number of temporary files http-wagon.*.tmp if wagon is used in a long time running JVM (like a CI server) * [WAGON-369] - wagon http doesn't follow HTTP 302 redirects for PUT * [WAGON-370] - Adding additional wagon provider as dependency does not work * [WAGON-371] - for security reason preemptive must be off by default for GET * [WAGON-379] - webdav site deployement fail with mvn 2.2.1 ** Improvement * [WAGON-368] - Support NTLM authentication in webdav * [WAGON-380] - webdav wagon 1.6 requires Release Notes - Maven Wagon - Version 2.4 ** Bug * [WAGON-372] - SSL client-side certificates stopped working in maven 3.0.4 * [WAGON-383] - Regression for SSLv3 * [WAGON-385] - some securities check are disabled per default (change the off per default) * [WAGON-386] - build failure with jdk 1.7 * [WAGON-387] - Remove default easy ssl mode -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-208) Reduce the size of Repository locations for each of the Dependencies.
[ https://jira.codehaus.org/browse/MPIR-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-208. --- Resolution: Won't Fix Cleanup, reopen if you still care. Reduce the size of Repository locations for each of the Dependencies. - Key: MPIR-208 URL: https://jira.codehaus.org/browse/MPIR-208 Project: Maven Project Info Reports Plugin Issue Type: Improvement Components: dependencies Affects Versions: 2.2 Reporter: Vincent Siveton If no artefacts in column repo, this column should be not listed for increase the reading. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-107) Add configuration for the Project Dependency Graph / Dependency Tree
[
https://jira.codehaus.org/browse/MPIR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-107.
---
Resolution: Won't Fix
Cleanup, reopen if you still care.
Add configuration for the Project Dependency Graph / Dependency Tree
Key: MPIR-107
URL: https://jira.codehaus.org/browse/MPIR-107
Project: Maven Project Info Reports Plugin
Issue Type: Improvement
Components: dependencies
Reporter: Arnaud
Like we can configure the tree in the maven-dependency-plugin
(http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html),
Why we can't configure the tree in this plugin ?
In my project, i 'd like show only module of my compagny in the tree, and if
there are conflict.
so i 'd like use this configuration (it works with the commande : mvn
dependency:tree )
{code}
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version${versionDependency}/version
configuration
includesnet.mycompany.*/includes
verbosetrue/verbose
/configuration
/plugin
/plugins
/build
{code}
thank you
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-149) Add a qualityManagement goal
[ https://jira.codehaus.org/browse/MPIR-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359035#comment-359035 ] Michael Osipov edited comment on MPIR-149 at 12/13/14 4:21 PM: --- Can you add a patch running off current trunk otherwise I will close this issue by the end of the year? was (Author: michael-o): Can you add a patch running off current trunk otherwise I will close this issue by the end of the year. Add a qualityManagement goal Key: MPIR-149 URL: https://jira.codehaus.org/browse/MPIR-149 Project: Maven Project Info Reports Plugin Issue Type: Wish Reporter: Xavier Chatelain Priority: Minor Attachments: MPIR-149_maven-2.0.x.patch, MPIR-149_maven-2.1.x.patch, MPIR-149_maven-project-info-reports-plugin.patch More and more projects use an external quality management tool. So it would be interesting to add a qualityManagement goal similar to the cim and issueTracking goals. With this goal, user could add this kind of configuration in his pom.xml: qualityManagement systemsonar/system urlhttp://host/sonar/myProject/url /ciManagement -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-149) Add a qualityManagement goal
[ https://jira.codehaus.org/browse/MPIR-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359035#comment-359035 ] Michael Osipov commented on MPIR-149: - Can you add a patch running off current trunk otherwise I will close this issue by the end of the year. Add a qualityManagement goal Key: MPIR-149 URL: https://jira.codehaus.org/browse/MPIR-149 Project: Maven Project Info Reports Plugin Issue Type: Wish Reporter: Xavier Chatelain Priority: Minor Attachments: MPIR-149_maven-2.0.x.patch, MPIR-149_maven-2.1.x.patch, MPIR-149_maven-project-info-reports-plugin.patch More and more projects use an external quality management tool. So it would be interesting to add a qualityManagement goal similar to the cim and issueTracking goals. With this goal, user could add this kind of configuration in his pom.xml: qualityManagement systemsonar/system urlhttp://host/sonar/myProject/url /ciManagement -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-267) With Maven 3, Dependency Repository Locations links artifacts with my local repository manager id and url instead of public repository info
[ https://jira.codehaus.org/browse/MPIR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359037#comment-359037 ] Michael Osipov commented on MPIR-267: - Hervé, does this issue still apply to trunk? If not, I'd like to cose with not a bug. With Maven 3, Dependency Repository Locations links artifacts with my local repository manager id and url instead of public repository info - Key: MPIR-267 URL: https://jira.codehaus.org/browse/MPIR-267 Project: Maven Project Info Reports Plugin Issue Type: Bug Components: dependencies Affects Versions: 2.4, 2.6 Reporter: Herve Boutemy MPIR-244 fixed the issue in the first table of the Dependency Repository Locations section but the next table still has the issue: the header of the table gives the mirror id and the link to download the artifact points to the repository manager -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-230) Enable inheritance of custom properties
[ https://jira.codehaus.org/browse/MPIR-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-230. --- Resolution: Won't Fix Cleanup, reopen if you still care. Enable inheritance of custom properties --- Key: MPIR-230 URL: https://jira.codehaus.org/browse/MPIR-230 Project: Maven Project Info Reports Plugin Issue Type: Improvement Environment: http://mail-archives.apache.org/mod_mbox/maven-users/201108.mbox/%3CCAOGo0VY7r=-3AofJ56Hu0+R4uf_nADEEbHYpusJ6hnJA=wf...@mail.gmail.com%3E Reporter: sebbaz+ch Custom properties were added recently; these allow (e.g.) the mail page to be nicely customised. This works fine for a single module project, but it appears to be tricky to share the properties easily between modules. It would be very useful if the plugin supported custom properties defined in a parent POM. One possibly method would be to allow references to properties defined in a jar, rather than in the filing system. However, this would still require the jar to be created and deployed. If the custom properties could be treated more like site.xml, that would be ideal. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-35) Site Plugin should work from Template. Plugin Should not generate Markup from Java
[ https://jira.codehaus.org/browse/MPIR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-35: --- Fix Version/s: (was: 2.x) Site Plugin should work from Template. Plugin Should not generate Markup from Java --- Key: MPIR-35 URL: https://jira.codehaus.org/browse/MPIR-35 Project: Maven Project Info Reports Plugin Issue Type: New Feature Reporter: Tim O'Brien Attachments: maven-project-info-reports.patch, project-info-itest.zip The site plugin currently generates markup from Java. There is logic in the team list report that prints HTML and Javascript directly to a StringBuffer and there is no facility for customization. Because of this, every single site that uses the project info reports ends up with the same text. Google for the text of the team-list plugin and there are at least 18,000 matching pages. There needs to be a facility for customization. I propose that the default report is published from a velocity template loaded form the classpath, but the site plugin checks for the presence of an overriding velocity template in a know path (or from a URL). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-268) Add Gradle dependency information
[ https://jira.codehaus.org/browse/MPIR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-268. --- Resolution: Won't Fix Seems like no Gradle user cares and I (the reporter) use Maven only. Closing this. Add Gradle dependency information - Key: MPIR-268 URL: https://jira.codehaus.org/browse/MPIR-268 Project: Maven Project Info Reports Plugin Issue Type: Bug Components: dependency-info Affects Versions: 2.6 Reporter: Michael Osipov The Dependency Information report is missing a Gradle dependency snippet. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-35) Site Plugin should work from Template. Plugin Should not generate Markup from Java
[ https://jira.codehaus.org/browse/MPIR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-35. -- Resolution: Won't Fix Cleanup, reopen if you still care. Site Plugin should work from Template. Plugin Should not generate Markup from Java --- Key: MPIR-35 URL: https://jira.codehaus.org/browse/MPIR-35 Project: Maven Project Info Reports Plugin Issue Type: New Feature Reporter: Tim O'Brien Attachments: maven-project-info-reports.patch, project-info-itest.zip The site plugin currently generates markup from Java. There is logic in the team list report that prints HTML and Javascript directly to a StringBuffer and there is no facility for customization. Because of this, every single site that uses the project info reports ends up with the same text. Google for the text of the team-list plugin and there are at least 18,000 matching pages. There needs to be a facility for customization. I propose that the default report is published from a velocity template loaded form the classpath, but the site plugin checks for the presence of an overriding velocity template in a know path (or from a URL). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-17) Create XML documents containing report data.
[ https://jira.codehaus.org/browse/MPIR-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359040#comment-359040 ] Michael Osipov commented on MPIR-17: Is this issue still valid? Create XML documents containing report data. Key: MPIR-17 URL: https://jira.codehaus.org/browse/MPIR-17 Project: Maven Project Info Reports Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3 Reporter: Chris Hagmann Fix For: 2.x Original Estimate: 10 hours Remaining Estimate: 10 hours It would be a huge improvement if each report was written as as XML document before optionally rendering it. If you did that, then other plugins could use those XML reports, apply XSLT or whatever to generate their own version of a report. It would make the whole reporting thing much more flexible. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-283) CLONE - Announce e-mail and project website must reference source download page
[ https://jira.codehaus.org/browse/MPIR-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359041#comment-359041 ] Michael Osipov commented on MPIR-283: - Why is this a bug in MPIR? CLONE - Announce e-mail and project website must reference source download page --- Key: MPIR-283 URL: https://jira.codehaus.org/browse/MPIR-283 Project: Maven Project Info Reports Plugin Issue Type: Bug Reporter: Robert Scholte Priority: Blocker The ASF releases source. As such, announcements must link to the download page, and the component website must also link to the download page. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-252) Dependency Management report doesn't exclude system scoped dependencies
[
https://jira.codehaus.org/browse/MPIR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359042#comment-359042
]
Michael Osipov commented on MPIR-252:
-
Is this issue still valid?
Dependency Management report doesn't exclude system scoped dependencies
---
Key: MPIR-252
URL: https://jira.codehaus.org/browse/MPIR-252
Project: Maven Project Info Reports Plugin
Issue Type: Bug
Components: dependency-management
Affects Versions: 2.5.1
Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
Reporter: Martijn Verburg
{noformat}
[WARNING] Unable to create Maven project for com.sun:tools:pom:localVersion
from repository.
org.apache.maven.project.ProjectBuildingException: Error resolving project
artifact: Failure to find com.sun:tools:pom:localVersion in
http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the
local repository, resolution will not be reattempted until the update
interval of jclarity-central has elapsed or updates are forced for project
com.sun:tools:pom:localVersion
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:296)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:237)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:204)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:157)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:146)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:132)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:112)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
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:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
[jira] (MPIR-251) Artifact ###### has no file error regression.
[
https://jira.codehaus.org/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359043#comment-359043
]
Michael Osipov commented on MPIR-251:
-
Is this issue still valid?
Artifact ## has no file error regression.
-
Key: MPIR-251
URL: https://jira.codehaus.org/browse/MPIR-251
Project: Maven Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 2.5
Reporter: Ian Brandt
Priority: Minor
Attachments: pom.xml
It appears that MPIR-158 has regressed. I'm seeing the same exact issue in
2.5 with Maven 3.0.4:
{noformat}
[INFO] Generating Dependencies report---
maven-project-info-reports-plugin:2.5
[ERROR] Artifact: com.sun:tools:jar:1.5.0 has no file.
[ERROR] Artifact: com.thoughtworks.xstream:xstream:jar:1.3 has no file.
[ERROR] Artifact: commons-beanutils:commons-beanutils:jar:1.8.0 has no file.
[ERROR] Artifact: commons-cli:commons-cli:jar:1.1 has no file.
[ERROR] Artifact: commons-codec:commons-codec:jar:1.3 has no file.
[ERROR] Artifact: commons-collections:commons-collections:jar:3.2.1 has no
file.
[ERROR] Artifact: commons-digester:commons-digester:jar:2.0 has no file.
[ERROR] Artifact: commons-fileupload:commons-fileupload:jar:1.2.2 has no file.
...{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
