baerrach wrote:
>
> I've re-opened it.
>
> I haven't had the chance to look in detail at the problem.
>
> If there are enough steps to reproduce the problem then there is a
> better chance of it getting fixed.
>
I've resolved my issue, and commented on the jira as follows:
OK, I have fixed
On Mon, Jan 12, 2009 at 9:32 PM, crowne wrote:
>
> I am experiencing this too, and I found a jira for this issue which was
> closed but I think should be reopened.
> http://jira.codehaus.org/browse/MECLIPSE-408
I've re-opened it.
I haven't had the chance to look in detail at the problem.
If the
I am experiencing this too, and I found a jira for this issue which was
closed but I think should be reopened.
http://jira.codehaus.org/browse/MECLIPSE-408
Regards,
Neil Crow.
Ian Orford wrote:
>
> Maven 2.0.9
> maven-eclipse-plugin 2.5.1
> Eclipse 3.4.1
>
> Some time ago, my "mvn eclipse:e
Maven 2.0.9
maven-eclipse-plugin 2.5.1
Eclipse 3.4.1
Some time ago, my "mvn eclipse:eclipse" commands started misbehaving. I
had been using it for ages previously.
My repo on my development workstation is in C:\Dev\.m2\repository.
The .classpath files that are generated when I run "mvn eclips