Hello
There I totally agree with Benoit. I was part
of the team that see no bad reason for publishing the
Papyrus Junit framework and moreover I see only good reason.
There were several discussions on it that lead
at least to these public elements: bug [1] and patch [2].
But there also a lot of other propositions…
I can look again to it with a more precise
specification from the Papyrus group.
Francois for Papyrus
[1]:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=517711
[2]:
https://git.eclipse.org/r/#/c/98541/
Hi,
2 years ago I raised a similar problem [1], at
the end there was only an agreement to publish the developer
plugins and test framework in a nightly update site on
Hudson.
These last 2 years didn’t changed my mind (on
the contrary).
I still thinks that we should move “developer
plugins” and “junit framework” into the papyrus release (not
in the release train, maybe as part of the toolsmith
feature)
(or remove them from core repository)
Basically this update site shouldn’t exist [2]
and pretty much everything should be in Papyrus release
(except one of the template plugin used for
code generation)
ð
Can anyone give me a good reason for not
publishing the junit framework?
Regards,
Benoit
1:
https://dev.eclipse.org/mhonarc/lists/mdt-papyrus.dev/msg02657.html
2:
https://hudson.eclipse.org/papyrus/job/Papyrus-Master-Developer/lastSuccessfulBuild/artifact/repository/plugins/
Ps: @Ernesto: If you don’t use matrix then, you
may simply relax upper constraint for nattable
plugins[3.0.0, 6.0.0(
De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Ernesto Posse
Envoyé : mercredi 4 octobre 2017 18:17
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Papyrus JUnit feature
Oxygen update site
Yes, the integration milestone would
not pose much trouble to do and would be
accessible through the milestones update site.
I'll link the address to it when the build is
done, published and available, which should be
around tomorow evening.
HTH,
Quentin
On 4 October
2017 at 17:42, Ernesto Posse <eposse@xxxxxxxxxxxxx>
wrote:
Ah! That
explains it. Thanks. But I think we should
have that integration build anyway, for our
releases build.
Sorry to cause additional
confusion! The bumping to version
4.0.0 for org.eclipse.papyrus.infra.nattable.common
was made just a week ago as part of https://git.eclipse.org/r/#/c/105759/.
It was another
bundle, org.eclipse.papyrus.infra.nattable, that
was bumped to 4.0.0 in the Gerrit
change that I referred to below and
that became part of the Oxygen.1
release... So this explains why it is
still version 3.0.0
of org.eclipse.papyrus.infra.nattable.common
in the release repo for the Oxygen.1
release (as expected).
On
4 October 2017 at 17:20, Peter
Cigéhn <peter.cigehn@xxxxxxxxx>
wrote:
Maybe I do
something wrong, but when
checking with the Oomph
Repository Explorer view,
there still seem to be
something strange. As Ernesto
points out, when checking the
Oxygen release (and staging)
repo, the latest version of
the
org.eclipse.papyrus.infra.nattable.common
bundle is still 3.0.0:
But when checking
the nightly build, it has been
bumped to next major version:
Not sure if
this explains the issues
that Ernesto have
identified, that the
dependency on version
[4.0.0, 5.0.0) for this
bundle cannot be resolved
when using the SimRel repo
for Oxygen. Sure, if the
bumping of major version
was made *after* the
release of Oxygen.1, and
that version 4.0.0 only
exist for the nightly
builds. But to my
understanding the bumping
of major version was made
before the Oxygen.1
release (at least looking
at when https://git.eclipse.org/r/#/c/102439/
was merged, which is the
change that bumped the
version also on the Oxygen
maintenance branch).
How come that
the version 4.0.0 of the
org.eclipse.papyrus.infra.nattable.common
bundle is not actually
included in the Oxygen.1
release?
On 4
October 2017 at 17:00,
LE MENEZ Quentin <Quentin.LEMENEZ@xxxxxx>
wrote:
Hi,
The
main problem is,
in this case,
that your target
depends on a
nightly and a
release. Of
course I do not
expect you to
move to Photon
but as there is
no release of
the dev tools
along the main
plugins and
these progress
with the related
nightly (in this
case oxygen
3.2.0 for SR2) I
would advise you
to change, for
the time being,
your papyrus to
the Oxygen
nightly.
Of
course if that
is preferable to
you I could also
push a milestone
integration
release (papyrus
main plugins)
for you to base
yourself upon
instead of the
latest release.
As
for Nattable,
the required
plugins are
indeed in 4.0.0
(cf [1]) hence
the feature
should indeed
have been
changed to
reflect this
(major+1 in this
case).
Quentin
[1]
https://hudson.eclipse.org/papyrus/job/Papyrus-Oxygen/lastSuccessfulBuild/artifact/repository/plugins/
De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de
Ernesto Posse
Envoyé :
mercredi 4
octobre 2017
16:44
À :
Papyrus Project
list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet :
Re:
[mdt-papyrus.dev]
Papyrus JUnit
feature Oxygen
update site
Hi, some more
questions
inline:
Hi
Ernesto,
This
job is not
building
against photon
(Nattable
backported the
changes in the
streams/3.0-maintenance) hence the dependency (nattable is now 4.0.0,
even in oxygen
;p).
Huh. Well,
that's
confusing. Any
other things
that have been
backported
that we should
be aware of?
As
this feature
is not
supposed to be
released, it
is mainly used
to run our
tests and has
some dev
tools, there
is no
“backup”. If
you are
building
against the
released 3.1.0
you will have
to depend on a
local
solution, or
depend on the
nightly.
Although there
are some talk
about cleaning
it up and
releasing
parts of it
this is not
done yet.
We are
building
against 3.1
now. At the
moment there
are no plans
to move to
Photon, so we
need to still
be able to do
maintenance on
Oxygen.
What
is you TP
and/or use of
the dev tools
?
We use the
Papyrus JUnit
feature for
tests,
naturally, and
we should not
have to
disable our
tests from the
build. Our
(release) TP
includes the
following:
I see that
http://download.eclipse.org/staging/oxygen
has Papyrus
3.1 I've also
looked at the
milestones
update sites
for 3.x (e.g.
http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/3.1/RC4/)
but they all
seem to have
org.eclipse.papyrus.infra.nattable
3.0.0. I also
looked at the
Oxygen nightly
(http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/oxygen
which points
to
https://hudson.eclipse.org/papyrus/job/Papyrus-Oxygen/lastSuccessfulBuild/artifact/repository/features/)
and it also
seems to have
nattable 3.0.0
as well. So,
nattable was
backported to
the
streams/3.0-maintenance
branch but it
is not being
published in
the milestones
or nightly
update sites?
Where is it
then?
_______________________________________________
mdt-papyrus.dev
mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your
delivery options,
retrieve your
password, or
unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev