>> - start the build, and replace the generated >> optional by one grabbed from the one in binary >> tarball. >> >> In such case, I'll have to include both source and binary in >> rpm, and to reduce rpm size, I'd rather like to have optional.jar >> available (and signed) in download dir >> >> - Use InterfaceFaker from Jon (and ask Jon how it works ;) >> >> >> Thanks for your advices...
>As you won't provide those commercial jars packaged, what's the use of >building related tasks ? A packaged application should not >rely on external >world to work, but on the environment established by its >dependencies only. I agree but jakarta rpm users may complains if they don't find optional tasks for there vaj, weblogic... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
