[ANN] Maven Fluido Skin 1.8 released
The Apache Maven team is pleased to announce the release of the Maven Fluido Skin, version 1.8. https://maven.apache.org/skins/maven-fluido-skin/ You should specify the version in your project's site configuration: org.apache.maven.skins maven-fluido-skin 1.8 Release Notes - Maven Fluido Skin - Version 1.8 ** Sub-task * [MSKINS-104] - Remove obsolete meta tags * [MSKINS-106] - Replace unregistered meta tags with standard ones ** Bug * [MSKINS-143] - Allow setting GA options for forceSSL and anonymizeIP * [MSKINS-144] - Maven web site include ancient and non-functional Apache address ** Improvement * [MSKINS-129] - Update Google Analytics to new analytics.js * [MSKINS-137] - Enable "Hamburger menu" with top-nav only * [MSKINS-142] - indent html for sub-menus * [MSKINS-145] - Google+ Shutdown - remove code from skins * [MSKINS-153] - Use XHTML5 tags in site.vm ** Task * [MSKINS-107] - Add "generator" meta tag in HTML head * [MSKINS-148] - Drop redundant "All rights reserved" * [MSKINS-149] - Align common Velocity structures with Default Skin ** Dependency upgrade * [MSKINS-155] - Upgrade Maven Site Plugin to 3.8.2 * [MSKINS-156] - Upgrade Maven Doxia Sitetools to 1.9.1 in skin descriptor Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 3.8.2 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 3.8.2. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 3.8.2 ** Bug * [MSITE-823] - Documentation says JDK 1.6 required, doxia dependency requires 1.7 * [MSITE-842] - $currentFileName and $alignedFileName are incorrect for Maven Report plugins that use several Sink instances ** Improvement * [MSITE-824] - Generate (X)HTML5 by default * [MSITE-830] - Dependency upgrades related to identified security reports * [MSITE-836] - when a report mojo fails with a RuntimeException, let m-site-p plugin tell which report is failing * [MSITE-838] - Include support for confluence/docbook/twiki by default ** Dependency upgrade * [MSITE-758] - upgrade wagon-api from 1.0 to 3.3.1 * [MSITE-839] - Upgrade to Maven Doxia (Sitetools) 1.9 * [MSITE-841] - Upgrade to Maven Doxia Sitetools 1.9.1 * [MSITE-843] - Update Jetty to 9.2.28 * [MSITE-844] - Update requirement to Java 7 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Default Skin 1.3 released
The Apache Maven team is pleased to announce the release of the Maven Default Skin, version 1.3. https://maven.apache.org/skins/maven-default-skin/ You should specify the version in your project's site configuration: org.apache.maven.skins maven-default-skin 1.3 Release Notes - Maven Default Skin - Version 1.3 ** Task * [MSKINS-136] - switch to Git ** Dependency upgrade * [MSKINS-151] - Upgrade Parent to 33 * [MSKINS-152] - Upgrade Maven Doxia Sitetools to 1.9.1 in skin descriptor * [MSKINS-154] - Upgrade Maven Site Plugin to 3.8.2 for ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using Git tags to cut releases to Maven Central from TravisCI
I've been experimenting with setting up Maven Central publishing from a
TravisCI build (since it's free for my OSS GitHub project), and I ended up
with a pattern that I think is pretty nice to work with (I've struggled
with the maven-deploy-plugin in the past).
I've written it up here
https://bpodgursky.com/2019/07/31/using-travisci-to-deploy-to-maven-central-via-git-tagging-aka-death-to-commit-clutter/
but
tl,dr, the key thing I haven't seen used widely is the use of tags to
define release versions, eg:
```
if [ ! -z "$TRAVIS_TAG" ]
then
mvn --settings "${TRAVIS_BUILD_DIR}/.travis/mvn-settings.xml"
org.codehaus.mojo:versions-maven-plugin:2.1:set -DnewVersion=$TRAVIS_TAG
1>/dev/null 2>/dev/null
else
echo "No tags, using snapshot version from pom.xml"
fi
mvn deploy -P publish -DskipTests=true --settings
"${TRAVIS_BUILD_DIR}/.travis/mvn-settings.xml"
```
This lets me cut a central release by just pushing a tag:
```
$ git tag 1.23
$ git push origin 1.23
```
I've used Maven a fair amount but I wouldn't consider myself perfectly in
tune with best practices, so I'm curious what others think of this
approach, or if there are other streamlined central deploy setups
(especially from CI/Travis) that I missed.
Thanks,
Ben
