{"id":1045,"date":"2010-07-16T20:58:11-04:00","date_gmt":"2010-07-17T00:58:11+00:00","guid":{"rendered":"http:\/\/peterjanes.ca\/blog\/?p=1045"},"modified":"2010-07-27T08:16:19-04:00","modified_gmt":"2010-07-27T12:16:19+00:00","slug":"a-pattern-for-webstart-in-maven","status":"publish","type":"post","link":"https:\/\/peterjanes.ca\/blog\/2010\/07\/16\/a-pattern-for-webstart-in-maven\/","title":{"rendered":"A pattern for WebStart in Maven"},"content":{"rendered":"

Java WebStart<\/a> and JNLP<\/a> can be finicky beasts, especially when paired with Maven-generated websites and artifact repositories. Over the last few months I’ve developed POM and JNLP template patterns that I think are useful when used with the webstart-maven-plugin:jnlp<\/a> goal; the main advantage is that applications can be WebStarted directly from the repository, which means that the version available is always the latest -SNAPSHOT<\/code> or release.<\/p>\r\n\r\n

In the POM I define two variables, site.baseUrl<\/code> and artifactUrl<\/code>. site.baseUrl<\/code> defines the server and root path where all Maven-generated websites are published; it has a prefix because usually I’d only set it once in the corporate POM. artifactUrl<\/code> is the full URL of the project-specific website.<\/p>\r\n\r\n

By default both site.baseUrl<\/code> and artifactUrl<\/code> point to the location where -SNAPSHOT<\/code> sites are published, usually by a CI<\/abbr> system. They’re overridden in two profiles: release<\/code> switches site.baseUrl<\/code> to the release website (which is applied to artifactUrl<\/code>, so there’s no need to set it again), and devel<\/code> sets artifactUrl<\/code> to the local target directory (and omits site.baseUrl<\/code>, which ends up unused).<\/p>\r\n\r\n

<project><\/code>\r\n...\r\n  <properties>\r\n    <site.baseUrl>http:\/\/repository\/snapshot-site\/<\/site.baseUrl>\r\n    <artifactUrl>${site.baseUrl}\/${project.artifactId}<\/artifactUrl>\r\n  <\/properties><\/code>\r\n...\r\n  <profiles>\r\n    <profile>\r\n      <id>release<\/id>\r\n      <properties>\r\n        <site.baseUrl>http:\/\/repository\/release-site\/<\/site.baseUrl>\r\n      <\/properties>\r\n      <distributionManagement>\r\n        <site>\r\n          <id>release-site<\/id>\r\n          <url>dav:${artifactUrl}<\/url>\r\n        <\/site>\r\n      <\/distributionManagement>\r\n    <\/profile>\r\n    <profile>\r\n      <id>devel<\/id>\r\n      <properties>\r\n        <artifactUrl>file:\/\/${project.build.directory}<\/artifactUrl>\r\n      <\/properties>\r\n    <\/profile>\r\n  <\/profiles><\/code>\r\n...\r\n<\/project><\/code><\/pre>\r\n\r\n
In the JNLP template, the codebase<\/code> is set to artifactUrl<\/code>, which means that the resulting JNLP will retrieve any artifact dependencies from the snapshot, release or local output directories.<\/p>\r\n\r\n
<jnlp\r\n  spec=\"$jnlpspec\"\r\n  codebase=\"${artifactUrl}\/jnlp\/\"\r\n  version=\"$project.Version\"\r\n><\/code>\r\n...\r\n<\/jnlp><\/code><\/pre>\r\n\r\n
Note that the artifact dependencies still need to be copied into the jnlp<\/code> directory, which webstart-maven-plugin:jnlp<\/code> does by default.  It would be nice to be able to get them from their canonical locations on the repository, but that’s not easily accomplished.<\/p><\/div>
<\/div>","protected":false},"excerpt":{"rendered":"Java WebStart and JNLP can be finicky beasts, especially when paired with Maven-generated websites and artifact repositories. Over the last few months I’ve developed POM and JNLP template patterns that I think are useful when used with the webstart-maven-plugin:jnlp goal; the main advantage is that applications can be WebStarted directly from the repository, which means…","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"mf2_syndication":[],"venue_id":0},"categories":[1],"tags":[],"kind":false,"_links":{"self":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts\/1045"}],"collection":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/comments?post=1045"}],"version-history":[{"count":7,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts\/1045\/revisions"}],"predecessor-version":[{"id":1052,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts\/1045\/revisions\/1052"}],"wp:attachment":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/media?parent=1045"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/categories?post=1045"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/tags?post=1045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}