-
Notifications
You must be signed in to change notification settings - Fork 30
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
Update p2AsMaven docs for multi-project usage in Gradle 6+ #119
Comments
What version are you using? Goomph 3.20.0 fixed compat with Gradle 6. |
Odd, I am on 3.21.0. I'm investigating further to see if I can narrow down the issue. |
My mistake.
|
It still failed after making the change and doing a clean build of the maven repo. Build scan here: https://gradle.com/s/7qczvv44rxefy |
Aha. It's because you're creating the repo yourself. Goomph does this automatically, but since you're using maven {
url project(':enm.model.p2').file('build/p2asmaven/maven')
metadataSources {
mavenPom()
artifact()
}
} I think it's common to use |
That most certainly did the trick! It now works as expected. Cheers, and thank you for your time! |
Fixed in |
Awesome, keep up the great work! IMHO this plugin is a lot more ergonomic than Tycho/Maven builds. I am delighted to have stumbled upon it. |
Hello,
I just wanted to inform you that the
p2AsMaven
task does not appear to work in Gradle versions greater than 5.6.4.Here is an example build that works in 5.6.4 but not 6.0.
enm.model/build.gradle
enm.model.p2/build.gradle
Running the build in 6.0 results in:
repeated for each dependency
Note: The repository exists and is valid in both cases. Perhaps gradle 6 has stricter constraints on version matching the dependency?
The text was updated successfully, but these errors were encountered: