[jira] (ARCHETYPE-383) Use velocity expressions in descriptor properties
[
https://jira.codehaus.org/browse/ARCHETYPE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296310#comment-296310
]
Bue Pierre-Christophe commented on ARCHETYPE-383:
-
the bug fiw worked fine for standard properties (artifactId, groupId, ...), but
still does not work with user defined properties. For example:
${artifactId}.substring(0,1).toUpperCase()
with artifactId=toto will give a=T, but
${b}.substring(0,1).toUpperCase()
with b=toto will give a=${b}.substring(0,1).toUpperCase()
> Use velocity expressions in descriptor properties
> -
>
> Key: ARCHETYPE-383
> URL: https://jira.codehaus.org/browse/ARCHETYPE-383
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Plugin
>Affects Versions: 2.1
>Reporter: Emmanuel Hugonnet
>Assignee: Olivier Lamy
> Fix For: 2.2
>
> Attachments: patch_jira_383.patch
>
>
> The descriptor can use velocity expressions for value and defaultValue, thus
> enabling the creation of velocity global properties for an archetype.
> For example :
>
>
> ${rootArtifactId.substring(0,1).toUpperCase()}${rootArtifactId.substring(1)}
>
--
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] (MSKINS-48) make Fluido Skin more responsive
Hugues Obolonsky created MSKINS-48: -- Summary: make Fluido Skin more responsive Key: MSKINS-48 URL: https://jira.codehaus.org/browse/MSKINS-48 Project: Maven Skins Issue Type: Improvement Components: Fluido Skin Affects Versions: fluido-1.2.1 Reporter: Hugues Obolonsky Attachments: fluido-responsive.patch The maven fluido skin is not optimise for cellphone device. Patch provided as a proposition but maybe need more css tuning. The patch provide an upgraded version of bootstrap with .hidden_phone class which work on tag. -- 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-5274) Filtering: check if there are any placeholders that were not substituted
Benjamin Walther Büel created MNG-5274: -- Summary: Filtering: check if there are any placeholders that were not substituted Key: MNG-5274 URL: https://jira.codehaus.org/browse/MNG-5274 Project: Maven 2 & 3 Issue Type: New Feature Components: General Affects Versions: 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0 Environment: any Reporter: Benjamin Walther Büel Attachments: MavenExtension-checkForPlaceholders.zip, maven-filtering-ext-1.0.pom Functionality that checks if after filtering there are remaining placeholders that were not replaced during filtering. Example: template.properties: log.level=@log.level@ hibernate.show-sql=@hibernate.show-sql@ filter file my.properties: log.level=debug target file: log.level=debug hibernate.show-sql=@hibernate.show-sql@ With the attached extended resources&filter plugins will throw: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin-ext:2.5:copy-resources (copy-resources) on project foo: File server.properties line:hibernate.show-sql=@hibernate.show-sql@ contains one or more placeholders not replaced by filter(s). Usage: org.apache.maven.plugins maven-resources-plugin-ext 2.5 @ target/classes true -- 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] (MECLIPSE-719) to-maven mojo does not handle source bundles correctly
Gabriele Catania created MECLIPSE-719:
-
Summary: to-maven mojo does not handle source bundles correctly
Key: MECLIPSE-719
URL: https://jira.codehaus.org/browse/MECLIPSE-719
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Affects Versions: 2.9
Environment: Any eclipse SDK version
Reporter: Gabriele Catania
Priority: Minor
Attachments: handle-sources.patch
the to-maven mojo does not install source bundles according to maven
conventions. For example, the following plugins:
# {{org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar}}
# {{org.eclipse.osgi.source_3.4.3.R34x_v20081215-1030.jar}}
should be deployed respectively to:
#
{{M2_REPO/org/eclipse/osgi/3.4.3-R34x_v20081215-1030/osgi-3.4.3-R34x_v20081215-1030.jar}}
#
{{M2_REPO/org/eclipse/osgi/3.4.3-R34x_v20081215-1030/osgi-3.4.3-R34x_v20081215-1030-sources.jar}}
instead, they are deployed here:
#
{{M2_REPO/org/eclipse/osgi/3.4.3-R34x_v20081215-1030/osgi-3.4.3-R34x_v20081215-1030.jar}}
#
{{M2_REPO/org/eclipse/osgi/}}{color:red}{{source/}}{color}{{3.4.3-R34x_v20081215-1030/}}{color:red}{{source}}{color}{{-3.4.3-R34x_v20081215-1030.jar}}
To test this behaviour, I downloaded an eclipse sdk and ran the to-maven mojo
in its unpacked installation directory
I am attaching a quick patch I devised to set the "sources" classifier on
plugins whose name ends with ".source". I tried to minimize code changes, a
revised implementation should probably modify {{createGroupId()}} and
{{createArtifactId()}}, and avoid installing the pom for the sources jar.
--
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] (MSITE-619) Method calculateLink threw exception for reference $PathTool
[ https://jira.codehaus.org/browse/MSITE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296340#comment-296340 ] Johannes Schneider commented on MSITE-619: -- I just run into that exception. This worked fine some time ago. I think a recent update to the site plugin triggered that bug. Please, please - at least add a better exception message... > Method calculateLink threw exception for reference $PathTool > > > Key: MSITE-619 > URL: https://jira.codehaus.org/browse/MSITE-619 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3, site descriptor >Affects Versions: 3.0 > Environment: Maven 3.0.3, MacOS-X 10.6.8 >Reporter: Oliver Boehm >Assignee: Lukas Theussl > > After running 'mvn site:site' I get the following errors after upgrading to > maven-site-plugin 3.0 (with 3.0-beta-3 this error does not happen!): > ... > [ERROR] Method calculateLink threw exception for reference $PathTool in > template org/apache/maven/doxia/siterenderer/resources/default-site.vm at > [2,31] > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 34.451s > [INFO] Finished at: Sun Nov 20 20:29:56 CET 2011 > [INFO] Final Memory: 22M/81M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.0:site (default-cli) on project > patterntesting-rt: Error during page generation: Error while generating code. > Invocation of method 'calculateLink' in class > org.codehaus.plexus.util.PathTool threw exception > java.lang.NullPointerException @ > org/apache/maven/doxia/siterenderer/resources/default-site.vm[2,41] -> [Help > 1] > ... > These are the POMs which are used: > - > http://patterntesting.cvs.sourceforge.net/viewvc/patterntesting/PatternTesting10/patterntesting-parent/pom.xml > - > http://patterntesting.cvs.sourceforge.net/viewvc/patterntesting/PatternTesting10/patterntesting-rt/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] (MRELEASE-705) Project directory appended twice
[
https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296352#comment-296352
]
Robert Scholte commented on MRELEASE-705:
-
Based on only the output above it is not possible to reproduce this issue.
According to the logging the base directory is called {{test-project-1}} (I
think), but this seems to be a file and not a directory. I still think we have
to find the real cause around here.
Andrey, it would be nice if you could figure out with which version this bug
was introduced (the gap between 2.0 and 2.2.2, if you have tried this version,
is huge).
Also: Is this also an issue for Maven3?
> Project directory appended twice
>
>
> Key: MRELEASE-705
> URL: https://jira.codehaus.org/browse/MRELEASE-705
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.2.1
> Environment: accurev scm provider
>Reporter: Vadim Tsing
>Priority: Blocker
> Attachments: output.txt
>
>
> During perform, the fix for MRELEASE-457 changes the checkout directory by
> appending the checkout path, later the release manager appends it again in
> determineWorkingDirectory(). As a result maven cannot find the checked out
> project.
> Please see attached log file with -X output, specifically line 1541 that
> shows the correct project path, however, when it comes to running the deploy
> command, it appends project path again as indicated by line 1553.
--
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] (MRELEASE-645) Allow File/Directory Patterns for the checkModificationExcludes Option
[
https://jira.codehaus.org/browse/MRELEASE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-645.
---
Resolution: Fixed
Fix Version/s: 2.3
Fixed in [r1325475|http://svn.apache.org/viewvc?rev=1325475&view=rev] and
[r1325481|http://svn.apache.org/viewvc?rev=1325481&view=rev]
> Allow File/Directory Patterns for the checkModificationExcludes Option
> --
>
> Key: MRELEASE-645
> URL: https://jira.codehaus.org/browse/MRELEASE-645
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: branch, prepare, scm
>Affects Versions: 2.1
> Environment: all
>Reporter: Stefan Ferstl
>Assignee: Robert Scholte
>Priority: Minor
> Fix For: 2.3
>
> Attachments: maven-release-manager-r1305146.patch,
> maven-release-plugin-it.patch,
> maven-release-plugin-it-with-scm-provider.patch, modification-excludes.patch,
> MRELEASE-645.patch
>
>
> The {{checkModificationExcludes}} option does currently only allow the
> definition single files to be excluded from the SCM modification check. If
> this option is defined, all files anywhere in the maven project structure
> with the specified name will be excluded from the check. It is currently not
> possible to exclude files only within a specific directory or to exclude
> classes of files, i.e. all files matching a specific file name pattern.
> If the {{checkModificationExcludes}} option allowed the definition of file
> and directory patterns, these things would be possible.
> *Example 1*: I'd like to exclude a test resource
> {{src/test/resources/foo.properties}} from the modification check but the
> real foo.properties in {{src/main/resources}} should still be checked.
> {code:xml}
>
>
> src/test/resources/foo.properties
>
> {code}
> *Example 2*: I'd like to exclude all properties files with the prefix {{bar}}
> from the modification check:
> {code:xml}
>
> **/bar*.properties
>
> {code}
> The attached patch modifies the {{ScmCheckModificationsPhase}} to use the
> {{DirectoryScanner}} from plexus-utils instead of doing a strict file name
> comparison. The patch does not provide more unit tests for this feature but
> it adjusts the existing tests to run without any failures.
--
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-70) Html title of generated pages does not include project name
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296364#comment-296364 ] Dennis Lundberg commented on DOXIASITETOOLS-70: --- Heinrich, Have you had time to confirm that it is working for you now? > Html title of generated pages does not include project name > --- > > Key: DOXIASITETOOLS-70 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-70 > Project: Maven Doxia Sitetools > Issue Type: Bug > Components: Site renderer >Affects Versions: 1.2 > Environment: Apache Maven 3.0.3 > (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200) > Maven home: /usr/local/apache-maven/apache-maven-3.0.3 > Java version: 1.6.0_18, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: en_US, platform encoding: ANSI_X3.4-1968 > OS name: "linux", version: "2.6.18-028stab092.1", arch: "amd64", family: > "unix" >Reporter: Heinrich Schuchardt >Assignee: Dennis Lundberg > Fix For: 1.3 > > Attachments: pom.xml, pom.xml > > > Dear maintainer, > according to > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > the title of each page should be the concatenation of the site title and the > title of the current page. E.g. if in pom.xml the name element is: > Site Plugin Test > then target/site/index.html should have a line > Site Plugin Test - About > This is not working. The site title is missing and the created index.html > only contains > About > This effects how the page is shown in Google, Bing and other search engines. > To have the page correctly related in search machines with the project it is > desirable to have the project name in the HTML title. > For testing you can use the appended pom.xml > Best regards > Heinrich Schuchardt -- 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-72) Allow declaring Google AdSense in site.xml
Dennis Lundberg created DOXIASITETOOLS-72: - Summary: Allow declaring Google AdSense in site.xml Key: DOXIASITETOOLS-72 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-72 Project: Maven Doxia Sitetools Issue Type: New Feature Components: Decoration model Affects Versions: 1.2 Reporter: Dennis Lundberg To get this rolling let's start by adding the possibility to add the account specifics of Google AdSense to the site.xml. There are two pieces of information needed for this: a client id and a slot id. The other data needed for publishing AdSense are the width and height. Since these are specific to how the skin layout, it will not be possible to set these in site.xml When this new feature is available in site.xml people can start adding AdSense code in their skin implementations. The default Velocity template will not include any html or JavaScript for AdSense. This is something that each skin implementor must do themselves. -- 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-72) Allow declaring Google AdSense in site.xml
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIASITETOOLS-72. - Resolution: Fixed Fix Version/s: 1.3 Assignee: Dennis Lundberg Fixed in [r1325495|http://svn.apache.org/viewvc?view=revision&revision=1325495]. > Allow declaring Google AdSense in site.xml > -- > > Key: DOXIASITETOOLS-72 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-72 > Project: Maven Doxia Sitetools > Issue Type: New Feature > Components: Decoration model >Affects Versions: 1.2 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 1.3 > > > To get this rolling let's start by adding the possibility to add the account > specifics of Google AdSense to the site.xml. There are two pieces of > information needed for this: a client id and a slot id. The other data needed > for publishing AdSense are the width and height. Since these are specific to > how the skin layout, it will not be possible to set these in site.xml > When this new feature is available in site.xml people can start adding > AdSense code in their skin implementations. The default Velocity template > will not include any html or JavaScript for AdSense. This is something that > each skin implementor must do themselves. -- 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-482) SvnInfoConsumer not I18N aware
[
https://jira.codehaus.org/browse/SCM-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296367#comment-296367
]
Robert Scholte commented on SCM-482:
Fixed in [r1325497|http://svn.apache.org/viewvc?rev=1325497&view=rev]
Verified by changing its value to {{"de"}}, which caused some failing tests.
With {{"en"}} all svnexe tests succeed.
> SvnInfoConsumer not I18N aware
> --
>
> Key: SCM-482
> URL: https://jira.codehaus.org/browse/SCM-482
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.2
> Environment: Debian GNU Linux (squeeze), Subversion 1.5.6
>Reporter: Grzegorz Grzybek
> Fix For: 1.x
>
>
> There is a problem with class
> {{org.apache.maven.scm.provider.svn.svnexe.command.info.SvnInfoConsumer}} -
> it heavely depends on:
> bq. svn --non-interactive info
> result
> which differs under different locale settings
> It would be *much* better if
> {{org.apache.maven.scm.provider.svn.svnexe.command.info.SvnInfoCommand.createCommandLine(SvnScmProviderRepository,
> ScmFileSet, boolean, String)}} use:
> bq. svn --non-interactive --xml info
> instead of:
> bq. svn --non-interactive info
> the former produces:{panel}
>
>
> kind="dir"
>path="."
>revision="1647">
> http://javelin/svn/com.winuel.sip/trunk
>
> http://javelin/svn/com.winuel.sip
> e17e3fd1-5418-7e4b-8253-85740d203573
>
>
> normal
> infinity
>
> revision="1647">
> grgr
> 2009-07-14T11:49:37.776704Z
>
> {panel} and the latter (on my computer):{panel}
> Ścieżka: .
> URL: http://javelin/svn/com.winuel.sip/trunk
> Katalog główny repozytorium: http://javelin/svn/com.winuel.sip
> UUID repozytorium: e17e3fd1-5418-7e4b-8253-85740d203573
> Wersja: 1647
> Rodzaj obiektu: katalog
> Zlecenie: normalne
> Autor ostatniej zmiany: grgr
> Ostatnio zmieniona wersja: 1647
> Data ostatniej zmiany: 2009-07-14 13:49:37 +0200 (Wt){panel}
> It's obvious that this command should be locale-independent
> regards
> Grzegorz Grzybek
--
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-482) SvnInfoConsumer not I18N aware
[
https://jira.codehaus.org/browse/SCM-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed SCM-482.
--
Resolution: Fixed
Fix Version/s: 1.7
Assignee: Robert Scholte
> SvnInfoConsumer not I18N aware
> --
>
> Key: SCM-482
> URL: https://jira.codehaus.org/browse/SCM-482
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.2
> Environment: Debian GNU Linux (squeeze), Subversion 1.5.6
>Reporter: Grzegorz Grzybek
>Assignee: Robert Scholte
> Fix For: 1.7, 1.x
>
>
> There is a problem with class
> {{org.apache.maven.scm.provider.svn.svnexe.command.info.SvnInfoConsumer}} -
> it heavely depends on:
> bq. svn --non-interactive info
> result
> which differs under different locale settings
> It would be *much* better if
> {{org.apache.maven.scm.provider.svn.svnexe.command.info.SvnInfoCommand.createCommandLine(SvnScmProviderRepository,
> ScmFileSet, boolean, String)}} use:
> bq. svn --non-interactive --xml info
> instead of:
> bq. svn --non-interactive info
> the former produces:{panel}
>
>
> kind="dir"
>path="."
>revision="1647">
> http://javelin/svn/com.winuel.sip/trunk
>
> http://javelin/svn/com.winuel.sip
> e17e3fd1-5418-7e4b-8253-85740d203573
>
>
> normal
> infinity
>
> revision="1647">
> grgr
> 2009-07-14T11:49:37.776704Z
>
> {panel} and the latter (on my computer):{panel}
> Ścieżka: .
> URL: http://javelin/svn/com.winuel.sip/trunk
> Katalog główny repozytorium: http://javelin/svn/com.winuel.sip
> UUID repozytorium: e17e3fd1-5418-7e4b-8253-85740d203573
> Wersja: 1647
> Rodzaj obiektu: katalog
> Zlecenie: normalne
> Autor ostatniej zmiany: grgr
> Ostatnio zmieniona wersja: 1647
> Data ostatniej zmiany: 2009-07-14 13:49:37 +0200 (Wt){panel}
> It's obvious that this command should be locale-independent
> regards
> Grzegorz Grzybek
--
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-70) Html title of generated pages does not include project name
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296383#comment-296383 ] Heinrich Schuchardt commented on DOXIASITETOOLS-70: --- Dear Dennis, with the artifacts available from http://repository.apache.org/snapshots/ the problem is resolved. Thank you for your support. Best regards Heinrich > Html title of generated pages does not include project name > --- > > Key: DOXIASITETOOLS-70 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-70 > Project: Maven Doxia Sitetools > Issue Type: Bug > Components: Site renderer >Affects Versions: 1.2 > Environment: Apache Maven 3.0.3 > (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200) > Maven home: /usr/local/apache-maven/apache-maven-3.0.3 > Java version: 1.6.0_18, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: en_US, platform encoding: ANSI_X3.4-1968 > OS name: "linux", version: "2.6.18-028stab092.1", arch: "amd64", family: > "unix" >Reporter: Heinrich Schuchardt >Assignee: Dennis Lundberg > Fix For: 1.3 > > Attachments: pom.xml, pom.xml > > > Dear maintainer, > according to > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > the title of each page should be the concatenation of the site title and the > title of the current page. E.g. if in pom.xml the name element is: > Site Plugin Test > then target/site/index.html should have a line > Site Plugin Test - About > This is not working. The site title is missing and the created index.html > only contains > About > This effects how the page is shown in Google, Bing and other search engines. > To have the page correctly related in search machines with the project it is > desirable to have the project name in the HTML title. > For testing you can use the appended pom.xml > Best regards > Heinrich Schuchardt -- 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] (MSITE-619) Method calculateLink threw exception for reference $PathTool
[ https://jira.codehaus.org/browse/MSITE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl reopened MSITE-619: - Assignee: (was: Lukas Theussl) I doubt that this worked with any recent version of the site plugin. Unfortunately, the Exception message comes from the Velocity parser, so we'd have to manually check for null hrefs in the vm script. I still maintain that a href is required, so the Exception is valid, but I'd be happy to apply a patch to log a better error message. > Method calculateLink threw exception for reference $PathTool > > > Key: MSITE-619 > URL: https://jira.codehaus.org/browse/MSITE-619 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3, site descriptor >Affects Versions: 3.0 > Environment: Maven 3.0.3, MacOS-X 10.6.8 >Reporter: Oliver Boehm > > After running 'mvn site:site' I get the following errors after upgrading to > maven-site-plugin 3.0 (with 3.0-beta-3 this error does not happen!): > ... > [ERROR] Method calculateLink threw exception for reference $PathTool in > template org/apache/maven/doxia/siterenderer/resources/default-site.vm at > [2,31] > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 34.451s > [INFO] Finished at: Sun Nov 20 20:29:56 CET 2011 > [INFO] Final Memory: 22M/81M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.0:site (default-cli) on project > patterntesting-rt: Error during page generation: Error while generating code. > Invocation of method 'calculateLink' in class > org.codehaus.plexus.util.PathTool threw exception > java.lang.NullPointerException @ > org/apache/maven/doxia/siterenderer/resources/default-site.vm[2,41] -> [Help > 1] > ... > These are the POMs which are used: > - > http://patterntesting.cvs.sourceforge.net/viewvc/patterntesting/PatternTesting10/patterntesting-parent/pom.xml > - > http://patterntesting.cvs.sourceforge.net/viewvc/patterntesting/PatternTesting10/patterntesting-rt/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
