Repro steps: 1. Login to JON instance. 2. navigate to RHQ AS server resource 3. Packages > New; Upload New Package 4. Specify "Jar Library" as the "Type", but upload a .jar 5. Attempt to deploy. 6. Packages > History 7. Note the failure for the jar you attempted to upload. Expected result: Successful deployment Current result: java.lang.UnsupportedOperationException: Deployment of new libraries is not supported by the plugin. at org.rhq.plugins.jbossas.JBossASServerComponent.deployPackages(JBossASServerComponent.java:413) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:446) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595)
This is expected, we haven't implemented it yet.
not only is this expected, but this is a private plugin that is not part of the RHQ codebase proper. please open in the appropriate repository for the plugin you're building, if you want this addressed as a bug (or i suppose a feature request).
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-762
Since the JBoss plugins are now part of the RHQ project, it makes sense to re-open this bug/feature request. Stack trace in Comment #1 is still present in the JON 2.3.1 builds. Corey will close out the JOPR-87 JOPR-283.
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage