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?
We haven't seen any problems in the Eclipse integration regarding the
property editors. What exactly is the problem with registering
additional property editors. I'm sure there is a way to make that
optional, just trying to understand what the actual problem is. The
XBean folks just released XBR and we'll probably stick with that, but
we can get a fix in for property editors if it is not configurable
right now.
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
----------------------------------------------------------
You are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of
dogmas or goals, it's always because these dogmas or
goals are in doubt.
-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
