Re: Help with task:

[Greg Woolsey]

Excellent!  One way to do it would be to submit patches or pull requests
[1] against the project that contain the new files and, if possible,
updates to the documentation web page sources [2] integrating the new
examples.

If you don't mind waiting longer for developers to review and integrate
changes you could just open a Bugzilla ticket [3] and attach examples
there.  That would rely more on a developer doing the work of integrating
the sample files in the project and documentation, which might take a
while, as we're all volunteers with families and day jobs.

I would suggest starting paralleling the existing Java examples [4].  They
can then be linked in parallel on the Examples web page [5] (currently only
spreadsheet examples), and extended to include links to the other examples
not currently referenced by the web site.  Those examples have been
developed over time in response to user questions and new functionality, so
they are a known good cross-section of POI use cases and components.

[1]  http://poi.apache.org/subversion.html
[2]  https://svn.apache.org/repos/asf/poi/site/src/documentation/
[3]  https://bz.apache.org/bugzilla/enter_bug.cgi?product=POI
[4]
https://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/
[5]  https://poi.apache.org/spreadsheet/examples.html


On Thu, Aug 17, 2017 at 2:19 AM Avinash Anand  wrote:

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?856abd21
>
> Hi Team,
>
>
> I would like to help with writing examples of using Apache poi with JVM
> languages, like kotlin.
>
>
> Regards
>
> Avinash Anand
>
> github - https://github.com/avinash-anand
>

Re: 3.17-beta2 vs. 3.17 final?

[Greg Woolsey]

I have a pull request with Vaadin [1] that is currently an echo chamber - I
think the key developer I've been in contact with is on summer holiday.  I
think I found the last bug in my POI code, and the remaining issues with
their integration tests relate to picking up a POI release with that fix
and one other issue that is entirely Vaadin based, a regression of some
form with my changes that I want their help pinning down.  So I think as
far as I'm concerned 3.17 is ready in that respect.  My next set of
submissions that depend on that PR have to do with Excel data table styles,
another esoteric area of the OOXML spec.  I've got that working and tested
in my project, so I think the POI code there is stable as well.

Replacing the chart API feels like a 4.0 thing to me for sure.  And
deprecating the existing classes/API may need to extend longer than 2
releases, similar to what's been done for the CellType change from int to
Enum, just because it's a major breaking change and there are quite a few
projects that use the chart API one way or another, either for creation or
reading.

I'm ready to vote +1 for a 3.17 release candidate this weekend.  I won't be
checking it until Tuesday, though, since I'm 2 miles from the US solar
eclipse path of totality, and we have guests from the UK arriving...

[1]  https://github.com/vaadin/spreadsheet/pull/595

On Thu, Aug 17, 2017 at 1:42 PM Andreas Beeker  wrote:

> Hi Greg,
>
> when do you know, if your chances are ok for Vaadin?
>
> if that is accepted, I would like to release 3.17 final and then switch to
> 4.0 (jdk7) -
> IIRC we discussed to immediately release 4.0-beta1 - is this correct /
> does it make sense?
>
> Regarding the API changes - I haven't checked the pull requests, but I
> usually don't mind the changes to XSLF.
> And about XSSF, we still can decide to deprecate the existing chart api in
> 4.0.
>
> So if no-one minds, I would prepare a release candidate on Sunday ...
>
> Andi
>
>
>

Re: 3.17-beta2 vs. 3.17 final?

[Andreas Beeker]

Hi Greg,

when do you know, if your chances are ok for Vaadin?

if that is accepted, I would like to release 3.17 final and then switch to 4.0 
(jdk7) -
IIRC we discussed to immediately release 4.0-beta1 - is this correct / does it 
make sense?

Regarding the API changes - I haven't checked the pull requests, but I usually 
don't mind the changes to XSLF.
And about XSSF, we still can decide to deprecate the existing chart api in 4.0.

So if no-one minds, I would prepare a release candidate on Sunday ...

Andi




signature.asc
Description: OpenPGP digital signature

[Bug 61440] XSSFValueAxis unable to set MajorGridLines() in XSSFLineChartData

[bugzilla]

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

Javen O'Neal  changed:

   What|Removed |Added

   Severity|normal  |enhancement
 OS||All

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

3.17-beta2 vs. 3.17 final?

[Greg Woolsey]

I could use a new release, don't care what we call it :)

Anyone have pending things they want to get finalized first?  We had
targeted end of summer for 3.17 final, but I don't remember any hard
criteria for what folks wanted included in 3.17.

I know there's been discussion about a new unified charts API, but as
that's new work, and should probably start out as a beta to gather feedback
and leave room for API changes, I don't feel it needs to be in 3.17.

I noticed last night my commit didn't cause any build failures, so it
appears all the work figuring out which build instances aren't stable has
paid off for now.

[Bug 61440] New: XSSFValueAxis unable to set MajorGridLines() in XSSFLineChartData

[bugzilla]

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

Bug ID: 61440
   Summary: XSSFValueAxis unable to set MajorGridLines() in
XSSFLineChartData
   Product: POI
   Version: 3.14-FINAL
  Hardware: PC
Status: NEW
  Severity: normal
  Priority: P2
 Component: XSSF
  Assignee: dev@poi.apache.org
  Reporter: cbenagara...@gmail.com
  Target Milestone: ---

Created attachment 35245
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35245=edit
linechart

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

[Bug 61396] DataBarFormatting, setWidthMin by default 10 % in excel output(when i getWidthMin gives 0 and i unable to setWidthMin to any other value)

[bugzilla]

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

raja  changed:

   What|Removed |Added

   Priority|P2  |P1
 OS||All
 CC||cbenagara...@gmail.com
   Severity|major   |blocker

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

Re: Help with task:

[pj.fanning]

Thanks Avinash. Would you be able to create a sample or samples using Kotlin?
Apache POI does support quite a lot of Microsoft document formats but maybe
xlsx is a good place to start. The XSSF API for reading and/or writing xlsx
files might be a good one to demonstrate.
Feel free to suggest something else.
Maybe you could create a Github repo and we can look at merging it in our
samples directory in the main Apache repo when the demo is complete.



--
View this message in context: 
http://apache-poi.1045710.n5.nabble.com/Help-with-task-tp5728534p5728535.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

Help with task:

[Avinash Anand]

I would like to help out with the task listed at
https://helpwanted.apache.org/task.html?856abd21

Hi Team,


I would like to help with writing examples of using Apache poi with JVM
languages, like kotlin.


Regards

Avinash Anand

github - https://github.com/avinash-anand