If you are looking for the jars that contains that class, the dist of wildfly-9.0.0.CR1-SNAPSHOT have it on  those two jars:

org.jboss.as.domain.management.security.adduser.AddUser

                 located in jar         ./wildfly-9.0.0.CR1-SNAPSHOT/bin/client/jboss-cli-client.jar

org.jboss.as.domain.management.security.adduser.AddUser

                 located in jar         ./wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base/org/jboss/as/domain-management/main/wildfly-domain-management-1.0.0.Beta2.jar

If you look at ./dist/target instead of the project root it will reduce the ambiguities on your search.
I've made a tool for locate classes as you did, I called jfinder and it facilitates my life a lot.  :)
Actually, I have to improve that, because it brings anything that contains the string to be searched.

Hello Brandon,

We split the source base for 9, so now the core server is in a separate repo, wildfly-core.

The class you are looking for is here:
https://github.com/wildfly/wildfly-core/tree/master/domain-management/src/main/java/org/jboss/as/domain/management/security/adduser

Happy Hacking,
-Jason

On Apr 10, 2015, at 9:19 PM, Brandon Gaisford <bgaisford@punagroup.com> wrote:


Newbie contributor here,

Started looking into WFLY-2456, have forked/cloned/built the project and the server starts up as expected.  Started digging through the source tree for the org.jboss.as.domain.management.security.adduser.AddUser class but it does’t appear to be there.  I’m guessing the dependency is being sucked in by Maven during the build process.

A quick search through the dist tree reveals a couple jars that contain the class in question:

Starting search for org/jboss/as/domain/management/security/adduser/AddUser.class in /Volumes/Dev/punagroup/git/wildfly
Zipfile: /Volumes/Dev/punagroup/git/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/bin/client/jboss-cli-client.jar contains entry name: org/jboss/as/domain/management/security/adduser/AddUser.class
Zipfile: /Volumes/Dev/punagroup/git/wildfly/dist/target/wildfly-9.0.0.CR1-SNAPSHOT/bin/client/jboss-cli-client.jar contains entry name: org/jboss/as/domain/management/security/adduser/AddUser.class
Zipfile: /Volumes/Dev/punagroup/git/wildfly/dist/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base/org/jboss/as/domain-management/main/wildfly-domain-management-1.0.0.Beta2.jar contains entry name: org/jboss/as/domain/management/security/adduser/AddUser.class
Zipfile: /Volumes/Dev/punagroup/git/wildfly/testsuite/integration/smoke/target/jbossas/bin/client/jboss-cli-client.jar contains entry name: org/jboss/as/domain/management/security/adduser/AddUser.class
Zipfile: /Volumes/Dev/punagroup/git/wildfly/testsuite/integration/target/jbossas/bin/client/jboss-cli-client.jar contains entry name: org/jboss/as/domain/management/security/adduser/AddUser.class
Zipfile: /Volumes/Dev/punagroup/git/wildfly/web-dist/target/wildfly-web-9.0.0.CR1-SNAPSHOT/modules/system/layers/base/org/jboss/as/domain-management/main/wildfly-domain-management-1.0.0.Beta2.jar contains entry name: org/jboss/as/domain/management/security/adduser/AddUser.class
Exiting routine.

Looking for advice from the group, has this code not been migrated to the new source tree yet, or are there other intentions.  Any pointers would be appreciated.


Brandon


_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev