To: Maven Users List
Subject: Re: [ANN] Maven Site Plugin 2.0-beta-7 Released
The only thing else I can think of is that your local repo somehow got
messed up. You could try removing the directories org/apache/maven/doxia
and org/apache/maven/plugins/maven-site-plugin from your local repo
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 13, 2008 11:33 PM
To: Maven Users List
Subject: Re: [ANN] Maven Site Plugin 2.0-beta-7 Released
Then you need to override this by putting 2.0-beta-7 under the
pluginManagement section in *your* POM.
Giovanni Azua
To: Maven Users List
Subject: Re: [ANN] Maven Site Plugin 2.0-beta-7 Released
Then you need to override this by putting 2.0-beta-7 under the
pluginManagement section in *your* POM.
Giovanni Azua wrote:
Hi Dennis,
Many thanks! Yes the mvn help:effective-pom shows it is picking up
hi,
I had been following this thread because the MSITE-274 is not working for me
yet.
I have of course checked that the plugin is defined within the build section
and have tried several things but none work. I still get MSITE-274.
During the build, the previous 2.0-beta-6 is still pulled, below
Try running 'mvn decendency:tree' to see if some of your dependencies
are pulling in an old version of the Site Plugin.
Also running 'mvn help:effective-pom' will show you the POM that is
actually used when you run mvn.
Giovanni Azua wrote:
hi,
I had been following this thread because the
I put it in JIRA so it won't be forgotten:
http://jira.codehaus.org/browse/MPLUGIN-124
Handsome !
So, if I understand, the site goal of the maven-site-plugin is a build
mojo.
My bad, I though that it was a reporting mojo.
Yes, it is a build plugin. But it's easy to think of it as
You define the site plugin inside reporting, I guess you want it inside
build.
Isn't strange to have to define the maven-site-plugin inside build just to
specify the version ?
Why maven 2 can't take into account the version declare inside reporting ?
It seems to more natural isn't it ?
Rémy
Rémy Sanlaville wrote:
You define the site plugin inside reporting, I guess you want it inside
build.
Isn't strange to have to define the maven-site-plugin inside build just to
specify the version ?
Why maven 2 can't take into account the version declare inside reporting ?
It seems to more
There are two kinds of Mojos. A Mojo is a goal in plugin. There are build
mojos and there are reporting mojos. Build mojos are configured in the
build section of the POM while reporting mojos are configured in the
reporting section of the POM.
We should enhance the plugin-plugin to make it
Rémy Sanlaville wrote:
There are two kinds of Mojos. A Mojo is a goal in plugin. There are build
mojos and there are reporting mojos. Build mojos are configured in the
build section of the POM while reporting mojos are configured in the
reporting section of the POM.
We should enhance the
On Jul 7, 2008, at 5:17 AM, Dennis Lundberg wrote:
There are two kinds of Mojos. A Mojo is a goal in plugin. There are
build mojos and there are reporting mojos. Build mojos are
configured in the build section of the POM while reporting mojos
are configured in the reporting section of the
Yes, I did. It got downloaded, along with the newer doxia. I assume
it's getting used.
I think it's good practice to specify the version on your build and
reporting plugins to ensure repeatability of builds.
-K
On Jul 3, 2008, at 3:30 PM, Dennis Lundberg wrote:
Kathryn Huxtable wrote:
I
So I intended also to ask if I should maybe be looking at anything
else. Consider it asked. -K
On Jul 4, 2008, at 9:53 AM, Kathryn Huxtable wrote:
Yes, I did. It got downloaded, along with the newer doxia. I assume
it's getting used.
I think it's good practice to specify the version on
I can say, having looked at the HTML produced, that all the anchor
tags have newlines following them. This is generating the extra space.
For instance, the APT text
After reading this document, if you desire more detailed design
information, go to
{{{design.html}Design}}.
Depending
If you want to try it out, the code is available at
$ cvs -d :pserver:[EMAIL PROTECTED]:/home/cvs/i2mi login
$ cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvs/i2mi co
ldappc-mvn
The tests are broken at the moment, but not relevant for the site, so
adding -Dmaven.test.skip=true will be
Okay, I deleted the older site plugins from my local repo and rebuild
the site. It downloaded version 2.0-beta-6, despite my having, so far
as I know, no references to it, and a specific reference to 2.0-beta-7
in my pom.xml file.
I'm bewildered. Surely there are no transitive reporting
Okay, I renamed my entire repository and started from scratch. After
several attempts with strange results, I removed the maven-site-plugin
directory from my local repository and ran the command at the head of
the attached file. I'm also attaching my pom.
Note that it downloads both the
You define the site plugin inside reporting, I guess you want it
inside build.
I can confirm that MSITE-274 is fixed for me with beta-7.
HTH,
-Lukas
Kathryn Huxtable wrote:
Okay, I renamed my entire repository and started from scratch. After
several attempts with strange results, I removed
Thanks, that did the trick! -K
On Jul 4, 2008, at 3:08 PM, Lukas Theussl wrote:
You define the site plugin inside reporting, I guess you want it
inside build.
I can confirm that MSITE-274 is fixed for me with beta-7.
HTH,
-Lukas
Kathryn Huxtable wrote:
Okay, I renamed my entire
I don't see that MSITE-274 (spaces added) is fixed. I'm still getting
the extra spaces. -K
On Jul 3, 2008, at 12:34 AM, Dennis Lundberg wrote:
The Maven team is pleased to announce the release of the Maven Site
Plugin, version 2.0-beta-7
The Maven 2 Site plugin is used to generate a site
Kathryn Huxtable wrote:
I don't see that MSITE-274 (spaces added) is fixed. I'm still getting
the extra spaces. -K
I don't get the extra spaces when I specify version 2.0-beta-7. Did you
explicitly say this in your POM?
project
...
build
plugins
plugin
The Maven team is pleased to announce the release of the Maven Site
Plugin, version 2.0-beta-7
The Maven 2 Site plugin is used to generate a site for the project. The
generated site also includes the project's report distributions that was
configured in the reporting section of the pom.
22 matches
Mail list logo
