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

use scmInfo when publishing ivy #3026

Open
MasseGuillaume opened this issue Mar 16, 2017 · 6 comments
Open

use scmInfo when publishing ivy #3026

MasseGuillaume opened this issue Mar 16, 2017 · 6 comments

Comments

@MasseGuillaume
Copy link
Member

@MasseGuillaume MasseGuillaume commented Mar 16, 2017

steps

set scmInfo
publish a sbt-plugin

problem

repository field is empty
http://ant.apache.org/ivy/history/latest-milestone/ivyfile/repository.html

expectation

scmInfo is not used

notes

this field is important for scaladex to work. We had to manually tag more than 400 plugins.

@jvican
Copy link
Member

@jvican jvican commented Mar 25, 2017

Yes, please. ScmInfo should be used...

@eed3si9n
Copy link
Member

@eed3si9n eed3si9n commented Mar 27, 2017

This might require update to Ivy itself in https://github.com/sbt/ivy. Happy to accept PR on this.

@MasseGuillaume
Copy link
Member Author

@MasseGuillaume MasseGuillaume commented Oct 6, 2017

It should also set a license field.

@laughedelic
Copy link
Member

@laughedelic laughedelic commented Oct 26, 2017

The license tag is present in the generated ivy.xml. But I don't see anything in the ivy specification related to the scmInfo. I'm only doubting about the repository tag. I guess, it's not related to scm anyhow, but could it be used for storing scm information?

@laughedelic
Copy link
Member

@laughedelic laughedelic commented Oct 26, 2017

Another related thing: sbt-bintray doesn't fill the Homepage field on Bintray, but it's present in the ivy.xml in the description tag.

@jvican
Copy link
Member

@jvican jvican commented Oct 26, 2017

We did this in Lambda World's spree. @MasseGuillaume I think that with this info, you can trace back from the ivy file to the github repo. It's true that the scm info is not present, but homepage is. Assuming that all projects use homepage for their repository homepage and not the project website (which is what I've seen anyway in all the builds I've hacked on), this should be feasible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.