Berin has been doing some changes to the maven build for the better, but
I think you have to upgrade the jar plugin to be able to build. The code
itself is not broken, I have an example app built on top of it.

On Mon, 2004-01-19 at 21:15, Vincent Tence wrote:
> It's the introduction of COP to Swing. A framework for building
> component based swing apps. It uses fortress for container.
> 
> The idea is to use fine grained components as application "Screens".
> (Think of them like component versions of regular JPanels). You get the
> benefit of COP in that your swing app screens are no longer so coupled
> and you avoid traditional Swing spaghetti code. All screens are wired
> together with the help a some key components provided by the framework:
> 
> - The EventBus - which you already know of, provides the event subsystem
> that screens use to communicate
> - The ActionManager well ... manages Swing Actions run in response to 
> button/menus/.. clicks. Commands can be run in sync or async mode using
> the excalibur event package.
> - The ScreenManager embeds Screens in panels or dialogs for display.
> 
> Then there are some utlity components, useful in almost any Swing app:
> document manager, document store, ...
> 
> If you're thinking of developping a *maintainable* Swing app, that's the
> way to go.
> 
> - Vincent
> 
> On Mon, 2004-01-19 at 15:20, Alex Karasulu wrote:
> > Vince,
> > 
> > What was this guiapp thing you worked on over at sf.net.  The cvs stuff
> > is broke and I ran across it wondering if I can use if for a client.  
> > Could you give me some background and functionality. 
> > 
> > Alex
> > 
> > 
>