date:20161021

[GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

2016-10-21 Thread Gump [HEAD] :-(

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at gene...@gump.apache.org.

Project ooxml-schemas has an issue affecting its community integration.
This issue affects 5 projects.
The current state of this project is 'Failed', with reason 'Build Timed Out'.
For reference only, the following projects are affected by this:
- ooxml-schemas :  POI
- org.apache.poi :  POI
- poi :  POI
- poi-ooxml-schemas :  POI
- poi-test :  POI


Full details are available at:
http://vmgump.apache.org/gump/public/poi/ooxml-schemas/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole jar output [ooxml-schemas-[0-9]*[0-9T].jar] identifier set to 
project name
 -INFO- Failed with reason build timed out
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/poi/ooxml-schemas/gump_work/build_poi_ooxml-schemas.html
Work Name: build_poi_ooxml-schemas (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 hour 3 secs
Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only -Dant.build.clonevm=true org.apache.tools.ant.Main 
-Dgump.merge=/srv/gump/public/gump/work/merge.xml compile-ooxml-xsds 
[Working Directory: /srv/gump/public/workspace/poi]
CLASSPATH: 
/usr/lib/jvm/java-8-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/poi/ooxml-lib/curvesapi-1.04.jar:/srv/gump/public/workspace/poi/ooxml-lib/xmlbeans-2.6.0.jar.orig:/srv/gump/public/workspace/poi/compile-lib/bcpkix-jdk15on-1.54.jar:/srv/gump/public/workspace/poi/compile-lib/bcprov-ext-jdk15on-1.54.jar:/srv/gump/public/workspace/poi/compile-lib/slf4j-api-1.7.12.jar
-
Buildfile: /srv/gump/public/workspace/poi/build.xml

check-jars:

fetch-jars:

check-ooxml-jars:

fetch-ooxml-jars:

init:
 [echo] Using Ant: Apache Ant(TM) version 1.10.0alpha compiled on October 
22 2016 from ${ant.home}, Ant detected Java 1.8 (may be different than actual 
Java sometimes...)
 [echo] Using Java: 1.8.0_60/1.8.0_60-b27/25.60-b23/Java HotSpot(TM) 64-Bit 
Server VM from Oracle Corporation on Linux: 3.13.0-66-generic
 [echo] Using Findbugs: 3.0.1 for Java 1.8.0_60

check-ooxml-xsds:

fetch-ooxml-xsds:
  [get] Getting: 
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%201st%20edition%20Part%204%20(PDF).zip
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip
  [get] Getting: 
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%201st%20edition%20Part%202%20(PDF).zip
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part2.zip
  [get] Getting: 
https://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/xmldsig-core-schema.xsd
  [get] Getting: http://uri.etsi.org/01903/v1.3.2/XAdES.xsd
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/XAdES.xsd
  [get] Getting: http://uri.etsi.org/01903/v1.4.1/XAdESv141.xsd
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/XAdESv141.xsd
[unzip] Expanding: 
/srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip into 
/srv/gump/public/workspace/poi/ooxml-lib
[unzip] Expanding: 
/srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part2.zip into 
/srv/gump/public/workspace/poi/ooxml-lib
[unzip] Expanding: 
/srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip into 
/srv/gump/public/workspace/poi/ooxml-lib

check-compiled-ooxml-xsds:

compile-ooxml-xsds:
[mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-xsds
[mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-sources
[mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-classes
 [copy] Copying 2 files to /srv/gump/public/workspace/poi/build/xmlbean-xsds
 [copy] Copying 87 resources to 
/srv/gump/public/workspace/poi/build/xmlbean-xsds
  [xmlbean] Time to build schema type system: 5.577 seconds
  [xmlbean] Time to generate code: 9.966 seconds
 [copy] Copying 7 files to 
/srv/gump/public/workspace/poi/build/xmlbean-sources
[javac] Compiling 4575 source fil

Fwd: Re: Build failed in Jenkins: POI #1599

2016-10-21 Thread Javen O'Neal

Fyi
-- Forwarded message --
From: "Pono Takamori" 
Date: Oct 21, 2016 13:06
Subject: Re: Build failed in Jenkins: POI #1599
To: , 
Cc:

I've grown the disk, thanks for letting us know about the problem.

Cheers,
-Pono

On Fri, Oct 21, 2016 at 8:25 AM, Javen O'Neal  wrote:
> FYI, this job failed due to running out of disk space on ubuntu-eu2.
> https://builds.apache.org/job/POI/1599/
> Caused by: org.tmatesoft.svn.core.SVNException: svn: E204899: No space
> left on device.
>
> Let us know if there's anything we should do to our builds to save on
> disk space, such as clearing old temp files or clearing old build
> artifacts.
>
> Thanks
> Javen on behalf of Apache POI
>
> -- Forwarded message --
> From: Apache Jenkins Server 
> Date: Fri, Oct 21, 2016 at 5:35 AM
> Subject: Build failed in Jenkins: POI #1599
> To: dev@poi.apache.org
>
>
> See 
>
> --
> [...truncated 98 lines...]
> at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.
doReport(DAVConnection.java:360)
> at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.
runReport(DAVRepository.java:1340)
> at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.
update(DAVRepository.java:868)
> at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.
updateInternal(SvnNgAbstractUpdate.java:247)
> at org.tmatesoft.svn.core.internal.wc2.ng.
SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:111)
> at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.
run(SvnNgUpdate.java:38)
> at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.
run(SvnNgUpdate.java:18)
> at org.tmatesoft.svn.core.internal.wc2.ng.
SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
> at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(
SvnOperationRunner.java:21)
> at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(
SvnOperationFactory.java:1235)
> at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.
java:294)
> at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(
SVNUpdateClient.java:311)
> at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(
SVNUpdateClient.java:291)
> at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(
SVNUpdateClient.java:387)
> at hudson.scm.subversion.UpdateUpdater$TaskImpl.
perform(UpdateUpdater.java:158)
> ... 13 more
> Retrying after 10 seconds
> Updating http://svn.apache.org/repos/asf/poi/trunk at revision
> '2016-10-21T12:34:11.560 +'
> ERROR: Failed to update http://svn.apache.org/repos/asf/poi/trunk
> org.tmatesoft.svn.core.SVNException: svn: E204899: No space left on device
> at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.
error(SVNErrorManager.java:64)
> at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.
error(SVNErrorManager.java:51)
> at org.tmatesoft.svn.core.internal.io.dav.http.
HTTPConnection.request(HTTPConnection.java:793)
> at org.tmatesoft.svn.core.internal.io.dav.http.
HTTPConnection.request(HTTPConnection.java:398)
> at org.tmatesoft.svn.core.internal.io.dav.http.
HTTPConnection.request(HTTPConnection.java:386)
> at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.
performHttpRequest(DAVConnection.java:863)
> at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.
doReport(DAVConnection.java:360)
> at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.
runReport(DAVRepository.java:1340)
> at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.
update(DAVRepository.java:868)
> at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.
updateInternal(SvnNgAbstractUpdate.java:247)
> at org.tmatesoft.svn.core.internal.wc2.ng.
SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:111)
> at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.
run(SvnNgUpdate.java:38)
> at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.
run(SvnNgUpdate.java:18)
> at org.tmatesoft.svn.core.internal.wc2.ng.
SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
> at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(
SvnOperationRunner.java:21)
> at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(
SvnOperationFactory.java:1235)
> at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.
java:294)
> at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(
SVNUpdateClient.java:311)
> at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(
SVNUpdateClient.java:291)
> at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(
SVNUpdateClient.java:387)
> at hudson.scm.subversion.UpdateUpdater$TaskImpl.
perform(UpdateUpdater.java:158)
> at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.
delegateTo(WorkspaceUpdater.java:162)
> at hudson.scm.SubversionSCM$CheckOutTask.perform(
Subve

Re: Functionality injection technique for XWPF

2016-10-21 Thread Dominik Stadler

Thanks for showing bits, that makes it easier to start a discussion!

So what you are trying to handle are different CT_... classes which have
very similar content and thus would require repeated code otherwise.

I see the following options in general for handling something like that:

1. Reflection to access similar classes in one way
2. Generate a small additional layer of code that encapsulates this
duplication
3. Use XmlBeans to "Weave-in" some additional interfaces into the CT_...
classes to handle this
4. Use a separate 3rd party functionality to "weave-in" or add aspects.

Personally I would prefer 2. over 1. because it keeps the code easier to
debug. You could maybe even automatically detect similar things
automatically and create the code accordingly.

Idea number 4 would add a complex dependency that likely has it's own set
of problems, for 3. I am not sure if feasible, could be nice if XmlBeans
supports it

Another point to consider is that reflection can have quite a performance
penalty, so as soon as it is involved in calls that are done a lot, you
will be limited pretty soon when handling larger documents (I am not sure
what use an Excel file with 1 mio rows or a Word document with thousands of
pages is, but somehow our users want to do it all the time).

Dominik.

On Fri, Oct 21, 2016 at 1:17 PM, Murphy, Mark 
wrote:

> Take a look at this commit, it shows what I am talking about. There is
> still a lot more to do, but I don't want to go too far down a path that
> will be incorrect. The classes XMLContent and XMLMarkup are delegates that
> provide common functionality to XWPFDocument, and XWPFHeaderFooter,
> XWPFTableCell, XWPFComment, XWPFFootnotes, etc. There is still a little
> overlap between XWPFDocument and XMLContent since I haven't fully added all
> the necessary parts to XMLContent yet, but eventually, the paragraphs,
> tables, and bodyElements properties in XWPFDocuments would be migrated
> fully to XMLContent, and the only methods implemented in XWPFDocument would
> be code that is specific to the Document part, for example Section code,
> though I think that might end up with its own class as well.
>
> I have run this through the unit tests, and there are some bugs in it
> which I am in the process of correcting locally, but this gives a decent
> overview of what I am thinking of. Once this is complete, we would be able
> to fix bugs in paragraph, or Table code in a single location.
>
> I still am unsure about what to do with the Exceptions that this throws. I
> think they should be handled as close to the source as possible, but what
> logging exists to handle this, and how would you notify the user that an
> issue exists.
>
> Here is a link to the commit in my GitHub repository.
>
> https://github.com/apache/poi/commit/3bc9cf77fd690132257f9524ebc95d
> b3ec7bde03
>
> -Original Message-
> From: Nick Burch [mailto:apa...@gagravarr.org]
> Sent: Monday, October 17, 2016 2:51 AM
> To: POI Developers List 
> Subject: Re: Functionality injection technique for XWPF
>
> On Mon, 17 Oct 2016, Mark Murphy wrote:
> > I found I should be able to do it using reflection to avoid long
> > strings of instanceof conditions which is really the same as
> > duplicating the code, but all inside one class. Any issue with using
> Reflection?
>
> If you post some of the code you're working on, with some ideas, we can
> hopefully all take a look and see if we can help improve things
>
> Feel free to post to a github gist, a branch on your own github, a branch
> in svn, patch to jira etc!
>
> (Quite a bit of XWPF has come from user contributions, so may well be
> missing some overall architecture improvements that piece-meal fixes didn't
> require)
>
> Nick
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional
> commands, e-mail: dev-h...@poi.apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

Jenkins build is back to normal : POI #1601

2016-10-21 Thread Apache Jenkins Server

See 


-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Jenkins build is back to normal : POI-JDK8 #1301

2016-10-21 Thread Apache Jenkins Server

See 


-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60289] UTF decoding in XSSFRichTextString does not work when the code is lowercase

2016-10-21 Thread bugzilla

https://bz.apache.org/bugzilla/show_bug.cgi?id=60289

Dominik Stadler  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
   Keywords||PatchAvailable
 Resolution|--- |FIXED

--- Comment #2 from Dominik Stadler  ---
Applied in r1766065, thanks for the patch, this will be included in 3.16-beta1.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60294] New: Add "unknown" ShapeType for 4095

2016-10-21 Thread bugzilla

https://bz.apache.org/bugzilla/show_bug.cgi?id=60294

Bug ID: 60294
   Summary: Add "unknown" ShapeType for 4095
   Product: POI
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P2
 Component: HSLF
  Assignee: dev@poi.apache.org
  Reporter: talli...@mitre.org

On TIKA-2129, Seva Alekseyev shared a file that throws:

java.lang.IllegalArgumentException: Unknown shape type: 4095
at org.apache.poi.sl.usermodel.ShapeType.forId(ShapeType.java:314)
at
org.apache.poi.hslf.usermodel.HSLFShapeFactory.createSimpleShape(HSLFShapeFactory.java:98)
at
org.apache.poi.hslf.usermodel.HSLFShapeFactory.createShape(HSLFShapeFactory.java:62)
at org.apache.poi.hslf.usermodel.HSLFSheet.getShapes(HSLFSheet.java:173)
at org.apache.tika.parser.microsoft.HSLFExtractor.parse(HSLFExtractor.java:93)
at org.apache.tika.parser.microsoft.OfficeParser.parse(OfficeParser.java:149)
at org.apache.tika.parser.microsoft.OfficeParser.parse(OfficeParser.java:117)

When I save the file as pptx, the shape is called "AutoShape". According to one
vendor of MSOffice processing tools, 4095 is a recognized code for 'Unknown'.

Any objections to adding this to ShapeType?

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

2016-10-21 Thread Stefan Bodewig

Hi Dominik

On 2016-10-20, Dominik Stadler wrote:

> Since some time one of the steps in the POI builds inside Gump is failing,
> see below. We think it is related to the 1 hour timeout that is applied by
> default.

Yes, looks that way.

> The step compiles a big number of files, but finishes in a few minutes
> usually. Our builds on the Apache Jenkins instance usually take up to 40
> minutes for the complete build which includes a number of additional steps,
> so we are not sure why it is taking so long here, maybe the machine is
> quite limited on memory/CPU?

Yes, vmgump is a pretty limited. We are in the process of replacing it,
but it may take a while until we get there.

> Is there a simple way to try to increase the timeout for this specific
> build?

This is not implemented, although most of the infrastructure would be
there.

In case anybody with some working Python knowledge can spare a bit of
time: https://svn.apache.org/repos/asf/gump/live/ holds the code.

All builders create an instance of gump.util.process.Cmd and the timeout
value could be configured via a constructor arg. For POI it would be
enough to add an optional timeout property to
gump.core.model.builder.Ant (likely Builder would be the better place)
and use that from gump.core.build.Ant.getAntCommand - the builder
instance is project.ant.

I'm not sure how quick I'd be able to make the changes myself, I'm
switching between a couple of tasks (including the new VM for gump)
right now.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60293] New: Handling illegal "Odd" footer in XWPF

