Re: svn commit: r1918174 - /poi/site/src/documentation/release-guide.txt

[Dave Fisher]

Wow. That’s been out of date for a long time.

> On Jun 5, 2024, at 9:10 AM, fannin...@apache.org wrote:
> 
> Author: fanningpj
> Date: Wed Jun  5 16:10:19 2024
> New Revision: 1918174
> 
> URL: http://svn.apache.org/viewvc?rev=1918174&view=rev
> Log:
> update release doc
> 
> Modified:
>poi/site/src/documentation/release-guide.txt
> 
> Modified: poi/site/src/documentation/release-guide.txt
> URL: 
> http://svn.apache.org/viewvc/poi/site/src/documentation/release-guide.txt?rev=1918174&r1=1918173&r2=1918174&view=diff
> ==
> --- poi/site/src/documentation/release-guide.txt (original)
> +++ poi/site/src/documentation/release-guide.txt Wed Jun  5 16:10:19 2024
> @@ -56,7 +56,7 @@
>the dev list with a note to say you're building a release.
> 
>7. Before building, you should run the "rat-check" build task, which
> -  uses https://incubator.apache.org/rat/";>Apache Rat
> +  uses https://creadur.apache.org/rat/";>Apache Rat
>   to check the source tree for files lacking license headers. Files
>   without headers should be either fixed, or added to the exclude list
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: commits-unsubscr...@poi.apache.org
> For additional commands, e-mail: commits-h...@poi.apache.org
> 


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

Re: New Release to get rid of CVE

[Dave Fisher]

Hi Stephan,

Two answers.

1) Please list the CVEs that would be fixed. It’s quite possible they have no 
impact on POI or XMLBeans.

2) Please consider submitting a PR to make the fix. We can always use more 
contributors and everyone here is a volunteer.

Best,
Dave

> On May 15, 2024, at 2:23 AM, Stefan Bischof  wrote:
> 
> hi,
> 
> could you please plan a new release to get rid of CVE  from 
> apache-commons-compress 1.25.0 -> 1.26.1
> 
> bests
> 
> 
> -
> 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: Java 11 for POI 5?

[Dave Fisher]

These are great points.

> On Feb 21, 2024, at 11:27 AM, PJ Fanning  wrote:
> 
> Usually when projects dump Java 8 support, they is a strong reason. I don't 
> see any here.
> * I am not aware of any dependency that we rely on that has fixes that we 
> can't uptake if we stick to Java 8 - ie the projects still publish Java 8 
> friendly releases even if they have higher version releases that don't 
> support Java 8
> * I am not aware of any major Java runtime features that we need to uptake 
> that are not in Java 8
> * For me, there is a better solution to optimising support for newer Java 
> versions while still supporting older Java versions - Multi Release Jars [1]
> * The POI build support for module-info classes is pretty stable and for me 
> is far from the most complicated part of the build - I, personally, have much 
> more a problem with the build time wasted on poi-ooxml-full, the complexity 
> of poi-ooxml-lite and poi-integration - and the fact that we can't automate 
> our releases because of this complexity. I have given up bringing up 
> discussions about such items due to general lack of engagement with the dev 
> mailing list.

Let’s try again then. Let’s discuss the genesis of ooxml-lite. At Apachecon NA 
Oakland in 2008(?) Nick, Yegor, and I were sitting at a Hackathon table working 
together on POI when Jukka on the Tika project came over and said they really 
wanted to use POI for OOXML parsing but a 13MB jar file was just too big. Yegor 
thought about it and the next day OOXML-lite at 3MB was implemented.

It is worth asking in these days where 6GB docker images are almost normal if 
our users will care about the difference in newer versions?

Best,
Dave

> * We have other Apache projects like Tika, Drill and Linkis that use POI and 
> some of those still apps still use Java 8 builds. We have 1000s of other 
> projects that depend on us - eg [2]
> * If you look at Stackoverflow or our mailing lists, there is a large number 
> of users who are using old POI versions and I think we need to avoid making 
> it harder for those users to upgrade. Java 8 still gets regular security 
> patches and depending on what you read, as many as 30% of Java users still 
> use Java 8 (eg [3[).
> 
> [1] https://openjdk.org/jeps/238
> [2] https://mvnrepository.com/artifact/org.apache.poi/poi-ooxml/usages
> [3[ https://newrelic.com/resources/report/2023-state-of-the-java-ecosystem
> 
> 
> On 2024/02/19 23:00:32 stanton fisque wrote:
>> something to consider, which kind of gathers a few of the opinions that have 
>> been discussed, maybe in a different light.
>> 
>> POI is in an odd situation because it is BOTH a consumer of dependencies, 
>> and IS also a dependency, since it is a library and not a stand-alone 
>> product.
>> 
>> as a consumer of dependencies, it should be partial to keeping pace with 
>> what it consumes.  it would be a big dis-service if POI lagged behind on its 
>> dependencies and ended up getting dinged for a CERT or other security issue 
>> and not be able to mitigate it due to being incompatible with newer versions 
>> of its dependencies.
>> 
>> though, on the other side, POI should not be too aggressive since it is 
>> consumed by so many other products "out in the wild". 
>> 
>> i think a java-11 requirement would suffice for now.
>> 
>> i do not know if i am eligible (my tacit assumption is no, atm) to offer a 
>> +1, but if i could, i would.
>> 
>> 
>> Stanton Fisque
>> principal technologist
>> latticeware.com
>> portland, oregon
>> 
>>> On Feb 19, 2024, at 10:54 AM, Alain FAGOT BÉAREZ  
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> +1 for moving to Java 11 as minimum
>>> 
>>> My opinion is that we should jump to the oldest LTS version each time one 
>>> LTS reached its end of life. This means that we would jump from 8 to 17 at 
>>> once... Which is also not so friendly to be done right now!
>>> 
>>> Kind regards,
>>> Alain FAGOT BÉAREZ
>>> 
>>> 
>>> 
>>> 
>>> ⁣Obter o BlueMail para Android ​
>>> 
>>> Em 17 de fev de 2024 09:39, em 09:39, Dominik Stadler 
>>>  escreveu:
 Hi,
 
 What do others thing?
 
 We currently are at +2/-1 for moving to Java 11 minimum.
 
 Would be good if we get a more significant number of votes for this.
 
 Thanks... Dominik.
 
 
 On Sat, Feb 3, 2024 at 10:04 PM Axel Howind  wrote:
 
> Hi,
> 
> for whatever reason I cannot reach both the Nabble and MarkMail
 archives
> to check if this has been discussed before, but I think it would be a
 good
> idea to bump the minimum Java version for POI 5 to 11. I’d also be ok
 (or
> rather like) 17. What do you think?
> 
> Cheers,
> Axel
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
> 
> 
>> 
>> 
>> 

Re: Java 11 for POI 5?

[Dave Fisher]

I certainly know since I helped negotiate it out of the Apache Attic.

My point is that XMLBeans remains a separate codebase and build from POI. If it 
requires Java 8 then POI requires Java 8. What java version does XMLBeans 
require?

> On Feb 4, 2024, at 12:04 PM, Axel Howind  wrote:
> 
> AFAIK XMLBeans is now maintained by the POI project itself, so it should not 
> be problematic.
> 
> 
>> Am 04.02.2024 um 20:59 schrieb Dave Fisher :
>> 
>> What version of Java is the minimum for XMLBeans? We should not forget 
>> XMLBeans in this discussion.
>> 
>> Best,
>> Dave
>> 
>>> On Feb 3, 2024, at 5:54 PM, Axel Howind  wrote:
>>> 
>>> No one forces users of POI to update to the latest version. Going to 11 in 
>>> POI 6 doesn't mean we
>>> have to stop providing bug fixes to POI 5 from one day to the next. But 
>>> whoever is still using
>>> Java 8 is now certainly used to not being able to use the newest version of 
>>> every dependency.
>>> 
>>> Most major frameworks and many libraries now have a baseline of at least 
>>> Java 11. And many of
>>> those that are still on 8 will also have to do the switch because features 
>>> from older Java
>>> versions will be removed and the replacements are not yet available on 8:
>>> - finalizers (replaced by Cleaner introduced in 9)
>>> - sun.misc.Unsafe (replacement depends on use case, some introduced from 9 
>>> on)
>>> 
>>> Current minimum Java version for some of the most used framework and 
>>> libraries:
>>> Spring Framework and Spring Boot: java 17
>>> WildFly: Java 11
>>> Quarkus: Java 11
>>> Hibernate: Java 11
>>> KeyCloak: Java 17
>>> RabbitMQ: Java 11
>>> 
>>> Even the IDEs require more recent versions to run (but can compile using 
>>> older versions):
>>> Eclipse: Java 11 (17 recommeded)
>>> Netbeans: Java 11
>>> IntelliJ: Java 17
>>> 
>>> Even some dependencies of POI already require Java 11 in their current 
>>> version:
>>> Jakarta XML bind: Java 11 is required for version 4.x
>>> xmlsec: Java 11 is required for 4.x
>>> 
>>> And some will bump the Java version for their next major release:
>>> Log4j 3.x will require Java 17
>>> PDFbox 4.x will require Java 11
>>> Saxon is (hopefully?) still Java 8 compatible but not tested anymore under 
>>> Java 8
>>> 
>>> So staying on 8 would mean that POI will not be able to upgrade 
>>> dependencies to the latest
>>> versions of some of the dependencies and possibly rely on versions that 
>>> will be unsupported in the
>>> foreseeable future.
>>> 
>>> Moving to Java 11 will make the code easier to maintain. There are a lot of 
>>> improvements in IO,
>>> String handling, and collections that make the code more concise, easier to 
>>> understand, and maintain.
>>> 
>>> 
>>>> Am 03.02.2024 um 22:18 schrieb PJ Fanning :
>>>> 
>>>> Current POI version is 5.2.5. So I presume the idea is to release a POI 6 
>>>> with Java 11 only support. I'm -1 on this. I don't see any great advantage 
>>>> in only supporting Java 11. Java 8 is still widely supported by vendors.
>>>> 
>>>> https://endoflife.date/oracle-jdk says 6 more years of Java 8.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Saturday 3 February 2024 at 22:04:26 GMT+1, Axel Howind  
>>>> wrote: 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Hi,
>>>> 
>>>> for whatever reason I cannot reach both the Nabble and MarkMail archives 
>>>> to check if this has been discussed before, but I think it would be a good 
>>>> idea to bump the minimum Java version for POI 5 to 11. I’d also be ok (or 
>>>> rather like) 17. What do you think?
>>>> 
>>>> Cheers,
>>>> Axel
>>>> 
>>>> 
>>>> -
>>>> 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
>>>> 
>>> 
>>> 
>>> -
>>> 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
>> 
> 


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

Re: Java 11 for POI 5?

[Dave Fisher]

What version of Java is the minimum for XMLBeans? We should not forget XMLBeans 
in this discussion.

Best,
Dave

> On Feb 3, 2024, at 5:54 PM, Axel Howind  wrote:
> 
> No one forces users of POI to update to the latest version. Going to 11 in 
> POI 6 doesn't mean we
> have to stop providing bug fixes to POI 5 from one day to the next. But 
> whoever is still using
> Java 8 is now certainly used to not being able to use the newest version of 
> every dependency.
> 
> Most major frameworks and many libraries now have a baseline of at least Java 
> 11. And many of
> those that are still on 8 will also have to do the switch because features 
> from older Java
> versions will be removed and the replacements are not yet available on 8:
> - finalizers (replaced by Cleaner introduced in 9)
> - sun.misc.Unsafe (replacement depends on use case, some introduced from 9 on)
> 
> Current minimum Java version for some of the most used framework and 
> libraries:
> Spring Framework and Spring Boot: java 17
> WildFly: Java 11
> Quarkus: Java 11
> Hibernate: Java 11
> KeyCloak: Java 17
> RabbitMQ: Java 11
> 
> Even the IDEs require more recent versions to run (but can compile using 
> older versions):
> Eclipse: Java 11 (17 recommeded)
> Netbeans: Java 11
> IntelliJ: Java 17
> 
> Even some dependencies of POI already require Java 11 in their current 
> version:
> Jakarta XML bind: Java 11 is required for version 4.x
> xmlsec: Java 11 is required for 4.x
> 
> And some will bump the Java version for their next major release:
> Log4j 3.x will require Java 17
> PDFbox 4.x will require Java 11
> Saxon is (hopefully?) still Java 8 compatible but not tested anymore under 
> Java 8
> 
> So staying on 8 would mean that POI will not be able to upgrade dependencies 
> to the latest
> versions of some of the dependencies and possibly rely on versions that will 
> be unsupported in the
> foreseeable future.
> 
> Moving to Java 11 will make the code easier to maintain. There are a lot of 
> improvements in IO,
> String handling, and collections that make the code more concise, easier to 
> understand, and maintain.
> 
> 
>> Am 03.02.2024 um 22:18 schrieb PJ Fanning :
>> 
>> Current POI version is 5.2.5. So I presume the idea is to release a POI 6 
>> with Java 11 only support. I'm -1 on this. I don't see any great advantage 
>> in only supporting Java 11. Java 8 is still widely supported by vendors.
>> 
>> https://endoflife.date/oracle-jdk says 6 more years of Java 8.
>> 
>> 
>> 
>> 
>> 
>> 
>> On Saturday 3 February 2024 at 22:04:26 GMT+1, Axel Howind  
>> wrote: 
>> 
>> 
>> 
>> 
>> 
>> Hi,
>> 
>> for whatever reason I cannot reach both the Nabble and MarkMail archives to 
>> check if this has been discussed before, but I think it would be a good idea 
>> to bump the minimum Java version for POI 5 to 11. I’d also be ok (or rather 
>> like) 17. What do you think?
>> 
>> Cheers,
>> Axel
>> 
>> 
>> -
>> 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
>> 
> 
> 
> -
> 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: POI PMC roll call

[Dave Fisher]

Hi PJ,

I still monitor the project, and would, as over a decade ago be a third +1, if 
needed.

Thank you for your leadership. More inline.

> On Mar 3, 2023, at 6:26 AM, PJ Fanning  wrote:
> 
> Hi everyone,
> 
> Apologies if anyone thinks I'm going in the wrong direction here. The TLDR 
> is: I am asking if PMC members could respond with whether they are still 
> interested in working on POI or if they are no longer in a position to help.
> 
> There appears to only be a couple of POI PMC members that are active at this 
> stage (on mailing lists, dealing with bugzilla, Github commits, etc.).

As I said, I am on standby as I have been for years.

Given the following choices which would be most important.

1. We gave fully moved to Git from SVN? If so I can help with the messaging.
2. We will always need to keep bugzilla, but it could help to switch to GitHub 
issues for new bugs.
3. What is the status of CI. Is it on ASF Jenkins?
4. What is the status of gradle and the build on GitHub?
> 
> I'm not seeking anything drastic like considering retiring POI (aka moving to 
> the Attic). It is suggested in ASF guidelines that mature projects 
> occasionally do a Roll Call [1]. There doesn't appear to be many people that 
> we could look to invite to become committers or PMC members.
> 
> I'm interested in continuing but would like to cut back my involvement. I am 
> involved in a few other ASF projects and want to concentrate on those.
> 
> Even if we do have a few active PMC members, we might want to consider guide 
> lines on what sort of code changes to make and how often we intend to do 
> releases.
> 
> The code base is very large and I have to admit some of patches that I merge 
> that are submitted by outside contributors - that I don't know that part of 
> the code base well and am reliant on the test coverage to pick up issues. And 
> we have a lot of code that does not have great test coverage. Most of the 
> patches come with minimal new tests - there are definitely exceptions - some 
> of the patches are of very high quality.

Developers who provide quality patches are candidates to be committers.

> 
> It's also hard to keep up with new features in Microsoft file formats (ie new 
> XSDs) and the Java Runtime is being overhauled in ways that may eventually 
> break some POI code.

We should discuss these concerns slowly on this mailing list.

Like POI was heavily dependent on XMLBeans there are other projects that are 
dependent on POI like Tika. This dependence is what led to Yegor’s creation of 
OOXML lite almost 15 years ago.

Best,
Dave
> 
> Regards,
> PJ
> 
> 
> [1] https://www.apache.org/dev/pmc.html#move-to-attic
> 
> -
> 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: Migrate from Bugzilla to GitHub Issues

[Dave Fisher]

ASF projects must store source and source releases on ASF controlled 
properties. A significant amount of work has been done in the last decade to 
connect Gitbox with GitHub.

If anyone personally has trouble with Microsoft’s owning GitHub they can use 
the gitbox mirrors.

14 years ago we had significant discussions around trusting Microsoft. Let’s 
not go there again.

If someone wants to volunteer to make CodeBerg or Gitlab or whatever work with 
the ASF you are looking at a major effort.

Sent from my iPhone

> On Aug 18, 2022, at 5:41 AM, Yegor Kozlov  wrote:
> 
> GitHub is cool and personally, I much prefer GitHub PRs to Bugzilla.
> There are two questions though:
> 
> 1. Github is Apache-friendly, but it is not owned by ASF. For whatever
> reasons they can change their policy, access, etc. and we won't have
> control over it. It's hypothetical, but who knows?
> 
> 2. What will happen to the  mail list archives with links to Bugzilla ?
> Will it possible to redirect Bugzilla urls to the migrated GitHub Issues?
> 
> Regards,
> Yegor
> 
>> On Thu, Aug 18, 2022 at 3:21 PM Peter Keller 
>> wrote:
>> 
>> Dear all,
>> 
>> When considering a move like this, you might like to also consider
>> alternatives to GitHub. I am not going to argue strongly for one service
>> over another, but just note that there is continuing sensitivity for
>> some over Microsoft's policies with respect to GitHub. The Software
>> Freedom Conservancy recently suggested CodeBerg and SourceHut as
>> alternatives: see https://sfconservancy.org/GiveUpGitHub/
>> 
>> Regards,
>> 
>> Peter.
>> 
>>> On 18/08/2022 12:31, PJ Fanning wrote:
>>> Thanks Vladimir for bringing this up. I think it would be a good idea to
>> have a discussion on this list before anyone dedicates too much effort.
>>> 
>>> My own opinion is that it would be great to get off bugzilla. I see the
>> merit in using Github instead of Jira - because Github is an integrated
>> environment supporting Issues, Pull Requests and Continuous Integration.
>>> 
>>> I would argue that maybe we could consider also moving to Git (away from
>> Subversion). I have a big preference for Pull Requests over patch files
>> being attached to Bugzilla. These patch files get stale very quickly while
>> Git/Github provides good tooling for rebasing or merging the latest
>> trunk/main branch changes into PRs.
>>> 
>>> One of the requirements of efforts OSSF Scorecard [1] and SLSA [2] is
>> that code commits are peer reviewed and PRs are a good way to do this. We
>> probably want to get away from having ASF committers committing code
>> directly to svn or git trunk/main branch.
>>> 
>>> [1] https://github.com/ossf/scorecard
>>> [2] https://slsa.dev/
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Thursday 18 August 2022 at 10:48:18 IST, Vladimir Sitnikov <
>> sitnikov.vladi...@gmail.com> wrote:
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Just in case, I can prepare a throwaway repository with migrated
>>> issues/attachments for POI.
>>> I would need an export from Bugzilla database for POI issues.
>>> You could ask it from INFRA like in
>>> https://issues.apache.org/jira/browse/INFRA-23475.
>>> 
 Do you have examples of successful transition from Bugzilla to GitHub
 issues for Apache projects?
>>> Well, there are only a few active Apache projects that still use
>> Bugzilla.
>>> Many migrated to JIRA some time ago.
>>> 
>>> Apache Lucene migrates from JIRA to GitHub Issues right now:
>>> * https://github.com/apache/lucene/issues/993
>>> 
>>> Apache Airflow moved from JIRA to GitHub several years ago:
>>> * https://lists.apache.org/thread/g4sc91y585ypc7tgphlhvxt3v8nqsg5d
>>> * See https://github.com/apache/airflow/releases
>>> * See https://github.com/apache/airflow/issues
>>> 
>>> ---
>>> 
>>> LLVM project migrated 50'000+ issues from Bugzilla to GitHub in Nov 2021:
>>> * Here's the result: https://github.com/llvm/llvm-project/issues
>>> * https://github.com/llvm/llvm-project/issues/52603
>>> * https://github.com/llvm/llvm-iwg/issues/56
>>> 
>>> Coq project migrated 5000 issues from Bugzilla to GitHub:
>>> * https://www.theozimmermann.net/2017/10/bugzilla-to-github/
>>> 
>>> Spring project migrated from JIRA to GitHub in 2019:
>>> *
>>> 
>> https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
>>> 
>>> Sping Data project migrated from JIRA to GitHub in 2021:
>>> *
>>> 
>> https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues
>>> 
>>> 
>>> Vladimir
>>> 
>>> -
>>> 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
>> 
>> 


-
To unsubscribe, 

Fwd: Error when processing doap file http://svn.apache.org/repos/asf/xmlbeans/trunk/xkit/doap_XMLBeans.rdf:

[Dave Fisher]

FYI

Sent from my iPhone

Begin forwarded message:

> From: Projects 
> Date: June 9, 2022 at 7:03:58 PM PDT
> To: Site Development 
> Subject: Error when processing doap file 
> http://svn.apache.org/repos/asf/xmlbeans/trunk/xkit/doap_XMLBeans.rdf:
> Reply-To: site-...@apache.org
> 
> URL: http://svn.apache.org/repos/asf/xmlbeans/trunk/xkit/doap_XMLBeans.rdf
> mismatched tag: line 200, column 6
> Source: 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml

Re: [VOTE] Apache POI 5.2.0 release (RC2)

[Dave Fisher]

Wow 6 PMC members voted when was the last time that happened?

Sent from my iPhone

> On Jan 14, 2022, at 3:01 PM, PJ Fanning  wrote:
> 
> The vote carries with 6 +1s from PMC members. I will proceed with the 
> release and announcement. 
> 
> Thanks everyone for verifying the release.
> 
> 
> 
> 
> 
> 
> On Sunday 9 January 2022, 22:36:48 GMT+1, Andreas Beeker 
>  wrote: 
> 
> 
> 
> 
> 
> +1 from me. Thank you for providing the release, PJ!
> 
> Eventually we need to decide, if we only provide the logging api jars or also 
> the implementation,
> as SLF4J is used at least in XmlSec and providing the api is not enough [1].
> On the other side for log4j-shell, we had the excuse of only providing the 
> api ...
> 
> Andi
> 
> [1] https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/index.html
> 
> 
> 
> -
> 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
> 


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

Log4j 2.16.0 a more complete fix to Log4Shell

[Dave Fisher]

https://lists.apache.org/thread/d6v4r6nosxysyq9rvnr779336yf0woz4

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

[jira] [Commented] (XMLBEANS-571) Excel file read failure using xmlbeans 3.0.0 whereas it works on xmlbeans 2.6.0

[Dave Fisher (Jira)]

[ 
https://issues.apache.org/jira/browse/XMLBEANS-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420864#comment-17420864
 ] 

Dave Fisher commented on XMLBEANS-571:
--

I think you need to talk to your manager. If they will let you patch one 
version, but not let you use a released version then there is some concern 
about risk assessment. Not only that - not upgrading may leave both your 
company's systems at risk as well as your clients.

It highly recommended that POI and XMLBeans users upgrade.

> Excel file read failure using xmlbeans 3.0.0 whereas it works on xmlbeans 
> 2.6.0
> ---
>
> Key: XMLBEANS-571
> URL: https://issues.apache.org/jira/browse/XMLBEANS-571
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 3.0.0
> Environment: linux
>Reporter: Sateesh
>Priority: Blocker
> Fix For: Version 3.0.0
>
> Attachments: XLSXReaderExample.java, test.xlsx
>
>
> I have an Excel file cell with note processing successfully with Apache POI 
> 3.14 + xmlbeans 2.6.0. 
> But when we moved to xmlbeans 3.0.0 it fails with following exception. If 
> I delete the note in the Excel file it processes successfully with 3.0.0. 
> Attached the testcase
> Source_File,0: org.apache.poi.POIXMLException: 
> java.lang.reflect.InvocationTargetException
>  at 
> org.apache.poi.POIXMLFactory.createDocumentPart(POIXMLFactory.java:65)
>  at 
> org.apache.poi.POIXMLDocumentPart.read(POIXMLDocumentPart.java:601)
>  at 
> org.apache.poi.POIXMLDocumentPart.read(POIXMLDocumentPart.java:613)
>  at org.apache.poi.POIXMLDocument.load(POIXMLDocument.java:174)
>  at 
> org.apache.poi.xssf.usermodel.XSSFWorkbook.(XSSFWorkbook.java:249)
>  ...
> Caused by: java.lang.reflect.InvocationTargetException
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
>  at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
>  at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
>  at java.lang.reflect.Constructor.newInstance(Constructor.java:437)
>  at 
> org.apache.poi.xssf.usermodel.XSSFFactory.createDocumentPart(XSSFFactory.java:56)
>  at 
> org.apache.poi.POIXMLFactory.createDocumentPart(POIXMLFactory.java:62)
>  ... 12 more
> Caused by: org.apache.xmlbeans.XmlException: error: Content is not allowed 
> in trailing section.
>  at 
> org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3439)
>  at 
> org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1271)
>  at 
> org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1258)
>  at 
> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
>  at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:747)
>  at 
> org.apache.poi.xssf.usermodel.XSSFVMLDrawing.read(XSSFVMLDrawing.java:128)
>  at 
> org.apache.poi.xssf.usermodel.XSSFVMLDrawing.(XSSFVMLDrawing.java:116)
>  ... 18 more
> Caused by: org.xml.sax.SAXParseException: Content is not allowed in 
> trailing section.
>  at 
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
> Source)
>  at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown 
> Source)
>  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown 
> Source)
>  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown 
> Source)
>  at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown 
> Source)
>  at 
> org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown
>  
> Source)
>  at 
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
> Source)
>  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown 
> Source)
>  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown 
> Source)
>  at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>  at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown 
> Source)
>  at 
> org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>  at 
> org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3413)
>  ... 24 more



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: svn commit: r1893606 - /poi/site/src/documentation/content/xdocs/components/index.xml

