Jean-Francois Nadeau wrote:
> I'm playing/learning with Maven to built my Magnolia-webapp (author and
> public instances).
>
> I know how to built an empty webapp or an enterprise webapp.
>
> by changing this:
> <groupId>info.magnolia</groupId><artifactId>magnolia-empty-webapp</artifactId>
>
> to: <groupId>info.magnolia.eebundle</groupId>
> <artifactId>magnolia-enterprise-webapp</artifactId>
>
> I want almost everything from the entreprise bundle but I don't want all the
> demo applications and travel sites. What is the best way to achieve this?
>
> 1-Start from the empty-webapp and add all dependencies. Anyone have a pom.xml
> that does something like that?
>
> 2-Start from the enterprise-webapp and remove some module. How can I do that?
Our project depends on the magnolia-enterprise-bundle-parent POM artifact with
import scope like this:
----
<dependencyManagement>
<dependencies>
<dependency>
<groupId>info.magnolia.eebundle</groupId>
<artifactId>magnolia-enterprise-bundle-parent</artifactId>
<version>${magnolia.version}</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
----
This concept works for the community version as well of course if you pick the
correct community artifact.
After this it's really easy to add dependencies on modules, because you don't
need to specify the version of the module, since Maven can find it via the
imported POM. Adding a dependency to the form module is as easy as this:
----
<dependencies>
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-module-form</artifactId>
</dependency>
</dependencies>
----
Nils.
----------------------------------------------------------------
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: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
