[ http://jira.jboss.com/jira/browse/JBAS-1265?page=history ]
Scott M Stark resolved JBAS-1265:
---------------------------------
Resolution: Done
Fix Version: JBossAS-3.2.7 Final
JBossAS-4.0.2RC1
A --bootdir or -d option has been added which is an absolute directory path or
url to a dir which is prepended to the Main boot classpath. If this is a file
path or url and the path is a dir, the dir and any jars are added to the boot
classpath.
> Restore the patchdir option behavior
> ------------------------------------
>
> Key: JBAS-1265
> URL: http://jira.jboss.com/jira/browse/JBAS-1265
> Project: JBoss Application Server
> Type: Feature Request
> Components: MicroContainer bus
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
> Reporter: Scott M Stark
> Assignee: Scott M Stark
> Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1
>
>
> Its seems that the patchdir server option no longer is really of much use
> since it cannot be used to patch the bootstrap components itself. There was a
> new -B|-bootlib option to prepend jars to the bootclasspath added to 3.2
> branch and the 4.0.1 release that allowed one to add jars to the dist/lib
> directory ahead of any bootstrap jars. This has been critiqued as:
> <critique>
> The problem with your patch, from my viewpoint, is that it uses
> ServerLoader.addLibrary(). This forces the
> javax-management-monitor-Monitor-patch.jar patch to jboss-jmx.jar to reside
> in the same directory as the rest of the boot JARs. That means that I either
> add my javax-management-monitor-Monitor-patch.jar patch JAR to the
> ${JBOSS_HOME}/lib directory, which means I'm directly fiddling with the Jboss
> distribution and I want to treat that as read-only, or I move all of
> ${JBOSS_HOME}/lib over to someplace under my own control, which means I am
> over-treating the correction. It seems that if the patch to Main uses
> ServerLoader.addURL() instead, I can keep the bulk of the boot JARs in
> ${JBOSS_HOME}/lib and still have the Monitor patch in a directory under my
> control.
> </critique>
> I believe the correct resolution is to restore the patchdir option to a
> behavior which prepends its argument url to the bootstrap classpath using the
> addURL as requested.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
