This fails if someone has ${glassfish.home} as /s/b/publish/glassfishpe, and we
cann't have the limitation to have bin, lib, domains directories under "glassfish"
Nightly build failed after making that change as we have different
$glassfish.home set for different type of builds..
<zip destfile="${glassfish.zipfile}"
- basedir="${install.home}"
- includes="**"
+ basedir="${install.home}/.."
+ includes="glassfish/**"
excludes="samples/**"
I will lookinto this to fix for both such options.
Amy Roh wrote:
> Looks like an oversight happened when we changed to glassfish with
> clustering installer.
>
> I have updated the issue [1] so Dinesh can take a look at it. It
> should be fixed for the next promoted build.
>
> [1] https://glassfish.dev.java.net/issues/show_bug.cgi?id=965
>
> Thanks,
> Amy
>
> Kedar Mhaswade wrote:
>
>> Are you experiencing
>>
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=965?
>>
>> Looks like a packaging/image-creation issue.
>>
>>
>> Kedar
>>
>> Arun Gupta wrote:
>>
>>> GlassFish v2 b13 jar [1] extracts all the contents in the current
>>> directory without creating glassfish directory. So once I hit on
>>> "Accept", the installer starts creating docs, javadb, docs, lib etc.
>>> directories without creating a parent glassfish directory.
>>>
>>> Can this be fixed ?
>>>
>>> [1]
>>> http://java.net/download/javaee5/promoted/WINNT/glassfish-installer-v2-b13.jar
>>>
>>>
>>> -Arun
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>