[jira] (MCHANGELOG-132) Add configuration value for custom commit links
[ https://jira.codehaus.org/browse/MCHANGELOG-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dane Hammer closed MCHANGELOG-132. -- Resolution: Won't Fix This is resolved by the already existing displayChangeSetDetailUrl element. > Add configuration value for custom commit links > --- > > Key: MCHANGELOG-132 > URL: https://jira.codehaus.org/browse/MCHANGELOG-132 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Dane Hammer >Priority: Minor > > Add configuration value for building commit links, similar to how > displayFileDetailUrl can be used to customize the generated link. > For example, the plugin works with a git project for building the changelog > but the links don't line up with a GitHub hosted project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGELOG-132) Add configuration value for custom commit links
Dane Hammer created MCHANGELOG-132: -- Summary: Add configuration value for custom commit links Key: MCHANGELOG-132 URL: https://jira.codehaus.org/browse/MCHANGELOG-132 Project: Maven 2.x Changelog Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Dane Hammer Priority: Minor Add configuration value for building commit links, similar to how displayFileDetailUrl can be used to customize the generated link. For example, the plugin works with a git project for building the changelog but the links don't line up with a GitHub hosted project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5369) Inconsistent interaction between activeProfiles and activeByDefault
[
https://jira.codehaus.org/browse/MNG-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317593#comment-317593
]
Anthony Whitford commented on MNG-5369:
---
I think I just stumbled on this bug too... I have a profile defined in the
{{settings.xml}} with an {{activeByDefault}} set to {{true}}, then the profile
also has some definition in my corporate parent pom. Despite the
{{activeByDefault}}, the profile was not being activated. I had to add an
explicit {{active-profiles}} section to make it work. But I do think this is a
bug because the documentation suggests that {{activeByDefault}} should work
fine, {{mvn help:active-profiles}} also reported the profile as active, and
this was working fine with Maven 2.2.1.
> Inconsistent interaction between activeProfiles and activeByDefault
> ---
>
> Key: MNG-5369
> URL: https://jira.codehaus.org/browse/MNG-5369
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles, Settings
>Affects Versions: 3.0.4
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
> Maven home: /home/rchen/dev/tools/apache-maven-3.0.4
> Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
> Java home: /home/rchen/dev/tools/jdk1.6.0_26/jre
> Default locale: en_CA, platform encoding: UTF-8
> OS name: "linux", version: "2.6.36-020636-generic", arch: "amd64", family:
> "unix"
>Reporter: Ronald Chen
> Attachments: maven-active-by-default-parent.tar.gz,
> maven-profiles-bug.png
>
>
> I have two profiles. One is activated by activeProfiles in settings.xml and
> the other is activeByDefault = true
> They are both expected to be active as I am not using -P in my commands.
> The bug is there are some cases in which the activeByDefault profile is not
> active.
> It seems like whenever both profiles are located in the same pom, the
> activeByDefault profile is no longer active. But moving the activeProfiles
> profile up into a parent pom or moving the activeByDefault profile down to a
> module both seems to work.
> Its a rather complicated to describe, so I have attached 6 sample projects
> which illustrates various scenarios. I've summarized the results in the
> attached image.
> You can also run all the projects with the command:
> ls -1 | xargs --verbose -I CASE mvn -f CASE/sub-parent/project/pom.xml
> validate -s CASE/settings.xml |grep -vP '^\[INFO\]'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory
[
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated SCM-709:
---
Description:
SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
language independend.
Without the {{--porcelain}} option files were listed relative to the working
directory, but with {{--porcelain}} files are listed relative to the repository
root. In most cases these are the same, but not always.
was:
SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
language independend.
The regular expressions have changed, but they are too wide, which might cause
invalid matches.
Assignee: Robert Scholte
Summary: REGRESSION: git status doesn't work if repository root is not
the working directory (was: REGRESSION: git status regexps invalid)
> REGRESSION: git status doesn't work if repository root is not the working
> directory
> ---
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.8, 1.8.1
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result
> language independend.
> Without the {{--porcelain}} option files were listed relative to the working
> directory, but with {{--porcelain}} files are listed relative to the
> repository root. In most cases these are the same, but not always.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-79) APT document with verbatim section including C #include causes NPE
Andy Isaacson created DOXIASITETOOLS-79:
---
Summary: APT document with verbatim section including C #include
causes NPE
Key: DOXIASITETOOLS-79
URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-79
Project: Maven Doxia Sitetools
Issue Type: Bug
Reporter: Andy Isaacson
Attachments: mtest.tar.gz
A simple apt.vm document including a C program fragment in a verbatim section
causes "mvn site" to fail with a NPE. The failure can be worked around by
escaping the # as backslash-# but the requirement to do this is not documented,
nor AFAICS is the feature of supporting #include in verbatim sections.
Attaching a complete testcase mtest.tar.gz.
{noformat}
% cat src/site/apt/hello.vm
#include "stdio.h"
int main(void) { printf("hello, world!\n"); return 0; }
% mvn --version
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.6.6", arch: "amd64", family: "unix"
% mvn site
...
[WARNING] No project URL defined - decoration links will not be relativized!
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
[ERROR] Parser Exception: /tmp/mtest/src/site/apt/hello.apt.vm
[ERROR] org.apache.velocity.runtime.parser.ParseException: Encountered
"\"stdio.h\"" at line 2, column 13.
Was expecting:
"(" ...
at
org.apache.velocity.runtime.parser.Parser.generateParseException(Parser.java:3360)
at
org.apache.velocity.runtime.parser.Parser.jj_consume_token(Parser.java:3237)
...
[ERROR] ResourceManager.getResource() parse exception
[ERROR] org.apache.velocity.exception.ParseErrorException: Encountered
"\"stdio.h\"" at line 2, column 13 of /tmp/mtest/src/site/apt/hello.apt.vm
Was expecting:
"(" ...
at org.apache.velocity.Template.process(Template.java:137)
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:415)
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:335)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1102)
at
org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:498)
...
[ERROR] Error parsing /tmp/mtest/src/site/apt/hello.apt.vm as a velocity
template, using as text.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.798s
[INFO] Finished at: Fri Jan 18 12:51:17 PST 2013
[INFO] Final Memory: 11M/153M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project
mtest: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
NullPointerException -> [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-641) Assembly fails on resource name with a percent character
[
https://jira.codehaus.org/browse/MASSEMBLY-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harald Wellmann updated MASSEMBLY-641:
--
Attachment: assembly-bug.zip
> Assembly fails on resource name with a percent character
>
>
> Key: MASSEMBLY-641
> URL: https://jira.codehaus.org/browse/MASSEMBLY-641
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.4
>Reporter: Harald Wellmann
> Attachments: assembly-bug.zip
>
>
> Given a classpath resource like {{path/to/10%.txt}}, the Maven Assembly
> plugin fails with the following exception.
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on
> project assembly-bug: Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on
> project assembly-bug: Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> 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:319)
> 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.PluginExecutionException: Execution
> default of goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single
> failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.IllegalArgumentException
> at sun.net.www.ParseUtil.decode(ParseUtil.java:202)
> at java.net.JarURLConnection.parseSpecs(JarURLConnection.java:185)
> at java.net.JarURLConnection.(JarURLConnection.java:162)
> at
> sun.net.www.protocol.jar.JarURLConnection.(JarURLConnection.java:81)
> at sun.net.www.protocol.jar.Handler.openConnection(Handler.java:41)
> at java.net.URL.openConnection(URL.java:971)
> at java.net.URL.openStream(URL.java:1037)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents(PlexusIoURLResource.java:34)
> at
> org.codehaus.plexus.archiver.ArchiveEntry.getInputStream(ArchiveEntry.java:106)
> at
> org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:590)
> at
> org.codehaus.plexus.archiver.zip.AbstractZipArchiver.addResources(AbstractZipArchiver.java:398)
> at
> org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:323)
> at
> org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:222)
> at
> org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:910)
> at
> org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArchiver.java:51
[jira] (MASSEMBLY-641) Assembly fails on resource name with a percent character
Harald Wellmann created MASSEMBLY-641:
-
Summary: Assembly fails on resource name with a percent character
Key: MASSEMBLY-641
URL: https://jira.codehaus.org/browse/MASSEMBLY-641
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.4
Reporter: Harald Wellmann
Given a classpath resource like {{path/to/10%.txt}}, the Maven Assembly plugin
fails with the following exception.
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on project
assembly-bug: Execution default of goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
IllegalArgumentException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on project
assembly-bug: Execution default of goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
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:319)
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.PluginExecutionException: Execution default
of goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.IllegalArgumentException
at sun.net.www.ParseUtil.decode(ParseUtil.java:202)
at java.net.JarURLConnection.parseSpecs(JarURLConnection.java:185)
at java.net.JarURLConnection.(JarURLConnection.java:162)
at
sun.net.www.protocol.jar.JarURLConnection.(JarURLConnection.java:81)
at sun.net.www.protocol.jar.Handler.openConnection(Handler.java:41)
at java.net.URL.openConnection(URL.java:971)
at java.net.URL.openStream(URL.java:1037)
at
org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents(PlexusIoURLResource.java:34)
at
org.codehaus.plexus.archiver.ArchiveEntry.getInputStream(ArchiveEntry.java:106)
at
org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:590)
at
org.codehaus.plexus.archiver.zip.AbstractZipArchiver.addResources(AbstractZipArchiver.java:398)
at
org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:323)
at
org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:222)
at
org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:910)
at
org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArchiver.java:512)
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:186)
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:436)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{noformat}
--
This message is automat
[jira] (MRELEASE-798) Commit additional files with release plugin
[ https://jira.codehaus.org/browse/MRELEASE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317561#comment-317561 ] Robert Scholte commented on MRELEASE-798: - Not yet > Commit additional files with release plugin > --- > > Key: MRELEASE-798 > URL: https://jira.codehaus.org/browse/MRELEASE-798 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: prepare, scm >Affects Versions: 2.3.2 >Reporter: Thorsten Hoeger > > Hi, > is there any possibility to have the release-plugin commit additional files > which were > generated/modified in the preparationGoals. > Now only the pom.xml is commited. Using scm-plugin has some serious drawbacks > in this > situation. > If it is not possible at the moment, is there any chance to get this in the > future. Maybe > there could be a parameter additionalCommitFiles with a list of files to > commit along with > pom.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-161) PMD/CPD violation exclusions by class/issue
Andrey Utis created MPMD-161: Summary: PMD/CPD violation exclusions by class/issue Key: MPMD-161 URL: https://jira.codehaus.org/browse/MPMD-161 Project: Maven 2.x PMD Plugin Issue Type: New Feature Components: CPD, PMD Reporter: Andrey Utis Attachments: pmd2.7.1_exclusions2.patch I work on a system that has a lot of legacy code with a lot of PMD/CPD violations. Introducing PMD to the build is not an easy option, since the build would always fail. So the next best thing is to exclude any existing violations and only fail if a new violation is introduced. Unfortunately, if I have thousands of violations, PMD doesn't provide a good way to do this. I'd have to add comments or annotations to all these places to ignore the violation. We came up with an alternative solution to this. We modified the PMD plugin to read a properties file that contains a mapping of class name to a list of excluded violations. If a particular violation is in this file, it does not cause the build to fail. Similar idea for CPD. An svn patch is attached (apply to 2.7.1) (Disclaimer: this is probably not the most elegant piece of code but it works and it was quick. Feel free to re-factor and make it more in line with the rest of the plugin code) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-137) Shade Plugin does not consider Maven repositories contributed via profiles
Bernd Vogt created MSHADE-137:
-
Summary: Shade Plugin does not consider Maven repositories
contributed via profiles
Key: MSHADE-137
URL: https://jira.codehaus.org/browse/MSHADE-137
Project: Maven 2.x Shade Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: Bernd Vogt
We're using a global parent pom vor all our projects. this pom is accessible
via a company internal Maven repository, which will be contributed via a maven
profile specified in the local settings.xml.
Now, building sth. with Maven Shade Plugin breaks, because Schade Plugin
doesn't include the repo contributed via the profile in settings.xml to the
list of available repositories.
In the following error log the artifact
{{de.visualrules.maven:visualrules-parent:pom:5}} cannot be resolved, but it is
accessible via the internal repo contributed via the profile in the
settings.xml. The build stebs bevore are aware of the repo and could resolve
the artifact without any problems.
{noformat}
[INFO] --- maven-shade-plugin:1.4:shade (default) @ maven2x-agent ---
[INFO] Including
de.visualrules.runtimetools:maven-interceptor:jar:0.5.0-SNAPSHOT in the shaded
jar.
[INFO] Including
de.visualrules.runtimetools:artifactbuilder-common:jar:0.5.0-SNAPSHOT in the
shaded jar.
[INFO] Including commons-codec:commons-codec:jar:1.3 in the shaded jar.
[INFO] Replacing original artifact with shaded artifact.
[INFO] Replacing
D:\src\e43\vr\ws\runtime-tools\maven-interception\maven2x-agent\target\maven2x-agent-0.5.0-SNAPSHOT.jar
with
D:\src\e43\vr\ws\runtime-tools\maven-interception\maven2x-agent\target\maven2x-agent-0.5.0-SNAPSHOT-shaded.jar
Downloading:
http://repo.bosch-si.com/content/groups/public/de/visualrules/maven/visualrules-parent/5/visualrules-parent-5.pom
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Visual Rules Runtime Tools SUCCESS [1.279s]
[INFO] artifactbuilder-common SUCCESS [3.248s]
[INFO] maven-interception SUCCESS [0.016s]
[INFO] maven-interceptor . SUCCESS [2.934s]
[INFO] maven2x-agent . FAILURE [5.496s]
[INFO] maven3x-agent . SKIPPED
[INFO] vmspy . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 13.288s
[INFO] Finished at: Fri Jan 18 11:47:59 CET 2013
[INFO] Final Memory: 12M/148M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:1.4:shade (default) on project
maven2x-agent: Error creating shaded jar: 1 problem was encountered while
building the effective model for
de.visualrules.runtimetools:maven2x-agent:0.5.0-SNAPSHOT
[ERROR] [FATAL] Non-resolvable parent POM for
de.visualrules.runtimetools:runtime-tools:0.5.0-SNAPSHOT: Could not find
artifact de.visualrules.maven:visualrules-parent:pom:5 in bosch-si.com
(http://repo.bosch-si.com/content/groups/public) and 'parent.relativePath'
points at wrong local POM @
de.visualrules.runtimetools:runtime-tools:0.5.0-SNAPSHOT,
D:\src\e43\vr\ws\runtime-tools\pom.xml, line 4, column 10
[ERROR] for project de.visualrules.runtimetools:maven2x-agent:0.5.0-SNAPSHOT at
D:\src\e43\vr\ws\runtime-tools\maven-interception\maven2x-agent\dependency-reduced-pom.xml
for project de.visualrules.runtimetools:maven2x-agent:0.5.0-SNAPSHOT at
D:\src\e43\vr\ws\runtime-tools\maven-interception\maven2x-agent\dependency-reduced-pom.xml
[ERROR] -> [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-269) (optionally) create dependency convergence also for single module projects
Michael Wenig created MPIR-269: -- Summary: (optionally) create dependency convergence also for single module projects Key: MPIR-269 URL: https://jira.codehaus.org/browse/MPIR-269 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: dependency-convergence Affects Versions: 2.6 Reporter: Michael Wenig We are using the dependency convergence report for a quick check if a project could be released or not. Unfortunately the report is not created for single module projects. MPIR-10 mentions that it is useful for multi module and therefore disabled by default for single module projects. Unfortunately "by default" is not correct as there is no option to activate it. At our site the report also makes sense for single modules. The report shows if there are snapshot versions of other projects used. Of course someone could take a look into the dependency report and search for SNAPSHOT. But it is a lot easier for the developers to follow a simple rule "look into this report" - and it could be used programmatically if the report is alway present. Is there any reason against activating this report also for single module (an option which is false per default would be sufficient)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
