Hello,
thank you for your comments.
So far as i understand it now, you develop against your own (also developed) branch
of jxta, so you can include fixes and so on. ok.
=> Do you have plans to release a shoal version against a released version of jxta?
I mean, i am pretty aware of the fact, that when i have access to all my own libraries, that i will
also include my bug fixes to those libraries, as soon as i am aware of them.
But for someone like me who is out there, who includes foreign projects like shoal, it feels awkward,
that i have to add "project specific" jars/libraries (e.g. of your "own" jxta) to make it work, while
on the other hand there are other projects, who might depend on a released version of jxta.
When this happens, i would usually balance it out, by using a released version of project 'shoal' and
project B, which depends on the same version of jxta.
But with a project specific version of jxta, i will never be able to include project B.
Mh.
On Tue, Oct 07, 2008 at 11:32:18AM -0400, Joseph Fialli wrote:
> The cvs log for the jxta.jar checkin states it is from this branch and also states the precise SVN version number that
> tags the precise versions of these files that were used to create the jxta.jar that is checked in.
> Shreedhar Ganapathy wrote:
> > Hi Olaf
> > It corresponds to Jxta's SVN revision 556 plus a couple of added
> > fixes. We have branched from Jxta's trunk in order to stabilize for
> > upcoming GlassFish and Sailfin releases.