FYI:
The asenv files are launcher unit test resource files in order to be
able to fake a V3 installation, which allows me to test "bad" domain.xml
files etc.
The common-util ones are there for exercising AsenvPropertyReader --
which does a lot of stuff other than dealing with those config files
Thanks for updating the files Bill. The common-util files were REALLY
ancient so I cleaned them up.
On 4/1/2010 5:13 PM, Byron Nevins wrote:
> Bill,
>
> Don't bother with the other two. I'll follow up. They are probably
> both flotsam and/or jetsam.
>
>
> On 4/1/2010 11:35 AM, Bill Shannon wrote:
>> I find three versions of asenv.conf in the workspace:
>>
>> admin/launcher/src/test/resources/config/asenv.conf
>> common/common-util/src/test/resources/config/asenv.conf
>> packager/nucleus-base/config/asenv.conf
>>
>>
>> I assume the last one is the "real" one that ends up in the build.
>>
>> The first two are in test directories. The second one looks like an
>> old one from v2.
>>
>> If I update asenv.conf to add AS_DEF_NODEAGENTS_PATH, which of the
>> first two do I need to update as well?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188