Technique to see "latest" libraries?

[Jack]

Hi,

Normally when you use savant you have an entry like:
<x:artifact id="liquidity-common.jar" group="Liquidity"
projectname="Common" name="liquidity-common" version="1.2.3"
type="jar" />

I would like to be able to always get the latest version of this jar
from the repository without needing to change my dependencies.xml
file.

I have tested creating a sym-link to the latest file BUT when the
underlying file is modified - I do not get the latest copy of the
file. (the sym-link looks like: liquidity-common-1.2.3.jar =>
liquidity-common-LATEST.jar

I have also tried copy'ing the file instead of using a sym-link.

Neither of these techniques will cause the local file to be uploaded
unless the local copy of the file is removed prior to the build.

Thanks,
-- Jack --

[Brian Pontarelli]

It looks like you are using Savant 1.0. If that is the case, there is
no way to grab the latest JAR from the repository. In Savant 1.5, you
can set the artifact to use the {latest} version and Savant will make
its best effort to determine what that is. Like this:

<artifact group="foo.com" name="bar" version="{latest}"/>

In most cases you really don't want the "latest" from the repository,
what you really want is a local integration build and a check that
prevents you from releasing until you remove the integration build.
Grabbing the "latest" can cause your build or runtime to break
unexpectedly. The worst situation is if you finally have everything
tested and working, someone releases a new build of a library you
depend on, you then perform your production build and grab this new
version. However, the whole time you had been testing against a
different version. This can introduce major bugs.

This is the primary reason that Savant has avoided these concepts to
date and why we aren't supporting the changes in JDK 7. In some cases,
JDK 7 might do this auto-upgrade at runtime. That's even worse.

With Savant 1.5, we provide integration builds to fix these issues.
This system lets you perform local builds across many projects and
grab the latest integration build in other projects. We also have a
Ant task that will verify you don't have integration builds in your
project.xml file prior to making a release. You should never release a
version of your project using an integration or latest build.

Here's the docs on integration builds:

http://code.google.com/p/savant-build/wiki/1_5IntegrationBuilds

Here's the Ant task to ensure you don't have integration or latest
builds:

http://code.google.com/p/savant-build/wiki/1_5AntCheckIntegrationBuildTask

We feel that integration builds are really the best way to build your
software and prevent any types of surprises.

-bp

[Jack]

Thank yo very much for the quick reply - much appreciated.

-- Jack --

>        http://code.google.com/p/savant-build/wiki/1_5AntCheckIntegrationBuil...

>
> We feel that integration builds are really the best way to build your  
> software and prevent any types of surprises.
>
> -bp
>
> On Oct 19, 2009, at 7:35 AM, Jack wrote:
>
>
>
>
>
> > Hi,
>
> > Normally when you use savant you have an entry like:
> >        <x:artifact id="liquidity-common.jar" group="Liquidity"
> > projectname="Common" name="liquidity-common" version="1.2.3"
> > type="jar" />
>
> > I would like to be able to always get the latest version of this jar
> > from the repository without needing to change my dependencies.xml
> > file.
>
> > I have tested creating a sym-link to the latest file BUT when the
> > underlying file is modified - I do not get the latest copy of the
> > file.  (the sym-link looks like: liquidity-common-1.2.3.jar =>
> > liquidity-common-LATEST.jar
>
> > I have also tried copy'ing the file instead of using a sym-link.
>
> > Neither of these techniques will cause the local file to be uploaded
> > unless the local copy of the file is removed prior to the build.
>
> > Thanks,

> >     -- Jack --- Hide quoted text -
>
> - Show quoted text -