The jetty-service.jar in the 2.4.1 tree is ancient. I
didn't even realise that there was one. I should
probably remove it.
The idea is that if people want to run JBoss with
Jetty they d/l the combined bundle.
If you choose to run a separate Jetty installation you
run the risk of version mismatches - i.e. you may be
running a combination of versions of JBoss and Jetty
for which I have not released any integration at all.
Fortunately the APIs are fairly stable, and thus jars
tend to be swappable - but there is no guarantee.
For 3.0 I hope Jetty will simply be yet another
Service Archive that gets deployed as part of RH - so
yes, no separate tree (outside the .sar).
Jules
--- Jason Dillon <[EMAIL PROTECTED]> wrote: > > >
What version of Jetty was used to build the
> 2.4.1 JBoss release?
> >
> > The bundle is called
> JBoss-2.4.1_Jetty-3.1.RC9-1.zip - does that give it
> > away ? :-)
>
> Thanks =P I meant for JBoss-2.4.1.zip. I had to
> copy the jetty-service.jar
> from RC9 to make it work (I run from a seperate
> release of jetty... in my
> /thirdparty repository.
>
> > The final '1' is the bundle release counter,
>
> For 3.0 jetty will be completly integrated? No
> seperate jboss/ & jetty/
> directories and such?
>
> --jason
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
>
https://lists.sourceforge.net/lists/listinfo/jboss-development
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
