This one is clearly the one I was fearing last time you reported an issue
parent pom still has old svnpubsub url, causing unwanted relative path
Should either release parent pom or use m-site-p topParentUrl param to force
relative path calculations (like multi module builds)
Regards
Hervé (not
Hi Herve,
Can we please have a look at my account (Username:tibor17), especially
the profile because the Groups is jira-users instead of maven-developers.
Thx for answer.
Tibor
--
View this message in context:
http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-
Github user jsievers closed the pull request at:
https://github.com/apache/maven-wagon/pull/19
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature i
Hi,
so after a time i had done an other releases and found out the following:
I do the release like:
mvn release:prepare ...release:perform
cd target/checkout
mvn -Preporting site site:stage
now
mvn scm-publish:publish-scm
but unfortunately the published site doesn't contain the correct
c
GitHub user jsievers opened a pull request:
https://github.com/apache/maven-wagon/pull/19
[WAGON-432] make sure User-Agent header is sent exactly once
- remove unnecessary explicit default User-Agent (all 3 HTTP wagon
providers [http, lightweight, webdav] send a User-Agent by d
