-
Notifications
You must be signed in to change notification settings - Fork 288
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
regression: Upgrade to jodconverter-local 4.2.3 imply to also add a dependency to jodconverter-core #183
Comments
* Explicit the dependency to jodconverter-core (see jodconverter/jodconverter#183)
* Explicit the dependency to jodconverter-core (see jodconverter/jodconverter#183)
It was not supposed to be. Maybe I misunderstood the gradle api dependency. jodconverter-core is supposed to be exposed from jodconverter-local. I'll fix that today. |
Could you please try the 4.2.4-SNAPSHOT please ?? I don't want to publish another faulty release!! Thank for reporting this by the way 👍 |
I will try. FTR our build is currently failing with:
our nexus is connected to central so we should have it, and locally I got the warning:
Not sure what's wrong though, since I can see the pom in https://search.maven.org/remotecontent?filepath=org/jodconverter/jodconverter-local/4.2.3/jodconverter-local-4.2.3.pom |
Hmm... I use the deprecated 'maven' plugin to publish my artifacts. I got a "warning" about missing "repository id" when I released the version. I never saw that before. Not sure why and what the consequences are... Maybe I'll have to rework my publishing todos list to fix this! |
So I just rebuilt locally jodconverter with |
Great! Thanks! I'll publish the version today. Sorry for that! |
No problem :) |
Fixed by 09b2751 |
I just upgraded jodconverter-local on XWiki to 4.2.3 and I got some builds issues because of class not found: after investigation it's because jodconverter-core is no longer retrieved. When adding explicitely the dependency it's working well.
I guess it's related with a1a5809#diff-442861bd065d1a83bdf0bf7cbf606f95R6
The text was updated successfully, but these errors were encountered: