Created attachment 940718 [details] screenshot Description of problem: When uploading a maven jar with a parent or dependency specified to artifact repostiory, the action fails due to java.lang.NoClassDefFoundError: org/codehaus/plexus/PlexusContainer. User gets an Error popup (see screenshot) similar to those mentioned in bug 999876. Server log contains: WARNING [Sisu] ... Error injecting: org.eclipse.aether.internal.transport.wagon.PlexusWagonProvider: java.lang.NoClassDefFoundError: org/codehaus/plexus/PlexusContainer ... Caused by: java.lang.ClassNotFoundException: org.codehaus.plexus.PlexusContainer from [Module "org.eclipse.aether:main" from local module loader @6f8cc276 (finder: local module finder @2330a31 (roots: <product_root>/modules,<product_root>/modules/system/layers/brms,<product_root>/modules/system/layers/base))] ... (stack trace in attachement) Version-Release number of selected component (if applicable): BRMS 6.1.0 DR3
Created attachment 940719 [details] stacktrace
Hi Zusana, Can you attach the jar file you used which causes this error to happen? I've tried uploading several jar's without seeing the error popup. Thanks Jeremy
Created attachment 940991 [details] test jar This is a very simple maven jar. The prject has only one dependency - junit:junit:4.11. Make sure you start with a clean product - most importantly, that you don't have the junit artifact in repositories used by the business-central. You could use anything else, just as long as the maven used by business-central has to look for something 'outside'. That will result in the 'java.lang.ClassNotFoundException: org.codehaus.plexus.PlexusContainer'.
Seems the problem might be with 'org.eclipse.aether' module setup. In <eap_root>/modules/system/layers/brms/org/eclipse/aether/main/ find module.xml and add dependency on: <module name="org.eclipse.sisu" export="false" slot="main" services="import" optional="false"/> This allowed me to upload the jar at the very least.
https://github.com/droolsjbpm/kie-wb-distributions/commit/61670484c81f898f27cbd9615a0381d81938cb92 Thanks Zusana. I couldn't reproduce this at first because my ~/.m2 repository was resolving the dependencies automatically. This is now fixed by making sure that the org.eclipse.aether module depends on org.eclipse.sisu, as you suggested.
Based on the comment 6, I am moving this to ON_QA for verification again.
No change, the commit might not have made it into product - the dependency is not declared in the module.
Hi Zusana, The fix (Sep 25th) did not make the cut for DR4 (Sep 24th), but it will be included in ER1. Jeremy
Verified with ER2.