On Jan 16, 2008, at 1:11 PM, Nandini Ektare wrote:
>
>> -----Original Message-----
>> From: Jerome Dochez <Jerome.Dochez_at_Sun.COM>
>>
>> Date: Wed, 16 Jan 2008 10:49:15 To:dev_at_glassfish.dev.java.net
>> Subject: Re: V3 build failure
>>
>>
>> no I think you tried to delete jmx-remote and then add it again
>> right ?
> Yes to incorporate the changes to reduce server footprint I
> separated server and client modules.
>> that did not work when people had other files in the local
>> workspace like the target directory.
> So if I understand it correctly, anyone who has built the space once
> before will have target dir present and will be forced to do a
> complete a fresh build.
or manually delete the admin/jmx-remote directory to clean this up.
>
>
> Is there a way to make such changes transparent to existing
> workspaces?
well I am not a subversion expert but there might be an svn update
option to force overwriting in existing directory...
>
>> I also add the fix some of your pom.xml that had a few dependencies
>> versions wrong.
> I will take a look at the new versions.
>
> It's a bit confusing though because I did not change any
> dependencies. And it built fine even with those wrong versions.
so this has happened because you probably built at least once the
imported modules with the wrong versions and they were stored in your
local repo (~/.m2/repository). Then you probably changed the imported
modules versions but did not change the <dependencies> versions (which
were picking the old one), therefore the build was successful.
>
>
> Is there something in the build process (or a separate step before
> commit) to verify whether correct versions have been included?
one of the way is to remove your local .m2 repo, that clears up all
local build you may have done and would have shown the failure. That's
usually what I do when I change a lot of dependencies or versions of
my modules.
after checking in, you should also check hudson to see if the build
pass.
Jerome
>
>
> Nandini
>> 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
>> > <mailto:Jerome.Dochez_at_Sun.COM> Date: Wed, 16 Jan 2008
>> 09:52:32 -0800 To: dev_at_glassfish.dev.java.net <mailto:dev_at_glassfish.dev.java.net
>> > To: dev_at_glassfish.dev.java.net <mailto: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 <mailto:dev-unsubscribe_at_glassfish.dev.java.net
>> > For additional commands, e-mail: dev-
>> help_at_glassfish.dev.java.net <mailto: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
>