becoming involved with the richFaces/a4j project| JBoss.org Content Archive (Read Only)

1. Re: becoming involved with the richFaces/a4j project

jbalunas Feb 26, 2009 9:47 AM (in response to zmarrapese)

Hi Zack,

We are always looking for motivated developers and users to help out :-)

My advice would be to find a jira or two that excite you dig in. Or if you have a new idea post the idea here and we can all discuss it. This will help focus your attention on specific areas so you can get up to speed.

If you have a jira user name already great - if not make one, but before just assigning an issue to you post your thoughts so no one duplicates effort.

Then create a patch and post it. We'll review and apply it. After some interactions like this and interest we can discuss commit rights, etc....

Good to hear from you,
Jay

2. Re: becoming involved with the richFaces/a4j project

fmarwede Mar 1, 2009 5:56 PM (in response to zmarrapese)

Hi all,
generally I'm interested in developing, too. I worked for a company using Richfaces, so I've done a lot of testing in the last two years. But in the next months I'll have time to do something I'm really interested in. And this is understanding (and maybe fighting against) some bugs I found ;-)

But at the beginning I really have a beginner question. I'm skilled in using Eclipse and in using SVN but I'm new to Maven.

I read

http://www.jboss.org/community/docs/DOC-9919

and

http://www.jboss.org/community/docs/DOC-9930

and I installed the Maven integration for Eclipse, checked out the svn trunk repository of Richfaces and I tried to modify the setting file as described. But I got some errors looking like simple xml stuff -tag not closed. I couldn't solve this, the file looks okay.

My question: When you read this, what I could have forgotten, or is there a step by step description for eclipse users?

Thank you!

3. Re: becoming involved with the richFaces/a4j project

nbelaevski Mar 2, 2009 2:36 PM (in response to zmarrapese)

Hello,

Here is default settings.xml with added profiles for your convenience:

<!--
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>
 <!-- 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
 | 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>
 -->
 <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>
 </profiles>

 <!-- activeProfiles
 | List of profiles that are active for all builds.
 |
 <activeProfiles>
 <activeProfile>alwaysActiveProfile</activeProfile>
 <activeProfile>anotherAlwaysActiveProfile</activeProfile>
 </activeProfiles>
 -->
 <activeProfiles>
 <activeProfile>RichFaces</activeProfile>
 </activeProfiles>
</settings>

How we use Eclipse:

1. Add workspace classpath variable for Maven repository:

mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo

(http://maven.apache.org/guides/mini/guide-ide-eclipse.html)

2. Build project using mvn install
3. Run

mvn eclipse:clean eclipse:eclipse -Dwtpversion=2.0 -DdownloadSources=true

from the project root. This will create Eclipse service files (.project, .classpath & .settings).
Note: this command creates Eclipse projects for dependent modules only for the case when all dependent modules are in execution scope (when ran from project root). In contrast, running it from the root of separate project (e.g. ui\tree) will create dependencies to repository .jar files. What does that mean practically? ui\tree depends ui\drag-drop module. If you changed something in ui\drag-drop and want to see these changes in "tree" project imported into Eclipse, you'll have to do

mvn clean install

for ui\drag-drop (that will build and install new version of this module to local Maven repository) and then refresh "tree" project.

Form (.jar or workspace project) of the dependencies used can be changed in any time, just edit build path (either set dependency to repository .jar file or workspace project). For web projects also setup checkboxes for dependencies at "Jave EE dependencies" tab in project properties.

It is handy to have infrequently modified modules (like framework projects) imported as .jar dependencies and one or two modules you constantly work on, as workspace projects. To achieve that, generate project descriptors just for the developer example project and then change dependencies to the required workspace projects as described above.

4. Import projects (the ones you wish to work on together with all dependent projects) into Eclipse using Import -> Existing projects. Make sure there are no classpath build errors (shown in "Problems" view).

This plugin: http://m2eclipse.codehaus.org/ is handy for running Maven commands just inside Eclipse, however I constantly get various issues when I use it for dependency management, so I won't recommend to enable this feature.

Please let me know if you have any questions/some additional guidance is necessary.

4. Re: becoming involved with the richFaces/a4j project

fmarwede Mar 3, 2009 1:54 AM (in response to zmarrapese)

Thank you for these detailed instructions! However, I got a problem with point 2: I have Java Heap Space problems, although I set it to 1024 (in eclipse.ini). Here my detailed approach:

1. I used SVN-Client of Eclipse to checkout the Richfaces trunk.
2. I replace the setting.xml with the one you posted.
3. I set workspace classpath variable in Eclipse (your step 1)
4. I used http://m2eclipse.codehaus.org/ for your step 2: Right click on project, run, maven install. Here what I got on console:

[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Jboss RichFaces project
[INFO] JSF Components Development kit
[INFO] Java Server Faces component generator
[INFO] Maven plugin for JSF components code generation
[INFO] YUI Compressor Maven Mojo
[INFO] Archetype - maven-archetype-jsf-component
[INFO] Archetype for jsf webapp project
[INFO] Archetype - maven-archetype-plug-n-skin
[INFO] maven-resource-dependency-plugin
[INFO] Java Server Faces AJAX framework
[INFO] Java Server Faces AJAX framework API
[INFO] Java Server Faces AJAX framework implementation
[INFO] Ajax4Jsf test framework
[INFO] jsf-test
[INFO] RichFaces Components
[INFO] Java Server Faces AJAX framework
[INFO] Drag and Drop
[INFO] Effect
[INFO] Panel
[INFO] Panel Bar
[INFO] Data Filter Slider
[INFO] Google map component
[INFO] jQuery Selectors
[INFO] Virtual Earth
[INFO] Separator components
[INFO] Spacer
[INFO] Paint java 2D
[INFO] Toggle panel
[INFO] Tab panel
[INFO] Toggle panel
[INFO] Tool bar
[INFO] Input number slider
[INFO] Input number spinner
[INFO] Tree control
[INFO] Suggestion box
[INFO] Extended data table and lists
[INFO] Modal panel
[INFO] Data Scroller
[INFO] Menu components
[INFO] Drop down menu
[INFO] tooltip
[INFO] Panel menu
[INFO] Calendar
[INFO] Tree Model
[INFO] Message
[INFO] Scrollable Data Table
[INFO] insert
[INFO] componentControl
[INFO] orderingList
[INFO] listShuttle
[INFO] contextMenu
[INFO] columns
[INFO] combobox
[INFO] pickList
[INFO] progressBar
[INFO] fileUpload
[INFO] inplaceInput
[INFO] inplaceSelect
[INFO] functions
[INFO] hotKey
[INFO] beanValidator
[INFO] state
[INFO] extendedDataTable
[INFO] Editor
[INFO] Richfaces extensions for a different environments
[INFO] Project documentation
[INFO] RichFaces JSF components library
[INFO] RichFaces Components Examples
[INFO] skins
[INFO] Laguna Add-On Skin
[INFO] glassX
[INFO] darkX
[INFO] richfaces-demo Maven Webapp
[INFO] ----------------------------------------------------------------------------
[INFO] Building Jboss RichFaces project
[INFO] task-segment: [install]
[INFO] ----------------------------------------------------------------------------
[INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from repository.jboss.com
WAGON_VERSION: 1.0-beta-2
[INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from atlassian-m2-repository
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for updates from repository.jboss.com
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for updates from atlassian-m2-repository
[INFO] site:attach-descriptor
[INFO] install:install
[INFO] Installing C:\workspace\Richfaces trunk\pom.xml to C:\Dokumente und Einstellungen\Florian\.m2\repository\org\richfaces\root\3.3.1-SNAPSHOT\root-3.3.1-SNAPSHOT.pom
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL org.richfaces:root:pom:3.3.1-SNAPSHOT ( task-segment: [install] )
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 5 second
[INFO] Finished at: Tue Mar 03 07:43:19 CET 2009
[INFO] Memory 10M/25M
[INFO] ----------------------------------------------------------------------------
[INFO] ----------------------------------------------------------------------------
[INFO] Building JSF Components Development kit
[INFO] task-segment: [install]
[INFO] ----------------------------------------------------------------------------
[INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from repository.jboss.com
[INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from atlassian-m2-repository
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for updates from repository.jboss.com
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for updates from atlassian-m2-repository
[INFO] site:attach-descriptor
[INFO] install:install
[INFO] Installing C:\workspace\Richfaces trunk\cdk\pom.xml to C:\Dokumente und Einstellungen\Florian\.m2\repository\org\richfaces\cdk\3.3.1-SNAPSHOT\cdk-3.3.1-SNAPSHOT.pom
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL org.richfaces:cdk:pom:3.3.1-SNAPSHOT ( task-segment: [install] )
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 2 second
[INFO] Finished at: Tue Mar 03 07:43:22 CET 2009
[INFO] Memory 7M/25M
[INFO] ----------------------------------------------------------------------------
[INFO] ----------------------------------------------------------------------------
[INFO] Building Java Server Faces component generator
[INFO] task-segment: [install]
[INFO] ----------------------------------------------------------------------------
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for updates from repository.jboss.com
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for updates from atlassian-m2-repository
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for updates from repository.jboss.com
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for updates from atlassian-m2-repository
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking for updates from repository.jboss.com
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking for updates from atlassian-m2-repository
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for updates from repository.jboss.com
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for updates from atlassian-m2-repository
[INFO] resources:resources
[WARN] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 165 resources
[WARN] While downloading com.wutka:dtdparser:1.21
 This artifact has been relocated to com.wutka:dtdparser:1.21.


attempting to create parent directories for destination: commons-collections-2.1.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//commons-collections/commons-collections/2.1/commons-collections-2.1.jar
..........................................................
[INFO] compiler:compile
Compiling 166 source files to C:\workspace\Richfaces trunk\cdk\generator\target\classes
[INFO] resources:testResources
[WARN] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\workspace\Richfaces trunk\cdk\generator\src\test\resources
[INFO] compiler:testCompile
Compiling 12 source files to C:\workspace\Richfaces trunk\cdk\generator\target\test-classes
[INFO] surefire:test
attempting to create parent directories for destination: surefire-junit-2.4.3.pom.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/apache/maven/surefire/surefire-junit/2.4.3/surefire-junit-2.4.3.pom
.
attempting to create parent directories for destination: surefire-providers-2.4.3.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-providers/2.4.3/surefire-providers-2.4.3.pom
.
attempting to create parent directories for destination: surefire-junit-2.4.3.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/apache/maven/surefire/surefire-junit/2.4.3/surefire-junit-2.4.3.jar
.....
[INFO] Surefire report directory: C:\workspace\Richfaces trunk\cdk\generator\target\surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.ajax4jsf.builder.xml.XPathComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.782 sec
Running org.ajax4jsf.builder.generator.ClassPatternSetTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.ajax4jsf.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.ajax4jsf.builder.generator.AbstractClassStubBuilderTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.234 sec
Running org.ajax4jsf.builder.xml.XMLBodySerializerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.063 sec
Running org.ajax4jsf.builder.xml.XMLBodyTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.093 sec
Running org.ajax4jsf.builder.xml.XMLBodyMergeTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.ajax4jsf.builder.config.ClassWalkingLogicTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec

Results :

Tests run: 27, Failures: 0, Errors: 0, Skipped: 0

[INFO] jar:jar
[INFO] Building jar: C:\workspace\Richfaces trunk\cdk\generator\target\generator-3.3.1-SNAPSHOT.jar
[INFO] install:install
[INFO] Installing C:\workspace\Richfaces trunk\cdk\generator\target\generator-3.3.1-SNAPSHOT.jar to C:\Dokumente und Einstellungen\Florian\.m2\repository\org\richfaces\cdk\generator\3.3.1-SNAPSHOT\generator-3.3.1-SNAPSHOT.jar
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL org.richfaces.cdk:generator:jar:3.3.1-SNAPSHOT ( task-segment: [install] )
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 23 second
[INFO] Finished at: Tue Mar 03 07:43:45 CET 2009
[INFO] Memory 16M/63M
[INFO] ----------------------------------------------------------------------------
[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven plugin for JSF components code generation
[INFO] task-segment: [install]
[INFO] ----------------------------------------------------------------------------
attempting to create parent directories for destination: modello-maven-plugin-1.0-alpha-18.pom.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/codehaus/modello/modello-maven-plugin/1.0-alpha-18/modello-maven-plugin-1.0-alpha-18.pom
..
attempting to create parent directories for destination: modello-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello/1.0-alpha-18/modello-1.0-alpha-18.pom
...
attempting to create parent directories for destination: modello-maven-plugin-1.0-alpha-18.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/codehaus/modello/modello-maven-plugin/1.0-alpha-18/modello-maven-plugin-1.0-alpha-18.jar
......
attempting to create parent directories for destination: modello-plugin-xdoc-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-xdoc/1.0-alpha-18/modello-plugin-xdoc-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-plugins-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugins/1.0-alpha-18/modello-plugins-1.0-alpha-18.pom
.
attempting to create parent directories for destination: plexus-classworlds-1.2-alpha-9.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-classworlds/1.2-alpha-9/plexus-classworlds-1.2-alpha-9.pom
.
attempting to create parent directories for destination: modello-core-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-core/1.0-alpha-18/modello-core-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-plugin-xml-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-xml/1.0-alpha-18/modello-plugin-xml-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-plugin-plexus-registry-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-plexus-registry/1.0-alpha-18/modello-plugin-plexus-registry-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-plugin-store-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-store/1.0-alpha-18/modello-plugin-store-1.0-alpha-18.pom
.
attempting to create parent directories for destination: plexus-velocity-1.1.4.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.4/plexus-velocity-1.1.4.pom
.
attempting to create parent directories for destination: plexus-components-1.1.8.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.8/plexus-components-1.1.8.pom
.
attempting to create parent directories for destination: plexus-1.0.9.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.9/plexus-1.0.9.pom
..
attempting to create parent directories for destination: modello-plugin-xsd-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-xsd/1.0-alpha-18/modello-plugin-xsd-1.0-alpha-18.pom
.
attempting to create parent directories for destination: maven-plugin-api-2.0.7.pom.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/apache/maven/maven-plugin-api/2.0.7/maven-plugin-api-2.0.7.pom
..
attempting to create parent directories for destination: modello-plugin-jdom-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-jdom/1.0-alpha-18/modello-plugin-jdom-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-plugin-jpox-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-jpox/1.0-alpha-18/modello-plugin-jpox-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-db-keywords-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-db-keywords/1.0-alpha-18/modello-db-keywords-1.0-alpha-18.pom
.
attempting to create parent directories for destination: saxpath-1.0-FCS.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/saxpath/saxpath/1.0-FCS/saxpath-1.0-FCS.pom
.
attempting to create parent directories for destination: modello-plugin-converters-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-converters/1.0-alpha-18/modello-plugin-converters-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-plugin-stax-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-stax/1.0-alpha-18/modello-plugin-stax-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-plugin-xpp3-1.0-alpha-18.pom.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-xpp3/1.0-alpha-18/modello-plugin-xpp3-1.0-alpha-18.pom
.
attempting to create parent directories for destination: modello-plugin-xdoc-1.0-alpha-18.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/codehaus/modello/modello-plugin-xdoc/1.0-alpha-18/modello-plugin-xdoc-1.0-alpha-18.jar
..
attempting to create parent directories for destination: modello-core-1.0-alpha-18.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/codehaus/modello/modello-core/1.0-alpha-18/modello-core-1.0-alpha-18.jar
..................................................
attempting to create parent directories for destination: modello-plugin-xml-1.0-alpha-18.jar.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-xml/1.0-alpha-18/modello-plugin-xml-1.0-alpha-18.jar
...
attempting to create parent directories for destination: modello-plugin-plexus-registry-1.0-alpha-18.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/codehaus/modello/modello-plugin-plexus-registry/1.0-alpha-18/modello-plugin-plexus-registry-1.0-alpha-18.jar
...
attempting to create parent directories for destination: modello-plugin-store-1.0-alpha-18.jar.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-store/1.0-alpha-18/modello-plugin-store-1.0-alpha-18.jar
.....
attempting to create parent directories for destination: plexus-velocity-1.1.4.jar.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.4/plexus-velocity-1.1.4.jar
..
attempting to create parent directories for destination: modello-plugin-xsd-1.0-alpha-18.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/codehaus/modello/modello-plugin-xsd/1.0-alpha-18/modello-plugin-xsd-1.0-alpha-18.jar
......
attempting to create parent directories for destination: modello-plugin-jdom-1.0-alpha-18.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/codehaus/modello/modello-plugin-jdom/1.0-alpha-18/modello-plugin-jdom-1.0-alpha-18.jar
.....
attempting to create parent directories for destination: modello-plugin-jpox-1.0-alpha-18.jar.tmp
Downloading [repository.jboss.com] -> http://repository.jboss.com/maven2//org/codehaus/modello/modello-plugin-jpox/1.0-alpha-18/modello-plugin-jpox-1.0-alpha-18.jar
..........
attempting to create parent directories for destination: modello-db-keywords-1.0-alpha-18.jar.tmp
Downloading [central] -> http://repo1.maven.org/maven2/org/codehaus/modello/modello-db-keywords/1.0-alpha-18/modello-db-keywords-1.0-alpha-18.jar
........
[INFO] ----------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ----------------------------------------------------------------------------
[INFO] Java heap space
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 73 second
[INFO] Finished at: Tue Mar 03 07:44:58 CET 2009
[INFO] Memory 0M/63M
[INFO] ----------------------------------------------------------------------------

5. Re: becoming involved with the richFaces/a4j project

fmarwede Mar 3, 2009 3:34 AM (in response to zmarrapese)

Next try: Without eclipse, in windows console, your steps 1,2 and 3. 2 and 3 with a long duration, but both ended with compilation errors...

Sorry, I fear something is still going wrong. Maybe I should learn Maven with a more simple project, before getting on your nerves with that.

6. Re: becoming involved with the richFaces/a4j project

nbelaevski Mar 3, 2009 4:14 AM (in response to zmarrapese)

Here is what I have in MAVEN_OPTS environment variable:

MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=256m

. Please set it and give a try.

Can you please post what compilation errors you get?

7. Re: becoming involved with the richFaces/a4j project

fmarwede Mar 3, 2009 7:39 AM (in response to zmarrapese)

Thank you. I tried it once more and now with a little bit more knowledge about Maven and with a fresh workspace only for the Richfaces project.

Step 1 OK (fast)

Step 2 Needs a long time, here the last lines of console:


Results :

Tests in error:
 testRenderScripts(org.richfaces.renderkit.html.ScrollableDataTableRendererTes
)

Tests run: 133, Failures: 0, Errors: 1, Skipped: 0

 Found PropertyDescriptor java.beans.PropertyDescriptor@7be93698
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

Please refer to C:\workspaceRichfaces\RF_TRUNK\ui\scrollableDataTable\target\su
efire-reports for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19 minutes 35 seconds
[INFO] Finished at: Tue Mar 03 13:07:42 CET 2009
[INFO] Final Memory: 75M/254M
[INFO] ---------------------------------
---------------------------------------

Step 3 ended with:

[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] basedir C:\workspaceRichfaces\RF_TRUNK\ui\assembly\target\modules\insert
does not exist
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalStateException: basedir C:\workspaceRichfaces\RF_TRUNK\ui\assem
bly\target\modules\insert does not exist
 at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:
550)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.mergeXMLdir(AssemblyLib
raryMojo.java:709)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.mergeXML(AssemblyLibrar
yMojo.java:661)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.execute(AssemblyLibrary
Mojo.java:278)
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:453)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:559)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:500)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecy
cle(DefaultLifecycleExecutor.java:925)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Def
aultLifecycleExecutor.java:768)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:530)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:513)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:483)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:331)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:292)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:142)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20 minutes 20 seconds
[INFO] Finished at: Tue Mar 03 13:34:02 CET 2009
[INFO] Final Memory: 56M/254M
[INFO] ------------------------------------------------------------------------

