We have a codebase that's going to be somewhat unstable for a while.
We want to publish "snapshots" but not the sort where Maven will
automatically bring in the latest version.
Date and timestamped snapshots were suggested. I've seen artifacts
named project-x.x-YYYYMMDD.n.jar, where I think n is a timestamp. Can
Maven 1 be told to do this?
Is this a matter of changing project.xml and building/deploying the
jar, or is there a special command/plugin that will datestamp the
jar automatically?
Thanks,

Just use the "artifact" deployment mechanism (ie, maven.repo.*, not
maven.repo.central).

A recent version of the artifact plugin (1.5.2 added to Maven 1.0.2,
or the version included with Maven 1.1 beta-2+) is highly recommended.

If your version includes SNAPSHT, it will be replaced with the
timestamp when you do "jar:deploy". Dependencies with that timestamp
will work, and dependencies with SNAPSHT will use the latest.

Hope this helps.

Cheers,
Brett

12/2/05, Wendy Smoak <wsmoak (AT) gmail (DOT) comwrote:
We have a codebase that's going to be somewhat unstable for a while.
We want to publish "snapshots" but not the sort where Maven will
automatically bring in the latest version.

Date and timestamped snapshots were suggested. I've seen artifacts
named project-x.x-YYYYMMDD.n.jar, where I think n is a timestamp. Can
Maven 1 be told to do this?

Is this a matter of changing project.xml and building/deploying the
.jar, or is there a special command/plugin that will datestamp the
jar automatically?

Thanks,

12/1/05, Brett Porter <brett.porter (AT) gmail (DOT) comwrote:

Just use the "artifact" deployment mechanism (ie, maven.repo.*, not
maven.repo.central).

A recent version of the artifact plugin (1.5.2 added to Maven 1.0.2,
or the version included with Maven 1.1 beta-2+) is highly recommended.

Is 1.5.2 known to work with Maven 1.0.2? The docs say that Maven 1.1
is required.

I tried both 1.5.1 and 1.5.2, and I always get the following exception
from jar:deploy :

Failed to deploy to: apache Reason:
Cannot
connect. Reason: Private key was not found. You must define a private
key or a password for repo: apache

I'm sure my key is fine, because I can ssh or scp to people.apache.org
with no password. I'll go triple-check that the path and filename of
the private key are correct in maven.repo.apache.privatekey.

Please let me know which version of the artifact plugin I should use
with Maven 1.0.2, and I'll check in my changes so one of the other
developers can try it. Maybe it's just me.

1.5.2 should work with maven 1.0.2, the documentation is not completely
accurate. I just did a successful jar:deploy using scp protocol and
private key. Did you specify the maven.repo.list=apache property and the
maven.repo.apache.privatekey as an absolute path?
-Lukas

Wendy Smoak wrote:
12/1/05, Brett Porter <brett.porter (AT) gmail (DOT) comwrote:


>>Just use the "artifact" deployment mechanism (ie, maven.repo.*, not
>>maven.repo.central).
>>
>>A recent version of the artifact plugin (1.5.2 added to Maven 1.0.2,
>>or the version included with Maven 1.1 beta-2+) is highly recommended.

Is 1.5.2 known to work with Maven 1.0.2? The docs say that Maven 1.1
is required.

I tried both 1.5.1 and 1.5.2, and I always get the following exception
from jar:deploy :

Failed to deploy to: apache Reason:
Cannot
connect. Reason: Private key was not found. You must define a private
key or a password for repo: apache

I'm sure my key is fine, because I can ssh or scp to people.apache.org
with no password. I'll go triple-check that the path and filename of
the private key are correct in maven.repo.apache.privatekey.

Please let me know which version of the artifact plugin I should use
with Maven 1.0.2, and I'll check in my changes so one of the other
developers can try it. Maybe it's just me.

12/2/05, Lukas Theussl <theussl (AT) triumf (DOT) cawrote:
1.5.2 should work with maven 1.0.2, the documentation is not completely
accurate. I just did a successful jar:deploy using scp protocol and
private key. Did you specify the maven.repo.list=apache property and the
maven.repo.apache.privatekey as an absolute path?

Yes and yes, but it doesn't like something about the path to id_dsa.
I copied it into the project, used
and then it worked. (Maybe the
dot in the path, which included /wsmoak/.ssh/id_dsa, was a problem.)

Should the filename for the .jar and the .pom match? I suppose it
won't matter for Maven 1, but this is what got uploaded:

jar:deploy:
Uploading to
Uploading to

Thanks,