I'm assuming you have the source, and want to build and deploy it (opposed to having a binary and wanting do to a deploy-file).
There should be a maven plugin that defines the atlassian-plugin packaging. This plugin would define a mapping from atlassian-plugin to a lifecycle (which defines which plugins are run) and an artifact type (which says that the extension is .jar). In order for these mappings to be picked up, you need to specify <extensions>true</extensions> on that maven plugin. If that doesn't work, try sending us some more info than 'it doesn't work'. Some output (with -X), a pom, ... Tom On Dec 23, 2007 3:34 PM, Dan Hardiker <[EMAIL PROTECTED]> wrote: > Hi, > > I have some artifacts which have <packaging>jar</packaging> and some > which have <packaging>atlassian-plugin</packaging>, and I want to use > "mvn deploy" to put them into my subversion-backed repository (I am > using wagon-svn). The jar goes in fine, but the atlassian-plugin doesn't. > > To save questions, the atlassian-plugin packaging simply lays out the > jar slightly differently (requiring an atlassian-plugin.xml, and adding > in bundled dependencies into META-INF/lib or extracting them in an > uber-jar fashion depending on settings). > > I've checked out the wagon source and greped it for both "jar" and > "packaging", neither of which got me far at all. I'm not even sure where > this behaviour is defined and google is being uncharacteristically > unhelpful. > > Any idea where I should be looking to configure the atlassian-plugin > packaging to react the same in wagon as jar packaging? > > > -- > Dan Hardiker > Adaptavist.com Ltd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