[Dave Fisher]

> On Sep 24, 2021, at 11:10 AM, fannin...@apache.org wrote:
> 
> It may be possible to use newer XMLBeans jars but there no guarantees, 
> especially of the XMLBeans version

It may be possible to use newer XMLBeans jars but there are no guarantees, 
especially if the XMLBeans version

Re: Forrest replacement

[Dave Fisher]

Hi -

My progress is slower than I hoped.

I have a handle on conversion of the xml pages to GitHub Flavored Markdown by 
adapting Forrest’s Anakia2Markdown plugin. There are still some xml elements to 
translate.

TODOs are:

- Menu generation from sitemap.
- Changes/Status page generation.
- New template based on template-site…
- FAQ page - manual conversion will be done. It’s a one off.

> On Jul 13, 2021, at 10:56 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> I’ve had two git repositories created:
> 
> poi-site and poi-xmlbeans-site
> 
>> On Jul 11, 2021, at 1:31 PM, Andreas Beeker  wrote:
>> 
>> Hi Dave,
>> 
>>> A simpler way of stating (b) is that we separate the site from the release 
>>> process. This makes sense to me since since there are portions of the site 
>>> like download pages that should be changed after the release package has 
>>> been made.
>> Ok +1 for this
>> 
>>> If there are portions of the site that should be versioned with the release 
>>> and apidocs then we should probably work to include those pages with the 
>>> apidocs. I vaguely recall that it is possible to extend the apidocs to 
>>> include other files.
>> I'm fine with it, but I think we hardly make use of it - here is how to do 
>> it:
>> https://stackoverflow.com/questions/10779169/including-images-in-javadocs 
>> <https://stackoverflow.com/questions/10779169/including-images-in-javadocs>
>> WRT Pelican vs jBake:
>> I'm leaning towards jBake, because I'm not sure, if I need to do python 
>> modifications with Pelican, which skills I'm lacking.
>> 
> It is likely that no custom python plugins will be required and everything in 
> the sites will be markdown, html, css, and javascript.
> 
> Pelican uses JINJA templates for the base.
> 
> Should a new Pelican Plugin be needed I will push to include it in 
> infrastructure-pelican and it will be Infra that will maintain it.
>> On the other hand, the markdown source is clear and simple.
>> So I would say, Dave, make up your mind and choose what you think fits best. 
>> I think the POI PMC can handle both.
>> 
> I’m going to lean towards Pelican for now.
> 
> There is a plugin for Forrest that supposedly will make mdtext files during a 
> forrest build. If that works then this will be pretty quick.
>>> I’ll need to refine the OpenOffice Pelican scaling issue. I suspect that 
>>> the logo is the issue. Did you use a tool? If so, what?
>> No tool - I need to scale most pages to 200% because of an 1:1 scaling on my 
>> hidpi / wayland gui.
>> With openoffice the menu text only zooms marginally whereas the blue bar 
>> behind it zooms linear.
>> The drop down menus are then scaled too much.
>> 
>> 
>> 
>> 
> 
> This looks like a bad mix of pt, px, and rem in the css. Thanks!
>> 
>>> WRT Javadocs, not sure if I understood you right, but I assume we still 
>>> generate the docs with the javadoc default layout of the active (= as set 
>>> in the environment) JDK and update the POIs minor version directory with 
>>> it. If jBake/Pelican complains about a missing link here, we still can use 
>>> external links and replace them with local links via gradle for the 
>>> archives.
>>> Sure. One question is whether or not we wish to retain every version of 
>>> javadocs in the site.
>> A while back we decided to keep and update the minor versions.
>> Eventually we might want to remove obsolete javadocs, but we haven't 
>> discussed on this.
>> 
>>> Is the following still accurate: 
>>> https://svn.apache.org/repos/asf/poi/site/README.txt 
>>> <https://svn.apache.org/repos/asf/poi/site/README.txt> 
>>> <https://svn.apache.org/repos/asf/poi/site/README.txt> 
>>> <https://svn.apache.org/repos/asf/poi/site/README.txt>?
>> No this is not uptodate. "gradle site" and "ant site" only work with Java 8 
>> and maybe eventually we would like to skip that version.
>> After the java-/docs are generated, I copy/commit them to the svnpubsub 
>> branch.
>> 
> So we can do this to the new git repositories instead. That should be easy to 
> script.
> 
>> WRT XmlBeans: I use "ant site" in the site branch and commit the 
>> "./build/site" artifacts.
>> 
>>> I can work in parallel with either jBake or Pelican in GitHub producing 
>>> poi.staged.apache.org <http://poi.staged.apache.org/> 
>>> <http://poi.staged.apache.org/> and xmlbeans.staged.apache.org 
>>> <http

Re: Forrest replacement

[Dave Fisher]

Hi -

I’ve had two git repositories created:

poi-site and poi-xmlbeans-site

> On Jul 11, 2021, at 1:31 PM, Andreas Beeker  wrote:
> 
> Hi Dave,
> 
>> A simpler way of stating (b) is that we separate the site from the release 
>> process. This makes sense to me since since there are portions of the site 
>> like download pages that should be changed after the release package has 
>> been made.
> Ok +1 for this
> 
>> If there are portions of the site that should be versioned with the release 
>> and apidocs then we should probably work to include those pages with the 
>> apidocs. I vaguely recall that it is possible to extend the apidocs to 
>> include other files.
> I'm fine with it, but I think we hardly make use of it - here is how to do it:
> https://stackoverflow.com/questions/10779169/including-images-in-javadocs 
> 
> WRT Pelican vs jBake:
> I'm leaning towards jBake, because I'm not sure, if I need to do python 
> modifications with Pelican, which skills I'm lacking.
> 
It is likely that no custom python plugins will be required and everything in 
the sites will be markdown, html, css, and javascript.

Pelican uses JINJA templates for the base.

Should a new Pelican Plugin be needed I will push to include it in 
infrastructure-pelican and it will be Infra that will maintain it.
> On the other hand, the markdown source is clear and simple.
> So I would say, Dave, make up your mind and choose what you think fits best. 
> I think the POI PMC can handle both.
> 
I’m going to lean towards Pelican for now.

There is a plugin for Forrest that supposedly will make mdtext files during a 
forrest build. If that works then this will be pretty quick.
>> I’ll need to refine the OpenOffice Pelican scaling issue. I suspect that the 
>> logo is the issue. Did you use a tool? If so, what?
> No tool - I need to scale most pages to 200% because of an 1:1 scaling on my 
> hidpi / wayland gui.
> With openoffice the menu text only zooms marginally whereas the blue bar 
> behind it zooms linear.
> The drop down menus are then scaled too much.
> 
> 
> 
> 

This looks like a bad mix of pt, px, and rem in the css. Thanks!
> 
>> WRT Javadocs, not sure if I understood you right, but I assume we still 
>> generate the docs with the javadoc default layout of the active (= as set in 
>> the environment) JDK and update the POIs minor version directory with it. If 
>> jBake/Pelican complains about a missing link here, we still can use external 
>> links and replace them with local links via gradle for the archives.
>> Sure. One question is whether or not we wish to retain every version of 
>> javadocs in the site.
> A while back we decided to keep and update the minor versions.
> Eventually we might want to remove obsolete javadocs, but we haven't 
> discussed on this.
> 
>> Is the following still accurate: 
>> https://svn.apache.org/repos/asf/poi/site/README.txt 
>>  
>>  
>> ?
> No this is not uptodate. "gradle site" and "ant site" only work with Java 8 
> and maybe eventually we would like to skip that version.
> After the java-/docs are generated, I copy/commit them to the svnpubsub 
> branch.
> 
So we can do this to the new git repositories instead. That should be easy to 
script.

> WRT XmlBeans: I use "ant site" in the site branch and commit the 
> "./build/site" artifacts.
> 
>> I can work in parallel with either jBake or Pelican in GitHub producing 
>> poi.staged.apache.org  
>>  and xmlbeans.staged.apache.org 
>>   
>> until we are ready to shift. I’ll wait a few days before requesting two git 
>> repositories to see if there are other ideas.
> Is *.staged.apache.org already the live site? If not, how does the staging to 
> the live site work?
> 
> 

See https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features 


The staged sites will be poi.staged.apache.org  
and poi-xmlbeans.staged.apache.org  

We can actually put the apidocs into their own branch and publish as subdirs. 
You can look at the branches of GitHub.com/apache/openjpa for an example.
> If you start converting the forrest xmls to either jBake(groovy)/Pelican(md), 
> please have a look at the changes.xml soon, as this might need some 
> scripting. Also the formatted code parts would be nice to have.
> 
Certainly. I’m thinking we can use a client side highlighter. See 
https://highlightjs.org
> I'm now progressing with the src/bin archives without the site files in our 
> gradle script.
> 
Great.

All the best,
Dave
> Andi.
> 
> 

Re: Forrest replacement

[Dave Fisher]

Hi Andi,

> On Jul 9, 2021, at 4:13 PM, Andreas Beeker  wrote:
> 
> Hi Dave,
> 
> thanks for the feedback.
> 
> Regarding the different site branch - POI has the site in the bin/src 
> archives, XmlBeans doesn't.
> 
> Although I'm not a fan of the bin/src archives, as I usually just use a 
> package manager to get the jars,
> I'm a bit undecided what our goal should be:
> a) having all in one package and create a snapshot of the docs => include 
> site in the archive
> b) having smaller release archives and create the site by other means => 
> remove the link to the site (branch)

A simpler way of stating (b) is that we separate the site from the release 
process. This makes sense to me since since there are portions of the site like 
download pages that should be changed after the release package has been made.

If there are portions of the site that should be versioned with the release and 
apidocs then we should probably work to include those pages with the apidocs. I 
vaguely recall that it is possible to extend the apidocs to include other files.

> 
> I'm ok with either generator - jBake or Pelican. If we would go for jBake, I 
> would recommend to use the groovy-mte templates so the documentation is 
> really groovy :), i.e. the structure/template is implemented via method calls 
> or json-like structures.

With groovy we can do some interesting approaches to menus to customize by the 
folder.
Here are some jbake/groovy templates I authored starting with the main one:
https://github.com/apache/openoffice-org/blob/main/templates/page.gsp 

Here are some jbake/groovy templates I contributed to:
https://github.com/apache/incubator/blob/master/templates/homepage.gsp 

https://github.com/apache/incubator/blob/master/templates/projectspage.gsp 


> WRT Pelican, I like the ASF and Petri templates most - they rendering is ok 
> on my hidpi display and smartphone.

We worked for that, thanks!

> OpenOffice has some scaling problems on the hidpi display - smartphone is ok.

I’ll need to refine the OpenOffice Pelican scaling issue. I suspect that the 
logo is the issue. Did you use a tool? If so, what?

I’m fine with either approach. If we go with jBake then we'll need Jenkins 
jobs. If we go with Pelican then .asf.yaml will fully support us - 
Infrastructure and I understand the Pelican plugins.

> WRT Javadocs, not sure if I understood you right, but I assume we still 
> generate the docs with the javadoc default layout of the active (= as set in 
> the environment) JDK and update the POIs minor version directory with it. If 
> jBake/Pelican complains about a missing link here, we still can use external 
> links and replace them with local links via gradle for the archives.

Sure. One question is whether or not we wish to retain every version of 
javadocs in the site.

> 
>> Meanwhile others can focus on generating apidocs with Gradle.
> The generation of the Javadocs itself is already implemented in gradle - 
> module-wise and overall - I just need to put the things together for the 
> src/bin archives.

Is the following still accurate: 
https://svn.apache.org/repos/asf/poi/site/README.txt 
?

It seems to be only partially in gradle since there are instructions here for 
running "ant javadocs"

The published website is here: 
https://svn.apache.org/repos/asf/poi/site/publish/ 
 as I’ve validated here: 
https://infra-reports.apache.org/site-source/ 


For xmlbeans: https://svn.apache.org/repos/asf/xmlbeans/site/ 
 with the published site here: 
https://svn.apache.org/repos/asf/xmlbeans/site/build/site/ 


I can work in parallel with either jBake or Pelican in GitHub producing 
poi.staged.apache.org  and 
xmlbeans.staged.apache.org  until we are 
ready to shift. I’ll wait a few days before requesting two git repositories to 
see if there are other ideas.

All the Best,
Dave

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

Re: Forrest replacement

[Dave Fisher]

Hi -

I have experience with both jBake and Pelican ASF. (This is the replacement for 
the Apache CMS. I contributed heavily to it.)

jBaked sites are incubator.apache.org  (including 
several Anakia legacy parts. It’s complicated.) and openoffice.org 
 (twice baked as jBake can only handle a maximum of 
16384 files.)

Pelican ASF - www.apache.org , httpd.apache.org 
, openoffice.apache.org 
, petri.apache.org , 
flex.apache.org , olingo.apache.org 
, openjpa.apache.org , ….

I think for POI there are two matters to consider.

(1) API Docs are what is generated by the build and many sites merely copy 
these apidocs into a folder. The doxia/jBake question is somewhat irrelevant. 
In the case of OpenJPA they are actually configured now to handle these in a 
different site branch and they get deployed only as they change with a release.

(2) The poi website in the old xml style. As much as this is pretty 
straightforward xml then it can be converted to any of Markdown, Asciidoctor, 
or RST.

Personally I would be willing to put some time into a reorganized web template 
based on the look in openoffice.apache.org  and 
template.staged.apache.org . I converted 
openoffice.a.o to a top navigation bar from left nav just last week. See 
GitHub.com/apache/openoffice-project/.

I would be willing to put effort into a Pelican ASF version of the POI website 
which could include APIDocs from releases.

Meanwhile others can focus on generating apidocs with Gradle.

And I guess that means the same approach for XMLBeans.

All the best,
Dave


> On Jul 9, 2021, at 2:31 PM, Andreas Beeker  wrote:
> 
> Here are two further links as Doxia might be difficult to be invoked from 
> gradle:
> 
> Netbeans seemed to prefer JBake:
> https://cwiki.apache.org/confluence/display/NETBEANS/Static+Site+Generator+Tools+For+New+Web+Site
> 
> Static Site Generators (SSG):
> https://jamstack.org/generators/
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
> 

Re: Returned post for annou...@apache.org

[Dave Fisher]

Hi -

The Keys file is referenced in two places.

Once in the verification section where it has the older link.
The second time under archives where it points to the archive. That can be 
fixed since the dist/downloads location is automatically copied to archives.a.o.

Regarding the nightly build Sebb is pretty strict. I think that this has 
loosened some. To change it we should not make the nightly so prominent on the 
download page. Move below the archive section, and make it clear that these are 
for developers and are not releases and there is no guarantee about the 
suitability of use.

Regards,
Dave

> On Jan 19, 2021, at 2:47 PM, Andreas Beeker  wrote:
> 
> Annouce is always open for surprises ... we have the same structure of the 
> pages for quite a while and every 2nd release they complain.
> 
> 
>  Forwarded Message 
> Subject:  Returned post for annou...@apache.org 
> 
> Date: 19 Jan 2021 22:38:37 -
> From: announce-ow...@apache.org 
> To:   kiwiwi...@apache.org 
> 
> 
> Hi! This is the ezmlm program. I'm managing the
> annou...@apache.org  mailing list.
> 
> I'm working for my owner, who can be reached
> at announce-ow...@apache.org .
> 
> I'm sorry, your message (enclosed) was not accepted by the moderator.
> If the moderator has made any comments, they are shown below.
> 
>>  >
> Sorry, but the announce mail is not acceptable.
> The KEYS file must only be referenced from
> https://downloads.apache.org/poi/KEYS 
> (or the older https://www.apache.org/dist/poi/KEYS 
>  which redirects there)
> 
> Also the download page must not link to nightly builds.
> Such builds may only be advertised on pages intended for developers, not
> the general public.
> 
> Please fix the download page and submit a corrected announce email.
> 
> Thanks
> Sebb.
> <  <
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org

Re: License file

[Dave Fisher]

> On Jan 12, 2021, at 10:42 AM, Nick Burch  wrote:
> 
> On Tue, 12 Jan 2021, Andreas Beeker wrote:
>> do we really need that long LICENSE file?
>> 
>> Junit / Jacoco and few others aren't necessary to run POI and only used to 
>> build it.
>> 
>> Do utility libraries need to be included in the official LICENSE file?
> 
> If we ship them we need to detail them

Exactly.

> 
>> May we create an additional LICENSE file for development with POI.
> 
> I seem to recall that some projects do have different license files for their 
> source and binary releases, to account for the different components at build 
> and run time

Yes. Since it has been sometime since we reviewed Licensing. It is important to 
do so.


> 
> The best advice on license files at the ASF can be normally found in the 
> Incubator, as they're always helping new incoming projects get it right. If 
> you can't get a clear answer from reading the stuff at 
>  and 
>  I'd suggest ping'ing 
> general@incubator and asking one of the experts there for a hand!

I have mentored many podlings in the Incubator.

Let’s start with an audit to generate three lists:

(1) What added code do we currently include in our codebase.
(2) What are the dependencies in our builds. What is brought in - not our build 
tools.
(3) What is included in our binaries. (2) and (3) should be the same, but ...

Once we have those lists we review what licenses and notices are required. We 
then revisit our LICENSE and NOTICE files, and we will decide if we should have 
a separate LICENSE and NOTICE for binary releases.

What are the current build instructions for trunk?

Regards,
Dave

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

[Dave Fisher]

FYI -

POLogger was part of the initial commit of POI to the Apache Jakarta project on 
Jan. 31, 2002.

https://svn.apache.org/viewvc?view=revision&revision=352063 


History from svn can be found here:
https://svn.apache.org/viewvc/poi/trunk/src/java/org/apache/poi/util/POILogFactory.java?view=log
 

https://svn.apache.org/viewvc/poi/trunk/src/java/org/apache/poi/util/POILogger.java?view=log
 


There were many bug fixes, etc.

Regards,
Dave

> On Dec 5, 2020, at 2:46 PM, Bill Taylor  wrote:
> 
> Good idea.  I've been through the slf 4 j transition in other places.  It
> is PAINFUL and nobody wants to do it, but the resulting system is a lot
> better.
> 
> On Sat, Dec 5, 2020 at 5:36 PM Marius Volkhart  wrote:
> 
>> Hello,
>> 
>> POI currently uses a custom facility for logging: the POILogger interface.
>> This serves as a level of indirection to allow consumers to plug in a
>> logging implementation of their own. Best as I can tell, this facility was
>> added nearly 10 years ago, and the logging landscape has changed a lot in
>> that time. I'd like to revisit this facility.
>> 
>> The impact of temporary objects due to logging has been of increasing focus
>> in the last few years. Projects like Apache Log4J have gone to great
>> lengths to reduce the number of temporary objects created for logging
>> purposes, and run garbage-free in some configurations. At this time,
>> POILogger is comparatively garbage heavy. Every call to POILogger.log(int,
>> Object...) requires at least an Object[] allocation, even if the message
>> won't be logged. In many cases, string concatenation is done before calling
>> log(int, Object...), resulting in more allocations. The logging frameworks
>> like Log4J have solved this by adding overloads that take a varying number
>> of arguments.
>> 
>> Once inside of log(int, Object...), if it is determined that the message
>> should be logged, the common case of a single Object array is not optimized
>> for. Furthermore, the log forging escape regex is compiled every time.
>> 
>> Despite providing an indirection of it's own, POI still has a hard
>> dependency on Apache Commons Logging, and ships with a POILogger
>> implementation that defers to Commons Logging.
>> 
>> The performance topics could all be addressed without much difficulty. The
>> question I pose is, should they be? Other Apache projects exist to focus on
>> the problem of how to do logging well. I propose that POI uses one of the
>> logging frameworks directly, rather than having the POILogger abstraction.
>> 10 years ago, logging frameworks didn't split their API and backend the way
>> that Log4J and SLF4J/Logback do today, so the need for an indirection was
>> greater.
>> 
>> Commons Logging is already a dependency, so it may seem a logical choice is
>> to use it directly. However, Commons Logging has a very limited API, which
>> would make POI authors write more logging code than they do now. It also
>> suffers from high garbage.
>> 
>> Instead, I propose that Log4J is the more logical choice. It's a popular
>> logging framework, under the Apache umbrella, and is a leader when it comes
>> to considering performance while providing rich logging APIs. Using the
>> Log4J API lets application authors decide if they want to use Logback,
>> Log4J Core, or some other logging backend, and gives them a lot of
>> flexibility in how logging is done.
>> 
>> Of course, removing POILogger is an API change. However, it is marked as
>> being @Internal, and previous discussion
>>  suggests there are
>> unlikely to be many users of this API. This feels like a change that could
>> happen after the 5.0 release.
>> 
>> I would like to complete this work, and would also write new documentation
>> to explain how POI submits log events to the Log4J API.
>> 
>> Proposed changes:
>> - Remove Commons Logging dependency
>> - Add Log4J API dependency
>> - Remove POILogger API
>> - Remove POILogFactory API
>> - Modify all log sites to use Log4J API
>> - Write new documentation for how POI submits events
>> 
>> --
>> Cheers,
>> Marius Volkhart
>> 

Fwd: Working around a JRE bug

[Dave Fisher]

From the Tomcat Dev List ...

Sent from my iPhone

Begin forwarded message:

