I use a script to build the release notes, it doesn't take into consideration that some dependencies have been updated multiple times on the way to 3.0.0.RC1. On our usual update releases I try to had a note "recorded for historical purposes" or the like, however with 964 entries in this RC I didn't go through that manual process. My apologies for any confusion while reading the notes.
Cheers, Jamie On Sun, Mar 17, 2013 at 6:06 PM, Ryan Moquin <[email protected]> wrote: > Actually the dependencies table looks better, then dependencies on the > release notes page looks funny, > > > On Sun, Mar 17, 2013 at 4:18 PM, Ryan Moquin <[email protected]> wrote: >> >> Congrats! Excited to see RC1 out!!! >> >> I see a bunch off odd/conflicting things in the upgraded dependencies list >> thoug. For example: >> >> KARAF-449 - Upgrade to PAX-WEB 1.1.0 (SNAPSHOT right now) >> KARAF-797 - Upgrade to Pax Web 1.1.1 >> KARAF-682 - upgrade to jetty 7.4.2.v20110526 >> KARAF-757 - upgrade to jetty 7.4.4.v20110707 >> KARAF-789 - Upgrade jetty to 7.4.5.v20110725 >> KARAF-989 - Upgrade to Aries Application 0.4 >> KARAF-990 - Upgrade to Aries JMX 0.4 >> KARAF-991 - Upgrade to Aries JPA 0.4 >> KARAF-992 - Upgrade to Aries JNDI 0.4 >> KARAF-993 - Upgrade to Aries Proxy 0.4 >> KARAF-994 - Upgrade to Aries Transaction 0.4 >> KARAF-995 - Upgrade to Aries Util 0.4 >> KARAF-998 - upgrade to jetty 7.5.4.v20111024 >> KARAF-1028 - Upgrade to Felix Framework 4.0.2 >> >> Is that list simply listing old dependency changes? It looks like it has >> to be since there are multiple upgrades mentioned of the same library and >> obviously it isn't using aries 0.4.... >> >> Or am I just missing something? > >
