[jboss-as7-dev] Documentation of Management Operations
David M. Lloyd
david.lloyd at redhat.com
Thu Jan 27 19:08:11 EST 2011
You first have to clone and install https://github.com/jbossas/jboss-dmr
since it's a snapshot.
On 01/27/2011 03:07 PM, Scott Stark wrote:
> When I cloned https://github.com/bstansberry/jboss-as/tree/detyped2 and
> switched to the detyped2 branch,
> I'm failing to build the JBoss Application Server: Controller Client
> module due to an issue with the
> org.jboss:jboss-dmr:jar:1.0.0.Beta2-SNAPSHOT artifact. Is my
> settings.xml out of date or something?
>
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Controller Client
> 7.0.0.Alpha2-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [WARNING] The POM for org.jboss:jboss-dmr:jar:1.0.0.Beta2-SNAPSHOT is
> missing, no dependency information available
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.431s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [1.095s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [2.288s]
> [INFO] JBoss Application Server: Controller Client ....... FAILURE [0.041s]
> [INFO] JBoss Application Server: Controller Core ......... SKIPPED
> [INFO] JBoss Application Server: Deployment Repository ... SKIPPED
> [INFO] JBoss Application Server: Process Controller ...... SKIPPED
> [INFO] JBoss Application Server: Server .................. SKIPPED
> [INFO] JBoss Application Server: Domain Core ............. SKIPPED
> [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: OSGi .................... SKIPPED
> [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Arquillian: Aggregator .. SKIPPED
> [INFO] JBoss Application Server: Arquillian: Service ..... SKIPPED
> [INFO] JBoss Application Server: Naming Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
> [INFO] JBoss Application Server: Threading Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
> [INFO] JBoss Application Server: Domain Client ........... SKIPPED
> [INFO] JBoss Application Server: Domain Controller ....... SKIPPED
> [INFO] JBoss Application Server: EE ...................... SKIPPED
> [INFO] JBoss Application Server: Host Controller ......... SKIPPED
> [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Managed Beans Subsystem . SKIPPED
> [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: OSGi Config Admin ....... SKIPPED
> [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Remoting Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
> [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Weld Integration ........ SKIPPED
> [INFO] JBoss Application Server: Build ................... SKIPPED
> [INFO] JBoss Application Server: Arquillian: Common Container SKIPPED
> [INFO] JBoss Application Server: Arquillian: Embedded Container SKIPPED
> [INFO] JBoss Application Server: Arquillian: Managed Container SKIPPED
> [INFO] JBoss Application Server: Arquillian: Remote Container SKIPPED
> [INFO] JBoss Application Server: Demos ................... SKIPPED
> [INFO] JBoss Application Server: Microcontainer Subsystem SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Plugin . SKIPPED
> [INFO] JBoss Application Server: Test Suite: Aggregator .. SKIPPED
> [INFO] JBoss Application Server: Test Suite: Integration Tests SKIPPED
> [INFO] JBoss Application Server: Test Suite: Smoke Tests . SKIPPED
> [INFO] JBoss Application Server: Test Suite: Stress Tests SKIPPED
> [INFO] JBoss Application Server: Test Suite: Benchmark Tests SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 6.799s
> [INFO] Finished at: Thu Jan 27 13:05:55 PST 2011
> [INFO] Final Memory: 34M/81M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project jboss-as-controller-client:
> Could not resolve dependencies for project
> org.jboss.as:jboss-as-controller-client:jar:7.0.0.Alpha2-SNAPSHOT:
> Failure to find org.jboss:jboss-dmr:jar:1.0.0.Beta2-SNAPSHOT in
> https://repository.jboss.org/nexus/content/groups/developer/ was cached
> in the local repository, resolution will not be reattempted until the
> update interval of jboss-developer-repository-group has elapsed or
> updates are forced -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn<goals> -rf :jboss-as-controller-client
>
>
> On 1/24/11 8:49 PM, Brian Stansberry wrote:
>> Committed in my detyped2 branch[1]
>>
>> 1) Checkout and build [1]
>>
>> 2) Start a standalone instance
>>
>> 3) In another window, cd into the demos module
>>
>> mvn install -Dexample=description
>>
>> It will dump the server's resource tree and then the descriptive
>> information we've written so far.
>>
>>
>> [1] https://github.com/bstansberry/jboss-as/tree/detyped2
>>
>> On 1/24/11 9:40 AM, Brian Stansberry wrote:
>>> I'll add a demo in the detyped2 branch that reads and prints the
>>> metadata from a standalone server.
>>>
>>> On 1/24/11 9:20 AM, Dimitris Andreadis wrote:
>>>> Maybe it is easier to write a client that connects to a live server, gets this metadata
>>>> information and prints it out in the desired form?
>>>>
>>>> something like 'twiddle info<objectname>' but over the profileservice?
>>>>
>>>> On 24/01/2011 14:40, Heiko Braun wrote:
>>>>>
>>>>> Can we create a WIKI space that documents existing managed operations?
>>>>> Will it possible to get some HTML docs? Or would I need to read every subsystem java code in order
>>>>> to figure out what managed op's and attributes are available?
>>>>>
>>>>> Ike
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
- DML
More information about the jboss-as7-dev
mailing list