You should probably do svn move x.java b/x.java
As it is, you're making a new copy of the file, while leaving the old one,
so Maven compiles and packages both.
At this point, svn del x.java should fix your problem.
On Mon, Apr 21, 2008 at 2:55 PM, Byron Nevins <Byron.Nevins_at_sun.com> wrote:
> I don't get it. Let's say I have a class, a.x
> I did a 'svn copy x.java b/x.java'
>
> It worked. Now there is an "x.java" in /a/b, but not in /a
>
> I rebuild the module.
> Inside the brand new module jar are both: a.x and a.b.x
> !!!
>
> So now I delete the module from the maven repository.
> I delete the target directory
> I run mvn -o
>
> Inside the jar is, again, a.x and a.b.x
>
> How can I make a.x go away?!?
> Where is it getting a.x from?!?
>
> --
> Byron Nevins Work 408-276-4089, Home 650-359-1290, Cell 650-784-4123 - Sun
> Microsystems, Inc.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>
--
Jason Lee, SCJP
Software Architect -- Objectstream, Inc.
Mojarra and Mojarra Scales Dev Team
https://mojarra.dev.java.net
https://scales.dev.java.net
http://blogs.steeplesoft.com