no I think you tried to delete jmx-remote and then add it again
right ? that did not work when people had other files in the local
workspace like the target directory. I also add the fix some of your
pom.xml that had a few dependencies versions wrong. you should review
the changes.
jerome
On Jan 16, 2008, at 10:40 AM, Nandini Ektare wrote:
> Hi Jerome,
>
> Is there something that I need to fix? Or is it the expected way it
> would behave on future changes?
>
> I had a structural change in the dirs in jmx-remote module and I
> deleted existing and added the new changed module (with same name)
>
> I thought mvn -U install would take care of it. Won't it?
>
> Thanks
> Nandini
>>
>>
>> Subject: V3 build failure
>> From: Jerome Dochez <Jerome.Dochez_at_Sun.COM>
>> Date: Wed, 16 Jan 2008 09:52:32 -0800
>> To: dev_at_glassfish.dev.java.net
>> To: dev_at_glassfish.dev.java.net
>> Hi All
>>
>> You will most likely experience a build failure after updating the
>> V3 workspace (unless you do a fresh checkout), you will need to
>> manually delete the v3/admin/jmx-remote directory from you local
>> workspace to fix it.
>>
>> Once you deleted that directory, rerun a svn update and do a normal
>> mvn install
>>
>> Thanks, Jerome
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>