[jira] (MCHANGES-305) Provide support for private Github repos
[ https://jira.codehaus.org/browse/MCHANGES-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Billerby updated MCHANGES-305: --- Attachment: github-credentials.diff Supplied a patch that adds basic authentication for github reporting. Provide support for private Github repos Key: MCHANGES-305 URL: https://jira.codehaus.org/browse/MCHANGES-305 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: github Reporter: Erik Billerby Attachments: github-credentials.diff The egit-github client provides support for both basic authentication and oauth. It should be pretty easy to implement in the github issue downloader. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-305) Provide support for private Github repos
[ https://jira.codehaus.org/browse/MCHANGES-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Billerby updated MCHANGES-305: --- Attachment: github-credentials-update.patch The second file (named github-credentials-update.patch) is the valid one. The first one contained a change I made to the pom-file which was only for my local build. Provide support for private Github repos Key: MCHANGES-305 URL: https://jira.codehaus.org/browse/MCHANGES-305 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: github Reporter: Erik Billerby Attachments: github-credentials.diff, github-credentials-update.patch The egit-github client provides support for both basic authentication and oauth. It should be pretty easy to implement in the github issue downloader. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINVOKER-149) Possibility to have different settings.xml per IT
[ https://jira.codehaus.org/browse/MINVOKER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar reassigned MINVOKER-149: -- Assignee: (was: Anders Hammar) Possibility to have different settings.xml per IT - Key: MINVOKER-149 URL: https://jira.codehaus.org/browse/MINVOKER-149 Project: Maven 2.x Invoker Plugin Issue Type: Improvement Environment: n/a Reporter: Anders Hammar Attachments: MINVOKER-149_basic-it.patch Today you can only specify a settings.xml that is used for all ITs. It would sometimes be good to be able to specify different settings.xml per IT. That settings should then override the global one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINVOKER-149) Possibility to have different settings.xml per IT
[ https://jira.codehaus.org/browse/MINVOKER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar updated MINVOKER-149: --- Attachment: MINVOKER-149_basic-it.patch Patch with basic IT added Possibility to have different settings.xml per IT - Key: MINVOKER-149 URL: https://jira.codehaus.org/browse/MINVOKER-149 Project: Maven 2.x Invoker Plugin Issue Type: Improvement Environment: n/a Reporter: Anders Hammar Assignee: Anders Hammar Attachments: MINVOKER-149_basic-it.patch Today you can only specify a settings.xml that is used for all ITs. It would sometimes be good to be able to specify different settings.xml per IT. That settings should then override the global one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-483) (SwfMacro) org.apache.maven.plugins:maven-site-plugin:3.2:site: org.apache.maven.doxia.module.apt.AptParser cannot be cast to java.lang.String
[ https://jira.codehaus.org/browse/DOXIA-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320667#comment-320667 ] Manuel Blechschmidt commented on DOXIA-483: --- Hi [~michael-o], is it possible for you to add the attached patch in this ticket to the next DOXIA core release? Thanks a lot Manuel (SwfMacro) org.apache.maven.plugins:maven-site-plugin:3.2:site: org.apache.maven.doxia.module.apt.AptParser cannot be cast to java.lang.String -- Key: DOXIA-483 URL: https://jira.codehaus.org/browse/DOXIA-483 Project: Maven Doxia Issue Type: Bug Components: Core Affects Versions: 1.3 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /usr/share/maven Java version: 1.6.0_41, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac Reporter: Manuel Blechschmidt Attachments: DOXIA-SWF-BUG.patch, DOXIA-SWF-BUG.tgz, Screen Shot 2013-02-22 at 17.56.12.png # Download the attached tgz file # Open a console # Enter tar xzf DOXIA-SWF-BUG.tgz # cd DOXIA-SWF-BUG # run mvn -X site Expected: * System should generate a cool maven site with a cool embedded movie Actual: * Doxia crashes with the following Exception Caused by: java.lang.ClassCastException: org.apache.maven.doxia.module.apt.AptParser cannot be cast to java.lang.String at org.apache.maven.doxia.macro.SwfMacro.execute(SwfMacro.java:57) at org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:120) at org.apache.maven.doxia.module.apt.AptParser$MacroBlock.traverse(AptParser.java:2919) at org.apache.maven.doxia.module.apt.AptParser.traverseSectionBlocks(AptParser.java:861) at org.apache.maven.doxia.module.apt.AptParser.traverseSection(AptParser.java:807) at org.apache.maven.doxia.module.apt.AptParser.traverseBody(AptParser.java:758) at org.apache.maven.doxia.module.apt.AptParser.parse(AptParser.java:228) at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:63) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:401) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) 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) ... 20 more Some of the plugins that I am using are putting a parser variable into one of the maps. This parser variable should be ignored by the SwfMacro but isn't. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-739) Goal eclipse:eclipse very slow
[
https://jira.codehaus.org/browse/MECLIPSE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320668#comment-320668
]
Patrick Decat commented on MECLIPSE-739:
This issue does not occur with Maven 3.1.0 maven-eclipse-plugin:2.9.
Goal eclipse:eclipse very slow
--
Key: MECLIPSE-739
URL: https://jira.codehaus.org/browse/MECLIPSE-739
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: WTP support
Affects Versions: 2.9
Environment: Windows XP, Maven 3
Reporter: Romain N
Priority: Critical
In a multiple project, when I run the goal eclipse:eclipse, the plugin spends
a lot of time to execute it (=~ 12min)
For each submodule, it blocs on this line:
{quote}[INFO] Adding support for WTP version 2.0.{quote}
And when I run the goal in debug mode (-X), I see it spends many time in
dependencies hierarchie, for exemple:
{quote}
[DEBUG] org.springframework:spring-context:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-aop:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] aopalliance:aopalliance:jar:1.0:compile (selected for compile)
[DEBUG] org.springframework:spring-asm:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-beans:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-beans:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-expression:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG] org.springframework:spring-asm:jar:3.0.5.RELEASE:compile
(selected for compile)
[DEBUG]
fr.generali.pdo.fondation.fwk:pdo-framework-logs:jar:1.0.14:compile (selected
for compile)
[DEBUG] ch.qos.logback:logback-classic:jar:0.9.28:compile (selected for
compile)
[DEBUG] ch.qos.logback:logback-core:jar:0.9.28:compile (selected for
compile)
{quote}
In this exemple, the plugin spends 30secondes on the last line.
My maven eclipse configuration is the next:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.9/version
configuration
eclipseDownloadSources combine.self=override /
downloadSources combine.self=overridetrue/downloadSources
downloadJavadocs combine.self=overridetrue/downloadJavadocs
forceRecheck combine.self=overridefalse/forceRecheck
additionalBuildCommands combine.self=override /
additionalProjectnatures combine.self=override /
wtpversion combine.self=override2.0/wtpversion
workspacee:\workspace/workspace --
classpathContainers combine.self=override
classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/classpathContainer
/classpathContainers
/configuration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-483) (SwfMacro) org.apache.maven.plugins:maven-site-plugin:3.2:site: org.apache.maven.doxia.module.apt.AptParser cannot be cast to java.lang.String
[ https://jira.codehaus.org/browse/DOXIA-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320669#comment-320669 ] Manuel Blechschmidt commented on DOXIA-483: --- Hi Oliver, I just triggered Michael for adding my patch to DOXIA 1.4 I just wanted to inform you too. FYI: [~olamy] (SwfMacro) org.apache.maven.plugins:maven-site-plugin:3.2:site: org.apache.maven.doxia.module.apt.AptParser cannot be cast to java.lang.String -- Key: DOXIA-483 URL: https://jira.codehaus.org/browse/DOXIA-483 Project: Maven Doxia Issue Type: Bug Components: Core Affects Versions: 1.3 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /usr/share/maven Java version: 1.6.0_41, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac Reporter: Manuel Blechschmidt Attachments: DOXIA-SWF-BUG.patch, DOXIA-SWF-BUG.tgz, Screen Shot 2013-02-22 at 17.56.12.png # Download the attached tgz file # Open a console # Enter tar xzf DOXIA-SWF-BUG.tgz # cd DOXIA-SWF-BUG # run mvn -X site Expected: * System should generate a cool maven site with a cool embedded movie Actual: * Doxia crashes with the following Exception Caused by: java.lang.ClassCastException: org.apache.maven.doxia.module.apt.AptParser cannot be cast to java.lang.String at org.apache.maven.doxia.macro.SwfMacro.execute(SwfMacro.java:57) at org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:120) at org.apache.maven.doxia.module.apt.AptParser$MacroBlock.traverse(AptParser.java:2919) at org.apache.maven.doxia.module.apt.AptParser.traverseSectionBlocks(AptParser.java:861) at org.apache.maven.doxia.module.apt.AptParser.traverseSection(AptParser.java:807) at org.apache.maven.doxia.module.apt.AptParser.traverseBody(AptParser.java:758) at org.apache.maven.doxia.module.apt.AptParser.parse(AptParser.java:228) at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:63) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:401) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) 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) ... 20 more Some of the plugins that I am using are putting a parser variable into one of the maps. This parser variable should be ignored by the SwfMacro but isn't. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MTOOLCHAINS-5) Look for toolchains.xml in some central place
Göran Uddeborg created MTOOLCHAINS-5:
Summary: Look for toolchains.xml in some central place
Key: MTOOLCHAINS-5
URL: https://jira.codehaus.org/browse/MTOOLCHAINS-5
Project: Maven 2.x Toolchains Plugin
Issue Type: Improvement
Affects Versions: 1.0
Reporter: Göran Uddeborg
From what I understand, the {{toolchains.xml}} file is _only_ looked for in
{{$\{user.home\}/.m2}}. This is quite inconvenient if you want to provide a
central configuration for a large development team. I suggest to look for it
in some central place too. {{$M2_HOME/conf}} would seem to be a natural
place, following the model of {{settings.xml}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-742) Regression in 2.2.2 related to maven-gpg-plugin
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320674#comment-320674 ] Gili commented on MRELEASE-742: --- Confirmed. This works as expected in Maven 3.0.5, Maven Release Plugin 2.4 and maven-gpg-plugin 1.4. Regression in 2.2.2 related to maven-gpg-plugin --- Key: MRELEASE-742 URL: https://jira.codehaus.org/browse/MRELEASE-742 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.2.2 Environment: OS X 10.6, Maven 3.0.3, maven-gpg-plugin 1.4 Reporter: Andres Rodriguez After updating to Release Plugin 2.2.2 gpg plugin fails with error: Cannot obtain passphrase in batch mode Which is thrown (see http://maven.apache.org/plugins/maven-gpg-plugin/xref/org/apache/maven/plugin/gpg/AbstractGpgMojo.html) when the passphrase has not been set and the use agent parameter is false. The passphrase is set in my settings.xml and the useAgent has the default false value. Downgrading to 2.2.1 fixes the problem and the built artifacts are correctly signed. An example POM project can be found at: http://code.google.com/p/derquinse-commons/source/browse/trunk/derquinse-pom/pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-742) Regression in 2.2.2 related to maven-gpg-plugin
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-742. --- Resolution: Not A Bug Assignee: Robert Scholte Regression in 2.2.2 related to maven-gpg-plugin --- Key: MRELEASE-742 URL: https://jira.codehaus.org/browse/MRELEASE-742 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.2.2 Environment: OS X 10.6, Maven 3.0.3, maven-gpg-plugin 1.4 Reporter: Andres Rodriguez Assignee: Robert Scholte After updating to Release Plugin 2.2.2 gpg plugin fails with error: Cannot obtain passphrase in batch mode Which is thrown (see http://maven.apache.org/plugins/maven-gpg-plugin/xref/org/apache/maven/plugin/gpg/AbstractGpgMojo.html) when the passphrase has not been set and the use agent parameter is false. The passphrase is set in my settings.xml and the useAgent has the default false value. Downgrading to 2.2.1 fixes the problem and the built artifacts are correctly signed. An example POM project can be found at: http://code.google.com/p/derquinse-commons/source/browse/trunk/derquinse-pom/pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-3131) Error message is misleading if a missing plugin parameter is of a type like List
[
https://jira.codehaus.org/browse/MNG-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-3131.
---
Resolution: Fixed
Fixed in
[r.f6f4ef5e|http://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=f6f4ef5e]
Error message is misleading if a missing plugin parameter is of a type like
List
Key: MNG-3131
URL: https://jira.codehaus.org/browse/MNG-3131
Project: Maven 2 3
Issue Type: Bug
Reporter: Dennis Lundberg
Assignee: Robert Scholte
Fix For: 3.1.0
Here is a sample output I got when I was working on the changes-plugin:
{code}
[INFO] One or more required plugin parameters are invalid/missing for
'changes:announcement-mail'
[0] inside the definition for plugin: 'maven-changes-plugin'specify the
following:
configuration
...
smtpHostVALUE/smtpHost
/configuration.
[1] inside the definition for plugin: 'maven-changes-plugin'specify the
following:
configuration
...
toAddressesVALUE/toAddresses
/configuration.
{code}
Notice the second parameter toAdresses. It is of the type List, so the
correct configuration would be something like this
{code}
configuration
...
toAddresses
toAddressVALUE/toAddress
/toAddresses
/configuration.
{code}
I haven't found where in the code base the handling of List/Map/Array
parameters is. That code could probably be borrowed/reused in
maven-core/src/main/java/org/apache/maven/plugin/PluginParameterException.java
which is the class responsible for formating the above messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-3131) Error message is misleading if a missing plugin parameter is of a type like List
[
https://jira.codehaus.org/browse/MNG-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-3131:
Component/s: Plugins and Lifecycle
Error message is misleading if a missing plugin parameter is of a type like
List
Key: MNG-3131
URL: https://jira.codehaus.org/browse/MNG-3131
Project: Maven 2 3
Issue Type: Bug
Components: Plugins and Lifecycle
Reporter: Dennis Lundberg
Assignee: Robert Scholte
Fix For: 3.1.0
Here is a sample output I got when I was working on the changes-plugin:
{code}
[INFO] One or more required plugin parameters are invalid/missing for
'changes:announcement-mail'
[0] inside the definition for plugin: 'maven-changes-plugin'specify the
following:
configuration
...
smtpHostVALUE/smtpHost
/configuration.
[1] inside the definition for plugin: 'maven-changes-plugin'specify the
following:
configuration
...
toAddressesVALUE/toAddresses
/configuration.
{code}
Notice the second parameter toAdresses. It is of the type List, so the
correct configuration would be something like this
{code}
configuration
...
toAddresses
toAddressVALUE/toAddress
/toAddresses
/configuration.
{code}
I haven't found where in the code base the handling of List/Map/Array
parameters is. That code could probably be borrowed/reused in
maven-core/src/main/java/org/apache/maven/plugin/PluginParameterException.java
which is the class responsible for formating the above messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1911) Building plugins with extensions in a reactor fails
[
https://jira.codehaus.org/browse/MNG-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-1911:
Description:
I have the following in my main pom
{code:xml}
build
pluginManagement
plugins
plugin
groupIdorg.apache.servicemix.plugins/groupId
artifactIdmaven2-jbi-plugin/artifactId
version1.0-SNAPSHOT/version
extensionstrue/extensions
/plugin
/plugins
/pluginManagement
/build
{code}
If i try to add it to the modules, the first time, maven complains that it can
not download the plugin.
If i remove the {{extensions}} tag, all works, but i need it :)
was:
I have the following in my main pom
build
pluginManagement
plugins
plugin
groupIdorg.apache.servicemix.plugins/groupId
artifactIdmaven2-jbi-plugin/artifactId
version1.0-SNAPSHOT/version
extensionstrue/extensions
/plugin
/plugins
/pluginManagement
/build
If i try to add it to the modules, the first time, maven complains that it can
not download the plugin.
If i remove the extensions tag, all works, but i need it :)
Building plugins with extensions in a reactor fails
---
Key: MNG-1911
URL: https://jira.codehaus.org/browse/MNG-1911
Project: Maven 2 3
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0.1
Reporter: Guillaume Nodet
Priority: Critical
Fix For: 3.2
Attachments: MNG-1911.zip
I have the following in my main pom
{code:xml}
build
pluginManagement
plugins
plugin
groupIdorg.apache.servicemix.plugins/groupId
artifactIdmaven2-jbi-plugin/artifactId
version1.0-SNAPSHOT/version
extensionstrue/extensions
/plugin
/plugins
/pluginManagement
/build
{code}
If i try to add it to the modules, the first time, maven complains that it
can not download the plugin.
If i remove the {{extensions}} tag, all works, but i need it :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-164) Would be it possible to validate Java and Javascript file in one pass?
Florent PAILLARD created MPMD-164: - Summary: Would be it possible to validate Java and Javascript file in one pass? Key: MPMD-164 URL: https://jira.codehaus.org/browse/MPMD-164 Project: Maven 2.x PMD Plugin Issue Type: Wish Components: PMD Reporter: Florent PAILLARD Priority: Minor Attachments: PMD result screenshot.png Hello, It would be really cool to have all Java and Javascript violation reported within the same pmd.xml file. My final goal would be to have everything summarized in the Jenkins PMD result screen (see screenshot attached). I have no idea if PMD / PMD Maven plugin could structurally support that modification. Maybe I should take a totally different approach... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5443) Maven 3.0.5 regression in release:perform: Host name may not be null
[
https://jira.codehaus.org/browse/MNG-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320683#comment-320683
]
Jesse Glick commented on MNG-5443:
--
With {{-e}}:
{code:none}
java.lang.IllegalArgumentException: Host name may not be null
at
org.apache.maven.wagon.providers.http.httpclient.HttpHost.init(HttpHost.java:79)
at
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:501)
at
org.apache.maven.wagon.providers.http.httpclient.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at
org.apache.maven.wagon.providers.http.httpclient.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
at
org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:746)
?
{code}
Debugging made considerably more complicated by lack of deployed
{{*-sources.jar}} for shaded artifacts, but everything looks fine at line 746
at least. Using {{-X}} turned up nothing more of interest.
Setting {{-Dmaven.wagon.http.ssl.insecure=true}} (either on {{mvn}} command
line, or in {{$MAVEN_OPTS}}) as per WAGON-385 did not help. I also tried
{{.allowall}} and {{.ignore.validity.dates}} without luck.
Maven 3.0.5 regression in release:perform: Host name may not be null
--
Key: MNG-5443
URL: https://jira.codehaus.org/browse/MNG-5443
Project: Maven 2 3
Issue Type: Bug
Components: Deployment
Environment: Ubuntu 12.04 32-bit, JDK 7u15
Reporter: Jesse Glick
Priority: Blocker
Attachments: ssl.png
With Maven 3.0.4 deploying to our Artifactory server from {{release:perform}}
works fine:
{code:none}
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ ... ---
Uploading: https://artifactoryonline.com/.../releases/.../8/...-8.pom
Uploaded: https://artifactoryonline.com/.../releases/.../8/...-8.pom (16
KB at 11.1 KB/sec)
{code}
But the same command in Maven 3.0.5 fails:
{code:none}
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ ... ---
Uploading: https://artifactoryonline.com/.../releases/.../8/...-8.pom
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] ...
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
project ...: Failed to deploy artifacts: Could not transfer artifact
...:...:pom:8 from/to ... (https://artifactoryonline.com/.../releases):
Host name may not be null - [Help 1]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-235) Maven Ant Tasks project website provides wrong download link
[ https://jira.codehaus.org/browse/MANTTASKS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320688#comment-320688 ] Maciej Matys commented on MANTTASKS-235: Now website shows 2.1.4-SNAPSHOT as a version right upper corner. Maven Ant Tasks project website provides wrong download link Key: MANTTASKS-235 URL: https://jira.codehaus.org/browse/MANTTASKS-235 Project: Maven 2.x Ant Tasks Issue Type: Bug Affects Versions: 2.1.3 Environment: web browser Reporter: Nathaniel Waisbrot Assignee: Olivier Lamy The project's download page (http://maven.apache.org/ant-tasks/download.html) links to http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-ant-tasks-2.1.3.jar This URL is incorrect. A working URL would be http://www.apache.org/dyn/closer.cgi/maven/ant-tasks/2.1.3/binaries/maven-ant-tasks-2.1.3.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5443) Maven 3.0.5 regression in release:perform: Host name may not be null
[
https://jira.codehaus.org/browse/MNG-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320695#comment-320695
]
Olivier Lamy commented on MNG-5443:
---
it's a sample https://artifactoryonline.com or you really have all dots ?
Maven 3.0.5 regression in release:perform: Host name may not be null
--
Key: MNG-5443
URL: https://jira.codehaus.org/browse/MNG-5443
Project: Maven 2 3
Issue Type: Bug
Components: Deployment
Environment: Ubuntu 12.04 32-bit, JDK 7u15
Reporter: Jesse Glick
Priority: Blocker
Attachments: ssl.png
With Maven 3.0.4 deploying to our Artifactory server from {{release:perform}}
works fine:
{code:none}
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ ... ---
Uploading: https://artifactoryonline.com/.../releases/.../8/...-8.pom
Uploaded: https://artifactoryonline.com/.../releases/.../8/...-8.pom (16
KB at 11.1 KB/sec)
{code}
But the same command in Maven 3.0.5 fails:
{code:none}
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ ... ---
Uploading: https://artifactoryonline.com/.../releases/.../8/...-8.pom
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] ...
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
project ...: Failed to deploy artifacts: Could not transfer artifact
...:...:pom:8 from/to ... (https://artifactoryonline.com/.../releases):
Host name may not be null - [Help 1]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-361) Improve linguistic style of bottom
Michael Osipov created MJAVADOC-361: --- Summary: Improve linguistic style of bottom Key: MJAVADOC-361 URL: https://jira.codehaus.org/browse/MJAVADOC-361 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.9 Reporter: Michael Osipov Priority: Minor Attachments: bottom.patch The current default value of bottom does not adhere to the English language style: 1. A hyphen is used to denote the year ranges which is incorrect. An en dash must be used, see [http://en.wikipedia.org/wiki/En_dash#Ranges_of_values here]. 2. All Rights Reserved includes unnecessary/incorrect capitalization. An appropriate patch has been attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5443) Maven 3.0.5 regression in release:perform: Host name may not be null
[
https://jira.codehaus.org/browse/MNG-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320697#comment-320697
]
Jesse Glick commented on MNG-5443:
--
The actual host name, repo name, and group/artifactId are elided with ? since
they are not publicly readable anyway.
Maven 3.0.5 regression in release:perform: Host name may not be null
--
Key: MNG-5443
URL: https://jira.codehaus.org/browse/MNG-5443
Project: Maven 2 3
Issue Type: Bug
Components: Deployment
Environment: Ubuntu 12.04 32-bit, JDK 7u15
Reporter: Jesse Glick
Priority: Blocker
Attachments: ssl.png
With Maven 3.0.4 deploying to our Artifactory server from {{release:perform}}
works fine:
{code:none}
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ ... ---
Uploading: https://artifactoryonline.com/.../releases/.../8/...-8.pom
Uploaded: https://artifactoryonline.com/.../releases/.../8/...-8.pom (16
KB at 11.1 KB/sec)
{code}
But the same command in Maven 3.0.5 fails:
{code:none}
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ ... ---
Uploading: https://artifactoryonline.com/.../releases/.../8/...-8.pom
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] ...
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
project ...: Failed to deploy artifacts: Could not transfer artifact
...:...:pom:8 from/to ... (https://artifactoryonline.com/.../releases):
Host name may not be null - [Help 1]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
