Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.1, EE-2.0.0.GA
-
Fix Version/s: 3.1
-
Component/s: Sample Apps
-
Labels:None
-
Environment:ICEfaces 2 build
Description
We support both Ant and Maven 2 builds of our sample applications. However, depending on how the build is done, artifacts from one strategy can interfere with the other. For example, in the portlet examples, if you build with Ant and then build with Maven, the actions of the Ant build can cause Maven to fail or to generate a .war file that isn't correct.
Specifically, the portlet builds rely on getting src code and other files from the non-portlet versions of the samples and this can have an effect if the build mechanisms are mixed without "cleaning" in between. So the best thing would be to ensure that a "clean" is done in advance of using either build strategy.
Specifically, the portlet builds rely on getting src code and other files from the non-portlet versions of the samples and this can have an effect if the build mechanisms are mixed without "cleaning" in between. So the best thing would be to ensure that a "clean" is done in advance of using either build strategy.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The Maven builds will now call the Ant "clean" target to ensure there are no "duplicated class" issues. Resolving as fixed.