Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha2
-
Fix Version/s: 2.0-Alpha3, 2.0.0
-
Component/s: Sample Apps
-
Labels:None
-
Environment:maven2, ICEfaces-2
Description
-
Hide
- maven.zip
- 35 kB
- Krashan Brahmanjara
-
- maven/component/pom.xml 4 kB
- maven/component-metadata/pom.xml 4 kB
- maven/core/pom.xml 6 kB
- maven/facelets/pom.xml 3 kB
- maven/just-ice/pom.xml 3 kB
- maven/pom.xml 17 kB
- maven/push-server/pom.xml 1 kB
- maven/samples/address-demo/pom.xml 3 kB
- maven/samples/auctionMonitor/pom.xml 3 kB
- maven/samples/.../facelets/pom.xml 4 kB
- maven/samples/.../facelets-enh/pom.xml 4 kB
- maven/samples/.../jsp/pom.xml 4 kB
- maven/samples/.../portlets/pom.xml 4 kB
- maven/samples/portlet/chat/pom.xml 3 kB
- maven/samples/portlet/location/pom.xml 3 kB
- maven/samples/tutorial/dragdrop1/pom.xml 3 kB
- maven/samples/tutorial/dragdrop2/pom.xml 3 kB
- maven/samples/.../easyajaxpush/pom.xml 3 kB
- maven/samples/tutorial/effects1/pom.xml 3 kB
- maven/samples/tutorial/effects2/pom.xml 3 kB
- maven/samples/tutorial/tiles/pom.xml 3 kB
- maven/samples/tutorial/timezone1/pom.xml 3 kB
- maven/samples/tutorial/timezone2/pom.xml 3 kB
- maven/samples/tutorial/timezone3/pom.xml 3 kB
- maven/samples/tutorial/timezone4/pom.xml 3 kB
- maven/samples/tutorial/timezone5/pom.xml 3 kB
- maven/samples/tutorial/timezone6/pom.xml 3 kB
- maven/samples/tutorial/timezone7/pom.xml 3 kB
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
True. My configurations are for Icefaces 1.8.2 but can be extended for icefaces 2 too.
I saw that http://anonsvn.icefaces.org/repo/maven2/ are basic and not complete.
Configuration update for Icefaces 1.8.2 was registered at ICE-5387 and sent as contribution.
Sorry...should word last comment better. Are you examples for ICEfaces-2.0? This jira is for maven support of that particular version. We could open another one if you want to contribute for other releases.
Is this for ICEfaces-2.0?? We also have a jira open for maven archetypes if you want to contribute for that:-
http://jira.icefaces.org/browse/ICE-5324
I would like to share& contribute some maven configurations for Icefaces sources from our development environment.
This configuration contain full library dependecies, configurations by jdk, some parametrization and some plugi configurations.
This package does'nt allow for Icefaces sources compilation but maven javadoc:javadoc can be done.
I suppose it will be usable to complete your final maven configurations
auction example does not follow standard maven configuration for source files. For example, readme.html is a resource and with the ant script is currently located with the source files in WEB-INF/classes/org/icefaces.... however, with maven, this file and the auction.properties files that are combined with the java class files are separated into WEB-INF/classes/resources/org.icefaces.... as path.
I ended up having to use the maven-antrun-plugin which copies it over to the correct location in the build directory during phase "process-resources". Ideally, we would leave these types of files in sample apps in the /resources/ designated path for the build directory and then the maven builds wouldnt' be so tricky.
revised location for snapshot repository for everyone to ensure annoymous user access:-
looking to setup snapshot repository on anonymous svn repository for access to all users. This one will not be involved in the automatic update to ibiblio but will contain ICEfaces-2.0.0-A2 release and any future alpha, beta or candidate releases.
location at svn/repo/tools/maven/trunk/snapshots
example of how to use profile for tomcat6 would be "mvn package -P tomcat6" default is glassfish3
May rename these targets as the real difference is enterprise server (has jsf2 jars) and se server (no jsf jars).
rev 20424 excludes .svn files properly. Also have pom for auctionMonitor for tomcat6 and glassfish3(default).
rev 20420 has 2 profiles (default is glassfish3, other is tomcat6). For some reason on windows machine only (same pom, etc), the .svn files are being included in the packaged war. --have tried many things to exclude them.
QA has tested so complete