Dashboard > Community Wiki > ... > Developing with Magnolia > Developer information
Developer information Log In View a printable version of the current page.

Added by GrĂ©gory Joseph , last edited by GrĂ©gory Joseph on May 14, 2008  (view change)
Labels: 

Sources

To check all modules' trunks from subversion, execute the following in a shell:

svn co -N http://svn.magnolia.info/svn/modules/community
cd community
./checkout.sh

(checkout.sh is a script that simply checks out all known modules. It is paired with newmodule.sh and svnall.sh

It will be generally expected that you understand the basic principles of Maven and other tools you use.

Creating patches

To create patches just run:
svn diff > your-changes.patch

or if you have changed files you want to disregard:
svn diff changed files > your-changes.patch

If you're attaching this to Jira (which is about the only way you'll get your patch applied anyway), a good idea would be to include the issue id in the filename.

Applying patches:

patch -p 0 < this-change.patch

Links

Subversion (SVN)

Magnolia uses Subversion for source code management. It is similar to CVS, but has better support for refactoring and a better revision system.

Maven

Magnolia is a multi-module project and is built using maven.

JSR 170 - Java Content Repository

JSP

Eclipse

In its previous incarnation on JspWiki, this page was last edited on May 3, 2007 2:18:43 PM by Olli
Other known authors include :

  • AndreasBrenk
  • FerrisNicolaisen
  • BorisKraft
Powered by a free Atlassian Confluence Open Source Project License granted to Magnolia International. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators