On Aug 12, 2008, at 16:20, Scott Ferguson wrote:
> On Aug 12, 2008, at 4:05 PM, Rob Lockstone wrote:
>> Prior to version 3.1.x of Resin, it was possible to pass arguments to
>> the script that started resin, typically -X and -D arguments that
>> would get passed to the JVM.
>> As of version 3.1, this is now accomplished by using the <jvm-arg>
>> in the resin.conf file.
> You can use -Dfoo=bar from the command line in the most recent
> versions of 3.1.x.
> Earlier versions were not copying that command line from the watchdog
> to Resin, but that should now be fixed.
Cool! Do you mean the snapshot? Because I have 3.1.6 Pro and it
doesn't allow that.
> -- Scott
>> As a developer, I like to be able run our code locally for testing/
>> debugging. But we have some pretty big caches that take a little time
>> to load up during initialization, and often are not needed when doing
>> local testing. So I put in some code that looks for a property and
>> disables the caching if this property is set. Prior to Resin 3.1, I
>> was able to pass this property in when I started up resin from the
>> command line. To get the same behavior with Resin 3.1, I've created a
>> copy of my resin.conf file named nocache.conf that has this extra
>> property in it and I pass -conf conf/nocache.conf into the 3.1 httpd
>> Since I don't often update my resin.conf, I can live with this, but I
>> was wondering if there's an easier way to accomplish what I'm doing
>> short of keeping two, nearly identical, versions of my resin.conf
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list