Hi, glad you like it :)
Just to clear up: the initial reason for this was to make integration of archetype-based solutions easier into non-maven apps. For example, for nexus-archetype-plugin, I really needed the model _only_, nothing else, so I "stole" the modello mdo file of archetype-catalog (and create ARCHETYPE-303 issue along) and put that into nexus plugin (it was simpler than "dragging" in archetype-common and have zillion of excludes just to reach the model and nothing else). On the other hand, Maven Indexer (former Nexus Indexer) was offering -- mostly for IDE integrations -- an indexer based ArchetypeDataSource, so maven indexer "needs" that interface only, but not the catalog model. Finally, we ended up with doubled models in Nexus -- they are completely separated by plugin-classloaders, etc and not causing any problem at all -- but still, I wanted a cleanup since it was not correct (and tattletale was pushing me to do it :D ). After this change, the nexus-archetype-plugin will just reference the archetype-catalog model as external dependency, just as it needed to be in first place. And at the end, like in good bedtime stories, after this change: http://svn.apache.org/viewvc?view=revision&revision=1036665 it all proved non-issue: Indexer based ArchetypeDataSource is not widely used -- as far as I know, in IDEs only -- and is not used in Nexus at all :D But still, having separate models will still ease of some next potential integrator's life. Thanks, ~t~ On Thu, Nov 18, 2010 at 11:58 PM, Brett Porter <br...@apache.org> wrote: > > > Sounds like a good enhancement. > > > You can actually commit it yourself if you'd like (and then perhaps for > specific review if you are unsure) - lazy consensus and relying on version > control are fine :) Additionally it's actually easier to review this commit > in SVN in this case since you're moving files around the patch has a lot of > + / - noise. > > Thanks, > Brett > > -- > Brett Porter > br...@apache.org > http://brettporter.wordpress.com/ > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
