I have updated my dependencies.
Hi Ralph,
I hope
you doing good.
Another
year, another round of updates…
I try
to update Graphiti to 0.19.0 for Eclipse 2022.06 and
the update of the simrel project failed again because
BPMN2 Modeler restricts Graphiti to 0.18.0. Could you
please open that up again?
Here’s
the build failure log:
https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/2838/
My
Gerrit change for the simrel project is
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/193534.
Best
regards,
Michael
Von: Wenz, Michael
Gesendet: Donnerstag, 20. Mai 2021 09:23
An: Ralph Soika <ralph.soika@xxxxxxxxx>
Betreff: RE: New Graphiti version for
Eclipse 2021-06
Thanks, that looks
good. I was able to install the BPMN Modeler from that
update site into my test Eclipse with Graphiti 0.18.0.
Opening up the
dependencies is probably a good idea, that would spare
us going through this procedure each year.
It seems that both
OSGI and Eclipse bundles support defining a minimum
version by something like this:
org.eclipse.graphiti;bundle-version="0.18.0"
But I’m not sure
what Maven/Tycho makes out of that, could be that it
interprets it as fixed dependency to just this
version.
What I usually do
(also I found this way back in recommendations on the
internet), is that I set the next mayor version as
upper bound. That allows the required project to
provide bugfixes and minor updates, but since the
mayor version needs to be increased for breaking or
API changes would still be a safety net for such
cases. The dependency would the look like this:
org.eclipse.graphiti;bundle-version="[0.18.0,1.0.0)"
or maybe
org.eclipse.graphiti;bundle-version="[0.18.0,2.0.0)"
As Explanation for
the syntax: the rectangular brackets “[“ or “]” mean
including this version, the round brackets “(“ or “)”
mean excluding this version.
As explanation why
using version 2 as excluded upper limit might be
better: there have been already discussions in the
past started from Eclipse side (Wayne Beaton) if
Graphiti should not move out of incubation. It might
be that we need to do that soon, so maybe directly
using 2.0.0 as the excluded upper limit would make
sense. In case we will do that and leave incubation,
Graphiti would update to 1.0.0 without any changes to
the API. The best guarantee for that is my lack of
time I can spend on the project and basically having
no further active committers any more…. ☹)
Best regards,
Michael
Hi Michael,
the build was successful and a new
updated version is now provided
http://download.eclipse.org/bpmn2-modeler/updates/stable/2021-06/1.5.3/
Can you verify if this is what you
expect?
Another question: I am using the
bundle-version
[0.14.0,0.18.0)
Why should I not change this in way
that I say : use graphiti version 0.18.0 or above. I
think I can trust in your work and there is no need to
set a fixed upper version number.
What would be the correct pattern to
describe this in a manifest file?
Best regards
Ralph
On 20.05.21
08:09, Wenz, Michael wrote:
HI Ralph,
Thanks for your
help in this. Yes, this is what I meant.
I created the
new Graphiti version 0.18.0 just this week, so far
there was just the 0.17.0 version in the simrel,
that is why simrel so far picked up that version.
Your build
probably points to our release update site for
0.17.0:
http://download.eclipse.org/graphiti/updates/0.17.0
and because of that uses the older version. The
0.18.0 milestone update site is at
http://download.eclipse.org/graphiti/updates/milestones/S-0.18.0M3-202105181817
, there is not yet a release update site.
Yes, the simrel
stuff is not easy to understand. It basically tries
to combine the given individual projects into one
thing that can work together by checking what is
available on the update sites of the individual
projects and if the restrictions the projects have
in their manifests can get resolved using the given
update sites.
Best regards,
Michael
Hi Michael,
what you mean is that I should
change in my MANIFEST.MF files lines like:
org.eclipse.graphiti;bundle-version="[0.14.0,0.18.0)",
org.eclipse.graphiti.ui;bundle-version="[0.14.0,0.18.0)",
into
org.eclipse.graphiti;bundle-version="[0.14.0,0.19.0)",
org.eclipse.graphiti.ui;bundle-version="[0.14.0,0.19.0)",
...right?
I wonder why my build took the
0.17.0 version instead of 0.18.0. Or is this just
because I build it some weeks ago?
Sorry for the stupid question, but
the the entire simrel build process is still a
mystery to me.
I already opened a bug report (https://bugs.eclipse.org/bugs/show_bug.cgi?id=573649)
and I will change my MANIFEST.MF files. So you can
monitor my changes.
Best regards
Ralph
On 19.05.21
14:23, Wenz, Michael wrote:
Hi Ralph,
I’m trying to
push a new version of Graphiti (0.18.0) for
Eclipse 2021-06. But the simrel aggregation voter
fails because it restricts Graphiti to 0.17.0:
04:53:39 [0]Only one of the following can be installed at once:
04:53:39 Graphiti (Incubation) 0.18.0.202105181817 (org.eclipse.graphiti 0.18.0.202105181817)
04:53:39 Graphiti (Incubation) 0.17.0.202005151449 (org.eclipse.graphiti 0.17.0.202005151449)
04:53:39
04:53:39 bundle(org.eclipse.graphiti 0.18.0.202105181817) is required by:
04:53:39 ValidationSet(main)
04:53:39 Contribution(Graphiti for SimRel 2021-06)
04:53:39 MappedRepository(https://download.eclipse.org/graphiti/updates/milestones/S-0.18.0M3-202105181817/)
04:53:39 Feature(org.eclipse.graphiti.feature.feature.group [0.18.0,0.19.0))
04:53:39 bundle(org.eclipse.graphiti 0.17.0.202005151449) is required by:
04:53:39 ValidationSet(main)
04:53:39 Contribution(SOA-BPMN2 Modeler)
04:53:39 MappedRepository(https://download.eclipse.org/bpmn2-modeler/updates/2021-06/1.5.3)
04:53:39 Feature(org.eclipse.bpmn2.modeler.runtime.jboss.feature.group 1.5.3)
04:53:39 InstallableUnit(org.eclipse.bpmn2.modeler.core 1.5.3.Final-v20210419-0844-B1)
Full build
log:
https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/2159/console
The open
Gerrit change for Graphiti simrel is:
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/180769
Could you as
last year push a new version of the SOA-BPMN2
Modeler that allows Graphiti 0.18.0?
The difference
between Graphiti 0.17.0 and 0.18.0 are very small,
there are just a couple of bug fixes, no changes
in the API or in behavior.
Best regards,
Michael
Michael Wenz
Expert Developer, BTP
Core FP R&C Core Dev BG (SE)
SAP SE Dietmar-Hopp-Allee 16,
69190 Walldorf, Germany
T +49 6227 7-61613, E michael.wenz@xxxxxxx
Please consider the impact on the
environment before printing this e-mail.
Pflichtangaben/Mandatory Disclosure
Statement:
http://www.sap.com/company/legal/impressum.epx
Diese E-Mail kann Betriebs- oder
Geschäftsgeheimnisse oder sonstige vertrauliche
Informationen enthalten. Sollten Sie diese
E-Mail irrtümlich erhalten haben, ist Ihnen eine
Kenntnisnahme des Inhalts, eine Vervielfältigung
oder Weitergabe der E-Mail ausdrücklich
untersagt. Bitte benachrichtigen Sie uns und
vernichten Sie die empfangene E-Mail.
Vielen Dank.
This e-mail may contain trade
secrets or privileged, undisclosed, or otherwise
confidential information. If you have received
this e-mail in error, you are hereby notified
that any review, copying, or distribution of it
is strictly prohibited. Please inform us
immediately and destroy the original
transmittal.
Thank you for your cooperation
--
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 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
