Hi On further investigation, this was caused by a long directory path in the set.default.REPO_DIR property. Providing I keep the './wrapper' pattern in the first 80 characters, I don't get the "Removed state pid file" error.
Hopefully someone can help with my second question though! I've been following the example here: http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/usage_jsw.html therefore I am expecting "All dependencies and the artifact itself are placed in target/appassembler/repo", however I am getting the scripts generated in target/generated-resources/appassembler/jsw/app1. My artifacts are being generated in target as expected. How can I link the scripts to the artifacts so that I can run the daemon without editing either the shell script or the wrapper.conf? target/generated-resources/appassembler target/generated-resources/appassembler/jsw target/generated-resources/appassembler/jsw/app1 target/generated-resources/appassembler/jsw/app1/lib target/generated-resources/appassembler/jsw/app1/lib/libwrapper-linux-x86-32.so target/generated-resources/appassembler/jsw/app1/lib/libwrapper-macosx-universal-32.jnilib target/generated-resources/appassembler/jsw/app1/lib/wrapper-windows-x86-32.dll target/generated-resources/appassembler/jsw/app1/lib/libwrapper-solaris-x86-32.so target/generated-resources/appassembler/jsw/app1/lib/wrapper.jar target/generated-resources/appassembler/jsw/app1/bin target/generated-resources/appassembler/jsw/app1/bin/app1.bat target/generated-resources/appassembler/jsw/app1/bin/wrapper-macosx-universal-32 target/generated-resources/appassembler/jsw/app1/bin/app1 target/generated-resources/appassembler/jsw/app1/bin/wrapper-solaris-x86-32 target/generated-resources/appassembler/jsw/app1/bin/wrapper-linux-x86-32 target/generated-resources/appassembler/jsw/app1/bin/wrapper-windows-x86-32.exe target/generated-resources/appassembler/jsw/app1/conf target/generated-resources/appassembler/jsw/app1/conf/wrapper.conf Here is an extract from my pom: <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>appassembler-maven-plugin</artifactId> <version>1.1-SNAPSHOT</version> <configuration> <repositoryLayout>flat</repositoryLayout> <includeConfigurationDirectoryInClasspath>true</includeConfigurationDirectoryInClasspath> <daemons> <daemon> <id>app1</id> <mainClass>com.specialprojectslab.Sleepy</mainClass> <commandLineArguments> <commandLineArgument>start</commandLineArgument> </commandLineArguments> <platforms> <platform>jsw</platform> </platforms> </daemon> </daemons> </configuration> <executions> <execution> <id>generate-jsw-scripts</id> <phase>package</phase> <goals> <goal>generate-daemons</goal> </goals> </execution> </executions> </plugin> </plugins> </build> I have tried 1.0 and 1.1-SNAPSHOT (compiled from svn tree). Regards Jasper * Jasper Humphrey ([email protected]) wrote: > Hi Appassembler team, > I've used appassember to generate jsw launchers on Solaris 10, but I get > a "Removed stale pid file" error due to the Solaris ps command not > showing the full argument list of the process. > > I can see Nexus had the same issue before with jsw: > https://issues.sonatype.org/browse/NEXUS-49 > > I have modified the generated script to use /usr/usb/ps temporarily. > Shall I submit a patch for appassembler? > > Regards > Jasper --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
