What we need is an MDA approach :-) A model of the application and a set
of cartridges for a particular development environment.
On Tue, 2005-05-17 at 15:28 -0600, Chad Brandon wrote:
> Yeah we do need a generic code project generator, and then we could use
> templates for each given target build
On Tue, 2005-05-17 at 18:46 +0200, Matthias Bohlen wrote:
> Hi all,
>
> just tried the Maven IDE plug-in for Eclipse. Looks promising. It can
> even recognize plugins for Maven and can edit their preferences if
> they supply an Eclipse plug-in for Mevenide. (Does everybody understand
> what plugs
Yeah we do need a generic code project generator, and then we could use
templates for each given target build tool, right now we are duplicating
effort between the maven and ant generator. Also when we move to
maven2, it would be a lot easier if the andromdapp plugin was just a
wrapper around
Hi all,
I started work on Android, an Eclipse Plug-in for AndroMDA. Currently, I
am working on a "New AndroMDA Project" wizard that does exactly what the
AndroMDApp maven plug-in does. In fact, I am planning to use AndroMDApp
as the backend for the wizard. While I was thinking about it, it
appe
I tried it a while ago, and while it had good ideas, I think it had a
ways to go in usabiliy, maybe its improved since then.
Matthias Bohlen wrote:
Hi all,
just tried the Maven IDE plug-in for Eclipse. Looks promising. It can
even recognize plugins for Maven and can edit their preferences if
they
Hi all,
just tried the Maven IDE plug-in for Eclipse. Looks promising. It can
even recognize plugins for Maven and can edit their preferences if
they supply an Eclipse plug-in for Mevenide. (Does everybody understand
what plugs into what? :-)).
Martin, are you interested to integrate our AndroMDA
