![]() At least they’ve now stopped releasing multiple incompatible versions with the same version number (they really did use to do that). This looks pretty poor to me as there’s lots that need importing, but I’ll see how things yeah, all these look somewhat odd, but these Google authored artifacts can be weird. Reactor.blockhound.* resolution:="optional", Then run atlas-package and similarly get error after error, so I kept on adding to the for each unresolved requirement until I had something which allowed me to compile: Ĭom.* resolution:="optional",Ĭom.* resolution:="optional",Ĭom.jcraft.jzlib.* resolution:="optional",Ĭom.press.* resolution:="optional",Ĭom.* resolution:="optional", * resolution:="optional",Ĭom.aayushatharva.brotli4j.* resolution:="optional", So I added this 4j to the like so: Ĭom.web.conditions.* resolution:="optional", container.OsgiContainerException: Cannot start plugin: me.-app 10:36:07,210 UpmAsynchronousTaskManager:thread-2 ERROR Unable to enable plugin me.-app at .BundleImpl.start(BundleImpl.java:984) at .BundleImpl.start(BundleImpl.java:998) at .Felix.resolveBundleRevision(Felix.java:4149) Now the question is, would that impact the behaviour of your plugin ? most likely not, it should have those platform artifacts out of the box.įormer Confluence Just as another update here, after adding the exclusions, I then got this osgi wiring problem on atlas-package Caused by: : In your case, you already know which dependency is bringing in those, so you can apply maven exclusions as follow You should apply the hint there use mvn dependency:tree to see what dependency is bringing in these artifacts, for instance : mvn dependency:tree -Dincludes=:guava Hello, this error means that your plugin is bundling artifacts that are already provided in the product through its platform. ![]() …but the question is, is there a better way? When you have a legitimate reason for disabling this check, as in your situation, you can so do by adding this to your AMPS configuration: īut I’ll just reiterate that most AMPS users should not do this, they should use the dependencies that the platform provides. Maven bans dependencies with no configuration: For more information about the errors and possible solutions, please read the following articles:Įach of the banned dependencies comes from a dependency in -client:google-http-client (which :google-auth-library-oauth2-http is dependent on). Re-run Maven using the -X switch to enable full debug logging. To see the full stack trace of the errors, re-run Maven with the -e switch. Look above for specific messages explaining why the rule failed. Failed to execute goal :confluence-maven-plugin:8.2.3:validate-banned-dependencies (default-validate-banned-dependencies) on project google-analytics-for-confluence: Some Enforcer rules have failed. Use 'mvn dependency:tree' to locate the source of the banned dependencies. Make sure platform artifacts are not bundled into pluginįound Banned Dependency: :jsr305:jar:3.0.2įound Banned Dependency: :guava:jar:26.0-jreįound Banned Dependency: javax.annotation:javax.annotation-api:jar:1.3.2įound Banned Dependency: :httpclient:jar:4.5.13įound Banned Dependency: :httpcore:jar:4.4.13 Rule 0: .enforcer.BannedDependencies failed with message: When this is added, I get an error from banned dependencies: - confluence-maven-plugin:8.2.3:validate-banned-dependencies (default-validate-banned-dependencies) google-analytics-for-confluence. I’m building a Confluence plugin with the following dependency:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |