You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: news/4.37/pde.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,28 @@ A special thanks to everyone who [contributed to PDE](acknowledgements.md#plug-i
4
4
5
5
## General Updates
6
6
7
+
### JUnit Plugin-test launches
8
+
9
+
<details>
10
+
<summary>Contributors</summary>
11
+
12
+
-[Christoph Läubrich ](https://github.com/laeubi)
13
+
</details>
14
+
15
+
PDE previously has created JUnit Plugin-test launches with some broad inclusion settings and defaults that do not always fit different project setups.
16
+
From now on, it uses a more minmal aproach wehn creating new JUnit Plugin-test launches by default that is only selecting the test-plugin and leverage
17
+
the option to include all required dependencies automatically.
18
+
19
+
This results in much smaller launches that start up faster and do not pull in everything in your workspace by default what is exspecially a problem when
20
+
many independent components in a workspace are to be tested.
21
+
22
+
Beside of this it is now possible to configure the used default settings for new launches to adapt to individual needs, because of this
23
+
we **strongly recommend** you review these settings and make sure they fit your needs after an upgrade.
As this only affects new launches, you either need to adapt existing launches or delete older ones so they are created with fresh settings on the next run.
0 commit comments