[jira] [Commented] (MPIR-343) Skip Dependency Information report if package is maven-plugin
[ https://issues.apache.org/jira/browse/MPIR-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210624#comment-16210624 ] Hervé Boutemy commented on MPIR-343: ok > Skip Dependency Information report if package is maven-plugin > - > > Key: MPIR-343 > URL: https://issues.apache.org/jira/browse/MPIR-343 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-info >Affects Versions: 2.8.1 >Reporter: Michael Osipov > > Dependency Information report is run for all types of packagings. The > information is displayed for various build systems but Maven Plugins can only > be reasonably used within Maven. The information snippets are pointless. We > should skip generation with a logged info that this does not make sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPIR-343) Skip Dependency Information report if package is maven-plugin
[ https://issues.apache.org/jira/browse/MPIR-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210285#comment-16210285 ] Michael Osipov commented on MPIR-343: - That's a very good point. Same probably applies for extensions. Let's close this one. > Skip Dependency Information report if package is maven-plugin > - > > Key: MPIR-343 > URL: https://issues.apache.org/jira/browse/MPIR-343 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-info >Affects Versions: 2.8.1 >Reporter: Michael Osipov > > Dependency Information report is run for all types of packagings. The > information is displayed for various build systems but Maven Plugins can only > be reasonably used within Maven. The information snippets are pointless. We > should skip generation with a logged info that this does not make sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPIR-349) Bad modules links in 'index/modules' reports when 'distributionManagement.site.url' comes from settings.xml
[
https://issues.apache.org/jira/browse/MPIR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210257#comment-16210257
]
Hervé Boutemy commented on MPIR-349:
ok, I'll just had a look, there are some easy to fix issues, then I'll do a
release: probably the vote will start this WE
> Bad modules links in 'index/modules' reports when
> 'distributionManagement.site.url' comes from settings.xml
> ---
>
> Key: MPIR-349
> URL: https://issues.apache.org/jira/browse/MPIR-349
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: index, modules
>Affects Versions: 2.9
>Reporter: Alix Lourme
>Assignee: Hervé Boutemy
> Labels: features
> Fix For: 2.10
>
> Attachments: MPIR-349-maven-project-info-reports-plugin.patch,
> variableSettingsIndexReport.zip
>
>
> When the _distributionManagement.site.url_ contains a property filled in
> _settings.xml_ like :
> _pom.xml_ :
> {code}
>
>
> projectSite
> ${sitePublishLocation}/foo/${project.artifactId}
>
>
> {code}
> _settings.xml_:
> {code}
>
>
>
>
> site-location
>
>
> file://tmp/sitePublish
>
>
>
>
> site-location
>
>
> {code}
> The modules links in *index* report contain
> {code}
> ${sitePublishLocation}
> {code}
> Problem can be reproduced with [^variableSettingsIndexReport.zip] project
> (dependencies required : [maven-site-plugin
> 3.6-SNAPSHOT|http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-plugin]
> & [doxia-integration-tools
> 1.7.2-SNAPSHOT|https://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/trunk/]).
> This command fails:
> {code}
> mvn site -s settings-site-location.xml
> {code}
> This command works:
> {code}
> mvn site -s settings-site-location.xml
> -DsitePublishLocation="/tmp/sitePublish"
> {code}
> The root cause is explained in MSITE-783 and fixed by DOXIASITETOOLS-166.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MPIR-334) Empty Maven Dependency Convergence Report
[
https://issues.apache.org/jira/browse/MPIR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091238#comment-15091238
]
Hervé Boutemy edited comment on MPIR-334 at 10/18/17 11:08 PM:
---
It's a modified pom from this project:
https://github.com/iluwatar/java-design-patterns/blob/master/pom.xml
I just added the following reporting section (with the working 2.7, 2.8.1 is
not working):
{code:xml}
false
${project.build.directory}/site
org.apache.maven.plugins
maven-project-info-reports-plugin
2.7
true
true
false
dependencies
index
modules
summary
dependency-convergence
dependency-info
dependency-management
{code}
was (Author: ice09):
It's a modified pom from this project:
https://github.com/iluwatar/java-design-patterns/blob/master/pom.xml
I just added the following reporting section (with the working 2.7, 2.8.1 is
not working):
false
${project.build.directory}/site
org.apache.maven.plugins
maven-project-info-reports-plugin
2.7
true
true
false
dependencies
index
modules
summary
dependency-convergence
dependency-info
dependency-management
> Empty Maven Dependency Convergence Report
> -
>
> Key: MPIR-334
> URL: https://issues.apache.org/jira/browse/MPIR-334
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-convergence
>Affects Versions: 2.8, 2.8.1
>Reporter: Alexander Culum
> Labels: close-pending
>
> copied from
> http://stackoverflow.com/questions/33070728/empty-maven-dependency-convergence-report
> The report section "Dependencies used in modules" is empty if
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.8.0 or
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.8.1 is used.
> Solution: use the older version of the plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.7. A report
> section 'Dependencies used in sub-projects' is added. This section contains
> details about the dependency convergence problem in the submodules.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MPIR-343) Skip Dependency Information report if package is maven-plugin
[ https://issues.apache.org/jira/browse/MPIR-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210252#comment-16210252 ] Hervé Boutemy commented on MPIR-343: a plugin may not be only a plugin: see for example asciidoctor-maven-plugin which is a maven plugin, but also a Doxia Parser Module to simply add as a dependency to maven-site-plugin then in general, yes, a plugin is only a plugin, but sometimes not making efforts to remove the info does not really bring value IMHO > Skip Dependency Information report if package is maven-plugin > - > > Key: MPIR-343 > URL: https://issues.apache.org/jira/browse/MPIR-343 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-info >Affects Versions: 2.8.1 >Reporter: Michael Osipov > > Dependency Information report is run for all types of packagings. The > information is displayed for various build systems but Maven Plugins can only > be reasonably used within Maven. The information snippets are pointless. We > should skip generation with a logged info that this does not make sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MPIR-346) Upgrade to Doxia Sitetools 1.7
[ https://issues.apache.org/jira/browse/MPIR-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPIR-346: --- Fix Version/s: 2.10 > Upgrade to Doxia Sitetools 1.7 > -- > > Key: MPIR-346 > URL: https://issues.apache.org/jira/browse/MPIR-346 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov > Fix For: 2.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MPIR-345) Upgrade to Doxia 1.7
[ https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPIR-345: --- Fix Version/s: 2.10 > Upgrade to Doxia 1.7 > > > Key: MPIR-345 > URL: https://issues.apache.org/jira/browse/MPIR-345 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov > Fix For: 2.10 > > Attachments: 1.7.log, MPIR-345.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MPIR-359) Generated links for Mercurial SCM are broken
[ https://issues.apache.org/jira/browse/MPIR-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPIR-359: --- Fix Version/s: 2.10 > Generated links for Mercurial SCM are broken > > > Key: MPIR-359 > URL: https://issues.apache.org/jira/browse/MPIR-359 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: scm >Affects Versions: 2.9 >Reporter: Andreas Sewe > Fix For: 2.10 > > > The links generated for the Mercurial SCM still refer to > http://mercurial.selenic.com/ and subpages. These links no longer work. > Mercurial’s website is not available at https://www.mercurial-scm.org/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPIR-349) Bad modules links in 'index/modules' reports when 'distributionManagement.site.url' comes from settings.xml
[
https://issues.apache.org/jira/browse/MPIR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209484#comment-16209484
]
Brad Flood commented on MPIR-349:
-
[~hboutemy] version 2.10, containing the fix for MPIR-349 does not appear to
have been released yet. Can you provide an indication on plans to release
2.10?
If it is not planned, could you please advise as to how to configure
project-info-reports-plugin:2.9 to work around this? I've followed the other
tickets and believe I am current with regards to all other suggested
workarounds.
We are currently blocked, not able to generate production site reports without
the broken links caused by this issue.
The project variableSettingsIndexReport (provided in this ticket) fails with my
configuration.
I have maven-site-plugin:3.6, and sitetools 1.7.4 is configured correctly
there. But project-info-reports-plugin uses doxia-integration-tools:1.6
{code:java}
[DEBUG] Populating class realm
plugin>org.apache.maven.plugins:maven-project-info-reports-plugin:2.9
[DEBUG] Included:
org.apache.maven.plugins:maven-project-info-reports-plugin:jar:2.9
[DEBUG] Included: org.apache.maven.reporting:maven-reporting-impl:jar:2.3
[DEBUG] Included: org.apache.maven.shared:maven-shared-utils:jar:0.6
[DEBUG] Included: com.google.code.findbugs:jsr305:jar:2.0.1
[DEBUG] Included: backport-util-concurrent:backport-util-concurrent:jar:3.1
[DEBUG] Included: org.apache.maven.shared:maven-dependency-tree:jar:2.2
[DEBUG] Included: org.codehaus.plexus:plexus-component-annotations:jar:1.5.5
[DEBUG] Included: org.eclipse.aether:aether-util:jar:0.9.0.M2
[DEBUG] Included: org.apache.maven.doxia:doxia-integration-tools:jar:1.6
...
{code}
I cannot figure out how to configure MPIR to use
org.apache.maven.doxia:doxia-integration-tools:jar:1.7.4.
Any help is appreciated, either by releasing the 2.10 or giving guidance on
what I am missing regarding the workaround.
Thanks
> Bad modules links in 'index/modules' reports when
> 'distributionManagement.site.url' comes from settings.xml
> ---
>
> Key: MPIR-349
> URL: https://issues.apache.org/jira/browse/MPIR-349
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: index, modules
>Affects Versions: 2.9
>Reporter: Alix Lourme
>Assignee: Hervé Boutemy
> Labels: features
> Fix For: 2.10
>
> Attachments: MPIR-349-maven-project-info-reports-plugin.patch,
> variableSettingsIndexReport.zip
>
>
> When the _distributionManagement.site.url_ contains a property filled in
> _settings.xml_ like :
> _pom.xml_ :
> {code}
>
>
> projectSite
> ${sitePublishLocation}/foo/${project.artifactId}
>
>
> {code}
> _settings.xml_:
> {code}
>
>
>
>
> site-location
>
>
> file://tmp/sitePublish
>
>
>
>
> site-location
>
>
> {code}
> The modules links in *index* report contain
> {code}
> ${sitePublishLocation}
> {code}
> Problem can be reproduced with [^variableSettingsIndexReport.zip] project
> (dependencies required : [maven-site-plugin
> 3.6-SNAPSHOT|http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-plugin]
> & [doxia-integration-tools
> 1.7.2-SNAPSHOT|https://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/trunk/]).
> This command fails:
> {code}
> mvn site -s settings-site-location.xml
> {code}
> This command works:
> {code}
> mvn site -s settings-site-location.xml
> -DsitePublishLocation="/tmp/sitePublish"
> {code}
> The root cause is explained in MSITE-783 and fixed by DOXIASITETOOLS-166.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml
[
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209480#comment-16209480
]
Vincent Vandenschrick commented on MDEPLOY-221:
---
For the records, I've just tried the 3.5.2 release candidate to build the
Jspresso framework and everything worked like a charm.
> deploy generates wrong timestamps in maven-metadata.xml
> ---
>
> Key: MDEPLOY-221
> URL: https://issues.apache.org/jira/browse/MDEPLOY-221
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.8.2
>Reporter: Roland Illig
>Assignee: Guillaume Boué
>
> When deploying an artifact to a Nexus server, the file {{maven-metadata.xml}}
> can end up with inconsistent timestamps.
> {noformat}
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 24 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 171 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> (18 kB at 591 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> (2.2 kB at 71 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 59 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 43 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 33 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 40 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76-sources.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76-sources.jar
> (12 kB at 386 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 59 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 65 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven
[jira] [Created] (MINDEXER-106) ClassNotFoundException (org.sonatype.aether.version.InvalidVersionSpecificationException) under recent Maven versions
Andreas Sewe created MINDEXER-106:
-
Summary: ClassNotFoundException
(org.sonatype.aether.version.InvalidVersionSpecificationException) under recent
Maven versions
Key: MINDEXER-106
URL: https://issues.apache.org/jira/browse/MINDEXER-106
Project: Maven Indexer
Issue Type: Bug
Affects Versions: 5.1.1
Environment: Apache Maven 3.5.0
(ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
Reporter: Andreas Sewe
It is impossible to use the latest released {{indexer-core}} (version 5.1.1) in
a mojo executing under a recent version of Maven (3.5.0):
{noformat}
Caused by: java.lang.NoClassDefFoundError:
org/sonatype/aether/version/InvalidVersionSpecificationException
at
org.apache.maven.index.context.IndexUtils.constructArtifactInfo(IndexUtils.java:111)
at
org.apache.maven.index.context.IndexUtils.updateDocument(IndexUtils.java:135)
at
org.apache.maven.index.updater.IndexDataReader.readIndex(IndexDataReader.java:92)
at
org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexData(DefaultIndexUpdater.java:509)
at
org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:197)
at
org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:76)
at
org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:642)
at
org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:862)
at
org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:157)
...
Caused by: java.lang.ClassNotFoundException:
org.sonatype.aether.version.InvalidVersionSpecificationException
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SCM-531) Incorrect SCM URL constructed when using parent POM that is not in the parent directory
[
https://issues.apache.org/jira/browse/SCM-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209020#comment-16209020
]
jycr commented on SCM-531:
--
It seems that it "works as designed" :
https://stackoverflow.com/questions/20513744/project-artifactid-in-parent-pom-xml-resolves-odd#answer-20517630
> Incorrect SCM URL constructed when using parent POM that is not in the parent
> directory
> ---
>
> Key: SCM-531
> URL: https://issues.apache.org/jira/browse/SCM-531
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-site
> Environment: Apache Maven 2.2.0 (r788681; 2009-06-26 14:04:01+0100)
> Java version: 1.6.0_16
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux" version: "2.6.31-19-generic" arch: "amd64" Family: "unix"
>Reporter: Darren Bell
>
> In our parent pom we have this:
> {noformat}
>
> master-pom
>
>
> scm:cvs:ext:build@server:/srv/cvs/:${scm.module}
>
> scm:cvs:ext:build@server:/srv/cvs/:${scm.module}
> http://server/fe/browse/UK-CVS-Rsync/${scm.module}
>
> {noformat}
> Our child pom (not in the same directory), has this:
> {noformat}
> dd-util
>
> util
>
> {noformat}
> Of course, the child pom is overriding the property. Well, it sort of works.
> When building the site of the parent pom, we get:
> {noformat}
> http://server/fe/browse/UK-CVS-Rsync/master-pom
> {noformat}
> ... which is correct. But when building the site for the child pom, we get:
> {noformat}
> http://server/fe/browse/UK-CVS-Rsync/util/dd-util
> {noformat}
> I'm quite confused as to why it whould be appending the artifactId of the
> child project. The property is getting replaced ok, but the the extra bit?
> This has got to be a bug.
> I'm not releasing the project, just building the site.
> Any ideas? If this is against the wrong project, can it be moved?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
