Hi Karl, thanks for your reply. I have to apologize, I was overtired when writing the mail. Indeed, it was my own fault - I had the wrong pom opened in an editor and the one actally used had a wrong lifecycle phase binding for the plugin (prepare-package) which caused the misbehaviour. I guess appassembler tried to copy the projects resulting jar to the appassemble folder and it was not yet available.
Sorry again, next time I'll take a natch of sleep beforehand. Everything works fine, great plugin. And - yeah, I'm using it to create scripts not executables :-) Best, Matthes 2012/10/10 Karl Heinz Marbaise <khmarba...@gmx.de> > Hi, > > > > I am using the appassembler plugin to create executables for my > >> application. >> > > To make things clear the appassembler-maven-plugin is intended to create > scripts (bash/bat) to start an application and not for making > executables... > > > <plugin> >> <groupId>org.codehaus.mojo</**groupId> >> <artifactId>appassembler-**maven-plugin</artifactId> >> <version>1.3</version> >> <configuration> >> <programs> >> <program> >> <mainClass>my.app.MyApp</**mainClass> >> <name>MyApp</name> >> </program> >> </programs> >> </configuration> >> </plugin> >> > > This isn't the full pom, cause the error output which is attached to the > mail is expression something different... > > Can you post the complete pom may be put the pom on pastebin or may be on > github project to see the project and how the whole pom looks like... > > > target/classes as an artifact to the repository (see full log attached). >> > Apart from that it is not a full log output... > > Kind regards > Karl-Heinz Marbaise > -- > SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 > Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029 > Hauptstrasse 177 USt.IdNr: DE191347579 > 52146 Würselen http://www.soebes.de >