8. Re: becoming involved with the richFaces/a4j project

fmarwede Mar 3, 2009 7:46 AM (in response to zmarrapese)

I checked the described folder \ui\assembly\target\modules. There are many folders called like RF components and their content seems to be okay. But insert (for example) is not there. So I understand this "Fatal Error" but how it occurs?

I additionaly have to say that there were many exceptions in between Step 3. Here an extract.

dleFailures(DefaultLifecycleExecutor.java:331)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:292)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:142)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to downl
oad the artifact from any repository
 at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def
aultWagonManager.java:332)
 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:200)
 ... 26 more
[ERROR] Not found artifact org.richfaces.ui:editor:jar:3.3.1-SNAPSHOT
org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download
 the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
 mvn install:install-file -DgroupId=org.richfaces.ui -DartifactId=editor -Dve
rsion=3.3.1-SNAPSHOT -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=editor -Dvers
ion=3.3.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drepository
Id=[id]


 org.richfaces.ui:editor:jar:3.3.1-SNAPSHOT



 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:212)
 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:74)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.unpackArtifact(Assembly
LibraryMojo.java:733)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.extractModules(Assembly
LibraryMojo.java:486)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.execute(AssemblyLibrary
Mojo.java:274)
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:453)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:559)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:500)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecy
cle(DefaultLifecycleExecutor.java:925)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Def
aultLifecycleExecutor.java:768)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:530)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:513)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:483)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:331)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:292)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:142)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to downl
oad the artifact from any repository
 at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def
