From general-return-1754-archive-asf-public=cust-asf.ponee.io@attic.apache.org Fri Mar 2 19:28:53 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id E8D1818062F for ; Fri, 2 Mar 2018 19:28:52 +0100 (CET) Received: (qmail 62062 invoked by uid 500); 2 Mar 2018 18:28:52 -0000 Mailing-List: contact general-help@attic.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@attic.apache.org Delivered-To: mailing list general@attic.apache.org Received: (qmail 62046 invoked by uid 99); 2 Mar 2018 18:28:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2018 18:28:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D3E311A0443 for ; Fri, 2 Mar 2018 18:28:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Ob1E6Td8f_4G for ; Fri, 2 Mar 2018 18:28:47 +0000 (UTC) Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 2C0D45F126 for ; Fri, 2 Mar 2018 18:28:47 +0000 (UTC) Received: by mail-qk0-f181.google.com with SMTP id s188so13109788qkb.2 for ; Fri, 02 Mar 2018 10:28:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=EftiQ7+NN4pL3yYTCHefq29fUK0UuNRvvPEEZICx2D8=; b=REPlq3iX9pgtGUu11rWV+IEeuePX71fQhNlgr9K2hfuWGDMxlH+dhp7fmmqcL8voIn LUa/vfQeUXlLAdm6/Qm5Cha2F1cuhWsWSYBGZu22a9fg4auQboHTWNW6Klus2V3SKNFD nrF+p1hkvIHnpLTHrxhzWwhiYTvOe4fWVSNlDwkvHY3qfnOYRp/BnFQVntkbzirg1V9I CaVUB5o9qhx8f3Upm9Zk1GcAwps19rgsBeBOfSbvBIyPNQFjXDGpIekNGHlFTPb7zOVI osDxKFFk7t2j9PUJ+bl1BHL4Kgi7lEhmk2TjHJ0X+FzuZDNnhsSDb45Jk4iqx4uRiT9Z DuwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EftiQ7+NN4pL3yYTCHefq29fUK0UuNRvvPEEZICx2D8=; b=Y/eaJAOSOEQT5yMVS6h69b5n+NXH2AF9jSUiiIEVrXWR+T+S0Dhiu3PVQFywif0hb1 oFsOowHGrlfz4RSmrBNqcTmnGUFvWw/pcd27wIDxwrPlZw4b9k5PLwbAaDb3xIonIb+9 Fr/h333J2fXH8yMXteO4kJKTbCVVBYYm7Lew8mCJV2a4ZlXhtAcMSy93pd4Rsvu7m84C nzmRIhSPeKPng7YVnXmnrMNNPtRP5uGDfcIbz/B7oiMpXBRbl9idi8OJ2oyGyfdTTY/8 y5YoXoI/4KSUjrA6c0cCeuZ31lUl37A8/MY4Hb4HlDbuvDv0kCTZJmV0SOiVNYOKEgoi UxLA== X-Gm-Message-State: AElRT7FmYKTvJQIcbeuriePbE3KsH4djrRo+QBpdxTJYEwvnoUZKs1EI w8lwfofIpKldhEZMIfie7xNoBBuTCQdZERzQMel2GA== X-Google-Smtp-Source: AG47ELvfqNfudE8SS2e0Ui/KUeKI8g+ubb+sZS8OUPmzo18amS6DRy/Ox8KaWRC3IcRbGC5i5tLT+P/e0VoK9+9dmAs= X-Received: by 10.55.89.194 with SMTP id n185mr9907817qkb.111.1520015326332; Fri, 02 Mar 2018 10:28:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.59.165 with HTTP; Fri, 2 Mar 2018 10:28:45 -0800 (PST) From: Mark Murphy Date: Fri, 2 Mar 2018 13:28:45 -0500 Message-ID: Subject: Getting XMLBeans out of the attic To: general@attic.apache.org Content-Type: multipart/alternative; boundary="001a114c9778944cf205667225c1" --001a114c9778944cf205667225c1 Content-Type: text/plain; charset="UTF-8" So going back to a previous thread, what would be involved with POI taking on XMLBeans as a second product? I believe we have enough PMC members willing to take it on and provide releases. We also have committers ready and waiting to make updates. We benefit from bug fixes, other users benefit from public releases, there are no naming conflicts, and we already have a functioning PMC capable of running an ASF project. The problem as I see it is that not only do Apache projects (Solar, Tika) use POI, but users of those projects also use XMLBeans to consume XML. Having two semi independent versions of XMLBeans in the classpath could be problematic. The Attic website says: Process of leaving the Attic again Options are: - Forking the project - we'll link to any forks which have been created so please let us know - Restarting the community in the Apache Incubator - Recreating a PMC for the project We'll take "Recreating a PMC for the project" Alex. How do we move forward with POI taking on XMLBeans as a second project. ---------- Forwarded message ---------- From: Upayavira To: "Javen O'Neal" , POI Developers List < dev@poi.apache.org> Cc: general@attic.apache.org, dev@xmlbeans.apache.org Bcc: Date: Tue, 07 Nov 2017 17:16:04 +0000 Subject: Re: Non-maintainer upload of bugfixes for the XMLBeans library in the Attic Could POI take on XMLbeans as a second product? If they intend to maintain it, and can provide 3+ PMC members who will vote on releases, then presumably the POI project could make releases of the Apache XMLBeans product? Then there's no naming issues, everyone benefits from public releases. At such a point as there is enough interest, it can fork back into its own community. POI committers would gain commit rights on an XMLBeans repo. Upayavira On Tue, 7 Nov 2017, at 04:59 PM, Javen O'Neal wrote: > Any other project using XMLBeans on Android would likely be affected by > the > same issue. Making the XMLBeans update within the POI source code or POI > maven coordinates would make it more difficult for others to find this > update. > > If we had to change the Java package name to > org.apache.poi.internal.xmlbeans, it would take a bit of trickery to > allow > users to continue using the official releases, XMLBeans 2.3.0 or 2.6.0 if > the bug doesn't affect them. > > On Nov 7, 2017 03:41, "sebb" wrote: > > On 7 November 2017 at 07:20, jan iversen wrote: > > > > > > Sent from my iPad > > > >> On 6 Nov 2017, at 21:47, Dominik Stadler wrote: > >> > >> Hi, > >> > >> The Apache XMLBeans library was moved to the Attic a few years ago > >> (05/2014), however Apache POI still uses the library as it's core XML > >> binding framework. > >> > >> While the Apache POI PMC and the development community is already > >> discussing possible replacements for some time, use of XMLBeans is still > >> deeply rooted and thus hard to replace quickly. > >> > >> Over time, we discovered a few grave bugs in XMLBeans which lead to > >> bug-reports that we cannot fix ourselves. > >> > >> Therefore we would like to start discussion about an NMU of XMLBeans to > get > >> a fix for the most pressing issues. > >> > >> See https://bz.apache.org/bugzilla/show_bug.cgi?id=59268 for the full > >> discussion,and https://github.com/pjfanning/xmlbeans for a fork with > >> initial bugfixes. > >> > >> Among others, we would like to fix the following, changes for these are > >> already applied and verified in the github fork: > >> * the official XMLBeans-JAR contains duplicate classes, making it > >> impossible to use it on Android as the Android build fails due to this > >> * cannot use Unicode surogates, thus affecting use of Apache POI in > >> non-latin-script areas > >> * Remove W3C and JAVAX classes which are not needed any more since Java 6 > >> (current Apache POI development is on Java 8) > >> > >> > >> So is there a precedent for something like this? What steps do we need to > >> make to get an updated version of XMLBeans published? > > > > Others might have examples of how it was done in the past. Making a fork > on e.g. github with a new non-apache name is the simplest way. > > > > However if I understand it correct your intention is only to maintain > XMLbeans for the benefit of POI. That gives you (as I see it) another > option, you can include the source code in your project and do the > patches > as part of your project. > > I think it would need to be in a different package to avoid possible > confusion with the original. > And it should be obvious that it is not intended for external use. > > e.g. org.apache.poi.internal.xmlbeans > > > rgds > > jan i > >> > >> > >> Thanks... Dominik > >> > >> On behalf of the Apache POI PMC > >> > >> > >> About Apache POI > >> ----------------------- > >> > >> Apache POI is well-known in the Java field as a library for reading and > >> writing Microsoft Office file formats, such as Excel, PowerPoint, Word, > >> Visio, Publisher and Outlook. It supports both the older (OLE2) and > >> new (OOXML - Office Open XML) formats. > >> > >> See https://poi.apache.org/ for more details > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org > For additional commands, e-mail: dev-help@poi.apache.org --001a114c9778944cf205667225c1--