You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Wendy Smoak <ws...@gmail.com> on 2005/12/02 06:01:01 UTC

[m1] Publishing identifiable/reproducible snapshots

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,
--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m1] Publishing identifiable/reproducible snapshots

Posted by Lukas Theussl <lt...@apache.org>.

> 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:

I fixed this one just yesterday 
(http://jira.codehaus.org/browse/MPARTIFACT-56), but it will be in 
artifact-plugin-1.7 only, which means you won't profit from it in m1.0.2...

-Lukas



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m1] Publishing identifiable/reproducible snapshots

Posted by Wendy Smoak <ws...@gmail.com>.
On 12/2/05, Lukas Theussl <th...@triumf.ca> wrote:
> 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 
-Dmaven.repo.apache.privatekey=id_dsa 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 tiles/poms/tiles-core-0.2-20051203.055537.pom:
Uploading to tiles/jars/tiles-core-0.2-20051203.055551.jar:

Thanks,
--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m1] Publishing identifiable/reproducible snapshots

Posted by Lukas Theussl <th...@triumf.ca>.
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:
> On 12/1/05, Brett Porter <br...@gmail.com> wrote:
> 
> 
>>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.
>    http://maven.apache.org/maven-1.x/reference/plugins/artifact/
> 
> 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:
> org.apache.maven.wagon.authentication.AuthenticationException: 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.
> 
> --
> Wendy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 

-- 
______________________________________________________________________________

Lukas Theussl
TRIUMF                                  email: theussl@triumf.ca
4004 Wesbrook Mall                      tel.: + 1 604 222 1047 ext. 6446
Vancouver, British Columbia             http://www.triumf.ca/people/theussl/
Canada V6T 2A3
______________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m1] Publishing identifiable/reproducible snapshots

Posted by Wendy Smoak <ws...@gmail.com>.
On 12/1/05, Brett Porter <br...@gmail.com> wrote:

> 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.
   http://maven.apache.org/maven-1.x/reference/plugins/artifact/

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:
org.apache.maven.wagon.authentication.AuthenticationException: 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.

--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m1] Publishing identifiable/reproducible snapshots

Posted by Brett Porter <br...@gmail.com>.
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 SNAPSHOT, it will be replaced with the
timestamp when you do "jar:deploy". Dependencies with that timestamp
will work, and dependencies with SNAPSHOT will use the latest.

Hope this helps.

Cheers,
Brett

On 12/2/05, Wendy Smoak <ws...@gmail.com> wrote:
> 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,
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org