Ugh. I was -1 on the commit that caused this and it hasn't yet been
fixed. I'll be rolling it back later today. IT should build with
Maven 2.0.4 and no changes to the plugin plugin. I can't see that it
needs the latter, but it certainly requires Maven 2.1 which is not good.
- Brett
On 30/08/2006, at 8:12 AM, Vincent Siveton wrote:
Hi Jörg,
Based on your comments, here are my succesfull steps to build
maven-site-plugin from scratch:
- dwl and install m2-20060828.203000.tar.gz
- removed my repository
- added snapshot repository (see [1])
- build Maven (see [2])
* svn co http://svn.apache.org/repos/asf/maven/components/trunk/
* mvn -Papache install
* mvn -Pcodehaus install (if failed for some plexus or modello
artefacts)
- build maven site
* svn co http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-
site-plugin
* mvn -Papache install
To use maven-site, you need also PIR plugin so:
- svn co https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-
project-info-reports-plugin
- mvn -Papache install
HTH
Could you provide us the full stack trace? I dont see any reference to
maven-plugin-plugin:2.0-alpha-3.
Cheers,
Vincent
[1] http://maven.apache.org/guides/development/guide-plugin-
snapshot-repositories.html
[2] http://maven.apache.org/guides/development/guide-building-m2.html
2006/8/29, Joerg Hohwiller <[EMAIL PROTECTED]>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
As fix for MSITE-138, I want to build the maven-site-plugin from
trunk.
As I figured out, I also need to update maven-plugin-plugin that
also requires
me to update maven itself. As suggested by Vincent, I got the
latest integration
build which was m2-20060828.203000.tar.gz (2.1-SNAPSHOT).
I checked out http://svn.apache.org/repos/asf/maven/plugins/trunk
and tried to
build this with the new maven.
Unfortunately I got stuck again.
I always get:
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-plugin-plugin
Version: 2.0-alpha-3
Since maven did not tell me the path to this dependency, I decided to
move my complete local repository (~/.m2/repository) away and
start from
scratch. Then maven only downloaded apache-3.pom and maven-
parent-4.pom and then
failed with the same error. As I greped in the downloaded POMs for
maven-plugin-plugin, I got no results. To me it seems that maven
itself is
wired with the dependency on maven-plugin-plugin:2.0-alpha-3 (+).
Since maven-plugin-plugin:2.0-alpha-3 is not available and I can
not build
maven-plugin-plugin I am stuck.
Any suggestions what to do?
Thanks a lot...
Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE9KrGmPuec2Dcv/8RAqJhAJ9PB2HYHeFEePG4weMaLvq4K0C9dQCeJFIV
7Z8hgrMavddpHyNMsNeOLeg=
=ZK2r
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
