-
1. Re: Some recent improvements to jboss-server-manager and jbo
shelly.mcgowan Nov 3, 2008 11:30 AM (in response to akostadinov)I'll take a look at the changes.
-
2. Re: Some recent improvements to jboss-server-manager and jbo
shelly.mcgowan Nov 5, 2008 2:48 PM (in response to akostadinov)he changes identified plus:
https://jira.jboss.org/jira/browse/JBASM-21
contain cleanup of the srv mgr code plus updates to the dependency versions. I'd like to have a new release to be included in AS 5.0.0.GA by the end of the week; however, would like to get input on the dependencies from Paul and/or Dimitris.
I'd also like to change the version for JBoss Server Manager currently at 0.1.2.GA and make it a 1.0.0.GA release. -
3. Re: Some recent improvements to jboss-server-manager and jbo
pgier Nov 5, 2008 3:03 PM (in response to akostadinov)As far as the app server cyclic dependencies, the issue is solved from my point of view. They are currently excluded from the app server build, so it doesn't matter to me whether the scope is set to "provided" or not for these.
-
4. Re: Some recent improvements to jboss-server-manager and jbo
akostadinov Nov 6, 2008 3:11 AM (in response to akostadinov)Then I prefer leaving the dependencies as is, because we cannot and (don't want) to guarantee server-manager will run within the AS test suite only.
Moreover jboss-test depends on server-manager so there will be possible problems with the "provided" scope.
One possible improvement to server-manager would be to use the versions specified in component-matrix.pom but
1. I don't know how to do it without pulling in the dependencies from it
2. Why is JBoss AS using junit 3.8.2-brew !? -
5. Re: Some recent improvements to jboss-server-manager and jbo
dimitris Nov 6, 2008 5:09 AM (in response to akostadinov)I don't have the time to look into the changes in full detail, so if you are confident with the changes go ahead.
Again, I think the goal is to minimize dependencies and simplify things whenever possible.
PS
The <version.junit>3.8.2-brew</version.junit> in the component-matrix looks like an inconsistency, as version.junit is not used in the pom below.
I'll switch that to 3.8.2 and use it properly.