Below is a snapshot of the profile that we use with jetty. > mvn -PpackAndSite clean install The example below shows both styles of running pack200, the remote version takes quite a while to execute because the build.eclipse.org machine is rather slow and the pack200 default setting is based on an ibm jdk on that machine. Care should be taken to pack with the same version of java that your artifacts are planning on releasing with. To execute the sign on build.eclipse.org (which it has to be) you need to mail the webmaster@eclipse.org and have your username added as an executor of the /usr/bin/sign script. You should use a setting.xml somewhat like this: project.eclipse.website foo /home/bar/.ssh/priv ------------------------------------------------------------------------- packAndSign org.mortbay.jetty.toolchain eclipse-signing-maven-plugin 1.0-SNAPSHOT pack local /usr/lib/jvm/java-6-sun/bin package pack sign scpexe:// build.eclipse.org /home/data/httpd/download-staging.priv/rt/jetty jetty.eclipse.website ${project.build.directory}/packed/${project.artifactId}-${project.version}.zip package sign repack remote scpexe:// build.eclipse.org /home/data/users/jmcconnell jetty.eclipse.website ${project.build.directory}/signed/${project.artifactId}-${project.version}.zip package pack fixCheckSums ${project.build.directory}/packed/${project.artifactId}-${project.version}.zip ${project.build.directory}/fixed/${project.artifactId}-${project.version}.zip ${project.build.directory}/checksumFix/${project.artifactId}-${project.version}/site/artifacts.xml package fixCheckSums promoteSite scpexe:// build.eclipse.org /home/www/jetty/nightly jetty.eclipse.website ${project.build.directory}/fixed/${project.artifactId}-${project.version}.zip I${project.version} package promote