date:20170127

Re: Evaluating expressions outside a cell value context

2017-01-27 Thread Nick Burch


On Sat, 28 Jan 2017, Greg Woolsey wrote:

As noted in one of the method JavaDocs, we also need to expose and make use
of the ConditionalFormattingRule "priority" attribute.  That's key to
matching the right rule when more than one rule applies to a cell.  Only
the first match in priority order is applied.


Your slight challenge is that not all Conditional Formatting rules have a 
priority... XLSX ones do, and newer XLS ones based on CFRule12Record (sid 
= 0x087A) do, but the older XLS ones (CFRuleRecord / 0x01B1) don't. I'm 
not sure what Excel does for those, but my hunch (based on our API) is 
that it uses their order as a priority.



I've created a fork in GitHub for this, and committed a stab at 
high-level API methods that could be added to the FormulaEvaluator 
interface:

https://github.com/WoozyG/poi/commit/d44fee7bd03ed450af589467ec90e2581b9f2b16$


FormulaEvaluator is an interface, which we have 4 implementations of in 
our codebabse, and I'd guess that other complex users of POI will have 
dozens more. I'm not sure, therefore, that we want to be putting all of 
the CF and DV logic methods on there, especially as it'll be common to all 
implementations


The HSSF classes for CF all use org.apache.poi.ss.formula.Formula which is 
PTG based. The HSSF classes for DV seem to store the raw PTGs.


