Re: [ANNOUNCE] Commons Parent 38 released

Thank you Sebb! Gary On Wed, Jun 24, 2015 at 9:16 AM, sebb wrote: > Commons Parent 38 has been released. > [It may take a few hours before the artifacts are available from Maven > Central] > > The main reason for this release is to fix the bug in site.xml > discovered recently. > > Changes: > o

Re: [io] xml parser blues :)

That worked like a charm, great stuff. Thanks a lot ! Kristian 2015-06-24 17:46 GMT+02:00 sebb : > I added the following to the surefire configuration section in the pom: > > > > xerces:xercesImpl > > > This worked for me. > > > On 24 June 2015 at 11:57, sebb wrote: > > O

[ANNOUNCE] Commons Parent 38 released

Commons Parent 38 has been released. [It may take a few hours before the artifacts are available from Maven Central] The main reason for this release is to fix the bug in site.xml discovered recently. Changes: o Fix URL for Security link o Update Assembly Plugi

Re: [io] Preparing for 2.5 release

Should update to CP38 now it has been released (will take a few hours to reach Maven Central) Also some plugins: antrun 1.8 checkstyle 2.15 findbugs 3.0.1 (commons.findbugs.version) On 23 June 2015 at 17:49, Kristian Rosenvold wrote: > My personal itch list is getting very short, and includes

[RESULT] [VOTE] (lazy consensus) Commons Parent 38 from RC2

72 hours have elapsed with no objections, so the lazy vote is deemed to have passed. On 21 June 2015 at 16:10, sebb wrote: > Hello All, > > The Apache Commons Parent POM provides common settings for all Apache > Commons components. > > > This is a VOTE to release Commons Parent 38 from RC2. > >

Re: [io] xml parser blues :)

I added the following to the surefire configuration section in the pom: xerces:xercesImpl This worked for me. On 24 June 2015 at 11:57, sebb wrote: > On 24 June 2015 at 11:09, Kristian Rosenvold wrote: >> (sorry, wrong keyboard shortcut) >> >> Invalid encodi

Re: [SCXML] Mirror or move to git?

Sorry for late response. I personally prefer moving from svn to git rather than just mirroring. I assume we can take advantage of the full features of git (e.g, easier branching and merging) better with that approach. What do others think? Regards, Woonsan On 5/5/15 3:27 PM, Benedikt Ritter wrot

Re: [io] xml parser blues :)

On 24 June 2015 at 11:09, Kristian Rosenvold wrote: > (sorry, wrong keyboard shortcut) > > Invalid encoding name "UTF_32BE". > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 42; Invalid > encoding name "UTF_32BE". > at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) > at org

Re: [io] xml parser blues :)

(sorry, wrong keyboard shortcut) Invalid encoding name "UTF_32BE". org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 42; Invalid encoding name "UTF_32BE". at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at o

[io] xml parser blues :)

BOMInputStreamTest#testReadXmlWithoutBOMUtf32Be and 3 others fail in "site" generation but not regular unit tests. I have identified that the problem is happening because xercesImpl/2.4.0/xercesImpl-2.4.0.jar is creeping in during site build With regular unit tests it picks up rt.jar!/com/sun/org

Re: [io] How picky about backward compatibility ?

Kristian Rosenvold wrote: > 2015-06-23 18:08 GMT+02:00 sebb : > >> On 23 June 2015 at 08:54, Kristian Rosenvold >> wrote: >> > I think I'll go for the release-notes approach; given that we can find >> > an appropriate technical solution. >> > >> > Right now I'm leaning towards simply changing th