In order for jboss-admin-console to use the new build system, I'll need to
merge it from head. I was hoping we could get things sorted out well in head
before we had to start back-porting.
However, so long as jboss-admin-console has a shallow dependency tree, I don't
think this would be th
FYI the structure we are going with is as follows:
Module name at cvs.sourceforge.net: jboss-admin-console
CVS Branch: HEAD
Build system: New build system
The jboss-admin-console module has been created in HEAD of sourceforge CVS. At
the moment the module just contains a skeleton project stru
I'd say Branch_4_0 and "traditional" buildmagic, if we are talking about the
3.x/4.x branches. The new build system is changed in HEAD, from what I
understand.
Scott, should really confirm this.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862695#38626
So if we go with buildmagic one of things to manage will be the 3rd Party
dependencies:
I've looked at \etc\buildmagic\libraries.ent in the tools module in CVS. I
should be adding references to thirdparty .jars which the Admin Consoles needs
in here right? And then add the jars themselves insid
Since this should be a replacement for the web-console and this bundled with
the app server why isn't this just going into the existing jboss-4.0/console
module?
The thirdparty jars need to be canonicalized to ensure that the dependencies
are understood. There should not be 10 commons-logging.j
"[EMAIL PROTECTED]" wrote : Since this should be a replacement for the
web-console and this bundled with the app server why isn't this just going into
the existing jboss-4.0/console module?
|
Currently I view the Admin Console as complementing rather than replacing the
web-console. I could s
If this is going to be a new module then use the new build structure. There is
no reason to keep propgating the buildmagic nonsense.
Ultimately I see no reason for there to be multiple consoles. The jmx-console,
web-console and admin console should all be based on the same underlying
architectu
"[EMAIL PROTECTED]" wrote :
| Ultimately I see no reason for there to be multiple consoles. The
jmx-console, web-console and admin console should all be based on the same
underlying architecture with different plugins and services comprising the
functionality. The existing consoles should be
So just to summarize:
Module name at cvs.sourceforge.net: jboss-admin-console.
CVS Branch: Branch_4_0.
Build system: New build system.
Thanks
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862935#3862935
Reply to the post :
http://www.jboss.org/index.htm
