I need to do some administrative maintenance on changes made to the JBoss Test project. :) A couple of months ago I'd done the following: * Incremented to 1.0.6-SNAPSHOT * Broke out the "Server Manager" Component into repos/jbossas/projects/server-manager (org.jboss.jbossas:jboss-as-server-manager:0.1.0-SNAPSHOT) * Added support to jboss-test for definition of server:config in N Ant files (was previously just allowed in 1). So time for some cleanup: * Create "JBoss Test" Project in JIRA (Unless it's listed under something else and I can't find it?) * Create "JBossAS Server Manager" Project in JIRA * Set proper groupId, artifactId for jboss-test. "org.jboss.test:jboss-test"? * Approve current groupId/artifactId for Server Manager. Thoughts on the current one shown above? * Track these changes in JIRA so they're included in the release notes (I'll take care of this once the projects are created). Dimitris/Ryan/others, please review and advise. S, ALR

I think your suggestions are fine. I agree we need a project for jboss-test, but do we also need one for servermanager, or is there a way for them to share the same project? IE, you could have named versions "Server Manager 1.1.1" and "JBoss Test 1.2.0" within the same project. But it's really up to you. Andrew Lee Rubinger wrote: > I need to do some administrative maintenance on changes made to the > JBoss Test project. :) > > A couple of months ago I'd done the following: > > * Incremented to 1.0.6-SNAPSHOT > * Broke out the "Server Manager" Component into > repos/jbossas/projects/server-manager > (org.jboss.jbossas:jboss-as-server-manager:0.1.0-SNAPSHOT) > * Added support to jboss-test for definition of server:config in N Ant > files (was previously just allowed in 1). > > So time for some cleanup: > > * Create "JBoss Test" Project in JIRA (Unless it's listed under > something else and I can't find it?) > * Create "JBossAS Server Manager" Project in JIRA > * Set proper groupId, artifactId for jboss-test. > "org.jboss.test:jboss-test"? > * Approve current groupId/artifactId for Server Manager. Thoughts on > the current one shown above? > * Track these changes in JIRA so they're included in the release notes > (I'll take care of this once the projects are created). > > Dimitris/Ryan/others, please review and advise. > > S, > ALR >

The ServerManager is actually used for tests only right? So its name should be JBoss test ServerManager. then.. why not keep it on the jboss-test project? We have right now a capillarity of small projects. i.e. we are creating a hairy monster!

Please disregard what I said about ServerManager. I was thinking about the old stuff we had on JBAS 4, and as I see it is already separated. (my bad)

I just need to be able to upload a new jboss-test, and from what I understood from QA, Andrew needs to do something before they can release another jar, and right now can't commit a testcase because of this.

>> * Create JIRA Project: JBoss Test >> * Create JIRA Project: JBoss AS Server Manager >> * Assign proper project lead for each (Absolutely not me ;) )

>> >> S, >> ALR >> >> Ryan Campbell wrote: >>> I think your suggestions are fine. I agree we need a project for >>> jboss-test, but do we also need one for servermanager, or is there a >>> way >>> for them to share the same project? IE, you could have named versions >>> "Server Manager 1.1.1" and "JBoss Test 1.2.0" within the same project. >>> But it's really up to you. >>> >>> Andrew Lee Rubinger wrote: >>>> I need to do some administrative maintenance on changes made to the >>>> JBoss Test project. :) >>>> >>>> A couple of months ago I'd done the following: >>>> >>>> * Incremented to 1.0.6-SNAPSHOT >>>> * Broke out the "Server Manager" Component into >>>> repos/jbossas/projects/server-manager >>>> (org.jboss.jbossas:jboss-as-server-manager:0.1.0-SNAPSHOT) >>>> * Added support to jboss-test for definition of server:config in N Ant >>>> files (was previously just allowed in 1). >>>> >>>> So time for some cleanup: >>>> >>>> * Create "JBoss Test" Project in JIRA (Unless it's listed under >>>> something else and I can't find it?) >>>> * Create "JBossAS Server Manager" Project in JIRA >>>> * Set proper groupId, artifactId for jboss-test. >>>> "org.jboss.test:jboss-test"? >>>> * Approve current groupId/artifactId for Server Manager. Thoughts on >>>> the current one shown above? >>>> * Track these changes in JIRA so they're included in the release notes >>>> (I'll take care of this once the projects are created). >>>> >>>> Dimitris/Ryan/others, please review and advise. >>>> >>>> S, >>>> ALR

