You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by "pj.fanning" <fa...@yahoo.com> on 2018/03/02 14:45:52 UTC
Re: publishing poi xmlbeans jars
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-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by "pj.fanning" <fa...@yahoo.com>.
Thanks Dave. I think it would be good to get the XMLBeans JIRA project
reopened if and when we get the XMLBeans project into the Apache Incubator.
Some of the issues we want to fix are already tracked as XMLBeans JIRAs.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by Alain FAGOT BÉAREZ <AB...@FOR-Scala.IT>.
Yet another dead code generator, used in Apache ODF kit, is MSV.
It seems like code generation from XSD schemas has not much to be changed anymore....
-------- Originale Nachricht --------
Von: Mark Murphy <jm...@gmail.com>
Gesendet: Thu Mar 15 14:01:51 GMT-03:00 2018
An: POI Developers List <de...@poi.apache.org>
Betreff: Re: publishing poi xmlbeans jars
forget JiBX, it looks deader than XMLBeans
On Thu, Mar 15, 2018 at 9:46 AM, Mark Murphy <jm...@gmail.com> wrote:
> Anyone look at JiBX? it is released under the 3-clause BSD license.
> http://jibx.sourceforge.net/jibx-license.html. It contains some code that
> is uder the Apache 1.1 license which should be ok, and some code under XPP3
> which is not listed by Apache, but appears to be based on the BSD license.
>
> Concerning XPP3, clause 3 may be problematic because it is not directly in
> the BSD 3 clause. This third clause is not the advertising clause found in
> the BCD 4 clause, but it is similar as it applies to documentation, so that
> could be a problem. Maybe legal should look at it and give a ruling.
> Finally, XPP3 clauses 4 and 5 appear to my non-legal eyes to be the same
> and equivalent to the BSD clause 3.
>
> On Fri, Mar 9, 2018 at 4:54 PM, Andreas Beeker <ki...@apache.org>
> wrote:
>
>> There's a workaround for the GPL problem:
>> https://issues.apache.org/jira/browse/LEGAL-264
>>
>> ... but my last experiments with the current ECMA schemas weren't so
>> successful:
>> https://stackoverflow.com/questions/46869482/
>>
>>
>> On 3/9/18 2:05 PM, Murphy, Mark wrote:
>> > Since JAXB is being dropped from Java SE (deprecated in Java 9, removed
>> in Java 11), I don't think that this will be a problem. There may be other
>> marshallers out there, but the more immediate problem is that we need to
>> remove all JAXB code from POI because we can no longer rely on the JVM
>> implementation, and the JAXB project is GPL code.
>>
>>
>>
>
Re: publishing poi xmlbeans jars
Posted by Mark Murphy <jm...@gmail.com>.
forget JiBX, it looks deader than XMLBeans
On Thu, Mar 15, 2018 at 9:46 AM, Mark Murphy <jm...@gmail.com> wrote:
> Anyone look at JiBX? it is released under the 3-clause BSD license.
> http://jibx.sourceforge.net/jibx-license.html. It contains some code that
> is uder the Apache 1.1 license which should be ok, and some code under XPP3
> which is not listed by Apache, but appears to be based on the BSD license.
>
> Concerning XPP3, clause 3 may be problematic because it is not directly in
> the BSD 3 clause. This third clause is not the advertising clause found in
> the BCD 4 clause, but it is similar as it applies to documentation, so that
> could be a problem. Maybe legal should look at it and give a ruling.
> Finally, XPP3 clauses 4 and 5 appear to my non-legal eyes to be the same
> and equivalent to the BSD clause 3.
>
> On Fri, Mar 9, 2018 at 4:54 PM, Andreas Beeker <ki...@apache.org>
> wrote:
>
>> There's a workaround for the GPL problem:
>> https://issues.apache.org/jira/browse/LEGAL-264
>>
>> ... but my last experiments with the current ECMA schemas weren't so
>> successful:
>> https://stackoverflow.com/questions/46869482/
>>
>>
>> On 3/9/18 2:05 PM, Murphy, Mark wrote:
>> > Since JAXB is being dropped from Java SE (deprecated in Java 9, removed
>> in Java 11), I don't think that this will be a problem. There may be other
>> marshallers out there, but the more immediate problem is that we need to
>> remove all JAXB code from POI because we can no longer rely on the JVM
>> implementation, and the JAXB project is GPL code.
>>
>>
>>
>
Re: publishing poi xmlbeans jars
Posted by Mark Murphy <jm...@gmail.com>.
Anyone look at JiBX? it is released under the 3-clause BSD license.
http://jibx.sourceforge.net/jibx-license.html. It contains some code that
is uder the Apache 1.1 license which should be ok, and some code under XPP3
which is not listed by Apache, but appears to be based on the BSD license.
Concerning XPP3, clause 3 may be problematic because it is not directly in
the BSD 3 clause. This third clause is not the advertising clause found in
the BCD 4 clause, but it is similar as it applies to documentation, so that
could be a problem. Maybe legal should look at it and give a ruling.
Finally, XPP3 clauses 4 and 5 appear to my non-legal eyes to be the same
and equivalent to the BSD clause 3.
On Fri, Mar 9, 2018 at 4:54 PM, Andreas Beeker <ki...@apache.org> wrote:
> There's a workaround for the GPL problem:
> https://issues.apache.org/jira/browse/LEGAL-264
>
> ... but my last experiments with the current ECMA schemas weren't so
> successful:
> https://stackoverflow.com/questions/46869482/
>
>
> On 3/9/18 2:05 PM, Murphy, Mark wrote:
> > Since JAXB is being dropped from Java SE (deprecated in Java 9, removed
> in Java 11), I don't think that this will be a problem. There may be other
> marshallers out there, but the more immediate problem is that we need to
> remove all JAXB code from POI because we can no longer rely on the JVM
> implementation, and the JAXB project is GPL code.
>
>
>
Re: publishing poi xmlbeans jars
Posted by Andreas Beeker <ki...@apache.org>.
There's a workaround for the GPL problem:
https://issues.apache.org/jira/browse/LEGAL-264
... but my last experiments with the current ECMA schemas weren't so successful:
https://stackoverflow.com/questions/46869482/
On 3/9/18 2:05 PM, Murphy, Mark wrote:
> Since JAXB is being dropped from Java SE (deprecated in Java 9, removed in Java 11), I don't think that this will be a problem. There may be other marshallers out there, but the more immediate problem is that we need to remove all JAXB code from POI because we can no longer rely on the JVM implementation, and the JAXB project is GPL code.
RE: publishing poi xmlbeans jars
Posted by "Murphy, Mark" <mu...@metalexmfg.com>.
Since JAXB is being dropped from Java SE (deprecated in Java 9, removed in Java 11), I don't think that this will be a problem. There may be other marshallers out there, but the more immediate problem is that we need to remove all JAXB code from POI because we can no longer rely on the JVM implementation, and the JAXB project is GPL code.
-----Original Message-----
From: Javen O'Neal [mailto:onealj@apache.org]
Sent: Thursday, March 08, 2018 9:24 PM
To: POI Developers List <de...@poi.apache.org>
Subject: Re: publishing poi xmlbeans jars
+1 sending it back to Incubator or subproject of Commons.
+0.9 as a subproject of POI.
Would prefer Xmlbeans to have its own PMC to make it easier for other Apache devs to make changes, but given how stable/mature it is, the support volume should be low.
If/when POI does replace XMLBeans for a more memory efficient/faster XML library, it'd be awkward for our PMC to manage a product we don't use. We can move it out to incubator, attic, or put it up for adoption when that time comes.
As long as the board doesn't have reservations about us subprojecting XMLBeans and then making another change in a couple years, I'm fine with taking XMLBeans as a subproject of POI.
On Thu, Mar 8, 2018, 10:50 Dominik Stadler <do...@gmx.at> wrote:
> +1
>
> On Wed, Mar 7, 2018 at 11:20 PM, pj.fanning <fa...@yahoo.com> wrote:
>
> > +1
> >
> >
> >
> > --
> > Sent from:
> > http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org For
> > additional commands, e-mail: dev-help@poi.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by Javen O'Neal <on...@apache.org>.
+1 sending it back to Incubator or subproject of Commons.
+0.9 as a subproject of POI.
Would prefer Xmlbeans to have its own PMC to make it easier for other
Apache devs to make changes, but given how stable/mature it is, the support
volume should be low.
If/when POI does replace XMLBeans for a more memory efficient/faster XML
library, it'd be awkward for our PMC to manage a product we don't use. We
can move it out to incubator, attic, or put it up for adoption when that
time comes.
As long as the board doesn't have reservations about us subprojecting
XMLBeans and then making another change in a couple years, I'm fine with
taking XMLBeans as a subproject of POI.
On Thu, Mar 8, 2018, 10:50 Dominik Stadler <do...@gmx.at> wrote:
> +1
>
> On Wed, Mar 7, 2018 at 11:20 PM, pj.fanning <fa...@yahoo.com> wrote:
>
> > +1
> >
> >
> >
> > --
> > Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> > For additional commands, e-mail: dev-help@poi.apache.org
> >
> >
>
Re: publishing poi xmlbeans jars
Posted by Dominik Stadler <do...@gmx.at>.
+1
On Wed, Mar 7, 2018 at 11:20 PM, pj.fanning <fa...@yahoo.com> wrote:
> +1
>
>
>
> --
> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: publishing poi xmlbeans jars
Posted by "pj.fanning" <fa...@yahoo.com>.
+1
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by Alain FAGOT BÉAREZ <ab...@for-scala.it>.
+1
Je 2018-03-07 14:40, Dave Fisher skribis:
> 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 <mu...@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:fanningpj@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-unsubscribe@poi.apache.org For additional
>> commands, e-mail: dev-help@poi.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
>> For additional commands, e-mail: dev-help@poi.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by Andreas Beeker <ki...@apache.org>.
Although I think that in the long-term we should go away from maintaining another apache project,
I don't have a better plan for the mid-term ... so +1.
I also think, that the svn + history approach is better than keeping it under POI root.
Even if we don't bring XmlBeans uptodate with annotations and other bling stuff,
the community can benefit from various existing and upcoming bugfixes.
On 3/7/18 7:18 PM, Greg Woolsey wrote:
> +1
>
> On Wed, Mar 7, 2018 at 10:03 AM Mark Murphy <jm...@gmail.com> wrote:
>
>> +1
>>
>>
>> On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher <da...@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 <mu...@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:fanningpj@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
>>>
>>>
Re: publishing poi xmlbeans jars
Posted by Greg Woolsey <gr...@gmail.com>.
+1
On Wed, Mar 7, 2018 at 10:03 AM Mark Murphy <jm...@gmail.com> wrote:
> +1
>
>
> On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher <da...@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 <mu...@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:fanningpj@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-unsubscribe@poi.apache.org For additional
> > commands, e-mail: dev-help@poi.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> > > For additional commands, e-mail: dev-help@poi.apache.org
> > >
> >
> >
>
Re: publishing poi xmlbeans jars
Posted by Mark Murphy <jm...@gmail.com>.
+1
On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher <da...@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 <mu...@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:fanningpj@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-unsubscribe@poi.apache.org For additional
> commands, e-mail: dev-help@poi.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> > For additional commands, e-mail: dev-help@poi.apache.org
> >
>
>
[VOTE][RESULTS] Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
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 <da...@comcast.net> wrote:
>
>
>> On Apr 2, 2018, at 10:23 AM, Dave Fisher <dave2wave@comcast.net <ma...@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 <jmarkmurphy@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> So where are we on this?
>>>
>>> On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher <dave2wave@comcast.net <ma...@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 <murphymdev@metalexmfg.com <ma...@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:fanningpj@yahoo.com <ma...@yahoo.com>]
>>>>> Sent: Tuesday, March 06, 2018 4:35 PM
>>>>> To: dev@poi.apache.org <ma...@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-unsubscribe@poi.apache.org <ma...@poi.apache.org> For additional
>>>> commands, e-mail: dev-help@poi.apache.org <ma...@poi.apache.org>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org <ma...@poi.apache.org>
>>>>> For additional commands, e-mail: dev-help@poi.apache.org <ma...@poi.apache.org>
>>>>>
>>>>
>>>>
>>
>
Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
> On Apr 2, 2018, at 10:23 AM, Dave Fisher <da...@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 <jm...@gmail.com> wrote:
>>
>> So where are we on this?
>>
>> On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher <da...@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 <mu...@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:fanningpj@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-unsubscribe@poi.apache.org For additional
>>> commands, e-mail: dev-help@poi.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
>>>> For additional commands, e-mail: dev-help@poi.apache.org
>>>>
>>>
>>>
>
Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
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 <jm...@gmail.com> wrote:
>
> So where are we on this?
>
> On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher <da...@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 <mu...@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:fanningpj@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-unsubscribe@poi.apache.org For additional
>> commands, e-mail: dev-help@poi.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
>>> For additional commands, e-mail: dev-help@poi.apache.org
>>>
>>
>>
Re: publishing poi xmlbeans jars
Posted by Mark Murphy <jm...@gmail.com>.
So where are we on this?
On Wed, Mar 7, 2018 at 12:40 PM, Dave Fisher <da...@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 <mu...@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:fanningpj@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-unsubscribe@poi.apache.org For additional
> commands, e-mail: dev-help@poi.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> > For additional commands, e-mail: dev-help@poi.apache.org
> >
>
>
Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
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 <mu...@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:fanningpj@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-unsubscribe@poi.apache.org For additional commands, e-mail: dev-help@poi.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
RE: publishing poi xmlbeans jars
Posted by "Murphy, Mark" <mu...@metalexmfg.com>.
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:fanningpj@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-unsubscribe@poi.apache.org For additional commands, e-mail: dev-help@poi.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by "pj.fanning" <fa...@yahoo.com>.
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-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
NABBLE Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
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 <jm...@gmail.com> 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 <fa...@yahoo.com> 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-unsubscribe@poi.apache.org
>> For additional commands, e-mail: dev-help@poi.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
Sent from my iPhone
> On Mar 6, 2018, at 8:47 AM, Mark Murphy <jm...@gmail.com> 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 <fa...@yahoo.com> 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-unsubscribe@poi.apache.org
>> For additional commands, e-mail: dev-help@poi.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by Mark Murphy <jm...@gmail.com>.
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 <fa...@yahoo.com> 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-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: publishing poi xmlbeans jars
Posted by "pj.fanning" <fa...@yahoo.com>.
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-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
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 <da...@comcast.net> 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 <jmarkmurphy@gmail.com <ma...@gmail.com>> wrote:
>>
>> That will make things a lot easier. Thanks Dave.
>>
>> On Fri, Mar 2, 2018 at 2:45 PM, Dave Fisher <dave2wave@comcast.net <ma...@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 <dave2wave@comcast.net <ma...@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 <jmarkmurphy@gmail.com <ma...@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 <fanningpj@yahoo.com <ma...@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-unsubscribe@poi.apache.org <ma...@poi.apache.org>
>>>>>> For additional commands, e-mail: dev-help@poi.apache.org <ma...@poi.apache.org>
>>>>>>
>>>>>>
>>>>
>>>
>>>
>
Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
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 <jm...@gmail.com> wrote:
>
> That will make things a lot easier. Thanks Dave.
>
> On Fri, Mar 2, 2018 at 2:45 PM, Dave Fisher <da...@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 <da...@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 <jm...@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 <fa...@yahoo.com> 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-unsubscribe@poi.apache.org
>>>>> For additional commands, e-mail: dev-help@poi.apache.org
>>>>>
>>>>>
>>>
>>
>>
Re: publishing poi xmlbeans jars
Posted by Mark Murphy <jm...@gmail.com>.
That will make things a lot easier. Thanks Dave.
On Fri, Mar 2, 2018 at 2:45 PM, Dave Fisher <da...@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 <da...@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 <jm...@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 <fa...@yahoo.com> 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-unsubscribe@poi.apache.org
> >>> For additional commands, e-mail: dev-help@poi.apache.org
> >>>
> >>>
> >
>
>
Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
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 <da...@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 <jm...@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 <fa...@yahoo.com> 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-unsubscribe@poi.apache.org
>>> For additional commands, e-mail: dev-help@poi.apache.org
>>>
>>>
>
Re: publishing poi xmlbeans jars
Posted by Dave Fisher <da...@comcast.net>.
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 <jm...@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 <fa...@yahoo.com> 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-unsubscribe@poi.apache.org
>> For additional commands, e-mail: dev-help@poi.apache.org
>>
>>
Re: publishing poi xmlbeans jars
Posted by Mark Murphy <jm...@gmail.com>.
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 <fa...@yahoo.com> 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-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>