[jira] (MPIR-251) Artifact ###### has no file error regression.
[
https://jira.codehaus.org/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335351#comment-335351
]
Steve Brown commented on MPIR-251:
--
This issue affects version 2.7 running on Maven 3.0.4. I have reproduced the
behaviour of a project with Oracle jar file dependencies. The issue occurs only
when there are Oracle jar files (e.g. ojdbc16.jar) in the dependencies.
> 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 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] (MASSEMBLY-670) Specifying option of causes timestamps not to be preserved
[ https://jira.codehaus.org/browse/MASSEMBLY-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335353#comment-335353 ] Kristian Rosenvold commented on MASSEMBLY-670: -- I have looked a bit at this one, and it turns out to be a substantial change. Files are added to the assembly based on *actual* file system attributes (as they exist on disk somewhere), and when lineEnding or filtering is active, a copy is made elsewhere with filtering applied. AFAIK java cannot set the actual creation date on these newly created files. The API in plexus archiver (the underlying archive creator) does not allow us to supply information like file creation date on a per-file level, which is one version of what we'd need to make this work. Alternately plexus-archiver could accept some kind of filtering callback to do the filtering itself just as the file is written to disk. (I am talking a bit out loud here...) I am partial to moving the logic in org.apache.maven.plugin.assembly.format.FileSetFormatter#formatFileSetForAssembly to a callback that is applied directly to the stream in plexus-archiver; in that way we could avoid copying entirely for the filtering. (The file is actually rewritten a number of times for filtering/copying, so this change kind-of makes sense). I am not in a position to give any kind of promise regarding implementing such a feature. The filtering feature in plexus-archiver sounds like a fun patch to do, but it's a bit of a job. Btw: A side effect of all this is that if you can create multiple filesets, some with and some without filtering, you might be able to preserve *some* attributes. > Specifying option of causes timestamps not to be > preserved > - > > Key: MASSEMBLY-670 > URL: https://jira.codehaus.org/browse/MASSEMBLY-670 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: component descriptor >Affects Versions: 2.4 > Environment: linux >Reporter: Steve Cohen > > (Summary originally was "assembly plugin tar.gz format does not preserve > timestamps of files it adds to archive". Changed to reflect actual issue > discovered through investigation.) > The .tar.gz archives created by the assembly plugin do not preserve the > timestamps of the files it adds to the archive. There is no setting to > override this. > This differs from the functionality of the tar program. That program > preserves timestamps by default, when adding to the archive and there is no > option to change this, although there are options to change the timestamps on > extraction. > The maven plugin should emulate tar here, I would think. -- 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-837) Release plugin resets parent to outdated version
[ https://jira.codehaus.org/browse/MRELEASE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335354#comment-335354 ] Markus KARG commented on MRELEASE-837: -- I reproduced this today and the bug still exists. As you can see, the plugin asks what the next development snapshot of parent is, and suggests 1.1-SNAPSHOT. I agreed to this, everything works without any error message, but after that the POM still uses the OLD 1.0-SNAPSHOT parent! POM before release: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 my-artifact 1.1-SNAPSHOT my-artifact my.group my-parent 1.0-SNAPSHOT scm:svn:svn://svn/Research/my-artifact/trunk releases http://nexus.quipsy.local/nexus/content/repositories/releases snapshots http://nexus.quipsy.local/nexus/content/repositories/snapshots Preparing and performing the release: C:\Users\Markus Karg\workspace\artifact\my-artifact>mvn release:prepare release:perform [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building my-artifact 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-release-plugin:2.0:prepare (default-cli) @ my-artifact --- [INFO] Verifying that there are no local modifications... [INFO] Executing: cmd.exe /X /C "svn --non-interactive status" [INFO] Working directory: C:\Users\Markus Karg\workspace\artifact\my-artifact [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : Resolve Project Dependency Snapshots.: 'my.group:my-parent' set to release? (yes/no) yes: : What is the next development version? (1.1-SNAPSHOT) 1.1-SNAPSHOT: : What is the release version for "my-artifact"? (my.group:my-artifact) 1.0: : What is SCM release tag or label for "my-artifact"? (my.group:my-artifact) my-artifact-1.0: : What is the new development version for "my-artifact"? (my.group:my-artifact) 1.1-SNAPSHOT: : [INFO] Transforming 'my-artifact'... [INFO] Not generating release POMs [INFO] Executing goals 'clean verify'... [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance. [INFO] [INFO] Scanning for projects... [INFO] [INFO] [INFO] [INFO] [INFO] [INFO] Building my-artifact 1.0 [INFO] [INFO] [INFO] [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ my-artifact --- [INFO] [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ my-artifact --- [INFO] [debug] execute contextualize [INFO] [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] [INFO] skip non existing resourceDirectory C:\Users\Markus Karg\workspace\artifact\my-artifact\src\main\resources [INFO] [INFO] [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ my-artifact --- [INFO] [INFO] No sources to compile [INFO] [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ my-artifact --- [INFO] [debug] execute contextualize [INFO] [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] [INFO] skip non existing resourceDirectory C:\Users\Markus Karg\workspace\artifact\my-artifact\src\test\resources [INFO] [INFO] [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ my-artifact --- [INFO] [INFO] No sources to compile [INFO] [INFO] [INFO] [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ my-artifact --- [INFO] [INFO] No tests to run. [INFO] [INFO] Surefire report directory: C:\Users\Markus Karg\workspace\artifact\my-artifact\target\surefire-reports [INFO] [INFO] --- [INFO] T E S T S [INFO] --- [INFO] [INFO] Results : [INFO] [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] [INFO] [INFO] [INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ my-artifact --- [INFO] [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] [INFO] Building jar: C:\Users\Markus Karg\workspace\artifact\my-artifact\target\my-artifact-1.0.jar [INFO] [INFO] ---
[jira] (MRELEASE-767) releasing flat multi-module projects using git
[ https://jira.codehaus.org/browse/MRELEASE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335355#comment-335355 ] Christoph Lenggenhager commented on MRELEASE-767: - What is the status here? The possibilities to fix this where it actually breaks are not that nice, but the above patch is actually working. It would be great to have this fixed in a release of the near future. It basically prevents anyone to use git, maven and eclipse in a flat multi-mode project. > releasing flat multi-module projects using git > -- > > Key: MRELEASE-767 > URL: https://jira.codehaus.org/browse/MRELEASE-767 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.3.1 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800) > Maven home: /usr/share/maven > Java version: 1.6.0_31, 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.4", arch: "x86_64", family: "mac" >Reporter: Jeremy Norris >Assignee: Mark Struberg > > When releasing a project as follows: > ./parent/pom.xml > ./module-a/pom.xml > ./module-b/pom.xml > From the parent directory, with an scm config in the parent pom.xml (only) as > follows: > > scm:git:ssh://github.com/repox.git > > scm:git:ssh://github.com/repox.git > master > https://github.com/view/repox.git > > In org/apache/maven/shared/release/util/ReleaseUtils.java:182 it does this > indiscriminately: > url = realignScmUrl( parentLevels, url ); > This will trim the repo url from 'ssh://github.com/repox.git' -> > 'ssh://github.com', which will cause a failure when pushing the tag. > This type of realignment is not appropriate when using a git scm type. -- 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-tabpanel&focusedCommentId=335359#comment-335359 ] Hendrik Schreiber commented on DOXIA-472: - Browsing the source via browser seems to be broken. => https://jira.codehaus.org/browse/DOXIA#selectedTab=com.atlassian.jirafisheyeplugin%3Afisheye-projectpanel May I ask, how you fixed this? Is the first encountered Markdown headline turned into the title? Does the Markdown header have to be of a certain level? Thanks! > 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 > Fix For: 1.5 > > > 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 - ". A live example on Maven site: > [maven-jsr330.html|http://maven.apache.org/maven-jsr330.html] done from > [maven-jsr330.md|https://svn.apache.org/repos/asf/maven/site/trunk/content/markdown/maven-jsr330.md] > 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] (MEAR-160) Performance regression while copying artifacts into ear
[ https://jira.codehaus.org/browse/MEAR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335360#comment-335360 ] Mark Howard commented on MEAR-160: -- I've also found this problem on my projects, 30s with 2.8, 8s with 2.9-SNAPSHOT, not with any unpacking. With the attached project I am seeing a good improvement: 2.8 51s 2.9-SNAPSHOT 19.232s Is it possible to get a release of 2.9 with the improvements so far? > Performance regression while copying artifacts into ear > --- > > Key: MEAR-160 > URL: https://jira.codehaus.org/browse/MEAR-160 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 > Environment: Intel Core i3 : Arch Linux 64-bit : Kernel 3.6.2 : ext4 > filesystem : JDK 7u9 >Reporter: Joseph Freeman >Assignee: Olivier Lamy > Fix For: 2.9 > > Attachments: test.zip > > > Just upgraded the maven ear plugin from 2.7 to 2.8 and it's now taking double > the time to build my project. The time increase happens when my jars and war > are being copied into the ear as unpacked artifacts. Packed artifacts are > still just as fast as before > Time Comparisons: > v2.7: > * unpacked => 24 seconds > * packed => 21 seconds > v2.8: > * unpacked => 49 seconds > * packed => 20 seconds -- 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-tabpanel&focusedCommentId=335361#comment-335361 ] Stephen Connolly commented on DOXIA-472: I added support for multi markdown metadata parsing. You'll need a 1.5-SNAPSHOT to see > 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 > Fix For: 1.5 > > > 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 - ". A live example on Maven site: > [maven-jsr330.html|http://maven.apache.org/maven-jsr330.html] done from > [maven-jsr330.md|https://svn.apache.org/repos/asf/maven/site/trunk/content/markdown/maven-jsr330.md] > 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] (MRELEASE-837) Release plugin resets parent to outdated version
[
https://jira.codehaus.org/browse/MRELEASE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335362#comment-335362
]
Robert Scholte commented on MRELEASE-837:
-
I see that you haven't locked to version of the {{maven-release-plugin}} or you
are using a very old version. Start by settings it to 2.4.2 and see if it can
still be reproduced.
> Release plugin resets parent to outdated version
>
>
> Key: MRELEASE-837
> URL: https://jira.codehaus.org/browse/MRELEASE-837
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Markus KARG
>Priority: Critical
>
> Using Maven 3.0.4 I noticed that the release plugin resets the parent to an
> outdated version. Here is what I noticed with all of my Projects when doing
> "mvn release:prepare":
> * Asks whether I want to update the parent version. I say "yes".
> * Asks whether "1.1" is the correct release version of paren, which is true.
> * Asks whether "1.2-SNAPSHOT" is the correct developer version of parent,
> which is true.
> * Asks whether "1.1" is the correct release version of child, which is true.
> * Asks whether "1.2-SNAPSHOT" is the correct developer version of child,
> which is true.
> After perform is done, my pom has different versions for parent and child:
> * Child correctly has "1.2-SNAPSHOT"
> * Parent incorrectly is reset to "1.1-SNAPSHOT"
> This is simple to fix in each POM, but annoying when releasing much and
> often. Hence I would be glad if this could get fixed soon.
--
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-837) Release plugin resets parent to outdated version
[ https://jira.codehaus.org/browse/MRELEASE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-837: Affects Version/s: 2.0 > Release plugin resets parent to outdated version > > > Key: MRELEASE-837 > URL: https://jira.codehaus.org/browse/MRELEASE-837 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0 >Reporter: Markus KARG >Priority: Critical > > Using Maven 3.0.4 I noticed that the release plugin resets the parent to an > outdated version. Here is what I noticed with all of my Projects when doing > "mvn release:prepare": > * Asks whether I want to update the parent version. I say "yes". > * Asks whether "1.1" is the correct release version of paren, which is true. > * Asks whether "1.2-SNAPSHOT" is the correct developer version of parent, > which is true. > * Asks whether "1.1" is the correct release version of child, which is true. > * Asks whether "1.2-SNAPSHOT" is the correct developer version of child, > which is true. > After perform is done, my pom has different versions for parent and child: > * Child correctly has "1.2-SNAPSHOT" > * Parent incorrectly is reset to "1.1-SNAPSHOT" > This is simple to fix in each POM, but annoying when releasing much and > often. Hence I would be glad if this could get fixed soon. -- 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-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:all-tabpanel ] Cremers stijn updated MPMD-174: --- Description: 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: org.apache.maven.plugins maven-pmd-plugin 3.0.1 http://my-tools.mycompany.com/sonar/profiles/export?format=pmd&language=java&name=MyProfile pmd check 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: org.apache.maven.plugins maven-pmd-plugin 3.0.1 http://nemo.sonarqube.org/profiles/export?format=pmd&language=java&name=Nemo pmd check 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 org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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:414) at org.codehaus.plexus.classworlds.launcher.Launcher.
[jira] (MPMD-174) Using a permalink from sonar as a ruleset does not work
Cremers stijn created MPMD-174: -- Summary: 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 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: org.apache.maven.plugins maven-pmd-plugin 3.0.1 http://my-tools.mycompany.com/sonar/profiles/export?format=pmd&language=java&name=MyProfile pmd check 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: org.apache.maven.plugins maven-pmd-plugin 3.0.1 http://nemo.sonarqube.org/profiles/export?format=pmd&language=java&name=Nemo pmd check But then i get the following error: [INFO] --- maven-pmd-plugin:3.0.1:pmd (pmd) @ nike-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 org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.co
[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-tabpanel&focusedCommentId=335363#comment-335363 ] Hendrik Schreiber commented on DOXIA-472: - Cool. I'll check it out. > 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 > Fix For: 1.5 > > > 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 - ". A live example on Maven site: > [maven-jsr330.html|http://maven.apache.org/maven-jsr330.html] done from > [maven-jsr330.md|https://svn.apache.org/repos/asf/maven/site/trunk/content/markdown/maven-jsr330.md] > 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] (MWAR-305) Filtering doesn't work as expected after switching from maven-filtering:1.0-beta-2 to maven-filtering:1.1
[
https://jira.codehaus.org/browse/MWAR-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335380#comment-335380
]
Grzegorz Grzybek commented on MWAR-305:
---
Hello - any news on this issue?
> Filtering doesn't work as expected after switching from
> maven-filtering:1.0-beta-2 to maven-filtering:1.1
> --
>
> Key: MWAR-305
> URL: https://jira.codehaus.org/browse/MWAR-305
> Project: Maven WAR Plugin
> Issue Type: Bug
>Reporter: Grzegorz Grzybek
>Priority: Critical
>
> {{maven-filtering:1.0-beta-3}} introduced a setting
> {{org.apache.maven.shared.filtering.AbstractMavenFilteringRequest.injectProjectBuildFilters}}
> defaulted to {{false}}.
> While constructing {{defaultFilterWrappers}} in
> {{org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(MavenProject,
> File)}} the {{MavenResourcesExecution}} is constructed.
> In {{maven-filtering:1.0-beta-2}} there's unconditional call:
> {code:java}
> loadProperties( filterProperties, mavenProject.getBuild().getFilters(),
> baseProps );
> {code}
> In {{maven-filtering:1.1}}+ there's conditional call:
> {code:java}
> if ( request.isInjectProjectBuildFilters() )
> {
> List buildFilters = new ArrayList(
> request.getMavenProject().getBuild().getFilters() );
> buildFilters.removeAll( request.getFileFilters() );
> loadProperties( filterProperties, buildFilters, baseProps );
> }
> {code}
> So my filters declared (as always) in:
> {code:xml}
>
>
> ../src/config/env/envX/config.properties
>
>
> {code}
> are *not taken into account* forcing me to set (configuration duplicate)
> [maven-war-plugin's
> filter|http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#filters]
> property.
> Please change (in
> {{org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp()}}) the line:
> {code:xml}
> mavenResourcesExecution.setFilters( filters );
> {code}
> to
> {code:xml}
> mavenResourcesExecution.setFilters( filters == null ?
> project.getBuild().getFilters() : filters );
> {code}
> regards
> Grzegorz Grzybek
--
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
