You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by "Eric J. Schwarzenbach" <Er...@wrycan.com> on 2007/02/07 23:28:16 UTC
Re: Xerces 2.9.0 out on ibiblio?
I take it this hasn't happened yet? I'm not finding it, but maybe you've
switched to using a different path?
Michael Glavassevich wrote:
> I'll be vacationing over the next two weeks. Hopefully someone will step
> up to the plate if they really need this in the repo before the new year.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> nbeyer@gmail.com wrote on 12/20/2006 11:30:37 PM:
>
>
>> I'm working on it on and off. I was actually close to getting the
>> latest XML Commons uploaded (the first step), but it's sort of turned
>> into a mess. The requirements for the central repo upload have changed
>> recently, so I've been trying to adjust to some of that. The biggest
>> change is that all files must have PGP signatures; the JAR, the source
>> JAR, the javadoc JAR, the POMs, etc. Frankly, I'm a bit of a newbie to
>> that part of the ASF release process. My 'web of trust' isn't very
>> web-like yet.
>>
>> This tied in with the holidays has backed me up, so if anyone else is
>> up for the challenge, I have most of the artifacts created and
>> prepared; the most important being the POMs.
>>
>> -Nathan
>>
>> On 12/20/06, Michael Glavassevich <mr...@ca.ibm.com> wrote:
>>
>>> I think Nathan may have started to get things in place but I haven't
>>>
> heard
>
>>> anything.
>>>
>>> Michael Glavassevich
>>> XML Parser Development
>>> IBM Toronto Lab
>>> E-mail: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>> Jacob Kjome <ho...@visi.com> wrote on 12/20/2006 12:38:05 AM:
>>>
>>>
>>>> Any progress on this? Ant-1.7 was just released this evening with
>>>> Xerces-2.8.1. I guess they ignored my request to move to 2.9.0. In
>>>> any case, It would be helpful if the latest jars could get out into
>>>> the various maven repositories sometime soon.
>>>>
>>>> Jake
>>>>
>>>>
>>>>
>>>>
> ---------------------------------------------------------------------
>
>>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
"Eric J. Schwarzenbach" <Er...@wrycan.com> wrote on
02/09/2007 06:45:57 PM:
> 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?
Things will be compatible because all of the DOM L3 serialization code is
in the Xalan serializer. The internals can evolve without breaking Xerces
because Xerces only needs to know which class (a name which isn't going to
change) in Xalan implements LSSerializer. Xerces will load this class when
its on the classpath, otherwise it just falls back to the older (and still
functioning) Xerces serializer. We already had a hook like that into
Xalan's DOM Level 3 XPath implementation.
Xerces 2.9.0 wanted the new serializer so it could deprecate its native
serializer. Xalan 2.7.1 wanted Xerces 2.9.0 for the hook. They don't need
to be released in synch in the future.
> 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?)
It will be maintained by both communities, but only by the committers who
are familiar enough with the specs and the code to maintain it. There are
only a few people actively involved in both projects with that knowledge.
That was the concern, but if you want to make the case again for having a
separate project you could try posting something to the xalan-dev [1]
list.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
[1] http://xml.apache.org/mail.html#xalan-dev
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by "Eric J. Schwarzenbach" <Er...@wrycan.com>.
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: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> "Eric J. Schwarzenbach" <Er...@wrycan.com> 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: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>> nbeyer@gmail.com 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 <mr...@ca.ibm.com> wrote:
>>>>
>>>>
>>>>> nbeyer@gmail.com 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: mrglavas@ca.ibm.com
>>>>> E-mail: mrglavas@apache.org
>>>>>
>>>>>
>>>>>
> ---------------------------------------------------------------------
>
>>>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
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: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
"Eric J. Schwarzenbach" <Er...@wrycan.com> 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: mrglavas@ca.ibm.com
> > E-mail: mrglavas@apache.org
> >
> > nbeyer@gmail.com 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 <mr...@ca.ibm.com> wrote:
> >>
> >>> nbeyer@gmail.com 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: mrglavas@ca.ibm.com
> >>> E-mail: mrglavas@apache.org
> >>>
> >>>
---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >>> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by "Eric J. Schwarzenbach" <Er...@wrycan.com>.
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: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> nbeyer@gmail.com 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 <mr...@ca.ibm.com> wrote:
>>
>>> nbeyer@gmail.com 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: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
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: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
nbeyer@gmail.com 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 <mr...@ca.ibm.com> wrote:
> > nbeyer@gmail.com 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: mrglavas@ca.ibm.com
> > E-mail: mrglavas@apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by Nathan Beyer <nd...@apache.org>.
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 <mr...@ca.ibm.com> wrote:
> nbeyer@gmail.com 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: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
nbeyer@gmail.com 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: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by Nathan Beyer <nd...@apache.org>.
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?
-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/
On 2/7/07, Michael Glavassevich <mr...@ca.ibm.com> wrote:
> When Nathan got busy nobody volunteered to pick it up. I'm not sure what
> the status is now.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> "Eric J. Schwarzenbach" <Er...@wrycan.com> wrote on
> 02/07/2007 05:28:16 PM:
>
> > I take it this hasn't happened yet? I'm not finding it, but maybe you've
> > switched to using a different path?
> >
> >
> > Michael Glavassevich wrote:
> > > I'll be vacationing over the next two weeks. Hopefully someone will
> step
> > > up to the plate if they really need this in the repo before the new
> year.
> > >
> > > Michael Glavassevich
> > > XML Parser Development
> > > IBM Toronto Lab
> > > E-mail: mrglavas@ca.ibm.com
> > > E-mail: mrglavas@apache.org
> > >
> > > nbeyer@gmail.com wrote on 12/20/2006 11:30:37 PM:
> > >
> > >
> > >> I'm working on it on and off. I was actually close to getting the
> > >> latest XML Commons uploaded (the first step), but it's sort of turned
> > >> into a mess. The requirements for the central repo upload have
> changed
> > >> recently, so I've been trying to adjust to some of that. The biggest
> > >> change is that all files must have PGP signatures; the JAR, the
> source
> > >> JAR, the javadoc JAR, the POMs, etc. Frankly, I'm a bit of a newbie
> to
> > >> that part of the ASF release process. My 'web of trust' isn't very
> > >> web-like yet.
> > >>
> > >> This tied in with the holidays has backed me up, so if anyone else is
> > >> up for the challenge, I have most of the artifacts created and
> > >> prepared; the most important being the POMs.
> > >>
> > >> -Nathan
> > >>
> > >> On 12/20/06, Michael Glavassevich <mr...@ca.ibm.com> wrote:
> > >>
> > >>> I think Nathan may have started to get things in place but I haven't
>
> > >>>
> > > heard
> > >
> > >>> anything.
> > >>>
> > >>> Michael Glavassevich
> > >>> XML Parser Development
> > >>> IBM Toronto Lab
> > >>> E-mail: mrglavas@ca.ibm.com
> > >>> E-mail: mrglavas@apache.org
> > >>>
> > >>> Jacob Kjome <ho...@visi.com> wrote on 12/20/2006 12:38:05 AM:
> > >>>
> > >>>
> > >>>> Any progress on this? Ant-1.7 was just released this evening with
> > >>>> Xerces-2.8.1. I guess they ignored my request to move to 2.9.0. In
> > >>>> any case, It would be helpful if the latest jars could get out into
> > >>>> the various maven repositories sometime soon.
> > >>>>
> > >>>> Jake
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > > ---------------------------------------------------------------------
> > >
> > >>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > >>>> For additional commands, e-mail: j-users-help@xerces.apache.org
> > >>>>
> > >>>
> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > >>> For additional commands, e-mail: j-users-help@xerces.apache.org
> > >>>
> > >>>
> > >>>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > >> For additional commands, e-mail: j-users-help@xerces.apache.org
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > For additional commands, e-mail: j-users-help@xerces.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Xerces 2.9.0 out on ibiblio?
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
When Nathan got busy nobody volunteered to pick it up. I'm not sure what
the status is now.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
"Eric J. Schwarzenbach" <Er...@wrycan.com> wrote on
02/07/2007 05:28:16 PM:
> I take it this hasn't happened yet? I'm not finding it, but maybe you've
> switched to using a different path?
>
>
> Michael Glavassevich wrote:
> > I'll be vacationing over the next two weeks. Hopefully someone will
step
> > up to the plate if they really need this in the repo before the new
year.
> >
> > Michael Glavassevich
> > XML Parser Development
> > IBM Toronto Lab
> > E-mail: mrglavas@ca.ibm.com
> > E-mail: mrglavas@apache.org
> >
> > nbeyer@gmail.com wrote on 12/20/2006 11:30:37 PM:
> >
> >
> >> I'm working on it on and off. I was actually close to getting the
> >> latest XML Commons uploaded (the first step), but it's sort of turned
> >> into a mess. The requirements for the central repo upload have
changed
> >> recently, so I've been trying to adjust to some of that. The biggest
> >> change is that all files must have PGP signatures; the JAR, the
source
> >> JAR, the javadoc JAR, the POMs, etc. Frankly, I'm a bit of a newbie
to
> >> that part of the ASF release process. My 'web of trust' isn't very
> >> web-like yet.
> >>
> >> This tied in with the holidays has backed me up, so if anyone else is
> >> up for the challenge, I have most of the artifacts created and
> >> prepared; the most important being the POMs.
> >>
> >> -Nathan
> >>
> >> On 12/20/06, Michael Glavassevich <mr...@ca.ibm.com> wrote:
> >>
> >>> I think Nathan may have started to get things in place but I haven't
> >>>
> > heard
> >
> >>> anything.
> >>>
> >>> Michael Glavassevich
> >>> XML Parser Development
> >>> IBM Toronto Lab
> >>> E-mail: mrglavas@ca.ibm.com
> >>> E-mail: mrglavas@apache.org
> >>>
> >>> Jacob Kjome <ho...@visi.com> wrote on 12/20/2006 12:38:05 AM:
> >>>
> >>>
> >>>> Any progress on this? Ant-1.7 was just released this evening with
> >>>> Xerces-2.8.1. I guess they ignored my request to move to 2.9.0. In
> >>>> any case, It would be helpful if the latest jars could get out into
> >>>> the various maven repositories sometime soon.
> >>>>
> >>>> Jake
> >>>>
> >>>>
> >>>>
> >>>>
> > ---------------------------------------------------------------------
> >
> >>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >>>> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>>>
> >>>
---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >>> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org