9 Replies Latest reply on Jun 26, 2009 7:57 PM by Nick Belaevski

    unable to build rich:progressBar sample

    Arbi Sookazian Master

      RF 3.3.1.GA

      Please explain what I need to do and why this build is not working out-of-the-box? 4 required artifacts are missing. Is there some other step(s) I need to do before running 'mvn clean install' in this directory?

      thx.

      /********************************************************/

      C:\java\richfaces-ui-3.3.1.GA\samples\progressBarDemo>mvn clean install
      [INFO] Scanning for projects...
      WAGON_VERSION: 1.0-beta-2
      [INFO] ------------------------------------------------------------------------
      [INFO] Building progressBarDemo Maven Webapp
      [INFO] task-segment: [clean, install]
      [INFO] ------------------------------------------------------------------------
      [INFO] [clean:clean]
      [INFO] Deleting directory C:\java\richfaces-ui-3.3.1.GA\samples\progressBarDemo\
      target
      [INFO] [resources:resources]
      [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
      i.e. build is platform dependent!
      [INFO] Copying 0 resource
      Downloading: http://download.java.net/maven/1/org.richfaces.ui/poms/core-3.3.1.G
      A.pom
      Downloading: http://repository.jboss.org/maven2/org/richfaces/ui/core/3.3.1.GA/c
      ore-3.3.1.GA.pom
      Downloading: http://repo1.maven.org/maven2/org/richfaces/ui/core/3.3.1.GA/core-3
      .3.1.GA.pom
      Downloading: http://download.java.net/maven/1/org.richfaces.ui/poms/progressBar-
      3.3.1.GA.pom
      Downloading: http://repository.jboss.org/maven2/org/richfaces/ui/progressBar/3.3
      .1.GA/progressBar-3.3.1.GA.pom
      Downloading: http://repo1.maven.org/maven2/org/richfaces/ui/progressBar/3.3.1.GA
      /progressBar-3.3.1.GA.pom
      Downloading: http://download.java.net/maven/1/org.richfaces.ui/poms/componentCon
      trol-3.3.1.GA.pom
      Downloading: http://repository.jboss.org/maven2/org/richfaces/ui/componentContro
      l/3.3.1.GA/componentControl-3.3.1.GA.pom
      Downloading: http://repo1.maven.org/maven2/org/richfaces/ui/componentControl/3.3
      .1.GA/componentControl-3.3.1.GA.pom
      Downloading: http://download.java.net/maven/1/org.richfaces.samples/poms/skins-3
      .3.1.GA.pom
      Downloading: http://repository.jboss.org/maven2/org/richfaces/samples/skins/3.3.
      1.GA/skins-3.3.1.GA.pom
      Downloading: http://repo1.maven.org/maven2/org/richfaces/samples/skins/3.3.1.GA/
      skins-3.3.1.GA.pom
      Downloading: http://download.java.net/maven/1/org.richfaces.ui/jars/core-3.3.1.G
      A.jar
      Downloading: http://repository.jboss.org/maven2/org/richfaces/ui/core/3.3.1.GA/c
      ore-3.3.1.GA.jar
      Downloading: http://repo1.maven.org/maven2/org/richfaces/ui/core/3.3.1.GA/core-3
      .3.1.GA.jar
      Downloading: http://download.java.net/maven/1/org.richfaces.ui/jars/progressBar-
      3.3.1.GA.jar
      Downloading: http://repository.jboss.org/maven2/org/richfaces/ui/progressBar/3.3
      .1.GA/progressBar-3.3.1.GA.jar
      Downloading: http://repo1.maven.org/maven2/org/richfaces/ui/progressBar/3.3.1.GA
      /progressBar-3.3.1.GA.jar
      Downloading: http://download.java.net/maven/1/org.richfaces.ui/jars/componentCon
      trol-3.3.1.GA.jar
      Downloading: http://repository.jboss.org/maven2/org/richfaces/ui/componentContro
      l/3.3.1.GA/componentControl-3.3.1.GA.jar
      Downloading: http://repo1.maven.org/maven2/org/richfaces/ui/componentControl/3.3
      .1.GA/componentControl-3.3.1.GA.jar
      Downloading: http://download.java.net/maven/1/org.richfaces.samples/jars/skins-3
      .3.1.GA.jar
      Downloading: http://repository.jboss.org/maven2/org/richfaces/samples/skins/3.3.
      1.GA/skins-3.3.1.GA.jar
      Downloading: http://repo1.maven.org/maven2/org/richfaces/samples/skins/3.3.1.GA/
      skins-3.3.1.GA.jar
      [INFO] ------------------------------------------------------------------------
      [ERROR] BUILD ERROR
      [INFO] ------------------------------------------------------------------------
      [INFO] Failed to resolve artifact.

      Missing:
      ----------
      1) org.richfaces.ui:core:jar:3.3.1.GA

      Try downloading the file manually from the project website.

      Then, install it using the command:
      mvn install:install-file -DgroupId=org.richfaces.ui -DartifactId=core -Dve
      rsion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file

      Alternatively, if you host your own repository you can deploy the file there:

      mvn deploy:deploy-file -DgroupId=org.richfaces.ui -DartifactId=core -Dvers
      ion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id
      ]

      Path to dependency:
      1) org.richfaces.samples:progressBarDemo:war:3.3.1.GA
      2) org.richfaces.ui:core:jar:3.3.1.GA

      2) org.richfaces.ui:progressBar:jar:3.3.1.GA

      Try downloading the file manually from the project website.

      Then, install it using the command:
      mvn install:install-file -DgroupId=org.richfaces.ui -DartifactId=progressB
      ar -Dversion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file

      Alternatively, if you host your own repository you can deploy the file there:

      mvn deploy:deploy-file -DgroupId=org.richfaces.ui -DartifactId=progressBar
      -Dversion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drepositor
      yId=[id]

      Path to dependency:
      1) org.richfaces.samples:progressBarDemo:war:3.3.1.GA
      2) org.richfaces.ui:progressBar:jar:3.3.1.GA

      3) org.richfaces.ui:componentControl:jar:3.3.1.GA

      Try downloading the file manually from the project website.

      Then, install it using the command:
      mvn install:install-file -DgroupId=org.richfaces.ui -DartifactId=component
      Control -Dversion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file

      Alternatively, if you host your own repository you can deploy the file there:

      mvn deploy:deploy-file -DgroupId=org.richfaces.ui -DartifactId=componentCo
      ntrol -Dversion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drepo
      sitoryId=[id]

      Path to dependency:
      1) org.richfaces.samples:progressBarDemo:war:3.3.1.GA
      2) org.richfaces.ui:componentControl:jar:3.3.1.GA

      4) org.richfaces.samples:skins:jar:3.3.1.GA

      Try downloading the file manually from the project website.

      Then, install it using the command:
      mvn install:install-file -DgroupId=org.richfaces.samples -DartifactId=skin
      s -Dversion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file

      Alternatively, if you host your own repository you can deploy the file there:

      mvn deploy:deploy-file -DgroupId=org.richfaces.samples -DartifactId=skins
      -Dversion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drepository
      Id=[id]

      Path to dependency:
      1) org.richfaces.samples:progressBarDemo:war:3.3.1.GA
      2) org.richfaces.samples:skins:jar:3.3.1.GA

      ----------
      4 required artifacts are missing.

      for artifact:
      org.richfaces.samples:progressBarDemo:war:3.3.1.GA

      from the specified remote repositories:
      central (http://repo1.maven.org/maven2),
      repository.jboss.org (http://repository.jboss.org/maven2),
      maven-repository.dev.java.net (http://download.java.net/maven/1)



      [INFO] ------------------------------------------------------------------------
      [INFO] For more information, run Maven with the -e switch
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 6 seconds
      [INFO] Finished at: Thu Jun 25 09:15:56 PDT 2009
      [INFO] Final Memory: 10M/18M
      [INFO] ------------------------------------------------------------------------

        • 2. Re: unable to build rich:progressBar sample
          Arbi Sookazian Master

          Same results after I edit settings.xml and run 'mvn clean install'. Am I missing something else? thx.

          4 required artifacts are missing.
          
          for artifact:
           org.richfaces.samples:progressBarDemo:war:3.3.1.GA
          
          from the specified remote repositories:
           central (http://repo1.maven.org/maven2),
           maven2-snapshots.jboss.com (http://snapshots.jboss.org/maven2),
           repository.jboss.com (http://repository.jboss.com/maven2/),
           repository.jboss.org (http://repository.jboss.org/maven2),
           maven-repository.dev.java.net (http://download.java.net/maven/1)
          
          
           at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTra
          nsitively(DefaultArtifactResolver.java:324)
           at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTra
          nsitively(DefaultArtifactResolver.java:288)
           at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDepende
          ncies(DefaultPluginManager.java:1417)
           at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
          nManager.java:407)
           at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
          ultLifecycleExecutor.java:559)
           ... 16 more


          settings.xml:
          <!--
          Licensed to the Apache Software Foundation (ASF) under one
          or more contributor license agreements. See the NOTICE file
          distributed with this work for additional information
          regarding copyright ownership. The ASF licenses this file
          to you under the Apache License, Version 2.0 (the
          "License"); you may not use this file except in compliance
          with the License. You may obtain a copy of the License at
          
           http://www.apache.org/licenses/LICENSE-2.0
          
          Unless required by applicable law or agreed to in writing,
          software distributed under the License is distributed on an
          "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
          KIND, either express or implied. See the License for the
          specific language governing permissions and limitations
          under the License.
          -->
          
          <!--
           | This is the configuration file for Maven. It can be specified at two levels:
           |
           | 1. User Level. This settings.xml file provides configuration for a single user,
           | and is normally provided in $HOME/.m2/settings.xml.
           |
           | NOTE: This location can be overridden with the system property:
           |
           | -Dorg.apache.maven.user-settings=/path/to/user/settings.xml
           |
           | 2. Global Level. This settings.xml file provides configuration for all maven
           | users on a machine (assuming they're all using the same maven
           | installation). It's normally provided in
           | ${maven.home}/conf/settings.xml.
           |
           | NOTE: This location can be overridden with the system property:
           |
           | -Dorg.apache.maven.global-settings=/path/to/global/settings.xml
           |
           | The sections in this sample file are intended to give you a running start at
           | getting the most out of your Maven installation. Where appropriate, the default
           | values (values used when the setting is not specified) are provided.
           |
           |-->
          <settings xmlns="http://maven.apache.org/settings/1.0.0"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
           <!-- localRepository
           | The path to the local repository maven will use to store artifacts.
           |
           | Default: ~/.m2/repository
           <localRepository>/path/to/local/repo</localRepository>
           -->
          
           <!-- interactiveMode
           | This will determine whether maven prompts you when it needs input. If set to false,
           | maven will use a sensible default value, perhaps based on some other setting, for
           | the parameter in question.
           |
           | Default: true
           <interactiveMode>true</interactiveMode>
           -->
          
           <!-- offline
           | Determines whether maven should attempt to connect to the network when executing a build.
           | This will have an effect on artifact downloads, artifact deployment, and others.
           |
           | Default: false
           <offline>false</offline>
           -->
          
           <!-- proxies
           | This is a list of proxies which can be used on this machine to connect to the network.
           | Unless otherwise specified (by system property or command-line switch), the first proxy
           | specification in this list marked as active will be used.
           |-->
           <proxies>
           <!-- proxy
           | Specification for one proxy, to be used in connecting to the network.
           |
           <proxy>
           <id>optional</id>
           <active>true</active>
           <protocol>http</protocol>
           <username>proxyuser</username>
           <password>proxypass</password>
           <host>proxy.host.net</host>
           <port>80</port>
           <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
           </proxy>
           -->
           </proxies>
          
           <!-- servers
           | This is a list of authentication profiles, keyed by the server-id used within the system.
           | Authentication profiles can be used whenever maven must make a connection to a remote server.
           |-->
           <servers>
           <!-- server
           | Specifies the authentication information to use when connecting to a particular server, identified by
           | a unique name within the system (referred to by the 'id' attribute below).
           |
           | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
           | used together.
           |
           <server>
           <id>deploymentRepo</id>
           <username>repouser</username>
           <password>repopwd</password>
           </server>
           -->
          
           <!-- Another sample, using keys to authenticate.
           <server>
           <id>siteServer</id>
           <privateKey>/path/to/private/key</privateKey>
           <passphrase>optional; leave empty if not used.</passphrase>
           </server>
           -->
           </servers>
          
           <!-- mirrors
           | This is a list of mirrors to be used in downloading artifacts from remote repositories.
           |
           | It works like this: a POM may declare a repository to use in resolving certain artifacts.
           | However, this repository may have problems with heavy traffic at times, so people have mirrored
           | it to several places.
           |
           | That repository definition will have a unique id, so we can create a mirror reference for that
           | repository, to be used as an alternate download site. The mirror site will be the preferred
           | server for that repository.
           |-->
           <mirrors>
           <!-- mirror
           | Specifies a repository mirror site to use instead of a given repository. The repository that
           | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
           | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
           |
           <mirror>
           <id>mirrorId</id>
           <mirrorOf>repositoryId</mirrorOf>
           <name>Human Readable Name for this Mirror.</name>
           <url>http://my.repository.com/repo/path</url>
           </mirror>
           -->
           </mirrors>
          
           <!-- profiles
           | This is a list of profiles which can be activated in a variety of ways, and which can modify
           | the build process. Profiles provided in the settings.xml are intended to provide local machine-
           | specific paths and repository locations which allow the build to work in the local environment.
           |
           | For example, if you have an integration testing plugin - like cactus - that needs to know where
           | your Tomcat instance is installed, you can provide a variable here such that the variable is
           | dereferenced during the build process to configure the cactus plugin.
           |
           | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
           | section of this document (settings.xml) - will be discussed later. Another way essentially
           | relies on the detection of a system property, either matching a particular value for the property,
           | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
           | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
           | Finally, the list of active profiles can be specified directly from the command line.
           |
           | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
           | repositories, plugin repositories, and free-form properties to be used as configuration
           | variables for plugins in the POM.
           |
           |-->
           <profiles>
           <profile>
           <id>RichFaces</id>
           <repositories>
           <repository>
           <releases>
           <enabled>true</enabled>
           </releases>
           <snapshots>
           <enabled>false</enabled>
           <updatePolicy>never</updatePolicy>
           </snapshots>
           <id>repository.jboss.com</id>
           <name>Jboss Repository for Maven</name>
           <url>
           http://repository.jboss.com/maven2/
           </url>
           <layout>default</layout>
           </repository>
           <repository>
           <releases>
           <enabled>false</enabled>
           </releases>
           <snapshots>
           <enabled>true</enabled>
           <updatePolicy>always</updatePolicy>
           </snapshots>
           <id>maven2-snapshots.jboss.com</id>
           <name>Jboss Repository for Maven Snapshots</name>
           <url>http://snapshots.jboss.org/maven2</url>
           <layout>default</layout>
           </repository>
           </repositories>
           <pluginRepositories>
           <pluginRepository>
           <id>maven2-snapshots.jboss.com</id>
           <name>Jboss Repository for Maven Snapshots</name>
           <url>http://snapshots.jboss.org/maven2</url>
           <releases>
           <enabled>false</enabled>
           </releases>
           <snapshots>
           <enabled>true</enabled>
           <updatePolicy>always</updatePolicy>
           </snapshots>
           </pluginRepository>
           <pluginRepository>
           <releases>
           <enabled>true</enabled>
           </releases>
           <snapshots>
           <enabled>false</enabled>
           <updatePolicy>never</updatePolicy>
           </snapshots>
           <id>repository.jboss.com</id>
           <name>Jboss Repository for Maven</name>
           <url>
           http://repository.jboss.com/maven2/
           </url>
           <layout>default</layout>
           </pluginRepository>
           </pluginRepositories>
           </profile>
          
           <!-- profile
           | Specifies a set of introductions to the build process, to be activated using one or more of the
           | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
           | or the command line, profiles have to have an ID that is unique.
           |
           | An encouraged best practice for profile identification is to use a consistent naming convention
           | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
           | This will make it more intuitive to understand what the set of introduced profiles is attempting
           | to accomplish, particularly when you only have a list of profile id's for debug.
           |
           | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
           <profile>
           <id>jdk-1.4</id>
          
           <activation>
           <jdk>1.4</jdk>
           </activation>
          
           <repositories>
           <repository>
           <id>jdk14</id>
           <name>Repository for JDK 1.4 builds</name>
           <url>http://www.myhost.com/maven/jdk14</url>
           <layout>default</layout>
           <snapshotPolicy>always</snapshotPolicy>
           </repository>
           </repositories>
           </profile>
           -->
          
           <!--
           | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
           | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
           | might hypothetically look like:
           |
           | ...
           | <plugin>
           | <groupId>org.myco.myplugins</groupId>
           | <artifactId>myplugin</artifactId>
           |
           | <configuration>
           | <tomcatLocation>${tomcatPath}</tomcatLocation>
           | </configuration>
           | </plugin>
           | ...
           |
           | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
           | anything, you could just leave off the <value/> inside the activation-property.
           |
           <profile>
           <id>env-dev</id>
          
           <activation>
           <property>
           <name>target-env</name>
           <value>dev</value>
           </property>
           </activation>
          
           <properties>
           <tomcatPath>/path/to/tomcat/instance</tomcatPath>
           </properties>
           </profile>
           -->
           </profiles>
          
           <!-- activeProfiles
           | List of profiles that are active for all builds.
           | -->
           <activeProfiles>
           <activeProfile>RichFaces</activeProfile>
           </activeProfiles>
          
          </settings>
          


          • 3. Re: unable to build rich:progressBar sample
            Nick Belaevski Master

            Try building "ui" folder first.

            • 4. Re: unable to build rich:progressBar sample
              Arbi Sookazian Master

              so I did a 'mvn clean install' in ui folder (successful). then 'mvn clean install' for progressBarDemo, results:

              C:\java\richfaces-ui-3.3.1.GA\samples\progressBarDemo>mvn clean install
              [INFO] Scanning for projects...
              WAGON_VERSION: 1.0-beta-2
              [INFO] ------------------------------------------------------------------------
              [INFO] Building progressBarDemo Maven Webapp
              [INFO] task-segment: [clean, install]
              [INFO] ------------------------------------------------------------------------
              [INFO] [clean:clean]
              [INFO] Deleting directory C:\java\richfaces-ui-3.3.1.GA\samples\progressBarDemo\
              target
              [INFO] [resources:resources]
              [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
              i.e. build is platform dependent!
              [INFO] Copying 0 resource
              Downloading: http://repository.jboss.com/maven2//org/richfaces/samples/skins/3.3
              .1.GA/skins-3.3.1.GA.pom
              Downloading: http://download.java.net/maven/1/org.richfaces.samples/poms/skins-3
              .3.1.GA.pom
              Downloading: http://repository.jboss.org/maven2/org/richfaces/samples/skins/3.3.
              1.GA/skins-3.3.1.GA.pom
              Downloading: http://repo1.maven.org/maven2/org/richfaces/samples/skins/3.3.1.GA/
              skins-3.3.1.GA.pom
              Downloading: http://repository.jboss.com/maven2//org/richfaces/samples/skins/3.3
              .1.GA/skins-3.3.1.GA.jar
              Downloading: http://download.java.net/maven/1/org.richfaces.samples/jars/skins-3
              .3.1.GA.jar
              Downloading: http://repository.jboss.org/maven2/org/richfaces/samples/skins/3.3.
              1.GA/skins-3.3.1.GA.jar
              Downloading: http://repo1.maven.org/maven2/org/richfaces/samples/skins/3.3.1.GA/
              skins-3.3.1.GA.jar
              [INFO] ------------------------------------------------------------------------
              [ERROR] BUILD ERROR
              [INFO] ------------------------------------------------------------------------
              [INFO] Failed to resolve artifact.
              
              Missing:
              ----------
              1) org.richfaces.samples:skins:jar:3.3.1.GA
              
               Try downloading the file manually from the project website.
              
               Then, install it using the command:
               mvn install:install-file -DgroupId=org.richfaces.samples -DartifactId=skin
              s -Dversion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file
              
               Alternatively, if you host your own repository you can deploy the file there:
              
               mvn deploy:deploy-file -DgroupId=org.richfaces.samples -DartifactId=skins
              -Dversion=3.3.1.GA -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drepository
              Id=[id]
              
               Path to dependency:
               1) org.richfaces.samples:progressBarDemo:war:3.3.1.GA
               2) org.richfaces.samples:skins:jar:3.3.1.GA
              
              ----------
              1 required artifact is missing.
              
              for artifact:
               org.richfaces.samples:progressBarDemo:war:3.3.1.GA
              
              from the specified remote repositories:
               central (http://repo1.maven.org/maven2),
               maven2-snapshots.jboss.com (http://snapshots.jboss.org/maven2),
               repository.jboss.com (http://repository.jboss.com/maven2/),
               repository.jboss.org (http://repository.jboss.org/maven2),
               maven-repository.dev.java.net (http://download.java.net/maven/1)
              
              
              
              [INFO] ------------------------------------------------------------------------
              [INFO] For more information, run Maven with the -e switch
              [INFO] ------------------------------------------------------------------------
              [INFO] Total time: 5 seconds
              [INFO] Finished at: Fri Jun 26 12:58:21 PDT 2009
              [INFO] Final Memory: 10M/17M
              [INFO] ------------------------------------------------------------------------


              • 5. Re: unable to build rich:progressBar sample
                Nick Belaevski Master

                Well, one more step to go: "mvn clean install" for samples\skins project

                • 6. Re: unable to build rich:progressBar sample
                  Arbi Sookazian Master

                  Ok, the build (target folder and contents, WAR, etc.) for progressBar is successful after building skins as well. thx.

                  • 7. Re: unable to build rich:progressBar sample
                    Arbi Sookazian Master

                    deployment of WAR was unsuccessful:

                    2009-06-26 15:56:12,961 ERROR [javax.enterprise.resource.webcontainer.jsf.application] JSF1029: The specified InjectionProvider implementation 'org.jboss.web.jsf.integration.injection.JBossInjectionProvider' does not implement the InjectionProvider interface.
                    
                    2009-06-26 15:56:13,273 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] ConfigureListener.contextInitialized(/progressBarDemo)
                    2009-06-26 15:56:13,273 ERROR [org.apache.catalina.core.ContainerBase] Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
                    java.lang.ClassCastException: com.sun.faces.config.WebConfiguration
                    
                    2009-06-26 15:56:13,273 ERROR [org.apache.catalina.core.StandardContext] Error listenerStart
                    2009-06-26 15:56:13,273 ERROR [org.apache.catalina.core.StandardContext] Context [/progressBarDemo] startup failed due to previous errors
                    2009-06-26 15:56:13,273 ERROR [org.apache.catalina.core.ContainerBase] Exception sending context destroyed event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
                    java.lang.ClassCastException: com.sun.faces.application.ApplicationAssociate
                    
                    


                    • 8. Re: unable to build rich:progressBar sample
                      Arbi Sookazian Master

                      AS version:

                      15:55:39,460 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA_CP02 (build: SVNTag=JBPAPP_4_3_0_GA_CP02 date=200808051050)


                      • 9. Re: unable to build rich:progressBar sample
                        Nick Belaevski Master

                        You should remove JSF to run this example on JBoss AS. BTW, the easiest way to run it, is "mvn clean jetty:run"