Stig,
just import the magnolia war into eclipse as a project, set up an
additional java ee utility project with your code and make the magnolia
project depend on the utility project. Once you have that you can start
development, no need to restart for jsp changes. You can use one of the
smaller modules available as a sample guide on how to structure your
module. Do your configs in magnolia itself, then export the data and
move it to your modules bootstrap folder.
Of course, you can also use maven to create a new module and then build
with maven. Also, the above is just my suggestion, not sure if that is
the intended way one should build a module for magnolia but this has
been working for us here.
Ruben
Stig Lau wrote:
On Jan 20, 2010, at 4:05 PM, Ruben Reusser wrote:
I find JRebel [1] useful to cut down dev time (it deploys your altered classes
without having to restart your web container)
I am aware of JRebel.
However, at the current stage we are developing, we need to deploy both .jsp's, config, compiled classes and the whole shebang.
From what I have understood of the development environment, to develop and test a standalone component, it has to be created in a seperate project and imported via magnolias component handler, or mixed together with the webapp. Am I correct?
-Stig,
Stig Lau wrote:
Hi
I'm currently investigating development of Magnolia modules, for layout and
functionality.
We've looked at the standard bundled Magnolia distribution, the modules list
<http://wiki.magnolia-cms.com/display/WIKI/List+of+Magnolia+Modules> and the
module and webapp archetypes.
Although the design of the modules are attractive, developing and testing
modules requires that they run in context of a Magnolia instance.
With the webapp-archetype and bundled Magnolia, the roundtrip involved from
code has been edited, to magnolia beeing restarted and accepting the module can
take some time.
Do you have a description of how a preferred module development environment
should be configured?
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