2016-10-21 Thread bugzilla

https://bz.apache.org/bugzilla/show_bug.cgi?id=60293

Bug ID: 60293
   Summary: Handling illegal "Odd" footer in XWPF
   Product: POI
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P2
 Component: XWPF
  Assignee: dev@poi.apache.org
  Reporter: talli...@mitre.org

On TIKA-2125, Seva Alekseyev provided a document that contains "odd" as the
footer type.

According to ECMA[1] (labeled-page 727, pdf-page 737), there can be three types
of footers: first, odd and even.  However, the way to encode those is "first"
"default" "even", and the xsd makes this clear.

   … 
  …  
The 

So the file submitted on TIKA-2125 is out of compliance.

Do we want to add special handling to convert "odd" to "default"?


[1]
http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-376,%20Fourth%20Edition,%20Part%201%20-%20Fundamentals%20And%20Markup%20Language%20Reference.zip

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Build failed in Jenkins: POI #1600

2016-10-21 Thread Apache Jenkins Server

See 

--
[...truncated 332 lines...]
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:868)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:247)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:111)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:38)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:158)
... 13 more
Caused by: org.tmatesoft.sqljet.core.SqlJetException: FULL: error code is FULL
at 
org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.openJournal(SqlJetPager.java:3051)
at 
org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.begin(SqlJetPager.java:2782)
at 
org.tmatesoft.sqljet.core.internal.btree.SqlJetBtree.beginTrans(SqlJetBtree.java:931)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.doBeginTransaction(SqlJetEngine.java:561)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.access$100(SqlJetEngine.java:55)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$12.runSynchronized(SqlJetEngine.java:535)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runEngineTransaction(SqlJetEngine.java:529)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runTransaction(SqlJetDb.java:238)
at 
org.tmatesoft.sqljet.core.table.SqlJetDb.runWriteTransaction(SqlJetDb.java:211)
at 
org.tmatesoft.svn.core.internal.wc17.db.statement.SVNWCDbCreateSchema.exec(SVNWCDbCreateSchema.java:225)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetStatement.done(SVNSqlJetStatement.java:420)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb$BumpRevisionPostUpdate.bumpMovedAway(SVNWCDb.java:5215)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb$BumpRevisionPostUpdate.transaction(SVNWCDb.java:5208)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:258)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.runTransaction(SVNSqlJetDb.java:252)
at 
org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.opBumpRevisionPostUpdate(SVNWCDb.java:5160)
at 
org.tmatesoft.svn.core.internal.wc17.SVNUpdateEditor17.closeEdit(SVNUpdateEditor17.java:1728)
at 
org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeEdit(SVNCancellableEditor.java:148)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.endElement(DAVEditorHandler.java:492)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:103)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1781)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2957)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at 
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:117)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
at 
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readDat

