Hi,
It sounds good.
I've a concern- Java 7's extended support is until July 22. Is it then good to
upgrade directly to java 8?
Aparna
On Tuesday, April 21, 2020, 9:15:29 PM GMT+5:30, Patrick Tasse
<patrick.ta...@gmail.com> wrote:
Hi,
There are a lot of deprecated methods and classes in SWTBot. Most (maybe all)
have been deprecated for at least one yearly release cycle. We could take the
opportunity to remove these deprecated APIs, thus making the 3.0.0 a true major
version increase.
At the same time, we could upgrade all plug-ins to use the Java 8 execution
environment. Most plug-ins are still using Java 6, whose extended support ended
in 2018.
How does that sound?
Patrick
On Sat, Apr 18, 2020 at 8:03 AM Jonah Graham <jo...@kichwacoders.com> wrote:
Semantic versioning should apply to the bundles, the project can (and should)
use the project version as part of marketing. So major new features can mean
the project has a major new version, even though some bundles do not have a
version bump.
HTH, Jonah
On Sat., Apr. 18, 2020, 07:58 Lorenzo Bettini, <lorenzo.bett...@gmail.com>
wrote:
HiBut then the major version shouldn't be increased, since there's no API
breakage. Otherwise we break the semantics of semantic versioning..Lorenzo
Il Ven 17 Apr 2020, 09:33 Aparna Argade <apr...@yahoo.com> ha scritto:
Hi Lorenzo,There is no API breakage, but 2 new plugins
(org.eclipse.swtbot.junit5_x and org.eclipse.swtbot.eclipse.junit5.headless)
and a feature (org.eclipse.swtbot.junit5) are added. Overall, the contribution
is of lines +3566, -234 (includes version change) Bug 559531
Aparna
On Friday, April 17, 2020, 12:13:40 PM GMT+5:30, Lorenzo Bettini
<lorenzo.bett...@gmail.com> wrote:
Hi
Just for curiosity, does JUnit 5 support introduce API breakage? I mean
breakage to justify major version change?
CheersLorenzo
Il Mer 15 Apr 2020, 14:49 Patrick Tasse <patrick.ta...@gmail.com> ha scritto:
Hi,
We are planning to release SWTBot version 3.0.0 in the Eclipse 2020-06 release.
The major version change is due to the introduction of support for JUnit 5.
We also intend to migrate the SWtBot project to use the Eclipse Public License
v2.0 [1].
This change only involves updating file headers and notices. It is not
necessary to gain permission from all copyright holders. More information can
be found in the EPL 2.0 FAQ [2].
This change is being tracked by Bug 562163 [3]. If you have any issues with
this migration, please comment on the bug.
Patrick
[1] https://www.eclipse.org/legal/epl-2.0/[2]
https://www.eclipse.org/legal/epl-2.0/faq.php[3]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=562163_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/swtbot-dev
_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/swtbot-dev
_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/swtbot-dev
_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/swtbot-dev
_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/swtbot-dev
_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/swtbot-dev
_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/swtbot-dev
