Hi to all,
I'm proudly announce the availability of the version 1.2.1 of the
appassembler-maven-plugin which is mostly a bug fix release.
The Application Assembler Plugin is a Maven plugin for generating
scripts for starting java applications. All dependencies and the
artifact of the project itself are placed in a generated Maven
repository in a defined assemble directory. All artifacts (dependencies
+ the artifact from the project) are added to the classpath in the
generated bin scripts.
Project URL:
http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/index.html
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11780&version=18320
The appassembler-maven-plugin is available under the following
coordinates via Maven-Central:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>appassembler-maven-plugin</artifactId>
<version>1.2.1</version>
</plugin>
Bug
[MAPPASM-95] - jvmSettings and daemons parameters
to generate:daemons are not documented in the
goals section of site.
[MAPPASM-100] - Windows Batch file doesn't propagate
exit code properly
[MAPPASM-107] - No doc on the inside of <daemons/>
[MAPPASM-118] - system dependency on tools.jar not accounted for
[MAPPASM-147] - Unix shell script fails as softlink
[MAPPASM-149] - Chicken-egg problem with 'mvn test'
[MAPPASM-150] - Created JSW (wrapper.conf) contains wrong
location for the generated repository.
[MAPPASM-151] - Write shell script error echo to stderr
Improvement
[MAPPASM-145] - Wrong order of artifacts in generated classpath
[MAPPASM-148] - Property 'basedir' misleading
New Feature
[MAPPASM-98] - need dependencies in system scope
[MAPPASM-155] - JSW - need to be able to configure
wrapper log directory
Task
[MAPPASM-143] - Why does the unit test fail with a new release?
The Mojo-Team
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
