Milos,

Additionally, it is impossible for us to know unless there is some representative test that is run on our side. I've had XBR in there for over a month now. Anything with system properties, threads, and now property editors have to have some representation in the tests. If you create something that represents the problem I'll fix it by the end of next week.

On 29-May-08, at 5:47 AM, Milos Kleint wrote:

Hey..

I've upgraded the netbeans users to latest 2.1-SNAPSHOT of maven
embedder. I've done so to get the fix for issue with bad metaversion
(RELEASE/LATEST) resolving.. However I've ended up with another severe
problem. xbean seems to register it's own property editors into
PropertyEditorManager on startup, wreaking havoc in the IDE.

http://www.netbeans.org/issues/show_bug.cgi?id=135868 (50 duplicate
reports since 2 days)
or
http://www.netbeans.org/issues/show_bug.cgi?id=136067

and there's probably more.

is there a way to make xbean stop doing it? will I in turn end up with
broken maven/plexus?

Thanks for any pointers.

Milos

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole

-- Christopher Alexander, A Pattern Language



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to