aultWagonManager.java:332)
 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:200)
 ... 26 more
[ERROR] Not found artifact org.richfaces.ui:editor:jar:sources:3.3.1-SNAPSHOT
org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download
 the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
 mvn install:install-file -DgroupId=org.richfaces.ui -DartifactId=editor -Dve
rsion=3.3.1-SNAPSHOT -Dclassifier=sources -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=editor -Dvers
ion=3.3.1-SNAPSHOT -Dclassifier=sources -Dpackaging=jar -Dfile=/path/to/file -Du
rl=[url] -DrepositoryId=[id]


 org.richfaces.ui:editor:jar:3.3.1-SNAPSHOT



 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:212)
 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:74)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.unpackArtifact(Assembly
LibraryMojo.java:733)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.extractModules(Assembly
LibraryMojo.java:491)
 at org.ajax4jsf.builder.mojo.AssemblyLibraryMojo.execute(AssemblyLibrary
Mojo.java:274)
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:453)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:559)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:500)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecy
cle(DefaultLifecycleExecutor.java:925)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Def
aultLifecycleExecutor.java:768)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:530)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:513)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:483)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:331)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:292)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:142)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to downl
oad the artifact from any repository
 at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def
aultWagonManager.java:332)
 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:200)
 ... 26 more

9. Re: becoming involved with the richFaces/a4j project

nbelaevski Mar 3, 2009 9:08 AM (in response to zmarrapese)

I guees the cause is the outdated Maven version. We use 2.0.9. What version do you use?

10. Re: becoming involved with the richFaces/a4j project

fmarwede Mar 3, 2009 9:34 AM (in response to zmarrapese)

2.0.10. Could that be a problem?

11. Re: becoming involved with the richFaces/a4j project

nbelaevski Mar 3, 2009 11:17 AM (in response to zmarrapese)

I've installed 2.0.10 and give it a try now.

12. Re: becoming involved with the richFaces/a4j project

nbelaevski Mar 3, 2009 12:54 PM (in response to zmarrapese)

I've fixed the issue with 2.0.10. Please update and try again.

13. Re: becoming involved with the richFaces/a4j project

fmarwede Mar 3, 2009 4:11 PM (in response to zmarrapese)

It is working...Step 2 was successfully completed in 49 min...Step 3 ins 16 minutes.

Thank you very much! Now I can explore the whole thing.

One more little question: What I have to do, when I have changed or updated something? clean and install takes almost an hour! Do you do that everyday?

14. Re: becoming involved with the richFaces/a4j project

fmarwede Mar 4, 2009 1:54 AM (in response to zmarrapese)

I'm interested in ScrollableDataTable, Tree and D&D stuff - so I imported the related projects. I got many errors (xml stuff but also some package dependencies, for example to antlr) and also I realized the complexity of all that stuff.

So my next question: What would you suggest for training? In my opinion it would be the best to start with a simple component, and the most simple configuration of projects possible, so I can change anything, build and test it with a small test web application to learn this cycle and to learn what is overall involved for developing a RF component.