That could be my proxy.  I will take a look at that thanks!

 

________________________________

From: Leonardo Uribe [mailto:[email protected]] 
Sent: Wednesday, May 06, 2009 1:49 PM
To: MyFaces Discussion
Subject: Re: Building tomahawk 1.1.19 fails during tests

 

Hi Joe

Checking the latest code (1.1.9-SNAPSHOT) everything compiles fine
(tomahawk core and core12).

But this tests fails if your computer does not have internet connection,
or maven does not have proper proxy configuration (the tests validates
.tld and faces-config.xml files):

------------------------------------------------------------------------
-------
Test set: org.apache.myfaces.test.MyFacesTagLibTestCase
------------------------------------------------------------------------
-------
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 1.016
sec <<< FAILURE!
testUniqueTagTestCase(org.apache.myfaces.test.MyFacesTagLibTestCase)
Time elapsed: 0.625 sec  <<< ERROR!
java.net.UnknownHostException: java.sun.com
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
    at java.net.Socket.connect(Socket.java:519)
    at java.net.Socket.connect(Socket.java:469)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
    at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
    at sun.net.www.http.HttpClient.New(HttpClient.java:306)
    at sun.net.www.http.HttpClient.New(HttpClient.java:323)

You can skip tests and compile tomahawk offline using:

mvn install -o -Dmaven.test.skip=true

regards

Leonardo Uribe

2009/5/6 Knudsen, Joe <[email protected]>


I trying to build tomahawk 1.1.19 and receive these errors so the build
fails.  Any ideas or should I bypass the tests.   Thanks, Joe Knudsen

INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation
WARNING: Component _id1 just got an automatic id, because there was no
id assigned yet. If this component was created dynamically (i.e. not by
a JSP tag) you should assign it an explicit static id or assign it the
id you get from the createUniqueId from the current UIViewRoot component
right after creation!
WARNING: Component _id1:_id0 just got an automatic id, because there was
no id assigned yet. If this component was created dynamically (i.e. not
by a JSP tag) you should assign it an explicit static id or assign it
the id you get from the createUniqueId from the current UIViewRoot
component right after creation!
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031
sec
Running org.apache.myfaces.component.html.ext.HtmlInputHiddenTest
WARNING: Component _id0 just got an automatic id, because there was no
id assigned yet. If this component was created dynamically (i.e. not by
a JSP tag) you should assign it an explicit static id or assign it the
id you get from the createUniqueId from the current UIViewRoot component
right after creation!
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.myfaces.custom.selectOneLanguage.SelectOneLanguageRendererTes
t
WARNING: Component _id0 just got an automatic id, because there was no
id assigned yet. If this component was created dynamically (i.e. not by
a JSP tag) you should assign it an explicit static id or assign it the
id you get from the createUniqueId from the current UIViewRoot component
right after creation!
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032
sec

Results :

Tests in error:
 testUniqueTagTestCase(org.apache.myfaces.test.MyFacesTagLibTestCase)
 testUniqueTagAttributes(org.apache.myfaces.test.MyFacesTagLibTestCase)
 testSetters(org.apache.myfaces.test.MyFacesTagLibTestCase)
 testClassPath(org.apache.myfaces.test.TomahawkClassElementTestCase)

Tests run: 178, Failures: 0, Errors: 4, Skipped: 0

[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] There are test failures.

 

Reply via email to