Nope, I gave the right command, but subeclipse won't handle a revert &
merge situation. Svn won't handle a restore & merge, nor a restore more
than 1 level deep. Or an update after a commit which failed. It can give
server 500 errors in some situations or say that a directory can not be
found while it's actually there. Loads of fun.
The best part is where svn update deletes a directory and then states it
can't add it back, because it exists. "while [ 1 ]; do svn update; done"
does miracles then.
Ah shoot, the commit worked, but subeclipse has wrecked my workspace
again. metamodel is back in place.
Carlo
On Sun, 2007-02-04 at 11:13 +0100, Carlo de Wolf wrote:
I gave the wrong svn command during merge, it's now probably in
some
nether regions of trunk. I'm fixing my workspace right now, because svn
completely wrecked it. Both subeclipse and the command line versions
contain serious bugs which can really make a mess of things.
Carlo
On Sat, 2007-02-03 at 23:34 -0800, Scott M Stark wrote:
> I seem to have lost the org.jboss.metamodel package from the ejb3 module
> after updating my 4.2 workspace. Where is it now?
>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development