Well, you can get the hash files created to if you upload using the
new deploy:deploy-file goal:
mvn deploy:deploy-file -DgroupId=GROUP_ID -DartifactId=ARTIFACT_ID
-Dversion=VERSION_ID -DgeneratePom=true \
-Dpackaging=jar \
-Dfile=PATH/TO/JAR \
-DrepositoryId=YOUR_COMPANYS_REPO_ID \
-Durl=scp://YOUR_COMPANYS_REPO_IP/PATH/TO/REPO
Where YOUR_COMPANYS_REPO_ID matches a server in settings.xml
<server>
<id>YOUR_COMPANYS_REPO_ID</id>
<username>YOUR_USERNAME</username>
<privateKey>/PATH/TO/PRIVATEKEY</privateKey>
</server>
However, I'm not sure if that is enough for snapshots...
-Stephen
On 1/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> What's the minimum that will keep m2 happy when retrieving a snapshot
> from a remote repository?
>
> I've got a project that I just can't build with m2, but I need to make
> a snapshot available.
>
> If I upload (in the correct directory structure):
> shale-core-1.0.1-SNAPSHOT.jar
> shale-core-1.0.1-SNAPSHOT.pom
> ... and can I get away with just one of the signatures (which one is
> preferable)?
>
> Anything else? How will it know when the snapshot has been updated?
>
> Thanks,
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Stephen Duncan Jr
www.stephenduncanjr.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
