So if it's not a separate project doesn't that mean Xerces and Xalan have to be released in sync? If Xalan x+1 is released depending on Xerces x, and Xerces x depends on Xalan Serializer x, isn't that a problem? That means you need both Xalan Serializer x and x+1 unless things happen to be compatible and you aren't using programmatic dependency management (as with Maven) that wants things to be logically consistent. Or am I missing something?
Shouldn't the need for logical consistancy trump "critical mass" concerns (and I'm not sure I even understand what that realistically means...if Xalan and Xerces depend on the serializer won't they be motivated, if not forcedm to maintain it as necessary even if its in a separate project?) Michael Glavassevich wrote: > Already talked about that with the Xalan folks. At the time they didn't > think it had the critical mass (i.e. too few committers) to survive as a > separate subproject. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [EMAIL PROTECTED] > E-mail: [EMAIL PROTECTED] > > "Eric J. Schwarzenbach" <[EMAIL PROTECTED]> wrote on > 02/09/2007 12:33:30 PM: > > >> This sounds like kind of a circular project dependency... Shouldn't this >> be eliminated, perhaps by serializer moving to commons or some such? >> >> Michael Glavassevich wrote: >> >>> Nathan, >>> >>> I'm not sure what Maven users expect the repository layout to look >>> > like > >>> but the second option sounds like it could confuse folks. IMHO, this >>> > jar > >>> really belongs amongst the Xalan artifacts. >>> >>> Thanks. >>> >>> Michael Glavassevich >>> XML Parser Development >>> IBM Toronto Lab >>> E-mail: [EMAIL PROTECTED] >>> E-mail: [EMAIL PROTECTED] >>> >>> [EMAIL PROTECTED] wrote on 02/07/2007 11:53:40 PM: >>> >>> >>> >>>> Assuming the serializer.jar is an important dependency for Xerces >>>> functionality, then I'd say that's up to the Xerces team. >>>> >>>> There are basically two options - >>>> * Wait for the next Xalan release, upload that under the 'xalan' >>>> > group > >>>> ID and link Xerces to that serializer.jar in the as a dependency. >>>> * Upload the serializer.jar now from Xerces package under the >>>> > 'xerces' > >>>> group ID and link to that as a dependency. >>>> >>>> -Nathan >>>> >>>> On 2/7/07, Michael Glavassevich <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>>> [EMAIL PROTECTED] wrote on 02/07/2007 10:41:52 PM: >>>>> >>>>> >>>>> >>>>>> Sorry. I did get busy. >>>>>> >>>>>> The Maven group has a new, more simple means of uploading stuff to >>>>>> >>>>>> >>> the >>> >>> >>>>>> central repo now, so I started looking at this again the other day, >>>>>> but I ran into a question that I was trying to track down and just >>>>>> >>>>>> >>> now >>> >>> >>>>>> gave up. >>>>>> >>>>>> The oddity is that the Xerces 2.9.0 contains a 'serializer.jar' >>>>>> > that > >>>>>> I'd need to upload first, but the JAR's manifest says that it's >>>>>> version 2.7.1 [1]. I assume this refers to the Xalan project, so I >>>>>> looked there to get the "canonical" version of the JAR, but Xalan >>>>>> currently only has a 2.7.0 release [2] and I verified that the >>>>>> serializer.jar in the Xalan package states that it's 2.7.0. >>>>>> >>>>>> How did Xerces get this JAR? Is there going to be another Xalan >>>>>> >>>>>> >>> release >>> >>> >>>>> soon? >>>>> >>>>> The Xalan developers built it for us after they froze their code. >>>>> >>>>> >>> Xerces >>> >>> >>>>> 2.9.0 was timed to coincide with Xalan 2.7.1. It was supposed to >>>>> >>>>> >>> happen a >>> >>> >>>>> few days apart to mitigate the chicken and egg problem we had. Xalan >>>>> needed a new Xerces release in order to enable the new DOM L3 >>>>> >>>>> >>> serializer >>> >>> >>>>> in their release. The new Xerces release needed the DOM L3 >>>>> > serializer > >>> from >>> >>> >>>>> Xalan. >>>>> >>>>> Unfortunately their release got delayed [3] for non-technical >>>>> > reasons. > >>> It >>> >>> >>>>> was tagged back in November but it still hasn't happened yet. I >>>>> >>>>> >>> believe >>> >>> >>>>> it's supposed to happen soon. If you need to put serializer.jar up >>>>> >>>>> >>> first, >>> >>> >>>>> you should probably wait for the Xalan release and get the jar from >>>>> >>>>> >>> there. >>> >>> >>>>>> -Nathan >>>>>> >>>>>> [1] Snippet from manifest of serializer.jar >>>>>> Implementation-Title: org.apache.xml.serializer >>>>>> Implementation-Version: 2.7.1 >>>>>> >>>>>> [2] http://www.apache.org/dist/xml/xalan-j/ >>>>>> >>>>>> >>>>> [3] http://marc.theaimsgroup.com/?l=xalan-dev&m=116495476400467&w=2 >>>>> >>>>> Michael Glavassevich >>>>> XML Parser Development >>>>> IBM Toronto Lab >>>>> E-mail: [EMAIL PROTECTED] >>>>> E-mail: [EMAIL PROTECTED] >>>>> >>>>> >>>>> > --------------------------------------------------------------------- > >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>>> >>>>> >>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
