Hello Razvan,
In my experience you will have a much better experience if you build your own
project based on Magnolia then trying to manually add JAR files to a default
bundle. Also I don't see how a Spring project is going to work with a separate
Magnolia bundle deployment.
I really recommend setting up a project to build your own custom Magnolia
project to do your customizations. This doesn't mean you will be compiling
Magnolia, your project will just depend on pre-built artifacts from Magnolia
and can choose for yourself which modules you want to use (like Blossom if
you'd like to use Spring with Magnolia), and add your own code and
configuration. This may seem like overkill at first, but I can assure you this
is actually one of the great things about Magnolia and something you'll grow to
love. Adding custom code to something like Wordpress for instance may seem easy
("I'll just edit this file, add some of my own here, etc."), but always tuns
into a unmanageable nightmare after a while.
I recommend checking out
https://documentation.magnolia-cms.com/display/DOCS/Creating+a+custom+bundle
and this series of blog posts:
Don’t build Magnolia: build your projects.
http://dev.magnolia-cms.com/~gjoseph/dont-build-magnolia-build-your-projects
Don’t configure Magnolia: let your projects configure it.
http://dev.magnolia-cms.com/~gjoseph/dont-configure-magnolia-let-your-projects-configure-it
Don’t deploy Magnolia: deploy your project.
http://dev.magnolia-cms.com/~gjoseph/dont-deploy-magnolia-deploy-your-project
Nils.
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=059b3faf-f241-4a53-b14a-162b84f77efe
----------------------------------------------------------------
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: <[email protected]>
----------------------------------------------------------------
