I'm fine with moving it to https://svn.jboss.org/repos/jbossas/projects/ for now and we can move it into its own repo if necessary at a later date.
I couldn't see this situation explicitly covered by http://wiki.jboss.org/wiki/Wiki.jsp?page=SubversionMigrationGuide?
"Extraction of module from JBossAS source tree" seems to deal with the case of moving to a new repo. Anyways I'll raise a JBIT issue and see how we get on.
"We are working to upgrade subversion to 1.4 to address some issues found while migrating projects out of the old labs repo (JBIT-1222). This needs to happen before we can reliably do any extractions."
Kabir recently posted to the dev list how he moved aop into its own project. I don't think we need to wait for any SVN migration, we can just do as he did:
1. svn mkdir https://svn.jboss.org/repos/jbossas/projects/admin-console
2. svn move https://svn.jboss.org/repos/jbossas/trunk/admin-console https://svn.jboss.org/repos/jbossas/projects/admin-console/trunk
Then we need to get this building properly and running and tested as far as we can against HEAD of jbossas/trunk. Once we're happy we have something that runs (e.g. don't worry about test failures due to the read only nature of the JBossMQ configuration in the /all profile) we can tag it...
svn copy https://svn.jboss.org/repos/jbossas/projects/admin-console/trunk https://svn.jboss.org/repos/jbossas/projects/admin-console/tags/JBossAdminConsole_1_1_SNAPSHOT -m "Tag of projects/admin-console for a 1.1 snapshot of the 'admin-console' project."
After that we can take a look at adding support for JBoss Messaging.
Steps 1 and 2 are done. The Admin Console source has been moved out of head. Now I am off to ensure that it builds and runs properly before taking the snapshot.
I've made some changes so the Admin Console can again be built correctly. However all the webtests failed when running on the "default" server because:
. JBossMQ is no longer available so the jms and destintion tests fail as expected.
. MainDeployer's listDeployed() operation returns empty collection so the datasource cannot be listed correctly.
. hot deploy doesn't work, so the newly created datasource cannot be deployed.
I can't test the Admin Console against the "all" server because the WebDeployer wouldn't come up.
In today's meeting Charles decided if we can pass the homePage and dataSource tests we'll tag it and move on, but looks like we'll have to wait a little longer before we can pass these tests!
Per Charles? suggestion, the standalone admin console project has been tagged even though the test against the latest HEAD of jbossas/trunk cannot be completed successfully.