Fwd: Build failed in Jenkins: POI #1599

2016-10-21 Thread Javen O'Neal

FYI, this job failed due to running out of disk space on ubuntu-eu2.
https://builds.apache.org/job/POI/1599/
Caused by: org.tmatesoft.svn.core.SVNException: svn: E204899: No space
left on device.

Let us know if there's anything we should do to our builds to save on
disk space, such as clearing old temp files or clearing old build
artifacts.

Thanks
Javen on behalf of Apache POI

-- Forwarded message --
From: Apache Jenkins Server 
Date: Fri, Oct 21, 2016 at 5:35 AM
Subject: Build failed in Jenkins: POI #1599
To: dev@poi.apache.org


See 

--
[...truncated 98 lines...]
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:360)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1340)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:868)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:247)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:111)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:38)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:158)
... 13 more
Retrying after 10 seconds
Updating http://svn.apache.org/repos/asf/poi/trunk at revision
'2016-10-21T12:34:11.560 +'
ERROR: Failed to update http://svn.apache.org/repos/asf/poi/trunk
org.tmatesoft.svn.core.SVNException: svn: E204899: No space left on device
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:793)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:398)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:863)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:360)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1340)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:868)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:247)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:111)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:38)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:158)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:996)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Reque

Build failed in Jenkins: POI-JDK8 #1300

