Hi Dinesh,
[...]
>>>> Another question:
>>>> it tries to find an image called glassfish-image-SNAPSHOT.jar which
>>>> has the same name as the image downloaded by 'maven bootstrap' in
>>>> the trunk. Maven stores both images in the same local maven
>>>> repository. So the branch image would overwrite the trunk image,
>>>> unless we are using different groupids for branch and trunk. This
>>>> implies I cannot have both: a FCS workspace and a trunk workspace on
>>>> the same machine.
>>>
>>>
>>> No that's not true, currently we have following locations for
>>> SNAPSHOT jar files.
>>> SJSAS90_FCS_BRANCH:
>>> http://download.java.net/javee5/fcs_branch/nightly/${glassfish.os.name}
>>> TRUNK:
>>> http://download.java.net/javaee5/trunk/nightly*/*${glassfish.os.name}
>>
>>
>> These are the maven remote maven repositories and you are right we
>> have different locations for theses. But this is not what I meant. I
>> am talking about my *local* maven repository (property
>> maven.repo.local). Calling 'maven bootstrap' will update
>> glassfish-image-SNAPSHOT.jar in
>> ~/.maven/repository/glassfish-image/jars on my computer. Both branch
>> and trunk use the same file under the same location.
>
> Yes, it would be the case if you have "maven.repo.local" variable
> defined in your $HOME/build.properties otherwise (if you don't have it
> defined as per build instructions
> <https://glassfish.dev.java.net/public/BuildGlassFish.html>) default
> value would be
>
> maven.repo.local=${glassfish.root}/glassfish_dependencies
>
> And the above value is relative path to the workspace,
> glassfish.root=${basedir}/../.. Branch and trunk builds will have
> different directories which don't conflict as against to what you are
> describing. So just use default values and the problem you are facing
> won't arise.
thanks, this is good info! I thought I need to define maven.repo.local
in ~/build.properties, because I have another non-glassfish project
using maven. But it sounds like using the defaults, so not explicitly
specifying maven.repo.local in ~/build.properties, works for both projects.
Regards Michael
>
> thanks
> Dinesh
>
[...]