Re: Generating xdoc content to be included into site
Heya,
Try ${project.build.directory}/generated-site or change the
generatedSiteDirectory parameter, see
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#generatedSiteDirectory
HTH,
-Lukas
Am 01.02.2017 um 11:49 schrieb Maxim Solodovnik:
Hello Karl,
Thanks a lot for the quick response
pre-site phase is being called if I'm using "mvn site"
but XML files from target/generated-sources/site/xdoc/ are not being
used while site generation ...
Should it be generated to the different folder?
On Wed, Feb 1, 2017 at 3:52 PM, Karl Heinz Marbaise wrote:
Hi,
On 01/02/17 06:52, Maxim Solodovnik wrote:
Hello All,
I wonder is it possible to generate content for maven site plugin?
We are using xdoc for our site. I would like to generate source using
xml-maven-plugin.
Right now I do it in generate-sources phase and polluting src/site/xdoc/
folder
I tried to change the process as follows:
1) generate site source in pre-site phase
2) put generated content into
${project.build.directory}/generated-sources/site/xdoc/
unfortunately it doesn't work this way :(
It seems pre-site phase is not being called during mvn site:site :(
What am I doing wrong?
If you call site:site you call the goal of the plugin and NOT the life
cycle. You need to call mvn site instead than pre-site and site life cycle
phases will run...
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Breadcrumb inheritance in site.xml
that wasn't possible during my time of activity, not sure if anything changed since: http://mail-archives.apache.org/mod_mbox/maven-users/201104.mbox/%3c4da464c8.2060...@apache.org%3E Cheers, -Lukas Am 12.06.2014 04:52, schrieb Benson Margulies: Is there a way to reset the breadcrumbs and not inherit them from a parent/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: PDF Plugin custom properties do not appear
Hi Nikola,
Sorry it took me so long, but you wrote just when my vacation started...
I think this is a feature that was never implemented, as the docs [1]
only mention ... System properties, Maven project properties and some
date properties. that can be filtered, ie no custom properties.
However, given that this works fine with the site plugin I would call it
a bug really, consider filing an issue in jira:
http://jira.codehaus.org/browse/MPDF
cheers,
-Lukas
[1] http://maven.apache.org/plugins/maven-pdf-plugin/examples/filtering.html
Am 05.08.2013 11:29, schrieb Nikola Mishev:
Hi all,
I am trying to generate a PDF, but I face the following issue.
Although I do have properties defined in my pom.xml they are not properly
filtered in any type of content I use.
e.g. I have the property defined in pom.xml
properties
myPropertyMy other value/myProperty
/properties
If I use this property in pdf.xml it appears in the generated PDF, but if I
set it in an .apt.vm file as ${myProperty} it doesn't.
The apt file is also with .vm extension as documented on the site.
On the other hand properties as ${project.name} work fine.
Do you have an idea what am I missing?
Thanks,
Nikola
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with multi-module site
Hi Russel, I checked your project at http://russgold.github.io/russgold/maven-video/sample10.zip Your site directory is in the project's root directory, it should be in src/site/ HTH, Lukas Russell Gold wrote: Hi Lukas, My problem is that the custom menus don't even show up in the parent, nor do the breadcrumbs. The docs suggest that the site descriptors are not attached automatically in maven 3, but they certainly were in my single-module trial, and they seem to be in Ryan's example, as well. I suspect the docs are a bit out of date. Thanks, Russ On Jun 20, 2013, at 8:53 AM, Lukas Theussl ltheu...@apache.org wrote: Custom menus are not inherited by default, I guess you have read the docs: http://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html The breadcrumbs should be inherited as long as the parent defines some: http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html#Breadcrumbs HTH, -Lukas Russell Gold wrote: Thanks for the suggestion; all of the sub-modules are indeed in properly named directories, as far as I can tell. The top-level project wasn't, but fixing that didn't do anything. Thanks, Russ On Jun 20, 2013, at 1:17 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: If I remember correctly, one problem is, when the name/directory of the module does not equal the artifactId of the module. Regards Mirko -- Sent from my mobile On Jun 20, 2013 1:04 AM, Russell Gold r...@gold-family.us wrote: I am using the site-maven-plugin (version 3.3) and cannot seem to get it to work. Using the exact same site.xml and additional files (faq, apt and xhtml types) that worked fine in a single project site, I am not getting breadcrumbs or custom menu items. I do get the submodules with their own sites, each of which is inheriting the reports from the parent, but that's it. My (58K) project is at http://russgold.github.io/russgold/maven-video/sample10.zip Thanks Russ - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html! - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with multi-module site
Custom menus are not inherited by default, I guess you have read the docs: http://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html The breadcrumbs should be inherited as long as the parent defines some: http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html#Breadcrumbs HTH, -Lukas Russell Gold wrote: Thanks for the suggestion; all of the sub-modules are indeed in properly named directories, as far as I can tell. The top-level project wasn't, but fixing that didn't do anything. Thanks, Russ On Jun 20, 2013, at 1:17 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: If I remember correctly, one problem is, when the name/directory of the module does not equal the artifactId of the module. Regards Mirko -- Sent from my mobile On Jun 20, 2013 1:04 AM, Russell Gold r...@gold-family.us wrote: I am using the site-maven-plugin (version 3.3) and cannot seem to get it to work. Using the exact same site.xml and additional files (faq, apt and xhtml types) that worked fine in a single project site, I am not getting breadcrumbs or custom menu items. I do get the submodules with their own sites, each of which is inheriting the reports from the parent, but that's it. My (58K) project is at http://russgold.github.io/russgold/maven-video/sample10.zip Thanks Russ - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html! - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Converting preformatted APT to PDF
Peter Lord wrote: On 11/01/13 11:26, Lukas Theussl wrote: Peter Lord wrote: On 11/01/13 08:14, Lukas Theussl wrote: My question was: is the wrapping different in the apt source and the pdf/html output? Pre-formatted text preserves line-breaks, so you would have to adjust the apt source to fit your needs. However, it seems to me that it should be possible to modify this behavior with some xsl-fo attributes as you have indicated. You'll have to play around with some keep-together settings, in particular keep-together.within-line, see http://stackoverflow.com/questions/2227797/xls-fo-fop-0-94-using-the-keep-together-with-wrap-option-wrap But I'm no fo expert, maybe try a specialized fo list/forum if you can't get it to work. Thanks again. I found that the maven generated .fo file is not removed - which helps debugging!. Reading this I can get my pdf-config.xml to insert the fop attributes in the correct place. However its still not wrapping. I understand that the FOP version used by the pdf plug-in (0.95) is now old with line break related issues resolved. I think I'll need to wait until the plug-in uses 1.0 or 1.1 Indeed, that's another issue I had forgotten. Unfortunately, the fop upgrade to 1.0 is stalled because of https://jira.codehaus.org/browse/DOXIA-409 and I just tried locally to use fop 1.1 and got stuck with a missing dependency which is apparently known to the fop people: http://comments.gmane.org/gmane.text.xml.fop.user/34912 So waiting for another fop release again... :( -Lukas Hi Lukas / all, Are you aware of any progress in these areas ? I tried using the trunk, 1.3-SNAPSHOT, but this brought in the same fop version. I haven't checked anything for a long time but the latest FOP version is still 1.1, so I don't expect any progress here. Sorry... -Lukas Thanks again, Pete - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Missing parent link in site, was Re: Error resolving parent pom (descriptor?) with site plugin
IIUC your findings are summed up here: http://maven.apache.org/plugins/maven-site-plugin/faq.html#Use_of_url HTH, -Lukas On 05/23/2013 04:24 AM, Dan Rollo wrote: Well, I never saw a response to this, and finally got tired of the missing 'parent' links in maven generated sites. At some point, it appears the maven-site-plugin stopped using the parent projects URL, and instead looks for the parent projects distributionManagement - site - url to determine if the parent project is reachable during site generation. So...to answer my own question: My workaround was to define a distMgt-site-url tag in the parent pom. Due to the way m-s-p tries to inherit the parent value of this URL and then append it's own artifactId (which works if your parent is located above you - was more viable in a svn world, not so true in a git world anymore), I also have to re-define the distMgt-site-url again in each of my child poms to ensure the child site's value is correct. Hope this might help anyone else who is wondering how to fix the message: [WARNING] Unable to find a URL to the parent project. The parent menu will NOT be added. (My original post was about a build problem, but the missing parent link was also annoying...) Dan On 12/12/2012 11:11 PM, Dan Rollo wrote: Hi, I'm seeing something I can't figure out, and wondering if this is a known issue. I have a multi-module maven project, which has as its parent a shared corporate pom (in a totally different source bank location). I can build this project successfully via mvn package. However, when I try to run the site goal, I get strange errors: [INFO] Parent project loaded from repository: xxx:pom-parent:pom:1.0.1 ... [WARNING] Unable to find a URL to the parent project. The parent menu will NOT be added. Downloading: http://xxx:8080/archiva/repository/cache-central/xxx/pom-parent/1.0.1/pom-parent-1.0.1.pom mojoFailed org.apache.maven.plugins:maven-site-plugin:3.2(default-site) and after that message, the build fails. Just in case, I verified the parent poms site descriptor is available both in our shared repo, and was downloaded to the local repo. It as if the site plugin can't find the parent pom. Here's a another error message: Unable to read local module-POM cause : SiteToolException: Unable to read local module-POM Odder still, the site goal used to work fine. This problem just started happening after I released a new version of the parent pom, and updated the project to use the new released parent. Thanks, Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Hiding markup from Velocity during site generation with md.vm source files
Did you try to escape the special character:
\#\#\# ?
-Lukas
On 03/20/2013 08:06 PM, Kevin Minder wrote:
Point of clarification. Velocity is eating the ### Sub-heading line because
from its perspective this is a comment and doesn't belong in the rendered
output.
On 3/20/13 3:04 PM, Kevin Minder wrote:
Hi Everyone,
I'm using Markdown formatting to create my site docs. I'm also using
Velocity
templating to pass some version information from the pom to the md.vm files.
Lets assume that I have a md.vm file like this:
Heading
--
### Sub-heading
Big long hairy code block with some nasty XML like this
messageJava failed, error
message[\${wf:errorMessage(wf:lastErrorNode())}]/message
I have two issues.
1. Velocity is eating the ### Sub-heading so my html doesn't have these
section header. I worked around this BTW by defining a property
HHH###/HHH in my POM and then using ${HHH} in my md.vm but this is a bit
of a hack and hurts the readability of the raw file.
2. I can't figure out how to hide the code block from Velocity and it is
choking on the nasty XML it.
I was hoping to be able to do this.
Heading
--
#[[###]]# Sub-heading
#[[
Big long hairy code block with some nasty XML like this
messageJava failed, error
message[\${wf:errorMessage(wf:lastErrorNode())}]/message
]]#
It looks like Velocity doesn't remove the ## markup from its rendered
output so then Markdown chokes on the #[[.
Anyone have any other ideas?
Kevin.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Hiding markup from Velocity during site generation with md.vm source files
Hmm, not sure if this is the correct behavior, the markdown module has never
been very well tested.
I would probably use your property hack, you don't have to define it in the pom
though, you can set it inside the template file like:
#set( $H = '###' )
$H
HTH,
-Lukas
On 03/21/2013 01:00 PM, Kevin Minder wrote:
Just did and that doesn't work. Velocity doesn't remove the line from the
output
(which is good) but Markdown for some reason doesn't interpret it as a
heading
(which is bad). So I end up with:
### Section Test
in the HTML instead of a nice shaded box.
On 3/21/13 3:27 AM, Lukas Theussl wrote:
Did you try to escape the special character:
\#\#\# ?
-Lukas
On 03/20/2013 08:06 PM, Kevin Minder wrote:
Point of clarification. Velocity is eating the ### Sub-heading line because
from its perspective this is a comment and doesn't belong in the rendered
output.
On 3/20/13 3:04 PM, Kevin Minder wrote:
Hi Everyone,
I'm using Markdown formatting to create my site docs. I'm also using
Velocity
templating to pass some version information from the pom to the md.vm
files.
Lets assume that I have a md.vm file like this:
Heading
--
### Sub-heading
Big long hairy code block with some nasty XML like this
messageJava failed, error
message[\${wf:errorMessage(wf:lastErrorNode())}]/message
I have two issues.
1. Velocity is eating the ### Sub-heading so my html doesn't have these
section header. I worked around this BTW by defining a property
HHH###/HHH in my POM and then using ${HHH} in my md.vm but this is a
bit
of a hack and hurts the readability of the raw file.
2. I can't figure out how to hide the code block from Velocity and it is
choking on the nasty XML it.
I was hoping to be able to do this.
Heading
--
#[[###]]# Sub-heading
#[[
Big long hairy code block with some nasty XML like this
messageJava failed, error
message[\${wf:errorMessage(wf:lastErrorNode())}]/message
]]#
It looks like Velocity doesn't remove the ## markup from its rendered
output so then Markdown chokes on the #[[.
Anyone have any other ideas?
Kevin.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Doxia markdown module: em-dash?
The markdown module uses the pegdown library (http://pegdown.org/) for parsing, any problems should be reported there. HTH, -Lukas Laird Nelson wrote: Hello; how do I render an em dash using the Doxia Markdown module? The following source code results in an empty string in the final HTML output. Each of the following non-whitespace lines represents an attempt: mdash; -- --- amp;mdash; I can make it render an em dash using #8212; but I'd like to understand why the other options don't work. Thanks, Laird - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Converting preformatted APT to PDF
My question was: is the wrapping different in the apt source and the pdf/html output? Pre-formatted text preserves line-breaks, so you would have to adjust the apt source to fit your needs. However, it seems to me that it should be possible to modify this behavior with some xsl-fo attributes as you have indicated. You'll have to play around with some keep-together settings, in particular keep-together.within-line, see http://stackoverflow.com/questions/2227797/xls-fo-fop-0-94-using-the-keep-together-with-wrap-option-wrap But I'm no fo expert, maybe try a specialized fo list/forum if you can't get it to work. HTH, -Lukas Peter Lord wrote: On 11/01/13 07:34, Lukas Theussl wrote: Are you saying that lines in the pdf/html output are wrapped differently than in the apt source? Pre-formatted text by definition preserves both spaces and line breaks so the text should be rendered exactly as in the apt source. Many thanks for your reply. What I see in the pdf is :- * text flowing off the end of the page - http://plord.co.uk/bex/page.png * text flowing off the side of the page - http://plord.co.uk/bex/width.png I really want to see text wrapped. Thanks, Pete -Lukas Peter Lord wrote: Hi All, I've been battling with trying to get preformatted text converted to pdf with the maven pdf plug-in ( http://maven.apache.org/plugins/maven-pdf-plugin/ ). The problem is with long or wide text, the text overflows the paper. The text is not wrapped by line or by page. Text never flows to a second page. The html output is really nice :-) The apt source is :- +-+ large number of lines +-+ I've tried creating pdf-config.xml file :- xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; xsl:attribute-set name=body.pre use-attribute-sets=base.pre.style xsl:attribute name=font-size6pt/xsl:attribute xsl:attribute name=line-height7pt/xsl:attribute xsl:attribute name=keep-togetherauto/xsl:attribute xsl:attribute name=keep-with-next.within-pageauto/xsl:attribute xsl:attribute name=wrap-optionwrap/xsl:attribute /xsl:attribute-set /xsl:stylesheet but no joy. Any suggestions to enable wrapping in pdf ? Many thanks, Pete - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Converting preformatted APT to PDF
Peter Lord wrote: On 11/01/13 08:14, Lukas Theussl wrote: My question was: is the wrapping different in the apt source and the pdf/html output? Pre-formatted text preserves line-breaks, so you would have to adjust the apt source to fit your needs. However, it seems to me that it should be possible to modify this behavior with some xsl-fo attributes as you have indicated. You'll have to play around with some keep-together settings, in particular keep-together.within-line, see http://stackoverflow.com/questions/2227797/xls-fo-fop-0-94-using-the-keep-together-with-wrap-option-wrap But I'm no fo expert, maybe try a specialized fo list/forum if you can't get it to work. Thanks again. I found that the maven generated .fo file is not removed - which helps debugging!. Reading this I can get my pdf-config.xml to insert the fop attributes in the correct place. However its still not wrapping. I understand that the FOP version used by the pdf plug-in (0.95) is now old with line break related issues resolved. I think I'll need to wait until the plug-in uses 1.0 or 1.1 Indeed, that's another issue I had forgotten. Unfortunately, the fop upgrade to 1.0 is stalled because of https://jira.codehaus.org/browse/DOXIA-409 and I just tried locally to use fop 1.1 and got stuck with a missing dependency which is apparently known to the fop people: http://comments.gmane.org/gmane.text.xml.fop.user/34912 So waiting for another fop release again... :( -Lukas Pete HTH, -Lukas Peter Lord wrote: On 11/01/13 07:34, Lukas Theussl wrote: Are you saying that lines in the pdf/html output are wrapped differently than in the apt source? Pre-formatted text by definition preserves both spaces and line breaks so the text should be rendered exactly as in the apt source. Many thanks for your reply. What I see in the pdf is :- * text flowing off the end of the page - http://plord.co.uk/bex/page.png * text flowing off the side of the page - http://plord.co.uk/bex/width.png I really want to see text wrapped. Thanks, Pete -Lukas Peter Lord wrote: Hi All, I've been battling with trying to get preformatted text converted to pdf with the maven pdf plug-in ( http://maven.apache.org/plugins/maven-pdf-plugin/ ). The problem is with long or wide text, the text overflows the paper. The text is not wrapped by line or by page. Text never flows to a second page. The html output is really nice :-) The apt source is :- +-+ large number of lines +-+ I've tried creating pdf-config.xml file :- xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; xsl:attribute-set name=body.pre use-attribute-sets=base.pre.style xsl:attribute name=font-size6pt/xsl:attribute xsl:attribute name=line-height7pt/xsl:attribute xsl:attribute name=keep-togetherauto/xsl:attribute xsl:attribute name=keep-with-next.within-pageauto/xsl:attribute xsl:attribute name=wrap-optionwrap/xsl:attribute /xsl:attribute-set /xsl:stylesheet but no joy. Any suggestions to enable wrapping in pdf ? Many thanks, Pete - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Converting preformatted APT to PDF
Are you saying that lines in the pdf/html output are wrapped differently than in the apt source? Pre-formatted text by definition preserves both spaces and line breaks so the text should be rendered exactly as in the apt source. -Lukas Peter Lord wrote: Hi All, I've been battling with trying to get preformatted text converted to pdf with the maven pdf plug-in ( http://maven.apache.org/plugins/maven-pdf-plugin/ ). The problem is with long or wide text, the text overflows the paper. The text is not wrapped by line or by page. Text never flows to a second page. The html output is really nice :-) The apt source is :- +-+ large number of lines +-+ I've tried creating pdf-config.xml file :- xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; xsl:attribute-set name=body.pre use-attribute-sets=base.pre.style xsl:attribute name=font-size6pt/xsl:attribute xsl:attribute name=line-height7pt/xsl:attribute xsl:attribute name=keep-togetherauto/xsl:attribute xsl:attribute name=keep-with-next.within-pageauto/xsl:attribute xsl:attribute name=wrap-optionwrap/xsl:attribute /xsl:attribute-set /xsl:stylesheet but no joy. Any suggestions to enable wrapping in pdf ? Many thanks, Pete - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven3 PDF-Plugin1.2 - How to disable or change the default generated pdf footer text?
I haven't tested this in a while but the pdf footer should be the same as the site footer, did you try this: http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html#Custom_footer HTH, -Lukas Thorsten Nieser wrote: Hi together, Hopefully anybody could give me short hint how to resolve my current problem. I use Maven3 and the Doxia Pdf-Plugin 1.2 to generate the documentation bundle of the project I currently work on. * org.apache.maven.plugins * maven-pdf-plugin * 1.2 The project shall be released under GPL v.3 to be compatible with the Apache Common license v.2 and so it's not really matching that the generated documentation pdf gets the following footer text added by default: © 2 0 1 3 , NAME . A L L R I G H T S R E S E R V E D. Rights aren't really reserved by me - it's copy left. Is there any possibility to change the content of the footer text line? Thanks for your efforts in advance! With best regards Thorsten - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trouble with link on my 'maven site' when child projects aren't subfolders of parent project
bill_s wrote: After publishing the maven site for my project, I'm having problems with the relative links working correctly on the site menu under the section 'Parent Project'. Right now, it points to '../../index.html'. However, the true location of the parent site is '../parent/index.html' I think the directory structure of our project has something to do with it, but it isn't easy to change and I'm having trouble figuring out where I can make adjustments to fix the site links instead of reorganizing all our projects. Instead of the obvious folder structure for parents and children like this: Our folder structure looks like this: Looking at the pom.xml for CHILD, we have the following defined for the dependencies: and this defined for the parent: I run 'mvn clean' then 'mvn site' then 'mvn site:deploy' (not sure if all those are necessary, but I'm a beginner and I've found it works). When I view the site and look at the webpage for CHILD, the 'Modules' links on the menu of the site link correctly but the 'Parent Project' links do not point to the correct location. It seems they always just point up one level site directory structure. What is the best way to handle this so links to parent project will be correct? For example, instead of the parent of CHILD pointing to ../../index.html, I need it to point to ../parent/index.html. I'm using maven-site-plugin:3.0. I haven't set up any site descriptor files yet, but I can do that if needed. My distributionManagement site url is defined only in the pom.xml file for 'parent'. Solution: specify correct distributionManagement urls in all sub-projects, see http://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html#Staging_and_deploying HTH, -Lukas Thanks, Bill -- View this message in context: http://maven.40175.n5.nabble.com/Trouble-with-link-on-my-maven-site-when-child-projects-aren-t-subfolders-of-parent-project-tp5736877.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: pdf problem
Anders Hammar wrote: Have a look at the PDF Plugin: https://maven.apache.org/plugins/maven-pdf-plugin/ IIRC it doesn't work well with Maven 3. Or possibly not even at all. I've been using the pdf plugin with maven 3 for ages, apart from the missing reports [1] I never noticed any m3 specific problems. Can you elaborate? -Lukas [1] http://jira.codehaus.org/browse/MPDF-48 /Anders On 2012-10-23 22:32, Loay Mohammed wrote: Dear All I have mvn install in my windows 7 and it is working fine, i have documents in xml make by mvn, how can i make it to be in PDF. Thanks -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: doxia-book-maven-plugin - How do I bind book sections to markdown files?
If you only want to generate a pdf parallel to the site, you should rather use the maven-pdf-plugin [1] instead of the doxia-book-maven-plugin. It works better in my experience. HTH, -Lukas [1] http://maven.apache.org/plugins/maven-pdf-plugin/ Oliver Schrenk wrote: Hi, I want to use the markdown files I use for site generation under `src/site/markdown` to also generate a pdf using doxia-book-maven-plugin. I created an examplary `book.xml` under `src/books/book.xml` book xmlns=http://maven.apache.org/BOOK/1.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/BOOK/1.0.0 http://maven.apache.org/xsd/book-1.0.0.xsd; idbook/id titleRefProc Snapshot Process Syntax Guide/title chapters chapter idbind/id titleBindings/title sections section id01-stuff.md/id /section /sections /chapter /chapters /book My `pom.xml` looks like this: ... plugin groupIdorg.apache.maven.doxia/groupId artifactIddoxia-book-maven-plugin/artifactId version1.3-SNAPSHOT/version executions execution phasepre-site/phase goals goalrender-books/goal /goals /execution /executions configuration books book directorysrc/site/markdown/directory descriptorsrc/books/book.xml/descriptor formats format idpdf/id /format /formats /book /books /configuration /plugin ... I get [ERROR] Failed to execute goal org.apache.maven.doxia:doxia-book-maven-plugin:1.3-SNAPSHOT:render-books (default) on projectsnapshot-io-gson: Error while generating book in format 'pdf'. No document that matches section with id=01-json.md. - [Help1] Which is to be expected as I have no clue on how to map my markdown files to the various chapters and sections and I can't find any infos on it. Does anybody know how to do this? Best regards Oliver Schrenk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Can't find site descriptor
For reference: this has been filed before: https://jira.codehaus.org/browse/MSITE-639 Cheers, -Lukas Andy Ruch wrote: Hello, My build is failing because it can't find the site descriptor site_en.xml for the parent pom. I have the goal site:attach-descriptor in the parent pom and the descriptor is being deployed as site.xml. This only seems to be a problem when I'm using a release version of the parent. When I use a snapshot version, the site descriptor gets resolved to site.xml. Can someone tell me why the locale en gets added to the classifier only sometimes? How can I deploy the site descriptor with the locale added? Also, are release and snapshot versions treated differently? Is there a reason that when using a snapshot, the descriptor gets resolved to the site.xml? Maven Version: 3.0.4 Site Version: 3.1 Thanks, Andy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven v3.0.3, PDF plugin v1.1 : fo:list-block is not a valid child element of fo:list-block
Andy wrote: Caused by: org.apache.maven.plugin.MojoExecutionException: Error during document generation: Error creating PDF from /home/andy/work/datanucleus/documentation/m2_accessplatform/target/pdf/mav en- pdf-plugin.fo: org.apache.fop.fo.ValidationException: file:/home/andy/work/datanucleus/documentation/m2_accessplatform/target/pd f/maven- pdf-plugin.fo:28264:175: Error(28264/175): fo:list-block is not a valid child element of fo:list-block. Did you look at the maven-pdf-plugin.fo file under target/pdf/ to see what the fo file looks like? Seems like you ran into a bug, but I don't know enough to say what caused it. If the fo file is wrong, then either your original file has issues or whatever translated the original into this fo file would seem to have an issue. Well I looked at it, but then since I'm not familiar with this FO format wouldn't know what is wrong with it. Since all XDOC files validated, then I'd assume the original file has no issue. Either way I have it in a separate project and is 100% reproduceable. Raised it as https://jira.codehaus.org/browse/MPDF-57 How did you validate the xdocs? When I run 'mvn -Dvalidate=true site:site' on the project you attached at MPDF-57 I get stuck immediately with basic validation errors (no schema definition). See http://maven.apache.org/plugins/maven-site-plugin/faq.html#Can_I_validate_xml HTH, -Lukas Thanks for your reply. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site, deployment url and inheritance
Grégory Joseph wrote:
Hi there,
I've seen this topic debated many times, and still haven't figured
everything out. I was recently confused by the handling and
inheritance of urls in Maven. I think I got most of it, when it comes
to project.url.
Now, when it comes to deploying a site, I'm baffled. Up to
maven-site-plugin 2.1.1, things seem to be fairly understandable. It
wasn't exactly possible (at least to my understanding) to have
multi-module projects sites deployed in a versioned directory
(because ${artifactId}/${version} would be re-interpolated for every
submodule). But at least, I could do a help:effective-pom, and get the
URLs that would be used for deployment.
Now I just tried 3.1, and I'm baffled that I can't seem to be able to
completely override the distributionManagement.site.url defined by my
parent pom. Using help:effective-pom gives me the URLs I expect, and
the ones i would like Maven to use when deploying the site. However,
the plugin seems to think differently, and tries to upload to
relativised urls, somehow inheriting the site url defined in a
corporate parent pom, adding some levels of ../ and finally the path
i'm expecting.
It kind of sounds like MSITE-600 to me, so I'm unsure if/how the issue
was fixed. Example:
* Corporate parent pom defines this site deployment url:
prot://foo/${artifactId}/${version} -- it works for this pom, and it's
a good enough default for most of our single-module projects. Not the
lack of trailing slash, btw.
* Some multi-module project defines this site deployment url:
prot://foo/xuq/lolcats/${version}. And the resulting deployment urls
end up looking like:
prot://foo/corp-parent/12//../../xuq/lolcats/${version} (and I still
don't know where the double slash comes from)
Normalizing this is exactly the same as
prot://foo/xuq/lolcats/${version}, so the deployment location should be
correct. Did you try site:stage to check?
-Lukas
So unlike one of the latest comments in MSITE-600, I'm not even trying
to change the protocol. But it seems that either the wagon (i'm using
dav, if that's relevant), or the Nexus instance I have at the
receiving end, don't cope well with those ../.
Question is two fold:
* Why is the plugin even trying to do that ? Why is it not following
the same rules as effective-pom ? How can one preview what urls will
be used, then ?
* How do people really deploy sites with a version number in the path,
when using a corporate parent pom, without redefining the site.url
for every single project ?
Thanks for any hint or tip !
Cheers,
-greg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Site, deployment url and inheritance
Grégory Joseph wrote:
Just tried staging, and indeed, the paths in that case are correct* -
but again, I'm assuming that's because the normalization is done and
supported by my local FS ?
IIRC normalization is done by the wagon you are using for the deploy, so
it's outside the realm of the site plugin. I seem to remember that this
was also the reason for adding a dot component /./ in the deployment url
because some wagons only worked like that (I might be wrong though, it's
been a while...).
OTOH, I don't quite see what the problem is, a non-normalized url is
still a valid url and every server/file system should be able to deal
with it. Or do you have a specific actual issue that's caused by it?
There have been issues reported (MSITE-531, MSITE-601) but in each case
the underlying cause was outside maven/wagon/site-plugin.
-g
* with the strange bug that https://nexus.domain.org/xyz; was
converted to targetstaging/http/s.domain.org/xyz ...
that looks weird indeed, if you have a test case I will look at it.
-Lukas
On 2 July 2012 13:57, Grégory Joseph greg@gmail.com wrote:
Hi Lukas,
On 2 July 2012 13:18, Lukas Theussl ltheu...@apache.org wrote:
Grégory Joseph wrote:
It kind of sounds like MSITE-600 to me, so I'm unsure if/how the issue
was fixed. Example:
* Corporate parent pom defines this site deployment url:
prot://foo/${artifactId}/${version} -- it works for this pom, and it's
a good enough default for most of our single-module projects. Not the
lack of trailing slash, btw.
* Some multi-module project defines this site deployment url:
prot://foo/xuq/lolcats/${version}. And the resulting deployment urls
end up looking like:
prot://foo/corp-parent/12//../../xuq/lolcats/${version} (and I still
don't know where the double slash comes from)
Normalizing this is exactly the same as
prot://foo/xuq/lolcats/${version},
It *should* be, but by using those URLs as-is, Maven relies on the
receiving end to do the normalization.
And I'm still wondering why it bothers doing that in the first place ;)
so the deployment location should be
correct. Did you try site:stage to check?
How is that helping ? I am not worried about inter-module links -
those indeed seem to work - but about why the parent's urls are taken
into account in the first place, and if there's a good reason for
that, then I wonder why normalization doesn't happen on the Maven
side.
Cheers,
-g
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to pass in site source directory into pdf:pdf?
Do you have some source files for the site or only reports? Try to add a
dummy index.apt or any other site source.
HTH,
-Lukas
hujirong wrote:
I got the error below when run mvn pdf:pdf. I tried mvn pdf:pdf
-DsiteDirectory=${basedir}/target/site, still same error.
Thanks
Jirong
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf (default-cli) on project
CdiServicesParent: Error during document generation: Source directory
doesn't exists (C:\Sandbox\MDM\CdiServicesParent\src\site). - [
Help 1]
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-pass-in-site-source-directory-into-pdf-pdf-tp5710298.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to pass in site source directory into pdf:pdf?
The pdf plugin expects some source files to process, you have to add that yourself, see [1] for a mini guide. As I said, a simple dummy index file will presumably get you around the error. Note that not all reports are supported by the pdf plugin [2] and with maven 3 you won't get any reports at all. HTH, -Lukas [1] http://maven.apache.org/guides/mini/guide-site.html [2] http://maven.apache.org/plugins/maven-pdf-plugin/examples/configuring-reports.html hujirong wrote: My site at C:\Sandbox\MDM\CdiServicesParent\target\site is generated by mvn site:site and only contains css and image folder, nothing else. But my pdf:pdf is look for the source of site at C:\Sandbox\MDM\CdiServicesParent\src\site. How can I pass this in parameters? Thanks Jirong -- View this message in context: http://maven.40175.n5.nabble.com/How-to-pass-in-site-source-directory-into-pdf-pdf-tp5710298p5710305.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with Maven Project Info Reports Plugin in maven 3
http://maven.apache.org/plugins/maven-project-info-reports-plugin/examples/selective-project-info-reports.html Note the different reporting configuration in maven 3: http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Configuration_formats HTH, -Lukas Subash Chaturanga wrote: Hi all, NOTE : In other words, in my maven-project-info-reports-plugin, it generates following.(as logs indicates). I want to remove generating two of them. Which are *Dependency Management* report and *Dependencies* report . It will be great if anybody can provide me a solution. [INFO] Generating About report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Source Repository report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Plugin Management report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Mailing Lists report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Issue Tracking report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Project Plugins report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Project Summary report--- maven-project-info-reports-plugin:2.2 [INFO] Generating *Dependency Management* report--- maven-project-info-reports-plugin:2.2 [INFO] Generating *Dependencies* report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Project License report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Project Team report--- maven-project-info-reports-plugin:2.2 [INFO] Generating Continuous Integration report--- maven-project-info-reports-plugin:2.2 On Wed, Mar 21, 2012 at 2:49 PM, Subash Chaturangasubash...@gmail.comwrote: Hi all, I am using maven 3. In Maven Project Info Reports Plugin (version 2.4), I am having problems in report generating. I found out that, the reason cause of report generation related to dependency management . Because in maven-project-info-reports-plugin they have several goals running and one of them, which is unnecessary for me is project-info-reports:dependency-management which causing me trouble (hangs the build for 4-5 mins saying [WARNING] The repository url 'https://repository.jboss.org/maven2/' is invalid - Repository 'jboss-deprecated-repository' will be blacklisted.). Is there a way to exclude an goal from the project-info-reports plugin to get rid from this issue. (i.e project-info-reports:dependency-management) Thanks /Subash - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy upload location
Documented behavior: If subprojects inherit the site URL from a parent
POM, they will automatically append their artifactId to form their
effective deployment location.
This is the default behavior and currently cannot be switched off. If
you want to change this, you have to explicitly set the url in all
sub-projects.
HTH,
-Lukas
David Kendall wrote:
Is there any way to control the exact upload location when doing a mvn
site-deploy?
I am working with a code base that has a number of parent pom files -
different parents for different types of project. When i do a mvn
site-deploy the site is uploaded to something like
${site.deploy.base.url}/${grandparent.artifactid}/${parent.artifactid}/${project.artifactId}/...
What I really want is for the site-deploy to ignore the parent poms and
to upload to a pattern more like this
${site.deploy.base.url}/${project.groupId}/${project.artifactId}/${project.version}/...
In my parent pom I have tried adding specifying
distributionManagement
site
iddocumentation-site/id
url${site.deploy.base.url}/${project.groupId}/${project.artifactId}/${project.version}/url
/site
/distributionManagement
.. but maven just appends the names of the parent poms to the paths anyway.
I am using maven 2.0.11 and deploying using SCP - in case this is
significant.
Is there any way to override the default upload path when deploying a site?
Thanks
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn site:stage is failing on multi-module project
The distributionManagement url is only used to construct relative links between different modules in a multi-module build. The actual absolute location is irrelevant for site:stage, you can use any dummy address, eg file://tmp/junk/ or the one you give below (did you try?). Evidently, you'll have to correct this once you want to really deploy the site. HTH, -Lukas Daivish Shah wrote: HI Lukas, Which means if i don't provide Following TAG it will not work. distributionManagement site idwww.yourcompany.com/id urlscp://www.yourcompany.com/www/docs/project//url /site /distributionManagement For Local repository deployment i don't have any URL setup. As we are trying to explore on this. And once we know things we can setup the website for Javadoc. But there isn't any way to execute the fullsite ? I don't have actual URL to provide here. Please guide me. Thanks. On Mon, Feb 27, 2012 at 11:10 PM, Lukas Theusslltheu...@apache.org wrote: site:stage is just a local preview of site:deploy, you need to specify a distributionManagement.url in the parent pom so links between modules will be consistent with the deployed site. HTH, -Lukas Daivish Shah wrote: Hi, I have project structure as below. maven-parent-project maven-ejb maven-schema maven-ws maven-ear I have all require entry to generate the site in all POM.XML I am able to execute mvn site and mvn site:site command successfully. But when i am trying to execute following command i am getting exception. mvn site:stage [INFO] --**--** [INFO] BUILD FAILURE [INFO] --**--** [INFO] Total time: 1.156s [INFO] Finished at: Mon Feb 27 17:11:46 PST 2012 [INFO] Final Memory: 4M/15M [INFO] --**--** [ERROR] Failed to execute goal org.apache.maven.plugins:**maven-site-plugin:3.0:deploy (default-cli) on project maven-project-parent: Missing distribution management in project Maven Parent Project (maven-parent-project:maven-**parent-project:0.0.1-SNAPSHOT) - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/**confluence/display/MAVEN/** MojoExecutionExceptionhttp://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException As i know if i don't execute this command i can't access all sub modules from the parents index.html so i have to execute this command successfully. Please help me out, Where i am wrong exactly? Thanks. --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn site:stage is failing on multi-module project
site:stage is just a local preview of site:deploy, you need to specify a distributionManagement.url in the parent pom so links between modules will be consistent with the deployed site. HTH, -Lukas Daivish Shah wrote: Hi, I have project structure as below. maven-parent-project maven-ejb maven-schema maven-ws maven-ear I have all require entry to generate the site in all POM.XML I am able to execute mvn site and mvn site:site command successfully. But when i am trying to execute following command i am getting exception. mvn site:stage [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.156s [INFO] Finished at: Mon Feb 27 17:11:46 PST 2012 [INFO] Final Memory: 4M/15M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:deploy (default-cli) on project maven-project-parent: Missing distribution management in project Maven Parent Project (maven-parent-project:maven-parent-project:0.0.1-SNAPSHOT) - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException As i know if i don't execute this command i can't access all sub modules from the parents index.html so i have to execute this command successfully. Please help me out, Where i am wrong exactly? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site:site fails due to not resolving in the reactor?
Benson Margulies wrote: I have a rather vanilla project that fails in release:perform. The real failure underlying this comes from the following recipe: 1) Eliminate the result jar artifacts from the local repo. 2) run mvn install site:site the site phase fails in javadoc, complaining that one of the modules can't find the jar produced by another. I can reproduce this with 3.0.4. I can probably build up a test case, but it's hard for me to believe that this does not result from some fairly simple mischief. Does this ring any bells? one bell ringing here: http://jira.codehaus.org/browse/MSITE-171 HTH, -Lukas The error message when it fails is: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-cli) on project gcoref: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal on project gcoref-tools: Could not resolve dependencies for project com.basistech.gcoref:gcoref-tools:jar:2-bim-candidates-SNAPSHOT: Failure to find com.basistech.gcoref:gcoref-core:jar:2-bim-candidates-SNAPSHOT in http://maven.basistech.net/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of Nexus has elapsed or updates are forced - [Help 1] The reporting section of the top-level effective Pom, which I imagine is the most relevant stuff, is : reporting outputDirectory/Users/benson/x/gcoref-tc/target/site/outputDirectory plugins plugin artifactIdmaven-site-plugin/artifactId version3.0/version configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-project-info-reports-plugin/artifactId version2.4/version reportSets reportSet reports reportsummary/report reportindex/report reportdependencies/report reportissue-tracking/report reportscm/report /reports configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /reportSet /reportSets configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.8/version reportSets reportSet idhtml/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idnon-aggregate/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idaggregate/id reports reportaggregate/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet /reportSets configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /plugin /plugins /reporting - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Method calculateLink threw exception...
Check that all item elements in your site.xml have a href, see http://jira.codehaus.org/browse/MSITE-619 HTH, -Lukas Thomas Scheffler wrote: Hi, I'm having issues with mvn site resulting in a NullPointer exception. Could someone give me a hint what can cause these exceptions? regards Thomas [INFO] Generating Developer Activity report --- maven-changelog-plugin:2.2 [INFO] Using existing changelog.xml... [DEBUG] Multipage report: 0 subreports [DEBUG] Velocimacro : added #link( href name target img position alt border width height ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #image( img alt border width height ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #banner( banner id ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #links( links ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #breadcrumbs( breadcrumbs ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #displayTree( display item ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #menuItem( item ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #mainMenu( menus ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #copyright( ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #publishDate( position publishDate version ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #poweredByLogo( poweredBy ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #googleAnalytics( accountId ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [ERROR] Method calculateLink threw exception for reference $PathTool in template org/apache/maven/doxia/siterenderer/resources/default-site.vm at [2,29] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.564s [INFO] Finished at: Wed Jan 18 10:18:07 CET 2012 [INFO] Final Memory: 26M/618M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project mycore-parent: 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,39] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project mycore-parent: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: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: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:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at
Re: [doxia] sink.unknown and sink.figureGraphics
The Doxia AbstractXmlParser and XhtmlBaseParser contain usage examples of most sink events, see eg [1,2]. Otherwise I would probably need more information to be able to help. Cheers, -Lukas [1] http://maven.apache.org/doxia/doxia/doxia-core/xref/org/apache/maven/doxia/parser/AbstractXmlParser.html#390 [2] http://maven.apache.org/doxia/doxia/doxia-core/xref/org/apache/maven/doxia/parser/XhtmlBaseParser.html#498 On Fri, Dec 23, 2011 at 11:53 PM, qualitesys59 dcrue...@qualitesys.comwrote: Looking for a working example of sink.unkown and sink.figureGraphics fonctions. I have a lot of pb with the sinkFactory.createSink initialisation process and org.codehaus.plexus.PlexusContainer jar download from Maven Central. Can you help with good tips, docs, tutorials ? Thanks -- View this message in context: http://maven.40175.n5.nabble.com/doxia-sink-unknown-and-sink-figureGraphics-tp5098225p5098225.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: APT: How to add relative links with special symbols?
Tsz-Wo Nicholas Sze wrote:
Hi Lukas,
Thanks a lot for the reply. So there is no way to do it due to DOXIA-397.
As noted there, a workaround is to use absolute links.
I got a second question: Is it possible to add links in verbatim text? The
following does not work.
No, as documented at
http://maven.apache.org/doxia/references/apt-format.html:
'Like in HTML, verbatim text is preformatted. Unlike HTML, verbatim text
is escaped: inside a verbatim display, markup is not interpreted by the
APT processor.'
Cheers,
-Lukas
+---
A link: {{{http://host/foo}foo}}
+---
~~ BAD: The output is preA link: {{{http://host/foo}foo}}/pre.
Regards,
Nicholas
From: Lukas Theusslltheu...@apache.org
To: Maven Users Listusers@maven.apache.org
Sent: Wednesday, December 7, 2011 11:17 PM
Subject: Re: APT: How to add relative links with special symbols?
That's a known issue and discussed here:
http://jira.codehaus.org/browse/DOXIA-397
HTH,
-Lukas
Tsz-Wo Nicholas Sze wrote:
Hi,
I tried to add relative links with special symbols (e.g. '%', ' ', '(') to apt
docs. However, the special symbols are removed/replaced in the generated doc
and so the link does not work. For examples,
* {{{../api/Test.html#foo(int, String)}Unespaced relative url}}
~~ BAD: It becomesa href=../api/Test.html#fooint_StringUnespaced relative
url/a
* {{{../api/Test.html#foo%28int,%20String%29}Espaced relative url}}
~~ BAD: It becomesa href=../api/Test.html#foo28int20String29Espaced relative
url/a
I notice that it works for absolute links.
* {{{http://host/api/Test.html#foo(int, String)}Unespaced absolute url}}
~~ GOOD: It becomesa class=externalLink
href=http://host/api/Test.html#foo(int, String)Unespaced absolute
url/a
* {{{http://host/api/Test.html#foo%28int,%20String%29}Espaced absolute
url}}
~~ GOOD: It becomesa class=externalLink
href=http://host/api/Test.html#foo%28int,%20String%29;Espaced
absolute url/a
I apologize if this is not the correct emailing list for the question.
Regards,
Nicholas
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: APT: How to add relative links with special symbols?
Use xdoc for anything serious, that's my trick! :)
-Lukas
Tsz-Wo Nicholas Sze wrote:
Hi Lukas,
I have read the apt doc but I wonder if you may have some trick to do it. :)
Thanks again.
Nicholas
From: Lukas Theusslltheu...@apache.org
To: Maven Users Listusers@maven.apache.org
Sent: Thursday, December 8, 2011 12:44 AM
Subject: Re: APT: How to add relative links with special symbols?
Tsz-Wo Nicholas Sze wrote:
Hi Lukas,
Thanks a lot for the reply. So there is no way to do it due to DOXIA-397.
As noted there, a workaround is to use absolute links.
I got a second question: Is it possible to add links in verbatim text? The
following does not work.
No, as documented at
http://maven.apache.org/doxia/references/apt-format.html:
'Like in HTML, verbatim text is preformatted. Unlike HTML, verbatim text
is escaped: inside a verbatim display, markup is not interpreted by the
APT processor.'
Cheers,
-Lukas
+---
A link: {{{http://host/foo}foo}}
+---
~~ BAD: The output is preA link: {{{http://host/foo}foo}}/pre.
Regards,
Nicholas
From: Lukas Theusslltheu...@apache.org
To: Maven Users Listusers@maven.apache.org
Sent: Wednesday, December 7, 2011 11:17 PM
Subject: Re: APT: How to add relative links with special symbols?
That's a known issue and discussed here:
http://jira.codehaus.org/browse/DOXIA-397
HTH,
-Lukas
Tsz-Wo Nicholas Sze wrote:
Hi,
I tried to add relative links with special symbols (e.g. '%', ' ', '(') to apt
docs. However, the special symbols are removed/replaced in the generated doc
and so the link does not work. For examples,
* {{{../api/Test.html#foo(int, String)}Unespaced relative url}}
~~ BAD: It becomesa href=../api/Test.html#fooint_StringUnespaced relative
url/a
* {{{../api/Test.html#foo%28int,%20String%29}Espaced relative url}}
~~ BAD: It becomesa href=../api/Test.html#foo28int20String29Espaced relative
url/a
I notice that it works for absolute links.
* {{{http://host/api/Test.html#foo(int, String)}Unespaced absolute url}}
~~ GOOD: It becomesa class=externalLink
href=http://host/api/Test.html#foo(int, String)Unespaced absolute
url/a
* {{{http://host/api/Test.html#foo%28int,%20String%29}Espaced absolute
url}}
~~ GOOD: It becomesa class=externalLink
href=http://host/api/Test.html#foo%28int,%20String%29;Espaced
absolute url/a
I apologize if this is not the correct emailing list for the question.
Regards,
Nicholas
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: APT: How to add relative links with special symbols?
That's a known issue and discussed here:
http://jira.codehaus.org/browse/DOXIA-397
HTH,
-Lukas
Tsz-Wo Nicholas Sze wrote:
Hi,
I tried to add relative links with special symbols (e.g. '%', ' ', '(') to apt
docs. However, the special symbols are removed/replaced in the generated doc
and so the link does not work. For examples,
* {{{../api/Test.html#foo(int, String)}Unespaced relative url}}
~~ BAD: It becomesa href=../api/Test.html#fooint_StringUnespaced relative
url/a
* {{{../api/Test.html#foo%28int,%20String%29}Espaced relative url}}
~~ BAD: It becomesa href=../api/Test.html#foo28int20String29Espaced relative
url/a
I notice that it works for absolute links.
* {{{http://host/api/Test.html#foo(int, String)}Unespaced absolute url}}
~~ GOOD: It becomesa class=externalLink
href=http://host/api/Test.html#foo(int, String)Unespaced absolute
url/a
* {{{http://host/api/Test.html#foo%28int,%20String%29}Espaced absolute url}}
~~ GOOD: It becomesa class=externalLink
href=http://host/api/Test.html#foo%28int,%20String%29;Espaced
absolute url/a
I apologize if this is not the correct emailing list for the question.
Regards,
Nicholas
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Generate report PDF with Maven PDF Plugin
Manfred Moser wrote: On 11-11-30 07:43 AM, 4ndrew wrote: Hi, I'd like to generate a PDF file from the results of Maven Surefire Plugin. But when I'm trying to run mvn pdf:pdf its says: *[INFO] Ignoring api call removed in maven 3, no reports are generated!* Any idea would be appreciated! Thx! the pdf plugin is originally a maven 1 plugin and has not really been maintained much. You would probably have to fix it up to get it to work ... This is not correct, the m2 version of the pdf plugin is well-maintained and working: http://maven.apache.org/plugins/maven-pdf-plugin/ The mentioned issue above is probably this: http://jira.codehaus.org/browse/MPDF-41 It's fixed in v. 1.2-SNAPSHOT only, ie not released yet. Some info about report generation in the pdf plugin is available here: http://maven.apache.org/plugins/maven-pdf-plugin/examples/configuring-reports.html HTH, -Lukas manfred - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generate report PDF with Maven PDF Plugin
On Thu, Dec 1, 2011 at 7:58 AM, Lukas Theussl ltheu...@apache.org wrote: Manfred Moser wrote: On 11-11-30 07:43 AM, 4ndrew wrote: Hi, I'd like to generate a PDF file from the results of Maven Surefire Plugin. But when I'm trying to run mvn pdf:pdf its says: *[INFO] Ignoring api call removed in maven 3, no reports are generated!* Any idea would be appreciated! Thx! the pdf plugin is originally a maven 1 plugin and has not really been maintained much. You would probably have to fix it up to get it to work ... This is not correct, the m2 version of the pdf plugin is well-maintained and working: http://maven.apache.org/**plugins/maven-pdf-plugin/http://maven.apache.org/plugins/maven-pdf-plugin/ The mentioned issue above is probably this: http://jira.codehaus.org/**browse/MPDF-41http://jira.codehaus.org/browse/MPDF-41 It's fixed in v. 1.2-SNAPSHOT only, ie not released yet. Sorry to correct myself: it's fixed as being documented that pdf report generation does not work using maven 3, you need to use maven 2. Cheers, -Lukas Some info about report generation in the pdf plugin is available here: http://maven.apache.org/**plugins/maven-pdf-plugin/** examples/configuring-reports.**htmlhttp://maven.apache.org/plugins/maven-pdf-plugin/examples/configuring-reports.html HTH, -Lukas manfred --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unable to generate html report for maven-findbugs plugin
Hi, *) if you want to generate the findbugs report via the site plugin, the configuration should go into the reporting, not build section of the pom *) AFAICS neither formats nor canGenerate are listed as supported configuration options of the findbugs plugin: http://mojo.codehaus.org/findbugs-maven-plugin/2.3.2/findbugs-mojo.html *) the message 'canGenerate is false' probably means that there are no class files to analyse, make sure your project sources are compiled before you run the report HTH, -Lukas On 11/02/2011 11:07 AM, yerra babji wrote: Hi, I am trying to create a findbugs report using mvn site. I pasted my pom.xml entry at the bottom. When I try to execute mvn site, it is giving the following two lines and after completing the command execution, i am unable to see any report generated for findbugs. [INFO] configuring report plugin org.codehaus.mojo:findbugs-maven-plugin:2.3.2 [INFO] *canGenerate is false* I guess issue is because of this canGenerate. how to make this value to true? Can any one please help to generate the findbugs report. I am using Maven 3.0.3. project ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version3.0-beta-2/version configuration reportPlugins plugin groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version2.3.2/version configuration formats formatxml/format formathtml/format /formats canGeneratetrue/canGenerate /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jxr-plugin/artifactId version2.1/version configuration aggregatetrue/aggregate /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId version2.6/version /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.4/version configuration formats formatxml/format formathtml/format /formats /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId version2.6/version /plugin /reportPlugins /configuration /plugin /plugins /build - - - - - /project Thanks, Babji - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: APT: Issue with adding xml code snippets as Verbatim
Try to only escape the '$' character, see
http://velocity.apache.org/engine/devel/user-guide.html#escapinginvalidvtlreferences
HTH,
-Lukas
On 09/23/2011 12:12 AM, Params wrote:
Thanks Robert, I tried couple of combinations and found this to work:
value#set($varline = '${wf:errorCode(wordcount)}') ${varline}/value
However, the display text I now get as html is:
value ${wf:errorCode(wordcount)}/value
Is there a way, I can get the wordcount inside single quotes?
Following three combinations don't work:
value#set($varline = '${wf:errorCode(\'wordcount\')}') ${varline}/value
value#set($varline = ${wf:errorCode('wordcount')}) ${varline}/value
value#set($varline = ${wf:errorCode(\'wordcount\')}) ${varline}/value
--
Thanks,
Params
--
View this message in context:
http://maven.40175.n5.nabble.com/APT-Issue-with-adding-xml-code-snippets-as-Verbatim-tp4831524p4831674.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Can DITA be used to create site documentation?
Not yet: http://jira.codehaus.org/browse/DOXIA-288 -Lukas On 09/22/2011 05:06 AM, Eric Kolotyluk wrote: I was wondering if it is possible to use DITA to generate the documentation for a site. We use DITA for other stuff and it integrates nicely with Eclipse, I was hoping someone might have gone down this route already. Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: doxia and docbook
as documented here: http://maven.apache.org/plugins/maven-site-plugin/faq.html#How_to_include_a_custom_Doxia_module_like_Twiki and the directory names and extensions: http://maven.apache.org/doxia/references/index.html -Lukas On 09/13/2011 11:22 PM, Benson Margulies wrote: No, the folder name is 'docbook' for the 'simple-docbook' format, which is no the same thing as xdoc. It turns out that you have to add a dependency to the site plugin. I've improved the doc. On Tue, Sep 13, 2011 at 4:21 PM, Karl Heinz Marbaisekhmarba...@gmx.de wrote: Hi, adding src/site/docbook and putting things in it seems to have no effect. Do I need to add a plugin? As far as i know you need to call the folder xdoc instead of docbook add the doxia docbook format there if we are talking about the maven-site-plugin... http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: hyperlinks out of description?
On 09/12/2011 10:25 PM, Mark H. Wood wrote: Is there any way to embed hyperlinks in the POM description element? If I put them in plain, the result is an invalid document; if I wrap them in CDATA then the markup comes through. Adding and using the XHTML namespace made no difference with the plain markup. The description seems like the right place to link to e.g. protocol specifications and other standards. Like: BaloneySoft FooPlex implementsaour profile/a ofaRFC 1149/a. The description in the pom xsd [1] states: A detailed description of the project, used by Maven whenever it needs to describe the project, such as on the web site. While this element can be specified as CDATA to enable the use of HTML tags within the description, it is discouraged to allow plain text representation. If you need to modify the index page of the generated web site, you are able to specify your own instead of adjusting this text. This text is ambiguous IMO, since the description element is specified to be of type string, ie no markup allowed, and markup inside CDATA is (correctly) not interpreted by the site plugin. So if you want hyperlinks in your index page, you should specify your own. Also bear in mind that the description might be used in contexts other than html. HTH, -Lukas [1] http://maven.apache.org/maven-v4_0_0.xsd - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Doxia APT - possible to reference Maven properties?
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering HTH, -Lukas sebb wrote: Is it possible to reference Maven properties in APT documents? or environment variables? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site plugin in maven 3.
Hi, See comments in-line... Michael Haefele wrote: The question on using site with aggregated projects got me to trying out the maven 3 version of the site plugin.. Thought I'd post a little list of the steps required and a report card. My use case is I want to generate a site in some directory in a nightly CI build for an aggregated project. I don't really care what the site looks like beyond maybe adding any reporting plugins that sound interesting. I certainly don't want to deploy it anywhere as it's already web accessible as an artifact of the nightly build (this has the added benefit of being able to compare Tuesday's site with Wednesday's site). Basically i want to run the plugin and use whatever the default output is In Maven 2, this use case didn't fare very well (specifically this use case. If this is an outlandish use case, that's fine). Basically I jumped through 4 or 5 flaming hoops and gave up (again, it's a nice to have, but not part of core business in any way, so the last 3 hoops were more out of stubbornness than a good use of my time). So hopefully Maven 3 would be a little more forgiving. Apart from some issues with reporting plugins [1] it shouldn't matter whether you run it with maven 2 or 3, it's rather a question of which version of the site-plugin you're using. Version 3 of the site plugin is compatible with maven 2 and 3. [1] http://maven.apache.org/plugins/maven-site-plugin/maven-3.html To get started, I followed the link sent in the other post. ( http://maven.apache.org/**plugins/maven-site-plugin/faq.** html#Why_dont_the_links_**between_parent_and_child_** modules_work_when_I_run_mvn_**sitehttp://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site ) I need to use site:stage, but this requires the site to be generated... So... mvn clean site:site mvn site:stage (mvn clean site:site site:stage does not work well I discovered) why not? Yields: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:stage (default-cli) on project pep-parent-dep-mgmt: Missing site information in the distribution management of the project pep-parent-dep-mgmt (com.pep:pep-parent-dep-mgmt:3.10-SNAPSHOT) - [Help 1] So I'll count this as Hoop #1. Why does maven need this information (as in, why can't maven leave this blank or put in a fix-me value)? site:stage is just a local preview of site:deploy for which this information is needed. In particular relative links between modules are constructed using this information. There were lots of problems with this in older versions of the plugin, see [2] and linked issues. So even though in your particular case the distMngmt.site info is not directly needed, it is necessary to ensure that that the staged site is exactly the same as the deployed site. [2] http://jira.codehaus.org/browse/MSITE-533 I tried adding distributionManagement site idwww.yourcompany.com/id urlscp://www.yourcompany.com/www/docs/project//url /site /distributionManagement , straight out of http://maven.apache.org/plugins/maven-site-plugin/usage.html#Deploying_a_Site (even though i'm not actually deploying). But this eventually causes some weird directory names in the site links (they include the scp://), so I took that out and just used url/ that doesn't sound right, do you have a test case? This one actually deployed everything except the grandparent module (we have a grandparent, a parent which has grandparent as parent, and an aggregating project, which does not have the parent or grandparent as a parent) to target/staging/../../../../ (which turned out to be just above my ~ directory). I don't know where all the ../../../ came from (maybe the relativePath in theparent tag?). I can only guess but I assume that you have a complicated project structure, maybe with non-default directory layout? Did you read [3], especially the 'Note' under 'Staging and deploying'? Otherwise please provide a simple test project. [3] http://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html I finally goldilocked on urlmysite/url Which doesn't really make any sense, but seems to do the least crazy to the staging directory structure.. I added this to the aggregating project and the grandparent project mvn clean site:site mvn site:stage This now works except the grandparent project doesn't seem to have it's own directory (clicking on the module link takes you to the staging directory).. But certainly good enough for my purposes.. In summary, I'd probably give the 3.0 site plugin a B- for this use case, which is a HUGE improvement over maven 2. My main issue is with configuring thesite tag, which seems like an unnecessary step if site:stage doesn't need it (especially since getting it wrong can do odd things to where the files are staged). It would be great if this defaulted to
Re: Site plugin in maven 3.
Michael Haefele wrote: Third time trying to send this... I keep getting spam blocked. Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 552 552 spam score (5.3) exceeded threshold (HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,URI_OBFU_WWW (state 18). The long and the short of it is I need to come up with a set of test projects to verify what I am seeing. If I'm reading this right, there are a few expected behaviors.. 1. mvn site:site site:stage should work. It should work up to http://maven.apache.org/plugins/maven-site-plugin/faq.html#What_is_the_difference_between_mvn_site_and_mvn_site:site 2. ThedistributionManagementsiteurl is important. Only in a multi-module build and/or if you want to stage/deploy your site. * It can be in the form of file://mysite/ or scp://mysite/ it should be a valid URL (and to make sense it should be an absolute URL, even though in practice a relative one will probably work too, as in the example you have shown in your previous email). * It will be inherited by child modules (as in hierarchy, not aggregator/directory children) and appended with that child artifactId. yes, unless you explicitly override it in the inheriting child. However, note http://jira.codehaus.org/browse/MSITE-600 which I still haven't managed to fix in a satisfactory manner. ** This will not work if the module directory does not match the artifactId. 3. Does theprojecturl tag matter? See http://maven.apache.org/plugins/maven-site-plugin/faq.html#Use_of_url http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_do_my_absolute_links_get_translated_into_relative_links What I would like to do is add site idanId/id urlscp://mysite//url /site to my corporate pom and have that be inherited down to the children, grandchildren, etc nodes.. So, for example, if I have a hierarchy corp-my-grandparent-my-parent-my-module and an aggregator root module corp-my-aggregator which aggregates my-grandparent, my-parent and my-module my-aggregator/ my-aggregator/my-grandparent my-aggregator/my-parent my-aggregator/my-module If only corp has a url defined, I would expect the my-module url to be scp://mysite/my-grandparent/my-parent/my-module/ ? yes And the following structure for my-aggregator/staging ? target/staging/corp/my-aggregator target/staging/corp/my-grandparent target/staging/corp/my-grandparent/my-parent target/staging/corp/my-grandparent/my-parent/my-grandparent yes And all the links properly navigate this structure. hopefully ;) Cheers, -Lukas I've got a bit of vacation coming up, but after that I will try to come up with some simple test projects to confirm what I am seeing on our main project (or perhaps expose that I'm doing something non-maveny that i can fix). Thanks! Mike - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Links broken on multimodule site
try site:stage: http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site HTH, -Lukas iapazmino wrote: Hello, I've got a multimodule project built with maven 3 with the 3.0-beta-3 version for the maven-site-plugin. The parent and every module have an small site.xml descriptor with a few links and the reports included in the menu menu ref=reports/, nothing special. The problem is when trying to navigate from the Project Modules page in the parent to the modules. This links are broken. For instance the link for the project-api module points to parent/target/site/project-api/index.html but the actual location is parent/api/target/site/index.html So, there are two problems with this URL, first the module's site is generated in its own target directory, not in the parent's target directory as expected. Second, the actual folder for the module is api, as it's declared in the parent's pom, but the module's artifactId is project-api. I read the site:site plugin's goal documentation but can't find anything useful on this case. Where should I tune this site generation? Thanks in advance, IP -- View this message in context: http://maven.40175.n5.nabble.com/Links-broken-on-multimodule-site-tp4779168p4779168.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clirr.skip does not seem to work for mvn site
did you use pluginManagement? http://maven.apache.org/pom.html#Plugin_Management HTH, -Lukas sebb wrote: If a parent POM includes Clirr in the reports section, is it possible to suppress/exclude the report in a child Pom? It seems to be possible to override the level and comparison version in the child Pom, but when I tried addingskiptrue/skip that seems to be ignored by the site plugin. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site plugin and deploy layout
On 08/30/2011 11:18 AM, mickael leduque wrote:
Hi,
I'm trying to use the site plugin and to deploy with a very simple directory
layout.
The deploy location should be something like
scp://${site-deploy.base.location}/{project.groupId}/${project.artifactId}/${project.version}/
Nothing really unconventional, eh ?
But after trying, reading everywhere, (there seems to be a heap of
distributionManagement url issues...) I could'nt find a way to do it.
When there is a project hierarchy, there just doesn't seem to be a way that
works, as children won't just inherit the property.
Just inheriting would be the reasonable way to do it ? It seems the child
will persist adding some random and unwanted bit to the url.
(yes I know those are not totally random, but for me it's really the same as
it's not documented anywhere)
http://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html
See the 'Note' under 'Staging and deploying'.
HTH,
-Lukas
For example, with
ProjectA
|_ Project B
|_ Project C
if I define
distributionManagement.site.url=scp://${site-deploy.base.location}/{project.groupId}/${project.artifactId}/${project.version}/
in ProjectA, ProjectC will site-deploy to
${site-deploy.base.location}/{project.groupId}/${project.artifactId}/${project.version}/projectC/projectD
Totally useless.
Is there any way to achieve what I want without putting a site.url in each
and every project pom ? Without that, inheritance is completely useless.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: site plugin and deploy layout
On 08/30/2011 11:35 AM, mickael leduque wrote: 2011/8/30 Lukas Theusslltheu...@apache.org http://maven.apache.org/**plugins/maven-site-plugin/** examples/multimodule.htmlhttp://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html See the 'Note' under 'Staging and deploying'. HTH, -Lukas Hm, I have seen that note, but I don't find it really helpful because it just convinces me that inheritance is inconsistent in this case, thus there is some bug. I'm more searching some workaround, like some way to tell maven that I don't want this kind of inheritance here. You can stop searching, the only workaround is to override the url in each child module. Note that this is not a site-plugin issue, the default inheritance mechanism is done by maven-core. -Lukas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: NPE with maven-site-plugin:3.0
Please open an issue at http://jira.codehaus.org/browse/MSITE with a reproducible test case. Thanks, -Lukas On 08/22/2011 02:18 PM, Thomas Scheffler wrote: Hi, after updating to version 3.0 of maven-site-plugin I get a NullPointerException that does not occur with 3.0-beta3. How can I figure out, what causes that? There is not clear error message so I guess it's a bug... Here is the last part of the log: [DEBUG] Multipage report: 0 subreports [DEBUG] Velocimacro : added #link( href name target img position alt border width height ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #image( img alt border width height ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #banner( banner id ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #links( links ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #breadcrumbs( breadcrumbs ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #displayTree( display item ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #menuItem( item ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #mainMenu( menus ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #copyright( ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #publishDate( position publishDate version ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #poweredByLogo( poweredBy ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #googleAnalytics( accountId ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [ERROR] Method calculateLink threw exception for reference $PathTool in template org/apache/maven/doxia/siterenderer/resources/default-site.vm at [2,29] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 14.407s [INFO] Finished at: Mon Aug 22 14:16:21 CEST 2011 [INFO] Final Memory: 96M/874M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project mycore-iview2: 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,39] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project mycore-iview2: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: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: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:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at
Re: site 3.0 breaks site deployment
This is probably related to http://jira.codehaus.org/browse/MSITE-600. Can you provide a simple test project? I am currently looking into it. -Lukas Randy Sr wrote: I moved from 3.0-beta3 to 3.0 of the maven site plugin and now my site deployment is broken. I have a root project with a site and a multi-module project that has the root project as a parent but with a completely separate site. With the 3.0 maven site plugin, it makes the multi-module project site relative to the root project site, by using the root project site URL and appending ../project-version to it, but that breaks down the line, and is not what I want. Both pom files have the distributionManagement/site element to direct it to specific URLs for upload. I have reverted to 3.0-beta3 and now it works again. Is there a way to prevent the 3.0 plugin from having this new behavior? Or is there another way to accomplish what I want: two separate sites for the root project and the multi-module project. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deploying site.xml
Using Maven 3? See http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Site_descriptor_attachment HTH, -Lukas On 08/19/2011 12:21 PM, Lóránt Pintér wrote: Hi, I just noticed that when I do mvn site on my project, that Maven tries to download the site.xml for its parent project: [INFO] Parent project loaded from repository: com.topdesk:tis-parent:pom:3.2-SNAPSHOT Downloading: http://nexus-proxy.tis.local/nexus/content/groups/public/com/topdesk/tis-parent/3.2-SNAPSHOT/tis-parent-3.2-SNAPSHOT-site_en.xml Downloading: http://nexus-proxy.tis.local/nexus/content/groups/public/com/topdesk/tis-parent/3.2-SNAPSHOT/tis-parent-3.2-SNAPSHOT-site.xml The parent project *does* have a site.xml, but it doesn't get deployed when I do mvn deploy. Is there a way I can get it to be deployed? Thanks, Lorant - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multi-Module and differing artifactId
Hi,
I am not aware of any other solution, but I remember the following
comment by Benjamin, quoted from http://jira.codehaus.org/browse/MNG-5000:
The cause of the issue was that module-2 has a different artifactId
than its module name. Let me stress that such a layout is a recipe for
trouble as it results in effective URLs that depend on the source of the
POM (project vs repo), i.e. if somebody (e.g. a plugin) was to construct
the POM of this project from the repository, it would see different URLs
than those used when building the project. The same problem would also
arise during local project building when URLs are inherited from a
grand-parent via one or more intermediate parents and any of those
parents is resolved from the repo. For this reason, it's highly
recommended to synchronize the module name with the artifactId.
HTH,
-Lukas
Stefan Seidel wrote:
Hi,
I guess this has been asked before, but is there any way to gracefully
handle situations in a multi-level modular project where the artifactId
does not always correspond to the folder name of the module?
It's especially about the scm url and connection.
So my folder structure is like this:
+/ = org.test:parent
++/childA = org.test.parent:childA
++/childB = org.test.parent:childWithOtherName
Now the scm url for childWithOtherName will always be the one from the
parent with /childWithOtherName appended, and there is no way I can
force it to use /childB, unless I specify the whole path, which is
tedious with large projects.
I even tried to use ${project.parent.scm.connection}, which evaluates
fine with help:evaluate, but will not expand when used in the scm
connection.
Any help?
Stefan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use default layout repository with maven 1
Manfred Moser wrote: On Mon, August 15, 2011 12:13 pm, amaresh mourya wrote: Hi All, Can I use default layout repository with Maven 1? By specifying following in my POM? repository idmaven2-repository/id nameRepository for Maven/name urlhttp://abc.net/maven/2//url layoutdefault/layout /repository Please.. do NOT use Maven 1 anymore. Upgrade to Maven 3 or at least the latest version of Maven 2... ... and the answer to the question is 'no': http://jira.codehaus.org/browse/MAVEN-1694 -Lukas manfred - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Resources filtering failed if file contains @ on Linux/Mac
maybe this: http://jira.codehaus.org/browse/MRESOURCES-104 ?
-Lukas
On 07/19/2011 12:01 PM, Li Yanhui wrote:
Hi,
I'm using maven-resources-plugin:2.4.3 on my Mac.
I found it can't replace placeholder in properties file if it contains the '@'
character.
For example, I have a env.properties under src\main\resources which has the
following content:
jdbc.url=jdbc:oracle:thin:@192.168.1.212:1521:demodb
solr.home=${solr.home}
I have the following configuration in pom.xml:
build
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
/resources
...
/build
Then I run the following command:
mvn clean resources:resources -Dsolr.home=/tmp/solr
And check file content using:
cat target/classes/env.properties
It remains the original content.
If I removed the '@' character in properties file, it just works.
Any ideas?
PS. I also tested this case on Windows and Linux, it passed on Windows but
failed on Linux.
Regards,
Li Yanhui
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven fails while running mvn site
The site plugin needs to be configured in the build section of the pom,
not in reporting.
HTH,
-Lukas
On 07/15/2011 11:56 AM, nataraj.krishnamur...@cognizant.com wrote:
Hi
I am trying to run mvn site and I get the following error
Details : I am using Maven 2.2.1 and use JDK 1.6. I have pasted the
POM.xml below
?xml version=1.0 encoding=UTF-8?
project xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdRS/groupId
artifactIdAAL/artifactId
version12/version
nameATTRIEVAL Service/name
description retrieval service/description
inceptionYear2010/inceptionYear
organization
nameer/name
url../../galileo/url
/organization
developers
developer
idheckr/id
nameJohn/name
emailj...@gmail.com/email
url../../galileo/url
organizationier/organization
roles
roleGalileo
Manager/role
/roles
timezone+0/timezone
/developer
/developers
issueManagement
systemWEBSTAR/system
urlhttp://webstar/default.asp?logId=/url
/issueManagement
build/
reporting
plugins
plugin
artifactIdmaven-changes-plugin/artifactId
configuration
issueLinkTemplate%URL%/default.asp?logId=%ISSUE%/issueLinkTemplate
xmlPath${basedir}/src/site/xdoc/changes.xml/xmlPath
/configuration
reportSets
reportSet
reports
reportjira-report/report
/reports
/reportSet
reportSet
reports
reportchanges-report/report
/reports
/reportSet
/reportSets
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.3/version
configuration
outputDirectory${basedir}/../BinaryRetrievalResource/WebContent/xdocs
/outputDirectory
/configuration
/plugin
/plugins
/reporting
/project
INFO] Scanning for projects...
[INFO]
[INFO] Building ATTACHMENT RETRIEVAL Service
[INFO]task-segment: [site]
[INFO]
[WARNING] DEPRECATED [issueLinkTemplate]: As of 2.1 use
issueLinkTemplatePerSystem : this one will be with system default
[INFO] [site:site {execution: default-site}]
[ERROR] The JIRA Report only supports JIRA. No JIRA Report will be
generated.
[WARNING] No URL defined for the project - decoration links will not be
resolved
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for
updates from central
[INFO] Skipped About report, file index.html already exists for the
English version.
[INFO] Generating Issue Tracking report.
[INFO] Generating Project Team report.
[INFO] Generating Dependencies report.
[INFO] Generating Project Plugins report.
[INFO] Generating Continuous Integration report.
[INFO] Generating Source Repository report.
[INFO] Generating Plugin Management report.
[INFO] Generating Mailing Lists report.
[INFO] Generating Project Summary report.
[INFO] Generating Changes Report report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a
linkage error (java.lang.AbstractMethodError) and may be out-of-date.
Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.0-beta
-7]
urls[0] = file:/D:/Documents and
Re: Site deploy problem
site-plugin-2.3 has some problems with property resolution, see eg
http://jira.codehaus.org/browse/MSITE-585. I'm not sure if this is the
same issue as yours, could you try with 2.4-SNAPSHOT?
HTH,
-Lukas
Johan Vogelzang wrote:
Oh I forgot...
I use Maven 2.2.1 and maven-site-plugin version 2.3.
The behavior is the same on Windows and Linux.
Johan.
2011/7/13 Johan Vogelzangjohan.vogelz...@gmail.com
Hi Maven users,
I've a problem with deploying a site to an url containing property
variables.
The site url -as part of the distributionManagement section- is located in
the company parent pom:
properties
reposerver.host.namemyrepohost/reposerver.host.name
/properties
...
distributionManagement
site
idsite-repo/id
urlscp://${reposerver.host.name}/var/www/html/maven2/sites/url
/site
/distributionManagement
When I execute mvn help:effective-pom I see that the url is correctly
resolved to: scp://myrepohost/var/www/html/maven2/sites
But when I execute mvn site-deploy the build fails with an
UnknownHostException. In the logging I see that the url is not resolved:
[INFO] [site:deploy {execution: default-deploy}]
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Connection refused
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnecting
scp://${reposerver.host.name}/var/www/html/maven2/sites - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Cannot connect. Reason: java.net.UnknownHostException: ${
reposerver.host.name}
Thanks in advance,
--
Johan Vogelzang
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven-Doxia-Plugin: Generating LaTeX Code from APT
Yes, sorry. The maven-doxia-plugin (and underlying book code) is really just alpha quality IMO... -Lukas Karl Heinz Marbaise wrote: Hi Lukas, The latex sink has a protected constructor that takes a 'String preamble' parameter, the default is [1], so you should be able to adjust that. First thanks for this answer but that means there is no chance to change that via the maven-doxia-plugin Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven-Doxia-Plugin: Generating LaTeX Code from APT
Karl Heinz Marbaise wrote: Hi Lukas, Yes, sorry. No need to apologize for that... That's my good education... ;) The maven-doxia-plugin (and underlying book code) is really just alpha quality IMO... That means it can be done some work on it... We were thinking at one point to deprecate the whole book/maven-plugin components, but it seems that it is actually used by some people... so if you want to take a look, there's certainly room for improvement. I was impressed of the quality of the resulting LaTeX code and the resulting PDF, cause it looks much better than the PDF which is created via iText (I assume)...except for the flexibility... Did you also try the maven-pdf-plugin? I think it's much better than the book code (yeah, I wrote it...) So my idea was to go in direction with LaTeX and using the latex-maven-plugin, which unfortunately has bug...but this is a different story... So my first idea is to think about enhancing the doxia-maven-plugin and increase the configuration flexibility of it...Or should it be done in a different way... May be you can give me a hint where to look for improvements on that subject... You could have a look at the doxia-converter instead: http://maven.apache.org/doxia/doxia-tools/doxia-converter/index.html It might be worth to consider re-writing the doxia-maven-plugin to use that instead of book. HTH, -Lukas Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven-Doxia-Plugin: Generating LaTeX Code from APT
The latex sink has a protected constructor that takes a 'String preamble' parameter, the default is [1], so you should be able to adjust that. HTH, -Lukas [1] https://svn.apache.org/repos/asf/maven/doxia/doxia/trunk/doxia-modules/doxia-module-latex/src/main/resources/org/apache/maven/doxia/module/latex/default_preamble.tex Karl Heinz Marbaise wrote: Hi, currently i'm trying to generate LaTeX code from the apt documentation...the result is working, but currently i have a problem that there exists no possibility to change for example the configuration of generated LaTeX file. For example i would like to change the encoding which is currently defined to latin1 or may be putting something different into the document preamble...for example different handling instead of fancyhdr etc. or may be the most important to change the page style etc. Does someone know if this is possible? Somehow? Cause i couldn't find any docs about that?... Many thanks in advance. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn compile works mvn site-deploy causes complation error
Leandro wrote: Thanks Wayne. I've just solved it adding one dependency to the project. Why that problem only appears with mvn site and not with mvn deploy? It's the javadoc report that bombs because of missing annotation deps, and javadoc only runs with site. Also sometimes if I run mvn install site:stage (with install before) I don't get errors, otherwise I do. Why is this happening? See http://jira.codehaus.org/browse/MSITE-171 HTH, -Lukas Thanks again! From: Wayne Fay [via Maven] [ml-node+4346618-1269415335-202...@n5.nabble.com] Sent: 28 April 2011 15:27 To: Leandro Iriarte Subject: Re: mvn compile works mvn site-deploy causes complation error In this URL you can see the complete output running mvn site -X in the module which error: http://pastebin.com/8yV8WBQh Is the same error I get when I run mvn site:stage in the root project It is really not hard to scan a debug log and find problems. Look near the bottom of your log for lines that say [ERROR]. It appears you have some annotation issues in PollMessages and CreateProcessListener. Wayne - To unsubscribe, e-mail: [hidden email]/user/SendEmail.jtp?type=nodenode=4346618i=0by-user=t For additional commands, e-mail: [hidden email]/user/SendEmail.jtp?type=nodenode=4346618i=1by-user=t If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/mvn-compile-works-mvn-site-deploy-causes-complation-error-tp4343797p4346618.html To unsubscribe from mvn compile works mvn site-deploy causes complation error, click herehttp://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4343797code=bGVhbmRyby5pcmlhcnRlQGZ1c2VpbS5jb218NDM0Mzc5N3wtMTQ1MTMwNzY1. -- View this message in context: http://maven.40175.n5.nabble.com/mvn-compile-works-mvn-site-deploy-causes-complation-error-tp4343797p4346660.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: PDF Plugin
It works here. You are probably using an incompatible plugin, eg try
disabling the reports. If you can't get it to work, attach a small test
project at http://jira.codehaus.org/browse/MPDF
HTH,
-Lukas
Stephen Cresswell wrote:
Has anyone got the PDF plugin working with Maven 2.2.1?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.2/version
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pdf-plugin/artifactId
version1.1/version
executions
execution
idpdf/id
phasesite/phase
goals
goalpdf/goal
/goals
configuration
outputDirectory
${project.reporting.outputDirectory}/outputDirectory
/configuration
/execution
/executions
/plugin
Results in
Caused by: java.lang.NoSuchMethodException:
org.apache.maven.doxia.sink.Sink.toString()
at java.lang.Class.getMethod(Class.java:1605)
at
org.apache.maven.plugins.pdf.PdfMojo$SinkDelegate.invoke(PdfMojo.java:1935)
Cheers,
S
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-3.0.2 + maven-site-plugin-3.0-beta-3 + multi module projects (can't resolve module dependencies)
I'm not sure I follow you, why do you say a workaround is to go back to maven 2? MSITE-171 was opened against site-plugin-2.0-beta-5, as I said, it's an old issue that's been there forever AFAIK. -Lukas Andrew Hughes wrote: Update, I tried to back this out to maven2 and a collection of old plugins, but I still can't get it working. Everything I try fails for this reason or something else telling me to update my plugins. I even totally re-created new project/modules in an effort to fix this. I'm totally stumped with this and starting to wonder if I am on a wild goose chase :'( On Thu, Apr 14, 2011 at 9:14 AM, Andrew Hughesahhug...@gmail.com wrote: Lukas, Thanks for the answer. Unless I can fix this myself I had better shut up about it. I guess the workaround here is to stay on maven 2 for the time being (note that the pomreporting sections are different in m2 and m3 pom.xml's ). Thanks for the info. Steve, That's a really good point and a big gotcha for anyone trying to release their project. Seems like m2 might be the only proper workaround to this (if you really do want sites). In addition to this... a little off topic but quite relevant to what you have said. I'm a big fan of sites, but I believe site-deploy shouldn't be a goal that is run during a release. This is because the site can be re-built and deployed anytime you want (post release). It's convenient to have these run together, but let's say a password has expired or the site's url host is turned off, or network problems - I think it adds unnecessary risk to a release. Consequently we turned this off... plugin groupId org.apache.maven.plugins /groupId artifactId maven-release-plugin /artifactId configuration !-- removed site-deploy from the release goals, a failed site-deploy should not hold up a release, it can be manually deployed from ./target/checkout after the release:perform has finished or manually deployed later from the scm tag -- goals deploy /goals /configuration /plugin I have a different opinion on this. I am a big fan of maven site's however I don't believe that if something fails during On Wed, Apr 13, 2011 at 5:09 PM, Stevo Slavićssla...@gmail.com wrote: I'm also affected by this issue, when releasing project using maven-release-plugin, prepare goes well, perform fails as it detects site in distributionManagement and default goals run are deploy site-deploy so maven tries to generate and deploy site, but since site plugin tries to resolve something that's not installed/deployed yet, release:perform fails. One workaround could be to configure prepare mojo's http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#preparationGoals to be clean install instead of default clean verify, install is after verify, if verification fails install will not be performed, if verification is successful install will be performed and artifacts will be available in local repository, so as long as release:perform is run on same node/machine by same user as release:prepare, site should be generated and deployed; deploy will install/overwrite artifacts again in local repo and deploy them to remote repo. Regards, Stevo. On Wed, Apr 13, 2011 at 9:17 AM, Lukas Theusslltheu...@apache.org wrote: That's an old issue, see http://jira.codehaus.org/browse/MSITE-171 and related tickets. -Lukas Andrew Hughes wrote: Hi All, Before each of the following test, I delete my project/module artifacts from my local repo The following works :) *mvn clean install * *mvn site* The following fails :( *mvn clean install site* The following also fails :( *mvn clean install site:site* The error I consistently get is: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on project acme-project: failed to get Reports: Failed to execute goal on project acme-project-d: Could not resolve dependencies for project com.acme.project:acme-project-module-d:ejb:5.1.0-SNAPSHOT: *Could not find artifact com.acme.project:acme-project-module-a:jar:5.1.0-SNAPSHOT* in archiva (http://acme.com/repository/all/) - [Help 1] ...site appears to be running on the incorrect phase or build lifecycle. Consequently, the (module) dependencies have not been install/deployed to my local repository yet. Any idea's how I can fix this??? Cheers. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands,
Re: maven-3.0.2 + maven-site-plugin-3.0-beta-3 + multi module projects (can't resolve module dependencies)
That's an old issue, see http://jira.codehaus.org/browse/MSITE-171 and related tickets. -Lukas Andrew Hughes wrote: Hi All, Before each of the following test, I delete my project/module artifacts from my local repo The following works :) *mvn clean install * *mvn site* The following fails :( *mvn clean install site* The following also fails :( *mvn clean install site:site* The error I consistently get is: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on project acme-project: failed to get Reports: Failed to execute goal on project acme-project-d: Could not resolve dependencies for project com.acme.project:acme-project-module-d:ejb:5.1.0-SNAPSHOT: *Could not find artifact com.acme.project:acme-project-module-a:jar:5.1.0-SNAPSHOT* in archiva (http://acme.com/repository/all/) - [Help 1] ...site appears to be running on the incorrect phase or build lifecycle. Consequently, the (module) dependencies have not been install/deployed to my local repository yet. Any idea's how I can fix this??? Cheers. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site breadcrumbs: trouble with inheritance
Which version of the site plugin are you using? Please try latest snapshots (2.3- or 3.0-beta-4-) and report back. Thanks, -Lukas Andreas Sewe wrote: Hi all, I have the following two projects: A dedicated website project for my root URL org.example:site (with urlhttp://example.org//url) and an organizational POM org.example:parent (with urlhttp://example.org/parent/url) The parent of org.example:site is the organizational POM, org.example:parent. Both projects have their own site.xml. So far, I think, that's all according to Best Practices. The trouble starts once I configure breadcrumbs. What I want to generate are the following two breadcrumb trails: Example.org Site and Example.org Site Example.org Parent for org.example:site and org.example:parent, respectively. Note that these two trails do not mirror the project's inheritance tree, but rather the users' expectations (org.example:site is the main website artifact, after all). But no matter what breadcrumbs I define in the site.xml of both projects, I cannot get the desired effect. In particular, the following doesn't work: !--org.example:parent's site.xml -- breadcrumbs item name=Example.org Site href=http://example.org// item name=Example.org Parent href=http://example.org/parent// /breadcrumbs !--org.example:site's site.xml -- breadcrumbs item name=Example.org Site href=http://example.org// /breadcrumbs While the breadcrumbs of org.example:parent are correct, the trail of org.example:site is simply too long: Example.org Site Example.org Parent It's almost as if not merging occurred at all. But it gets worse: If I change the site.xml of org.example:site just slightly, the breadcrumb trail of org.example:site grows even longer: breadcrumbs item name=Example.org *Main* Site href=http://example.org// /breadcrumbs yields Example.org Site Example.org Parent Example.org *Main* Site Can someone please explain to me what's going on here? To me, the inheritance behavior of breadcrumbs looks rather random. Best wishes, Andreas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site breadcrumbs: trouble with inheritance
Andreas Sewe wrote: Hi all, I have the following two projects: A dedicated website project for my root URL org.example:site (with urlhttp://example.org//url) and an organizational POM org.example:parent (with urlhttp://example.org/parent/url) The parent of org.example:site is the organizational POM, org.example:parent. Both projects have their own site.xml. So far, I think, that's all according to Best Practices. The trouble starts once I configure breadcrumbs. What I want to generate are the following two breadcrumb trails: Example.org Site and Example.org Site Example.org Parent for org.example:site and org.example:parent, respectively. Note that these two trails do not mirror the project's inheritance tree, but rather the users' expectations (org.example:site is the main website artifact, after all). But no matter what breadcrumbs I define in the site.xml of both projects, I cannot get the desired effect. In particular, the following doesn't work: !--org.example:parent's site.xml -- breadcrumbs item name=Example.org Site href=http://example.org// item name=Example.org Parent href=http://example.org/parent// /breadcrumbs !--org.example:site's site.xml -- breadcrumbs item name=Example.org Site href=http://example.org// /breadcrumbs While the breadcrumbs of org.example:parent are correct, the trail of org.example:site is simply too long: Example.org Site Example.org Parent It's almost as if not merging occurred at all. But it gets worse: If I change the site.xml of org.example:site just slightly, the breadcrumb trail of org.example:site grows even longer: breadcrumbs item name=Example.org *Main* Site href=http://example.org// /breadcrumbs yields Example.org Site Example.org Parent Example.org *Main* Site Two things: 1) breadcrumbs always get appended, you cannot override or remove a breadcrumb that has been added in a parent 2) identical breadcrumbs are ignored In your first case above, you are trying to add the same breadcrumb (same name, same href) again that is already defined in the parent, so according to 2) it is ignored and you only get the parent breadcrumbs. In your second case the child breadcrumb is appended according to 1) so you get 3 (2 parent + 1 child) breadcrumbs. This is the currently expected behavior. The fact that one cannot override or remove breadcrumbs is annoying, you might want to file a feature request for it. HTH, -Lukas Can someone please explain to me what's going on here? To me, the inheritance behavior of breadcrumbs looks rather random. Best wishes, Andreas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Can't get mvn site to generating site/reports
first thing: *always* pin down the versions of the plugins you want to use. Your log says you're running site-plugin-2.0.1, but it looks like your using maven 3, in which case you have to use the m3 version of the plugin [1]. And as your log states explicitly: there is no version number for the cobertura plugin. If that doesn#t fix it, open a jira with a reproducible test case. HTH, -Lukas [1] http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html emerson wrote: Hi, I'm trying to get cobertura working on my project, and it isn't generating any pages or reports for the site. Below is the log and further below the pom.xml. I just want to get maven to generate the tests, cobertura, checkstyle, pmd and findbugs reports to be shown in my CI server (jenkins) Another question: what is the best practice for this, is it running site, or is using a different profile with the instrumentation and report configuration? Just for the record, this is an simple stand-alone app generated using mvn archetype (with just one class and one test). C:\fabricasw\new_workspace\testcoberturamvn site [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for testcobertura:testcobertura:ja r:0.0.1-SNAPSHOT [WARNING] 'reporting.plugins.plugin.version' for org.codehaus.mojo:cobertura-maven-plugin is missing. @ line 78, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] [INFO] Building testcobertura 0.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- cobertura-maven-plugin:2.4:clean (site) @ testcobertura --- [INFO] [INFO] --- maven-site-plugin:2.0.1:site (default-site) @ testcobertura --- [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 2.188s [INFO] Finished at: Mon Apr 11 14:21:13 BRT 2011 [INFO] Final Memory: 5M/10M [INFO] pom.xml project xmlns=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; modelVersion4.0.0/modelVersion groupIdgtestcobertura/groupId artifactIdtestcobertura/artifactId version0.0.1-SNAPSHOT/version packagingjar/packaging nametestcobertura/name urlhttp://maven.apache.org/url properties project.build.sourceEncodingUTF-8/project.build.sourceEncoding /properties build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.4/version configuration instrumentation / /configuration executions execution idsite/id phasepre-site/phase goals goalclean/goal /goals /execution execution idinstrument/id phasepackage/phase goals goalinstrument/goal goalcobertura/goal /goals /execution /executions /plugin /plugins /build dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId
site deploy wagon scp error: unexpected filename
Hi there, I am testing the site deploy with the current snapshot of the site-plugin, and while deploying to apache works without problems, I'm getting the following error when deploying to a sourceforge project: scp://shell.sf.net/home/project-web/jaxodraw/htdocs/staging - Session: Opened [INFO] Pushing /Users/ltheussl/devel/JaxoDraw/trunk/jaxodraw/target/site Executing command: mkdir -p /home/project-web/jaxodraw/htdocs/staging/ Executing command: mkdir -p /home/project-web/jaxodraw/htdocs/staging/ Executing command: scp -t /home/project-web/jaxodraw/htdocs/staging/wagon4907440633151551251.zip Transfer error: java.io.IOException: SCP terminated with error: 'scp: error: unexpected filename: /wagon4907440633151551251.zip' Transfer error: org.apache.maven.wagon.TransferFailedException: Error occurred while deploying '/wagon4907440633151551251.zip' to remote repository: scp://shell.sf.net/home/project-web/jaxodraw/htdocs/staging: SCP terminated with error: 'scp: error: unexpected filename: /wagon4907440633151551251.zip' The problem seems to be the slash in the beginning of the filename but I haven't been able to workaround it, if anybody has a hint... Thanks, -Lukas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Reopen MPIR-180 (Repositories which require authentication get blacklisted)?
Please do not re-open issues that are marked as fixed in released versions, create a new issue and link back to the original one. Thanks, -Lukas Thierry Carre wrote: Hi all, My internal repository requires an authentication. When I build the Dependencies report with : mvn org.apache.maven.plugins:maven-project-info-reports-plugin:2.3:dependencies -- No problem, it works fine. but with : mvn org.apache.maven.plugins:maven-project-info-reports-plugin:2.3.1:dependencies -- my repository is blacklisted again, as with the older plugin versions ( 2.2) http://jira.codehaus.org/browse/MPIR-180 Am I alone in this case? (I'm using maven 3.0.2) Thanks Thierry -- View this message in context: http://maven.40175.n5.nabble.com/Reopen-MPIR-180-Repositories-which-require-authentication-get-blacklisted-tp4229472p4229472.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Missing links in site generation of multi-module project
Hi Craig, Unfortunately this depends on a couple of other releases that have to be done first (doxia, doxia-site-tools, shared-doxia-tools), so I'm afraid it's not going to happen tomorrow,... but we're working on it. Cheers, -Lukas Harpel, Craig wrote: Lukas, thanks for helping me out with this last month. Any chance 2.3 will be released soon (or a beta)? Thanks, Craig -Original Message- From: Harpel, Craig [mailto:char...@mitre.org] Sent: Wednesday, February 16, 2011 11:17 AM To: Maven Users List Subject: RE: Missing links in site generation of multi-module project Got it! Yes, I can confirm that 2.3-SNAPSHOT does indeed fix my problem. Thanks a lot!! Craig -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 11:01 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project http://maven.apache.org/guides/development/guide-testing-development-plugins.html HTH, -Lukas PS sorry, dense too :) Harpel, Craig wrote: Sorry for being dense, but I don't see a 2.3-SNAPSHOT; where can I grab it from? -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 7:49 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: changes:jira-report - No report for missing PID
You shouldn't need the pid (where is it written that you do?), eg for the doxia jira report [1] we just have urlhttp://jira.codehaus.org/browse/DOXIA/url in the pom [2]. It's probably a different problem, check your logs. HTH, -Lukas [1] http://maven.apache.org/doxia/jira-report.html [2] https://svn.apache.org/repos/asf/maven/doxia/site/pom.xml Stevo Slavić wrote: When browsing your JIRA project just hower over or copy URL of almost any link, and there you will find project's pid. Although maven needs pid (JIRA APIs require it) and not shorthand human-readable code, when configuring issueManagement/url I typically leave both pid and shorthand code in URL like in issueManagement systemJIRA/system urlhttp://jira.codehaus.org/browse/MCHANGES?pid=11212/url /issueManagement So it's somewhat human-readable for developers and maven (plugins) can use it. Regards, Stevo On Tue, Mar 8, 2011 at 1:56 PM, mehtakkomal.me...@hcl.com wrote: Hi, I am trying to generate a jira-report for my project. I do not know the 5 digit PID of my project. Thus I am getting an empty report as my site output. But I have specified a 5 chars valid project name ID, which works perfect on the jira..com Here is my POM. As a maven output I always get a BUILD SUCCESSFUL. But the jira-report.html file has following error message: An error occured that made it impossible to generate this report. Please check the console for information on what might be the cause of this. POM.xml ... maven-project-info-reports-plugin 2.3.1 summary org.apache.maven.plugins maven-changes-plugin 2.3 Fix Version,Type,Key,Summary,Resolution Closed Fix Version DESC, Type 1000 jira-report ... JIRA http://jira.company.com/browse/ABCDE xyz http://jira.company.com/browse/ABCDE Please help. Also what is the connection between a Project name ABCDE and the PID. Is PID a must param to fetch the jira report? thanks, Komal -- View this message in context: http://maven.40175.n5.nabble.com/changes-jira-report-No-report-for-missing-PID-tp3413891p3413891.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Build Site for parent module, but skip the children?
Related question: Is there a way of doing the exact opposite, ie exclude the parent site? I have a top level project that only serves as an aggregator and want to deploy the module sites *only*? -Lukas Brian Fox wrote: mvn -N site-deploy On Tue, Mar 1, 2011 at 4:50 PM, Brian Ferrisbdfer...@gmail.com wrote: I have a large multi-module project that I wish to build a site for using Maven's site functionality. The trick is that I'd like to avoid building the sub-module sites as well. Building the individuals sites for each sub-module takes a while (even with the dependency report disabled) and it's information that I don't need (the parent site is sufficient for my needs). I haven't found a good way of doing this. I specify my site plugin configuration in the parent pom. While my first inclination was to use inheritfalse/inherit on the plugin config, this just meant that each sub-module had the default site configuration as opposed to not building a site at all. The only other idea I've had is to run mvn -am -pl . site to just run the site goal through the parent module. The problem here is that it's not clear how I'd make this work inside my Hudson/Jenkins CI build process, which is already running mvn clean install. I still need to build and install all my submodules, even if I only deploy the site for the parent. Any ideas? Thanks, Brian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3 site: how to add report configured in module to parent's report config?
Jeff Jensen wrote: With Maven 3, how do I configure the site plugin to have a module's defined site reports added to the parent's defined site reports (and parent doesn't have the child report defined) instead of replacing the parent's report config? Is this expected to work/possible (I'm hoping I don't have to dupe the reports config into the child module)? In the parent pom'sbuild/pluginManagement element, I configured the site plugin with default reports configuration. This works great for having all modules run with the same reports. Now one module needs an additional report which shouldn't run for the other modules as it would just duplicate the effort. So I added the site plugin config with that one additional report configured to that module'sbuild/plugins element. However, for that module, now the other reports, defined in the parent, don't run; only the one report configured in its pom runs. I would guess that this is the expected behavior, as otherwise it would not be possible to remove reports defined in the parent. You will have to add all the reports again if you want them to run in this module. Cheers, -Lukas I didn't find docs/info on this problem and my experiments didn't change anything. Anyone have advice on how to solve this problem? I realize one workaround is to create a separate project/pom and have a different CI job run that one report, and I may have to, but it seems this Should Work (TM) and I don't know how yet! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site-deploy always appends ${project.artifactId} in the deploy URL
This is expected and documented [1]: 'If subprojects inherit the site
URL from a parent POM, they will automatically append their artifactId
to form their effective deployment location'. If you want to overide
that, you need to declare a site.url in the sub-project.
HTH,
-Lukas
[1] http://maven.apache.org/plugins/maven-site-plugin/usage.html
Simone Tripodi wrote:
Hi all guys,
I'm facing a wired issue, I don't understand if it concerns the
maven-site-plugin or the deploy plugin, btw every time I try to deploy
the site, the ${project.artifactId} is always appended to the
distributionManagement.site.url
i.e. if the url is
ftp://ftp.acme.org/projects/${project.artifactId}/${project.version}
the resulting url will be
ftp://ftp.acme.org/projects/${project.artifactId}/${project.version}/${project.artifactId}
Any hint/suggestion? My parent pom is public and can be found on
github[1], many thanks in advance!
Simo
[1] https://github.com/99soft/infra
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Missing links in site generation of multi-module project
I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Missing links in site generation of multi-module project
http://maven.apache.org/guides/development/guide-testing-development-plugins.html HTH, -Lukas PS sorry, dense too :) Harpel, Craig wrote: Sorry for being dense, but I don't see a 2.3-SNAPSHOT; where can I grab it from? -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 7:49 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site plugin - broken links between modules only on site stage
Marcin Kuthan wrote:
Hi Lukas
Sorry for inconvenience with my example. I extracted self-contained
test project:
http://m4enterprise.googlecode.com/svn/trunk/test2/
The example is prepared to use m-site-p version 2.3-SNAPSHOT. You can
customize plugin version with com.acme.maven.corporate-pom.siteVersion
property.
I didn't specify staging location because for the default location
target/staging on aggregate project level the results are the same.
Please execute the following commands on the aggregate pom level (top level):
mvn clean
mvn site:site
mvn site:stage -DsiteUrl='scp://myhost/var/www'
Stage is generated into target/staging/myhost/var/www/ but links
to submodules point to
../../../../localhost/var/www/modular-war-parent/.
Instead localhost myhost should be used as I specified in the
command line property. localhost is defined as a default value in
the pom and should be overwritten.
Yes, this is MSITE-135. When building the modules, the siteUrl from the
parent is used.
If you remove the siteUrl from your properties, then you get correct
links when using a cl parameter, however, if you don't specify a cl
parameter, you'll get a ${siteUrl} literal in your path. If it's just
for staging, this is probably good enough. For live deploy you might
want to avoid properties, or you could force to fail the build if a
property is not set.
HTH,
-Lukas
For plugin version 2.2 siteUrl property is interpreted as I expected,
but the links are broken due to wrong directory depth:
mvn site:stage -DsiteUrl='scp://myhost/var/www'
-Dcom.acme.maven.corporate-pom.siteVersion='2.2'
And the link is ../../../../../myhost/var/www/
I hope that it would help.
Marcin
On 1 February 2011 10:04, Lukas Theusslltheu...@apache.org wrote:
Dear Marcin,
I am unable to build your project (missing dependencies, failed enforcer
rules), please provide a simple, self-contained test project if you want me
to check something for you.
However, from your description, this still sounds like MSITE-135 to me; in
4. the {very-long-name.siteUrl} property is interpolated with the parent
project value instead of the cl value.
But then, since you specify the staging location on the command line anyway,
I don't see why you don't use the stagingDirectory parameter directly,
instead of going via distributionManagement.siteUrl, see
http://maven.apache.org/plugins/maven-site-plugin/usage.html (Staging a
site).
HTH,
-Lukas
Marcin Kuthan wrote:
Hi Lukas
I don't think that my findings are related to MSITE-135. Only
2.3-SNAPSHOT is affected.
You should reproduce the issue in 10 mins:
1. Follow http://code.google.com/p/m4enterprise/wiki/GettingStarted
(only Checkout Source Code and Install Corporate POM sections)
2. Go to trunk/modular-war
3. Call:
mvn clean
mvn -Dcom.acme.maven.corporate-pom.siteVersion=2.3-SNAPSHOT
-Dcom.acme.maven.corporate-pom.enforcerRulesDisabled site:site
site:stage
4. Call:
mvn clean
mvn -Dcom.acme.maven.corporate-pom.siteVersion=2.3-SNAPSHOT
-Dcom.acme.maven.corporate-pom.enforcerRulesDisabled site:site
site:stage
-Dcom.acme.maven.corporate-pom.distributionManagement.siteUrl=scp://host/var/www
For 3) generated stage are fine, links in modular-war to submodules are
valid.
For 4) links are broken,
com.acme.maven.corporate-pom.distributionManagement.siteUrl property
is ignored
If you use
-Dcom.acme.maven.corporate-pom.distributionManagement.siteUrl=file:///home/
results are even worse. URLs are totally broken.
Marcin
On 31 January 2011 16:32, Lukas Theusslltheu...@apache.orgwrote:
This sounds like a manifestation of
http://jira.codehaus.org/browse/MSITE-135 but I'm not sure. If you can
attach a simple test project that would help, I haven't tried to fix this
yet.
-Lukas
Marcin Kuthan wrote:
Hi Lukas
I'm sorry that I didn't specify versions in the first post. I tested
my poms with version 2.2 (for Maven 2.2.1) and version 3.0-beta-3 (for
Maven 3.0.2). In both cases links are invalid.
I updated my build to 2.3-SNAPSHOT and plugin reported invalid
character inurl element. There was a mistake in property name, and
literal value ${prop} was used instead of interpreted value. The new
plugin versions helped me to find out this bug - great!
I checked again version 2.2, even with fixed property name links in
the project stage are still invalid.
For version 2.3-SNAPSHOT it seems to be almost ok. The depth of
directory levels in the links is now correct but it looks that
distributionManagement.site.url is not resolved correctly.
Please look at
http://code.google.com/p/m4enterprise/source/browse/trunk/corporate-pom/pom.xml.
Element distributionManagement.site.url is set as a property
${com.acme.maven.corporate-pom.distributionManagement.siteUrl}.
Default value of the property is
scp://sites.intranet.acme.com/var/www. In my settings.xml I
overwrite this property with scp://sites.my-company.com/var/www.
As a result: stage is generated into
Re: Site plugin - broken links between modules only on site stage
Dear Marcin,
I am unable to build your project (missing dependencies, failed enforcer
rules), please provide a simple, self-contained test project if you want
me to check something for you.
However, from your description, this still sounds like MSITE-135 to me;
in 4. the {very-long-name.siteUrl} property is interpolated with the
parent project value instead of the cl value.
But then, since you specify the staging location on the command line
anyway, I don't see why you don't use the stagingDirectory parameter
directly, instead of going via distributionManagement.siteUrl, see
http://maven.apache.org/plugins/maven-site-plugin/usage.html (Staging a
site).
HTH,
-Lukas
Marcin Kuthan wrote:
Hi Lukas
I don't think that my findings are related to MSITE-135. Only
2.3-SNAPSHOT is affected.
You should reproduce the issue in 10 mins:
1. Follow http://code.google.com/p/m4enterprise/wiki/GettingStarted
(only Checkout Source Code and Install Corporate POM sections)
2. Go to trunk/modular-war
3. Call:
mvn clean
mvn -Dcom.acme.maven.corporate-pom.siteVersion=2.3-SNAPSHOT
-Dcom.acme.maven.corporate-pom.enforcerRulesDisabled site:site
site:stage
4. Call:
mvn clean
mvn -Dcom.acme.maven.corporate-pom.siteVersion=2.3-SNAPSHOT
-Dcom.acme.maven.corporate-pom.enforcerRulesDisabled site:site
site:stage
-Dcom.acme.maven.corporate-pom.distributionManagement.siteUrl=scp://host/var/www
For 3) generated stage are fine, links in modular-war to submodules are valid.
For 4) links are broken,
com.acme.maven.corporate-pom.distributionManagement.siteUrl property
is ignored
If you use
-Dcom.acme.maven.corporate-pom.distributionManagement.siteUrl=file:///home/
results are even worse. URLs are totally broken.
Marcin
On 31 January 2011 16:32, Lukas Theusslltheu...@apache.org wrote:
This sounds like a manifestation of
http://jira.codehaus.org/browse/MSITE-135 but I'm not sure. If you can
attach a simple test project that would help, I haven't tried to fix this
yet.
-Lukas
Marcin Kuthan wrote:
Hi Lukas
I'm sorry that I didn't specify versions in the first post. I tested
my poms with version 2.2 (for Maven 2.2.1) and version 3.0-beta-3 (for
Maven 3.0.2). In both cases links are invalid.
I updated my build to 2.3-SNAPSHOT and plugin reported invalid
character inurlelement. There was a mistake in property name, and
literal value ${prop} was used instead of interpreted value. The new
plugin versions helped me to find out this bug - great!
I checked again version 2.2, even with fixed property name links in
the project stage are still invalid.
For version 2.3-SNAPSHOT it seems to be almost ok. The depth of
directory levels in the links is now correct but it looks that
distributionManagement.site.url is not resolved correctly.
Please look at
http://code.google.com/p/m4enterprise/source/browse/trunk/corporate-pom/pom.xml.
Element distributionManagement.site.url is set as a property
${com.acme.maven.corporate-pom.distributionManagement.siteUrl}.
Default value of the property is
scp://sites.intranet.acme.com/var/www. In my settings.xml I
overwrite this property with scp://sites.my-company.com/var/www.
As a result: stage is generated into
target/staging/sites.my-company.com/var/www directory, but the links
look like
../../../../sites.intranet.acme.com/var/www/modular-war-parent/index.html
There is no sites.intranet.acme.com elements in the effective pom of
the project, variables are resolved correctly to values from
settings.xml.
Could you check for differences between directory structure and links
generation for 2.3-SNAPSHOT, please? Are they generated in the similar
way?
Many Thanks,
Marcin
On 31 January 2011 14:04, Lukas Theusslltheu...@apache.orgwrote:
Which version of the site plugin are you using (it's not specified in
your
poms)? Please test 2.3-SNAPSHOT, some staging issues should be fixed with
http://jira.codehaus.org/browse/MSITE-533.
HTH,
-Lukas
Marcin Kuthan wrote:
Hi
My multi module project is structured with separate aggregate pom and
parent pom (aggregate pom is not a parent pom).
All modules are aggregated by aggragate pom (parent pom is also
submodule of aggregate pom). All submodules inherit from parent pom.
Aggregate pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/pom.xml
Parent pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-parent/pom.xml
And other submodules:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-core/pom.xml
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-webapp/pom.xml
For all modulesurl are defined to reflect project structure. When
the site is deployed (mvn site-deploy) links between modules are
valid, but for site stage (mvn site:stage or mvn site:stage-deploy)
are broken.
It looks that relative links point one directory level too high. In
the index page of aggregate pom the link to the parent module looks
Re: Site plugin - broken links between modules only on site stage
Which version of the site plugin are you using (it's not specified in your poms)? Please test 2.3-SNAPSHOT, some staging issues should be fixed with http://jira.codehaus.org/browse/MSITE-533. HTH, -Lukas Marcin Kuthan wrote: Hi My multi module project is structured with separate aggregate pom and parent pom (aggregate pom is not a parent pom). All modules are aggregated by aggragate pom (parent pom is also submodule of aggregate pom). All submodules inherit from parent pom. Aggregate pom: http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/pom.xml Parent pom: http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-parent/pom.xml And other submodules: http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-core/pom.xml http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-webapp/pom.xml For all modulesurl are defined to reflect project structure. When the site is deployed (mvn site-deploy) links between modules are valid, but for site stage (mvn site:stage or mvn site:stage-deploy) are broken. It looks that relative links point one directory level too high. In the index page of aggregate pom the link to the parent module looks like: ../../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html If I change it to (remove one directory level): ../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html link is valid. Links to modular-war-parent from modular-war-core and modular-war-webapp are valid, e.g: ../index.html, only links from aggregate pom to submodules are broken. I tried to remove trailing slashes fromurl element but it didn't help, the links were unchanged. Do you have an idea where is a mistake in my configuration? And why links are broken only for site stage, when for regular site deployment are valid? Thanks, Marcin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site plugin - broken links between modules only on site stage
This sounds like a manifestation of
http://jira.codehaus.org/browse/MSITE-135 but I'm not sure. If you can
attach a simple test project that would help, I haven't tried to fix
this yet.
-Lukas
Marcin Kuthan wrote:
Hi Lukas
I'm sorry that I didn't specify versions in the first post. I tested
my poms with version 2.2 (for Maven 2.2.1) and version 3.0-beta-3 (for
Maven 3.0.2). In both cases links are invalid.
I updated my build to 2.3-SNAPSHOT and plugin reported invalid
character inurl element. There was a mistake in property name, and
literal value ${prop} was used instead of interpreted value. The new
plugin versions helped me to find out this bug - great!
I checked again version 2.2, even with fixed property name links in
the project stage are still invalid.
For version 2.3-SNAPSHOT it seems to be almost ok. The depth of
directory levels in the links is now correct but it looks that
distributionManagement.site.url is not resolved correctly.
Please look at
http://code.google.com/p/m4enterprise/source/browse/trunk/corporate-pom/pom.xml.
Element distributionManagement.site.url is set as a property
${com.acme.maven.corporate-pom.distributionManagement.siteUrl}.
Default value of the property is
scp://sites.intranet.acme.com/var/www. In my settings.xml I
overwrite this property with scp://sites.my-company.com/var/www.
As a result: stage is generated into
target/staging/sites.my-company.com/var/www directory, but the links
look like
../../../../sites.intranet.acme.com/var/www/modular-war-parent/index.html
There is no sites.intranet.acme.com elements in the effective pom of
the project, variables are resolved correctly to values from
settings.xml.
Could you check for differences between directory structure and links
generation for 2.3-SNAPSHOT, please? Are they generated in the similar
way?
Many Thanks,
Marcin
On 31 January 2011 14:04, Lukas Theusslltheu...@apache.org wrote:
Which version of the site plugin are you using (it's not specified in your
poms)? Please test 2.3-SNAPSHOT, some staging issues should be fixed with
http://jira.codehaus.org/browse/MSITE-533.
HTH,
-Lukas
Marcin Kuthan wrote:
Hi
My multi module project is structured with separate aggregate pom and
parent pom (aggregate pom is not a parent pom).
All modules are aggregated by aggragate pom (parent pom is also
submodule of aggregate pom). All submodules inherit from parent pom.
Aggregate pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/pom.xml
Parent pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-parent/pom.xml
And other submodules:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-core/pom.xml
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-webapp/pom.xml
For all modulesurlare defined to reflect project structure. When
the site is deployed (mvn site-deploy) links between modules are
valid, but for site stage (mvn site:stage or mvn site:stage-deploy)
are broken.
It looks that relative links point one directory level too high. In
the index page of aggregate pom the link to the parent module looks
like:
../../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html
If I change it to (remove one directory level):
../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html
link is valid.
Links to modular-war-parent from modular-war-core and
modular-war-webapp are valid, e.g: ../index.html, only links from
aggregate pom to submodules are broken.
I tried to remove trailing slashes fromurlelement but it didn't
help, the links were unchanged.
Do you have an idea where is a mistake in my configuration? And why
links are broken only for site stage, when for regular site deployment
are valid?
Thanks,
Marcin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Missing reports menu
Did you take into account the inheritAsRef attribute? If not it will default to false, meaning the reports menu is populated in the parent, and if the parent has no reports, it is removed... At least this is according to documentation, but I am confused about this myself, see my last comment at http://jira.codehaus.org/browse/MSITE-502. If you have a test project I will look at it. -Lukas Jörg Schaible wrote: Guys, recently I had to notice that our generated sites often miss the reports menu at all. This is somewhat annoying since no link exists anymore to the generated reports (although they exist), only the Maven logo is present in the left navbar. Looking at the output of site:effective-site the entry menu ref=reports / is simply missing. Does anybody know, what triggers this annoying behavior? It happens for projects that inherit from a separate parent in the repository and have themselves no own site.xml. We have this with M2 (site- plugin 2.2) and M3 (site-plugin 3.0.-beta-2). - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Site deployment (scp) with NullKnownHostProvider fails on Maven3
For the NPE in m3, this has just been filed: http://jira.codehaus.org/browse/MSITE-546 For m2, I'm not sure I understand you correctly, first you say it works, then you say it doesn't with the ssh extension (which you shouldn't need for scp). Maybe it's a version incompatibility, the current site plugin (m2) has a dependency on wagon-provider-api-1.0-beta-4. HTH, -Lukas Marcin Kuthan wrote: Hi I'm working on corporate pom and I would keep common corporate pom version for Maven 2 and Maven 3. But I can't configure site deployment with scp wagon provider for Maven 2 and 3. To avoid interaction during scp deployment I configured server with NullKnownHostProvider in settings.xml. server idsite/id usernamesite/username passwordpassword/password configuration knownHostsProvider implementation=org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostProvider hostKeyCheckingno/hostKeyChecking /knownHostsProvider /configuration /server With Maven 2 I'm able to deploy site successfully but Maven 3 throws NPE: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:stage-deploy (default-cli) on project corporate-pom: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:stage-deploy failed. NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:stage-deploy (default-cli) on project corporate-pom: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:stage-deploy 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:534) 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: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:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:stage-deploy failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:116) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.lang.NullPointerException at org.apache.maven.plugins.site.SiteDeployMojo.configureWagon(SiteDeployMojo.java:474) at org.apache.maven.plugins.site.SiteStageDeployMojo.deployStagingSite(SiteStageDeployMojo.java:185) at org.apache.maven.plugins.site.SiteStageDeployMojo.execute(SiteStageDeployMojo.java:145) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) ... 20 more I was surprised that for site deployment with scp there is no need to add wagon-ssh extension to my pom (at least for Maven 3). But if I declare extension: extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh/artifactId version1.0-beta-7/version /extension Site deployment with Maven 2 also fails (Maven3 throws NPE again): [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to configure Wagon: 'scp' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at
Re: pdf plugin broken in maven3?
http://maven.apache.org/guides/development/guide-testing-development-plugins.html HTH, -Lukas Andrew Geery wrote: I don't see 1.2-SNAPSHOT in the main repository -- what repository should I be pointing at? Thanks Andrew On Fri, Jan 21, 2011 at 2:53 PM, Lukas Theusslltheu...@apache.org wrote: I haven't actually tried with maven 3 but as I understand from Olivier's comments at MPDF-41, it should work apart from the reports inclusion. I have just re-deployed the current 1.2-SNAPSHOT, if you can test it, I will attempt a release next week (I was planning to release it during the Xmas holydays but Santa Claus brought me another toy...) Thanks, -Lukas Andrew Geery wrote: Is the PDF plugin expected to work in Maven3? I see this bug report [http://jira.codehaus.org/browse/MPDF-41], but it doesn't look like there has been a new release [or even that the issue has been resolved]. Does anyone know the timing for a new release? Thanks Andrew # mvn -v Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) Java version: 1.6.0_20, vendor: Sun Microsystems Inc. Java home: /usr/java/jdk1.6.0_20/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 2.6.9-42.elsmp, arch: i386, family: unix # mvn pdf:pdf ... [INFO] --- maven-pdf-plugin:1.1:pdf (default-cli) @ test --- [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.750s [INFO] Finished at: Fri Jan 21 11:58:52 EST 2011 [INFO] Final Memory: 11M/110M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf (default-cli) on project test: Execution default-cli of goal org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf: java.lang.NoSuchMethodError: org.apache.maven.plugin.PluginManager.verifyReportPlugin(Lorg/apache/maven/model/ReportPlugin;Lorg/apache/maven/project/MavenProject;Lorg/apache/maven/execution/MavenSession;)Lorg/apache/maven/plugin/descriptor/PluginDescriptor; - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: pdf plugin broken in maven3?
I haven't actually tried with maven 3 but as I understand from Olivier's comments at MPDF-41, it should work apart from the reports inclusion. I have just re-deployed the current 1.2-SNAPSHOT, if you can test it, I will attempt a release next week (I was planning to release it during the Xmas holydays but Santa Claus brought me another toy...) Thanks, -Lukas Andrew Geery wrote: Is the PDF plugin expected to work in Maven3? I see this bug report [http://jira.codehaus.org/browse/MPDF-41], but it doesn't look like there has been a new release [or even that the issue has been resolved]. Does anyone know the timing for a new release? Thanks Andrew # mvn -v Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) Java version: 1.6.0_20, vendor: Sun Microsystems Inc. Java home: /usr/java/jdk1.6.0_20/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 2.6.9-42.elsmp, arch: i386, family: unix # mvn pdf:pdf ... [INFO] --- maven-pdf-plugin:1.1:pdf (default-cli) @ test --- [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.750s [INFO] Finished at: Fri Jan 21 11:58:52 EST 2011 [INFO] Final Memory: 11M/110M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf (default-cli) on project test: Execution default-cli of goal org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf: java.lang.NoSuchMethodError: org.apache.maven.plugin.PluginManager.verifyReportPlugin(Lorg/apache/maven/model/ReportPlugin;Lorg/apache/maven/project/MavenProject;Lorg/apache/maven/execution/MavenSession;)Lorg/apache/maven/plugin/descriptor/PluginDescriptor; - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml: property interpolation and inheritance
That's an old bug: http://jira.codehaus.org/browse/MSITE-135
I am currently looking at site inheritance issues, maybe I'll get to it...
-Lukas
Andreas Sewe wrote:
Hi all,
I have a question regarding property interpolation and inheritance in
the case of site descriptors. I looks to my like these behave
differently than property interpolation and inheritance in the case of
the POM.
Suppose I have the following element within my parent project's site.xml
bannerRight
name${project.description}/name
/bannerRight
Now a child project's site:effective-site contains the following:
bannerRight
nameDescription of the *parent* project/name
/bannerRight
Why is that? Inherited elements in the POM (e.g., url) are subject to
property interpolation in the context of the child project rather than
the parent project. Why is this different for site descriptors? And is
there a workaround other than copy-and-pasting the site.xml into the
child project.
FWIW, I am using Maven 3.0.2, the maven-site-plugin version 3.0-beta-3,
and have attached my descriptor to the parent project; the attached
descriptor is already fully interpolated. :-(
Best wishes,
Andreas
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How do I use the Maven site plugin to push the reports to my local web server?
You mean site:deploy? http://maven.apache.org/plugins/maven-site-plugin/usage.html -Lukas ravi_atluri wrote: Hi I am really looking to get this issue resolved but am unable to do so. I have a local Apache Jetty web server installed in my local machine and I was wondering as to how to use the Maven site plugin to push the reports to my web server? Any help would be really appreciated. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to avoid '/./' part of URL during site deployment?
AFAIK a dot component in a path is still a valid URL so IMO the bug is on the server side. While it is probably a good idea for maven to normalize the path before the PUT, that's no reason to throw a 500 (internal server error...) Cheers, -Lukas Dennis Lundberg wrote: Hi After looking at the log over at the google code issue tracker, I think this bug is in Wagon. Uploading: ./css/maven-base.css to https://m4enterprise.googlecode.com/svn/site We should probably normalize the path before doing a PUT. On the other hand, it might be the the Site Plugin that is feeding it the wrong path. Please file an issue in JIRA for either of the projects so that we can track it properly. On 2010-12-15 23:24, Marcin Kuthan wrote: I configured extension explicitly: extension artifactIdwagon-webdav-jackrabbit/artifactId groupIdorg.apache.maven.wagon/groupId version1.0-beta-7/version /extension Exactly the same URL with '/./' and stack trace: Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://m4enterprise.googlecode.com/svn/site/./css/maven-base.css. Return code is: 500 at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280) at org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:188) at org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:182) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:257) ... 21 more On 15 December 2010 22:46, Dennis Lundbergdenn...@apache.org wrote: Hi Which version of the WebDAV Wagon are you using? Please try the latest 1.0-beta-7 if you aren't using it. On 2010-12-15 21:59, Marcin Kuthan wrote: Hi, I configured my project to use Wagon WebDAV provider to deploy project site. In general it works as I expected but it fails if the site is deployed on googlecode. Transfer error: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://m4enterprise.googlecode.com/svn/site/./css/maven-base.css. Return code is: 500 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:deploy (default-deploy) on project corporate-pom: Error uploading site: Failed to transfer file: https://m4enterprise.googlecode.com/svn/site/./css/maven-base.css. Return code is: 500 - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:deploy (default-deploy) on project corporate-pom: Error uploading site at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) 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:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188) at org.apache.maven.cli.MavenCli.main(MavenCli.java:134) 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:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:271) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) ... 19 more Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file:
Re: Maven 3 site doesn't generate an index.html
Check http://jira.codehaus.org/browse/MSITE-425 HTH, -Lukas Gabriele Kahlout wrote: Hello, I don't know what could be the problem. Could someone send me a sample project for which executing mvn site results in an index file under target/site? I only get a css and images folder in there. I'm using Windows 7. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven site broken on table generation
There are 2 issues here: the one that Dennis pointed out that the last
line of the table has to match the first; the other that you can't have
all cells in all rows empty. Just add at least one row with at least one
non-empty cell to make it work.
Since you say that this used to work, it would help to know in which
version the regression happened, I have tried with 2.0 site plugin (you
also have to downgrade the project-info-report-plugin then to avoid the
ArrayIndexOutOfBounds) and got the same exception.
HTH,
-Lukas
On 11/10/2010 07:33 AM, Dennis Lundberg wrote:
On 2010-11-09 22:25, Huang, Thomas (388J) wrote:
Hi,
I am using Maven 2.2.1 and mave-site-plugin 2.1.1. When I run 'maven site', it
gives me an error on parsing my APT file on table generation. It is stopped on
the first line where I defined the table with
*--++ +
|
*--
...
I ran into a similar issue about a week ago. The problem was that some
rows in the table didn't have enough rows in it. It was not the lines of
data in the APT file, but rather the formatting rows that contained the
error.
*-+---+--+
| {{{./jboss-packaging-maven-plugin/}jboss-packaging}} | 2.1.1 |
*-+--+
The last line above needed to be replace with this one (notice the added
+ character)
*-+---+--+
See this URL (which seems to currently be down) for what I did to fix it:
http://fisheye.codehaus.org/changelog/mojo/?cs=12955
This used to worked and no change was made to my APT file. I have tried older
versions of the plugin. The 2.1 plugin emit the same error. All 2.0.x plugins
emil an arrayoutofbound exception. This is blocking my site deploy. Please
advice.
Thomas.
Re: maven-pdf-plugin/maven-surefire-report-plugin showSuccess causing errors
This should be filed for surefire http://jira.codehaus.org/browse/SUREFIRE component 'Maven Surefire Report Plugin'. The problem is that for showSuccess=false an empty table is written but fo expects some tableRows even if they are empty. Cheers, -Lukas Darren Hartford wrote: Hey all, Not sure where to put this issue, but using the surefire-report(2.6) with showSuccess=false, with the maven-pdf-plugin (1.1) breaks. This is using a multi-module/aggregate report approach, maven 2.2.1. With showSuccess=true, everything works fine. Basic intent is to, on a release, create an aggregate/summary PDF of the release, but some of the items. such as the surefire-report, are too verbose. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId version2.6/version configuration !-- although would prefer this, causing fo:table-body generation issues -- showSuccessfalse/showSuccess aggregatetrue/aggregate /configuration /plugin Error === [ERROR] BUILD ERROR [INFO] [INFO] Error during document generation: Error creating PDF from /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: org.apache.fop.fo.ValidationException: file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): fo:table-body is missing child elements. Required Content Model: marker* (table-row+|table-cell+) [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error during document generation: Error creating PDF from /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: org.apache.fop.fo.ValidationException: file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): fo:table-body is missing child elements. Required Content Model: marker* (table-row+|table-cell+) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:584) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) 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:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during document generation: Error creating PDF from /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: org.apache.fop.fo.ValidationException: file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): fo:table-body is missing child elements. Required Content Model: marker* (table-row+|table-cell+) at org.apache.maven.plugins.pdf.PdfMojo.generatedPdf(PdfMojo.java:574) at org.apache.maven.plugins.pdf.PdfMojo.execute(PdfMojo.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.apache.maven.doxia.docrenderer.DocumentRendererException: Error creating PDF from /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: org.apache.fop.fo.ValidationException: file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): fo:table-body is missing child elements. Required Content Model: marker* (table-row+|table-cell+) at org.apache.maven.doxia.docrenderer.pdf.fo.FoPdfRenderer.generatePdf(FoPdfRenderer.java:349) at org.apache.maven.doxia.docrenderer.pdf.fo.FoPdfRenderer.render(FoPdfRenderer.java:175) at org.apache.maven.doxia.docrenderer.AbstractDocumentRenderer.render(AbstractDocumentRenderer.java:160) at
Re: Site plugin version management
Did you google for it? http://jira.codehaus.org/browse/MSITE-490 Why the javadoc doesn't work I don't know... -Lukas Benson Margulies wrote: Site:site says this over and over, in addition to running the javadoc over and over. INFO] Generating Project License report. [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin. What should I be specifying, and where should I be specifying it (reporting versus plugin management). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Building ODE with Maven
Tina Schliemann wrote: Hi, I try to build the apache ode with maven. With that command mvn install –Dmaven.test.skip=true I get that error [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task -ûDmaven.test.skip=true': you must specify a valid lifecycle You are using an invalid character for the cl option -D, it should be a normal minus sign. HTH, -Lukas phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pl uginVersion:goal The building of the elipse files with that command mvn eclipse:eclipse works fine Can u pls help me? Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: Building ODE with Maven
Tina Schliemann wrote: Hi It is a normal minus sign. That comes from copying out of the console. That’s the command I use mvn install –Dmaven.test.skip=true Then your console uses the wrong minus sign :) Compare: mvn install –Dmaven.test.skip=true (yours) mvn install -Dmaven.test.skip=true (mine) -Lukas -Ursprüngliche Nachricht- Von: Lukas Theussl [mailto:ltheu...@apache.org] Gesendet: Donnerstag, 16. September 2010 11:08 An: Maven Users List Betreff: Re: Building ODE with Maven Tina Schliemann wrote: Hi, I try to build the apache ode with maven. With that command mvn install –Dmaven.test.skip=true I get that error [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task -ûDmaven.test.skip=true': you must specify a valid lifecycle You are using an invalid character for the cl option -D, it should be a normal minus sign. HTH, -Lukas phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pl uginVersion:goal The building of the elipse files with that command mvn eclipse:eclipse works fine Can u pls help me? Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: PMD plugin: source xref not generated unless JXR runs first
Trevor Harmon wrote: On Aug 13, 2010, at 11:48 PM, Lukas Theussl wrote: if you want it to work with 'mvn site' you have to configure the jxr plugin as a report, see http://maven.apache.org/plugins/maven-jxr-plugin/usage.html Worked great; thanks! How can I help add this to the documentation? It was not at all clear to me... I have added a faq: http://svn.apache.org/viewvc?view=revisionrevision=985633 It will be published with the next release. Cheers, -Lukas Trevor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: PMD plugin: source xref not generated unless JXR runs first
This is not a bug, jxr has to run first if you want to link to xref. So if you want it to work with 'mvn site' you have to configure the jxr plugin as a report, see http://maven.apache.org/plugins/maven-jxr-plugin/usage.html HTH, -Lukas Trevor Harmon wrote: Hi, I'm trying to use the PMD plugin in my site reports, and it works fine except that it fails to generate source cross references. I get: [WARNING] Unable to locate Source XRef to link to - DISABLED If, however, I manually run the JXR plugin first: mvn jxr:jxr Then the source xref is generated and the warning goes away on the next build. This happens when running PMD via mvn site or directly with mvn pmd:pmd. I've attached a very simple test case that reproduces the problem with version 2.5 of the PMD plugin (the latest version). Is this a bug in the plugin, or have I configured it wrong? Thanks, Trevor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Apt munges local links to JavaDocs
I can confirm that this does NOT work as it should. I have opened
http://jira.codehaus.org/browse/DOXIA-397
Cheers,
-Lukas
Thom Nichols wrote:
I'm trying to put links in my apt documents that link to javadoc:
{{{../apidocs/groovyx/net/http/ParserRegistry.html#parseText(org.apache.http.HttpResponse)}ParserRegistry}}
I've got the relative path (../) in front, so it should be picked up as a
local (not internal link). Apt still doesn't like it though and munges it:
[WARNING] [APT Parser] Modified invalid link:
'parseText(org.apache.http.HttpResponse)' to
'../apidocs/groovyx/net/http/ParserRegistry.html#parseTextorg.apache.http.HttpResponse'
So essentially it doesn't like the parens in the anchor (method anchors that
include spaces and commas get munged too.) Boo! Now I can't link to
methods in javadocs. Do I need to add an absolute URI for all of these
links? As far as I can tell, I'm using doxia-core 1.1.3. Can someone
confirm for me that it _does_ work (maybe the dependencies aren't resolving
like I think they are?)
I'm using Maven 2.2.1 and running mvn site:site
Thanks!
Here's the relevant part of my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version2.1.1/version
dependencies
!-- For SyntaxHighlighter macro:
http://code.google.com/p/m2-site-tools/ --
dependency
groupIdcom.anasoft.os/groupId
artifactIdm2st-doxia-macros/artifactId
version${m2st.version}/version
/dependency
dependency
groupIdorg.apache.maven.doxia/groupId
artifactIddoxia-sink-api/artifactId
version1.1.3/version
/dependency
dependency
groupIdorg.apache.maven.doxia/groupId
artifactIddoxia-core/artifactId
version1.1.3/version
/dependency
/dependencies
/plugin
Re: maven-project-info-reports-plugin 2.2 - index page without links, empty navigation column?
This should be fixed in 2.1.1-SNAPSHOT: http://jira.codehaus.org/browse/MSITE-456 HTH, -Lukas Mirko Friedenhagen wrote: Hello, after my project reported a failure (java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791)) without me changing anything I searched for a solution and changed the maven-project-info-reports-plugin to version 2.2 in the reporting section and the maven-site-plugin to 2.1 (see http://fisheye.hudson-ci.org/changelog/Hudson/?cs=31237). Now the build succeeds again, however the index page does not show any links and though the individual reports are generated (see http://s312195779.online.de/hudson/job/hudson-jobConfigHistory/site/? resp. http://s312195779.online.de/hudson/job/hudson-jobConfigHistory/site/findbugs.html e.g.) the navigation column on the left side is empty for the individual reports as well. Regards Mirko - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Project Info Reports Plugin 2.2 Released
Are you sure you are using site-plugin-2.1? This should already be pulling in doxia-1.1. Also the line number 791 doesn't exist in XhtmlSink in doxia-1.1... it looks like you have an old doxia being mixed in by something else. If you can't track it, please attach a complete test project with error logs at http://jira.codehaus.org/browse/DOXIA. Thanks, -Lukas Kalle Korhonen wrote: Thanks! I tried 2.2 with the site plugin (2.1), but I'm getting: [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) which seems to be caused by: http://jira.codehaus.org/browse/DOXIA-215 Assuming the problem is that the site plugin uses an older version of doxia, is there a way to configure it use doxia 1.1 or is a new release of the site plugin required? Kalle On Thu, May 20, 2010 at 3:04 AM, Olivier Lamyol...@apache.org wrote: Hi, The Maven team is pleased to announce the release of the Maven 2.x Project Info Reports Plugin, version 2.2 NOTE : this version is site plugin 2.1+ required. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin, version 2.2 Bug : * [MPIR-150] - the dependency report ignores mirrors * [MPIR-159] - ZipException during mvn clean compile site * [MPIR-172] - Be sure that anchor are unique * [MPIR-174] - remove use of container.getLoggerManager() (to be compatible wih maven 3.x) * [MPIR-179] - Dependency File Details and Dependency Repository Locations tables have a border when rendered with maven-site-plugin 2.1 Improvement * [MPIR-137] - Dependency Locations should work with an intranet repository and restricted internet access * [MPIR-186] - Update location for Subversion Home page * [MPIR-189] - Allow configuration of mailing list header text. New Feature * [MPIR-170] - Create a module overview page ala m1 Task * [MPIR-101] - Update to Doxia 1.1 * [MPIR-173] - Review the Doxia Sink calls Enjoy, -- The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available
It's a warning about a maven-internal plugin, in this case the
project-info-reports plugin. Which version do you use? (If you upgrade
to latest 2.2, you also need site-plugin 2.1). Otherwise you can ignore
the warning.
HTH,
-Lukas
Raphael Ackermann wrote:
When running mvn clean install site on our own maven plugins I get the
following warnings
[INFO] Preparing javadoc:javadoc
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[INFO] [enforcer:enforce {execution: enforce-no-snapshots}]
[INFO] [site:site {execution: default-site}]
[INFO] Parent project loaded from repository.
[INFO] Parent project loaded from repository.
[INFO] Generating About report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Project Summary report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Dependencies report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
I am using the m-javadoc-p in version 2.7
mvn 2.2.1
Any hints as to what needs to be updated? Do I need to update code in
my plugin or plugin dependencies?
Raphael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available
Yes, it can be ignored AFAICT. I have opened a JIRA though:
http://jira.codehaus.org/browse/MPIR-194
Cheers,
-Lukas
Raphael Ackermann wrote:
I am using project-info-reports 2.2 and the maven-site-plugin 2.1 and
still get the warnings. So I guess I can ignore them in that case?!?
Raphael
On Fri, May 21, 2010 at 11:04, Lukas Theusslltheu...@apache.org wrote:
It's a warning about a maven-internal plugin, in this case the
project-info-reports plugin. Which version do you use? (If you upgrade to
latest 2.2, you also need site-plugin 2.1). Otherwise you can ignore the
warning.
HTH,
-Lukas
Raphael Ackermann wrote:
When running mvn clean install site on our own maven plugins I get the
following warnings
[INFO] Preparing javadoc:javadoc
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[INFO] [enforcer:enforce {execution: enforce-no-snapshots}]
[INFO] [site:site {execution: default-site}]
[INFO] Parent project loaded from repository.
[INFO] Parent project loaded from repository.
[INFO] Generating About report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Project Summary report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Dependencies report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
I am using the m-javadoc-p in version 2.7
mvn 2.2.1
Any hints as to what needs to be updated? Do I need to update code in
my plugin or plugin dependencies?
Raphael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Broken mvn site
Thanks! -Lukas Anders Hammar wrote: I'm pretty sure you're close to pissing some people off. why hasn't this been fixed yet and When is it going to be fixed is not the right wording for open source projects where you're not shipping in anything yourself. Creating jiras and providing patches (with test cases) is the way to go. /Anders On Wed, May 19, 2010 at 19:05, Tim Fulmertful...@dslextreme.com wrote: Hello, Yesterday we noticed an error when running mvn site to generate cobertura reports to track down some coverage issues. Turns out this was caused by a snapshot update mandated by the special way Maven handles plugin versioning. Things got even more special when trying to specify a version of org.apache.maven.plugins:maven-project-info-reports-plugin. Turns out plugin management doesn't work for reporting. The version specified in plugin management is ignored in reporting and the current version is used. Even though the current documentation on configuring reporting shows a plugin management configuration. The solution was to spam a version configuration across 20 some odd POM files. I'm sure we missed a few. This isn't the first time we've been bitten by Maven's special plugin versioning and dependency management. Other's have ongoing issues with this as well. My question is why hasn't this been fixed yet? Why is plugin management the one place where Maven's own versioning and dependency management practices are completely ignored in favor of something that's obviously broken? When is it going to be fixed? -- Tim - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: How to create a report based on annotations
No idea about the apt-maven-plugin, but for site customization, are you familiar with skins: http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html ? HTH, -Lukas Lewis, Eric wrote: Anyone? :-) -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Montag, 17. Mai 2010 11:07 An: Maven Users List Betreff: How to create a report based on annotations Hi I'd like to create a Maven report based on annotations (OVal annotations, to be precise). Can I use the apt-maven-plugin for this (and if yes, how would I do it)? Also, is there a tutorial for more sophisticated site plugins? Like using CSS styles, default images etc. Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
