[Building Sakai] New version of JSMPP

[Anthony Whyte]

Done.  The 2.0 jar was missing its associated jar.sha1, pom, pom.md5,  
pom.sha1 and the related maven-metadata.xml files would not update  
cleanly so I pulled the 2.0 jar down, deleted /jsmpp and redeployed  
both the 2.0 and 2.1b_01 jars.  The jsmpp portion of the maven2 repo  
looks good now.

https://source.sakaiproject.org/maven2/com/google/code/jsmpp/

For those interested in the magic of Maven when deploying 3rd party  
jars to a remote repository I include the commands I used below  
(minus required user/password settings embedded in my settings.xml).

mvn deploy:deploy-file -DgroupId=com.google.code \
   -DartifactId=jsmpp \
   -Dversion=2.0 \
   -Dpackaging=jar \
   -Dfile=./jsmpp-2.0.jar \
   -DrepositoryId=sakai-maven2 \
   -Durl=dav:https://source.sakaiproject.org/maven2

mvn deploy:deploy-file -DgroupId=com.google.code \
   -DartifactId=jsmpp \
   -Dversion=2.1b_01 \
   -Dpackaging=jar \
   -Dfile=./jsmpp-2.1b_01.jar \
   -DrepositoryId=sakai-maven2 \
   -Durl=dav:https://source.sakaiproject.org/maven2

Let me know if you can retrieve the jars.

Cheers,

Anth

On Jun 1, 2009, at 8:49 AM, Louis Botha wrote:

> Anthony,
>
> can you please also add the following jar to the sakai repo. Do not  
> replace the current JSMPP one. This is a build from the jsmpp trunk  
> to resolve SMS-59.
>
> The repo path will be :
>
> http://source.sakaiproject.org/maven2/com/google/code/jsmpp/2.1b_01/ 
> jsmpp-2.1b_01.pom
>
>
> thanks
>
> Louis
>
> <jsmpp-2.1b_01.jar>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2417 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090601/8a004ed0/attachment.bin