From 2ea43967dc6ec74f2af1439f191f40e2650dd7ea Mon Sep 17 00:00:00 2001
From: Curtis Rueden <ctrueden@wisc.edu>
Date: Mon, 31 Mar 2014 16:10:47 -0500
Subject: [PATCH 1/2] POM: add developer profiles for SNAPSHOT pinning

These handy profiles automatically update all version properties for
a given set of projects to SNAPSHOT versions rather than releases.

This makes it easier to develop multiple projects against one another,
although you must still be careful not to push changes to master which
rely on the SNAPSHOT coupling (otherwise the Jenkins build will fail).
---
 pom.xml | 69 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 69 insertions(+)

diff --git a/pom.xml b/pom.xml
index 3fa13b6d..77f260cd 100644
--- a/pom.xml
+++ b/pom.xml
@@ -906,6 +906,75 @@ Projects wishing to use pom-scijava as a parent project need to override the &lt
 	</prerequisites>
 
 	<profiles>
+		<!-- These developer profiles make it easy to pin to SNAPSHOT versions.
+		     Add an empty dev.<organization> file to the relevant component,
+		     or globally in your ~/.scijava directory, and dependencies will
+		     automatically update! You may also need to refresh your IDE;
+		     e.g., in Eclipse: right click, Maven > Update Project... -->
+		<profile>
+			<id>dev.imagej</id>
+			<activation>
+				<file>
+					<exists>${user.dir}/.scijava/dev.imagej</exists>
+				</file>
+			</activation>
+			<properties>
+				<imagej.version>2.0.0-SNAPSHOT</imagej.version>
+				<ij1-patcher.version>0.3.2-SNAPSHOT</ij1-patcher.version>
+				<imagej-launcher.version>2.0.4-SNAPSHOT</imagej-launcher.version>
+				<minimaven.version>1.0.3-SNAPSHOT</minimaven.version>
+			</properties>
+		</profile>
+		<profile>
+			<id>dev.imglib2</id>
+			<activation>
+				<file>
+					<exists>${user.dir}/.scijava/dev.imglib2</exists>
+				</file>
+			</activation>
+			<properties>
+				<imglib2.version>2.0.0-SNAPSHOT</imglib2.version>
+				<imglib2-ij.version>2.0.0-SNAPSHOT</imglib2-ij.version>
+				<imglib2-scripting.version>2.0.0-SNAPSHOT</imglib2-scripting.version>
+			</properties>
+		</profile>
+		<profile>
+			<id>dev.ome</id>
+			<activation>
+				<file>
+					<exists>${user.dir}/.scijava/dev.ome</exists>
+				</file>
+			</activation>
+			<properties>
+				<bio-formats.version>5.0.2-SNAPSHOT</bio-formats.version>
+			</properties>
+		</profile>
+		<profile>
+			<id>dev.scijava</id>
+			<activation>
+				<file>
+					<exists>${user.dir}/.scijava/dev.scijava</exists>
+				</file>
+			</activation>
+			<properties>
+				<scijava-common.version>2.14.1-SNAPSHOT</scijava-common.version>
+			</properties>
+		</profile>
+		<profile>
+			<id>dev.scifio</id>
+			<activation>
+				<file>
+					<exists>${user.dir}/.scijava/dev.scifio</exists>
+				</file>
+			</activation>
+			<properties>
+				<scifio-ome-xml.version>0.7.1-SNAPSHOT</scifio-ome-xml.version>
+				<scifio.version>0.10.3-SNAPSHOT</scifio.version>
+				<scifio-bf-compat.version>1.6.2-SNAPSHOT</scifio-bf-compat.version>
+				<scifio-lifesci.version>0.4.1-SNAPSHOT</scifio-lifesci.version>
+			</properties>
+		</profile>
+
 		<!-- Build test artifact when tests are present. -->
 		<profile>
 			<id>test-jar</id>

From 18be2a9bd94fbc32f7e9d75833d5cc16ece643ed Mon Sep 17 00:00:00 2001
From: Mark Hiner <hinerm@gmail.com>
Date: Wed, 16 Apr 2014 14:35:11 -0500
Subject: [PATCH 2/2] pom.xml: add new property anchors

As there are now property tags in the profiles section, there is not a
good anchor point to restrict the search and replace range for scripts
like bump-pom-scijava.

This adds a unique comment at the start and end of the primary
properties section to distinguish it from profile properties.
---
 pom.xml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pom.xml b/pom.xml
index 77f260cd..5c9e5595 100644
--- a/pom.xml
+++ b/pom.xml
@@ -51,6 +51,7 @@ Projects wishing to use pom-scijava as a parent project need to override the &lt
 		</developer>
 	</developers>
 
+	<!-- LIVE PROPERTIES START -->
 	<properties>
 		<!-- If two artifacts on the classpath use two different versions of the
 		     same dependency, behavior is inconsistent at best, and often broken.
@@ -128,6 +129,7 @@ Projects wishing to use pom-scijava as a parent project need to override the &lt
 		<!-- NB: Override argLine property for extra maven-surefire-plugin args. -->
 		<argLine />
 	</properties>
+	<!-- LIVE PROPERTIES END -->
 
 	<dependencyManagement>
 		<dependencies>