[ http://jira.codehaus.org/browse/MNG-1437?page=comments#action_83760 ] Ole Ersoy commented on MNG-1437: --------------------------------
Another consideration is upgrading modello for new Java releases to include support for new Java Features. The EMF Code Generation templates have already been upgraded to support generics, the new Enum, etc. What about Modello tooling? EMF already has lots of ECore Model Editors, Class Diagram Visualization, etc. How about Support? When I ask a questions on the EMF mailing list, Ed Merks usually gets back to me in 5 minutes with great very helpful anwswers (And he's extremely helpful and open when it comes to adding support for use cases). And I ask a lot of goofy questions. Sure you can support modello too, but from what I understand you want to optimize your use of resources. How about Modello articles on how to get Started etc? Are there Javadocs generated for Modello? With EMF just open eclipse help, and there's the Javadoc, Other help documentation, articles, etc. What about datasource integration? With EMF adding support for the datasources Modello supports is just a matter of adding a few JET Templates. EMF is the baseline for Service Data Objects, and the Apache Tuscany project provides an implementation for this, in addition to eclipse.org. This makes a lot of developers gravitate towards EMF, which really drives the future of it. This is an important consideration for a modeling framework, which I'm sure is the reason why IBM has put so many heavyweight resources behind it. Cheers, - Ole > How to make additions to the POM and have it be backward/forward compatible > --------------------------------------------------------------------------- > > Key: MNG-1437 > URL: http://jira.codehaus.org/browse/MNG-1437 > Project: Maven 2 > Issue Type: Task > Components: Design, Patterns & Best Practices > Reporter: Jason van Zyl > Priority: Trivial > Fix For: 2.1 > > > I would like to add categories and site staging information to the POM but > don't want to break everything. Brett and I have discussed this topic briefly > but we need the XML parsing mechanism to be a bit more flexible or we may > just have to embrace namespaces to make this work ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
