[
http://issues.apache.org/jira/browse/XALANJ-2086?page=comments#action_62331 ]
Brian Minchau commented on XALANJ-2086:
---
I have reviewed and approve the modification to the code. This dependancy on
sun.io.CharToByteConverter, but for the moment I
[ http://issues.apache.org/jira/browse/XALANJ-2086?page=history ]
Brian Minchau resolved XALANJ-2086:
---
Resolution: Fixed
Fix Version: CurrentCVS
Patch applied to CVS.
> Bug in the class org.apache.xml.serializer.Encodings
> -
[ http://issues.apache.org/jira/browse/XALANJ-2086?page=history ]
Brian Minchau updated XALANJ-2086:
--
Attachment: Encodings.patch1.txt
Attaching a patch based on the reporters comments in this issue.
> Bug in the class org.apache.xml.serializer.Encodin
[ http://issues.apache.org/jira/browse/XALANJ-2077?page=history ]
Brian Minchau resolved XALANJ-2077:
---
Resolution: Fixed
Fix Version: CurrentCVS
Patch was applied to CVS.
> Serializer's Encodings class methods slow: gettLastPrintable()
> co
[ http://issues.apache.org/jira/browse/XALANJ-2077?page=history ]
Brian Minchau updated XALANJ-2077:
--
Attachment: serializer.Encodings.patch3.txt
Attaching patch3 with the typo in the comments, that was caught by Henry, fixed.
> Serializer's Encodings
[ http://issues.apache.org/jira/browse/XALANJ-2036?page=history ]
Brian Minchau resolved XALANJ-2036:
---
Resolution: Incomplete
Resolving as incomplete. No test case was supplied, so we can't fix this one.
Please re-open this issue when you supply
[ http://issues.apache.org/jira/browse/XALANJ-1924?page=history ]
Brian Minchau resolved XALANJ-1924:
---
Resolution: Fixed
Fix Version: CurrentCVS
patch3 applied to CVS.
> Example on http://xml.apache.org/xalan-j/usagepatterns.html uses depric
[ http://issues.apache.org/jira/browse/XALANJ-2074?page=history ]
Brian Minchau resolved XALANJ-2074:
---
Resolution: Fixed
Fix Version: CurrentCVS
Resolving this issue, the patch was applied a little while ago, but the
resolution was not set a
[ http://issues.apache.org/jira/browse/XALANJ-2082?page=history ]
Brian Minchau resolved XALANJ-2082:
---
Resolution: Fixed
Fix Version: CurrentCVS
Patch applied to CVS.
> Serializer javadoc and comments should be more independent
> ---
[ http://issues.apache.org/jira/browse/XALANJ-2095?page=history ]
Brian Minchau resolved XALANJ-2095:
---
Resolution: Fixed
Fix Version: CurrentCVS
Patch applied to Apache CVS.
> Tab characters in text nodes are serialized to but shouldn't be
[ http://issues.apache.org/jira/browse/XALANJ-2096?page=history ]
Yash Talwar updated XALANJ-2096:
Attachment: XalanJ2096_Patch.txt
This patch modifies gold files spec1109.out and spec1110.out to reflect correct
output for corresponding testcases.
> Sm
Geir,
I could contact IBM legal if need be. I'm not in any legal department, I
just looking at this from my role as a member of the Xalan PMC.
Now that the CCLAs that you mention are signed, does it mean that ASF
doesn't have to ever have to worry again about individial CLAs signed by
IBM or Sun
My understanding is that Sun is signing a CCLA for their contribution of
JAXP 1.3.
I presume that like any code, the JAXP 1.3 code will have bugs, and will
develop over time, and will need fixes by someone. In the short term that
would most likely be Sun employees. As a Xalan PMC member it is my
[ http://issues.apache.org/jira/browse/XALANJ-2096?page=history ]
Yash Talwar updated XALANJ-2096:
Xalan info: [PatchAvailable]
> Smoketest fails with xml-xalan extract from CVS.
>
>
> Key: XALANJ
Smoketest fails with xml-xalan extract from CVS.
Key: XALANJ-2096
URL: http://issues.apache.org/jira/browse/XALANJ-2096
Project: XalanJ2
Type: Bug
Components: TestHarness-TestCase
Versions: CurrentCVS
Envi
[ http://issues.apache.org/jira/browse/XALANJ-2093?page=history ]
Brian Minchau updated XALANJ-2093:
--
Component: Serialization
> Serializer needs an API to set the end of line sequence
> ---
>
>
Xalan developers and committers:
please do not put any new author credits in our code.
A vote was held by the Apache Xalan PMC (Project Management Committee)
on the proposal that:
> no new author credits be introduced into source
> files for the Xalan processors or source for the documentation
> a
[
http://issues.apache.org/jira/browse/XALANJ-2095?page=comments#action_62297 ]
Yash Talwar commented on XALANJ-2095:
-
I have reviewed the patch provided by Brian Minchau. It looks good to me. I
approve this patch.
> Tab characters in text nodes
[ http://issues.apache.org/jira/browse/XALANJ-2095?page=history ]
Brian Minchau updated XALANJ-2095:
--
Attachment: CharInfo.patch1.txt
Attaching a patch for serializer's CharInfo.
The fix is not to set the horizontal tab as special for both
XML text node
[ http://issues.apache.org/jira/browse/XALANJ-2095?page=history ]
Brian Minchau updated XALANJ-2095:
--
Component: Serialization
> Tab characters in text nodes are serialized to but shouldn't be
>
[ http://issues.apache.org/jira/browse/XALANJ-2095?page=history ]
Brian Minchau updated XALANJ-2095:
--
Xalan info: [PatchAvailable]
reviewer: [EMAIL PROTECTED]
Marking PatchAvailable, and setting Yash T. as the reviewer.
> Tab characters in text n
[ http://issues.apache.org/jira/browse/XALANJ-2095?page=history ]
Brian Minchau reassigned XALANJ-2095:
-
Assign To: Brian Minchau
> Tab characters in text nodes are serialized to but shouldn't be
> --
[ http://issues.apache.org/jira/browse/XALANJ-2080?page=history ]
Henry Zongaro resolved XALANJ-2080:
---
Resolution: Duplicate
This is a duplicate of XALANJ-1962 - slightly different symptom, but same root
cause.
> EXSLT function set:has-same-node
Tab characters in text nodes are serialized to but shouldn't be
Key: XALANJ-2095
URL: http://issues.apache.org/jira/browse/XALANJ-2095
Project: XalanJ2
Type: Bug
Reporter: Brian Minchau
Pr
[
http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_62276 ]
Brian Minchau commented on XALANJ-2084:
---
Given Joanne's comment, once fixed, the new behavior will be to output
characters that are not in the output encoding as char
[ http://issues.apache.org/jira/browse/XALANJ-1912?page=history ]
Brian Minchau reassigned XALANJ-1912:
-
Assign To: Santiago Pericas-Geertsen
Assigning to Santiago P-G, after the Xalan JIRA meeting on April 5, 2005 he
sent me a not agreeing to look
Don't wrap RuntimeExceptions
Key: XALANJ-2094
URL: http://issues.apache.org/jira/browse/XALANJ-2094
Project: XalanJ2
Type: Bug
Versions: 2.6
Reporter: Frederic Simard
In org.apache.xalan.transformer.TransformerImpl the Run
[
http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_62271 ]
Rony Zoghby commented on XALANJ-2083:
-
Hi,
Good news! We can reproduce now with a standalone multi-threaded
single/multiple cpus example using the xalan version i've m
[ http://issues.apache.org/jira/browse/XALANJ-1574?page=history ]
Henry Zongaro reassigned XALANJ-1574:
-
Assign To: John Gentilin (was: Xalan Developers Mailing List)
> When trying to select 3824 rows from a DB i get an
> ArrayIndexOutOfBoundsExcep
[
http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_62266 ]
Henry Zongaro commented on XALANJ-2083:
---
Rony, you asked whether you're using the latest version of Xalan-J. No - the
latest version is Xalan-J 2.6, and you've repor
alan/test/java/build/xalan-smoketest-20050406.tar
[tar] Entry:
xml-xalan/test/smoketest/api/SAXTransformerFactoryAPITest/trax/sax/SAXTransformerFactoryAPITest_1.out
longer than 100 characters.
[tar] Resulting tar file can only be processed successfully by GNU
compatible tar commands
http://www.ietf.org/rfc/rfc2396.txt section 3.2.1 describes the registry
based authority part.
java.net.URI implements this correctly (as far as I can tell).
Regards
Dieter
"Brian Minchau (JIRA)"
06/04/2005 07:15
Please respond to
xalan-dev@xml.apache.org
To
xalan-dev@xml.apache.org
cc
I tagged xml-commons module yesterday with tag name
'*before-jaxp13-upgradation*'.
I plan to do the following but i will wait till tomorrow so as to give
chance to the community
to correct me if i am doing something wrong.
* update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
xml-com
[
http://issues.apache.org/jira/browse/XALANJ-1865?page=comments#action_62256 ]
Brian Minchau commented on XALANJ-1865:
---
Gopal, you are the originator of this issue. From the various comments in the
issue it seems to be a classpath/classloader is
Geir, I have uploaded sources at the same location
(xml-commons/contrib/jaxp13)
with Apache 2.0 license on every source file.
- Neeraj
Neeraj Bajaj wrote:
Ok, So i will add it and upload again.
- Neeraj
Geir Magnusson Jr. wrote:
On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
Hi Neeraj,
Subject:
Xalan-J bug triage minutes
Date:
Tuesday April 5, 2005
Xalan-J committers present:
- Brian Minchau (meeting chairperson)
- Dave Marston
- Henry Zongaro
- Joanne Tong
- John Gentilin
- Morris Kwan
- Sarah McNamara
- Yash Talwar
===
The question came up at the JIRA meeting today on whether the "Fix
Version/s" field can be used in a way that the Xalan custom field
"target-release" is not needed. The answer is yes.
I will be deleting the "target-release" custom field that I had added to
Xalan-J JIRA issues. The standard "Fix V
[ http://issues.apache.org/jira/browse/XALANJ-1403?page=history ]
Brian Minchau reassigned XALANJ-1403:
-
Assign To: Yash Talwar (was: Xalan Developers Mailing List)
Assigning to Yash Talwar, per the Xalan JIRA meeting on April 5, 2005.
However Yash
38 matches
Mail list logo