Merge pull request #1439 from jeffgbutler/eclipse-cleanup

Eclipse Cleanup

Author: jeffgbutler

core/mybatis-generator-core/src/site/xhtml/running/runningWithEclipse.xhtml

@@ -36,7 +36,7 @@
     </ol>
   </li>
   <li>Manually configure an update site that points to
-  <a href="https://mybatis.jfrog.io/artifactory/generator-eclipse-release/">https://mybatis.jfrog.io/artifactory/generator-eclipse-release/</a></li>
+  <a href="https://jeffgbutler.github.io/mybatis-generator-update-site/">https://jeffgbutler.github.io/mybatis-generator-update-site/</a></li>
   <li>Download the zipped eclipse update site from the GitHub release page
     (https://github.com/mybatis/generator/releases), unzip, and configure
     an update site that points to your unzipped directory.</li>

eclipse/org.mybatis.generator.eclipse.core.tests/META-INF/MANIFEST.MF

@@ -8,8 +8,7 @@ Bundle-RequiredExecutionEnvironment: JavaSE-17
 Require-Bundle: junit-jupiter-api;bundle-version="6.0.2",
  assertj-core;bundle-version="3.27.7"
 Automatic-Module-Name: org.mybatis.generator.eclipse.core.tests
-Export-Package: org.mybatis.generator.eclipse.core.tests,
- org.mybatis.generator.eclipse.core.tests.callback,
+Export-Package: org.mybatis.generator.eclipse.core.tests.callback,
  org.mybatis.generator.eclipse.core.tests.merge,
  org.mybatis.generator.eclipse.core.tests.merge.resources,
  org.mybatis.generator.eclipse.core.tests.merge.support

eclipse/org.mybatis.generator.eclipse.core.tests/src/org/mybatis/generator/eclipse/core/tests/RunAllTests.java

@@ -37,7 +37,7 @@ <h2>Build Overview</h2>
 regular Eclipse projects.</p>
 
 <h2>Feature Structure</h2>
-<p>There are eleven total projects that makeup the feature. Some projects are just for build support and testing.</p> 
+<p>There are nine total projects that makeup the feature. Some projects are just for build support and testing.</p> 
 <p>The published MBG feature is composed of five different Eclipse projects - a feature project,
 and four plugin projects.
 The feature project groups the four plugins together for easy installation.
@@ -130,16 +130,16 @@ <h2>Eclipse Workspace Setup</h2>
   </li>
 
   <li>Start Eclipse and make a new workspace</li>
-  <li><b>Important:</b> make sure that a version 8.0 or higher JDK is available and visible to Eclipse
+  <li><b>Important:</b> make sure that a version 21 or higher JDK is available and visible to Eclipse
      (Window&gt;Preferences&gt;Java&gt;Installed JREs).  A JDK is required - a JRE
-     alone will fail because of JavaDoc generation in the build and Tycho requires JDK 8.0 or above.</li>
+     alone will fail because of JavaDoc generation in the build and Tycho requires JDK 21 or above.</li>
   <li>Import the projects into the workspace
     <ol type="a">
       <li>Start the Eclipse project import wizard
         (File&gt;Import&gt;General&gt;Existing Projects into Workspace)
       </li>
       <li>Set the root directory to the "eclipse" sub-directory in your Git clone</li>
-      <li>Select all eleven projects, do not copy the projects into
+      <li>Select all nine projects, do not copy the projects into
         your workspace.
         The filled out wizard looks similar to this: <br />
         <p><img src="importWizard.png" alt="Eclipse Project Import Wizard"/></p>
@@ -149,7 +149,8 @@ <h2>Eclipse Workspace Setup</h2>
   </li>
   <li>The project includes Eclipse target platform definition files. The purpose is to set the minimum version
    of Eclipse supported by the feature and to ensure that you do not inadvertently use Eclipse features from later
-   versions. Target platform files are in the <code>releng</code> project. To activate
+   versions. The target platform files also provide access to dependencies needed during the build. 
+   Target platform files are in the <code>releng</code> project. To activate
    the target platform, open the proper target file and click on the link that says "Set as active target platform". This action
    may take a few minutes to complete. The README in the releng project contains information about which target platform file to use.
   </li>
@@ -252,9 +253,6 @@ <h2>Running the Unit Tests</h2>
       </ol>
   </li>
 </ul>
-<p>To run all tests, run the class <code>org.mybatis.generator.eclipse.core.tests.RunAllTests</code>
-which contains a test suite of all unit tests.
-</p>
 
 <h2>Building the Documentation</h2>
 <p>The documentation for MBG is integrated into the Eclipse help system.
@@ -282,7 +280,7 @@ <h2>Building the Feature for Local Distribution</h2>
 that points to this directory (Help&gt;Install New Software...) and install
 the new version with P2.</p>
 
-<p>If you are interested in publishing a new version to JFrog, please see the
+<p>If you are interested in publishing a new version to GitHub, please see the
 instructions on the <a href="publishing.html">Publishing</a> page.
 </body>
 </html>

eclipse/org.mybatis.generator.eclipse.doc/html-src/eclipseui/buildingFromSource.html

@@ -28,7 +28,7 @@
     qualifiedVersion  (standard Tycho property)
     project.build.directory (standard Maven property - points to the target directory)
     p2.repo.base.directory (the location of the composite repo.  This might have been initialized
-        by pulling a current copy from jfrog)
+        by pulling a current copy from GitHub)
     
 -->
 <project name="project" default="updateRepo">

eclipse/org.mybatis.generator.eclipse.doc/html-src/eclipseui/importWizard.png

@@ -236,7 +236,7 @@
    </license>
 
    <url>
-      <update label="MyBatis Generator Update Site" url="https://mybatis.jfrog.io/artifactory/generator-eclipse-release/"/>
+      <update label="MyBatis Generator Update Site" url="https://jeffgbutler.github.io/mybatis-generator-update-site/"/>
    </url>
 
    <plugin