> From: Mark Thomas 
> Date: November 5, 2020 at 4:57:58 AM PST
> To: Tomcat Developers List 
> Subject: Working around a JRE bug
> Reply-To: "Tomcat Developers List" 
> 
> All,
> 
> The summary:
> 
> - The JVM spec states that the ModulePackages attribute in
>  module-info.class DOES NOT have to list ALL packages in the module
> - bnd is consistent with the JVM spec and only lists the packages that
>  are required to be listed
> - the JRE uses a broken class loader optimisation that assumes that
>  ModulePackages DOES list ALL packages present in the module
> 
> When applications try and use our JARs with bnd provided module-info
> CNFE occur because the JRE can't find the module for some classes.
> 
> For a fuller description of the issue see:
> https://bugs.openjdk.java.net/browse/JDK-8255854
> 
> This is likely the cause of several currently open bugs reports of CNFE
> when using modules.
> 
> 
> Possible solutions:
> 
> 1. OpenJDK accepts the class loader optimisation is flawed and reverts
>   it.
>   Given the reaction so far to the reported bug this looks unlikely.
>   Even if this were to happen, class loading performance would be
>   impacted and it is going to take a long time before all the broken
>   JREs have been updated.
> 
> 2. The bnd project updates bnd to implement what amounts to an
>   undocumented requirement that the ModulePackages attribute lists all
>   packages in the module.
>   This is probably the cleanest solution but depends on the goodwill of
>   the bnd project who would be well within their rights to reject it as
>   invalid based on the JVM spec. I haven't yet approached the bnd
>   project. A fix along these lines might be ready for the next release
>   round but is unlikely to be ready for this one.
> 
> 3. We drop all the JPMS meta-data until we have a solution.
>   I'm not sure of the consequences for users wanting to use Tomcat JARs
>   in a JPMS environment.
> 
> 4. We "patch" module-info after bnd has generated it via:
>   - custom code (BCEL probably helps)
>   - jar (if using Java 9+ jar rebuilds the module-info.class file)
> 
> 5. We add "unnecessary" @aQute.bnd.annotation.jpms.Open annotations to
>   packages so bnd includes them in module-info.
>   It might be hard to remove these at a later date if folks start to
>   depend on them.
> 
> 
> I am currently thinking along these lines:
> 
> - Add @aQute.bnd.annotation.jpms.Open where necessary to fix this.
> - Document clearly in the Javadoc, change log, the release announcement
>  and the RELEASE NOTES that this is a temporary workaround that will be
>  removed as soon as a better fix is available.
> - Ask the bnd project to make a change to list all packages in a module
>  in the ModulePackages attribute.
> 
> Thoughts?
> 
> Mark
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
> 

[DISCUSS] Re: [VOTE] Apache POI 4.1.2 release (RC2)

[Dave Fisher]

Hi -

What resources would be needed to replace Dominick’s equipment? Depending on 
the resources it might be possible to have ASF infrastructure provision a VM to 
be managed by POI PMC.

Regards,
Dave

Sent from my iPhone

> On Feb 5, 2020, at 3:38 PM, Andreas Beeker  wrote:
> 
> Hi Tim,
> 
> do you also perform a crawl/regression test? ... now that Dominiks equipment 
> is unavailable.
> 
> Andi
> 
>> On 05.02.20 01:05, Tim Allison wrote:
>> +1
>> 
>> built without surprises, digests check out and Tika builds.  Thank you,
>> Andi and team!
>> 
>>> On Tue, Feb 4, 2020 at 2:20 PM Andreas Beeker  wrote:
>>> 
>>> +1 ... the NOTICE file was still on 2019, but I don't think this matters.
>>> Apart of it, my sample application works.
>>> 
>>> On 03.02.20 22:55, PJ Fanning wrote:
 +1 builds working and APIs are stable
On Monday 3 February 2020, 21:14:53 GMT, Andreas Beeker <
>>> kiwiwi...@apache.org> wrote:
 Hi *,
 
 I've prepared artifacts for the release of Apache POI 4.1.2 (RC2).
 
 The most notable changes in this release are:
 
 - XDDF - some work on better chart support
 - Common SL / EMF - ongoing rendering fixes - see #60656
 - XSLF - OOM fixes when parsing arbitrary shape ids + a new dependency
>>> to SparseBitSet 1.2 - see #64015
 https://dist.apache.org/repos/dist/dev/poi/4.1.2-RC2/
 
 The heap problem is solved and back to the old values - Thank you
>>> Dominik.
 I've added various XSLF fixes which I'd like to be mass tested.
 
 Please vote to release the artifacts.
 The vote keeps open for 72hrs after the regression results are available.
 Planned release announcement date is Friday, 2020-02-10.
 
 Andi
 
 
 
>>> 
>>> 
>>> 
> 
> 


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

Re: Remove bloated examples?

[Dave Fisher]

That stuff was really useful when we had no documentation well over a decade 
ago.

I wonder if Nick or Yegor have an opinion about this.

Regards,
Dave

Sent from my iPhone

> On Dec 8, 2019, at 11:20 AM, Alain Béarez  wrote:
> 
> +1 for removal of examples using outdated technologies
> 
> ⁣Obter o BlueMail para Android ​
> 
> Em 7 de dez de 2019 14:09, em 14:09, Andreas Beeker  
> escreveu:
>> Hi,
>> 
>> I'm in the progress of fixing a few Sonar issues and came across the
>> two examples SViewer and POIBrowser.
>> Those use either outdated technology like Applets or add a lot of
>> unrelated code (/ some unrelated  dependencies) to only a few POI
>> calls.
>> 
>> With a silent/positive consensus, I'll remove them soon.
>> 
>> Andi


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

2020 ASF Community Survey

[Dave Fisher]

Hello everyone,

If you have an apache.org  email, you should have received 
an email with
an invitation to take the 2020 ASF Community Survey. Please take 15
minutes to complete it.

If you do not have an apache.org  email address or you 
didn’t receive a
link, please follow this link to the survey:
https://communitysurvey.limequery.org/454363 


This survey is important because it will provide us with scientific
information about our community, and shed some light on how we can
collaborate better and become more diverse. Our last survey of this kind
was implemented in 2016, which means that our existing data about Apache
communities is outdated. The deadline to complete the survey is January
4th, 2020. You can find information about privacy on the survey’s
Confluence page [1].

Your participation is paramount to the success of this project! Please
consider filling out the survey, and share this news with your fellow
Apache contributors. As individuals form the Apache community, your
opinion matters: we want to hear your voice.

If you have any questions about the survey or otherwise, please reach
out to us!

Kindly,
ASF Diversity & Inclusion
https://diversity.apache.org/ 

[1]
https://cwiki.apache.org/confluence/display/EDI/Launch+Plan+-+The+2020+ASF+Community+Survey
 

Re: Concatenating, Indexing, and Copying a document to the end of another

[Dave Fisher]

Hi -

Assuming the OP has the rights this could be refactored into an example. I 
don’t think we require a full set of unit tests for an example.

Regards,
Dave

> On Oct 24, 2019, at 6:27 AM, Mark Murphy  wrote:
> 
> In addition, if you were paid to develop the software, it likely belongs to
> the company that paid you, and you would need to get a signed release to
> open source it. The Apache foundation is particularly touchy about this.
> 
> On Wed, Oct 23, 2019 at 5:30 AM pj.fanning  wrote:
> 
>> My personal opinion is that I'd prefer not to add this to the POI core. It
>> is
>> quite possible to have a community where people have side projects that use
>> the core code. The core POI code is already very large and we only have a
>> small number of volunteers to maintain it.
>> 
>> If we were to add this code to POI core, it would need samples, unit tests
>> and the code would need to be formatted and follow Java coding standards -
>> for instance, your code has some classes with names that start with
>> lowercase letters and parameter names that start with capital letters.
>> 
>> 
>> 
>> --
>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>> 
>> -
>> 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: Git question for the gurus

[Dave Fisher]

Hi Mark,

I find SVN better for me too. It has advantages, but branches are expensive. 
Your repository is monolithic and you only need the parts you are interested 
in. Git is distributed and branches are cheap, but it makes procedures more 
complex and less intuitive. I often feel like I’m going through a glass door 
where it is not clear if I need to push or pull to open.

I hope these pages from GitHub help:

https://help.github.com/en/articles/syncing-a-fork
https://help.github.com/en/articles/configuring-a-remote-for-a-fork
https://help.github.com/en/articles/pushing-to-a-remote

Regards,
Dave

> On Apr 26, 2019, at 7:46 AM, Mark Murphy  wrote:
> 
> I get SVN, it works like the other non-open source change management
> systems I have worked with in the past. I rarely end up confused by what I
> see happening. But I guess I just don't understand Git. I have a fork of
> POI on Git Hub JMarkMurphy/poi that I have been keeping synced with the
> main apache/poi repository. I do that by creating a pull request and merge
> from apache/poi to JMarkMurphy/poi. I do not have any of my updates in
> there, just attempts to keep my fork up to date. At this point my
> JMarkMurphy/poi is 9 commits ahead of apache/poi. Each time I merge changes
> I get another commit ahead. Is this normal? Is there anything I can do to
> avoid this?
> 
> What I want to be able to do is make a branch for a change, and since I
> only work on this in fits and starts, merge in apache/poi commits, and then
> merge those with my branch to deal with anything that may conflict with my
> change, then finally merge my branch back to trunk. Is that reasonable?
> Then how do you go about making changes in the Git repository live? Do I
> have to export it from Git, and make an SVN change? How do you do that?


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

Re: EXT MSG Re: Error while building POI project

[Dave Fisher]

OOXML *is* part of POI. You will need XMLBeans if you wish to compile these.

Sent from my iPhone

> On Apr 25, 2019, at 6:29 PM, Gauntt, David  wrote:
> 
> I have updated Eclipse to version 2019-03, and pulled the latest version of 
> Poi trunk from the Git mirror.  Eclipse now builds POI without errors, but 
> apparently I cannot make use of it (see details below).  I am trying to get 
> around this by going back to using Ant to build build.xml with the "jar" 
> target, but it fails during the test phase.  I am an Ant newbie, so I can 
> only guess as to what is happening here.
> 
> When Ant fails, the following written is to the console:
> 
> [junit] Running org.apache.poi.TestXMLPropertiesTextExtractor
>   [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1.028 sec
>   [junit] Running org.apache.poi.extractor.ooxml.TestExtractorFactory
>   [junit] Tests run: 15, Failures: 0, Errors: 4, Skipped: 0, Time 
> elapsed: 2.54 sec
> BUILD FAILED
> C:\Users\David M. Gauntt\git\poi\build.xml:1629: The following error occurred 
> while executing this line:
> C:\Users\David M. Gauntt\git\poi\build.xml:1595: The following error occurred 
> while executing this line:
> C:\Users\David M. Gauntt\git\poi\build.xml:1237: Tests failed
> 
> The lines of build.xml that cause the errors are:
> 
>depends="compile-main,compile-ooxml,-test-ooxml-check,jacocotask,-ooxml-lite-agent"
>  unless="ooxml.test.notRequired"
>description="test OOXML classes">
> //Fails on the following line
>
>
>
>
> and
>   
>
>
>
> //Fails on the following line
> jacocodest="build/jacoco-@{type}.exec">
>
>
>
>
> 
> I will see if I can disable a test target as a jury-rig, but that doesn't 
> seem like the best possible solution.
> 
> Details on Eclipse failure
> 
> I had written a UnitTest project to run unit tests on Poi (and other 
> software).  In Eclipse, I have added ApachePOI as a "Required Project" in the 
> build path, but I get the following in the Problem window:
> "The type org.openxmlformats.schemas.spreadsheetml.x2006.main.CTWorksheet 
> cannot be resolved. It is indirectly referenced from required .class files"
> I can get rid of this by adding two libarires that I downloaded from the 
> internet: "ooxml-schemas-1.4.jar" ad "ooxml-security-1.1.jar".  When I do 
> this I can build and run the UnitTest project, but it appears to be executing 
> the XSSFSheet code in "ooxml-schemas-1.4.jar" rather than in the ApachePOI 
> project, which defeats the whole purpose of the UnitTest project.
> 
> 
> 
> From: Gauntt, David
> Sent: Thursday, April 25, 2019 11:34:53 AM
> To: POI Developers List
> Subject: Re: EXT MSG Re: Error while building POI project
> 
> Thanks for looking into this; I will try updating Eclipse and rebuilding
> tonight.
> 
> I have also been working on building it using Ant within Eclipse; I will
> post a question in the next day or two about my current problem with that.
> 
> ‹
> David M. Gauntt, Ph.D.
> Associate Professor, Department of Radiology
> UAB Medical Center
> 
> 
> 
> 
> 
> 
>> On 4/25/19, 7:58 AM, "Dominik Stadler"  wrote:
>> 
>> Hi David,
>> 
>> Sorry that it took you some time to make it work, we try to make it easy,
>> but as things are constantly
>> 
>> Sounds like a limitation of Eclipse, I just tried with Eclipse 4.7.x and
>> saw the same error with latest trunk, it seems not many people working on
>> POI are using Eclipse nowadays.
>> 
>> I then tried with latest Eclipse 2019.03, there most of the compilation
>> errors are gone, 4 are remaining for casts that seem to be too complex for
>> Eclipse but are working with Oracle/OpenJDK/IBMJDK, we should probably
>> work
>> around those so we support at least the current version of Eclipse, even
>> if
>> it has limitations in its implementation of Java compilation.
>> 
>> I performed a few smaller changes that should make it work on Eclipse
>> 2019.03 again, so if you can switch Eclipse and update to latest trunk,
>> you
>> should be able to compile.
>> 
>> Thanks... Dominik.
>> 
>> 
>> On Thu, Apr 25, 2019 at 3:04 AM Gauntt, David 
>> wrote:
>> 
>>> I am getting close to my first successful build of the POI project, and
>>> have run into a couple of compiler errors that seem to be blocking me.
>>> The
>>> first of these is
>>> 
>>> 
>>> Cannot reference a field before it is defined
>>> 
>>> 
>>> This is caused 100 times in RecordTypes. java.  How is it that other
>>> people are getting this project to compile properly but not me?  I am
>>> building in Eclipse ver 2018-09 under Windows 10, using Java SE 1.8.
>>> The
>>> project is a copy of tag REL_4_1_0 from the Git mirror of POI.
>>> 
>>> 
>>> The following code illustrates this error.  Ironically, while the error
>>> message says that I am trying to reference a field, the error seems t

Re: Returned post for annou...@apache.org

[Dave Fisher]

You don’t have links to the download or download page. Take a look at previous 
announcements.

Sent from my iPhone

> On Apr 4, 2019, at 6:09 PM, Greg Woolsey  wrote:
> 
> Anyone see anything wrong with my XMLBeans announcement below, before I try
> again?  Looks right to me.  My Apache account is valid, it's what I use to
> commit and use this dev list :)
> 
> Greg
> 
> 
> -- Forwarded message -
> From: 
> Date: Thu, Apr 4, 2019 at 3:58 PM
> Subject: Returned post for annou...@apache.org
> To: 
> 
> 
> 
> Hi! This is the ezmlm program. I'm managing the
> annou...@apache.org mailing list.
> 
> I'm sorry, the list moderators for the announce list
> have failed to act on your post. Thus, I'm returning it to you.
> If you feel that this is in error, please repost the message
> or contact a list moderator directly.
> 
> --- Enclosed, please find the message you sent.
> 
> 
> 
> 
> 
> -- Forwarded message --
> From: Greg Woolsey 
> To: POI Users List , POI Developers List <
> dev@poi.apache.org>, gene...@poi.apache.org, annou...@apache.org
> Cc:
> Bcc:
> Date: Sat, 30 Mar 2019 10:54:58 -0700
> Subject: [ANNOUNCE] Apache XMLBeans 3.1.0 released
> The Apache POI PMC is pleased to announce the release of Apache XMLBeans
> 3.1.0.
> 
> Apache XMLBeans is a technology for accessing XML by binding it to Java
> types.
> 
> For detailed changes in this release, refer to the release notes [1] and
> the changelog [2].
> 
> Thank you to all our contributors for making this release possible.
> 
> On behalf of the Apache POI PMC,
> 
> Greg Woolsey
> 
> [1] Release notes:
> https://www.apache.org/dyn/closer.lua/poi/xmlbeans/release/dev/RELEASE-NOTES-3.1.0.txt
> [2] Changelog: https://xmlbeans.apache.org/status.html#rel_310


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

Re: XMLBeans 3.1.0 candidate build

[Dave Fisher]

Sent from my iPhone

> On Mar 24, 2019, at 3:31 PM, Andreas Beeker  wrote:
> 
> Hi Greg,
> 
> First of all, thank you Greg for taking the release manager role - I know 
> it's time consuming especially in the beginning.
> 
> It's ok, but not nice to have the bin directory in the src dist duplicated in 
> (/bin, /src/shell) - we can change that on the next release. I still think 
> it's better to have the shell scripts not under /bin in the source tree.

+1
> I don't like to have the javadocs in the src dist, but rather would like to 
> see them in bin dist.

+1
> 
> In my view, the src dist is a copy of the trunk whereas the bin dist contains 
> all the compiled/generated artifacts.

+1
> 
> The pgp signature (*.asc) doesn't need to be check-summed - for Nexus, I'm 
> not sure if they are automatically created on uploading the signature files.

+1, it doesn’t serve any purpose I’ve only ever seen it on a single project in 
the incubator and at least on Apache dist they should be removed.

> 
> Sorry for my late response - I've followed the discussions about the release, 
> but was too busy/tired for a timely follow-up.
> 
> - project structure / modularization (xmlbean_xpath.jar, xmlpublic.jar, 
> xbeans.jar, ...):
>   the source is full of modules, reflection calls and references to 
> xbeans.jar - I feel the urge to clean up that (in my view) mess. Basically we 
> should provide a xmlbeans.jar which contains everything and minimize 
> reflections.
> 
> - the KEYS file: I'd like to have one merged KEYS file for both projects and 
> use svn externals to link to the one place.

Since they are both in the same dist area in on Apache then they must be merged 
or the main one has all the keys.

There is one place on dist and never inside a release.

Regards,
Dave

> 
> Andi.
> 


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

Re: 4.0.1 build fails - no RELEASE-NOTES.txt in git

[Dave Fisher]

Hi -

Sent from my iPhone

> On Dec 26, 2018, at 4:17 PM, Filipp Gunbin  wrote:
> 
> Hi Andreas,
> 
>> On 26/12/2018 21:31 +0100, Andreas Beeker wrote:
>> 
>> Hi Filipp,
>> 
>> the documentation directory is a svn external, which is apparently not
>> mirrored to github.  In case you would like verify the 4.0.1 build,
>> the svn tag [1] should work ... hopefully.
> 
> I see, thanks.  It'd be nice to be able to build from git also (perhaps,
> a git submodule for documentation directory?)
> 
>> Just out of curiosity, why are you trying to run "ant dist" on a
>> released version?
> 
> Just a usual habit of building everything (including docs) from
> version-controlled sources :-)

The dist target is meant for the release manager. Please see 
https://poi.apache.org/devel/index.html where targets are documented. (I hope 
correctly.)

Regards,
Dave


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

Re: Dave's POI talk at COSCON

[Dave Fisher]

Yes. You found it!

Sent from my iPhone

> On Nov 6, 2018, at 12:29 PM, Tim Allison  wrote:
> 
> W00t!!!
> 
> Here's Dave's talk on POI at COSCON in Shenzhen, China on October 20, 2018:
> 
> https://www.youtube.com/watch?v=N7_Y3zNb_-w
> 
> -
> 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: Here are my slides (if attachments are not stripped)

[Dave Fisher]

Thanks!

On 2018/10/19 12:23:18, "pj.fanning"  wrote: 
> LGTM.
> 
> 2 minor typos:
> conjuction
> uneccessary
> 
> 
> 
> --
> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
> 
> -
> 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

Here are my slides (if attachments are not stripped)

[Dave Fisher]

Hi -

Any typos, tiny enhancements or other comments?

Regards,
Dave



Dave-poi.pptx
Description: MS-Powerpoint 2007 presentation

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

List of Slides for my China talk this coming weekend

[Dave Fisher]

Hi -

I’ve come with the plan for my POI talk next weekend. I need to finalize my 
slides tomorrow so that some Chinese translation can be done. I have some 
questions that I’ll mark as “—>”. If you can answer you’ll save me some 
research.

I plan to tell the story of POI, including Tika interactions, and Common 
Crawler, in the end I want to give people two places to contribute along with 
motivation.

(1) Title
Name of presentation
About Dave
(2) POI
When it started in Jakarta the simple use case.
End of Jakarta
(3) OOXML and the Microsoft Open Specification Promise
The OSP
The flame war
OpenXML4J - http://incubator.apache.org/ip-clearance/openxml4j.html 

XSSF, XSLF, and SS
(4) Tika and OOXML lite
Apachecon Oakland 2009 - Jukka asked Nick, Yegor and I during BarCamp 
if we could something about the 13MB ooxml jar. Yegor came up with a solution 
in a day. 
Unit Test and your Beans are included
—> Anyone: anything to add? XMLBeans impacts?
(5) Graphics2D
Discuss output techniques developed.
—> Yegor - is there some sample code you might share.
(6) Tika Text Extraction
—> Could use pointers to the basic tutorial.
(7) Common Crawler - 1TB of samples
Common Crawler - commoncrawl.org
Common Crawler Download - centic9
Regression sets for POI, Tika and PDFBox
—> Are there other Apache projects that use these documents?
(8) The POI Toolbox
A table of the various formats with input, output, and remarks.
(9) XMLBeans 3
Bringing the product out of the attic.
—> Any reasons besides better control of Entity Expansion attacks?
(10) Contributing to POI and Tika Will Improve Your Solr Search Results
How Solr and similar architectures depend on Tika and Tika depends on 
POI
Example is Headers and Footers choices on Word documents on the Tika 
List this past week.

Thanks for your help and feedback!

Regards,
Dave

Re: EMF corpus

[Dave Fisher]

I’m following this as part of my talk at COSCON which I plan to include common 
crawler.

Who is in charge of where the crawler is pointed and how would one ask for 
additional URLs?

Regards,
Dave

Sent from my iPhone

