[
http://jira.codehaus.org/browse/MOJO-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102042
]
Trygve Laugstol commented on MOJO-848:
--------------------------------------
Bind the appassembler to generate-resources and bind the assembler to something
before package. Put those two plugins in a profile and make the release plugin
include that profile when releasing. Make sure that the release plugin runs
with the profile enabled, using something like the arugments configuration on
the perform mojo (though I was sure there was a special configuration element
to select which profiles to use).
As for putting stuff on a network drive, I'd still point people to the Maven
repository. But if you really have to use some antrun magic to copy stuff
around.
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments
This example is a bit dated now, haven't touched the code in a while:
{code}
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>appassembler-maven-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>assemble</goal>
</goals>
</execution>
</executions>
<configuration>
<programs>
<program>
<name>dpserver</name>
<mainClass>no.java.dp.server.cli.DpServerCli</mainClass>
</program>
<program>
<name>installer</name>
<mainClass>no.java.dp.server.installer.InstallerCli</mainClass>
</program>
</programs>
</configuration>
</plugin>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.1</version>
<executions>
<execution>
<!--<phase>package</phase>-->
<goals>
<goal>directory-inline</goal>
<goal>attached</goal>
</goals>
</execution>
</executions>
<configuration>
<descriptors>
<descriptor>src/main/assembly/standalone.xml</descriptor>
</descriptors>
<tarLongFileMode>gnu</tarLongFileMode>
</configuration>
</plugin>
</plugins>
{code}
> Provide options to zip & copy assembled application
> ---------------------------------------------------
>
> Key: MOJO-848
> URL: http://jira.codehaus.org/browse/MOJO-848
> Project: Mojo
> Issue Type: New Feature
> Components: appassembler
> Reporter: David Hoffer
> Assignee: Trygve Laugstol
>
> The appassembler works great for assembling an application that can be
> launched with a batch/shell script but I can't distribute this as it is.
> What I need is for the results to be included in a zip file named with the
> proper name/version.
> I also need a mechanism to copy this zip file to a common location where
> applications are stored. This later step could be performed by this plugin
> or another which ever is the best approach. The end result of this is to be
> able to automate the release of an application using the appassembler plugin.
> In summary, what I want to be able to do to release my application is:
> mvn release:prepare release:perform package appassembler:assemble (or equiv.)
> where this results in the application being zipped and placed in specified
> network folder.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