2016-10-21 Thread Apache Jenkins Server

See 

--
[...truncated 159 lines...]
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:996)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.tmatesoft.sqljet.core.SqlJetException: FULL: error code is FULL
at 
org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.openJournal(SqlJetPager.java:3051)
at 
org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.begin(SqlJetPager.java:2782)
at 
org.tmatesoft.sqljet.core.internal.btree.SqlJetBtree.beginTrans(SqlJetBtree.java:931)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.doBeginTransaction(SqlJetEngine.java:561)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.access$100(SqlJetEngine.java:55)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine$9.runSynchronized(SqlJetEngine.java:475)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.runSynchronized(SqlJetEngine.java:217)
at 
org.tmatesoft.sqljet.core.table.engine.SqlJetEngine.beginTransaction(SqlJetEngine.java:471)
at 
org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.beginTransaction(SVNSqlJetDb.java:206)
... 28 more
ERROR: Subversion update failed
java.io.IOException: remote file operation failed: 
 at 
hudson.remoting.Channel@58e865bc:ubuntu-eu2: java.io.IOException
at hudson.FilePath.act(FilePath.java:1014)
at hudson.FilePath.act(FilePath.java:996)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: java.io.IOException
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:212)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:996)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to ubuntu-eu2(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at hudson.FilePath.act(FilePath.java:1007)
... 12 more
Caused by: hudson.scm.subversion.UpdaterException: failed to perform svn update
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:212)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)
at hudson.scm.SubversionSCM$Ch

[GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

2016-10-21 Thread Gump [HEAD] :-(

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at gene...@gump.apache.org.

Project ooxml-schemas has an issue affecting its community integration.
This issue affects 5 projects.
The current state of this project is 'Failed', with reason 'Build Timed Out'.
For reference only, the following projects are affected by this:
- ooxml-schemas :  POI
- org.apache.poi :  POI
- poi :  POI
- poi-ooxml-schemas :  POI
- poi-test :  POI


Full details are available at:
http://vmgump.apache.org/gump/public/poi/ooxml-schemas/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole jar output [ooxml-schemas-[0-9]*[0-9T].jar] identifier set to 
project name
 -INFO- Failed with reason build timed out
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/poi/ooxml-schemas/gump_work/build_poi_ooxml-schemas.html
Work Name: build_poi_ooxml-schemas (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 hour 6 secs
Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only -Dant.build.clonevm=true org.apache.tools.ant.Main 
-Dgump.merge=/srv/gump/public/gump/work/merge.xml compile-ooxml-xsds 
[Working Directory: /srv/gump/public/workspace/poi]
CLASSPATH: 
/usr/lib/jvm/java-8-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/poi/ooxml-lib/curvesapi-1.04.jar:/srv/gump/public/workspace/poi/ooxml-lib/xmlbeans-2.6.0.jar.orig:/srv/gump/public/workspace/poi/compile-lib/bcpkix-jdk15on-1.54.jar:/srv/gump/public/workspace/poi/compile-lib/bcprov-ext-jdk15on-1.54.jar:/srv/gump/public/workspace/poi/compile-lib/slf4j-api-1.7.12.jar
-
Buildfile: /srv/gump/public/workspace/poi/build.xml

check-jars:

fetch-jars:

check-ooxml-jars:

fetch-ooxml-jars:

init:
 [echo] Using Ant: Apache Ant(TM) version 1.10.0alpha compiled on October 
21 2016 from ${ant.home}, Ant detected Java 1.8 (may be different than actual 
Java sometimes...)
 [echo] Using Java: 1.8.0_60/1.8.0_60-b27/25.60-b23/Java HotSpot(TM) 64-Bit 
Server VM from Oracle Corporation on Linux: 3.13.0-66-generic
 [echo] Using Findbugs: 3.0.1 for Java 1.8.0_60

check-ooxml-xsds:

fetch-ooxml-xsds:
  [get] Getting: 
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%201st%20edition%20Part%204%20(PDF).zip
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip
  [get] Getting: 
http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%201st%20edition%20Part%202%20(PDF).zip
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part2.zip
  [get] Getting: 
https://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/xmldsig-core-schema.xsd
  [get] Getting: http://uri.etsi.org/01903/v1.3.2/XAdES.xsd
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/XAdES.xsd
  [get] Getting: http://uri.etsi.org/01903/v1.4.1/XAdESv141.xsd
  [get] To: /srv/gump/public/workspace/poi/ooxml-lib/XAdESv141.xsd
[unzip] Expanding: 
/srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip into 
/srv/gump/public/workspace/poi/ooxml-lib
[unzip] Expanding: 
/srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part2.zip into 
/srv/gump/public/workspace/poi/ooxml-lib
[unzip] Expanding: 
/srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip into 
/srv/gump/public/workspace/poi/ooxml-lib

check-compiled-ooxml-xsds:

compile-ooxml-xsds:
[mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-xsds
[mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-sources
[mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-classes
 [copy] Copying 2 files to /srv/gump/public/workspace/poi/build/xmlbean-xsds
 [copy] Copying 87 resources to 
/srv/gump/public/workspace/poi/build/xmlbean-xsds
  [xmlbean] Time to build schema type system: 5.94 seconds
  [xmlbean] Time to generate code: 11.863 seconds
 [copy] Copying 7 files to 
/srv/gump/public/workspace/poi/build/xmlbean-sources
[javac] Compiling 4575 source files to

Jenkins build is back to normal : POI-OpenJDK #246

2016-10-21 Thread Apache Jenkins Server

See 


-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Build failed in Jenkins: POI #1599

2016-10-21 Thread Apache Jenkins Server

See 

--
[...truncated 98 lines...]
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:360)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1340)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:868)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:247)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:111)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:38)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:158)
... 13 more
Retrying after 10 seconds
Updating http://svn.apache.org/repos/asf/poi/trunk at revision 
'2016-10-21T12:34:11.560 +'
ERROR: Failed to update http://svn.apache.org/repos/asf/poi/trunk
org.tmatesoft.svn.core.SVNException: svn: E204899: No space left on device
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:793)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:398)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:863)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:360)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1340)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:868)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:247)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:111)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:38)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at 
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:158)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:996)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
ERROR: Subversion update failed
java.io.IOException: remote file operation failed: 
 at

