If you are an internal developer or a contributor please follow the instructions found here: Coding Conventions. It is important to add them before jsp-property-group. There are two workarounds:Ī) Register taglib definitions in web.xmlĮdit web.xml and add the taglib definitions as follows. It uses only WEB-INF/lib and the entries defined in web.xml directly. Freemarker specific settings Taglib definitions (tld)įreeMarker does not search the classpath to find taglib definition. In these same settings, increase both timeout values by a factor of 10. This ensures that the classes are taken from the target directories. Make sure that the option Serve modules without publishing is selected. Setup the Server (Tomcat) Create a Server
Sometimes it is more convenient to checkout a project manually and then use the eclipse import function. Importing an already checked out project from file system click "Check out as Maven project." in the context menu.open "SVN Repository" perspective (Window -> Open perspective).open SVN Repository Exploring Perspective.You will have to register our SVN repository in case you want to checkout magnolia modules/projects Be sure to follow these steps first as else you'll not be able to checkout magnolia properly! Add SVN Repository These are not part of the Indigo bundle for now. The following plugins might come in handy. If you have m2e 1.0 installed you will likely get the following error upon importing a Maven project (i.e. This hits Magnolia with the setproperty Maven plugin and other Maven plugins as well (See list below). Indigo introduces m2e (Maven 2 Eclipse) 1.0, which seems to cause some problems with plugins that are not " known" by m2e. In order to save you some clicks to achieve the same with Git you need to check the following option under Eclipse -> Preferences -> Team -> Git -> Projects If you're used to work with SVN you might find this baffling, as you're accostumed to checkout a project from the central scm repository and see it connected to it, so that changes to your local copy are visually decorated by a special label or icon. The eclipse-indigo-macosx-cocoa-64-egit.zip bundle was created on 10 April 2012 and consists of the following platform, plugins and related versions:īy default cloning a Git repo and then importing it as a Java or Maven project does not show it as "shared", meaning that the Eclipse project looks disconnected from your local Git repo. It can also be found in Product Development/Eclipse folder. There is also preinstalled eclipse for Linux-64b.
If you can access Magnolia's internal network, a preinstalled eclipse for Mac OS X(Cocoa 64) called eclipse-indigo-macosx-cocoa-64-egit.zip can be found at our file server under Product Development/Eclipse Worry not, however, your IDE will work fine nonetheless. There's a bug in Indigo (see also related issue ) which causes Eclipse to show an annoying error message on poms. If you have any problems with Kepler bundle, please report them along w/ solution or workaround here.Those issues were not solved by installing Kepler but only by trashing the workspace and recreating it again. I had some performance issues with Indigo and git reindexing which was the primary reason for making Kepler bundle.
Install Eclipse & Plugins Eclipse Kepler (3.9)Īs of July 9th 2013 Kepler based image is available on file server with same set of plugins as those installed for 3.7 with addition of