Skip to content
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

During a maven deployment, javadoc.jar for the scala library is deployed twice #7421

Closed
scabug opened this issue Apr 25, 2013 · 3 comments
Closed
Assignees
Labels
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Apr 25, 2013

When you exercise a deploy target in the maven build.xml file (created when building a release), you either write to a local maven repo or a distant one. You can deploy twice the same jar to a local repo, but when you do it to a distant repo, it doesn't generally let you delete the to-be-overwritten artifact. This results in your ant deployment script's public suicide.

This particular case happens with the javadoc.jar generated for the scala-library (see attached log).

Examining the src/build/maven/maven-deploy.xml maven deployment file with git blame shows the javadoc jars were added to deployment targets by Josh in 2012, but a previous extra-attachement stanza existed from an addition by Lukas in 2008.

@scabug
Copy link
Author

@scabug scabug commented Apr 25, 2013

Imported From: https://issues.scala-lang.org/browse/SI-7421?orig=1
Reporter: @huitseeker
Affected Versions: 2.11.0-M2
Other Milestones: 2.11.0-M3
Attachments:

Loading

@scabug
Copy link
Author

@scabug scabug commented Apr 25, 2013

Loading

@scabug
Copy link
Author

@scabug scabug commented May 24, 2013

@adriaanm said:
2.10.x: scala/scala#2595

Loading

@scabug scabug closed this May 30, 2013
@scabug scabug added the build label Apr 7, 2017
@scabug scabug added this to the 2.10.3-RC1 milestone Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants