portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject security, sso, cyclic reference
Date Wed, 21 Jan 2009 05:22:46 GMT
Im trying to run the tests in jetspeed-security. A good portion of the  
tests are broken due to a SSO-impl bean not being found rooted in  
security-managers.xml. I am trying to get the tests fixed and get the  
trunk back to the point where people can get on with their job with  
running into broken (tests) builds.
Unfortunately in trying to fix it, I've come across a cyclic reference  
between jetspeed-security and jetspeed-sso.

Does anyone object to merging the jetspeed-sso component into jetspeed- 
security, and then removing the jetspeed-sso component?
If yes (you do object), please suggest a better solution

To reproduce this, you can add line 134 to AbstractSecurityTest.java


and modify the unpack-test-resources in the jetspeed-security  
pom.xml's assembly to include sso.xml:


add this dep to jetspeed-security:


and run:

mvn jetspeed:mvn -Dtarget=test-install

Im seeing:

[INFO] The projects in the reactor contain a cyclic reference: Edge  
between 'Vertex{label='org.apache.portals.jetspeed-2:jetspeed-sso'}'  
and 'Vertex{label='org.apache.portals.jetspeed-2:jetspeed-security'}'  
introduces to cycle in the graph  
org.apache.portals.jetspeed-2:jetspeed-security -->  
org.apache.portals.jetspeed-2:jetspeed-sso -->  

Another solution could be to use a modified assembly in the security  
tests that does not bring in the SSO dependencies via security- 
This leads to another discussion regarding the validity of the demo  
assemblies being reused in unit tests....

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message