[Bug 60289] UTF decoding in XSSFRichTextString does not work when the code is lowercase

2016-10-21 Thread bugzilla

https://bz.apache.org/bugzilla/show_bug.cgi?id=60289

Daniel Gonzalez  changed:

   What|Removed |Added

Summary|UTF decoding|UTF decoding in
   |XSSFRichTextString does not |XSSFRichTextString does not
   |work when the code is   |work when the code is
   |lowercase   |lowercase

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60289] UTF decoding XSSFRichTextString does not work when the code is lowercase

2016-10-21 Thread bugzilla

https://bz.apache.org/bugzilla/show_bug.cgi?id=60289

--- Comment #1 from dgon...@gmail.com  ---
Created attachment 34398
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34398&action=edit
Patch that fixes the bug

We created a trivial patch changing the regular expression on
XSSFRichTextString to accept lowercase hex values. I attached it in case it
could be useful.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60289] New: UTF decoding XSSFRichTextString does not work when the code is lowercase

2016-10-21 Thread bugzilla

https://bz.apache.org/bugzilla/show_bug.cgi?id=60289

Bug ID: 60289
   Summary: UTF decoding XSSFRichTextString does not work when the
code is lowercase
   Product: POI
   Version: 3.15-FINAL
  Hardware: PC
OS: All
Status: NEW
  Severity: trivial
  Priority: P2
 Component: XSSF
  Assignee: dev@poi.apache.org
  Reporter: dgon...@gmail.com

Created attachment 34397
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34397&action=edit
Microsoft Access Database to reproduce the bug

Hi,

The class XSSFRichTextString decodes the UTF strings that OOXML format stores
in the XML that it generates, this works as expected when the file is generated
from Excel as it generates the code with an uupercase hex value, eg: _x000D_
will get translated to /r. 

