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

Released archives of base aren't correctly laid out in maven repo #195

Closed
rtyler opened this issue Aug 17, 2015 · 3 comments
Closed

Released archives of base aren't correctly laid out in maven repo #195

rtyler opened this issue Aug 17, 2015 · 3 comments
Assignees
Labels

Comments

@rtyler
Copy link
Member

@rtyler rtyler commented Aug 17, 2015

Look at this repo layout and you'll see two directories jruby-gradle-plugin and jruby-gradle-base-plugin.

This is incorrectly laid out, and everything should be under jruby-gradle-plugin

@rtyler rtyler added bug base labels Aug 17, 2015
@rtyler rtyler self-assigned this Aug 17, 2015
@rtyler
Copy link
Member Author

@rtyler rtyler commented Aug 17, 2015

This is only affecting the base plugin because its directory (aka project name) doesn't match what it is supposed to be released as.

This is likely just a misconfiguration of the Gradle maven plugin

@rtyler
Copy link
Member Author

@rtyler rtyler commented Sep 16, 2015

Looks like this needs to be done in order for 1.1.0 to properly have its dependencies resolved. Going to throw this in the 1.1 milestone and release a 1.1.1 with a fix

@rtyler rtyler added this to the 1.1.0 - Dresden milestone Sep 16, 2015
@rtyler
Copy link
Member Author

@rtyler rtyler commented Sep 16, 2015

It looks like this bit of code in the bintray plugin is probably responsible. Since we don't have a pom type artifact in the archives configuration. One is being created with project.name as the name.

@rtyler rtyler closed this in 209ad7b Sep 16, 2015
rtyler added a commit that referenced this issue Sep 16, 2015
Fixes #195
rtyler added a commit that referenced this issue Sep 16, 2015
Fixes #195
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.