Hi Ralph, I have put together a minimal commit that uses the standard license feature: https://git.eclipse.org/r/c/bpmn2/org.eclipse.bpmn2/+/168696
Please review and merge. Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Wed, 2 Sep 2020 at 17:38, Ralph Soika <ralph.so...@imixs.com> wrote: > Hello, > > sorry to bother you again, but I think I need you help. > I overtook the projects: > > - mdt-bpmn2 <https://projects.eclipse.org/projects/modeling.mdt.bpmn2> > - "Eclipse Business Process Model and Notation (BPMN2)" > - soa-bepl <https://projects.eclipse.org/projects/soa.bpel> - > "Eclipse BPEL Designer" > > a view weeks ago. I tried to prepare an updated version for both projects > fixing some minor technical issues with the code compatibility in > Eclipse-2020-09. > > Now Ed Merks recognized that the license information in the > feature.xml/features.properties are in a bad shape. > > I tried to fix it but - as Ed told me - with no success (Bug 566499 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=566499>). I do not think > that I am in a position to fix this in a way that fulfills all the > requirements form the Eclipse Foundation. The license text was initial > created 9 and 10 years ago and was never changed by anybody. > The initial contribution for mdt-bpmn2 project was form RedHat. > > Can some one help me to edit these two files in a way that those files > meet the requirements form the Eclipse foundation? > I already have updated the license.html files to the latest Version 2.0 of > the Eclipse Public License. > And I thought that it should be fine if I add the text version of this > license directly into the features.xml file. (initial the license text was > part of the features.properties file). But as Ed told me this is not > accepted. > > Attached in this e-mail I send you the files, so that someone can take a > look into it. Again, if this were a purely technical problem, I would like > to solve it myself. However, as this is a legal problem, I do not dare to > make any further changes here by myself. > > > Thanks for your help in advance > > Best regards > Ralph > > > > > On 01.09.20 23:23, Wayne Beaton wrote: > > Right. I forgot about the Eclipse License Feature. > > FWIW, I've opened a bug > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=566576> to add this to the > Eclipse Project Handbook. > > Should (or do) we have this captured in the simultaneous release > documentation? > > Wayne > > On Tue, Sep 1, 2020 at 5:18 PM Matthias Sohn <matthias.s...@gmail.com> > wrote: > >> On Tue, Sep 1, 2020 at 10:52 PM Ralph Soika <ralph.so...@imixs.com> >> wrote: >> >>> Hi, >>> >>> in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text >>> seems to be outdated (it is still from the year 2011). >>> >>> Can someone please point me to a page or another eclipse project, where >>> I can see the correct Eclipse license text, so that I can copy the text >>> into my features.properties and license.html artifacts. Especially the text >>> for the feature.properties has a curious formatting. So I am looking for a >>> features.properties file where I can copy this formatting to avoid breaking >>> the text formatting at some line where I should not do so. >>> >> we use the eclipse license feature [1] e.g. here in the egit feature [2]. >> The version of the license feature is defined in the target platform we >> use [3]. >> In feature.properties we use [4]. If there is a new version of the >> license we >> update the version of the license feature we include in the target >> platform. >> >> [1] >> https://git.eclipse.org/r/plugins/gitiles/cbi/org.eclipse.license/+/refs/heads/master >> [2] >> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.xml#8 >> [3] >> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit.target/egit-4.16-staging.target#25 >> [4] >> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.properties#22 >> >> >> -Matthias >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >> > > > -- > > Wayne Beaton > > Director of Open Source Projects | Eclipse Foundation, Inc. > > Join us at our virtual event: EclipseCon 2020 > <https://www.eclipsecon.org/2020> - October 20-22 > > _______________________________________________ > cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > > -- > > *Imixs Software Solutions GmbH* > *Web:* www.imixs.com *Phone:* +49 (0)89-452136 16 > *Office:* Agnes-Pockels-Bogen 1, 80992 München > Registergericht: Amtsgericht Muenchen, HRB 136045 > Geschaeftsführer: Gaby Heinle u. Ralph Soika > > *Imixs* is an open source company, read more: www.imixs.org > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