But I have found that when you export from Microsoft Access 2010 (I haven't
tested in newer versions) through a Visual Basic macro using the method
DoCmd.TransferSpreadsheet
(https://msdn.microsoft.com/en-us/library/office/ff844793.aspx) with the type
acSpreadsheetTypeExcel12Xml to export to OOXML it generates the UTF characters
with the values in lowercase, eg: _x000d_ wich are not matched by the regular
expression used in XSSFRichTextString and thus get passed to the value
unmodified.

That's not a problem if the value is stored back to an xslx file, as Excel
understand it and decodes the character, but in my case we copy this value to a
CSV file which causes the code _x000d_ to be transferred to the text file and
not the expected /r. Similar results can be seen if you output the
XSSFRichTextString value to a log.

Attached is a simple Access Database with one table that has one rich text
field that contains the character /r and a Visual Basic module that exports the
contents of the tables to Excel, I have also included the Excel that results
from executing the macro.

Regards,
Daniel.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

RE: Functionality injection technique for XWPF

2016-10-21 Thread Murphy, Mark

Take a look at this commit, it shows what I am talking about. There is still a 
lot more to do, but I don't want to go too far down a path that will be 
incorrect. The classes XMLContent and XMLMarkup are delegates that provide 
common functionality to XWPFDocument, and XWPFHeaderFooter, XWPFTableCell, 
XWPFComment, XWPFFootnotes, etc. There is still a little overlap between 
XWPFDocument and XMLContent since I haven't fully added all the necessary parts 
to XMLContent yet, but eventually, the paragraphs, tables, and bodyElements 
properties in XWPFDocuments would be migrated fully to XMLContent, and the only 
methods implemented in XWPFDocument would be code that is specific to the 
Document part, for example Section code, though I think that might end up with 
its own class as well.

I have run this through the unit tests, and there are some bugs in it which I 
am in the process of correcting locally, but this gives a decent overview of 
what I am thinking of. Once this is complete, we would be able to fix bugs in 
paragraph, or Table code in a single location.

I still am unsure about what to do with the Exceptions that this throws. I 
think they should be handled as close to the source as possible, but what 
logging exists to handle this, and how would you notify the user that an issue 
exists.

Here is a link to the commit in my GitHub repository. 

https://github.com/apache/poi/commit/3bc9cf77fd690132257f9524ebc95db3ec7bde03

-Original Message-
From: Nick Burch [mailto:apa...@gagravarr.org] 
Sent: Monday, October 17, 2016 2:51 AM
To: POI Developers List 
Subject: Re: Functionality injection technique for XWPF

On Mon, 17 Oct 2016, Mark Murphy wrote:
> I found I should be able to do it using reflection to avoid long 
> strings of instanceof conditions which is really the same as 
> duplicating the code, but all inside one class. Any issue with using 
> Reflection?

If you post some of the code you're working on, with some ideas, we can 
hopefully all take a look and see if we can help improve things

Feel free to post to a github gist, a branch on your own github, a branch in 
svn, patch to jira etc!

(Quite a bit of XWPF has come from user contributions, so may well be missing 
some overall architecture improvements that piece-meal fixes didn't require)

Nick

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, 
e-mail: dev-h...@poi.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60219] [PATCH] FormulaParser can't parse external references when sheet name is quoted

2016-10-21 Thread bugzilla

https://bz.apache.org/bugzilla/show_bug.cgi?id=60219

IgnacioHR  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #9 from IgnacioHR  ---
Patch 34357 should be OK to fix this bug and does not modify the signature of
Workbook interface. I propose you incorporate patch 34357 to current version
and close this bug

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Re: Apache POI 3.15 released

2016-10-21 Thread Dominik Stadler

Hi,

thanks for this work, I think having the notable-change-items also in the
status.xml is a good thing because it is easier to remember what changes
did happen at the time the changelog is updated compared to when the
release is prepared later by one dev who might not be aware that somebody
else did build something a while back.

Dominik.

On Fri, Oct 21, 2016 at 12:23 PM, Javen O'Neal  wrote:

> I added the major changes from the 3.15 release notes [1] to the
> detailed changelog [2] in r1765977 [3].
>
> [1] https://www.apache.org/dyn/closer.lua/poi/release/RELEASE-NOTES.txt
> [2] https://poi.apache.org/changes.html
> [3] https://svn.apache.org/viewvc?view=revision&revision=1765977
>
> We could choose to update the changelog with the major changes when we
> announce a release, create the "RELEASE-NOTES-.txt" as Nick
> suggested, or both.
> If we decide that it's a headache maintaining the major changes in two
> locations and prefer going with "RELEASE-NOTES-.txt", then
> we can revert the changes I made to status.xml
>
> In the meantime, what's the best way to retrieve old release notes?
> Were they committed to a private or public SVN server? If not, we can
> dig through the dev@ email archive for the [VOTE] email, but this
> would take longer to extract.
>
> On Thu, Sep 29, 2016 at 3:08 PM, Nick Burch  wrote:
> > On 29/09/16 15:29, Javen O'Neal wrote:
> >>
> >> Do we archive the release notes somewhere so that someone can read a
> >> high-level summary of the changes for each release? Digging through
> >> the dev@ email list archive to find the release notes draft or
> >> searching a web archiver of one of the mirrors at a date in the past
> >> seem suboptimal. There is no release notes file in the subversion tag
> >> or a page on our site that summarizes the changes in a release more
> >> concisely than changes.html.
> >>
> >> The current https://poi.apache.org links to both 3.14 and 3.15, but we
> >> overwrote the 3.14 release notes on
> >> https://www.apache.org/dyn/closer.lua/poi/release/RELEASE-NOTES.txt
> >> and all mirrors when we released 3.15.
> >
> >
> > After a final release, the homepage and download page should only ever
> link
> > to the most current final version. No other versions should live on the
> dist
> > area, otherwise infra get grumpy...
> >
> > When we do an alpha or beta release, then homepage + download should
> link to
> > both
> >
> > If we don't already, it might be good to deploy the release notes twice,
> > once as "RELEASE-NOTES.txt" (overwritten often), once as
> > "RELEASE-NOTES-.txt". The latter would then always be
> available
> > from archive.apache.org even after a newer final release. Thoughts?
> >
> > Nick
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> > For additional commands, e-mail: dev-h...@poi.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

Re: Apache POI 3.15 released

2016-10-21 Thread Nick Burch


On Fri, 21 Oct 2016, Javen O'Neal wrote:

In the meantime, what's the best way to retrieve old release notes?
Were they committed to a private or public SVN server?


We've been using svnpubsub for dist for a while (2011 IIRC), so you ought 
to be able to get them from there by asking SVN for the release notes file 
at older revision numbers


(Shout if you can't do that easily, and I can try to script something up)

Nick

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Re: Apache POI 3.15 released

2016-10-21 Thread Javen O'Neal

I added the major changes from the 3.15 release notes [1] to the
detailed changelog [2] in r1765977 [3].

[1] https://www.apache.org/dyn/closer.lua/poi/release/RELEASE-NOTES.txt
[2] https://poi.apache.org/changes.html
[3] https://svn.apache.org/viewvc?view=revision&revision=1765977

We could choose to update the changelog with the major changes when we
announce a release, create the "RELEASE-NOTES-.txt" as Nick
suggested, or both.
If we decide that it's a headache maintaining the major changes in two
locations and prefer going with "RELEASE-NOTES-.txt", then
we can revert the changes I made to status.xml

In the meantime, what's the best way to retrieve old release notes?
Were they committed to a private or public SVN server? If not, we can
dig through the dev@ email archive for the [VOTE] email, but this
would take longer to extract.

On Thu, Sep 29, 2016 at 3:08 PM, Nick Burch  wrote:
> On 29/09/16 15:29, Javen O'Neal wrote:
>>
>> Do we archive the release notes somewhere so that someone can read a
>> high-level summary of the changes for each release? Digging through
>> the dev@ email list archive to find the release notes draft or
>> searching a web archiver of one of the mirrors at a date in the past
>> seem suboptimal. There is no release notes file in the subversion tag
>> or a page on our site that summarizes the changes in a release more
>> concisely than changes.html.
>>
>> The current https://poi.apache.org links to both 3.14 and 3.15, but we
>> overwrote the 3.14 release notes on
>> https://www.apache.org/dyn/closer.lua/poi/release/RELEASE-NOTES.txt
>> and all mirrors when we released 3.15.
>
>
> After a final release, the homepage and download page should only ever link
> to the most current final version. No other versions should live on the dist
> area, otherwise infra get grumpy...
>
> When we do an alpha or beta release, then homepage + download should link to
> both
>
> If we don't already, it might be good to deploy the release notes twice,
> once as "RELEASE-NOTES.txt" (overwritten often), once as
> "RELEASE-NOTES-.txt". The latter would then always be available
> from archive.apache.org even after a newer final release. Thoughts?
>
> Nick
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60288] Quadratic complexity: org.apache.poi.POIXMLDocumentPart#findExistingRelation(POIXMLDocumentPart part)

2016-10-21 Thread bugzilla

https://bz.apache.org/bugzilla/show_bug.cgi?id=60288

Javen O'Neal  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #2 from Javen O'Neal  ---
Thanks for finding this performance inefficiency and submitting a patch.
Applied in r1765935. These changes will be included in 3.16 beta 1.

Pull requests are fine.[1]

[1] https://poi.apache.org/guidelines.html#SubmittingPatches

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[GitHub] poi pull request #38: BUG-60288: removes defensive copy for internal relatio...

2016-10-21 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/poi/pull/38


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

Fwd: Re: Build failed in Jenkins: POI #1599

Re: Functionality injection technique for XWPF

Jenkins build is back to normal : POI #1601

Jenkins build is back to normal : POI-JDK8 #1301

[Bug 60289] UTF decoding in XSSFRichTextString does not work when the code is lowercase

[Bug 60294] New: Add "unknown" ShapeType for 4095

Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

[Bug 60293] New: Handling illegal "Odd" footer in XWPF

Build failed in Jenkins: POI #1600

Fwd: Build failed in Jenkins: POI #1599

Build failed in Jenkins: POI-JDK8 #1300

[GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

Jenkins build is back to normal : POI-OpenJDK #246

Build failed in Jenkins: POI #1599

[Bug 60289] UTF decoding in XSSFRichTextString does not work when the code is lowercase

[Bug 60289] UTF decoding XSSFRichTextString does not work when the code is lowercase

[Bug 60289] New: UTF decoding XSSFRichTextString does not work when the code is lowercase

RE: Functionality injection technique for XWPF

[Bug 60219] [PATCH] FormulaParser can't parse external references when sheet name is quoted

Re: Apache POI 3.15 released

Re: Apache POI 3.15 released

Re: Apache POI 3.15 released

[Bug 60288] Quadratic complexity: org.apache.poi.POIXMLDocumentPart#findExistingRelation(POIXMLDocumentPart part)

[GitHub] poi pull request #38: BUG-60288: removes defensive copy for internal relatio...

25 matches

Site Navigation

Mail list logo

Footer information