Skip to content
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.

Invalid name for a Snapshot build asset #8

Open
plmuninn opened this issue Jun 18, 2021 · 8 comments
Open

Invalid name for a Snapshot build asset #8

plmuninn opened this issue Jun 18, 2021 · 8 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@plmuninn
Copy link

Hi,

I'm trying to use this plugin for publishing package and everything works good beside of publishing SNAPHSOT versions. DO anyone had issue like this? Or could help me with it?

@bbstilson
Copy link
Owner

Would you mind sharing your build file? I would be happy to take a look and try to reproduce the problem.

@bbstilson bbstilson self-assigned this Jun 19, 2021
@plmuninn
Copy link
Author

I will add it shortly today

@FigBar
Copy link

FigBar commented Sep 15, 2021

Hi,
I was also recently trying to publish some SNAPSHOT version of Maven package to CodeArtifact using sbt-codeartifact. I came across the same issue. I did some debugging and here's what I found. As far as I understand this plugin doesn't support publishing SNAPSHOT versions.

  • First of all the names of published assets are wrong in case of snapshots. They should be published in the following format: <package_name>-<version_without_snapshot>-<timestamp(yyyyMMdd.HHmmss)>-<buildNumber>-<optional_classifier>.<extension (pom/jar)>.

  • Secondly the format of maven-metadata.xml is completely wrong for SNAPSHOT versions. The second example of maven-metadata.xml file under this link: example of maven-metadata.xml shows a correct form of this file for SNAPSHOT version.

Here's a screenshot from my debugging session showing that CodeArtifact returned 400 because of wrong asset name for SNAPSHOT version of a package.
sbt-codeartifact-400

Is there a chance of adding this case to the plugin?

@bbstilson
Copy link
Owner

Thanks for the details. I'll take a look at this tonight after work.

@bbstilson
Copy link
Owner

Quick update: I haven't solved this yet. I've made some progress, but work/life has been busy. I'll keep at it as time allows.

@gw-gdm
Copy link

gw-gdm commented Jan 23, 2022

Is there any update on this issue? It is really an important feature.

@bbstilson
Copy link
Owner

I'm sorry, my new job has kept me very busy, and I don't foresee having time to address this. Please feel free to submit a PR. I will be happy to review it.

@BassirouRabo
Copy link

when publishing, i am getting my Scala version appended to the package name example: myRepository:myPackageName_myScalaVersion how to remove the _myScalaVersion

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants