On Mon 2016-03-14 11:21, Sebastian Laskawiec wrote:
> I took a look at Nexus download statistics and Infinispan Uberjars are
> about 7% of our downloads (of course this calculation has been based on our
> JBoss Nexus instance and we have no data from other mirrors).
It's actually the opposite,
On Mon, Mar 14, 2016 at 12:21 PM, Sebastian Laskawiec
wrote:
> I took a look at Nexus download statistics and Infinispan Uberjars are about
> 7% of our downloads (of course this calculation has been based on our JBoss
> Nexus instance and we have no data from other mirrors).
To make a more practical proposal:
give me a way to start a local, non transactional Cache which doesn't
require any of:
- JGroups
- JBoss Marshalling
- JTA API
- Infinispan Commons
If I don't have - for example - JGroups and am starting a clustered
cache, I will see an exception "Enabling
Hi,
uber jars were introduced as an answer to complaints such as "there
are too many jars" but I still think this was the wrong answer.. too
many issues so please stop this: it's not helping usability to
understand which jars are needed, and it makes things worse with
runtime errors not matching
--
Galder Zamarreño
Infinispan, Red Hat
> On 14 Mar 2016, at 08:42, Tristan Tarrant wrote:
>
>
>
> On 11/03/2016 18:20, Galder Zamarreño wrote:
>> Are uber jars really that useful? From my own experience they often get
>
> The number of users who don't use a dependency
I took a look at Nexus download statistics and Infinispan Uberjars are
about 7% of our downloads (of course this calculation has been based on our
JBoss Nexus instance and we have no data from other mirrors).
So, once we are clear how Uber Jars should work... let's take a look at one
of the
On 11/03/2016 18:20, Galder Zamarreño wrote:
> Are uber jars really that useful? From my own experience they often get
The number of users who don't use a dependency management system (Maven,
Ivy, Gradle) is quite a lot higher than you'd expect.
Tristan
--
Tristan Tarrant
Infinispan Lead
Are uber jars really that useful? From my own experience they often get more in the way, e.g. clash of dependencies. We can fix our own clashes but once you have other modules creating uber jars users might get more of those clashes.Regardless of that, if we're continue with uber jars, it'd make
Hey!
Uber jars have been around for quite a while but some old problems are
still biting our ankles. The biggest problem is JBoss Logging... But before
diving into the technical discussion, I would like to clarify how do we
treat Uber Jars and how other (let's call them "extra") modules should