I don't think maven-reactor-plugin will help here then. I didn't know
Class-Path in manifest entry gets resolved to actual file directory so
symlink will not work in this case. Here's another option you can try:
In the admin/cli/pom.xml, add the following in the <build>...</build>
element:
<directory>${gf-install}/glassfishv3/glassfish/modules</directory>
<outputDirectory>${project.basedir}/target/classes</outputDirectory>
and execute the maven in admin/cli as:
mvn -Dgf-install=/<GlassFish installation>/ -DskipTests=true install
You'll see the updated admin-cli.jar in the glassfish/modules
directory. However, the admin-cli-sources.jar will also be there.
Let me know if this works for you.
Jane
Sanjeeb Sahoo wrote:
> On Monday 07 June 2010 11:27 PM, Yamini K B wrote:
>>
>>> I think this is related to Class-Path manifest entry present in the
>>> jar. Soft-links gets resolved to the actual file and Class-Path will
>>> no more be valid for your case.
>> So linking jars like this is not correct? How to overcome this problem?
>>
> Have you experimented with maven-reactor-plugin? You should be able to
> update your distributions/glassfish/target/stage area using maven
> every time you change some code.
>
> Sahoo