After an offline discussion with Sanjiva on the version issue I've
released JiBX 1.1 beta2 to match the Axis2 1.0 release. I realize a full
release would be better, but the beta at least gives a stable version
for build purposes while allowing me to continue work on the features
I've promised for my 1.1 release. I've also updated the Axis2
project.properties to reference the proper jars.
- Dennis
Steve Loughran wrote:
Sanjiva Weerawarana wrote:
On Thu, 2006-04-27 at 20:15 +1200, Dennis Sosnoski wrote:
I'll update to jibx-*-1.1beta2.jar by this weekend. I assume this is
okay, to get around the SNAPSHOT issue. I'd prefer to leave the
final 1.1 release until sometime in May, after I've had a chance to
do more with the binding generation/schema generation tools. If
anyone has a problem with using a beta version for the release,
please let me know now.
IMO it'll be better to have a proper version .. is it unfeasible to have
1.1 now and do a 1.2 in May/later? In any case the user will have to put
a new jar to get your newer version so it makes little difference it
seems to me. From an Axis2 1.0 perspective it looks nicer to have real
versions of everything .. and so far its only JibX that's at risk.
I'd veto any attempt to ship against -SNAPSHOT versions. Anyone who
used Muse would have been burned by this and you dont want to repeat
the problem. It becomes impossible to rebuild that version of the
product, and nobody wants to feel bugreps against it.
At least give it a version that is tagged in SVN and added to the
maven repos, like 1.1-beta1.
-steve
