ICEfaces
  1. ICEfaces
  2. ICE-5387

Update ICEfaces-1.8 maven2 poms

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Invalid
          • Affects Version/s: 1.8.2a
          • Fix Version/s: None
          • Component/s: Release
          • Labels:
            None
          • Environment:
            For icefaces 1.8.2

            Description

            Complete maven2 dependecies.
            Attached files are extended versions of files from http://anonsvn.icefaces.org/repo/maven2/
            Features
            - library dependecies
            - configurations by jdk
            - some additional parametrization
            - some plugin configurations.

            This package does'nt allow for Icefaces sources compilation but maven javadoc:javadoc can be done

            Additional comment
            - jsf version are selected by jdk
            - backport-util-concurrent are configured by jdk, it is not necessary but can improve performace
            - copy of some libraries necessary for local repostiory can be found at http://krokodylowy3.webpark.pl/maven/m2/repository
            - component library need both jsf 1.1 and 1.2 library on path so a little hack was done , local copy of jsf-1.1 library must be kept in local site
            like here
                  <dependency>
                      <groupId>org.icefaces</groupId>
                      <artifactId>jsf-api</artifactId>
                      <version>${jsf1.1-version}</version>
                      <scope>provided</scope>
                    </dependency>
            (above hack was'nt be necessaery up to 06.2009, at this time some changes in menu component was done)


              Activity

              Descending order - Click to sort in ascending order
              Hide
              Permalink
              Krashan Brahmanjara added a comment -

              Of course these poms looks too complex and can be simplier but they are effect of two years improvements for few environments.
              Some solutions are based on complex hibernate-parent.pom. It is good example of detailed configuratiion.

              Attached poms can be used both as compilation dependencies for Icefaces sources and runtime dependencies for target applications.
              Compilation / runtime dependecies are defined by <scope>. There is no reason to keep them separately - informatioin about compilation dependecies can be usable for developers.

              Configurations selected by jdk are effects of some compilation problems with original src/lib folder and some problems with runtime configurations.

              Show
              Krashan Brahmanjara added a comment - Of course these poms looks too complex and can be simplier but they are effect of two years improvements for few environments. Some solutions are based on complex hibernate-parent.pom. It is good example of detailed configuratiion. Attached poms can be used both as compilation dependencies for Icefaces sources and runtime dependencies for target applications. Compilation / runtime dependecies are defined by <scope>. There is no reason to keep them separately - informatioin about compilation dependecies can be usable for developers. Configurations selected by jdk are effects of some compilation problems with original src/lib folder and some problems with runtime configurations.
              Hide
              Permalink
              Ken Fyten added a comment -

              Although there are a lot of good ideas in these poms, we have to remember that these poms are strictly defined for run-time dependencies only, as we do not require Maven for building ICEfaces itself. Considering that we support a wide matrix of application servers, we have to ensure that all the ICEfaces poms fit each of these supported servers. To say that we can use a particular JDK to determine the dependencies is not always correct. Most of these application servers have a minimum JDK that is required for that particular server. The version of jsf can be irrelevant to the particular JDK in this instance. Our base icefaces, icefaces-facelets, icefaces-comps jars must be able to be used with all variations, all supported application servers & their recommended JDK's.

              The actual poms for building applications based on these options are where the complexities/dependencies should be kept. If you would like to help implement some sample poms (or even help with creating some archetypes referred to in jira ICE-5324) with the various options for run-time, this might be the best fit for these types of poms in the project. For example the portlet-api jar is not a run-time dependency for all ICEfaces builds. Neither is a war packaging. Only the common run-time dependencies should be kept within our base poms,

              Ultimately, these are poms that might be useful to some members of the community, but are not general enough to be part of the
              ICEfaces distribution.

              Closing this JIRA as Invalid.

              Show
              Ken Fyten added a comment - Although there are a lot of good ideas in these poms, we have to remember that these poms are strictly defined for run-time dependencies only, as we do not require Maven for building ICEfaces itself. Considering that we support a wide matrix of application servers, we have to ensure that all the ICEfaces poms fit each of these supported servers. To say that we can use a particular JDK to determine the dependencies is not always correct. Most of these application servers have a minimum JDK that is required for that particular server. The version of jsf can be irrelevant to the particular JDK in this instance. Our base icefaces, icefaces-facelets, icefaces-comps jars must be able to be used with all variations, all supported application servers & their recommended JDK's. The actual poms for building applications based on these options are where the complexities/dependencies should be kept. If you would like to help implement some sample poms (or even help with creating some archetypes referred to in jira ICE-5324 ) with the various options for run-time, this might be the best fit for these types of poms in the project. For example the portlet-api jar is not a run-time dependency for all ICEfaces builds. Neither is a war packaging. Only the common run-time dependencies should be kept within our base poms, Ultimately, these are poms that might be useful to some members of the community, but are not general enough to be part of the ICEfaces distribution. Closing this JIRA as Invalid.
              Hide
              Permalink
              Krashan Brahmanjara added a comment -

              Update of maven configurations

              Show
              Krashan Brahmanjara added a comment - Update of maven configurations

                People

                • Assignee:
                  Ken Fyten
                  Reporter:
                  Krashan Brahmanjara
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: