Rather than deal with releases at regular intervals a more
Maven-oriented approach will be taken from now on. This means that bug
fixes and significant changes will be pushed out immediately - though
planned changes will still be reported in advance, particularly when the
changes affect the API and so might break existing code.
If you are using Maven:
All new snapshot releases will be deployed to the Sonatype public
repository: https://oss.sonatype.org/content/groups/public/
Add the following entry to your POM
<dependencies>
....
<dependency>
<groupId>com.flagstone</groupId>
<artifactId>transform</artifactId>
<version>3.0-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
</dependencies>
Add the Sonatype public repository to your settings.xml:
<profiles>
...
<profile>
<repositories>
<repository>
<id>FlagstoneSnapshots</id>
<name>Flagstone Software Snapshots</name>
<releases>
<enabled>false</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
<url>https://oss.sonatype.org/content/groups/public</url>
<layout>default</layout>
</repository>
</repositories>
</profile>
</profiles>
If you are not using Maven, you can still download the latest snapshot
from the Flagstone web site:
http://www.flagstonesoftware.com/downloads/index.html
The snapshot files are not timestamped, e.g.
transform-3.0-SNAPSHOT-dist.tar.gz rather than
transform-3.0-20100703.133854-2-dist.tar.gz. This should make it simple
to drop in new releases though at the risk of getting snapshots mixed up
if there is a breaking change.
Regards,
Stuart
--
Flagstone Software Ltd.
|
