Re: [WSS4J] stable wss4j patch

Yup, cvs is still messed up. Sorry for the misinformation.

Looks like the wssec directory is no longer in the anonymous repository  
(my reason for thinking it was OK), but some of the other files have  
reverted to previous revisions.

Here's hoping that sf gets this figured out soon.

-jason


On Feb 4, 2004, at 8:21 AM, Davanum Srinivas wrote:

> anonymous repository is still screwed up a bit. chasing sf.net folks
>
> https://sourceforge.net/tracker/? 
> func=detail&atid=200001&aid=890168&group_id=1
> https://sourceforge.net/tracker/? 
> func=detail&atid=200001&aid=889004&group_id=1
>
> -- dims
>
> --- Jason Essington <[email protected]> wrote:
>> A couple of days ago cvs was messed up and it was including the  
>> removed
>> dir src/wssec. If you just delete that whole directory (wssec) from  
>> the
>> source tree, wss4j will build just fine (use ant 1.6).
>>
>> looks like the repository is o.k. now, so a fresh checkout should  
>> build
>> as well.
>>
>> -jason
>>
>> On Feb 3, 2004, at 4:23 AM, Sashka wrote:
>>
>>> Hi guys
>>> Is there any stable/semi-stable patch of the wss4j, I could use to
>>> check if
>>> I can use it, with working samples readme's etc.? - I downloaded the
>>> cvs
>>> yesterday, but it seems some parts of this code is quite crude (for
>>> example, wssec.WSConstants is referred in WSSecurityUtil but  
>>> <probably?
>>> refactored> found at org.apache.ws.security.WSConstants etc), so it
>>> doesn't
>>> pass build.
>>> 10x ahead,
>>> Sincerely,
>>> Jabb.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn