I've run it on my Win7 machine and I think I have th same failing issue as 
Bamboo: [INFO]   The post-build script did not succeed. The expected content in 
D:\java-workspace\codehaus-mojo\appassembler\appassembler-maven-plugin\target\it\programJvmArgumentsTest\target\appassembler\bin\program-03-test
 couldn't be found.EXTRA_JVM_ARGUMENTS="-Xms20m -Xmx256m -Xss128m -Dtest=false 
-Dlog4j.properties=false -Danton=2345 -Dberta="xaz"" And here's my 
program-03-test (and the line above is indeed not there) #!/bin/sh
# ----------------------------------------------------------------------------
#  Copyright 2001-2006 The Apache Software Foundation.
#
#  Licensed under the Apache License, Version 2.0 (the "License");
#  you may not use this file except in compliance with the License.
#  You may obtain a copy of the License at
#
#       http://www.apache.org/licenses/LICENSE-2.0
#
#  Unless required by applicable law or agreed to in writing, software
#  distributed under the License is distributed on an "AS IS" BASIS,
#  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#  See the License for the specific language governing permissions and
#  limitations under the License.
# ----------------------------------------------------------------------------
#
#   Copyright (c) 2001-2006 The Apache Software Foundation.  All rights
#   reserved.BASEDIR=`dirname $0`/..
BASEDIR=`(cd "$BASEDIR"; pwd)` # OS specific support.  $var _must_ be set to 
either true or false.
cygwin=false;
darwin=false;
case "`uname`" in
  CYGWIN*) cygwin=true ;;
  Darwin*) darwin=true
           if [ -z "$JAVA_VERSION" ] ; then
             JAVA_VERSION="CurrentJDK"
           else
             echo "Using Java version: $JAVA_VERSION"
           fi
           if [ -z "$JAVA_HOME" ] ; then
             
JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/${JAVA_VERSION}/Home
           fi
           ;;
esacif [ -z "$JAVA_HOME" ] ; then
  if [ -r /etc/gentoo-release ] ; then
    JAVA_HOME=`java-config --jre-home`
  fi
fi# For Cygwin, ensure paths are in UNIX format before anything is touched
if $cygwin ; then
  [ -n "$JAVA_HOME" ] && JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
  [ -n "$CLASSPATH" ] && CLASSPATH=`cygpath --path --unix "$CLASSPATH"`
fi# If a specific java binary isn't specified search for the standard 'java' 
binary
if [ -z "$JAVACMD" ] ; then
  if [ -n "$JAVA_HOME"  ] ; then
    if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
      # IBM's JDK on AIX uses strange locations for the executables
      JAVACMD="$JAVA_HOME/jre/sh/java"
    else
      JAVACMD="$JAVA_HOME/bin/java"
    fi
  else
    JAVACMD=`which java`
  fi
fiif [ ! -x "$JAVACMD" ] ; then
  echo "Error: JAVA_HOME is not defined correctly."
  echo "  We cannot execute $JAVACMD"
  exit 1
fiif [ -z "$REPO" ]
then
  REPO="$BASEDIR"/repo
fiCLASSPATH=$CLASSPATH_PREFIX:"$BASEDIR"/etc:"$REPO"/org/codehaus/mojo/appassembler-maven-plugin/it/programJvmArguments-test/1.0-SNAPSHOT/programJvmArguments-test-1.0-SNAPSHOT.jar
EXTRA_JVM_ARGUMENTS="-Xms16m"# For Cygwin, switch paths to Windows format 
before running java
if $cygwin; then
  [ -n "$CLASSPATH" ] && CLASSPATH=`cygpath --path --windows "$CLASSPATH"`
  [ -n "$JAVA_HOME" ] && JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
  [ -n "$HOME" ] && HOME=`cygpath --path --windows "$HOME"`
  [ -n "$BASEDIR" ] && BASEDIR=`cygpath --path --windows "$BASEDIR"`
  [ -n "$REPO" ] && REPO=`cygpath --path --windows "$REPO"`
fiexec "$JAVACMD" $JAVA_OPTS \
  $EXTRA_JVM_ARGUMENTS \
  -classpath "$CLASSPATH" \
  -Dapp.name="program-03-test" \
  -Dapp.pid="$$" \
  -Dapp.repo="$REPO" \
  -Dbasedir="$BASEDIR" \
  org.codehaus.mojo.appassembler.example.helloworld.HelloWorld \
  test-environment "$@" From: [email protected]
To: [email protected]
Date: Wed, 4 Jan 2012 17:31:18 +0000
Subject: RE: [mojo-dev] Appassembler plugin...







One thing I once hit was the difference between an absolutePath/absoluteFile 
and a canonicalPath/canonicalFile 
Using the latter fixed it for me on bamboo.
 
-Robert
> Date: Wed, 4 Jan 2012 17:32:22 +0100
> From: [email protected]
> To: [email protected]
> Subject: [mojo-dev] Appassembler plugin...
> 
> Hi,
> 
> i currently have a strange problem which i can't solve on my own...May 
> be someone can lend me a hand or has some suggestions......or may be i'm 
> just blockhead...
> 
> Currently the build more or less always fails...on the appassembler 
> plugin in bamboo....but i have a jenkins running which in the majority 
> of the cases 
> succeeds...(http://78.46.16.202:8080/jenkins/job/appassembler-plugin/)
> 
> If i check on my local machines (MacOS Java 1.6 / Ubuntu Java 1.6) with 
> Maven 2.2.1 / 3.0.3 it works...
> 
> Of course this are two different environments.....
> 
> So currently i'm assuming that there is a problem with the injection of 
> some components via plexus / sisu-guice DI ...?
> 
> Could using the following in an injected component cause such problem:
> 
> @plexus.component
> 
> instead of
> @component
> 
> ?
> 
> Many thanks in advance...
> 
> 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
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
                                                                                
  

Reply via email to