[ http://jira.codehaus.org/browse/MNG-1437?page=comments#action_83696 ] Ole Ersoy commented on MNG-1437: --------------------------------
Well, I posted this on the EMF Tools newsgroup anyways: http://www.eclipse.org/newsportal/article.php?id=21611&group=eclipse.tools.emf#21611 Incidentally, I would think that using EMF would improve productivity. Well, why is that Ole? Because with EMF all the model code is generate from the XML Schema. Need to update the model, update XML Schema and regenerate the model, and the code is up to date. Are you concerned that using a different model API would necessitate a lot of changes in the fundamental Maven code? I thought Plexus initializes model components? If that's the case then it should be a really straightforward switch. All that is needed is a module that Plexus uses to fetch EMF values from the loaded instance. This should be really easy to code, if it does not already exist. I pretty much have it done something like this done already for the JPackage project. And the pool of individuals working on the Maven model capabilities would be larger. IBM already has a large number of talented inviduals working on EMF full time. The Apache Tuscany project complements this team as well. Anyways, at least you know it's an option. If the development roadmap of Maven is such that very little depends on upgrading the model, then mabye the switch is not worth it. But how do you know that is the case? If all you had to do to upgrade the model is upgrade the xml schema, then why not do it? I assume the answer is that you can do this with Modello too, and the selection fo the ModelResource factory (The part that creates the model instances that correspond to each XML element) is trivial to implement. So if that's the case then EMF and Modello are on equal footing pretty much. What about the Maven Eclipse Plugins (The one for working with the Maven Model visually). EMF also generated a .edit project for ItemProviders that are used to hookup SWT widgets to their corresponding model. If you try out EMF you'll see that it generates not just the model, but also a .edit project containing ItemProviders for each model class. The ItemProviders adapt the model objects so that they can be hooked up to swt widgets. EMF also generates an editor using JFace components for the model. This forms a good picture of how to edit the model using eclipse. So using EMF could also speed Maven Eclipse Plugin development. Anyways I would think about this in terms of all the things the Maven Model drives, and how many of those things need to be updated when the model is updated. The EMF Framework is built around model driven development, so all the things that depend on the model, can be regenerated using JET templates when the model changes. If you have a similar capability in mind for Modello, then you are on equal footing, but if you have a simillar capability in mind, then why not just use EMF...and pool all the development resources? Either way Maven is a Brilliant product and thanks for all the hard work put into it. Happy New Year! - 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
