From: Sahoo <Sahoo_at_Sun.COM>
Date: Wed, 27 Aug 2008 20:01:38 +0530

Kedar Mhaswade wrote:
>
>
> Bhakti Mehta wrote:
>> Hi asadmin folks,
>> I need to add 4 scripts for xjc,schemagen,wsgen and wsimport in V3.
>> Metro will be downloaded via Update center so these scripts will be
>> installed by UC in bin folder of glassfish
>> I was looking at the template of asadmin scripts and tried to do the
>> following
>>
>> https://glassfish-svn.dev.java.net/source/browse/glassfish-svn/trunk/v3/webservices/jsr109-impl/pom.xml?view=diff&rev=22136&p1=trunk/v3/webservices/jsr109-impl/pom.xml&p2=trunk/v3/webservices/jsr109-impl/pom.xml&r1=22135&r2=22136
>>
>>
>> And this is the code for the template for my script
>>
>> https://glassfish-svn.dev.java.net/source/browse/glassfish-svn/trunk/v3/webservices/jsr109-impl/src/main/resources/wsgen?view=auto&rev=22136
>>
>>
>> However if I copy the scripts from target/classes/ to <directory of
>> web.zip>/glassfish/bin (Just trying to test out)
>> It tries to set AS_INSTALL to glassfish/bin instead of glassfish.
>> What am I missing?
>>
>> How does asadmin come out so clean in the web.zip bundle with just
>> this line?
>> java -jar "%~dp0..\modules\admin-cli-10.0-SNAPSHOT.jar" %*
>
> :) Black magic isn't? Performer: Byron Nevins.
>
> It uses the manifest entries to get to those additional jars.
> See the admin/cli/pom.xml.
Since we encode version number in file names, how does it work when one
upgrades one of the dependent jar files? The same applies to what Bhakti
is doing as well.

Thanks,
Sahoo