Re: V2.x not usable next to V1.x

No, the problem is not like that, it won't affect the stats.

What *could* be possible is that people have not moved to 2.x because they
have compile dependencies from components that *require* 1.1, and thus they
need 1.1 too....

Remember, they did not move from 1.1 to 1.1.2 and 1.1.3 either.

I think the stats are a fair representation of the 'demand' for JDOM, but
that people set up their maven systems 'a long time ago' and they are on
'auto pilot' so they are not aware of the bug fixes, performance gains, etc
that are in 1.1.2, 1.1.3, and 2.0.x. Also, I think the 'automated' systems
that download from maven are overestimating the number of maven downloads
when compared to the www.jdom.org site. I would guess that a lot of the 30k
downloads a month are from a few people who have badly configured build
environments that just download JDOM multiple times a day..... thus
inflating the doanload numbers. My guess would be that the 'big' users of
JDOM download the zip file once, and install it in to their 'build'
process, and then never touch it again until the next version is out. I
know that we do that where I work, and thus we have just 1 donload hit for
many many thousands of builds, developers, versions, etc. On the other
hand, a poorly configured maven 'shop' will likely have one download per
developer, per 'clean' build, per day....

Rolf


On Fri, 18 May 2012 09:21:28 -0700, Joe Bowbeer <[email protected]>
wrote:
> If there is a problem with the way jdom2 was published to maven, this
might
> affect your stats?
> 

_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/[email protected]