e.org]
Sent: Monday, July 02, 2018 7:07 PM
To: dev@poi.apache.org
Subject: Re: [RESULT][VOTE] Re: XMLBeans 3.0.0 release vote
> Would it make sense to change the links ... ?
Yes, that makes sense - please change it.
I had to install Forrest 0.8 and needed to start the site build via
//bin/forr
> Would it make sense to change the links ... ?
Yes, that makes sense - please change it.
I had to install Forrest 0.8 and needed to start the site build via
//bin/forrest site
plus adding the permissions to download forrest plugins.
I.e. committing xmlbeans/build/site will publish to the websit
Thanks Andi for updating the xmlbeans.apache.org site.
Would it make sense to change the links on
https://xmlbeans.apache.org/community/index.html to point to the POI mailing
lists - the XMLBeans lists haven't been reactivated?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312
The vote has passed with 3x +1 from POI / XmlBeans PMCs.
This thread can be used as a reference for the already released artifact ...
I'll now write the public announcement mail.
Andi.
On 7/1/18 9:09 PM, Dominik Stadler wrote:
> Uups, forgot to vote, I am +1 for XmlBeans 3.0.0 as no big problem
Uups, forgot to vote, I am +1 for XmlBeans 3.0.0 as no big problem related
to XmlBeans showed up in the regression runs for Apache POI
Dominik
On Sat, Jun 30, 2018 at 1:48 PM, Andreas Beeker
wrote:
> Hi PJ,
>
> before I update the website there is something missing:
>
> - a vote thread with 3x
Hi PJ,
before I update the website there is something missing:
- a vote thread with 3x +1 from PMCs (so you are missing another one)
Parallel to the website announcement an announcement mail should be also sent.
just check the archives for the POI announcement.
Can I support you on this?
Andi
Here are the results of a regression run on 1258881 documents.
Overall it looks fairly good, I see no big problems with either the
replaced zip-classes or XmlBeans 3.0.
There are 1332 suspicious new errors with the following breakdown:
* 664 times java.lang.NoClassDefFoundError:
org/openxmlforma
Hi,
Unfortunately I have to restart the run, commons-compress was missing which
caused 70k failures out of 1.2mio documents. Thus XmlBeans was not properly
tested and I need to re-trigger.
However I already noticed the following failures that look new (however
these are all very rare, not relate
A regression run on the > 1mio commoncrawl documents is underway...
Dominik
On Sun, Jun 24, 2018, 22:50 Andreas Beeker wrote:
> I'm +1 too ... we can refactor the code in the next release.
>
> A govdocs run would be nice, to see if we have further OOM problems.
>
> Andi
>
>
>
I'm +1 too ... we can refactor the code in the next release.
A govdocs run would be nice, to see if we have further OOM problems.
Andi
signature.asc
Description: OpenPGP digital signature
Some of the github pull request builds failed and I wasn't sure what was
causing the issue. Conceptually, the POI build no longer needs any piccolo
manipulation because xmlbeans 3.0.0 removes the support for piccolo
entirely.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f231286
Sorry for the confusion of pull request vs. github mirror - ... now it's on the
SVN.
What was the problem with the piccolo removal? ... after removing the "*.orig"
renamings it worked out of the box?
As we (POI) provide our own ContextTypeLoader (POIXMLTypeLoader), I'm just
trying to find out,
github is a read only mirror of the poi svn - we use pull requests on github
to demonstrate proposed changes but those pull requests need to be merged
using svn commits (by POI committers)
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
--
On 22 June 2018 at 21:49, Andreas Beeker wrote:
> I've just realized, that you've done the changes to the github mirror.
> In the context of POI, I'm looking at github only as a source for patches,
> but not as our project repo.
> So I try to integrate your changes locally and then to the svn rep
I've just realized, that you've done the changes to the github mirror.
In the context of POI, I'm looking at github only as a source for patches, but
not as our project repo.
So I try to integrate your changes locally and then to the svn repo ...
Andi
On 6/22/18 10:35 PM, Andreas Beeker wrote:
>
Before I vote, I'd like to see the XmlBeans 3.0.0 RC version in our POI build
and although you've removed and then reverted it, it would be nice, if
we don't need to do the piccolo modifications.
So it looks like I need to do those modifications locally and find out why
the piccolo stuff makes pro
Can I ask for a vote on releasing XMLBeans 3.0.0?
This branch builds and tests POI with a pre-release version of XMLBeans.
https://github.com/apache/poi/pull/113
Releasing this jar to Maven Central should just be a click of a button in
Nexus.
https://issues.apache.org/jira/browse/XMLBEANS-517?jq
17 matches
Mail list logo