> On Oct 8, 2018, at 10:31 PM, Dominik Stadler  wrote:
> 
> Hi Andi,
> 
> I have now executed the CommonCrawlDownload-tool on crawl 2018-30, only 144
> files did match by extension, I have collected them at
> https://www.dropbox.com/s/w3sxnb5l3er3kdq/downloadEMF.zip?dl=0 however many
> are actually some HTML, mostly redirects.
> 
> 5hwaterwiki2011.wikispaces.com_file_links_parana_river_wordart.emf:
> empty
> 5hwaterwiki2011.wikispaces.com_file_view_parana_river_wordart.emf:
> Windows Enhanced Metafile (EMF) image data version 0x1
> apache.org_foundation_press_kit_asf_logo_wide.emf:
> Windows Enhanced Metafile (EMF) image data version 0x1
> apkpure.com_emf-fitness_com.technogym.emf:
> HTML document, UTF-8 Unicode text, with very long lines, with CRLF, LF line
> terminators
> apkpure.com_eye-monster-invasion-free_com.abula.emf:
> HTML document, UTF-8 Unicode text, with very long lines, with CRLF, LF line
> terminators
> appraiser77.ru_adds_nechaev_rakova_2.files_image001.emz:
> gzip compressed data, max compression, from NTFS filesystem (NT)
> atlantabusinessnetwork.org_newsletter_july_image014.emz:
> ASCII text, with no line terminators
> atlantabusinessnetwork.org_newsletter_july_image015.emz:
> ASCII text, with no line terminators
> caicedo.wikispaces.com_file_history_imagen1.emf:
> empty
> caicedo.wikispaces.com_file_links_imagen1.emf:
> empty
> chisinau.md_public_files_primaria_info_utila_rezerva_cmc.emf:
> HTML document, ASCII text
> demaret.se_demaret060725.emf:
> HTML document, ASCII text
> demaret.se_demaret5.emf:
> HTML document, ASCII text
> downtowntactical.com_brand.emf:
> empty
> encyclopedia2.thefreedictionary.com_.emf:
> HTML document, UTF-8 Unicode text, with very long lines, with CRLF line
> terminators
> extension.sophia-it.com_content_.emf:
> HTML document, UTF-8 Unicode text, with very long lines, with CRLF, LF line
> terminators
> faculty.ksu.edu.sa_a-alkathiri_publishingimages_link.emf:
> empty
> festivales.wikispaces.com_file_links_dia_de_los_madres.emf:
> empty
> informationforsurvey.com_powerprocessplant_image002.emz:
> ASCII text, with no line terminators
> iranapps.ir_app_com.superphunlabs.emf:
> HTML document, UTF-8 Unicode text, with very long lines, with CRLF, LF line
> terminators
> irunguns.com_brand.emf:
> empty
> itec-int.co.jp_isop_users_images_giziroku.emf:
> Windows Enhanced Metafile (EMF) image data version 0x1
> itec-int.co.jp_isop_users_images_isopzirei.emf:
> Windows Enhanced Metafile (EMF) image data version 0x1
> itec-int.co.jp_isop_users_images_nipou.emf:
> Windows Enhanced Metafile (EMF) image data version 0x1
> itec-int.co.jp_isop_users_images_syuuhouzirei.emf:
> Windows Enhanced Metafile (EMF) image data version 0x1
> itec-int.co.jp_isop_users_images_toukou.emf:
> Windows Enhanced Metafile (EMF) image data version 0x1
> javalibs.com_artifact_org.eclipse.incquery_org.eclipse.incquery.patternlanguage.emf:
> HTML document, UTF-8 Unicode text, with very long lines, with CRLF, LF line
> terminators
> javalibs.com_artifact_org.eclipse_org.eclipse.wst.common.emf:
> HTML document, UTF-8 Unicode text, with very long lines, with CRLF, LF line
> terminators
> javalibs.com_artifact_org.eclipse.xpand_org.eclipse.xtend.typesystem.emf:
> HTML document, UTF-8 Unicode text, with very long lines, with CRLF, LF line
> terminators
> karayan.net_sourin_furusato1.files_image023.emz:
> gzip compressed data, max compression, from NTFS filesystem (NT)
> kentuckypawninc.com_brand.emf:
> empty
> llmotivation.wikispaces.com_file_links_picture1.emf:
> empty
> media.community.dell.com_zh_images_1000.4.2512.itroom.emf:
> HTML document, ASCII text, with CRLF line terminators
> media.community.dell.com_zh_images_1000.4.2513.itroom.emf:
> HTML document, ASCII text, with CRLF line terminators
> media.community.dell.com_zh_images_1000.4.8165.step2.emf:
> HTML document, ASCII text, with CRLF line terminators
> media.community.dell.com_zh_images_1000.4.8166.step3.emf:
> HTML document, ASCII text, with CRLF line terminators
> media.community.dell.com_zh_images_1000.4.8168.step2.emf:
> HTML document, ASCII text, with CRLF line terminators
> media.community.dell.com_zh_images_1000.5.2515.itroom.emf:
> HTML document, ASCII text, with CRLF line terminators
> mineralesygemas.com_index_archivos_image163.emz:
> HTML document, ASCII text
> mvnrepository.com_artifact_org.eclipse.emf:
> HTML document, UTF-8 Unicode text, with very long lines
> nienaltowski.net_drzewo_20r.nienaltowski.emf:
> Windows Enhanced Metafile (EMF) image data version 0x1
> nsw.hia.com.au_images_last_20chance_20for_20tickets.emf:
> HTML document, ASCII text, with CRLF line terminators
> play.google.com_store_apps_details_id=switches.emf:
> HTML document, ASCII text, with very long lines
> 

Re: Speaking on POI at China Open Source Conference in October

[Dave Fisher]

Hi Nick,

Sit at BarCamp 2 Monday morning or do a BOF later?

Would someone point me to the Common crawler information.

Regards,
Dave

Sent from my iPhone

> On Sep 17, 2018, at 8:07 AM, Nick Burch  wrote:
> 
>> On Sat, 15 Sep 2018, Dave Fisher wrote:
>> I’ll be at Apachecon Montreal, anyone else?
> 
> I'll be there! Happy to look at draft slides then, and offer advice :)
> 
> 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: Speaking on POI at China Open Source Conference in October

[Dave Fisher]

Hi -

These are all great ideas. Thanks!

I’ll be at Apachecon Montreal, anyone else?

Regards,
Dave

Sent from my iPhone

> On Sep 15, 2018, at 2:12 PM, Tim Allison  wrote:
> 
> Looks great! If at all possible, I’d appreciate a bullet or two on
> Dominik’s and my large scale regression tests... More input on test files
> for the corpus would be useful. Complete understand if this is off topic.
> Thank you!
> 
>> On Fri, Sep 14, 2018 at 5:27 PM Dave Fisher  wrote:
>> 
>> Hi Team,
>> 
>> I’ve been invited to speak at the COSCON in Shenzhen, China on October
>> 20-21. I’ll have two talks. One is about the Incubator, but one was my
>> choice and I chose POI due to a few interesting things happening here plus
>> our long history as a small project that show some important points about
>> Apache project governance.
>> 
>> I’m thinking about slides with these topics, but I’m looking to the
>> community to help me with some of the points to add what you know including
>> your opinions. Think of this like a group history project. In the end I
>> have one hour with plenty of time to be taken in translation.
>> 
>> (1) Apache POI 4.0 Motivations and Features
>>Java Jars
>>Remove Deprecated methods
>>OOXML 1.4
>> 
>> (2) XMLBeans 3.0.1
>>Entity Expansions
>>Taking over the codebase
>> 
>> (3) OOXML
>>Generated from XSD
>>Lite generated from listing of classes used in Unit Tests
>> 
>> (4) All of the formats
>>Table of formats and when they were introduced
>> 
>> (5) POI 3.5 - OOXML
>>Microsoft OpenSource Promise
>>Relevance
>>Project impact
>> 
>> Regards,
>> Dave
>> 


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

Speaking on POI at China Open Source Conference in October

[Dave Fisher]

Hi Team,

I’ve been invited to speak at the COSCON in Shenzhen, China on October 20-21. 
I’ll have two talks. One is about the Incubator, but one was my choice and I 
chose POI due to a few interesting things happening here plus our long history 
as a small project that show some important points about Apache project 
governance.

I’m thinking about slides with these topics, but I’m looking to the community 
to help me with some of the points to add what you know including your 
opinions. Think of this like a group history project. In the end I have one 
hour with plenty of time to be taken in translation.

(1) Apache POI 4.0 Motivations and Features
Java Jars
Remove Deprecated methods
OOXML 1.4

(2) XMLBeans 3.0.1
Entity Expansions
Taking over the codebase

(3) OOXML
Generated from XSD
Lite generated from listing of classes used in Unit Tests

(4) All of the formats
Table of formats and when they were introduced

(5) POI 3.5 - OOXML
Microsoft OpenSource Promise
Relevance
Project impact

Regards,
Dave


signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] new POI logo

[Dave Fisher]

Hi -

While I like V2, none of the docs is xlsx

Regards,
Dave

Sent from my iPhone

> On Sep 7, 2018, at 1:57 PM, Andreas Beeker  wrote:
> 
> Hi *,
> 
> Daniel (humbedooh) created a new logo for us and I don't want this issue left 
> undecided/unanswered.
> 
> So please vote for the logos and its properties:
> 
> V0) keep current version:
> https://svn.apache.org/repos/asf/poi/site/src/documentation/resources/images/project-header.svg
> V1) use Daniels first version:
> https://www.apache.org/logos/comdev-test/res/poi/poi-proposed.svg
> V2) use Daniels second version:
> http://www.apache.org/logos/comdev-test/res/poi/poi-proposed2.svg
> V3) suggest a different style - your favorite apache project logo?
> 
> C0) keep the gradient "POI" label
> C1) use the black "POI" label
> C2) suggest a different coloring style (foreground / background / frame / 
> font ...)
> 
> POLL) although we probably have more important things to do,
> we could have another logo contest
> 
> In the meantime I've really got used to the (modified) old style, therefore I 
> vote:   V0 / C0 / POLL: 0
> 
> (... but a small poll with my better half seems to be balanced ... :| )
> 
> If you want some inspiration, you can look through the other project logos at
> https://svn.apache.org/repos/asf/comdev/project-logos/originals
> 
> Thank you,
> 
> Andi
> 


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

Re: Provide alpha releases via Apache repo

[Dave Fisher]

Hi -

Release Policy is such that publishing a snapshot to a public, open repository 
is not allowed.

See http://www.apache.org/legal/release-policy.html#release-definition 


If we want to produce Alpha and Beta then we will need to VOTE on these. Or, we 
can let our users and dev know on the Mailing List where to find snapshots. We 
can put something in the RELEASE NOTES and I think there is something on the 
website. We could add a note on how to hack a user’s .m2 directory to put a 
SNAPSHOT into their maven builds.

Alternatively are we using GitBox so that the repos is on GitHub? If so then 
they can fork on GitHub to test.

Regards,
Dave

> On Sep 7, 2018, at 7:34 AM, Andreas Beeker  wrote:
> 
> Hi,
> 
> I haven't even announced 4.0.0 yet and now we've already got two issues and 
> both might have been found earlier, if the trunk would be tested by a broader 
> user base.
> 
> Wouldn't it make sense, to modify the build to upload to the Apache repo and 
> provide a note on how to use it as an additional maven repo?
> 
> Andi
> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Apache POI 4.0.0 release (RC1)

[Dave Fisher]

+1 (binding)

Thanks!

> On Aug 31, 2018, at 2:22 PM, Andreas Beeker  wrote:
> 
> Hi,
> 
> I've prepared artifacts for the release of Apache POI 4.0.0 (RC1).
> 
> The most notable changes in this release are:
> 
> - Removed support for Java 6 and 7 making Java 8 the minimum version supported
> - Unsplit packages for Jigsaw / Java 9 compatibility
> - OutputStreams aren't closed by write(OutputStream) methods anymore
> - Depends on new XMLBeans 3.0.1 release
> - New ooxml-schema version 1.4 - use via poi-ooxml-schema (preferred) or 
> ooxml-schema artifact
> - OPOIFS* classes removed / NPOIFS* classes renamed to OPOIFS*
> - new XDDF classes for shared diagram/chart functionality of X**F modules
> 
> https://dist.apache.org/repos/dist/dev/poi/4.0.0-RC1/
> 
> All tests pass. ASC files verify and SHA* are correct.
> There's no clutter in the src/bin packages.
> 
> Please vote to release the artifacts.
> The vote keeps open until we have have feedback from TIKA and a consent on 
> the govdocs results.
> 
> Planned release announcement date is open.
> 
> Here is my +1
> 
> Andi
> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Apache POI 4.0.0 release (RC1)

[Dave Fisher]

Hi -

Sent from my iPhone

> On Sep 1, 2018, at 5:30 PM, Andreas Beeker  wrote:
> 
> Hi Dave,
> 
> thank you for checking the files.
> 
> In the following, I use the tag "DIST" to refer to the artifacts uploaded to 
> the dist area and "MVN" for the artifacts uploaded to the nexus staging repo.
> 
> @1. DIST/MVN: fixed for future releases - for itself, I wouldn't rebuild all 
> the files (but can be convinced to do so), but if I need to rebuild the files 
> because of some other major problem, the LICENSE file would be fixed then too 
> ...

Check

> 
> @2. DIST/MVN: the artifact is built by "ant compile-ooxml-xsds", I've fixed 
> the build to include the legal files and fixed the artifacts

I’ll verify and then VOTE
> 
> @3a. DIST: I've fixed the typo in the release notes

Thanks.
> 
> @3b. DIST: although the timestamp is in the name of the outer archive, I 
> prefer to have no timestamp in the embedded jar - there's no difference in 
> the file coming from the global maven repo and the one we provide in the 
> prebuilt archive.
> I've fixed the reference to JDK 1.6 -> 1.8

Ok.

> 
> @3c. DIST: I don't understand the point.
> The following works for me ... I don't see a problem with the prebuilt files:

Sorry I was not clear. The build.xml is commented and producing MD5 / SHA1. 
Likely this must be until repository.apache.org is fixed.
> find . -name "*.sha256" -type f -execdir sha256sum -c {} \;
> find . -name "*.sha512" -type f -execdir sha512sum -c {} \;
> MVN: If you upload files manually to the nexus repo, the MD5 / SHA1 files are 
> created by nexus
> and because of INFRA-14923 SHA256/512 aren't allowed.

Maven and Infra are working on it.

