You are right, of course. Thanks for you help, at all seems to work now.
ltheussl wrote:
>
> deploy:deploy-file doesn't take the pom from the jar, it constructs a
> default pom if the generatePom and pomFile parameters are not used, see
> http://maven.apache.org/plugins/maven-deploy-plugin/d
deploy:deploy-file doesn't take the pom from the jar, it constructs a
default pom if the generatePom and pomFile parameters are not used, see
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
Btw I checked that the pom in the jar *is* the same as the one on the repo.
HT
I was unable to download the pom from repo1.maven.org [1], and so I
downloaded the jar, and used "mvn deploy:deploy-file" to upload it to my
repo. It looks like "mvn deploy:deploy-file" takes the pom from inside the
jar, and that version of the pom is wrong.
Normally in released plugins, the pom
[maybe the user-list would be a better place to ask this?]
I can see a dependency on doxia-book here:
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-maven-plugin/1.0-alpha-9/doxia-maven-plugin-1.0-alpha-9.pom
which pom did you look at?
-Lukas
David Roussel wrote:
Hi,
Summary:
Hmm, looks like the error occured because the pom in the jar file I installed
manually was not production ready. Perhaps the pom on repo1.maven.org is
correct, but I can't seem to access it.
David Roussel wrote:
>
> Hi,
>
> Summary:
> doxia-maven-plugin-1.0-alpha-9.pom should list a depende
Hi,
Summary:
doxia-maven-plugin-1.0-alpha-9.pom should list a dependency on doxia-book.
Evidence:
java.lang.NoClassDefFoundError:
org/apache/maven/doxia/book/BookDoxiaException
Background.
I tried to follow the "Writing Books" example given here:
http://maven.apache.org/doxia/book/index.ht
