This content has been marked as final. 
    
Show                 4 replies
    
- 
        1. Re: Release of JBossXB with no dependence on Oswego Concurrealoubyansky Aug 2, 2007 2:57 AM (in response to anil.saldhana)The reason for oswego was 1.4 compliance. If there are no more dependent projects that require 1.4 compliance we can switch to java.util.concurrent. 
- 
        2. Re: Release of JBossXB with no dependence on Oswego Concurreadrian.brock Aug 2, 2007 10:19 AM (in response to anil.saldhana)We can jboss retro jbossxb for 1.4 usage. 
- 
        3. Re: Release of JBossXB with no dependence on Oswego Concurrealoubyansky Aug 10, 2007 12:14 PM (in response to anil.saldhana)Done. http://jira.jboss.com/jira/browse/JBXB-105 
 I've also updated the snapshots:Uploading: https://snapshots.jboss.org/maven2/org/jboss/jbossxb/2.0.0-SNAPSHOT/jbossxb-2.0.0-2007 0810.160055-4.jar Uploading: https://snapshots.jboss.org/maven2/org/jboss/jbossxb/2.0.0-SNAPSHOT/jbossxb-2.0.0-2007 0810.160055-4-sources.jar Uploading: https://snapshots.jboss.org/maven2/org/jboss/jbossxb/1.0.0-SNAPSHOT/jbossxb-1.0.0-2007 0810.161128-3.jar Uploading: https://snapshots.jboss.org/maven2/org/jboss/jbossxb/1.0.0-SNAPSHOT/jbossxb-1.0.0-2007 0810.161128-3-sources.jar 
- 
        4. Re: Release of JBossXB with no dependence on Oswego Concurreanil.saldhana Aug 10, 2007 12:28 PM (in response to anil.saldhana)Thanks for that, Alex. Looks like it was a simple change for you. :) 
 
     
    