Re: xbean in 2.1 break embeddabable usage of maven

2008-06-02 Thread Milos Kleint
I've created an issue for it. http://jira.codehaus.org/browse/MNG-3609 Milos On 5/29/08, Milos Kleint <[EMAIL PROTECTED]> wrote: > On Thu, May 29, 2008 at 9:23 PM, David Jencks <[EMAIL PROTECTED]> wrote: > > I wonder if having xbean add an editor if there is nothing there for a > class > > alr

Re: xbean in 2.1 break embeddabable usage of maven

2008-05-29 Thread Milos Kleint
On Thu, May 29, 2008 at 9:23 PM, David Jencks <[EMAIL PROTECTED]> wrote: > I wonder if having xbean add an editor if there is nothing there for a class > already would work. Possibly. But will xbean then keep on working? Also there's a question of timing. What code gets called first etc.. I'm not

Re: xbean in 2.1 break embeddabable usage of maven

2008-05-29 Thread David Jencks
I wonder if having xbean add an editor if there is nothing there for a class already would work. thanks david jencks On May 29, 2008, at 12:06 PM, Milos Kleint wrote: Well, the PropertyEditors class in xbean sets every imaginable property editor to java.beans.PropertyEditorManager.register

Re: xbean in 2.1 break embeddabable usage of maven

2008-05-29 Thread Milos Kleint
Well, the PropertyEditors class in xbean sets every imaginable property editor to java.beans.PropertyEditorManager.registerEditor() overriding and IDE's own editors. That means property customizers disappear etc, some places in the IDE don't cope with that.. I've seen a report where the GridBagLayo

Re: xbean in 2.1 break embeddabable usage of maven

2008-05-29 Thread Jason van Zyl
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 creat

Re: xbean in 2.1 break embeddabable usage of maven

2008-05-29 Thread Jason van Zyl
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

xbean in 2.1 break embeddabable usage of maven

2008-05-29 Thread Milos Kleint
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 o