[
https://issues.apache.org/jira/browse/XERCESC-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2163:
Assignee: (was: Roger Leigh)
> XercesMessages_en_US.cat is installed to wr
[
https://issues.apache.org/jira/browse/XERCESC-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2135:
Assignee: (was: Roger Leigh)
> build: GNU iconv transcoder only works on GNU/Li
[
https://issues.apache.org/jira/browse/XERCESC-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2203:
Assignee: (was: Roger Leigh)
> MingGW time functions are bro
[
https://issues.apache.org/jira/browse/XERCESC-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2167:
Assignee: (was: Roger Leigh)
> Do not set SONAME when building shared l
[
https://issues.apache.org/jira/browse/XERCESC-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2164:
Assignee: (was: Roger Leigh)
> Failed to link nonstandard OpenSSL librar
[
https://issues.apache.org/jira/browse/XERCESC-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2208:
Assignee: (was: Roger Leigh)
> Rationalise XercesIntTy
[
https://issues.apache.org/jira/browse/XERCESC-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2156:
Assignee: (was: Roger Leigh)
> fix static linking with c
[
https://issues.apache.org/jira/browse/XERCESC-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2206:
Assignee: (was: Roger Leigh)
> Use char16_t and unicode literals to replace vari
[
https://issues.apache.org/jira/browse/XERCESC-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2200:
Assignee: (was: Roger Leigh)
> Update AppVeyor image in
[
https://issues.apache.org/jira/browse/XERCESC-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2204:
Assignee: (was: Roger Leigh)
> Remove message loa
[
https://issues.apache.org/jira/browse/XERCESC-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2205:
Assignee: (was: Roger Leigh)
> Require std::mutex and std::thr
Hi,
I'm afraid that I no longer use actively use Xerces-C++ for any of my current
projects and I have been far too time constrained to participate in any way for
some time. Please could I be removed from the project?
Thanks all for allowing me to contribute to the project over the last few
Hi Scott,
With regard to the retirement discussion, I just wanted to forward this message
on from Even Rouault who was having trouble subscribing and posting to the list:
Hi,
I have given a try to 3.2.4rc1 against the GDAL (https://gdal.org /
https://github.com/OSGeo/gdal)
FYI:
bullseye/stable: GCC 10.2
buster/oldstable: GCC 8.3
stretch: GCC 6.3
So C++11 should have been the default in the last three Debian major releases.
I agree that backing out the nullptr use is the best course of action
irrespective of any other considerations.
Kind regards,
Hi Scott,
All of our PRs are testing on Travis-CI using Ubuntu 18.04 with GCC 7.5 (e.g.
https://app.travis-ci.com/github/apache/xerces-c/jobs/552979282).
So that should be near enough to Debian, and it's not so cutting edge that the
compiler capabilities we are testing against aren't present on
Hi Scott,
+1 from me.
I've tested on FreeBSD/amd64. All the tests pass, plus an extended set of
tests used by my own application and its unit and integration tests.
Kind regards,
Roger
> -Original Message-
> From: Cantor, Scott
> Sent: 14 October 2022 17:34
> To:
> -Original Message-
> From: Cantor, Scott
> Sent: 14 October 2022 17:34
> To: c-dev@xerces.apache.org
> Subject: Re: 3.2.4 release candidate
>
> FWIW we still need one more +1 vote I believe.
I will try to find time to do some testing this weekend.
Regards,
Roger
> -Original Message-
> From: Boris Kolpackov
> Sent: 10 October 2022 17:17
> To: c-dev@xerces.apache.org
> Subject: Re: Prepping a 3.2.4 release
>
> Cantor, Scott writes:
>
> > On 10/10/22, 10:14 AM, "Boris Kolpackov"
> wrote:
> >
> > > What would be the other options for XML Schema
since 01 Oct 2022:
$ git shortlog -s --oneline --all --since "01 OCT 2012"
35 Alberto Massari
1 Chris Mc
26 Even Rouault
1 Fred Hornsey
183 Roger Leigh
171 Scott Cantor
I only joined out of necessity to keep it going for use by my work projects,
continued
Hi Scott,
I'm afraid that due to other commitments, I've been unable to do any further
work on the master branch for 4.0.0, and it's unlikely that this will change in
the near future. If anything, I'm unlikely to be able to spend much more time
on the project at all, and I might have to end
[
https://issues.apache.org/jira/browse/XERCESC-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17613131#comment-17613131
]
Roger Leigh commented on XERCESC-2236:
--
The change looks fine to me, and I've applied it to master
[
https://issues.apache.org/jira/browse/XERCESC-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17613126#comment-17613126
]
Roger Leigh commented on XERCESC-2219:
--
Yes, this was applied.
> XMLReader constructor: mem
[
https://issues.apache.org/jira/browse/XERCESC-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh closed XERCESC-2219.
Resolution: Fixed
> XMLReader constructor: memory leak when refreshRawBuffer() thr
Hi Robert,
I don't think you've overlooked anything here.
Kind regards,
Roger
> -Original Message-
> From: Robert Hairgrove
> Sent: 29 August 2022 10:10
> To: c-dev@xerces.apache.org; c-us...@xerces.apache.org
> Subject: Re: Xerces 4 and XML Schema 1.1 validation
>
> It looks like I
Hi Robert,
If you compiled without network access, then you'll need to be sure that all of
the schema files are accessible, for example by implementing a custom
EntityResolver. At a minimum, you'll want to provide your own schemas, plus
any schemas they depend upon, e.g. XMLSchema.
I would
[
https://issues.apache.org/jira/browse/XERCESC-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448399#comment-17448399
]
Roger Leigh commented on XERCESC-2231:
--
While the move to CMake may be related, this was all
[
https://issues.apache.org/jira/browse/XERCESC-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433408#comment-17433408
]
Roger Leigh commented on XERCESC-2220:
--
[~and...@avenza.com] The reason this hasn't been remedied
[
https://issues.apache.org/jira/browse/XERCESC-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417810#comment-17417810
]
Roger Leigh commented on XERCESC-2225:
--
XERCESC-2226 added as a followup.
> Link to instal
Roger Leigh created XERCESC-2226:
Summary: Increment minimum CMake version to 3.12
Key: XERCESC-2226
URL: https://issues.apache.org/jira/browse/XERCESC-2226
Project: Xerces-C++
Issue Type
Roger Leigh created XERCESC-2225:
Summary: Link to installed CMake targets of CURL
Key: XERCESC-2225
URL: https://issues.apache.org/jira/browse/XERCESC-2225
Project: Xerces-C++
Issue Type
Hi folks,
Would it be possible to add 3.2.4 as a new unreleased version in Jira? As you
have probably seen, Even Rouault has made several changes to fix bugs on the
3.2 branch, and it would be useful to release them.
Are there any other needed fixes to go into a new 3.2 point release?
Roger Leigh created XERCESC-2219:
Summary: XMLReader constructor: memory leak when
refreshRawBuffer() throws
Key: XERCESC-2219
URL: https://issues.apache.org/jira/browse/XERCESC-2219
Project: Xerces
Roger Leigh created XERCESC-2218:
Summary: CurlURLInputStream constructor memory leak
Key: XERCESC-2218
URL: https://issues.apache.org/jira/browse/XERCESC-2218
Project: Xerces-C++
Issue Type
Roger Leigh created XERCESC-2217:
Summary: ICUTranscoder::transcodeFrom buffer overflow
Key: XERCESC-2217
URL: https://issues.apache.org/jira/browse/XERCESC-2217
Project: Xerces-C++
Issue
having all the different message loaders presently implemented.
>
> Cheers,
> Robert
>
> --
>
> On 02.01.21 18:02, Roger Leigh wrote:
>> Hi Robert,
>>
>>
>> While the Xerces-C++ codebase notionally supports translation, I’m unaware
>&g
Hi Robert,
While the Xerces-C++ codebase notionally supports translation, I’m unaware of
any translations ever having been publicly submitted or used in the lifetime of
the project to date. So for the conventions indicated in the XML file, which
were likely written many years ago, I wouldn’t
On 17/08/2020 10:22, Michael Behrisch wrote:
Hi,
we are currently using Xerces-C++ on Linux, Windows and MacOS for
parsing XML inputs and validating it against schemas. The schemas (like
https://sumo.dlr.de/xsd/routes_file.xsd) are on a public web server
which enforces https and I have some
Hi Francesco,
To clarify a few points in your message. Xerces-C++ has always been
effectively UTF-16-only. Previously the 16-bit type used to represent
XMLCh was one of several possible types, including char16_t, wchar_t,
uint16_t, unsigned short or unsigned int or possibly others,
I moved all the issues using version 3.3.0 to version 4.0.0.
I don't have Jira admin access, so I can't delete the 3.3.0 release
version, which is no longer in use.
Roger
[
https://issues.apache.org/jira/browse/XERCESC-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2141:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> Enable C++11/14/17 with autoc
[
https://issues.apache.org/jira/browse/XERCESC-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2202:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> Update version of master bra
[
https://issues.apache.org/jira/browse/XERCESC-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2201:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> Update Travis-CI image in
[
https://issues.apache.org/jira/browse/XERCESC-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2200:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> Update AppVeyor image in
[
https://issues.apache.org/jira/browse/XERCESC-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2203:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> MingGW time functions are bro
[
https://issues.apache.org/jira/browse/XERCESC-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2210:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> Rem
[
https://issues.apache.org/jira/browse/XERCESC-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2208:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> Rationalise XercesIntTy
[
https://issues.apache.org/jira/browse/XERCESC-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2205:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> Require std::mutex and std::thr
[
https://issues.apache.org/jira/browse/XERCESC-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2207:
-
Fix Version/s: (was: 3.3.0)
4.0.0
> Rationalise network access
On 19/06/2020 13:44, Boris Kolpackov wrote:
Hi Roger,
Thanks for getting the ball rolling. See my comments below.
Roger Leigh writes:
One of the issues I encountered was difficulty in building on modern
platforms, Windows in particular, which was the impetus for developing
the CMake build
Dear all,
To follow up to the suggestion Boris made in the discussion on
https://issues.apache.org/jira/browse/XERCESC-2204, I would like to
outline a proposal for the development and release of a version 4.0.0 of
Xerces-C. Being a new major version, this would allow co-installation
with
[
https://issues.apache.org/jira/browse/XERCESC-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134809#comment-17134809
]
Roger Leigh commented on XERCESC-2208:
--
Please see open pull request for this change
[
https://issues.apache.org/jira/browse/XERCESC-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2208:
Assignee: Roger Leigh
> Rationalise XercesIntTy
[
https://issues.apache.org/jira/browse/XERCESC-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134558#comment-17134558
]
Roger Leigh commented on XERCESC-2204:
--
Since this is all abstracted via the msgloader interface
[
https://issues.apache.org/jira/browse/XERCESC-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134554#comment-17134554
]
Roger Leigh commented on XERCESC-2200:
--
I'll be able to upgrade the AppVeyor image and enable
[
https://issues.apache.org/jira/browse/XERCESC-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17133691#comment-17133691
]
Roger Leigh commented on XERCESC-2206:
--
There would certainly be no urgency in releasing what's
[
https://issues.apache.org/jira/browse/XERCESC-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh resolved XERCESC-2209.
--
Resolution: Fixed
> Remove HAVE_LSTRING
> ---
>
>
[
https://issues.apache.org/jira/browse/XERCESC-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh resolved XERCESC-2210.
--
Resolution: Fixed
> Remove XERCES_NO_MATCHING_DELETE_OPERA
[
https://issues.apache.org/jira/browse/XERCESC-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132685#comment-17132685
]
Roger Leigh commented on XERCESC-2204:
--
In practice, most distributions providing Xerces-C
[
https://issues.apache.org/jira/browse/XERCESC-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132681#comment-17132681
]
Roger Leigh commented on XERCESC-2200:
--
[~scantor] I also applied a minimal version of this fix
[
https://issues.apache.org/jira/browse/XERCESC-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132650#comment-17132650
]
Roger Leigh commented on XERCESC-2206:
--
I certainly don't want to proceed with anything
[
https://issues.apache.org/jira/browse/XERCESC-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130670#comment-17130670
]
Roger Leigh commented on XERCESC-2206:
--
None of this is intended to cause any *API* break
[
https://issues.apache.org/jira/browse/XERCESC-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130630#comment-17130630
]
Roger Leigh commented on XERCESC-2206:
--
I have deliberately set the version to 3.3 so
Roger Leigh created XERCESC-2210:
Summary: Remove XERCES_NO_MATCHING_DELETE_OPERATOR
Key: XERCESC-2210
URL: https://issues.apache.org/jira/browse/XERCESC-2210
Project: Xerces-C++
Issue Type
Roger Leigh created XERCESC-2209:
Summary: Remove HAVE_LSTRING
Key: XERCESC-2209
URL: https://issues.apache.org/jira/browse/XERCESC-2209
Project: Xerces-C++
Issue Type: Bug
Roger Leigh created XERCESC-2208:
Summary: Rationalise XercesIntTypes
Key: XERCESC-2208
URL: https://issues.apache.org/jira/browse/XERCESC-2208
Project: Xerces-C++
Issue Type: Bug
Roger Leigh created XERCESC-2207:
Summary: Rationalise network accessors
Key: XERCESC-2207
URL: https://issues.apache.org/jira/browse/XERCESC-2207
Project: Xerces-C++
Issue Type: Bug
Roger Leigh created XERCESC-2206:
Summary: Use char16_t and unicode literals to replace various
XMLCh types
Key: XERCESC-2206
URL: https://issues.apache.org/jira/browse/XERCESC-2206
Project: Xerces-C
Roger Leigh created XERCESC-2205:
Summary: Require std::mutex and std::thread
Key: XERCESC-2205
URL: https://issues.apache.org/jira/browse/XERCESC-2205
Project: Xerces-C++
Issue Type: Bug
Roger Leigh created XERCESC-2204:
Summary: Remove message loader
Key: XERCESC-2204
URL: https://issues.apache.org/jira/browse/XERCESC-2204
Project: Xerces-C++
Issue Type: Bug
Roger Leigh created XERCESC-2203:
Summary: MingGW time functions are broken
Key: XERCESC-2203
URL: https://issues.apache.org/jira/browse/XERCESC-2203
Project: Xerces-C++
Issue Type: Bug
[
https://issues.apache.org/jira/browse/XERCESC-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh resolved XERCESC-2201.
--
Resolution: Fixed
> Update Travis-CI image in
[
https://issues.apache.org/jira/browse/XERCESC-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh resolved XERCESC-2141.
--
Resolution: Fixed
> Enable C++11/14/17 with autoconf build and CMake bu
[
https://issues.apache.org/jira/browse/XERCESC-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124275#comment-17124275
]
Roger Leigh commented on XERCESC-2141:
--
In the interim, contemporary compilers are going
[
https://issues.apache.org/jira/browse/XERCESC-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2141:
-
Labels: autoconf build c++11 c++14 c++17 (was: autoconf build c++11 c++14)
> Enable C++11
[
https://issues.apache.org/jira/browse/XERCESC-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2141:
-
Summary: Enable C++11/14/17 with autoconf build and CMake build (was:
Enable C++11/14/17
[
https://issues.apache.org/jira/browse/XERCESC-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2141:
-
Summary: Enable C++11/14/17 with autoconf build (was: Enable C++11/14 with
autoconf build
[
https://issues.apache.org/jira/browse/XERCESC-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XERCESC-2141:
Assignee: Roger Leigh
> Enable C++11/14 with autoconf bu
Roger Leigh created XERCESC-2202:
Summary: Update version of master branch to 3.3.0
Key: XERCESC-2202
URL: https://issues.apache.org/jira/browse/XERCESC-2202
Project: Xerces-C++
Issue Type
Roger Leigh created XERCESC-2201:
Summary: Update Travis-CI image in use
Key: XERCESC-2201
URL: https://issues.apache.org/jira/browse/XERCESC-2201
Project: Xerces-C++
Issue Type: Bug
Roger Leigh created XERCESC-2200:
Summary: Update AppVeyor image in use
Key: XERCESC-2200
URL: https://issues.apache.org/jira/browse/XERCESC-2200
Project: Xerces-C++
Issue Type: Bug
[
https://issues.apache.org/jira/browse/XERCESC-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119784#comment-17119784
]
Roger Leigh commented on XERCESC-2102:
--
[~scantor] You just put the documentation to publish
[
https://issues.apache.org/jira/browse/XERCESC-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17115559#comment-17115559
]
Roger Leigh commented on XERCESC-2102:
--
As a point of reference, I've recently done a full
On 11/04/2020 14:41, Roger Leigh wrote:
On 10/04/2020 17:28, Cantor, Scott wrote:
A patch release of Xerces-C, V3.2.3, is now available. The web site
[1] and download site are refreshed [2] with the relevant links
updated. The list of issues addressed can be found at [3].
Hi Scott,
Does
On Sat, Apr 11, 2020 at 02:41:31PM +0100, Roger Leigh wrote:
On 10/04/2020 17:28, Cantor, Scott wrote:
A patch release of Xerces-C, V3.2.3, is now available. The web site [1] and
download site are refreshed [2] with the relevant links updated. The list of
issues addressed can be found at [3].
Hi
On 10/04/2020 17:28, Cantor, Scott wrote:
A patch release of Xerces-C, V3.2.3, is now available. The web site [1] and
download site are refreshed [2] with the relevant links updated. The list of
issues addressed can be found at [3].
Hi Scott,
Does archive.apache.org also need updating?
On 06/04/2020 13:28, Cantor, Scott wrote:
On 4/6/20, 8:24 AM, "Roger Leigh" wrote:
It should be pretty simple for any Apache contributor to push any
potential update as a feature branch to GitBox and then check the CI run
passes, prior to merging to an integration branch. This w
On 06/04/2020 12:42, Cantor, Scott wrote:
On 4/6/20, 7:21 AM, "Roger Leigh" wrote:
You can simply push your feature branch and wait for the tests to pass before
merging to and pushing the integration
branch.
I'm not sure that there's been adequate discussion of any actual d
Dear all,
CI testing was present prior to the switch from SVN to GitBox, but
needed re-enabling by Infra for the new repository. It's re-enabled
since yesterday (see INFRA-20073), and both the xerces-3.2 and master
branch are passing for both Travis and AppVeyor:
[
https://issues.apache.org/jira/browse/XERCESC-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh resolved XERCESC-2176.
--
Fix Version/s: 3.3.0
Resolution: Fixed
> Incorrect symbolic links created for Li
[
https://issues.apache.org/jira/browse/XERCESC-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073687#comment-17073687
]
Roger Leigh commented on XERCESC-2176:
--
[~brentd] Please could you give one of the PRs a try
[
https://issues.apache.org/jira/browse/XERCESC-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073686#comment-17073686
]
Roger Leigh commented on XERCESC-2176:
--
PRs opened for dev and 3.2: https://github.com/apache
[
https://issues.apache.org/jira/browse/XERCESC-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073671#comment-17073671
]
Roger Leigh commented on XERCESC-2176:
--
The CMake logic we have is buggy, and should only
[
https://issues.apache.org/jira/browse/XERCESC-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073107#comment-17073107
]
Roger Leigh commented on XERCESC-2190:
--
Yes, I was surprised when I went to check on Server 2008
[
https://issues.apache.org/jira/browse/XERCESC-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073098#comment-17073098
]
Roger Leigh commented on XERCESC-2177:
--
As mentioned on XERCESC-2190 I think we would be better
[
https://issues.apache.org/jira/browse/XERCESC-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073003#comment-17073003
]
Roger Leigh commented on XERCESC-2190:
--
I think that as a project we should have a clearly
[
https://issues.apache.org/jira/browse/XERCESC-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072988#comment-17072988
]
Roger Leigh commented on XERCESC-2176:
--
Sorry I've not had time to devote to this yet, I've had
[
https://issues.apache.org/jira/browse/XERCESC-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072987#comment-17072987
]
Roger Leigh commented on XERCESC-2190:
--
I checked both call sites.
WindowsFileMgr.cpp: Used
Hi Scott,
I wanted to check with you what the policy was regarding the requirement
for an Apache CLA for code contributions. Does this apply for the case
of simple and obvious one-liners and other fairly trivial fixes as
opposed to more substantial work which is actually creative?
Are
[
https://issues.apache.org/jira/browse/XERCESC-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052453#comment-17052453
]
Roger Leigh commented on XERCESC-2163:
--
[~candrews] With the switchover of Xerces-C to git
[
https://issues.apache.org/jira/browse/XERCESC-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052450#comment-17052450
]
Roger Leigh commented on XERCESC-2156:
--
The provided patch switches from the CMake FindCURL script
1 - 100 of 365 matches
Mail list logo