> 
>> It looks like the main build.xml was not used by the release manager due to 
>> MD5, SHA1 being missing as the rules are changing for repository.apache.org.
> DIST: Although I've used the release-prep steps described in the release 
> guide, I've removed the MD5/SHA1 hashes and generated the SHA256/512 hashes 
> manually and hopefully fixed the build for the next release.
> 
> Best wishes,
> Andi
> 
> 
>> On 9/1/18 11:54 PM, Dave Fisher wrote:
>> Hi -
>> 
>> I have a few questions which are minor.
>> 
>> (1) NOTICE has:
>> This product contains the Piccolo XML Parser for Java
>> (http://piccolo.sourceforge.net/). Copyright 2002 Yuval Oren.
>> 
>> Was this eliminated?
>> 
>> (2) In the maven ooxml-1.4 jars the LICENSE and NOTICE are missing from 
>> META-INF
>> I cannot figure out what builds this artifact. Please fix these and I’ll 
>> double check.
>> 
>> (3) In the RELEASE-NOTES.txt
>> (a) Should this be POIFS?
>> - OPOIFS* classes removed / NPOIFS* classes renamed to OPOIFS*
>> 
>> (b) These prebuilt artifacts do not have a date.
>> - pre-built binaries containing compiled versions of all Apache POI 
>> components and documentation 
>> (poi-bin-4.0.0-20180907.zip or poi-bin-4.0.0-20180907.tar.gz)
>> - source archive you can build POI from (poi-src-4.0.0-20180907.zip or 
>> poi-src-4.0.0-20180907.tar.gz)
>> Unpack the archive and use the following command to build all POI components 
>> with Apache Ant 1.8+ and JDK 1.6 or higher:
>> 
>> (c) Wrong type of checksum. Should be SHA-512.
>> All release artifacts are accompanied by MD5 checksums and PGP signatures
>> 
>> (4) Otherwise all signatures and checksums are correct.
>> LICENSE checks
>> NOTICE checks
>> RAT Check passes
>> Ant builds from source
>> 
>> It looks like the main build.xml was not used by the release manager due to 
>> MD5, SHA1 being missing as the rules are changing for repository.apache.org.
>> 
>> Regards,
>> Dave
>> 
>>> On Aug 31, 2018, at 2:22 PM, Andreas Beeker  wrote:
>>> 
>>> Hi,
>>> 
>>> I've prepared artifacts for the release of Apache POI 4.0.0 (RC1).
>>> 
>>> The most notable changes in this release are:
>>> 
>>> - Removed support for Java 6 and 7 making Java 8 the minimum version 
>>> supported
>>> - Unsplit packages for Jigsaw / Java 9 compatibility
>>> - OutputStreams aren't closed by write(OutputStream) methods anymore
>>> - Depends on new XMLBeans 3.0.1 release
>>> - New ooxml-schema version 1.4 - use via poi-ooxml-schema (preferred) or 
>>> ooxml-schema artifact
>>> - OPOIFS* classes removed / NPOIFS* classes renamed to OPOIFS*
>>> - new XDDF classes for shared diagram/chart functionality of X**F modules
>>> 
>>> https://dist.apache.org/repos/dist/dev/poi/4.0.0-RC1/
>>> 
>>> All tests pass. ASC files verify and SHA* are correct.
>>> There's no clutter in the src/bin packages.
>>> 
>>> Please vote to release the artifacts.
>>> The vote keeps open until we have have feedback from TIKA and a consent on 
>>> the govdocs results.
>>> 
>>> Planned release announcement date is open.
>>> 
>>> Here is my +1
>>> 
>>> Andi
>>> 
>>> 
>> 
> 

Re: [VOTE] Apache POI 4.0.0 release (RC1)

[Dave Fisher]

Hi -

I have a few questions which are minor.

(1) NOTICE has:
This product contains the Piccolo XML Parser for Java
(http://piccolo.sourceforge.net/). Copyright 2002 Yuval Oren.

Was this eliminated?

(2) In the maven ooxml-1.4 jars the LICENSE and NOTICE are missing from META-INF
I cannot figure out what builds this artifact. Please fix these and 
I’ll double check.

(3) In the RELEASE-NOTES.txt
(a) Should this be POIFS?
- OPOIFS* classes removed / NPOIFS* classes renamed to OPOIFS*

(b) These prebuilt artifacts do not have a date.
 - pre-built binaries containing compiled versions of all Apache POI components 
and documentation
   (poi-bin-4.0.0-20180907.zip or poi-bin-4.0.0-20180907.tar.gz)
 - source archive you can build POI from (poi-src-4.0.0-20180907.zip or 
poi-src-4.0.0-20180907.tar.gz)
  Unpack the archive and use the following command to build all POI components 
with Apache Ant 1.8+ and JDK 1.6 or higher:

(c) Wrong type of checksum. Should be SHA-512.
All release artifacts are accompanied by MD5 checksums and PGP 
signatures

(4) Otherwise all signatures and checksums are correct.
LICENSE checks
NOTICE checks
RAT Check passes
Ant builds from source

It looks like the main build.xml was not used by the release manager due to 
MD5, SHA1 being missing as the rules are changing for repository.apache.org 
.

Regards,
Dave

> On Aug 31, 2018, at 2:22 PM, Andreas Beeker  wrote:
> 
> Hi,
> 
> I've prepared artifacts for the release of Apache POI 4.0.0 (RC1).
> 
> The most notable changes in this release are:
> 
> - Removed support for Java 6 and 7 making Java 8 the minimum version supported
> - Unsplit packages for Jigsaw / Java 9 compatibility
> - OutputStreams aren't closed by write(OutputStream) methods anymore
> - Depends on new XMLBeans 3.0.1 release
> - New ooxml-schema version 1.4 - use via poi-ooxml-schema (preferred) or 
> ooxml-schema artifact
> - OPOIFS* classes removed / NPOIFS* classes renamed to OPOIFS*
> - new XDDF classes for shared diagram/chart functionality of X**F modules
> 
> https://dist.apache.org/repos/dist/dev/poi/4.0.0-RC1/
> 
> All tests pass. ASC files verify and SHA* are correct.
> There's no clutter in the src/bin packages.
> 
> Please vote to release the artifacts.
> The vote keeps open until we have have feedback from TIKA and a consent on 
> the govdocs results.
> 
> Planned release announcement date is open.
> 
> Here is my +1
> 
> Andi
> 
> 



signature.asc
Description: Message signed with OpenPGP

XMLBeans Project Page / DOAP

[Dave Fisher]

Hi Team,

Take a look at the xmlbeans project page here: 
https://projects.apache.org/project.html?poi-xmlbeans 


I can see that there is some good information like the new release! However 
there is also some stuff that is out of date / missing.

(1) mailing list.
(2) missing legacy releases
(3) maintainer name.

I can look into making the updates tomorrow.

Regards,
Dave


signature.asc
Description: Message signed with OpenPGP

Re: Copying chart

[Dave Fisher]

Hi -

You should create a Bugzilla and attach your patch.

Regards,
Dave

> On Aug 23, 2018, at 2:29 PM, monnomiznog...@gmail.com wrote:
> 
> Guys,
> 
> You cannot ask even from advanced developers to create a chart from scratch 
> with java code or any other code type.
> 
> Copying a chart from an existing model Excel file is needed in any real life 
> reporting project.
> 
> I've tinkered with the code and found a simple way to do it. I just needed 
> access to 2 private variables in XSSFChart class.
> 
> If I paste the test code could you implement the copy chart method somewhere 
> in the library ?
> 
> Re
> FD
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Vote on XMLBeans 2.7.0-rc1 release

[Dave Fisher]

Henning wants us to use the poi areas on dist.apache.org otherwise he would 
have to make special changes one off changes. We should have an XMLBeans sub 
directory.

Regards,
Dave

Sent from my iPhone

> On Jun 10, 2018, at 11:41 AM, Andreas Beeker  wrote:
> 
>> On 6/10/18 8:21 PM, pj.fanning wrote:
>> I do have the RC jars uploaded on Nexus (they are not released yet).
>> 
>> https://repository.apache.org/content/repositories/orgapachexmlbeans-1002/org/apache/xmlbeans/xmlbeans/2.7.0-rc1/
>> 
>> Is this enough?
>> 
>> I'm not sure how to push jars into https://dist.apache.org. I used the Nexus
>> UI (https://repository.apache.org) to push the RC jars into Nexud
>> Repository.
> 
> We had a discussion about this already a while ago, but I can't find the link 
> to it now.
> Basically the src/bin packages are mandatory for an Apache release.
> 
> I would try to create and populate the xmlbeans directory in dist.apache.org 
> via SVN.
> 
> I still don't get it, why we would provide the jars in the poi area. If this 
> doesn't work now (because of missing permissions), the poi/dev area is of 
> course ok too, but on releasing it, I would like to see it under xmlbeans.
> 
> Andi
> 
> 


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

[VOTE][RESULTS] Re: publishing poi xmlbeans jars

[Dave Fisher]

Hi -

There were 6 +1 votes to take on XMLBeans as a subproject.

Alain FAGOT BEAREZ
Javen O’Neal
Dominik Stadler
Andreas Beeker
Greg Woolsey
Mark Murphy

Regards,
Dave

> On Apr 2, 2018, at 10:44 AM, Dave Fisher  wrote:
> 
> 
>> On Apr 2, 2018, at 10:23 AM, Dave Fisher > <mailto:dave2w...@comcast.net>> wrote:
>> 
>> Hi Mark,
>> 
>> We will need to make INFRA JIRA tickets with reference to the VOTE part of 
>> this thread.
>> 
>> (1) Put XMLBeans svn repos under POI LDAP.
> 
> INFRA-16278 <https://issues.apache.org/jira/browse/INFRA-16278>
>> (2) Put the website under POI LDAP
>> (3) Take admin rights on the XMLBeans JIRA.
>> 
>> Once that has been done we’ll need to then work on making our bug fixes and 
>> then going through a release.
>> 
>> Regards,
>> Dave
>> 
>>> On Apr 2, 2018, at 10:15 AM, Mark Murphy >> <mailto:jmarkmur...@gmail.com>> wrote:
>>> 
>>> So where are we on this?
>>> 
>>> On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher >> <mailto:dave2w...@comcast.net>> wrote:
>>> 
>>>> Hi -
>>>> 
>>>> Let’s get back on track.
>>>> 
>>>> We want to release XMLBeans 2.7.0 with the org.apache.xmlbeans namespace
>>>> for the benefit of all of the users who are dependent on it. If POI does
>>>> not want to do this then XMLBeans will need to go to the Incubator.
>>>> 
>>>> Should we VOTE?
>>>> 
>>>> If yes then we can ask Infra to open the JIRA and move the svn somewhere
>>>> with the history. We also ask for the return of the website to our LDAP.
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>>> On Mar 7, 2018, at 4:04 AM, Murphy, Mark >>>> <mailto:murphym...@metalexmfg.com>>
>>>> wrote:
>>>>> 
>>>>> If we do that, it needs to be in a major release because namespaces
>>>> change. If we are going to repackage to support Java 9 modules, that should
>>>> also happen at the same time.
>>>>> 
>>>>> -Original Message-
>>>>> From: pj.fanning [mailto:fannin...@yahoo.com <mailto:fannin...@yahoo.com>]
>>>>> Sent: Tuesday, March 06, 2018 4:35 PM
>>>>> To: dev@poi.apache.org <mailto:dev@poi.apache.org>
>>>>> Subject: Re: publishing poi xmlbeans jars
>>>>> 
>>>>> I have an experimental xmlbeans jar where I changed the package name to
>>>> org.apache.poi.xmlbeans just to see if it was feasible to get it build. I
>>>> also have a poi branch that successfully uses this jar.
>>>>> https://repo1.maven.org/maven2/com/github/pjfanning/ 
>>>>> <https://repo1.maven.org/maven2/com/github/pjfanning/>
>>>> xmlbeans/2.7.0-beta1/
>>>>> It should be feasible to use a commons based package name if that was
>>>> the route we went.
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html 
>>>>> <http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html>
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org 
>>>>> <mailto:dev-unsubscr...@poi.apache.org> For additional
>>>> commands, e-mail: dev-h...@poi.apache.org <mailto:dev-h...@poi.apache.org>
>>>>> 
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org 
>>>>> <mailto:dev-unsubscr...@poi.apache.org>
>>>>> For additional commands, e-mail: dev-h...@poi.apache.org 
>>>>> <mailto:dev-h...@poi.apache.org>
>>>>> 
>>>> 
>>>> 
>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: publishing poi xmlbeans jars

[Dave Fisher]

> On Apr 2, 2018, at 10:23 AM, Dave Fisher  wrote:
> 
> Hi Mark,
> 
> We will need to make INFRA JIRA tickets with reference to the VOTE part of 
> this thread.
> 
> (1) Put XMLBeans svn repos under POI LDAP.

INFRA-16278 <https://issues.apache.org/jira/browse/INFRA-16278>
> (2) Put the website under POI LDAP
> (3) Take admin rights on the XMLBeans JIRA.
> 
> Once that has been done we’ll need to then work on making our bug fixes and 
> then going through a release.
> 
> Regards,
> Dave
> 
>> On Apr 2, 2018, at 10:15 AM, Mark Murphy  wrote:
>> 
>> So where are we on this?
>> 
>> On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher  wrote:
>> 
>>> Hi -
>>> 
>>> Let’s get back on track.
>>> 
>>> We want to release XMLBeans 2.7.0 with the org.apache.xmlbeans namespace
>>> for the benefit of all of the users who are dependent on it. If POI does
>>> not want to do this then XMLBeans will need to go to the Incubator.
>>> 
>>> Should we VOTE?
>>> 
>>> If yes then we can ask Infra to open the JIRA and move the svn somewhere
>>> with the history. We also ask for the return of the website to our LDAP.
>>> 
>>> Regards,
>>> Dave
>>> 
>>>> On Mar 7, 2018, at 4:04 AM, Murphy, Mark 
>>> wrote:
>>>> 
>>>> If we do that, it needs to be in a major release because namespaces
>>> change. If we are going to repackage to support Java 9 modules, that should
>>> also happen at the same time.
>>>> 
>>>> -Original Message-
>>>> From: pj.fanning [mailto:fannin...@yahoo.com]
>>>> Sent: Tuesday, March 06, 2018 4:35 PM
>>>> To: dev@poi.apache.org
>>>> Subject: Re: publishing poi xmlbeans jars
>>>> 
>>>> I have an experimental xmlbeans jar where I changed the package name to
>>> org.apache.poi.xmlbeans just to see if it was feasible to get it build. I
>>> also have a poi branch that successfully uses this jar.
>>>> https://repo1.maven.org/maven2/com/github/pjfanning/
>>> xmlbeans/2.7.0-beta1/
>>>> It should be feasible to use a commons based package name if that was
>>> the route we went.
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>>>> 
>>>> -
>>>> 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
>>>> 
>>> 
>>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: publishing poi xmlbeans jars

[Dave Fisher]

Hi Mark,

We will need to make INFRA JIRA tickets with reference to the VOTE part of this 
thread.

(1) Put XMLBeans svn repos under POI LDAP.
(2) Put the website under POI LDAP
(3) Take admin rights on the XMLBeans JIRA.

Once that has been done we’ll need to then work on making our bug fixes and 
then going through a release.

Regards,
Dave

> On Apr 2, 2018, at 10:15 AM, Mark Murphy  wrote:
> 
> So where are we on this?
> 
> On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher  wrote:
> 
>> Hi -
>> 
>> Let’s get back on track.
>> 
>> We want to release XMLBeans 2.7.0 with the org.apache.xmlbeans namespace
>> for the benefit of all of the users who are dependent on it. If POI does
>> not want to do this then XMLBeans will need to go to the Incubator.
>> 
>> Should we VOTE?
>> 
>> If yes then we can ask Infra to open the JIRA and move the svn somewhere
>> with the history. We also ask for the return of the website to our LDAP.
>> 
>> Regards,
>> Dave
>> 
>>> On Mar 7, 2018, at 4:04 AM, Murphy, Mark 
>> wrote:
>>> 
>>> If we do that, it needs to be in a major release because namespaces
>> change. If we are going to repackage to support Java 9 modules, that should
>> also happen at the same time.
>>> 
>>> -Original Message-
>>> From: pj.fanning [mailto:fannin...@yahoo.com]
>>> Sent: Tuesday, March 06, 2018 4:35 PM
>>> To: dev@poi.apache.org
>>> Subject: Re: publishing poi xmlbeans jars
>>> 
>>> I have an experimental xmlbeans jar where I changed the package name to
>> org.apache.poi.xmlbeans just to see if it was feasible to get it build. I
>> also have a poi branch that successfully uses this jar.
>>> https://repo1.maven.org/maven2/com/github/pjfanning/
>> xmlbeans/2.7.0-beta1/
>>> It should be feasible to use a commons based package name if that was
>> the route we went.
>>> 
>>> 
>>> 
>>> --
>>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>>> 
>>> -
>>> 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
>>> 
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: publishing poi xmlbeans jars

[Dave Fisher]

Hi -

Let’s get back on track.

We want to release XMLBeans 2.7.0 with the org.apache.xmlbeans namespace for 
the benefit of all of the users who are dependent on it. If POI does not want 
to do this then XMLBeans will need to go to the Incubator.

Should we VOTE?

If yes then we can ask Infra to open the JIRA and move the svn somewhere with 
the history. We also ask for the return of the website to our LDAP.

Regards,
Dave

> On Mar 7, 2018, at 4:04 AM, Murphy, Mark  wrote:
> 
> If we do that, it needs to be in a major release because namespaces change. 
> If we are going to repackage to support Java 9 modules, that should also 
> happen at the same time.
> 
> -Original Message-
> From: pj.fanning [mailto:fannin...@yahoo.com]
> Sent: Tuesday, March 06, 2018 4:35 PM
> To: dev@poi.apache.org
> Subject: Re: publishing poi xmlbeans jars
> 
> I have an experimental xmlbeans jar where I changed the package name to 
> org.apache.poi.xmlbeans just to see if it was feasible to get it build. I 
> also have a poi branch that successfully uses this jar.
> https://repo1.maven.org/maven2/com/github/pjfanning/xmlbeans/2.7.0-beta1/
> It should be feasible to use a commons based package name if that was the 
> route we went.
> 
> 
> 
> --
> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
> 
> -
> 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
> 



signature.asc
Description: Message signed with OpenPGP

NABBLE Re: publishing poi xmlbeans jars

[Dave Fisher]

My ISP suppresses Nabble emails. They are bounced - something to do with DKIM.

Sent from my iPhone

> On Mar 6, 2018, at 8:47 AM, Mark Murphy  wrote:
> 
> I have a question. If we bring it into POI as a sub-project, do we have to
> change its namespace? If it were added to Commons, would it have to change
> its namespace?
> 
> Here is my rational for restoring XMLBeans to an active project or
> sub-project.
> 
> XMLBeans is a stable project. It doesn't need much new work, but as new
> Java releases occur, and as technologies change, the need to update
> XMLBeans and keep it current with technology becomes apparent. In the attic
> it can not get these necessary refreshes, and projects which rely on it are
> forced to look elsewhere for the solution XMLBeans provides. Keeping
> XMLBeans alive, not as a zombie, but as a living mature project means that
> those projects that depend on it can continue productively depending on
> XMLBeans as technology advances. The POI project is willing to look after
> XMLBeans since we see the benefit of maintaining it vs. dropping it for
> some other yet to be determined XML solution, both to our own project and
> to others.
> 
> After looking over at Commons, it almost looks like that is the appropriate
> place to put it as long as we can do so without changing the namespace.
> 
>> On Mon, Mar 5, 2018 at 4:04 PM, pj.fanning  wrote:
>> 
>> My attempt at a short description of why we want to be able to patch
>> xmlbeans.
>> 
>> Apache Poi has a significant dependency on XmlBeans. There would need to be
>> a lot of work done to switch to an alternative (and this might happen at a
>> later date). We have identified a few issues in XmlBeans that we would like
>> to be fix and would like to be able to fix other high priority issues that
>> might be reported in future.
>> 
>> 
>> 
>> --
>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>> 
>> -
>> 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: publishing poi xmlbeans jars

[Dave Fisher]

Sent from my iPhone

> On Mar 6, 2018, at 8:47 AM, Mark Murphy  wrote:
> 
> I have a question. If we bring it into POI as a sub-project, do we have to
> change its namespace? If it were added to Commons, would it have to change
> its namespace?

In POI we would do as we wish. We would keep it as org.apache.xmlbeans. Commons 
can likely do the same but that is their PMC. We would need to negotiate with 
Commons as a PMC we can act now.

> 
> Here is my rational for restoring XMLBeans to an active project or
> sub-project.
> 
> XMLBeans is a stable project. It doesn't need much new work, but as new
> Java releases occur, and as technologies change, the need to update
> XMLBeans and keep it current with technology becomes apparent. In the attic
> it can not get these necessary refreshes, and projects which rely on it are
> forced to look elsewhere for the solution XMLBeans provides. Keeping
> XMLBeans alive, not as a zombie, but as a living mature project means that
> those projects that depend on it can continue productively depending on
> XMLBeans as technology advances. The POI project is willing to look after
> XMLBeans since we see the benefit of maintaining it vs. dropping it for
> some other yet to be determined XML solution, both to our own project and
> to others.
> 
> After looking over at Commons, it almost looks like that is the appropriate
> place to put it as long as we can do so without changing the namespace.

That’s the question.



> 
>> On Mon, Mar 5, 2018 at 4:04 PM, pj.fanning  wrote:
>> 
>> My attempt at a short description of why we want to be able to patch
>> xmlbeans.
>> 
>> Apache Poi has a significant dependency on XmlBeans. There would need to be
>> a lot of work done to switch to an alternative (and this might happen at a
>> later date). We have identified a few issues in XmlBeans that we would like
>> to be fix and would like to be able to fix other high priority issues that
>> might be reported in future.

Great. We should mention the issues as we resurrect XMLBeans.

Regards,
Dave

>> 
>> 
>> 
>> --
>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>> 
>> -
>> 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: publishing poi xmlbeans jars

[Dave Fisher]

Hi -

POI devs. Should we discuss quickly what it would mean to take on XMLBeans as a 
product of POI?

(1) Move code to a POI repository.
(2) Build.
(3) Get control of website.
(4) Release.

Alternatively others have suggested the following:
(A) Take XMLBeans to the Incubator doing the move and asking dependent projects 
if any dev would like to participate.
(B) Take XMLBeans to the Commons and make it a sub-module of Commons.

I think we have some urgency to move forward. It would help to have a 25 word 
description about why the project absolutely needs to do this.

Let me know.

Regards,
Dave

> On Mar 2, 2018, at 3:01 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> I declared Lazy Consensus on Board@ for POI to take the XMLBeans product. So 
> far we have two positive responses.
> 
> Do we have LAZY CONSENSUS?
> 
> FYI - I did a full search of lists.apache.org <http://lists.apache.org/> for 
> mentions of XMLBeans through sometime in August 2017
> 
> Here are the projects:
> 
> XMLBeans
> ———
> ODE
> NetBeans
> Axis
> Camel
> UIMA
> CXF
> Struts (2.3)
> Nifi
> Axis
> ManifoldCF
> Nutch
> Maven(?)
> WS
> OpenMeetings
> Buildr
> Synapse
> OpenWebBeans
> ServiceMix
> JUDDI (2.4)
> Flink
> Sling (2.3)
> 
> POI
> ——
> Nifi
> Solr
> Zika
> ManifoldCF
> ServiceMix
> 
> I think we should continue to build and release a new version of XMLBeans 
> 2.7.0
> 
> When we do so we update the website.
> 
> Meanwhile it would be fair to let all of these PMCs know our plan and why 
> this is needed. They can then help if they would like.
> 
> BTW - The XMLBeans project used JIRA ….
> 
> Regards,
> Dave
> 
>> On Mar 2, 2018, at 11:50 AM, Mark Murphy > <mailto:jmarkmur...@gmail.com>> wrote:
>> 
>> That will make things a lot easier. Thanks Dave.
>> 
>> On Fri, Mar 2, 2018 at 2:45 PM, Dave Fisher > <mailto:dave2w...@comcast.net>> wrote:
>> 
>>> Hi -
>>> 
>>> Given the Attic position and the mention of Royale. I will just take this
>>> to the Board.
>>> 
>>> They could take a resolution moving directly to POI. I will ask for this
>>> first.
>>> 
>>> Regards,
>>> Dave
>>> 
>>>> On Mar 2, 2018, at 11:35 AM, Dave Fisher >>> <mailto:dave2w...@comcast.net>> wrote:
>>>> 
>>>> Hi -
>>>> 
>>>> As both an IPMC member and as a POI PMC member I would prefer that we
>>> direct to POI.
>>>> 
>>>> I think we (POI) need to take over the XMLBeans Product.
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>>> On Mar 2, 2018, at 11:32 AM, Mark Murphy >>>> <mailto:jmarkmur...@gmail.com>> wrote:
>>>>> 
>>>>> So Oracle is removing JAXB from Java SE, Depricated in v9, to be
>>> removed in
>>>>> v11. I think we are stuck with XMLBeans for a while anyway. POI can
>>> sponsor
>>>>> XMLBeans which can then be put into incubation. At that point we can
>>> make
>>>>> updates. At some point XMLBeans emerges from incubation to be either a
>>>>> sub-project of POI, or it's own TLP. That need not be a big issue. We
>>> just
>>>>> need to keep it from being terminated. It isn't bad to be in Incubation.
>>>>> NetBeans is in Incubation. It will just stay there until we figure out
>>> how
>>>>> to manage it. If we take it over, we already have a community. The
>>>>> important part is to get it to a point where we can make updates to it.
>>> I
>>>>> think just making a fork for us, and giving it a new namespace could
>>> cause
>>>>> problems down the road with other projects that use POI and XMLBeans.
>>>>> 
>>>>> On Fri, Mar 2, 2018 at 9:45 AM, pj.fanning >>>> <mailto:fannin...@yahoo.com>> wrote:
>>>>> 
>>>>>> http://mail-archives.apache.org/mod_mbox/attic-general/ 
>>>>>> <http://mail-archives.apache.org/mod_mbox/attic-general/>
>>> 201803.mbox/browser
>>>>>> 
>>>>>> I think we could spend a lot of time on the attic approach.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866 
>>>>>> <http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866>.
>>> html
>>>>>> 
>>>>>> -
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org 
>>>>>> <mailto:dev-unsubscr...@poi.apache.org>
>>>>>> For additional commands, e-mail: dev-h...@poi.apache.org 
>>>>>> <mailto:dev-h...@poi.apache.org>
>>>>>> 
>>>>>> 
>>>> 
>>> 
>>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: publishing poi xmlbeans jars

[Dave Fisher]

Hi -

I declared Lazy Consensus on Board@ for POI to take the XMLBeans product. So 
far we have two positive responses.

Do we have LAZY CONSENSUS?

FYI - I did a full search of lists.apache.org <http://lists.apache.org/> for 
mentions of XMLBeans through sometime in August 2017

Here are the projects:

XMLBeans
———
ODE
NetBeans
Axis
Camel
UIMA
CXF
Struts (2.3)
Nifi
Axis
ManifoldCF
Nutch
Maven(?)
WS
OpenMeetings
Buildr
Synapse
OpenWebBeans
ServiceMix
JUDDI (2.4)
Flink
Sling (2.3)

POI
——
Nifi
Solr
Zika
ManifoldCF
ServiceMix

I think we should continue to build and release a new version of XMLBeans 2.7.0

When we do so we update the website.

Meanwhile it would be fair to let all of these PMCs know our plan and why this 
is needed. They can then help if they would like.

BTW - The XMLBeans project used JIRA ….

Regards,
Dave

> On Mar 2, 2018, at 11:50 AM, Mark Murphy  wrote:
> 
> That will make things a lot easier. Thanks Dave.
> 
> On Fri, Mar 2, 2018 at 2:45 PM, Dave Fisher  wrote:
> 
>> Hi -
>> 
>> Given the Attic position and the mention of Royale. I will just take this
>> to the Board.
>> 
>> They could take a resolution moving directly to POI. I will ask for this
>> first.
>> 
>> Regards,
>> Dave
>> 
>>> On Mar 2, 2018, at 11:35 AM, Dave Fisher  wrote:
>>> 
>>> Hi -
>>> 
>>> As both an IPMC member and as a POI PMC member I would prefer that we
>> direct to POI.
>>> 
>>> I think we (POI) need to take over the XMLBeans Product.
>>> 
>>> Regards,
>>> Dave
>>> 
>>>> On Mar 2, 2018, at 11:32 AM, Mark Murphy  wrote:
>>>> 
>>>> So Oracle is removing JAXB from Java SE, Depricated in v9, to be
>> removed in
>>>> v11. I think we are stuck with XMLBeans for a while anyway. POI can
>> sponsor
>>>> XMLBeans which can then be put into incubation. At that point we can
>> make
>>>> updates. At some point XMLBeans emerges from incubation to be either a
>>>> sub-project of POI, or it's own TLP. That need not be a big issue. We
>> just
>>>> need to keep it from being terminated. It isn't bad to be in Incubation.
>>>> NetBeans is in Incubation. It will just stay there until we figure out
>> how
>>>> to manage it. If we take it over, we already have a community. The
>>>> important part is to get it to a point where we can make updates to it.
>> I
>>>> think just making a fork for us, and giving it a new namespace could
>> cause
>>>> problems down the road with other projects that use POI and XMLBeans.
>>>> 
>>>> On Fri, Mar 2, 2018 at 9:45 AM, pj.fanning  wrote:
>>>> 
>>>>> http://mail-archives.apache.org/mod_mbox/attic-general/
>> 201803.mbox/browser
>>>>> 
>>>>> I think we could spend a lot of time on the attic approach.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.
>> html
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
>>>>> For additional commands, e-mail: dev-h...@poi.apache.org
>>>>> 
>>>>> 
>>> 
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: publishing poi xmlbeans jars

[Dave Fisher]

Hi -

Given the Attic position and the mention of Royale. I will just take this to 
the Board.

They could take a resolution moving directly to POI. I will ask for this first.

Regards,
Dave

> On Mar 2, 2018, at 11:35 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> As both an IPMC member and as a POI PMC member I would prefer that we direct 
> to POI.
> 
> I think we (POI) need to take over the XMLBeans Product.
> 
> Regards,
> Dave
> 
>> On Mar 2, 2018, at 11:32 AM, Mark Murphy  wrote:
>> 
>> So Oracle is removing JAXB from Java SE, Depricated in v9, to be removed in
>> v11. I think we are stuck with XMLBeans for a while anyway. POI can sponsor
>> XMLBeans which can then be put into incubation. At that point we can make
>> updates. At some point XMLBeans emerges from incubation to be either a
>> sub-project of POI, or it's own TLP. That need not be a big issue. We just
>> need to keep it from being terminated. It isn't bad to be in Incubation.
>> NetBeans is in Incubation. It will just stay there until we figure out how
>> to manage it. If we take it over, we already have a community. The
>> important part is to get it to a point where we can make updates to it. I
>> think just making a fork for us, and giving it a new namespace could cause
>> problems down the road with other projects that use POI and XMLBeans.
>> 
>> On Fri, Mar 2, 2018 at 9:45 AM, pj.fanning  wrote:
>> 
>>> http://mail-archives.apache.org/mod_mbox/attic-general/201803.mbox/browser
>>> 
>>> I think we could spend a lot of time on the attic approach.
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
>>> For additional commands, e-mail: dev-h...@poi.apache.org
>>> 
>>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: publishing poi xmlbeans jars

[Dave Fisher]

Hi -

As both an IPMC member and as a POI PMC member I would prefer that we direct to 
POI.

I think we (POI) need to take over the XMLBeans Product.

Regards,
Dave

> On Mar 2, 2018, at 11:32 AM, Mark Murphy  wrote:
> 
> So Oracle is removing JAXB from Java SE, Depricated in v9, to be removed in
> v11. I think we are stuck with XMLBeans for a while anyway. POI can sponsor
> XMLBeans which can then be put into incubation. At that point we can make
> updates. At some point XMLBeans emerges from incubation to be either a
> sub-project of POI, or it's own TLP. That need not be a big issue. We just
> need to keep it from being terminated. It isn't bad to be in Incubation.
> NetBeans is in Incubation. It will just stay there until we figure out how
> to manage it. If we take it over, we already have a community. The
> important part is to get it to a point where we can make updates to it. I
> think just making a fork for us, and giving it a new namespace could cause
> problems down the road with other projects that use POI and XMLBeans.
> 
> On Fri, Mar 2, 2018 at 9:45 AM, pj.fanning  wrote:
> 
>> http://mail-archives.apache.org/mod_mbox/attic-general/201803.mbox/browser
>> 
>> I think we could spend a lot of time on the attic approach.
>> 
>> 
>> 
>> 
>> --
>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
>> For additional commands, e-mail: dev-h...@poi.apache.org
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: publishing poi xmlbeans jars

[Dave Fisher]

You might point out how widely used POI is include Tika and Solr as consumers 
of POI/XMLBeans.

Also taking it out of the Attic was previously suggested by others...

Regards,
Dave

Sent from my iPhone

> On Feb 28, 2018, at 12:41 PM, Nick Burch  wrote:
> 
>> On Wed, 28 Feb 2018, pj.fanning wrote:
>> http://mail-archives.apache.org/mod_mbox/attic-general/201802.mbox/%3C1519744891.257410.1285160920.6801732D%40webmail.messagingengine.com%3E
>> 
>> Looks like we're not going to make much progress on resurrecting Apache
>> XMLBeans.
> 
> The big problem is with Maven users:
> * Anyone using Maven to depend on xmlbeans explicitly won't know to
>   switch to org.apache.poi:xmlbeans to get the fixes
> * Maven won't know that the the old 2.6.0 release and our new fix are
>   the same thing, so will happy pull both in
> 
> The smaller problem is by-hand-dependency users - the number of people on 
> stackoverflow or the mailing list who try combining old and new POI jars + 
> get stuck is rather high - so the chances of those people getting it right is 
> near zero
> 
> As long as all existing XMLBeans unit tests pass, it should be safe 
> (+sensible) for existing xmlbeans users to upgrade to our fixed version.
> 
> 
> Could someone help work up a good explanation of the jar-hell + maven issues, 
> so we can go back to the attic with a reason why we should be allowed to do 
> it? (My reading of the attic wasn't a flat-out no, just a "no unless you have 
> a good reason otherwise")
> 
> 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: ***UNCHECKED*** RE: adding dependencies on h2 and mockito

[Dave Fisher]

Hi -

We need to be really careful not to make OOXML deployments larger.

Why is H2, a database engine, being considered?

Regards,
Dave

Sent from my iPhone

> On Jan 26, 2018, at 11:55 AM, Alain FAGOT BÉAREZ  wrote:
> 
> You might have heard of Hypersonic SQL, some 10 years ago. H2 is the second 
> version thereof. 
> 
> ⁣Gesendet mit BlueMail ​
> 
> 
>  Originale Nachricht 
> Von: Greg Woolsey 
> Gesendet: Fri Jan 26 16:42:44 GMT-03:00 2018
> An: POI Developers List 
> Betreff: Re: ***UNCHECKED*** RE: adding dependencies on h2 and mockito
> 
> Total dependency size is important to my deployment, and probably others.
> I don't use SXSSF at all, and would not need/want the dependency (which
> I've never heard of in 20 years of database and Java development, which is
> strange to me, but irrelevant).  My preference is to make it optional, even
> though it's more work to code.  Default would be the current behavior,
> which works for almost everyone, apparently, and an option would be to
> enable this behavior and manage the package availability externally.
> 
> I suppose one could manually exclude the package as well, if SXSSF isn't
> used at all, since Java wouldn't try to load the classes unless a class
> referencing them was loaded, but that behavior is always subject to change
> and should not be relied upon.  Plus I wouldn't want to impose that on
> existing users who don't need/want it.
> 
>> On Fri, Jan 26, 2018 at 4:47 AM pj.fanning  wrote:
>> 
>> I could make h2 a `provided` dependency in our poi-ooxml pom.
>> The use of h2 is opt-in in the new code in my PR but I'll need to refactor
>> the code to allow our code not to throw ClassNotFoundException if the h2
>> classes are not on the runtime classpath. This is do-able but my concern is
>> that this is difficult to automate tests for (checking the code works when
>> the h2 jar is available and when it is not).
>> 
>> https://mvnrepository.com/artifact/com.h2database/h2 is very common
>> dependency, so my preference would be to have the explicit dependency from
>> poi-ooxml on h2 - but I'll go with whatever the consensus is.
>> 
>> 
>> 
>> --
>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>> 
>> -
>> 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: XMLBeans in 4.0.0 release

[Dave Fisher]

Hi -

I think that releasing a package with right XMLbean path in Maven Central might 
be best for our users. Finding that they have issues with old XMLbeans might be 
subtly difficult. I could be wrong.

Regards,
Dave

Sent from my iPhone

> On Jan 9, 2018, at 12:28 AM, Nick Burch  wrote:
> 
>> On Mon, 8 Jan 2018, pj.fanning wrote:
>> I understand the desire to replace XMLBeans altogether but I don't think we 
>> have enough developer time available to do this in the 4.0.0 time frame.
> 
> Given the amount of work that'd take, and a desire for other features and 
> bugs to be worked on in the mean time, I'd agree!
> 
> 
>> 1. Keep Apache XMLBeans 2.6.0 dependency - if users run into issues with
>> XMLBeans, they can choose to configure their own project builds to swap in
>> https://github.com/pjfanning/xmlbeans instead.
> 
> I don't think that's a good new-user experience (nor upgrading user 
> experience), the "default" they're pushed towards is known to have problems 
> and they'll likely struggle with them for a while before discovering the fix
> 
>> 2. Make https://github.com/pjfanning/xmlbeans the default dependency
>> 3. Delay POI 4.0.0 release until we can get an adequate replacement for
>> XMLBeans.
> 
> I'd suggest we either go back to the Attic PMC and do a fixed release of 
> XMLBeans there (based on your fixed github fork), or fork XMLBeans within POI 
> (based on your fixed fork) and release a fixed release ourselves.
> 
> Either way, we then have POI depend on a known-fixed rather than known-broken 
> jar by default!
> 
> 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: [DISCUSS] Getting a fixed version of XMLBeans

[Dave Fisher]

Hi

Sent from my iPhone

> On Nov 9, 2017, at 1:01 PM, Dominik Stadler  wrote:
> 
> Hi,
> 
> the initial discussion showed a few possible routes. I would like to
> discuss the options a bit more, probably followed by a vote to see which
> option has the majority.
> 
> I currently see the following possibilities:
> 
> a) Fork XMLBeans with a different name outside of Apache and upload a fixed
> version, just like PJ already did, only some more renaming would probably
> be necessary
> 
> b) Include the source of XMLBeans with POI and release fixes from there
> 
> c) As b), but change the code so different package names and jar-names are
> used to avoid colliding with the "official" version
> 
> d) Do nothing with XMLBeans and invest all the time for replacing XMLBeans
> soon

