[jira] (MPMD-166) Plugin fails when switching from 2.7.1 to 3.0.1
[
https://jira.codehaus.org/browse/MPMD-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=324841#comment-324841
]
Brett VanderVeen commented on MPMD-166:
---
Should that be documented in the usage?
http://maven.apache.org/plugins/maven-pmd-plugin/examples/usingRuleSets.html
Plugin fails when switching from 2.7.1 to 3.0.1
---
Key: MPMD-166
URL: https://jira.codehaus.org/browse/MPMD-166
Project: Maven 2.x PMD Plugin
Issue Type: Bug
Components: PMD
Affects Versions: 3.0
Reporter: Brett VanderVeen
Priority: Minor
Attachments: console.log, pom.xml
When running {{mvn clean deploy findbugs:findbugs}} on our modular Maven
project, we receive an *BUILD ERROR*: {{[PMD] No report found for mojo pmd}}
I have attached the console log and the pom file where the plugin is included
(parent pom for the project).
All that is changed is the version, from {{2.7.1}} to {{3.0.1}}
--
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-472) No page title is set when using markdown
[ https://jira.codehaus.org/browse/DOXIA-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=324842#comment-324842 ] Steve Moyer commented on DOXIA-472: --- Sure No page title is set when using markdown Key: DOXIA-472 URL: https://jira.codehaus.org/browse/DOXIA-472 Project: Maven Doxia Issue Type: Bug Components: Module - Markdown Affects Versions: 1.3 Reporter: Klaus Reimer Priority: Minor No page title is created for pages which are defined with the markup language markdown. A page in a project named Test opened with Chrome for example has the browser title Test - - Chrome and the browser tab is labeled with Test - . I recommend using the first headline in the markdown file as a page title. -- 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] (ARCHETYPE-436) Error installing a multimodule archetype created with mvn archetype:create-from-project
[ https://jira.codehaus.org/browse/ARCHETYPE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=324845#comment-324845 ] S van Sabben commented on ARCHETYPE-436: Does anyone know a workaround for this problem? Error installing a multimodule archetype created with mvn archetype:create-from-project --- Key: ARCHETYPE-436 URL: https://jira.codehaus.org/browse/ARCHETYPE-436 Project: Maven Archetype Issue Type: Bug Affects Versions: 2.2 Environment: Windows 7 (64 bits), maven 3.0.5, jdk 1.7 Reporter: S van Sabben Priority: Blocker I have a multi module project with a structure like: aggregator (pom) distribution (pom, bin.xml) parent (pom) n x modules(jar) hierarchies multiple level deep Inside the pom the modules reference the parent using: relativePath../project/relativePath I can create an archetype using archetype:create-from-project, and everything runs smoothly. But when I try to install the archetype (mvn install inside the target/generated-sources/archetype dir), I get the error: ERROR] ResourceManager : unable to find resource 'archetype-resources/__rootArtifactId__.aggregator/../__rootArtifactId__.parent/pom.xml' in any resource loader. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 7.818s [INFO] Finished at: Tue May 07 15:46:20 CEST 2013 [INFO] Final Memory: 10M/25M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test (default-integration-test) on project org.svs.archetype.osgi.blueprint.karaf.mul tiproject: [ERROR] Archetype IT 'basic' failed: org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Error merging velocity templates: Unable to find resource 'archetype-resources /__rootArtifactId__.aggregator/../__rootArtifactId__.parent/pom.xml' [ERROR] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test (default-integration-test) on pr oject org.svs.archetype.osgi.blueprint.karaf.multiproject: Archetype IT 'basic' failed: org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Error merging velocity templates: Unable to find resource 'archetype-resources/__rootA rtifactId__.aggregator/../__rootArtifactId__.parent/pom.xml' at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) 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 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Archetype IT 'basic' failed: org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Error merging velocity templates: Unable to find resource 'archetype-resources/__rootA rtifactId__.aggregator/../__rootArtifactId__.parent/pom.xml' at
[jira] (SCM-719) Lack of escaping prevents vertical bars in URLs
Jeremy Sowden created SCM-719: - Summary: Lack of escaping prevents vertical bars in URLs Key: SCM-719 URL: https://jira.codehaus.org/browse/SCM-719 Project: Maven SCM Issue Type: Bug Components: maven-scm-api Affects Versions: 1.8.1 Reporter: Jeremy Sowden Attachments: maven-scm-example.txt org.apache.maven.scm.provider.ScmUrlUtils.java provides no mechanism for escaping delimiters. If the URL is delimited by colons but contains a pipe, the SCM provider is not correctly parsed. I've attached an example. -- 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] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and mvn install not run yet
[
https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=324832#comment-324832
]
Eric Pabst edited comment on MDEP-410 at 5/9/13 2:47 PM:
-
.
was (Author: epabst):
I don't have rights to do so, but the JIRA component is set wrong for this
issue. It should be resolve or collect.
dependency:resolve fails for a multi-module project where one module depends
on another and mvn install not run yet
-
Key: MDEP-410
URL: https://jira.codehaus.org/browse/MDEP-410
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: resolve
Affects Versions: 2.7
Environment: Linux
Reporter: Eric Pabst
When I run dependency:tree on a multi-module project without having run a
mvn install, it fails with this error: {noformat}
[ERROR] Failed to execute goal on project slide-test-module-svn-2: Could not
resolve dependencies for project
org.slide:slide-test-module-svn-2:jar:1.1-SNAPSHOT: The following artifacts
could not be resolved: org.slide:slide-test-module-svn-3:jar:1.1-SNAPSHOT,
org.slide:git-component-for-testing-slide:jar:1.0.b1782: Could not find
artifact org.slide:slide-test-module-svn-3:jar:1.1-SNAPSHOT in maven-central
- [Help 1]
{noformat}
--
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] (MSITE-687) wrong site stage location when parent pom (not in reactor) has same site
[ https://jira.codehaus.org/browse/MSITE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSITE-687. --- Resolution: Fixed Assignee: Herve Boutemy IT added in [r1480749|http://svn.apache.org/r1480749] new parameter added in [r1480752|http://svn.apache.org/r1480752] to permit default value override wrong site stage location when parent pom (not in reactor) has same site Key: MSITE-687 URL: https://jira.codehaus.org/browse/MSITE-687 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:stage(-deploy) Affects Versions: 3.2 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: 3.3 Attachments: MSITE-687.zip problem found when staging Maven 3.1 and Doxia 1.4: root site calculation doesn't restrict to current reactor, but goes as far as the deploy site is the same for Maven 3.1-SNAPSHOT, the consequence wasn't too much: it just staged in target/staging/ref/3.1-LATEST so there was an [easy workaround|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=297bbca90f3d9d8b23d69d2493476b0df81d1de1] for Doxia 1.4, since the Doxia POM distributionManagement url is scm:svn:https://svn.apache.org/repos/infra/websites/production/maven-doxia/content/doxia-archives/doxia-LATEST and the root parent resolved is scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content, the calculated relative path is ../../maven-doxia/content/doxia-archives/doxia-LATEST, then calculated staging directory is maven-doxia/content/doxia-archives/doxia-LATEST (yes, not in target...) -- 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] (MSITE-669) site:stage creates incorrect structure when module paths contains sets of ../
[
https://jira.codehaus.org/browse/MSITE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-669:
Fix Version/s: (was: 3.3)
site:stage creates incorrect structure when module paths contains sets of
../
---
Key: MSITE-669
URL: https://jira.codehaus.org/browse/MSITE-669
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: multi module, relative links, site:stage(-deploy)
Affects Versions: 3.1, 3.2
Reporter: Lennart Jorelid
Assignee: Lukas Theussl
Attachments: msite_669.patch, msite_669_v2.patch, msite_669_v3.patch,
msite_669_v4.patch, nazgul_tools_project_dependencies.png,
nazgul_tools_reactor_structure.png, sample.zip
Given the module definitions given below, the site:stage goal produces sets
of maps relative to the staging directory - i.e. outside of the target
directory.
{code:xml}
modules
module../../validation/validation-api/module
module../../validation/validation-aspect/module
module../parent/module
/modules
{code}
The staged site should be fully included within the staging directory. It
would appear that relativization of links for site:stage should take special
links into consideration.
--
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] (MSITE-596) inheritedReports IT fails
[ https://jira.codehaus.org/browse/MSITE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSITE-596. --- Resolution: Fixed Fix Version/s: (was: backlog) Assignee: Herve Boutemy fixed as a side effect of MNG-5155: Maven 3.0.4 and later have the same behaviour than Maven 2 IT modified in consequence in [r1480782|http://svn.apache.org/r1480782] inheritedReports IT fails - Key: MSITE-596 URL: https://jira.codehaus.org/browse/MSITE-596 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: inheritance, Maven 3 Affects Versions: 3.0-beta-3 Reporter: Herve Boutemy Assignee: Herve Boutemy as discovered in MSITE-595: - with M2, each report is added: child has 2 reports generated = index+summary - with M3, each report replaces previous one: child has 1 report = summary What is the expected behaviour? I'd say M2 is buggy, since POM inheritance logic usually replaces instead adding Should we try to stick with M2 behaviour? (if feasible, I still didn't check) -- 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] (MSITE-686) Report inheritance does not work as specified
[ https://jira.codehaus.org/browse/MSITE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSITE-686. --- Resolution: Fixed Assignee: Herve Boutemy you're right: after some research, the behaviour was fixd in Maven 3.0.4 when fixing MNG-5155, maven-site-plugin IT updated in MNG-596 maven-site-plugin documentation updated in [r1480797|http://svn.apache.org/r1480797] thanks for your report Report inheritance does not work as specified - Key: MSITE-686 URL: https://jira.codehaus.org/browse/MSITE-686 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: inheritance, Maven 3, multi module Affects Versions: 3.2 Environment: Ubuntu 12.04 / Oracle JDK 7u17 / Maven 3.0.5 / m-site-p 3.2 Reporter: Wolf Geldmacher Assignee: Herve Boutemy Fix For: 3.3 Attachments: mvn-site.zip When mvn site is run on the project attached the child project inherits the report configuration from the parent) i.e. the list of reports to generate is not overridden as documented on http://maven.apache.org/plugins/maven-site-plugin/maven-3.html -- 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] (MPIR-226) Tests should not run Jetty on default ports
[
https://jira.codehaus.org/browse/MPIR-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MPIR-226.
---
Resolution: Fixed
Assignee: Herve Boutemy
Already fixed in [r1152625|http://svn.apache.org/r1152625]
Tests should not run Jetty on default ports
---
Key: MPIR-226
URL: https://jira.codehaus.org/browse/MPIR-226
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Environment: Windows 7, running a default Tomcat 6 installation on
port 8080.
Reporter: Dennis Lundberg
Assignee: Herve Boutemy
ProjectInfoReportUtilsTest.testGetInputStreamURL() starts up a Jetty
instance. The different tests communicate with Jetty on the ports 8080 and
8443. If someone, like me, is already running a web or servlet container on
one of those (default) ports, the test will fail with the following output:
{noformat}
Stacktrace
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:211)
at
org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:309)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.Server.doStart(Server.java:228)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.apache.maven.report.projectinfo.ProjectInfoReportUtilsTest.startJetty(ProjectInfoReportUtilsTest.java:235)
at
org.apache.maven.report.projectinfo.ProjectInfoReportUtilsTest.testGetInputStreamURL(ProjectInfoReportUtilsTest.java:148)
Standard Output
@SLTests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.185 sec
@SLRunning org.apache.maven.report.projectinfo.ProjectInfoReportUtilsTest
{noformat}
It would be better to use some non default ports for the tests.
--
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] (MPIR-229) The 'modules' report does not support 'url' elements using properties.
[
https://jira.codehaus.org/browse/MPIR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MPIR-229:
Component/s: modules
The 'modules' report does not support 'url' elements using properties.
--
Key: MPIR-229
URL: https://jira.codehaus.org/browse/MPIR-229
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: modules
Affects Versions: 2.4
Reporter: Christian Schulte
The 'modules' report does not support 'url' elements using properties.
{code:xml}
url${some.property}/${project.artifactId}-${project.version}/url
{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] (MNG-5475) [REGRESSION] repo and pluginRepo with different id's prevent resolution of common parent POM
John Casey created MNG-5475: --- Summary: [REGRESSION] repo and pluginRepo with different id's prevent resolution of common parent POM Key: MNG-5475 URL: https://jira.codehaus.org/browse/MNG-5475 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.5, 3.0.4, 3.1.0-alpha-1 Environment: OS X (10.8.3), JDK 1.6 Reporter: John Casey Priority: Critical Attachments: repo-id-squash.zip I have a settings.xml file with an activated profile that lists one repository and one pluginRepository, both pointing at the same repo (on disk) BUT using different repository id's. In this repository, I have deployed a parent POM and a plugin. The plugin lists the parent POM as its parent. I also have another jar project that uses the parent POM as its parent, and uses the plugin during its build. NOW: When building with Maven 3.0.3, the jar project build completes correctly. But, when I build with ANY VERSION AFTER 3.0.3 (3.0.4, 3.0.5, 3.1.0-alpha-1 from March 30th, io.tesla.maven.apache-maven 3.1.2...even though that's not part of Apache Maven at all) IT FAILS. The specific failure is that it cannot find the common parent POM as it's trying to resolve the plugin. Looking closely at the build logs, you can see Maven resolve the parent POM using the non-plugin repository, and update _maven.repository (I've verified that this non-plugin repository's id is stored here). Then, Maven tries to resolve the plugin POM, sees that the parent POM is in the local repository and isn't set to be updated yet. So, it tries to verify that that parent POM is available via the plugin repositories it knows about...which is where _maven.repository seems to come in. It has the wrong value, and causes Maven to discard the locally cached parent POM. So, Maven won't update this parent POM in the local repo, but refuses to use the one that's there because it came from the wrong place. It seems like Aether is not smart enough to understand that the two repositories are the same, even though the repository-id is different. I suspect this could lead to VERY strange-seeming errors if two projects referenced the same parent POM and repository URL but with different repo-id's. I'm attaching a test case. It contains the repository with the parent POM and the plugin, along with the source projects for each. It also contains the jar project (bar-child) which has a settings.xml file in it. Finally, in the bar-child/ directory you'll find build-*.log files corresponding to each attempt I made with different Maven versions. The root directory is: repo-id-squash/ NOTE: If you want to run the test case, you'll need to modify the paths in the bar-child/settings.xml since they're currently specific to my filesystem. -- 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-5476) [REGRESSION] @required parameter not being enforced.
Chris Graham created MNG-5476:
-
Summary: [REGRESSION] @required parameter not being enforced.
Key: MNG-5476
URL: https://jira.codehaus.org/browse/MNG-5476
Project: Maven 2 3
Issue Type: Bug
Components: POM
Affects Versions: 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0
Reporter: Chris Graham
For a plugin that has the following parameters defined:
{code}
/**
* The message flows to be added to the bar file.
* @parameter expression=${msgFlows}
* @required
*/
private String[] msgFlows;
/**
* The message sets to be added to the bar file.
* @parameter expression=${msgSets}
* @required
*/
private String[] msgSets;
{code}
and a pom config snippet of (note missing the msgSets):
{code:xml}
configuration
msgFlows
msgFlow/
/msgFlows
/configuration
{code}
maven 2.x (2.09 and 2.2.1) will correctly fail with the following error:
{code}
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing for
'message-broker:package-bar-file'
[0] Inside the definition for plugin 'maven-message-broker-plugin' specify the
following:
configuration
...
msgSetsVALUE/msgSets
/configuration
OR
on the command line, specify: '-DmsgSets=VALUE'
{code}
However, maven 3.x (3.0-beta-1 through to 3.0.5) do NOT enforce this.
I would expect the build to be failed in the same manner as 2.x.
--
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
