Frank Otto wrote:
Thanks, the setting to min-pages works.
I understand the overlay features, but how must I modify in my
jetspeed-mvn-portal-pom.xml? It's my first maven project. I'm developing
netbeans project and svn repository up to now.
The jetspeed-mvn-portal-pom.xml isn't used for building the custom portal war itself, only for what we call "integration" tasks like
database creation/seeding and deployment, not the pure "building" itself.
So, for customizing the war overlay configuration you'll have to modify the
main pom.xml itself.
How can I modify j2-admin and jetspeed-layouts? Is this the same way
with overlay?
If you want to customize j2-admin and jetspeed-layouts, then following a
similar overlay solution would be best practice yes.
For that, you'll have to define your own customized j2-admin or jetspeed-layouts war projects, build (and install) those new artifacts
(wars) yourself and adjust the jetspeed-mvn-portal-pom.xml to deploy these custom wars instead of the standard jetspeed wars.
Regards,
Ate
Ate Douma schrieb:
Frank Otto wrote:
Hi,
I want to build my custom portal with "min"-settings. In 2.1.3 it works.
There is no command:
http://portals.apache.org/jetspeed-2/tutorial/reference/build-commands.html
With current build I get all psml pages from repository. I need only
the main one.
The new maven-2 build is fully customizable and configurable with the
jetspeed provided plugins as well as any standard maven plugin.
The custom portal build uses the jetspeed.war artifact as war overlay
to build your custom portal war and there are several easy ways to
customize the merging of your own psml as well as using the default
provided (demo) full set of psml or minimal set of psml pages.
The jetspeed.war overlay artifact contains the predefined psml in two
separate folders: WEB-INF/pages and WEB-INF/min-pages.
By default (if you don't override or customize anything) everything
from the jetspeed.war overlay, including both these folders, will be
merged in your custom portal war.
For the psml, Jetspeed uses a configuration property (defined in
WEB-INF/conf/jetspeed.properties) where to look for (XML) psml files
to use at runtime:
# default path to (XML) PSML pages root folder
psml.pages.path = ${applicationRoot}/WEB-INF/pages
If you want to use the WEB-INF/min-pages, you can simply merge in your
own WEB-INF/conf/override.properties (better not modify the default
jetspeed.properties) and redefine this property by adding a
src/main/webapp/WEB-INF/conf/override.properties file of your own,
containing:
# custom path to (XML) PSML pages root folder
psml.pages.path = ${applicationRoot}/WEB-INF/min-pages
Adding/merging in your own psml files then is simple too, just add
them to a new src/main/webapp/WEB-INF/min-pages folder.
Alternatively, you can modify your custom portal project/pom.xml and
adjust the maven-war-plugin configuration to include/exclude/rearrange
bits and pieces just how you like it. For reference to using the
maven-war-plugin overlay features, see:
http://maven.apache.org/plugins/maven-war-plugin/overlays.html
HTH,
Ate
kind regards,
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
