Hi to you,

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)

Sometimes it's much more simpler than someone can ever imagine in particular myself...

......oh my lord (mea culpa!)...(Thanks for your support and time)...

I oversight completely that i had two entries for the same program name (program-03-test) in the integration test pom.xml:

            <program>

<mainClass>org.codehaus.mojo.appassembler.example.helloworld.HelloWorld</mainClass>
              <name>program-03-test</name>
              <commandLineArguments>
                <commandLineArgument>test-environment</commandLineArgument>
              </commandLineArguments>
            </program>
            <program>

<mainClass>org.codehaus.mojo.appassembler.example.helloworld.HelloWorld</mainClass>
              <name>program-03-test</name>
              <jvmSettings>
                <initialMemorySize>20m</initialMemorySize>
                <maxMemorySize>256m</maxMemorySize>
                <maxStackSize>128m</maxStackSize>
                <systemProperties>
                  <systemProperty>anton=2345</systemProperty>
                  <systemProperty>berta="xaz"</systemProperty>
                </systemProperties>
                <extraArguments>
                  <extraArgument>-Dtest=false</extraArgument>
                  <extraArgument>-Dlog4j.properties=false</extraArgument>
                </extraArguments>
              </jvmSettings>
              <commandLineArguments>
                <commandLineArgument>test-environment</commandLineArgument>
              </commandLineArguments>
            </program>

and of course the order of generation is not defined or be more accurate is depending on JVM etc. so sometimes the first one and sometimes the second was the final candidate which runs...

That seemed to cause the problems...waiting on the result of the CI...

Thanks for your support...

But this brings to my mind that i have to implement some kind of check for this problem......

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