Re: [Wrapper-user] app param not passed to WrapperSimpleApp

[Leif M. <lei...@ta...>]

Thies,
I am sorry for the trouble.  This is not really a bug.  It is because the
batch files or shell script that were named testwrapper in the Wrapper's bin
directory are being used as is for your application.  Those scripts have a
hard coding parameter in them that make it possible to pass in an argument
from the command line.
Please use the template batch files from the WRAPPER/src/bin directory for
your application.

This was an issue with 3.4.0 and 3.4.1 and several other users have been
confused by it as well.   We have added some checks to the 3.5.1 release
coming out today which will warn you when it detects this and hopefully save
the time I am sure you spent looking into this.

We are not currently in Iblio but I will have our team look into what is
necessary to upload.  One of our users had uploaded 3.2.3 several years
back.

Cheers,
Leif

On Fri, Jul 9, 2010 at 6:50 AM, Thies Edeling <th...@rr...> wrote:

> I'm using wrapper 3.4.1 and somehow the wrapper.app.parameter.1 config
> parameter isn't passed to the mainclass (WrapperSimpleApp in my case)
> anymore.
> Even when modifying the supplied test wrapper config to WrapperSimpleApp
> and using a non-existing class as parameter I'm still getting the usage
> message in my logs; no classnotfound exception.
>
> Is this a known issue? My config which was working for 3.2.3 doesn't
> work with 3.4.1 for this reason.
>
> Also, is there a Maven repo providing wrapper.jar for 3.4.1 ? Ibiblio
> only has 3.2.3.
>
> thx
>
>