Jean-François, Lars, Maven exclusions do look appealing and work well in some cases, but I discourage doing that, and back Nils's email reply instead. With exclusions, you start to bypass dependency management; it's comparable to deleting a single jar from your webapp, i.e. you have no guarantee that what remains will actually run properly. If an artifact has dependencies, then there's generally a good reason for that (I know, this sounds extreme for the case at hand though).
That said, if our demo webapp artifacts don't suit you, no worries, build your own webapp! As Nils said, you should first import e.g. our enterprise-bundle's dependencyManagement into yours. Then start from the empty-webapp and add the modules you need (no version required, it's managed). To get an idea of what modules are in magnolia-enterprise-webapp, mvn dependency:tree is your friend. It will also tell you precisely about those groupId:artifactId you look for. I hope this sheds some light a bit :) Cheers, Mika -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=7f968973-c206-4ce8-8f63-553c737aeb47 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
