Merge pull request #1444 from jeffgbutler/eclipse-build-improvements

Eclipse build improvements

Author: jeffgbutler

eclipse/.mvn/extensions.xml

@@ -20,7 +20,7 @@
   <extension>
     <groupId>org.eclipse.tycho</groupId>
     <artifactId>tycho-build</artifactId>
-    <version>5.0.2</version>
+    <version>${tycho-version}</version>
   </extension>
   <extension>
     <groupId>fr.jcgay.maven</groupId>

eclipse/.mvn/maven.config

@@ -1,3 +1,5 @@
 -Daether.checksums.algorithms=SHA-512,SHA-256,SHA-1,MD5
 -Daether.connector.smartChecksums=false
 --no-transfer-progress
+-Dtycho-version=5.0.2
+

eclipse/org.mybatis.generator.core/build.properties

@@ -24,5 +24,3 @@ bin.includes = META-INF/,\
                NOTICE
 src.includes = LICENSE,\
                NOTICE\
-
-customBuildCallbacks=customBuildCallbacks.xml

eclipse/org.mybatis.generator.core/customBuildCallbacks.xml

@@ -151,7 +151,7 @@ <h2>Eclipse Workspace Setup</h2>
     <code>org.mybatis.generator.core</code> project.  There are two ways to solve this:
       <ol type="a">
         <li>If you are comfortable with Maven, then you can run the Maven build by
-          executing "./mvnw clean integration-test" on the <code>pom.xml</code> in the
+          executing "./mvnw clean verify" on the <code>pom.xml</code> in the
           parent directory of all Eclipse projects (../eclipse)
           A slight warning: this will download many 
           dependent JARs from Maven central and eclipse.org the first time you run it.
@@ -255,7 +255,7 @@ <h2>Building the Feature for Local Distribution</h2>
 <p>If you want to build an updated version of the feature and distribute it locally, then
 follow these steps:</p>
 <ol>
-  <li>Run the Maven build by running "./mvnw clean integration-test" in the parent directory of
+  <li>Run the Maven build by running "./mvnw clean verify" in the parent directory of
       all projects (".../eclipse")</li>
   <li>Once the build completes the feature will be available in the <code>target/repository</code>
   directory of the <code>org.mybatis.generator.eclipse.site</code> project.</li>

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

@@ -36,12 +36,18 @@ <h1>Publishing a New Version</h1>
   <li>Follow the instructions in <a href="buildingFromSource.html">Building from Source</a> to
       checkout the source and setup the projects in Eclipse.  You can use the steps
       on that page to debug any changes and ensure that the build works properly.</li>
-   <li>Once you are ready to publish, run "<code>./mvnw -Prelease-composite clean integration-test</code>"
+   <li>Once you are ready to publish, run "<code>./mvnw clean verify -Prelease-composite</code>"
        on the <code>pom.xml</code> in the parent directory of all eclipse projects ("../eclipse"). This turns on
        the "release-composite"
        profile which adds build steps to retrieve the current P2 metadata from GitHub and prepare
        the release artifacts for uploading.
    </li>
+   <li>The "release-composite" profile also includes artifact signing with GPG
+	   so make sure you have your key setup and know your password.
+       If you are running the release on a Mac or Linux, you might get an error during the signing phase
+	   related to "Inappropriate ioctl for device".
+	   You can usually resolve this by entering <code>export GPG_TTY=$(tty)</code> in your terminal.
+   </li>
    <li>After the build runs, you should see a new subdirectory "<code>target/p2-composite-repo</code>" in the
        <code>org.mybatis.generator.eclipse.site</code> project.  That directory will contain all
        the updated artifacts for uploading to GitHub.