The new projects in JIRA are: JBoss AS Server Manager http://jira.jboss.com/jira/browse/JBASM JBoss Test http://jira.jboss.com/jira/browse/JBTEST I've temporary assigned Ryan and myself as leads until we figure out who would be more appropriate. We have already a problem with not clear leadership of individual AS components, now the situation is just getting worse with the expansion of standalone projects, we'll have more projects than developers :) For smaller/low-traffic projects like the above I'm not even sure we need leads. Any committer can make a change to those projects and release a new version whenever needed, after discussing it in the forums. Andrew Lee Rubinger wrote: > Clebert Suconic wrote: >> Please disregard what I said about ServerManager. I was thinking >> about the old stuff we had on JBAS 4, and as I see it is already >> separated. (my bad) > > Yes, it was separated as the function to start/stop/deploy is a > separate concern from testing APIs. The defining case was to reuse > these capabilities from Maven Plugins. > >> I just need to be able to upload a new jboss-test, and from what I >> understood from QA, Andrew needs to do something before they can >> release another jar, and right now can't commit a testcase because of >> this. > > I'm just waiting on the proper projects to be created in JIRA so we > can track the releases. I'll bug Dimitris about this again. > > >>> * Create JIRA Project: JBoss Test > >>> * Create JIRA Project: JBoss AS Server Manager > >>> * Assign proper project lead for each (Absolutely not me ;) ) > > S, > ALR > >>>> >>>> S, >>>> ALR >>>> >>>> Ryan Campbell wrote: >>>>> I think your suggestions are fine. I agree we need a project for >>>>> jboss-test, but do we also need one for servermanager, or is there >>>>> a way >>>>> for them to share the same project? IE, you could have named >>>>> versions >>>>> "Server Manager 1.1.1" and "JBoss Test 1.2.0" within the same >>>>> project. >>>>> But it's really up to you. >>>>> >>>>> Andrew Lee Rubinger wrote: >>>>>> I need to do some administrative maintenance on changes made to the >>>>>> JBoss Test project. :) >>>>>> >>>>>> A couple of months ago I'd done the following: >>>>>> >>>>>> * Incremented to 1.0.6-SNAPSHOT >>>>>> * Broke out the "Server Manager" Component into >>>>>> repos/jbossas/projects/server-manager >>>>>> (org.jboss.jbossas:jboss-as-server-manager:0.1.0-SNAPSHOT) >>>>>> * Added support to jboss-test for definition of server:config in >>>>>> N Ant >>>>>> files (was previously just allowed in 1). >>>>>> >>>>>> So time for some cleanup: >>>>>> >>>>>> * Create "JBoss Test" Project in JIRA (Unless it's listed under >>>>>> something else and I can't find it?) >>>>>> * Create "JBossAS Server Manager" Project in JIRA >>>>>> * Set proper groupId, artifactId for jboss-test. >>>>>> "org.jboss.test:jboss-test"? >>>>>> * Approve current groupId/artifactId for Server Manager. >>>>>> Thoughts on >>>>>> the current one shown above? >>>>>> * Track these changes in JIRA so they're included in the release >>>>>> notes >>>>>> (I'll take care of this once the projects are created). >>>>>> >>>>>> Dimitris/Ryan/others, please review and advise. >>>>>> >>>>>> S, >>>>>> ALR > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development