Maczka Michal <[EMAIL PROTECTED]> wrote on 03/05/2004 11:31:21 PM: > I don't think it will be that bad. Now clean, jar, compile plugin and it's > goal can be easly reused in other plugins > (e.g you don't have to write the same code for test plugin). The same can be said for the jelly code.
> My main problem with jelly/current design is that it disallows to reuse the > code easly. > See how test plugin is similar to java plugin. That can quite easily be fixed by creating a taglib as you know. > Duplicated code = no consitency = bad design. More over nobody else was ever > reusing our long jelly scripts. The whole point of maven is that you don't need to change the code, though. > With simple Pojo stratgey we might even serve as source of ant tasks! That'd be a great strategy. Extract the ant tasks into POJOs. > Sure. But I don't know a single person which tried to implement something > with jelly > which was really productive. I dare to say that it will be much faster to > write plugins in Java then in jelly. > I spent myself hours doing something horribly basic in jelly. And note that > number of users of plugins in not comparable > with the number of plugin devlopers. Most people just use the plugins and > the way it is implemented is not importand for them It's long been possible to write beans in jelly and call them from plugins, as you know. why do so few people do it? -- dIon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
