Updated the home and download pages to indicate we no longer generate aggregated JAR files.
OSLC4J SDK users will usually use Maven instead.
Signed-off-by: Jim Amsden <jamsden@us.ibm.com>
diff --git a/download.html b/download.html
index cdf9c58..36db9f9 100644
--- a/download.html
+++ b/download.html
@@ -38,11 +38,17 @@
<div class="lyoDownloadSmallText">OSLC4J 2.1.1 SDK with Dependencies</div>
</a>
+ <p>
+ Note: Eclipse/Lyo no longer builds aggregated JAR files for each release. Rather Eclipse/Lyo has more fully embraced Maven in two new ways. First, all Eclipse/Lyo projects are now Maven (not eclipse) projects. In practice that means that the eclipse .classpath, .settings and .project files are no longer stored in the git repositories. Instead eclipse IDE users should load Eclipse/Lyo projects as Maven projects. This will automatically construct the eclipse .classpath, .settings and .projects files from the information in the pom.xml file. This ensures the eclipse build and the maven builds will be in sync, using the same environment and dependencies. It will also display the projects using their artifact ids in the eclipse project explorer. This will hopefully reduce confusion between different names for the same thing.
+ </p>
+ <p>Second, users of the OSLC4J SDK should use Maven to handle project dependencies. This makes it easier to manage the dependencies, and to build different projects with different versions of OSLC4J SDK in the same SDK. Users who do not wish to use Maven projects can download the JAR files from the <a href="https://mvnrepository.com/artifact/org.eclipse.lyo.oslc4j">MVN Repository</a>.
+ </p>
+
<p>
All downloads are provided under the terms and conditions of the <a
href="/legal/epl/notice.php">Eclipse Public License</a> and the <a
href="http://www.eclipse.org/org/documents/edl-v10.php">Eclipse
- Distribution License</a> unless otherwise specified.
+ Distribution License</a> unless otherwise specified. Newer versions of OSLC4J are now available at <a href="https://mvnrepository.com/artifact/org.eclipse.lyo.oslc4j">MVN Repository</a>.
</p>
<h3>OSLC4J 2.1.1 and Eclipse approved versions of prerequisite
diff --git a/index.html b/index.html
index 4cdc7e0..d0481e5 100644
--- a/index.html
+++ b/index.html
@@ -71,12 +71,12 @@
<pre><code class="language-xml"><dependency>
<groupId>org.eclipse.lyo.oslc4j.core</groupId>
<artifactId>oslc4j-core</artifactId>
- <version>2.1.2</version>
+ <version>2.2.0</version>
</dependency></code></pre>
<p>Learn more about OSLC4J on <a href="https://wiki.eclipse.org/Lyo/LyoOSLC4J">Eclipse Lyo Wiki</a> and in the <a
- href="https://download.eclipse.org/lyo/docs/core/2.1.2/overview-summary.html">Javadocs</a>. You might enjoy the
+ href="https://download.eclipse.org/lyo/docs/core/2.2.0/overview-summary.html">Javadocs</a>. You might enjoy the
<a href="https://open-services.net/resources/tutorials/integrating-products-with-oslc/">OSLC tutorial based on
Lyo</a>.</p>
</div>
@@ -91,13 +91,13 @@
<pre><code class="language-xml"><dependency>
<groupId>org.eclipse.lyo.clients</groupId>
<artifactId>oslc-java-client</artifactId>
- <version>2.1.2</version>
+ <version>2.2.0</version>
</dependency></code></pre>
<p>Learn more about Lyo Client on <a href="https://wiki.eclipse.org/Lyo/BuildClient">Eclipse Lyo Wiki</a> and in
the <a
- href="https://download.eclipse.org/lyo/docs/client/2.1.2/overview-summary.html">Javadocs</a>.</p>
+ href="https://download.eclipse.org/lyo/docs/client/2.2.0/overview-summary.html">Javadocs</a>.</p>
</div>
diff --git a/pages/_download.html b/pages/_download.html
index a1e3433..754c795 100644
--- a/pages/_download.html
+++ b/pages/_download.html
@@ -69,10 +69,16 @@
</a>
<p>
+ Note: Eclipse/Lyo no longer builds aggregated JAR files for each release. Rather Eclipse/Lyo has more fully embraced Maven in two new ways. First, all Eclipse/Lyo projects are now Maven (not eclipse) projects. In practice that means that the eclipse .classpath, .settings and .project files are no longer stored in the git repositories. Instead eclipse IDE users should load Eclipse/Lyo projects as Maven projects. This will automatically construct the eclipse .classpath, .settings and .projects files from the information in the pom.xml file. This ensures the eclipse build and the maven builds will be in sync, using the same environment and dependencies. It will also display the projects using their artifact ids in the eclipse project explorer. This will hopefully reduce confusion between different names for the same thing.
+ </p>
+ <p>Second, users of the OSLC4J SDK should use Maven to handle project dependencies. This makes it easier to manage the dependencies, and to build different projects with different versions of OSLC4J SDK in the same SDK. Users who do not wish to use Maven projects can download the JAR files from the <a href="https://mvnrepository.com/artifact/org.eclipse.lyo.oslc4j">MVN Repository</a>.
+ </p>
+
+ <p>
All downloads are provided under the terms and conditions of the <a
href="/legal/epl/notice.php">Eclipse Public License</a> and the <a
href="http://www.eclipse.org/org/documents/edl-v10.php">Eclipse
- Distribution License</a> unless otherwise specified.
+ Distribution License</a> unless otherwise specified. Newer versions of OSLC4J are now available at <a href="https://mvnrepository.com/artifact/org.eclipse.lyo.oslc4j">MVN Repository</a>.
</p>
<h3>OSLC4J 2.1 and Eclipse approved versions of prerequisite
