Sorry I have now restored these.

Alasdair

On 1 September 2010 17:50, Holly Cummins <[email protected]> wrote:
>> Having further investigated the problem is less widespread than
>> subclipse led me to believe. I am about to remove the following
>> .project/.classpath/.settings files
>
> [...]
>
>> D samples-sandbox/wordassociation-sample/wordassociation-api/.classpath
>> D samples-sandbox/wordassociation-sample/wordassociation-api/.project
>> D       samples-sandbox/wordassociation-sample/wordassociation-
>> datasource/.classpath
>> D       samples-sandbox/wordassociation-sample/wordassociation-
>> datasource/.project
>> D samples-sandbox/wordassociation-sample/wordassociation-jpa/.classpath
>> D samples-sandbox/wordassociation-sample/wordassociation-jpa/.project
>> D samples-sandbox/wordassociation-sample/wordassociation-web/.classpath
>> D samples-sandbox/wordassociation-sample/wordassociation-web/.project
>>  M      samples/blog/blog-assembly
>> D       samples/blog/blog-assembly/.settings
>
> Could we please keep the eclipse metadata for the wordassociation
> projects? They're a bit different from the other samples, since the
> eclipse projects themselves form the deliverable. If people try and make
> the projects following the instructions and get it wrong, they can compare
> the metadata to the 'master' metadata and see what they did wrong. They
> can also point their eclipse at the existing projects and have something
> ready to go for a demo. I'm not convinced that mvn eclipse:eclipse could
> reproduce the metadata we have unless we hardcoded in a lot of overrides.
>
> Holly
>
>
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
>
>
>
>
>



-- 
Alasdair Nottingham
[email protected]

Reply via email to