I've discovered that the ID doesn't really matter. Looks like it may be a NetBeans-only thing? Switching to info.magnolia or just magnolia results in the same lists for everything.
Once I create a project from the archetype [b]magnolia-project-archetype[/b] I am able to start it up successfully. Good deal. I add in some config files to make it use the Oracle DB that I want to use, and it runs well. Now I want to add in some dependencies like magnolia-module-blossom, but the latest version in the Maven repo is 1.2.3! I can download 2.0.1 from the magnolia store in the admin interface. After adding several dependencies (Google Analytics, STK) I start finding that the versions of the modules are so out-dated that they aren't compatible with Magnolia 4.5.7. Or possibly the standard set of JARs in the base archetype is so outdated that they aren't compatible with the newer ones going in? So, maybe I'm taking the wrong approach here. I tried going through the Magnolia Academy in the wiki and it had some great resources for starting a project - but I'm not sure if I'm even starting the project I should be starting. At the end of the day, I need to make a custom skin for Magnolia and put together one module (preferably with the Spring framework through Blossom). How should I approach this? -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=80800281-5374-49b6-b1ae-acea4ca1d4a4 ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
