From 72ffd45518baf4fca83f44826e9a6617f61a2c74 Mon Sep 17 00:00:00 2001
From: Christoph Knoedlseder <knoedlsede@fim.uni-passau.de>
Date: Wed, 9 Oct 2024 11:18:40 +0200
Subject: [PATCH] better sources for some perfumes

---
 .../de/jsilbereisen/perfumator/data/perfumes/Assert_all.json    | 2 +-
 .../jsilbereisen/perfumator/data/perfumes/JFrame_dispose.json   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/main/resources/de/jsilbereisen/perfumator/data/perfumes/Assert_all.json b/src/main/resources/de/jsilbereisen/perfumator/data/perfumes/Assert_all.json
index c2a9e63..ed3c54f 100644
--- a/src/main/resources/de/jsilbereisen/perfumator/data/perfumes/Assert_all.json
+++ b/src/main/resources/de/jsilbereisen/perfumator/data/perfumes/Assert_all.json
@@ -3,7 +3,7 @@
   "description": "The \"org.junit.jupiter.api.assertAll\" is used to group multiple individual assertions together. The advantage of using this method to group the assertions instead of calling them individually is that if one assertion fails, the others are still executed. Therefore, the user gains insight on the results of all tests, instead of only the tests up to the failed assertion, where the thrown exception would otherwise terminate the test execution.",
   "detectorClassSimpleName": "AssertAllDetector",
   "i18nBaseBundleName": "assertAll",
-  "sources": ["https://stackoverflow.com/questions/40796756/assertall-vs-multiple-assertions-in-junit5"],
+  "sources": ["https://www.baeldung.com/junit5-assertall-vs-multiple-assertions"],
   "relatedPattern": null,
   "additionalInformation": null
 }
\ No newline at end of file
diff --git a/src/main/resources/de/jsilbereisen/perfumator/data/perfumes/JFrame_dispose.json b/src/main/resources/de/jsilbereisen/perfumator/data/perfumes/JFrame_dispose.json
index 32ab802..3e5800c 100644
--- a/src/main/resources/de/jsilbereisen/perfumator/data/perfumes/JFrame_dispose.json
+++ b/src/main/resources/de/jsilbereisen/perfumator/data/perfumes/JFrame_dispose.json
@@ -3,7 +3,7 @@
   "description": "Instead of calling \"System.exit\", which completely terminates the java virtual machine, the \"javax.swing.JFrame.dispose\" method closes the frame and its assigned resources in a more controlled manner. Closing the application this way, one has to make sure to terminate all running threads programmatically. While this may seem like a downside, it ultimately provides the most control, as ongoing processes can be completed before the program is terminated.",
   "detectorClassSimpleName": "JFrameDisposeDetector",
   "i18nBaseBundleName": "jFrameDispose",
-  "sources": ["Programmierung II - Uni Passau", "https://stackoverflow.com/questions/13360430/jframe-dispose-vs-system-exit"],
+  "sources": ["Programmierung II - Uni Passau", "https://docs.oracle.com/javase/8/docs/api/java/awt/Window.html#dispose--"],
   "relatedPattern": "BUG",
   "additionalInformation": null
 }
\ No newline at end of file