If we added two new SS usermodel classes, eg 
ConditionalFormattingEvaluator and DataValidationEvaluator, these could be 
classes (not interfaces) with your proposed new methods on. They could 
hold the logic (once) for all formats (as it's basically the same on all) 
for priority, checking etc


Doing that would also mean that "our" new classes could call out to our 
existing low-level ones to evaluate formulas. That would mean we wouldn't 
have to make a breaking change to the FormulaEvaluator interface too


Might that work for you?


No implementations have been done yet, and the Vaadin comments indicate
HSSF doesn't parse conditional formatting properly or something, and can't
be evaluated correctly currently.  I don't know exactly what they found
wrong, and it's rather annoying they didn't file any bugs.


I think that comment is out of date, from before the CF work in 3.13

Nick

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

[Bug 54157] No text extracted from Visio file

2017-01-27 Thread bugzilla

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

Javen O'Neal  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO
 OS|Linux   |All

--- Comment #1 from Javen O'Neal  ---
Can you try this in a more recent version of POI, such as 3.15 or 3.16 beta 1?
Do you get the same amount of extracted text?

-- 
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: Evaluating expressions outside a cell value context

2017-01-27 Thread Greg Woolsey

Thanks for the feedback.  I've created a fork in GitHub for this, and
committed a stab at high-level API methods that could be added to the
FormulaEvaluator interface:

https://github.com/WoozyG/poi/commit/d44fee7bd03ed450af589467ec90e2581b9f2b16#diff-7038cb0544a92793c214095bf721a1ff

Comments and better ideas welcome, of course.  I think these methods could
serve UI projects well, centralizing the logic needed to replicate Excel's
behavior in these areas.

As noted in one of the method JavaDocs, we also need to expose and make use
of the ConditionalFormattingRule "priority" attribute.  That's key to
matching the right rule when more than one rule applies to a cell.  Only
the first match in priority order is applied.

No implementations have been done yet, and the Vaadin comments indicate
HSSF doesn't parse conditional formatting properly or something, and can't
be evaluated correctly currently.  I don't know exactly what they found
wrong, and it's rather annoying they didn't file any bugs.

Greg

On Fri, Jan 27, 2017 at 3:18 AM Nick Burch  wrote:

> On Fri, 27 Jan 2017, Greg Woolsey wrote:
> > This can be done today by accessing the evaluate* package-scoped methods
> in
> > o.a.p.ss.formula.WorkbookEvaluator from a class defined in that package.
> > This requires some understanding of formula parsing and the resulting Ptg
> > array, and uses a method explicitly noted to not be for public use.
> >
> > A general-purpose public method would look something like the other
> > evaluate* methods:
> >
> > public ValueEval evaluate(String formula, CellReference ref, FormulaType
> > formulaType) {
>
> We have some evaluation related interfaces, maybe we could put one of
> those onto the Conditional Formatting and Data Validation classes, then
> add a evaluate method on WorkbookEvaluator based on that? (Add / expose)
>
> > However, we may also want a more semantic way to handle evaluating data
> > validations and conditional formatting.  Using them has several
> > complexities and wrinkles that make it hard to do right in all cases
>
> I'd lean towards adding ConditionalFormattingEvaluator and
> DataValidationEvaluator classes, which do the hard work of working out
> what applies, which of two competing things win etc. Put user-facing
> methods on those. Have those delegate down to the new WorkbookEvaluator to
> check if a given formula is true / false / etc
>
> > This is definitely a candidate for a branch/discuss/refine/merge
> workflow,
> > which I'm willing to pursue.  I haven't done SVN branches and merges in
> > about 7 years, but how bad can it be? :D
>
> You can always branch it in github if needed!
>
> > One wrinkle is that I've seen the Vaadin code that does the conditional
> > formatting, because I'm a licensed customer, but it is using their
> > commercial license.  That means I can't do the POI work on the more
> complex
> > and complete steps above.
>
> I think it's publically available source, just not under a license we can
> use. I've certainly found the source when tracking down some odd bugs! You
> won't be able to re-use their code, but I don't think that having seen it
> precludes you writing the POI one
>
> > I'm also willing to get my boss to contact Vaadin and see if they will
> > release the relevant bits of conditional formatting code to us for use in
> > POI with the Apache 2 license.  She's very good at that sort of thing.  I
> > wouldn't want it directly, but the patterns it follows likely mirror some
> > of what we need, and I don't want to cause a problem where there doesn't
> > need to be one.
>
> Maybe the way to sell it is not as "can you give" or "can you relicense",
> but "would you like to make someone else take over the development and
> maintenance for you" :)
>
> Nick
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

Re: [VOTE] Apache POI 3.16-beta2 release (RC1)

2017-01-27 Thread Javen O'Neal

Please disregard this email chain and respond to the other [VOTE] 3.16 beta
2 email chain.

On Jan 27, 2017 12:58 AM, "Javen O'Neal"  wrote:

> Hallo,
>
> I have prepared artifacts for the release of Apache POI 3.16-beta2 (RC1).
>
> Copied from the new summary section in the changelog [1], the most
> notable changes in this release are:
>
> - The third-party jar for commons-collections4 is now required for
> handling of OLE2 properties
> - Primitive (experimental) EMF/WMF text extraction support
> - Unicode and internationalization improvements
>
> In addition, we have made significant progress in several administrative
> areas, thanks to Dominik and Andreas,
> - Generating Jenkins continuous integration jobs [2] with a Groovy script
> - Continued work on Gradle build system to eventually replace our Ant
> build system (Ant is still our official build system)
> - JCmpApi to detect intentional (removing features that have been
> deprecated for at least 2 final releases) and unintentional API breaks
> (binary and source)
> - SonarCube fixes
> - fix open file leaks (mostly in unit tests)
>
>  https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1/
>
> What to look for?
> - verify the artifacts' md5 and sha1 hashes and asc signature. This is
> my second POI beta release signed with 8BABDD6C, so you
> may need to import it into your keystore.
> This key is included in the following KEYS files [3], [4].
> It is also be found by searching on [5], [6], or most other PGP key
> servers.
> Steps to verify this are at the end of this email.
> - add, remove, or modify notable changes. Updating the release notes does
> not require rolling a new release
> - run common-crawl test
> - run file leak detector
> - check for unintentional API breaks with JCmpApi
>
> Please vote [7] to release the artifacts. Please vote 0 if everything
> looks good but you did not have time to test the artifacts in a POI
> powered application.
>
> The vote stays open for at least 72hrs, 2017-01-31, 23:59 UTC, staying
> open until we have analyzed the results of common-crawl.
> If no issues are discovered, the planned release announcement date is
> Thursday, 2017-02-02.
>
> Javen O'Neal
>
> Steps to verify the build artifacts:
> wget https://dist.apache.org/repos/dist/dev/poi/KEYS; gpg --import KEYS
> gpg --import KEYS
> (alternatively,  gpg --keyserver pgp.mit.edu --recv-key 8BABDD6C)
> svn checkout https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1
> cd 3.16-beta2-RC1
> find . -name "*.md5" -type f -execdir md5sum -c {} \;
> find . -name "*.sha1" -type f -execdir sha1sum -c {} \;
> find . -name "*.asc" -exec gpg --no-secmem-warning --verify {} \;
>
> More detailed instructions can be found at
> https://poi.apache.org/download.html#verify
>
> [1] https://poi.apache.org/changes.html
> [2] https://builds.apache.org/view/POI/
> [3] https://dist.apache.org/repos/dist/dev/poi/KEYS
> [4] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> [5] https://people.apache.org/keys/
> [6] https://pgp.mit.edu/
> [7]
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-
> fractions
>
>
>

Re: Vote threads - don't reuse old threads

2017-01-27 Thread Javen O'Neal

Looks like Thunderbird was smarter than me at keeping the message headers
despite changing the subject.

I've resent the 3.16 beta 2 vote email in a fresh email chain. Please
disregard the old one.

On Jan 27, 2017 4:12 AM, "kiwiwings"  wrote:

> Hi,
>
> I've just noticed, that that Javens 3.16-beta2 vote mail was somehow buried
> in an old thread -
> and this happened to me too once in a while ...
>
> Please be aware, that using an old response as a template for a new thread
> leads to a continuation
> of the old thread (because of some header fields) - therefore copy
> the
> content and
> don't respond to the old thread.
>
> Not sure, if it makes to double-post the vote ...
>
> Anyways, thanks for taking care of the release, Javen!
>
> Andi
>
>
>
> --
> View this message in context: http://apache-poi.1045710.n5.
> nabble.com/Vote-threads-don-t-reuse-old-threads-tp5726386.html
> Sent from the POI - Dev mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

[VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-27 Thread Javen O'Neal

Hallo,

I have prepared artifacts for the release of Apache POI 3.16-beta2 (RC1).

Copied from the new summary section in the changelog [1], the most
notable changes in this release are:

- The third-party jar for commons-collections4 is now required for handling of 
OLE2 properties
- Primitive (experimental) EMF/WMF text extraction support
- Unicode and internationalization improvements

In addition, we have made significant progress in several administrative areas, 
thanks to Dominik and Andreas,
- Generating Jenkins continuous integration jobs [2] with a Groovy script
- Continued work on Gradle build system to eventually replace our Ant build 
system (Ant is still our official build system)
- JCmpApi to detect intentional (removing features that have been deprecated 
for at least 2 final releases) and unintentional API breaks (binary and source)
- SonarCube fixes
- fix open file leaks (mostly in unit tests)

 https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1/

What to look for?
- verify the artifacts' md5 and sha1 hashes and asc signature. This is
my second POI beta release signed with 8BABDD6C, so you
may need to import it into your keystore.
This key is included in the following KEYS files [3], [4].
It is also be found by searching on [5], [6], or most other PGP key servers.
Steps to verify this are at the end of this email.
- add, remove, or modify notable changes. Updating the release notes does not 
require rolling a new release
- run common-crawl test
- run file leak detector
- check for unintentional API breaks with JCmpApi

Please vote [7] to release the artifacts. Please vote 0 if everything
looks good but you did not have time to test the artifacts in a POI
powered application.

The vote stays open for at least 72hrs, 2017-01-31, 23:59 UTC, staying
open until we have analyzed the results of common-crawl.
If no issues are discovered, the planned release announcement date is
Thursday, 2017-02-02.

Javen O'Neal

Steps to verify the build artifacts:
wget https://dist.apache.org/repos/dist/dev/poi/KEYS; gpg --import KEYS
gpg --import KEYS
(alternatively,  gpg --keyserver pgp.mit.edu --recv-key 8BABDD6C)
svn checkout https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1
cd 3.16-beta2-RC1
find . -name "*.md5" -type f -execdir md5sum -c {} \;
find . -name "*.sha1" -type f -execdir sha1sum -c {} \;
find . -name "*.asc" -exec gpg --no-secmem-warning --verify {} \;

More detailed instructions can be found at
https://poi.apache.org/download.html#verify

[1] https://poi.apache.org/changes.html
[2] https://builds.apache.org/view/POI/
[3] https://dist.apache.org/repos/dist/dev/poi/KEYS
[4] https://svn.apache.org/repos/asf/poi/trunk/KEYS
[5] https://people.apache.org/keys/
[6] https://pgp.mit.edu/
[7]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions




signature.asc
Description: OpenPGP digital signature

[Bug 60140] OOM caused by Memory Leak in FileBackedDataSource

2017-01-27 Thread bugzilla

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

Markus Kilås  changed:

   What|Removed |Added

 CC||jmarkus+apach...@kilas.se

-- 
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 #47: Added fullwidth character to WorkbookUtil.validateShee...

2017-01-27 Thread hishidama

GitHub user hishidama opened a pull request:

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

Added fullwidth character to WorkbookUtil.validateSheetName

Some Japanese characters can not be used for Excel sheet names.
see https://support.microsoft.com/ja-jp/help/436482

Invalid characters are as follows:
colon ':', 'ï¼'(\uff1a)
yen sign(reverse solidus) '\\', 'ï¿¥'(\uffe5), 'ï¼¼'(\uff3c)
question mark '?', 'ï¼'(\uff1f)
square bracket '[', ']', 'ï¼»'(\uff3b), 'ï¼½'(\uff3d)
solidus '/', 'ï¼'(\uff0f)
asterisk '*', 'ï¼'(\uff0a)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/hishidama/poi 
wip/non-ascii-invalid-character-in-sheetname

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/poi/pull/47.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #47


commit c7d9b0c050984c1a92322708896ef6b363368b64
Author: hishidama 
Date:   2017-01-27T13:06:25Z

Added fullwidth character to WorkbookUtil.createSafeSheetName, 
validateSheetName




---
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

Vote threads - don't reuse old threads

2017-01-27 Thread kiwiwings

Hi,

I've just noticed, that that Javens 3.16-beta2 vote mail was somehow buried
in an old thread -
and this happened to me too once in a while ...

Please be aware, that using an old response as a template for a new thread
leads to a continuation
of the old thread (because of some header fields) - therefore copy the
content and
don't respond to the old thread.

Not sure, if it makes to double-post the vote ...

Anyways, thanks for taking care of the release, Javen!

Andi



--
View this message in context: 
http://apache-poi.1045710.n5.nabble.com/Vote-threads-don-t-reuse-old-threads-tp5726386.html
Sent from the POI - Dev mailing list archive at Nabble.com.

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

[GitHub] poi pull request #46: formula for non-ascii sheet name

2017-01-27 Thread hishidama

GitHub user hishidama opened a pull request:

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

formula for non-ascii sheet name

Japanese characters (such as 'ã»'(\u30fb) and 'ã'(\u3010)) are letters 
in Excel, but Java's Character.isLetter() returns false.
Therefore, if these characters are included in the sheet name, formula that 
references it throws an exception.

I treated these characters as letters.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/hishidama/poi wip/formula-non-ascii-sheetname

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/poi/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit f6f6597ab2c6bf92a09e00ec49e6c527712d6453
Author: hishidama 
Date:   2015-11-13T15:56:43Z

formula for non-ascii sheet name




---
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

[GitHub] poi pull request #26: formula for non-ascii sheet name

2017-01-27 Thread hishidama

Github user hishidama closed the pull request at:

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


---
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

Re: Evaluating expressions outside a cell value context

2017-01-27 Thread Nick Burch


On Fri, 27 Jan 2017, Greg Woolsey wrote:

This can be done today by accessing the evaluate* package-scoped methods in
o.a.p.ss.formula.WorkbookEvaluator from a class defined in that package.
This requires some understanding of formula parsing and the resulting Ptg
array, and uses a method explicitly noted to not be for public use.

A general-purpose public method would look something like the other
evaluate* methods:

public ValueEval evaluate(String formula, CellReference ref, FormulaType
formulaType) {


We have some evaluation related interfaces, maybe we could put one of 
those onto the Conditional Formatting and Data Validation classes, then 
add a evaluate method on WorkbookEvaluator based on that? (Add / expose)



However, we may also want a more semantic way to handle evaluating data
validations and conditional formatting.  Using them has several
complexities and wrinkles that make it hard to do right in all cases


I'd lean towards adding ConditionalFormattingEvaluator and 
DataValidationEvaluator classes, which do the hard work of working out 
what applies, which of two competing things win etc. Put user-facing 
methods on those. Have those delegate down to the new WorkbookEvaluator to 
check if a given formula is true / false / etc



This is definitely a candidate for a branch/discuss/refine/merge workflow,
which I'm willing to pursue.  I haven't done SVN branches and merges in
about 7 years, but how bad can it be? :D


You can always branch it in github if needed!


One wrinkle is that I've seen the Vaadin code that does the conditional
formatting, because I'm a licensed customer, but it is using their
commercial license.  That means I can't do the POI work on the more complex
and complete steps above.


I think it's publically available source, just not under a license we can 
use. I've certainly found the source when tracking down some odd bugs! You 
won't be able to re-use their code, but I don't think that having seen it 
precludes you writing the POI one



I'm also willing to get my boss to contact Vaadin and see if they will
release the relevant bits of conditional formatting code to us for use in
POI with the Apache 2 license.  She's very good at that sort of thing.  I
wouldn't want it directly, but the patterns it follows likely mirror some
of what we need, and I don't want to cause a problem where there doesn't
need to be one.


Maybe the way to sell it is not as "can you give" or "can you relicense", 
but "would you like to make someone else take over the development and 
maintenance for you" :)


Nick

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

Build failed in Jenkins: POI-DSL-SonarQube #29

2017-01-27 Thread Apache Jenkins Server

See 

Changes:

[onealj] reduce the chance of a lazy copy-paste error of creating wrong release 
version

[onealj] update 3.16 beta 2 release summary

[onealj] prepare for 3.16-beta3

[onealj] release prepare for 3.16-beta2 - updating build.xml and status.xml

[onealj] revert r1780499: wrong release-prep1 version (3.15-beta1)

[onealj] Revert r1780501: wrong release-prep1 version (3.15-beta1)

[onealj] prepare for 3.15-beta2

[onealj] release prepare for 3.15-beta1 - updating build.xml and status.xml

[onealj] default secring.gpg location to ~/.gnupg

[onealj] change copyright year to 2017

[onealj] change copyright date to 2017; fix broken urls

[centic] Adjust expected font-size in tests, XSSF seems to use slightly larger 
fonts on some machines

[centic] Need a fifth addopens-parameter for JDK 9

[centic] Finally enable test for bug 44937, we got the requested missing 
test-documents a long time ago already.

[centic] Don't wrap RuntimeException

[centic] Move test to base-test-class to run it for (S)XSSF as well
Also had to increase the numbers a bit as it fails locally for me otherwise

[centic] IntelliJ warnings, Javadoc, Formatting
Changes for the RecordFormatException deprecation

[centic] Jenkins DSL: Run all tests in no-scratchpad to try to get similar 
coverage-numbers

[centic] Cover some dev-tools with a few simple tests, close resources correctly

[centic] Bug 60031: Enhance test some more

--
[...truncated 9856 lines...]
at java.net.PlainSocketImpl.socketConnect(Native Method)
at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at 
org.apache.maven.wagon.providers.http.httpclient.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)
at 
org.apache.maven.wagon.providers.http.httpclient.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:118)
... 36 more
[WARNING] Could not get content
org.apache.maven.wagon.TransferFailedException: Connect to 
www.ecma-international.org:80 [www.ecma-international.org/195.70.7.123] failed: 
Connection timed out
at 
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:935)
at 
org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at com.googlecode.WGet.doGet(WGet.java:218)
at com.googlecode.WGet.execute(WGet.java:173)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: 
org.apache.maven.wagon.providers.http.httpclient.conn.ConnectTimeoutException: 
Connect to

Build failed in Jenkins: POI-DSL-1.6 #131

2017-01-27 Thread Apache Jenkins Server

See 

Changes:

[onealj] reduce the chance of a lazy copy-paste error of creating wrong release 
version

[onealj] update 3.16 beta 2 release summary

--
[...truncated 5595 lines...]
  1800K .. .. .. .. .. 23% 79.2M 1s
  1850K .. .. .. .. .. 24% 37.4M 1s
  1900K .. .. .. .. .. 25% 15.5M 1s
  1950K .. .. .. .. .. 25% 41.0M 1s
  2000K .. .. .. .. .. 26% 25.4M 1s
  2050K .. .. .. .. .. 27% 19.4M 1s
  2100K .. .. .. .. .. 27% 2.46M 1s
  2150K .. .. .. .. .. 28%  114M 1s
  2200K .. .. .. .. .. 29%  117M 1s
  2250K .. .. .. .. .. 29% 11.6M 1s
  2300K .. .. .. .. .. 30% 84.1M 0s
  2350K .. .. .. .. .. 31% 79.4M 0s
  2400K .. .. .. .. .. 31% 1.37M 1s
  2450K .. .. .. .. .. 32%  132M 1s
  2500K .. .. .. .. .. 32%  146M 1s
  2550K .. .. .. .. .. 33%  155M 0s
  2600K .. .. .. .. .. 34% 11.1M 0s
  2650K .. .. .. .. .. 34%  163M 0s
  2700K .. .. .. .. .. 35% 92.4M 0s
  2750K .. .. .. .. .. 36% 11.0M 0s
  2800K .. .. .. .. .. 36% 84.8M 0s
  2850K .. .. .. .. .. 37% 83.7M 0s
  2900K .. .. .. .. .. 38% 13.2M 0s
  2950K .. .. .. .. .. 38% 90.7M 0s
  3000K .. .. .. .. .. 39% 97.2M 0s
  3050K .. .. .. .. .. 40% 1.57M 0s
  3100K .. .. .. .. .. 40% 99.0M 0s
  3150K .. .. .. .. .. 41% 80.0M 0s
  3200K .. .. .. .. .. 42% 99.4M 0s
  3250K .. .. .. .. .. 42% 13.0M 0s
  3300K .. .. .. .. .. 43% 73.7M 0s
  3350K .. .. .. .. .. 43% 69.8M 0s
  3400K .. .. .. .. .. 44% 80.6M 0s
  3450K .. .. .. .. .. 45% 12.4M 0s
  3500K .. .. .. .. .. 45%  115M 0s
  3550K .. .. .. .. .. 46% 99.3M 0s
  3600K .. .. .. .. .. 47% 23.0M 0s
  3650K .. .. .. .. .. 47% 19.6M 0s
  3700K .. .. .. .. .. 48%  154M 0s
  3750K .. .. .. .. .. 49% 40.0M 0s
  3800K .. .. .. .. .. 49% 66.8M 0s
  3850K .. .. .. .. .. 50% 26.8M 0s
  3900K .. .. .. .. .. 51% 44.2M 0s
  3950K .. .. .. .. .. 51% 49.3M 0s
  4000K .. .. .. .. .. 52% 51.8M 0s
  4050K .. .. .. .. .. 53% 28.2M 0s
  4100K .. .. .. .. .. 53% 32.4M 0s
  4150K .. .. .. .. .. 54% 39.0M 0s
  4200K .. .. .. .. .. 54% 68.1M 0s
  4250K .. .. .. .. .. 55% 35.8M 0s
  4300K .. .. .. .. .. 56% 25.0M 0s
  4350K .. .. .. .. .. 56%  116M 0s
  4400K .. .. .. .. .. 57% 30.9M 0s
  4450K .. .. .. .. .. 58% 47.1M 0s
  4500K .. .. .. .. .. 58% 61.8M 0s
  4550K .. .. .. .. .. 59% 26.2M 0s
  4600K .. .. .. .. .. 60%  144M 0s
  4650K .. .. .. .. .. 60% 37.4M 0s
  4700K .. .. .. .. .. 61% 80.5M 0s
  4750K .. .. .. .. .. 62% 44.4M 0s
  4800K .. .. .. .. .. 62% 20.8M 0s
  4850K .. .. .. .. .. 63%  107M 0s
  4900K

[VOTE] Apache POI 3.16-beta2 release (RC1)

2017-01-27 Thread Javen O'Neal

Hallo,

I have prepared artifacts for the release of Apache POI 3.16-beta2 (RC1).

Copied from the new summary section in the changelog [1], the most
notable changes in this release are:

- The third-party jar for commons-collections4 is now required for handling of 
OLE2 properties
- Primitive (experimental) EMF/WMF text extraction support
- Unicode and internationalization improvements

In addition, we have made significant progress in several administrative areas, 
thanks to Dominik and Andreas,
- Generating Jenkins continuous integration jobs [2] with a Groovy script
- Continued work on Gradle build system to eventually replace our Ant build 
system (Ant is still our official build system)
- JCmpApi to detect intentional (removing features that have been deprecated 
for at least 2 final releases) and unintentional API breaks (binary and source)
- SonarCube fixes
- fix open file leaks (mostly in unit tests)

 https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1/

What to look for?
- verify the artifacts' md5 and sha1 hashes and asc signature. This is
my second POI beta release signed with 8BABDD6C, so you
may need to import it into your keystore.
This key is included in the following KEYS files [3], [4].
It is also be found by searching on [5], [6], or most other PGP key servers.
Steps to verify this are at the end of this email.
- add, remove, or modify notable changes. Updating the release notes does not 
require rolling a new release
- run common-crawl test
- run file leak detector
- check for unintentional API breaks with JCmpApi

Please vote [7] to release the artifacts. Please vote 0 if everything
looks good but you did not have time to test the artifacts in a POI
powered application.

The vote stays open for at least 72hrs, 2017-01-31, 23:59 UTC, staying
open until we have analyzed the results of common-crawl.
If no issues are discovered, the planned release announcement date is
Thursday, 2017-02-02.

Javen O'Neal

Steps to verify the build artifacts:
wget https://dist.apache.org/repos/dist/dev/poi/KEYS; gpg --import KEYS
gpg --import KEYS
(alternatively,  gpg --keyserver pgp.mit.edu --recv-key 8BABDD6C)
svn checkout https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1
cd 3.16-beta2-RC1
find . -name "*.md5" -type f -execdir md5sum -c {} \;
find . -name "*.sha1" -type f -execdir sha1sum -c {} \;
find . -name "*.asc" -exec gpg --no-secmem-warning --verify {} \;

More detailed instructions can be found at
https://poi.apache.org/download.html#verify

[1] https://poi.apache.org/changes.html
[2] https://builds.apache.org/view/POI/
[3] https://dist.apache.org/repos/dist/dev/poi/KEYS
[4] https://svn.apache.org/repos/asf/poi/trunk/KEYS
[5] https://people.apache.org/keys/
[6] https://pgp.mit.edu/
[7]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions




signature.asc
Description: OpenPGP digital signature

Re: Evaluating expressions outside a cell value context

[Bug 54157] No text extracted from Visio file

Re: Evaluating expressions outside a cell value context

Re: [VOTE] Apache POI 3.16-beta2 release (RC1)

Re: Vote threads - don't reuse old threads

[VOTE] Apache POI 3.16 beta 2 release (RC1)

[Bug 60140] OOM caused by Memory Leak in FileBackedDataSource

[GitHub] poi pull request #47: Added fullwidth character to WorkbookUtil.validateShee...

Vote threads - don't reuse old threads

[GitHub] poi pull request #46: formula for non-ascii sheet name

[GitHub] poi pull request #26: formula for non-ascii sheet name

Re: Evaluating expressions outside a cell value context

Build failed in Jenkins: POI-DSL-SonarQube #29

Build failed in Jenkins: POI-DSL-1.6 #131

[VOTE] Apache POI 3.16-beta2 release (RC1)

15 matches

Site Navigation

Mail list logo

Footer information