Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <455C582A.6030805@cyberspaceroad.com>
Date: Thu, 16 Nov 2006 12:23:06 +0000
From: Adam Hardy <adam.maven@cyberspaceroad.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: continuum-users@maven.apache.org
Subject: Re: SCM integration issue with deleted files
References: <45599D9F.7080606@cyberspaceroad.com>
 <4559A1D6.5070002@c-s.fr>	 <52bab8690611140729y58aebe90t5013c423adb49a8@mail.gmail.com>
 <fbd9e9df0611141312g1b005b9ax605d078d225b48a2@mail.gmail.com>
In-Reply-To: <fbd9e9df0611141312g1b005b9ax605d078d225b48a2@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Perforce! See what happens when you pay huge amounts of money for 
something? ;)

I've got 'clean' in every build definition.

I shall file it in Jira.

Thanks
Adam

Lee Meador wrote:
> The only similar problem I found was solved by making sure the Continuum
> build had a clean in it. I'm using a maven2 build from a script and
> subversion. The scm may make a difference.
> 
> -- Lee
> 
> On 11/14/06, Wayne Fay <waynefay@gmail.com> wrote:
>>
>> Tell your developers to stop deleting files? ;-)
>>
>> Sounds like a bug, go file it in JIRA and I'm sure it will be looked
>> at and hopefully addressed in a future version.
>>
>> Wayne
>>
>> On 11/14/06, ETIENNE Olivier <olivier.etienne@c-s.fr> wrote:
>> > I got the same problem and the only way I foun to solve it has been to
>> > drop the project and to create a new one.
>> >
>> > Adam Hardy a �crit :
>> > > I keep seeing a problem with continuum when a developer deletes a
>> file.
>> > >
>> > > Sometimes but not always continuum fails to delete the file from its
>> > > working directory. Then at some point soon afterwards, that deleted
>> > > class file will no longer compile, so the build fails and I receive a
>> > > notification.
>> > >
>> > > What is the best procedure to deal with this? Must I hunt down the
>> > > deleted files and manually delete them?
>> > >
>> > > In a rush this morning, I deleted everything in /working-dir/ with rm
>> > > -rf *
>> > >
>> > > Continuum did not like it. When I launched the build, it stopped
>> > > immediately with:
>> > >
>> > > java.lang.NullPointerException
>> > >     at
>> > >
>> >
>> org.codehaus.plexus.component.configurator.converters.lookup.DefaultConverterLookup.findConverterForType 
>>
>> (DefaultConverterLookup.java:115)
>> > >
>> > >
>> > > I had to restart continuum, and then the first build attempt died
>> > > badly with this:
>> > >
>> > > Exception:
>> > > Cannot checkout sources.
>> > > null
>> > >
>> > > but on the second attempt it behaved OK. Why is the working-dir so
>> > > important? Can't continuum detect that it needs to check out the
>> > > sources again? Is there a better way to delete all the sources 
>> without
>> > > causing this mess?
>> > >
>> > >
>> > > Thanks
>> > > Adam
>> > >
>> > >
>> >
>> >
>>
> 
> 
>