e) take XMLBeans out of the attic. Fix the bugs and make maintenance releases 
as 2.7, 2.8, etc. This would be an official version. Probably needs a board 
resolution.

> 
> Any thoughts? Other options?
> 
> Thanks... Dominik.


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

Re: Moving to Git

[Dave Fisher]

Hi -

Infrastructure is just now getting something called GitBox going which should 
help with integration of Apache LDAP etcetera. They are also working on a JIRA 
service ticket improvement.

Javen it might be good if you reached out to Infrastructure and a clear 
explanation of how to properly change and what that means for SVN and other 
workflows like site building and ant builds.

Regards,
Dave

> On Jun 28, 2017, at 7:24 AM, Allison, Timothy B.  wrote:
> 
> Y, we did it on Tika...in fact, we also jumped to github directly.  It was 
> great.  Not sure it dramatically increased contributions, but it does feel 
> modern...
> 
> -Original Message-
> From: Greg Woolsey [mailto:greg.wool...@gmail.com]
> Sent: Wednesday, June 28, 2017 9:37 AM
> To: POI Developers List 
> Subject: Re: Moving to Git
> 
> I'd be all for that. Not particularly proficient, but I can Google like 
> everyone else.
> 
> On Wed, Jun 28, 2017, 01:35 Javen O'Neal  wrote:
> 
>> A fair increase in Github PR's. Having a git repo might increase the
>> number of (good) PR's we get, as that seems to be where a lot of
>> developers are at.
>> 
>> Then we'd be able to have github show merged PR's with credit to the
>> author rather than closed PR's.
>> 
>> Looks like some of Apache Commons is going through the transition
>> right now.
>> https://wiki.apache.org/commons/MovingToGit
>> 
>> There's a lot of other Apache projects that have made the change that
>> could help us along too.
>> 
>> -
>> 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
> 



signature.asc
Description: Message signed with OpenPGP

Re: POI @ ApacheCon

[Dave Fisher]

I arrive as well

Sent from my iPhone

> On May 15, 2017, at 7:27 AM, Allison, Timothy B.  wrote:
> 
> I'll arrive tonight.  See you there!
> 
> -Original Message-
> From: David North [mailto:dno...@apache.org] 
> Sent: Monday, May 15, 2017 10:20 AM
> To: POI Developers List 
> Subject: POI @ ApacheCon
> 
> Who else is in Miami for ApacheCon? Do we have critical mass for an in-person 
> chat over breakfast/beer/... ?
> 
> --
> David North | www.dnorth.net
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional 
> commands, e-mail: dev-h...@poi.apache.org
> 
> 
> ТÐÐ¥FòVç7V'67&–&RÂRÖÖ–âFWb×Vç7V'67&–&Tö’æ6†Ræ÷&pФf÷"FF—F–öæÂ6öÖÖæG2ÂRÖÖ–âFWbÖ†VÇö’æ6†Ræ÷&pÐ
>  Ð


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

Re: [RESULT] [VOTE] Apache POI 3.14-final release (RC1)

[Dave Fisher]

I agree with Nick. Changes to the OOXML schema jars are a significant change.

Considering why the lite jar was created a metric on the size change of that 
jar would be helpful as well.

Regards,
Dave

Sent from my iPhone

> On Mar 6, 2016, at 3:47 AM, Nick Burch  wrote:
> 
>> On Sun, 6 Mar 2016, Andreas Beeker wrote:
>> The schema updates were already in POI 3.14-beta1 ... therefore I omit the 
>> following:
>> Excel: New version of ooxml-schema and ooxml-security jars to incorporate 
>> newer code
> 
> Since not everyone tracks our betas, and it's a noticable change, I'd suggest 
> leaving this in the FINAL changelog
> 
> 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: ODF Explorer

[Dave Fisher]

Hi Ian, 

Your tool and the compliments it is receiving are interesting.

Including poi and Yegor. What do people  think?

Regards,
Dave

Sent from my iPhone

> On Aug 29, 2015, at 8:53 PM, Ian C  wrote:
> 
> Hi Peter,
> 
> 
>> On Sun, Aug 30, 2015 at 1:16 AM, Peter Kelly  wrote:
>> Ok I just figured out the cause - it was trying to write a file to the 
>> ‘input’ directory (under the ODFExplorer directory where I had run 
>> ‘npm start’) but that directory did not exist. After I created that, I 
>> was able to upload files successfully and have them processed.
>> 
> great that you got it working. I will need to have that directory
> created, I just repeated the issue. Gosh it's annoying to mess up
> these little things.
> 
>> I love the tree widget you’ve got in the UI for navigating the element 
>> coverage - I don’t think I’ve seen something quite like this before for 
>> summarising information. The closest I can think of is DiskInventoryX for 
>> mac which shows how much data is used by various directories on your hard 
>> disk. But the idea of applying it to XML structures is really cool.
>> 
> Pleased you like the UI. I'm not a UI designer by a long shot, and
> just cobble together bits that work. Like dot for the graphs.
> 
>> I’m thinking it might be useful for us to have a web app which allows us 
>> to view the structure of individual documents like this, for inspection 
>> purposes. Once I’ve gotten Flat (my parser engine) into a state where it 
>> can output XML this should be doable, and would also help visualise the tree 
>> structure of files in non-XML formats, like Markdown.
> 
> Absolutely, having bashed the thing into life for this ODF case I want
> to try to make it more general.
> 
>> 
>> The use of a web UI based on node/angular is a good idea, as it’s a nice 
>> way of getting a UI that works in a cross platform manner, and can also be 
>> deployed on a server. This also strikes me as being relevant for the 
>> Corinthia web app. My personal preference is for Python on the server side, 
>> but only because that’s what I use in my day job - node is good also and 
>> ultimately either choice is fine and mainly depends on whoeverâHi Peter,
> 
> 
>> On Sun, Aug 30, 2015 at 1:16 AM, Peter Kelly  wrote:
>> Ok I just figured out the cause - it was trying to write a file to the 
>> ‘input’ directory (under the ODFExplorer directory where I had run 
>> ‘npm start’) but that directory did not exist. After I created that, I 
>> was able to upload files successfully and have them processed.
>> 
> great that you got it working. I will need to have that directory
> created, I just repeated the issue. Gosh it's annoying to mess up
> these little things.
> 
>> I love the tree widget you’ve got in the UI for navigating the element 
>> coverage - I don’t think I’ve seen something quite like this before for 
>> summarising information. The closest I can think of is DiskInventoryX for 
>> mac which shows how much data is used by various directories on your hard 
>> disk. But the idea of applying it to XML structures is really cool.
>> 
> Pleased you like the UI. I'm not a UI designer by a long shot, and
> just cobble together bits that work. Like dot for the graphs.
> 
>> I’m thinking it might be useful for us to have a web app which allows us 
>> to view the structure of individual documents like this, for inspection 
>> purposes. Once I’ve gotten Flat (my parser engine) into a state where it 
>> can output XML this should be doable, and would also help visualise the tree 
>> structure of files in non-XML formats, like Markdown.
> 
> Absolutely, having bashed the thing into life for this ODF case I want
> to try to make it more general.
> 
>> 
>> The use of a web UI based on node/angular is a good idea, as it’s a nice 
>> way of getting a UI that works in a cross platform manner, and can also be 
>> deployed on a server. This also strikes me as being relevant for the 
>> Corinthia web app. My personal preference is for Python on the server side, 
>> but only because that’s what I use in my day job - node is good also and 
>> ultimately either choice is fine and mainly depends on whoever’s implement 
>> it.
>> 
>> Regarding the graphs where you’ve used dot, I suggest having a look at 
>> some of the graph-based visualisations that d3 provides (I see you’re 
>> using d3 for some stuff already, but the XPath graph is in dot). I saw some 
>> force directed layout visualisations a colleague of mine did for a project 
>> we’re working on - I’ll have to check what he was using for that.
> 
> I did look at using d3 (which is a great tool) but couldn't quite get
> it to do what I wanted. And redrawing to filter the graphs and
> managing it in Javascript was all to hard. I reprocess the underlying
> JSON and regenerate the dot and have GraphViz regenerate the diagram.
> 
>> 
>> All up, looks good so far. I’m keen to see the code for the Java side of 
>> th

Fwd: A nice OOXML reference site

[Dave Fisher]

FYI. Corinthia is an Incubator podling that may be of interest to the POI 
community.

Regards,
Dave

Sent from my iPhone

Begin forwarded message:

> From: Peter Kelly 
> Date: August 13, 2015 at 1:11:35 PM PDT
> To: d...@corinthia.incubator.apache.org
> Subject: A nice OOXML reference site
> Reply-To: d...@corinthia.incubator.apache.org
> 
> I just came across this site, which appears to be relatively recent:
> 
> http://officeopenxml.com
> 
> It provides a *much* more easily readable explanation of the various OOXML 
> constructs than the specification itself.
> 
> —
> Dr Peter M. Kelly
> pmke...@apache.org
> 
> PGP key: http://www.kellypmk.net/pgp-key 
> (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
> 

Re: Another beta?

[Dave Fisher]

Hi NIck,

I think you hang out on the Tika dev list. Do you know when the next major 
release of Tika is coming? When do we need to release to be included?

If I knew that it might help get some daylight cycles on POI.

Regards,
Dave

On Jan 14, 2014, at 9:30 AM, Nick Burch wrote:

> Hi All
> 
> It has been a while since our last beta, and the change list 
>  seems to show we've fixed rather a lot 
> of bugs since 3.10 beta 2. However, we still have some community contributed 
> patches that haven't been applied, and a few bugs that I've heard various 
> committers mention they want to fix first.
> 
> What do people think about doing a 3.10 beta 3 release basically now, then 
> trying for 3.10 final in a month or so?
> 
> And would anyone like to volunteer to release manager the new beta? :)
> 
> 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: [Vote] Andreas Beeker as new POI Committer + PMC member

[Dave Fisher]

+1 from me.

Regards,
Dave

On Dec 18, 2013, at 10:55 PM, Yegor Kozlov wrote:

> Hi All
> 
> Andreas Beeker  has contributed a number of
> excellent patches and investigations [1].
> His code seems to follow our standards and I think he'd be a great addition
> to the POI committers list.
> 
> please vote:
> +1 - Make Andreas a committer
> 0  - I don't mind either way
> -1 - I'd rather Andreas wasn't a committer
> 
> Vote will be open until Monday, Dec 23rd. All community members are welcome
> (and encouraged!) to vote, as per normal Apache rules at least 3 existing
> PMC members need to +1 for the vote to be binding
> 
> I'm +1!
> 
> Yegor
> 
> [1] Andreas's patches
> 
> Bug 53176 Auto shapes render problem in pptx files
> Bug 49658 HSSFSHeet after insert EMF,DIB,VMF format Image,Can't open xls
> for Excel 2007
> Bug 55579 [PATCH] Patch for add/embed OLE objects into HSLF
> Bug 55578 New: [PATCH] Patch for embedding OLE1.0 package
> Bug 55579 New: [PATCH] Patch for add/embed OLE objects into HSLF
> Bug 55560 New: [PATCH] Patch for hiding slides
> Bug 48593 Multiple Saves Causes Slide Corruption
> Bug 49237 java.lang.IndexOutOfBoundsException on row.getRowStyle()
> Bug 52400 TNEF parsing unstable
> Bug 53475 Support for more DOCX encryption versions


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

Re: Please remove my file from your svn

[Dave Fisher]

Hi Chris,

I am on both the Apache POI and the Apache OpenOffice PMC. Action will be taken.

As a producer of PPT and PPTX files along with other Office documents we have 
always done our best to try to consume documents created by any producer 
including OpenOffice.org. I wonder if a PPT produced by the current Apache 
OpenOffice 4 would show this same solved bug.

No doubt a POI developer will remove this test case very soon and it will no 
longer be in our svn and will not be in our next release. True mirrors will 
catch up.

