You might be jumping the gun a bit with this one. tools.jar is only needed afaik for Jasper i.e. when Jetty (or Tomcat) needs to serve jsp pages. Not everyone will want this, indeed many people will probably run JBoss without a servlet engine, and so they won't need tools.jar.
David > -----Original Message----- > From: Ignacio Coloma [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 15, 2001 7:57 AM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] RH: tools.jar (javac)... > > > I'm preparing a patch (my humble contribution, snif!) for > run.bat/run.jar. > It includes: > > 1.- Support for tools.jar 'a la' Tomcat: you should define a JAVA_HOME > environment variable that points to your java instalation > directory. It > checks if tools.jar is where it should. If not, it doesn't > let you start > JBoss. > 2.- Moves all the JAXP env variables into run.jar, cleaning > the bat file. > 3.- Document into run.bat a bit what's happening. > 4.- Include commented lines to start jboss in debug mode > (JPDA), both by > socket and by shared memory. There are docs out there about > how to connect > to an already started app. I use this one a lot. > > Ignacio. > > > -----Mensaje original----- > > De: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]En nombre de > > Andreas Schaefer > > Enviado el: miércoles, 14 de noviembre de 2001 16:46 > > Para: [EMAIL PROTECTED]; > > [EMAIL PROTECTED] > > Asunto: Re: [JBoss-dev] RH: tools.jar (javac)... > > > > > > Yes, you are missing the fact that tools.jar is plattform/vendor > > dependant. > > Therefore you would have to distribute one for each plattform. > > > > Andy > > > > ----- Original Message ----- > > From: <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, November 14, 2001 8:14 AM > > Subject: Re: [JBoss-dev] RH: tools.jar (javac)... > > > > > > > > > > Maybe I am missing something, but isn't this whole issue about > > distributing > > > a compiler with JBoss so the user doesn't have to > download the JDK and > > edit > > > a configuration file to point to it? > > > > > > If that is the case, can't we distribute jikes? > > > > > > -Phil > > > > > > > > > > > > > > > "Scott M Stark" > > > <[EMAIL PROTECTED]> To: > > "JBossDev \(E-mail\)" > > > Sent by: > > <[EMAIL PROTECTED]> > > > [EMAIL PROTECTED] cc: > > > eforge.net > Subject: > > Re: [JBoss-dev] RH: tools.jar > > > > > (javac)... > > > > > > 11/13/2001 05:37 PM > > > Please respond to "Scott M Stark" > > > > > > > > > > > > > > > > > > > > > That is how both the bundled tomcat and standalone tomcat > handles this. > > > You have to have the JDK tools.jar, or jikes, or some > other compiler > > > configured > > > as part of the installation. Since we can't bundle tools.jar > > and javac.jar > > > is > > > just a black box we don't want to include since it source for > > it can't be > > > obtained, > > > there is nothing we can do to make this a platform > independent zero > > > configuration issue as far as I know. > > > > > > xxxxxxxxxxxxxxxxxxxxxxxx > > > Scott Stark > > > Chief Technology Officer > > > JBoss Group, LLC > > > xxxxxxxxxxxxxxxxxxxxxxxx > > > ----- Original Message ----- > > > From: "David Maplesden" <[EMAIL PROTECTED]> > > > To: "JBossDev (E-mail)" <[EMAIL PROTECTED]> > > > Sent: Tuesday, November 13, 2001 4:14 PM > > > Subject: RE: [JBoss-dev] RH: tools.jar (javac)... > > > > > > > > > > No I haven't and I see now what you mean, I didn't read > what you put > > > > carefully enough. Still you might be able to do it > this way, IIRC we > > > used > > > > to distribute javac in a javac.jar that was distributed > with JBoss to > > > > different platforms and it seemed to work OK. > > > > > > > > I thought the only reason we weren't distributing tools.jar > > in the same > > > way > > > > is because of licensing issues with Sun. > > > > > > > > That of course brings up a problem with 1) you can't > distribute any > > > package > > > > you create that contains tools.jar (I think). > > > > > > > > Perhaps the easiest thing to do for the Jetty dist is > to reference > > > tools.jar > > > > as if it exists in the lib/ext dir and simply include a > README telling > > > > people what is going on, then they can supply their own > (platform > > > specific > > > > if neccessary) jar. > > > > > > > > David > > > > > > > > > -----Original Message----- > > > > > From: Julian Gosnell [mailto:[EMAIL PROTECTED]] > > > > > Sent: Wednesday, November 14, 2001 1:02 PM > > > > > To: David Maplesden; [EMAIL PROTECTED]; > > > > > [EMAIL PROTECTED] > > > > > Subject: Re: [JBoss-dev] RH: tools.jar (javac)... > > > > > > > > > > > > > > > David Maplesden wrote: > > > > > > > > > > > 1) worked fine for me... > > > > > > > > > > Have you tried it on different architectures? > > > > > > > > > > My concern is that if I do the build on Linux, the tools.jar > > > > > from my 1.3.1 > > > > > distrib may not work on e.g. a Mac etc... > > > > > > > > > > Jules > > > > > > > > > > > > _______________________________________________ > > > Jboss-development mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Jboss-development mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development