[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jetty-dev] configure.dtd location
- From: Jesse McConnell <jesse.mcconnell@xxxxxxxxx>
- Date: Tue, 14 Apr 2009 19:09:44 -0500
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=qv8DhNb/S/K5bW8NEJwLTRI4UO7BQ2Ues1HHZ+yleS6Lqq7r4vXwgtHKn7gQDSUTMI zK7B86U13eqQxRbfciMQtv39LGPZFIgZyGQHDFvEXElb+KN8rduPiAl2Jrm0Qic7CrTT zUwiwg5/HKavr6TVUR0HZYffsjF1dTmmJro5A=
+1, I was wondering about changing the mortbay bit as well, good call
On Tue, Apr 14, 2009 at 18:53, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:
> I think that is a good location.
> Note we need to change the text as well, so I suggest that the config should
> not be:
> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN"
> I've updated all the configs I can find in the jetty-7 tree.
> can you make sure your conversion tool handles this DTD as well.
> Jesse McConnell wrote:
>> I am seeing a lot of http://jetty.eclipse.org/configure.dtd
>> definitions...we don't have that location afaik
>> I have been switching them to
>> http://www.eclipse.org/jetty/configure.dtd where we do have a
>> configure.dtd file that I placed there a while back...
>> open to discussing a better solution, just that the top one results in
>> lots of xml validation errors which eclipse loves to grip about..
>> jesse mcconnell
>> jetty-dev mailing list
> jetty-dev mailing list