(Have you looked at Apache Solr, Mahout, or Hadoop? You quote a paper from Doug 
Cutting an inventor of Hadoop, which was named after his child's top elephant.)

Regards,
Dave

On Dec 12, 2013, at 7:28 PM, Nirk Niggler wrote:

> Chris:
> 
> If you read my reply, you would see that I actually agree with you.  If
> Raiko cannot certify that the file can be distributed under the same
> license terms as Apache POI, the file should be removed.
> 
> I asked for clarification because IP issues in academia are rarely
> clear-cut. For example, if you received a scholarship of any sort (or were
> part of a funded graduate program), exception 5.1.3 would actually apply
> unless you obtained a written statement as described in section 5.4 (and
> this would be an exercise in futility)
> 
> That being said, if you are serious about going down this route, I would
> also suggest suggest going after others who are hosting the file, such as
> docstoc
> http://www.docstoc.com/docs/24138033/Tagging-with-Hidden-Markov-Models(shared
> by rbb85147
> http://www.docstoc.com/profile/rbb85147) and going after others that have
> publicly available mirrors of POI.  A quick search on github reveals a few
> mirrors, including:
> 
> -
> https://github.com/orione/POI/blob/master/test-data/slideshow/PictureLengthZero.ppt
> -
> https://github.com/samchuang/zkpoi/blob/master/test-data/slideshow/PictureLengthZero.ppt
> -
> https://github.com/tay204/VendorInterface/blob/master/poi-3.9/test-data/slideshow/PictureLengthZero.ppt
> 
> 
> 
> 
> On Thu, Dec 12, 2013 at 8:55 PM, Chris Demwell  wrote:
> 
>> Hi Nirk,
>> 
>> I would like to reiterate that this file is probably of negative value to
>> you: I have mentioned this is *not a Microsoft Office file* and therefore
>> seems unlikely to be a good test case for your project.
>> 
>> I am disappointed that I have to go into this: regardless of any terms of
>> ownership between SFU and myself, the ASF and the POI project are not party
>> to those terms. In any case, as it happens I'm aware of the terms from SFU
>> and sought such clarification immediately upon enrolment. This content was
>> a talk I gave as part of a special topics discussion course and not as
>> "homework". The terms can be seen at
>> http://www.sfu.ca/policies/gazette/research/r30-03.html - specifically,
>> section 5.1 applies:
>> 
>> "5.1 Although the University has the right to require assignment of an
>> interest in IP created by a University Member through the use of its
>> resources, the full ownership of IP and all rights pertaining to ownership
>> are vested in the Creator, unless the Creator has entered into an agreement
>> with the University to the contrary."
>> 
>> There are several exceptions listed, none of which apply to this file. This
>> is my IP, and more importantly it is not yours, nor Raiko's, nor do you
>> have license from SFU. Other than that I think we agree about the legal
>> situation. The waters are not muddy, you do not have license to this file.
>> 
>> Please remove it from your svn history or inform me that you don't intend
>> to do so.
>> 
>> 
>> 
>> 
>> On Thu, Dec 12, 2013 at 4:40 PM, Nirk Niggler >> wrote:
>> 
>>> Chris:
>>> 
>>> A cursory google search reveals that this was part of a class project and
>>> is publicly available at
>>> http://www.cs.sfu.ca/~anoop/courses/CMPT-882-Fall-2002/chris.ppt, which
>>> somewhat muddies the waters (you'd have to get clarification from your
>>> school regarding the IP rights associated with class homework and
>> projects).
>>> 
>>> Eric:
>>> 
>>> While there is no obvious confidential information in the document, the
>>> original contributor Raiko Eckstein violated the terms of the bugzilla <
>>> https://issues.apache.org/bugzilla/createaccount.cgi>
>>> 
 "Certify that any object code, source code, patch, documentation, etc.
>>> that you may supply to an Apache project can be redistributed under the
>>> same license terms and conditions as the project itself."
>>> 
>>> That alone should be grounds for removal.
>>> 
>>> 
>>> 
>>> On Thu, Dec 12, 2013 at 7:14 PM, Eric Peters  wrote:
>>> 
 I have nothing to do with the POI Apache project, other than being a
>> user,
 never contributed, nor have anything to associate other than being on
>> this
 mailing list - but I'd say chill the f*** out.
 
 The relative harms for the debug test file is probably negligible, and
>> in
 the grand scheme of things, its probably 

Re: Excel Function COUNTIFS available in poi ?

[Dave Fisher]

Hi Detlef,

Thanks!  Please create a bugzilla issue with [PATCH] in the subject at 
https://issues.apache.org/bugzilla/buglist.cgi?product=POI

Regards,
Dave

On Dec 9, 2013, at 6:11 AM, Detlef Brendle wrote:

> Hi Poi Team, 
> 
> I have come up with a proposal for an implementation for this function. 
> Please see the attached function plus its testcase.
> It works pretty nicely I would say.
> 
> Maybe you can integrate it to one of your next releases ?
> 
> Thanks,
> detlef
> 
> Von: "Detlef Brendle" 
> An: dev@poi.apache.org
> Gesendet: Samstag, 7. Dezember 2013 15:37:59
> Betreff: Excel Function COUNTIFS available in poi ?
> 
> Hi, 
> is the function countifs 
> (http://office.microsoft.com/en-us/excel-help/countifs-function-HA010047494.aspx)
>  available in the latest poi (3.10-beta2) 
> 
> Doesn't look like to me. 
> Has anybody implemented this function itself ? 
> 
> Thanks, 
> detlef
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org

Re: [ANNOUNCE] Apache POI 3.10 Beta 2 released

[Dave Fisher]

OLE Embedding looks like a hot patch to check out. It is certainly very useful.

Regards,
Dave

On Sep 22, 2013, at 2:28 PM, Nick Burch wrote:

> On Fri, 20 Sep 2013, Dominik Stadler wrote:
>> what are the next steps on POI? Do we stabilize a bit more and release 3.10 
>> before doing more risky stuff? Or do some more bugfixes before starting the 
>> 3.10 release process again?
> 
> Given we've had 2 betas so far, it would probably confuse users if we started 
> doing major and/or breaking changes before 3.10 final is out. Afterwards 
> we're fine to, compatibility rules withstanding! Hopefully that won't be that 
> long, if you want to make some big changes it's not too long to hold off...
> 
> What we do have is quite a lot of user contributed patches/fixes that haven't 
> been applied. If we're not very good at reviewing/applying them, then it has 
> two bad effects. Firstly, we're less likely to get more contributions in 
> future if we're not seen to appreciate them. Secondly, people who have their 
> patches ignored tend not to stick about, so we loose out on potential new 
> committers going forward. Neither good!
> 
> Everyone here is a volunteer, so no-one can demand anyone else do anything! 
> But, if I did have more spare time than I currently seem to, I'd personally 
> be focusing on trying to review + apply as many recent user contributed 
> fixes/enhancements as possible.
> 
> Either way, we probably want to set a rough deadline on the next release. A 
> few days before, we can do a straw poll on beta 3 vs final. If Tim decides 
> it's leaning towards another beta, then he can pretty much roll it then. If 
> final is the consensus, then probably best allow a week or so extra for last 
> minute fixes / tweaks, then roll 3.10 final!
> 
> In the mean time, if anyone wants to play with some major changes, best bet 
> is to take a branch in SVN to work on, then merge it back to trunk once 3.10 
> is out.
> 
> 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: [Vote] Tim Allison as new POI Committer + PMC member

[Dave Fisher]

+1 (binding)

On Jul 3, 2013, at 3:37 PM, Joe Wicentowski wrote:

>> I'm +1!
> 
> +1!
> 
> Thanks Tim!
> 
> Joe
> 
> -
> 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: [VOTE] Cedric Walter as committer

[Dave Fisher]

+1 (binding)

On Jun 17, 2013, at 8:33 AM, Yegor Kozlov wrote:

> Hi All
> 
> Cedric Walter  has submitted a bunch of
> outstanding patches in the area of formula support [1]. His
> contributions seem to be up to our standards, and I had no
> problems collaborating with him and reviewing his code.
> 
> Based on all that, I think he'd be a great addition to the POI committers list
> 
> Please vote, voting to end 7 days from today.
> 
> +1 - Make Cedric a committer
> 0  - I don't mind either way
> -1 - I'd rather Cedric wasn't a committer
> 
> Vote will be open until June 24th. All community members are welcome
> (and encouraged!) to vote, as per normal Apache rules at least 3
> existing PMC members need to +1 for the vote to be binding
> 
> I'm +1 (binding)
> 
> Yegor
> 
> [1] Cedric's patches
> 
> https://issues.apache.org/bugzilla/show_bug.cgi?id=54673
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55036
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55037
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55038
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55041
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55042
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55043
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55047
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55058
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55079
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55080
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55081
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55082
> 
> -
> 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: [Vote] Dominik Stadler as new POI Committer + PMC member

[Dave Fisher]

+1 (binding)

On May 29, 2013, at 3:07 PM, Nick Burch wrote:

> Hi All
> 
> Dominik Stadler  has been doing some great work 
> recently[1] on submitting new patches, and helping clarify + test existing 
> bugs. Based on all that, I think he'd be a great addition to the POI 
> committers list
> 
> Please vote:
> +1 - Let's add Domink to the committers+pmc roster
>  0 - I've not got time to review his contributions to decide, sorry
> -1 - There's a snag with adding him, which is...
> 
> Vote will be open until Monday 3rd. All community members are welcome (and 
> encouraged!) to vote, as per normal Apache rules at least 3 existing PMC 
> members need to +1 for the vote to be binding
> 
> I'm +1!
> 
> Nick
> 
> [1] A search of the list archives like the one below should give an idea:
> https://www.google.co.uk/#output=search&sclient=psy-ab&q=site:http%3A%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Fpoi-dev%2F+Dominik+Stadler&oq=site:http%3A%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Fpoi-dev%2F+Dominik+Stadler&gs_l=hp.3...328.5199.0.5875.8.8.0.0.0.0.159.818.4j4.8.0...0.0...1c.1.15.psy-ab.QpnhOhlRxc8&pbx=1&bav=on.2,or.r_qf.&bvm=bv.47244034,d.d2k&fp=c2ef035028b97662&biw=1902&bih=825
> 
> -
> 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: Error code told me to email the developers.

[Dave Fisher]

The developers list. Dev@poi.apache.org

I've done so. Thanks for your report.

Sent from my iPhone

On May 21, 2013, at 7:48 AM, Mathew Reny  wrote:

> I don't need any help, errors happen, however this error explicitly told me 
> to email you guys.  Below are the stack traces and source code that produced 
> the error.  If you need anything else from me, email me back.
> ---
> Exception in thread "main" 
> org.apache.poi.openxml4j.exceptions.OpenXML4JRuntimeException: Rule M2.4 
> exception : this error should NEVER happen, if so please send a mail to the 
> developers team, thanks !
>   at 
> org.apache.poi.openxml4j.opc.internal.ContentTypeManager.getContentType(ContentTypeManager.java:342)
>   at 
> org.apache.poi.openxml4j.opc.internal.ContentTypeManager.removeContentType(ContentTypeManager.java:255)
>   at 
> org.apache.poi.openxml4j.opc.OPCPackage.removePart(OPCPackage.java:919)
>   at 
> org.apache.poi.openxml4j.opc.PackagePart.getOutputStream(PackagePart.java:520)
>   at 
> org.apache.poi.xssf.usermodel.XSSFWorkbook.commit(XSSFWorkbook.java:1301)
>   at org.apache.poi.POIXMLDocumentPart.onSave(POIXMLDocumentPart.java:313)
>   at org.apache.poi.POIXMLDocument.write(POIXMLDocument.java:173)
>   at com.ashtonwoodshomes.OptionDumpMain.main(OptionDumpMain.java:38)
> 
> 
> 
> import java.io.File;
> import java.io.FileInputStream;
> import java.io.FileNotFoundException;
> import java.io.FileOutputStream;
> import java.io.IOException;
> import java.io.InputStream;
> 
> import org.apache.poi.openxml4j.exceptions.InvalidFormatException;
> import org.apache.poi.openxml4j.opc.OPCPackage;
> import org.apache.poi.ss.usermodel.Cell;
> import org.apache.poi.ss.usermodel.Row;
> import org.apache.poi.ss.usermodel.Sheet;
> import org.apache.poi.xssf.usermodel.XSSFWorkbook;
> 
> public class OptionDumpMain {
>   
>   public static void main(String[] args) throws InvalidFormatException, 
> IOException{
>   String filename = "thishasgraphs.xlsx";
>   InputStream in = new FileInputStream(new File(filename));
>   // XSSFWorkbook, InputStream, needs more memory
>   OPCPackage pkg = OPCPackage.open(in);
>   XSSFWorkbook wb = new XSSFWorkbook(pkg);
>   
>   Sheet appliances = wb.getSheet("Appliances");
>   
>   Row firstRow = appliances.getRow(1);
>   Cell dataCellRow1 = firstRow.getCell(2);
>   System.out.println(dataCellRow1.getNumericCellValue());
>   dataCellRow1.setCellValue(50);
>   
> 
>   
>   pkg.close();
>   
>   FileOutputStream fileOut = new FileOutputStream("workbook.xls");
>   wb.write(fileOut);
>   fileOut.close();
>   }
> }

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

Re: poi pull request: HSSFWorkbook.getAllEmbeddedObjects wasn't getting all emb...

[Dave Fisher]

Poi is an svn project as you should already know.

Sent from my iPhone

On May 20, 2013, at 7:36 PM, trejkaz  wrote:

> GitHub user trejkaz opened a pull request:
> 
>https://github.com/apache/poi/pull/2
> 
>HSSFWorkbook.getAllEmbeddedObjects wasn't getting all embedded objects
> 
>HSSFWorkbook.getAllEmbeddedObjects wasn't getting all embedded objects, 
> only the top-level ones. This fixes it to get them recursively.
> 
> You can merge this pull request into a Git repository by running:
> 
>$ git pull https://github.com/trejkaz/poi patch-1
> 
> Alternatively you can review and apply these changes as the patch at:
> 
>https://github.com/apache/poi/pull/2.patch
> 
> 
> commit 5ee3a2d1d0661fb0cf071e2f824d36ed29b8b899
> Author: Trejkaz (pen name) 
> Date:   2013-05-21T02:35:58Z
> 
>Update HSSFWorkbook.java
> 
>HSSFWorkbook.getAllEmbeddedObjects wasn't getting all embedded objects, 
> only the top-level ones.
> 
> 
> 
> 
> -
> 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: Contributing to XSLF Code

[Dave Fisher]

On May 17, 2013, at 2:26 PM, Nick Burch wrote:

> On Fri, 17 May 2013, Eliot Kimber wrote:
>> I am trying to use the XSLF code to implement manipulation and generation of 
>> PPTX presentations. I see that there are still some missing features and 
>> bugs. I am more than happy to contribute to the code to fill in some of the 
>> features I'm looking for. But I didn't want to start writing patches without 
>> checking what was already under way.
> 
> Most of the work on XSLF has been done by Yegor. (I did a bit at the start 
> around text extraction, then he put most of the work in for the rest!). The 
> remainder comes from user contributions, which we're always very keen to get!
> 
> Yegor is currently a bit snowed-under at work, so I don't believe he's 
> currently working on any XSLF code. If it's in SVN with a TODO, consider it 
> fair game to implement! If it's a new feature, probably best post something 
> here for a sanity check, then go ahead if no-one spots a problem with your 
> plan

Yes, Yegor is certainly snowed under at work. Also, there is some work yet to 
be contributed that we have done over XSLF that may be helpful. I would suggest 
that you communicate your thoughts clearly on the ML about any API changes that 
you would find helpful.

> 
>> My first task is to implement a PPTX "burster" that can produce a set of 
>> single-slide presentations from an existing presentation. I see that this 
>> task was discussed in the mailing list and some workaround code was 
>> provided. But it seems like it would be better to simply make the base code 
>> do the right thing in this case and I'd like to tackle that if it's not 
>> already in the process of being addressed.
> 
> I'd suggest you take that code, fix it and finish it, write some unit tests, 
> then contribute a patch for it. Ideally it would probably be something like a 
> utility that works on XSLF slideshows to produce new ones, or something like 
> that, with most of the logic on the main XSLF classes

Yegor and I certainly have continued interest in this area even if our 
attention is currently elsewhere. It would be great to see what you propose.

> 
>> I'm also working on code to generate new slides from a simple XML format 
>> that represents generic slide show content (that is, something that is 
>> relatively easy to generate from other stuff, like existing XML or whatever).
> 
> Have you seen the HSLF stuff for producing .ppt files, from java awt-style 
> code and the like?

This is a place to look.

Regards,
Dave


> 
> 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: POI Workbook adapter for ODFToolkit

[Dave Fisher]

On Feb 23, 2013, at 3:28 AM, Florian Hopf wrote:

> Hi,
> 
> I just wanted to let you know that I started work on a POI workbook adapter 
> for the ODFToolkit. The goal is to make the POI Workbook functionality 
> available for ODS documents so users can use the familiar POI API to read and 
> modify Open Document spreadsheets. The code still is in an early stage but so 
> far it looks quite promising. It's an interesting task because it is a rather 
> rare opportunity to have an existing implementation that I can use to see how 
> the API should behave. I already noticed that the ODFToolkit needs some 
> further enhancements and fixes to implement all the functionality but I am 
> waiting for the current release to be completed.
> 
> I think providing the existing POI API for Open Document formats will be a 
> huge benefit for many users as for simple use cases I expect this to be 
> nearly a drop in replacement.

This is wonderful. I'm looking forward to the results. When you are closer you 
should also inform the Apache Tika community as this may also improve the 
consumption of ODF docs in text extraction. Tika is used by Apache Solr and 
Apache Jackrabbit (JCR). 

Regards,
Dave


> 
> Regards
> Florian
> 
> -- 
> Florian Hopf
> Freelance Software Developer
> 
> http://blog.florian-hopf.de
> 
> -
> 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: How to change PNG DPI

[Dave Fisher]

Give it a try. You will use more memory.

Regards,
Dave

On Dec 27, 2012, at 4:07 AM, vegaecm wrote:

> Hi,
> 
> Our team use Apache POI to render PowerPoint documents (ppt and pptx) to
> PNG.
> Thank you for your efforts for this project, it is really great product!
> 
> Could you please give us a little advice (unless, of course, it is not
> difficult for you).
> 
> "Shape" class contains
> public static final int POINT_DPI = 72;
> 
> We would like to use another DPI value.
> Are there any objections just to change this value (i.e. to 96 or to 150)
> and rebuild project or would this approach be wrong and we need deep code
> changes?
> 
> Thanks in advance.
> 
> 
> 
> --
> View this message in context: 
> http://apache-poi.1045710.n5.nabble.com/How-to-change-PNG-DPI-tp5711758.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
> 


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

Re: Fixing our website to still work in 2013

[Dave Fisher]

Hi Yegor,

On Dec 19, 2012, at 6:59 AM, Yegor Kozlov wrote:

> I committed  the site in SVN and created a ticket for Infra:
> https://issues.apache.org/jira/browse/INFRA-5683
> 
> The new home for documentation is now
> https://svn.apache.org/repos/asf/poi/site/publish/
> Source XML for Forrest is in ./src
> Compiled .html is in ./publish
> 
> See https://svn.apache.org/repos/asf/poi/site/README.txt for instructions.
> 
>> Make it https://svn.apache.org/repos/asf/poi/site/content/. and we will be 
>> more ready to switch to the CMS.
> 
> I followed the pattern that other projects use. I may be wrong, but
> there is no point to put .html generated from Forrest into CMS. If we
> allow online-editing of the docs via CMS then we will need to refactor
> out .xml into a form compatible with the Apache CMS. Am I wrong?

Yours is the easiest way. There is a bit to learn with the CMS. In order to use 
it without major rewrite we would need to build the Forrest part into the CMS's 
buildbot. We could then edit the xml directly. There is an example:

See http://www.apache.org/dev/cmsadoption.html and look for Ant at the bottom.

See http://svn.apache.org/repos/asf/incubator/public/trunk/ for the build 
files. The Incubator uses python as well.

You can develop locally. See the instructions I wrote for OpenOffice( 
http://openoffice.apache.org/website-local.html#how-to-do-website-development-locally-for-technical-users
 ), these can be adapted for local testing.

> 
> P.S. I'm in the middle of uploading javadocs. For unknown reasons my
> svn refuses to commit all in one go and I have to chop apidocs into
> smaller parts.

This gets us switched before Infra's deadline. I wish I had more time for POI 
and CMS, but you know how busy I have been.

Regards,
Dave


> 
> Yegor
> 
> On Tue, Dec 18, 2012 at 12:48 AM, Dave Fisher  wrote:
>> 
>> On Dec 17, 2012, at 12:44 AM, Yegor Kozlov wrote:
>> 
>>>> I'd suggest not under trunk, but alongside
>>> 
>>> OK, it will be https://svn.apache.org/repos/asf/poi/site.
>> 
>> Make it https://svn.apache.org/repos/asf/poi/site/content/. and we will be 
>> more ready to switch to the CMS.
>> 
>>> I will try to find time this week to do the first pass.
>> 
>> I have been thinking about this as well. Let me know how I can help.
>> 
>> Regards,
>> Dave
>> 
>>> 
>>> Yegor
>>> 
>>> On Mon, Dec 17, 2012 at 12:16 PM, Nick Burch  wrote:
>>>> On Mon, 17 Dec 2012, Yegor Kozlov wrote:
>>>>> 
>>>>> I'm for svnpubsub, as it seems the shortest way.
>>>> 
>>>> 
>>>> I guess we could move to that, and plan to do it in a way that we can use
>>>> the cms later with minimal changes?
>>>> 
>>>> 
>>>>> As I understand, we will need to keep the generated html somewhere in
>>>>> svn and then ask Infra to enable svnpubsub for our site .
>>>> 
>>>> 
>>>> Yup
>>>> 
>>>> 
>>>>> Migration of the Forrest part seems easy:
>>>>> 1. create a new directory "site" under
>>>>> https://svn.apache.org/repos/asf/poi/trunk
>>>> 
>>>> 
>>>> I'd suggest not under trunk, but alongside
>>>> 
>>>> 
>>>>> 2. create two sub-directories:
>>>>> site/docs  <-- Forrest .xml files, copy them from
>>>>> trunk/src/documentation
>>>>> /site/publish  <-- generated html
>>>> 
>>>> 
>>>> We don't actually need to copy the source files, just tell forest where to
>>>> put the resulting published files (likely with a delete first to clean out,
>>>> so old files don't get stuck). Then you svn add/remove as needed and 
>>>> commit,
>>>> then a few secs later it's live!
>>>> 
>>>> 
>>>> 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
>>> 
>> 
>> 
>> -
>> 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
> 


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

Re: Fixing our website to still work in 2013

[Dave Fisher]

On Dec 17, 2012, at 12:44 AM, Yegor Kozlov wrote:

>> I'd suggest not under trunk, but alongside
> 
> OK, it will be https://svn.apache.org/repos/asf/poi/site.

Make it https://svn.apache.org/repos/asf/poi/site/content/. and we will be more 
ready to switch to the CMS.

> I will try to find time this week to do the first pass.

I have been thinking about this as well. Let me know how I can help.

Regards,
Dave

> 
> Yegor
> 
> On Mon, Dec 17, 2012 at 12:16 PM, Nick Burch  wrote:
>> On Mon, 17 Dec 2012, Yegor Kozlov wrote:
>>> 
>>> I'm for svnpubsub, as it seems the shortest way.
>> 
>> 
>> I guess we could move to that, and plan to do it in a way that we can use
>> the cms later with minimal changes?
>> 
>> 
>>> As I understand, we will need to keep the generated html somewhere in
>>> svn and then ask Infra to enable svnpubsub for our site .
>> 
>> 
>> Yup
>> 
>> 
>>> Migration of the Forrest part seems easy:
>>> 1. create a new directory "site" under
>>> https://svn.apache.org/repos/asf/poi/trunk
>> 
>> 
>> I'd suggest not under trunk, but alongside
>> 
>> 
>>> 2. create two sub-directories:
>>> site/docs  <-- Forrest .xml files, copy them from
>>> trunk/src/documentation
>>> /site/publish  <-- generated html
>> 
>> 
>> We don't actually need to copy the source files, just tell forest where to
>> put the resulting published files (likely with a delete first to clean out,
>> so old files don't get stuck). Then you svn add/remove as needed and commit,
>> then a few secs later it's live!
>> 
>> 
>> 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
> 


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

Re: [VOTE] Release POI 3.9

[Dave Fisher]

Thanks. I've had no time until tonight - I was traveling all last week.

I'm glad to see that the VOTE now has 3 +1.

On Dec 4, 2012, at 2:01 AM, Maxim Valyanskiy wrote:

> +1
> 
> 26.11.2012 18:43, Yegor Kozlov пишет:
>> Hi All,
>> 
>> A candidate for the POI-3.9 FINAL release is available at:
>> 
>> https://dist.apache.org/repos/dist/dev/poi/
>> 
>> The release candidate was built from the REL_3_9 tag and
>> includes all changes and fixes committed in trunk up to Monday, November 26:
>> 
>>  https://svn.apache.org/repos/asf/poi/tags/REL_3_9/
>> 
>> As with all Apache release votes, please check that not only does the
>> code work, and no major breakages have occurred since the last
>> release, but also that packaging is correct, license headers and
>> notices exist etc.
>> 
>> The vote options are:
>> 
>>  +1  - I support this release
>>  0   - I don't object to this release, but I haven't checked it
>>  -1  - There's a problem with the release, and that is 
>> 
>> I'm voting [+1]. Voting will last one week and end on Monday, December 3.
>> 
>> P.S. I updated the KEYS file with my new GPG key because my old one expired.
>> Please re-import before verifying signatures.
>> 
>> Regards,
>> Yegor
>> 
>> -
>> 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
> 


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

Re: [VOTE] Release POI 3.9

[Dave Fisher]

Forgive my previous email from a bad iPhone action. I won't be able to review 
until Tuesday or Wednesday.

Regards,
Dave

Sent from my iPhone

On Dec 2, 2012, at 11:12 AM, Evgeniy Berlog  wrote:

> +1
> 
> On Mon, Nov 26, 2012 at 4:43 PM, Yegor Kozlov  wrote:
> 
>> Hi All,
>> 
>> A candidate for the POI-3.9 FINAL release is available at:
>> 
>> https://dist.apache.org/repos/dist/dev/poi/
>> 
>> The release candidate was built from the REL_3_9 tag and
>> includes all changes and fixes committed in trunk up to Monday, November
>> 26:
>> 
>> https://svn.apache.org/repos/asf/poi/tags/REL_3_9/
>> 
>> As with all Apache release votes, please check that not only does the
>> code work, and no major breakages have occurred since the last
>> release, but also that packaging is correct, license headers and
>> notices exist etc.
>> 
>> The vote options are:
>> 
>> +1  - I support this release
>> 0   - I don't object to this release, but I haven't checked it
>> -1  - There's a problem with the release, and that is 
>> 
>> I'm voting [+1]. Voting will last one week and end on Monday, December 3.
>> 
>> P.S. I updated the KEYS file with my new GPG key because my old one
>> expired.
>> Please re-import before verifying signatures.
>> 
>> Regards,
>> Yegor
>> 
>> -
>> 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: [VOTE] Release POI 3.9

[Dave Fisher]

I won

Sent from my iPhone

On Dec 2, 2012, at 11:12 AM, Evgeniy Berlog  wrote:

> +1
> 
> On Mon, Nov 26, 2012 at 4:43 PM, Yegor Kozlov  wrote:
> 
>> Hi All,
>> 
>> A candidate for the POI-3.9 FINAL release is available at:
>> 
>> https://dist.apache.org/repos/dist/dev/poi/
>> 
>> The release candidate was built from the REL_3_9 tag and
>> includes all changes and fixes committed in trunk up to Monday, November
>> 26:
>> 
>> https://svn.apache.org/repos/asf/poi/tags/REL_3_9/
>> 
>> As with all Apache release votes, please check that not only does the
>> code work, and no major breakages have occurred since the last
>> release, but also that packaging is correct, license headers and
>> notices exist etc.
>> 
>> The vote options are:
>> 
>> +1  - I support this release
>> 0   - I don't object to this release, but I haven't checked it
>> -1  - There's a problem with the release, and that is 
>> 
>> I'm voting [+1]. Voting will last one week and end on Monday, December 3.
>> 
>> P.S. I updated the KEYS file with my new GPG key because my old one
>> expired.
>> Please re-import before verifying signatures.
>> 
>> Regards,
>> Yegor
>> 
>> -
>> 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: Problem extracting date from Outlook 2007 .msg file

[Dave Fisher]

Hi Joe,

Are you looking to pay this person to help or are you looking for someone with 
the same "itch" as you?

(Not that I am volunteering either way - it's not my area.)

Regards,
Dave

On Aug 21, 2012, at 2:33 PM, Joe Wicentowski wrote:

> Hi all,
> 
> I hadn't heard from anyone about the question I posed last week --
> regarding POI/HSMF's problems identifying dates in Outlook .msg files.
> Is there a better forum for me to post this?  Should I file a bug?
> Ideally, I'd like to find someone who can help complete the fix that
> Nick Burch began in POI's SVN trunk.
> 
> Thanks for any pointers about the best way to proceed,
> Joe
> 
> On Thu, Aug 16, 2012 at 6:52 PM, Joe Wicentowski  wrote:
>> Hi all,
>> 
>> Hello!  This is my message to the list.  I'm building an application
>> that relies on Tika to extract text from Outlook 2007 .msg files.
>> Tika relies on POI's HSMF libraries, which is why I'm writing to this
>> list about a problem: HSMF is not pulling out the date of many of my
>> Outlook messages.
>> 
>> For example, when I look at one of my message files (.msg) in Outlook,
>> it says that the message was sent on "Fri 6/22/2012 8:11 AM", but when
>> I process the same message with Tika, no date appears in the output
>> [1].
>> 
>> In comparison, I tried using a different tool, ruby-msg
>> (http://code.google.com/p/ruby-msg/), to process the same message, and
>> ruby-msg did pull out the date [2].  This experiment shows that the
>> email *is* in the .msg file, and that Tika is failing to pick it up.
>> 
>> Nick Burch from the Tika mailing list took a close, hands-on look at
>> my .msg file, determined the cause, and outlined a path to the fix:
>> 
>>> I think I've figured out what's wrong. It looks like outlook stores
>>> properties with a fixed size of 0-8 bytes in a different chunk in the file,
>>> which we weren't processing.
>>> 
>>> If you wanted to tackle it, that'd be great! You'll want to take a look at
>>> PropertiesChunk, and fill in the TODOs for readProperties and
>>> writeProperties, then add unit tests. See:
>>> 
>>> http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/src/org/apache/poi/hsmf/datatypes/PropertiesChunk.java?view=markup
>>> 
>>> When that's all done and working, then
>>> the final step is to update MAPIMessage to read some of the values as needed
>>> out of the properties
>>> 
>>> The info I've been working with comes from this blog post:
>>> http://blogs.msdn.com/b/openspecification/archive/2009/11/06/msg-file-format-part-1.aspx
>>> 
>>> (That links into suitable bits of the public documentation)
>>> 
>>> I suspect it's under a day's work. I've put in place the basics, just needs 
>>> someone to flesh it out.
>> 
>> While Nick kindly tracked down the cause, unfortunately I lack the
>> java chops to complete the solution.
>> 
>> Would anyone here be kind enough to assist me with this?
>> 
>> I'm happy to test any attempted fixes, and I'm happy to provide more
>> info, like sample Outlook files (.msg files).  My hope is that this
>> fix will allow POI to "just work" for more users who are evaluating
>> it.
>> 
>> Thank you in advance,
>> Joe
>> 
>> 
>> [1] Tika output showing no date, retrieved via the following command:
>> 
>>   java -jar tika-app-1.1.jar "Inquiry.msg" > inquiry.html
>> 
>> http://www.w3.org/1999/xhtml";>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>RE: Inquiry
>>
>>From
>>History Mailbox
>>To
>>'Snip'
>>Recipients
>>s...@gmail.com
>>
>>Dear Snip
>> ...
>> 
>> [2] The ruby-msg output -- notice the "Date:" line:
>> 
>> From: "History Mailbox" 
>> To: "Snip" 
>> Subject: RE: Inquiry
>> Date: Fri, 22 Jun 2012 12:11:00 -
>> Message-ID: <000807f9a285794eaad13ec6eae33a760117ae0e2...@pasa1mb01.pace.unc>
>> In-Reply-To: 
>> 
>> Priority: 0
>> Thread-Topic: Inquiry
>> Content-Type: multipart/alternative;
>> boundary="_=_NextPart_001_8149ed38.4fec8c61"
> 
> -
> 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: [VOTE] Evgeniy Berlog as committer

[Dave Fisher]

I am +1. (but we need to do this in private.)


On Jun 4, 2012, at 1:22 AM, Yegor Kozlov wrote:

> Hi All,
> 
> Our GSoC student, Evgeniy Berlog is doing a great job improving
> drawing support in HSSF.
> His contributions seem to be up to our standards and I'm happy to
> collaborate with him.
> 
> Evgeniy's ICLA is on file and if there are no objections, I'd like to
> grant him committership.
> 
> Please vote, voting will last 5 days and end on Friday, June 8.
> 
> The vote options are:
> 
> +1 - Make Evgeniy a committer
> 0  - I don't mind either way
> -1 - I'd rather Evgeniy wasn't a committer
> 
> I'm +1
> 
> Regards,
> Yegor
> 
> -
> 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: [VOTE] Evgeniy Berlog as committer

[Dave Fisher]

Forgive me. I've been working on project's in the Incubator where votes in 
public would be sure to have many ballots.

POI has been holding Committer votes in public for 5 years. They are just 
infrequent.

Refgards,
Dave

On Jun 4, 2012, at 3:13 PM, Dave Fisher wrote:

> Please ignore this thread. Committer votes are held on private lists in 
> Apache projects.
> 
> Regards,
> Dave
> 
> On Jun 4, 2012, at 1:26 AM, Sergey Vladimirov wrote:
> 
>> +1
>> 
>> -- 
>> Sergey Vladimirov
>> 
>> On Mon, Jun 4, 2012 at 12:22 PM, Yegor Kozlov  wrote:
>> 
>>> Hi All,
>>> 
>>> Our GSoC student, Evgeniy Berlog is doing a great job improving
>>> drawing support in HSSF.
>>> His contributions seem to be up to our standards and I'm happy to
>>> collaborate with him.
>>> 
>>> Evgeniy's ICLA is on file and if there are no objections, I'd like to
>>> grant him committership.
>>> 
>>> Please vote, voting will last 5 days and end on Friday, June 8.
>>> 
>>> The vote options are:
>>> 
>>> +1 - Make Evgeniy a committer
>>> 0  - I don't mind either way
>>> -1 - I'd rather Evgeniy wasn't a committer
>>> 
>>> I'm +1
>>> 
>>> Regards,
>>> Yegor
>>> 
>>> -
>>> 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
> 


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

Re: [VOTE] Evgeniy Berlog as committer

[Dave Fisher]

Please ignore this thread. Committer votes are held on private lists in Apache 
projects.

Regards,
Dave

On Jun 4, 2012, at 1:26 AM, Sergey Vladimirov wrote:

> +1
> 
> -- 
> Sergey Vladimirov
> 
> On Mon, Jun 4, 2012 at 12:22 PM, Yegor Kozlov  wrote:
> 
>> Hi All,
>> 
>> Our GSoC student, Evgeniy Berlog is doing a great job improving
>> drawing support in HSSF.
>> His contributions seem to be up to our standards and I'm happy to
>> collaborate with him.
>> 
>> Evgeniy's ICLA is on file and if there are no objections, I'd like to
>> grant him committership.
>> 
>> Please vote, voting will last 5 days and end on Friday, June 8.
>> 
>> The vote options are:
>> 
>> +1 - Make Evgeniy a committer
>> 0  - I don't mind either way
>> -1 - I'd rather Evgeniy wasn't a committer
>> 
>> I'm +1
>> 
>> Regards,
>> Yegor
>> 
>> -
>> 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: [VOTE] Release POI 3.8 FINAL

[Dave Fisher]

+1. Go POI 3.8!

Thank you Yegor!

On Mar 19, 2012, at 12:17 AM, Yegor Kozlov wrote:

> Hi All,
> 
> A candidate for the POI-3.8 FINAL release is available at:
> 
> https://dist.apache.org/repos/dist/dev/poi/
> 
> The release candidate was built from the REL_3_8_FINAL tag and
> includes all changes and fixes committed in trunk up to Saturday, March 17:
> 
> https://svn.apache.org/repos/asf/poi/tags/REL_3_8_FINAL/
> 
> As with all Apache release votes, please check that not only does the
> code work, and no major breakages have occurred since the last
> release, but also that packaging is correct, license headers and
> notices exist etc.
> 
> The vote options are:
> 
> +1  - I support this release
> 0   - I don't object to this release, but I haven't checked it
> -1  - There's a problem with the release, and that is 
> 
> I'm voting [+1]. Voting will last one week and end on Monday, 26th March.
> 
> Regards,
> Yegor
> 
> -
> 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: [VOTE] Release POI 3.8 FINAL

[Dave Fisher]

Hi -

If no one else votes, I'll do the checks and vote late today.

Regards,
Dave

On Mar 19, 2012, at 12:17 AM, Yegor Kozlov wrote:

> Hi All,
> 
> A candidate for the POI-3.8 FINAL release is available at:
> 
> https://dist.apache.org/repos/dist/dev/poi/
> 
> The release candidate was built from the REL_3_8_FINAL tag and
> includes all changes and fixes committed in trunk up to Saturday, March 17:
> 
> https://svn.apache.org/repos/asf/poi/tags/REL_3_8_FINAL/
> 
> As with all Apache release votes, please check that not only does the
> code work, and no major breakages have occurred since the last
> release, but also that packaging is correct, license headers and
> notices exist etc.
> 
> The vote options are:
> 
> +1  - I support this release
> 0   - I don't object to this release, but I haven't checked it
> -1  - There's a problem with the release, and that is 
> 
> I'm voting [+1]. Voting will last one week and end on Monday, 26th March.
> 
> Regards,
> Yegor
> 
> -
> 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: contributing code to POI

[Dave Fisher]

On Jan 30, 2012, at 1:28 PM, Niklas Rehfeld wrote:

> Thanks for clearing that up! I always get a bit confused with copyright stuff.
> 
>> You should use the same standard Apache License header that's used in the
>> POI source code. I can't spot anything about "the POI license" anywhere, can
>> you point me to it?
> 
> In the coding guidelines, http://poi.apache.org/resolutions/res001.html it 
> says
> 
>> 1. All classes and interfaces MUST have, right at the beginning, the POI 
>> License (see poi/doc/LICENSE).
> 
> then, just underneath in the amendments,
> 
>> As opposed to the formerly used POI License which was based on the Apache 
>> Public License, now that POI is part of Jakarta, use the APL 1.1 for the 
>> header. Currently, the Apache
>> Software Foundation requires us to use the full long version.
> 
> which seems out of date as well, if we're meant to be using AL2.

POI is over 10 years old at Apache and existed before. Hence POI license to APL 
1.1 to AL2.

Thanks for pointing out that we need to edit the site.

Regards,
Dave


> 
> Thanks again for the tips. I will try to send in some patches in the next 
> week.
> 
> Nik
> 
> -
> 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: contributing code to POI

[Dave Fisher]

All contributions to a project at The Apache Software Foundation are made under 
the Apache License 2.0. [1]

You are free to offer your own project under whatever license you wish, but you 
should offer your contribution to the project under the AL2. Here is a FAQ [2]

If your contribution is large then you should consider sending in an Individual 
Contributor License Agreement. [3]

If you wish, you retain copyright to your contributions.

Regards,
Dave

[1] http://www.apache.org/licenses/LICENSE-2.0.html
[2] http://www.apache.org/foundation/license-faq.html
[3] http://www.apache.org/licenses/icla.pdf


On Jan 29, 2012, at 7:49 PM, Niklas Rehfeld wrote:

> Hi all,
> 
> I have been working on a project that uses a lot of the POI libraries,
> and have come up with some code that I think would be useful to
> contribute back to the project. The main thing is an implementation of
> the DConRef record structure.
> 
> Now, I haven't released the project that this is part of yet, and I
> haven't decided on a license to release it under. I am a bit confused
> by the stuff in the contributing guidelines and the Coding standards.
> 
> For instance does it matter what license I release my project under,
> in terms of being able to contribute parts of the codebase to the POI
> project? I read in one of the parts that none of the code contributed
> is allowed to depend on gpl/lgpl licensed code. Does this mean I can't
> release my project under GPL and contribute parts of it to POI at the
> same time? Or am I completely misunderstanding something?
> 
> Also, what license/headers do I need to put at the top of a class when
> I contribute it? In some places it talks about "the POI License" and
> other places it talks about the ASL and releasing rights to the source
> under that license.
> 
> Cheers
> Nik
> 
> p.s. the link to the 'apache software license' in the checklist part
> of in http://poi.apache.org/guidelines.html is broken, it points to
> "licence-faq" rather than to "license-faq".
> 
> -
> 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: [VOTE] Release POI 3.8 beta5

[Dave Fisher]

+1.

I have some reservations for a FINAL release.

(1) When I check the signature of the tar.gz packages. I have to gunzip and 
change the name of the gpg.

(2) Sometimes the tests fail with:

[junit] Running org.apache.poi.hssf.usermodel.TestBugs
[junit] Invalid memory access of location 0x8 rip=0x10113a9bc
[junit] 
[junit] Running org.apache.poi.util.TestTempFile
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec

BUILD FAILED
/Users/dave/Documents/poi-3.8beta5/poi-3.8-beta5-src-zip/build.xml:630: Tests 
failed (crashed)

This could be something related to my configuration on my Mac.

(3) The build should make sure the character encoding is not ASCII, or change 
this test case.

[javac] 
/Users/dave/Documents/poi-3.8beta5/poi-3.8-beta5-src-tar/src/ooxml/testcases/org/apache/poi/xslf/extractor/TestXSLFPowerPointExtractor.java:192:
 warning: unmappable character for encoding ASCII
[javac]  "And onto the 4th, such fun???.\n" +
[javac] ^
[javac] 
/Users/dave/Documents/poi-3.8beta5/poi-3.8-beta5-src-tar/src/ooxml/testcases/org/apache/poi/xslf/extractor/TestXSLFPowerPointExtractor.java:192:
 warning: unmappable character for encoding ASCII
[javac]  "And onto the 4th, such fun???.\n" +
[javac]  ^
[javac] 
/Users/dave/Documents/poi-3.8beta5/poi-3.8-beta5-src-tar/src/ooxml/testcases/org/apache/poi/xslf/extractor/TestXSLFPowerPointExtractor.java:192:
 warning: unmappable character for encoding ASCII
[javac]  "And onto the 4th, such fun???.\n" +
[javac]   ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 3 warnings

We can discuss this in the next few weeks.

Regards,
Dave


On Dec 10, 2011, at 8:19 AM, Yegor Kozlov wrote:

> Hi All,
> 
> Please test-drive the release candidate for POI 3.8 beta5.
> 
> The release candidate files were built from the REL_3_8_BETA5 tag and
> are available from:
> 
> https://dist.apache.org/repos/dist/dev/poi/
> 
> As with all Apache release votes, please check that not only does the
> code work, and no major breakages have occurred since the last
> release, but also that packaging is correct, license headers and
> notices exist etc.
> 
> The vote options are:
> 
> +1 - I support this release
> 0   - I don't object to this release, but I haven't checked it
> -1  - There's a problem with the release, and that is 
> 
> I'm voting [+1]. Voting will last one week and end on Saturday, 17th December.
> 
> Yegor Kozlov
> 
> -
> 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: Beta 5?

[Dave Fisher]

On Nov 30, 2011, at 9:47 AM, Dave Fisher wrote:

> 
> On Nov 29, 2011, at 11:57 PM, Yegor Kozlov wrote:
> 
>> Two weeks back, I posted my plan to release 3.8-final in December
>> 2011, but now I realize that we are not yet ready and another beta
>> would be more appropriate.
>> Personally, I think we are ready for the final release in terms of new
>> features, but we are not quite good in terms of resolving bug reports
>> and applying patches -  there is quite a few recent bugs that need
>> attention.
>> 
>> I'm +1 to release beta5 in December. When does Tika need it ?
>> What if I cut the release around Dec 10, then give a week for review
>> aiming to be on the mirrors by Dec 20 ?
>> 
>> Right now I need at least a week to apply pending changes in XSLF -
>> I'm working on this API as a part of my daytime job and I'm happy with
>> the progress.
> 
> Bug +1

Oops BIG +1

Regards,
Dave

> 
> Regards,
> Dave
> 
>> 
>> Yegor
>> 
>> On Mon, Nov 28, 2011 at 11:23 PM, Nick Burch  wrote:
>>> Hi All
>>> 
>>> I know we were aiming to have done the final release by now, but volunteer
>>> energy (mine included!) has meant we've not yet quite finished everything
>>> 
>>> What do people think about doing another interim beta release? The reason I
>>> ask is that there have been quite a few fixes since August that I'd like to
>>> make available to Tika, but as Tika doesn't use nightly snapshots it'd need
>>> a release (beta or final) to get them
>>> 
>>> Thinking of 3.8 final, there are a few bugs I'd like to fix, but if I
>>> haven't had time by the release vote then I don't think that'd be the end of
>>> the world. The only thing I'd say really is needed is to apply the
>>> outstanding community patches (or at least review and throw back if not
>>> ready). Alas I probably won't have time in the next few weeks to do any
>>> patch review, but personally I'd see that as the only bit in the way.
>>> 
>>> What does everyone else think?
>>> 
>>> 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
>> 
> 
> 
> -
> 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: Beta 5?

[Dave Fisher]

On Nov 29, 2011, at 11:57 PM, Yegor Kozlov wrote:

> Two weeks back, I posted my plan to release 3.8-final in December
> 2011, but now I realize that we are not yet ready and another beta
> would be more appropriate.
> Personally, I think we are ready for the final release in terms of new
> features, but we are not quite good in terms of resolving bug reports
> and applying patches -  there is quite a few recent bugs that need
> attention.
> 
> I'm +1 to release beta5 in December. When does Tika need it ?
> What if I cut the release around Dec 10, then give a week for review
> aiming to be on the mirrors by Dec 20 ?
> 
> Right now I need at least a week to apply pending changes in XSLF -
> I'm working on this API as a part of my daytime job and I'm happy with
> the progress.

Bug +1

Regards,
Dave

> 
> Yegor
> 
> On Mon, Nov 28, 2011 at 11:23 PM, Nick Burch  wrote:
>> Hi All
>> 
>> I know we were aiming to have done the final release by now, but volunteer
>> energy (mine included!) has meant we've not yet quite finished everything
>> 
>> What do people think about doing another interim beta release? The reason I
>> ask is that there have been quite a few fixes since August that I'd like to
>> make available to Tika, but as Tika doesn't use nightly snapshots it'd need
>> a release (beta or final) to get them
>> 
>> Thinking of 3.8 final, there are a few bugs I'd like to fix, but if I
>> haven't had time by the release vote then I don't think that'd be the end of
>> the world. The only thing I'd say really is needed is to apply the
>> outstanding community patches (or at least review and throw back if not
>> ready). Alas I probably won't have time in the next few weeks to do any
>> patch review, but personally I'd see that as the only bit in the way.
>> 
>> What does everyone else think?
>> 
>> 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
> 


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

Re: release 3.8-final in late Dec

[Dave Fisher]

+1

Sent from my iPhone

On Nov 15, 2011, at 6:37 AM, Yegor Kozlov  wrote:

> Hi All!
> 
> What do people think if we release 3.8-final by the end of this year?
> My plan is to cut the release around Dec 15, then give 7-10 days for
> the vote and be on the mirrors by New Year.
> 
> I'm +1 to release in December.
> 
> Yegor
> 
> -
> 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: Is development in poi completely stalled ??

[Dave Fisher]

Sanmoy,

Let me add to what Nick wrote.

On Sep 19, 2011, at 2:10 PM, Nick Burch wrote:

> On Tue, 20 Sep 2011, Sanmoy Ray wrote:
>> Do not get me wrong in this, but poi development is very slow in compare to 
>> other popular apache projects
> 
> We're all volunteers here
> 
>> Development in XSLF started long back and still it lacks in many necessary
>> APIs.
> 
> Please feel free to submit patches!

Recently, we've had contributions to HWPF and XWPF!

> 
> Personally, I only get work time to code on XSLF for things relating to text 
> extraction, so I don't get a chance to do much on it beyond that. I believe 
> many of the other committers are in a similar position

Yegor recently did additional work with XSLF which made it into 3.8beta4.

>> I have found a defect in HSLF and reported, but no one replied even after 10 
>> days :-(
> 
> Did you include all the information needed? Were you able to include a 
> failing unit test and a problem file?
> 
> With projects staffed by volunteers, the better your bug report the better 
> chance there is that someone will be able to help you. Also, if you're able 
> to take some time to help others out with there problems, then there's a 
> greater chance that a volunteer will take some time one weekend of evening to 
> help you with yours!

Sometimes volunteers go on vacation and might not be back for awhile. You'll 
either need to dig into the source yourself or be patient until someone has 
time.

Regards,
Dave

> 
> 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: when is 3.8 stable version planned to be released

[Dave Fisher]

On Sep 13, 2011, at 6:22 AM, nmsrinivas wrote:

> hi ,
> Please help me any one
> 
> 1)poi XSSF doesn't read the blank cell(empty) with Cell.CELL_TYPE_BLANK ?
> how to read ?
> 

http://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/Workbook.html#setMissingCellPolicy(org.apache.poi.ss.usermodel.Row.MissingCellPolicy)

> 2) how to get the formula value of the cell ?
> ex: 2+2=4
> return 4;

See http://poi.apache.org/spreadsheet/eval.html



> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-poi.1045710.n5.nabble.com/when-is-3-8-stable-version-planned-to-be-released-tp4796754p4798484.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
> 


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

Re: [VOTE] Release POI 3.8 beta4 - Take 2

[Dave Fisher]

OK - I am +1

Regards,
Dave

On Aug 23, 2011, at 12:04 PM, Yegor Kozlov wrote:

> Hi All,
> 
> Please test-drive the release candidate for POI 3.8 beta4 (take 2).
> Compared to the first version, two release blockers have been found and fixed:
> 
> (1) https://issues.apache.org/bugzilla/show_bug.cgi?id=51686
> (2) Our collection of test files included a document that we are not
> allowed to distribute.  The doc in question has been removed.
> 
> The release candidate files are available from:
> 
> https://dist.apache.org/repos/dist/dev/poi/
> 
> (The jars and poms to feed into the maven repo are in /maven/
> directory, they will be pushed using mvn-deploy.sh)
> 
> As with all Apache release votes, please check that not only does the
> code work, and no major breakages have occurred since the last
> release, but also that packaging is correct, license headers and
> notices exist etc.
> 
> The vote options are:
> 
> +1 - I support this release
> 0 - I don't object to this release, but I haven't checked it
> -1 - There's a problem with the release, and that is 
> 
> I'm voting [+1]. Vote open for 72 hours and ends on Friday, 26th August.
> 
> Yegor
> 
> -
> 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: [VOTE] Release POI 3.8 beta4 - Take 2

[Dave Fisher]

On Aug 25, 2011, at 3:22 AM, Nick Burch wrote:

> On Thu, 25 Aug 2011, Yegor Kozlov wrote:
>> Dave and Nick,
>> Is it really a blocker? Can I have provisional +1 from you, providing
>> that the the problem fixed in trunk ASAP?
> 
> It's certainly a blocker on a final release. On a test file, on a beta 
> release, I'm less sure

I waver myself.

> 
>> If a missing ASF licence header is considered to be a blocker, then 
>> rat-check MUST be a part of the "dist" task to prevent such issues in the 
>> future.
> 
> I'd suggest that if rat isn't present, a warning is raised but the build 
> continues. The release manager should be instructed to always have Rat 
> installed. That way, people who take the POI codebase and tweak things can 
> still do their own custom builds, but we get the check

+1 to this.

I think reviewers ought to have Rat and Forrest 0.5 installed.

We should have improved instructions for release reviewers with example 
commands. It is cumbersome to deal with the keys and there are missing bits. 
Let's see if we agree on the steps.

(1) Verify artifacts - check signatures and checksums.
(2) Check that the zip and tar.gz artifacts unpack to the same content.
(3) Perform a full dist build of the source distribution. Check Unit Tests and 
RAT report.
(4) Check docs website from binary distro with built version.

Anything else?

Regards,
Dave

> 
> 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: [VOTE] Release POI 3.8 beta4 - Take 2

[Dave Fisher]

On Aug 25, 2011, at 1:38 AM, Nick Burch wrote:

> On Wed, 24 Aug 2011, Dave Fisher wrote:
>> Do you have a project that we could copy. If so, I'll throw it into the poi 
>> build.xml and see what's up.
> 
> I can do one better, it's already in our build.xml :)
> 
> Assuming you've installed the rat plugin in your ant lib (~/.ant/lib/) then 
> you just need to do "ant rat-check"

Works well.

BTW - Trunk now passes and using the build's rat the release candidate only 
shows the two files.

Regards,
Dave

> 
> 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: [VOTE] Release POI 3.8 beta4 - Take 2

[Dave Fisher]

On Aug 24, 2011, at 4:11 PM, Nick Burch wrote:

> On Wed, 24 Aug 2011, Dave Fisher wrote:
>> I think we have been accepting the dummy.txt, *.pen and *.dtd as exceptions.
> 
> The dummy ones should be being excluded already, though possibly they're not 
> due to a recent re-org. Ditto .pen and .dtd. Just to check - are you using 
> the "rat-check" ant target to do your checks? That has a set of excludes 
> included in it which should skip over the bits that are safe to ignore the 
> lack of headers in

I followed the rather thin example in the podling and did a license check:

java -jar ../../apache-rat-0.7/apache-rat-0.7.jar --addLicence 
/Users/dave/Documents/poi-3.8beta4/poi-3.8-beta4/src

I see some instructions here: 
http://incubator.apache.org/rat/apache-rat-tasks/index.html

Do you have a project that we could copy. If so, I'll throw it into the poi 
build.xml and see what's up.

Regards,
Dave



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