Danilo Luiz Rheinheimer 16 Years Ago I can see some areas to improve :- script : a portlet plugin to grails can be very usefull. Or another way to develop potlets on a script language.- to be able to extend liferay without the need of use the ext enviroment.- better error messages when something goes wrong.- make everything hot deployable. Please sign in to reply. Reply as... Cancel Alberto Montero Danilo Luiz Rheinheimer 16 Years Ago Hi Danilo.You're right. The ability to use scripting languages to develop in Liferay is one of the main topics of Romulus. Please sign in to reply. Reply as... Cancel Ezequiel Chavez Danilo Luiz Rheinheimer 16 Years Ago More areas to improve:-Full i18n support (Polls portlet, Web Form portlet, Calendar portlet, welcome message, terms of use agreement page).-Upgrade to Spring 2.5. Including AOP for cross cutting concerns (transaction, log, audit), creating Liferay NamespaceHandler for easy spring config, dependency injection for core struts actions.-Support for multiple environment, DTAP model (Development, Test, Acceptance and Production). Please sign in to reply. Reply as... Cancel
Alberto Montero Danilo Luiz Rheinheimer 16 Years Ago Hi Danilo.You're right. The ability to use scripting languages to develop in Liferay is one of the main topics of Romulus. Please sign in to reply. Reply as... Cancel
Ezequiel Chavez Danilo Luiz Rheinheimer 16 Years Ago More areas to improve:-Full i18n support (Polls portlet, Web Form portlet, Calendar portlet, welcome message, terms of use agreement page).-Upgrade to Spring 2.5. Including AOP for cross cutting concerns (transaction, log, audit), creating Liferay NamespaceHandler for easy spring config, dependency injection for core struts actions.-Support for multiple environment, DTAP model (Development, Test, Acceptance and Production). Please sign in to reply. Reply as... Cancel
Mika Koivisto 16 Years Ago Maven support would nice for those of use who use maven. Full on maven adaptation isn't required. A good starting point could be just providing maven artifacts for all the jars and war. Next step could be creating some maven plugins that would help creating Liferay plugins such as having Liferay plugins sdk as a maven plugin. Also Service Builder plugin would be great. Please sign in to reply. Reply as... Cancel Jason E Shao Mika Koivisto 14 Years Ago I have to strongly agree with this - increasingly I can't imagine living w/o Maven - and the hoops required to jump through to use Maven in Liferay have been painful.Some items I wish for:* Easier testing - better hooks for mock/unit testing & setups* Much better developer documentation (e.g. much of the ServiceBuilder produced classes can be very difficult for a new developer to decipher, since they tend to lack any reasonable javadoc/others* simpler application of cross-cutting concerns & capabilities (comments, blogs, auditing, backups, i18n, etc - e.g. ideally you should be able to easily implement some standard java i18n and have Liferay be able to dynamically inject langauges/bundlesOn the tools side, have you looked at Spring Roo? I'm not sold yet, but it looks interesting Please sign in to reply. Reply as... Cancel
Jason E Shao Mika Koivisto 14 Years Ago I have to strongly agree with this - increasingly I can't imagine living w/o Maven - and the hoops required to jump through to use Maven in Liferay have been painful.Some items I wish for:* Easier testing - better hooks for mock/unit testing & setups* Much better developer documentation (e.g. much of the ServiceBuilder produced classes can be very difficult for a new developer to decipher, since they tend to lack any reasonable javadoc/others* simpler application of cross-cutting concerns & capabilities (comments, blogs, auditing, backups, i18n, etc - e.g. ideally you should be able to easily implement some standard java i18n and have Liferay be able to dynamically inject langauges/bundlesOn the tools side, have you looked at Spring Roo? I'm not sold yet, but it looks interesting Please sign in to reply. Reply as... Cancel