Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Publishing to subgroups #440

Closed
bbarker opened this issue Sep 28, 2018 · 2 comments
Closed

Publishing to subgroups #440

bbarker opened this issue Sep 28, 2018 · 2 comments
Labels
solved The issue was fixed/resolved
Milestone

Comments

@bbarker
Copy link
Contributor

bbarker commented Sep 28, 2018

I may have identified a bug, though as always, more likely a user error. When the org/groupId is set to w.x.y.z in the build.sc file and I own the groupId w.x.y on Maven/Sontatype/whatever.

I'm getting this error now: Could not find staging profile for groupId: edu.cornell.ncrn.ced2ar. I've uploaded to this groupId before using maven/pom, but the issue might be that the top level groupId associated with the profile is actually just edu.cornell.ncrn.

So I thought on this line ( https://github.com/lihaoyi/mill/blob/master/scalalib/src/mill/scalalib/publish/SonatypeHttpApi.scala#L39 ), maybe it should be checking that profile("name").str is a substring of groupId (rather than equal to it). But I tested it out locally (hopefully correctly using mill/out/dev/launcher/dest/run) using the change .find(profile => profile("name").str.startsWith(groupId) and got the same error. So, I'm not sure what to investigate next.

@bbarker
Copy link
Contributor Author

bbarker commented Sep 28, 2018

I had it backwards, this is fixed by #441

@bbarker
Copy link
Contributor Author

bbarker commented Oct 5, 2018

Fixed in #441

@bbarker bbarker closed this as completed Oct 5, 2018
@lefou lefou added this to the 0.2.9 milestone May 8, 2019
@lefou lefou added the solved The issue was fixed/resolved label Jul 3, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
solved The issue was fixed/resolved
Projects
None yet
Development

No branches or pull requests

2 participants