-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DistributionMgmt->Site->URL incorrectly set for site:stage #333
Comments
@michael-o IMHO this is a bug in the maven-site-plugin, WDYT? |
Honestly, no.idea from the top.of.my head. |
I created https://issues.apache.org/jira/browse/MSITE-1032 for this. |
very strange ... last time when I released parent I don't have a problem |
The other way around, only affects single module repos. There |
if you set:
in plexus-sec-dispatcher stage will be ok ... magic 😄 |
I would like to release a plexus-pom, and next plexus-languages - with JDK 24 support Tested locally and looks ok. Do you have any objections? |
This will break maven-scm-publish-plugin leveraging that element as well. Also I consider this a workaround to say the least.. |
No objections to a release though. Not sure yet how to fix this issue (if at all in the parent) |
The distributionMgmt site URL in
plexus-pom/pom.xml
Line 328 in 393099c
scm:git:[email protected]:codehaus-plexus/plexus-sec-dispatcher.git
(from https://github.com/codehaus-plexus/plexus-sec-dispatcher/blob/35804938db2feec87fabe24d75509cd0d8dc3c47/pom.xml#L20). However this value is evaluated forsite:stage
(https://maven.apache.org/plugins/maven-site-plugin/stage-mojo.html) to calculate the folder structure being created belowtarget/staging
(for multimodule sites).By default the same value is also used by
maven-scm-publish-plugin
in https://maven.apache.org/plugins/maven-scm-publish-plugin/publish-scm-mojo.html#pubScmUrl. However this is already overwritten inplexus-pom/pom.xml
Line 534 in 393099c
distributionManagement.site.url
should rather point to the HTTP URL of where the site is hosted!The text was updated successfully, but these errors were encountered: