9:36 a.m.
Hi,
I'm trying to reduce the size of the distribution archives by removing
jar duplication. I noticed that we can already shave off 40MB of 160MB
by removing duplication.
Another option is to remove dependencies which are not actually needed
(if there are any). Can I get some help from module authors to detect them?
Thanks,
Adrian
11:38 a.m.
Try doing mvn dependency:tree for each module (or in the root) to print out the dependency
graph. That'll help people understand which dependencies are needed and which are
not.
On 18 Jun 2012, at 08:36, Adrian Nistor wrote:
Hi,
I'm trying to reduce the size of the distribution archives by removing
jar duplication. I noticed that we can already shave off 40MB of 160MB
by removing duplication.
Another option is to remove dependencies which are not actually needed
(if there are any). Can I get some help from module authors to detect them?
Thanks,
Adrian
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Project Lead, Infinispan
http://www.infinispan.org
Platform Architect, JBoss Data Grid
http://www.redhat.com/promo/dg6beta
2:21 p.m.
Right, here is the dependency graph.
On 06/18/2012 12:38 PM, Manik Surtani wrote:
Try doing mvn dependency:tree for each module (or in the root) to
print out the dependency graph. That'll help people understand which
dependencies are needed and which are not.
On 18 Jun 2012, at 08:36, Adrian Nistor wrote:
> Hi,
>
> I'm trying to reduce the size of the distribution archives by removing
> jar duplication. I noticed that we can already shave off 40MB of 160MB
> by removing duplication.
>
> Another option is to remove dependencies which are not actually needed
> (if there are any). Can I get some help from module authors to detect
> them?
>
> Thanks,
> Adrian
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org <mailto:infinispan-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org <mailto:manik@jboss.org>
twitter.com/maniksurtani <http://twitter.com/maniksurtani>
Project Lead, Infinispan
http://www.infinispan.org
Platform Architect, JBoss Data Grid
http://www.redhat.com/promo/dg6beta
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
4:42 p.m.
Everyone, please have a look and confirm that all of the dependencies here are actually
necessary in each module.
On 18 Jun 2012, at 13:21, Adrian Nistor wrote:
Right, here is the dependency graph.
On 06/18/2012 12:38 PM, Manik Surtani wrote:
>
> Try doing mvn dependency:tree for each module (or in the root) to print out the
dependency graph. That'll help people understand which dependencies are needed and
which are not.
>
>
> On 18 Jun 2012, at 08:36, Adrian Nistor wrote:
>
>> Hi,
>>
>> I'm trying to reduce the size of the distribution archives by removing
>> jar duplication. I noticed that we can already shave off 40MB of 160MB
>> by removing duplication.
>>
>> Another option is to remove dependencies which are not actually needed
>> (if there are any). Can I get some help from module authors to detect them?
>>
>> Thanks,
>> Adrian
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
> Manik Surtani
> manik(a)jboss.org
> twitter.com/maniksurtani
>
> Project Lead, Infinispan
> http://www.infinispan.org
>
> Platform Architect, JBoss Data Grid
> http://www.redhat.com/promo/dg6beta
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
<deptree.log>_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Project Lead, Infinispan
http://www.infinispan.org
Platform Architect, JBoss Data Grid
http://www.redhat.com/promo/dg6beta
9:32 p.m.
On 18 June 2012 17:35, Vladimir Blagojevic <vblagoje(a)redhat.com> wrote:
On 12-06-18 10:42 AM, Manik Surtani wrote:
> Everyone, please have a look and confirm that all of the dependencies
> here are actually necessary in each module.
Almost all my dependencies are needed depending on what the user
wants, which options he chooses to enable.
For example, Infinispan Query depends on Hibernate Search "engine" and
Lucene-Core, and from that we stricly require only
hibernate-commons-annotations. But it's very likely you want to use
custom Analyzers, which then triggers Solr packages, a dozen of jars
containing the analyzer extensions, SLF4J, commons-logging,
commons-lang, etc...
Others like Apache Avro + Jackson are needed only if you want
clustering. So that's optional ?
Were should we draw the line? Should we cut them all out, and have a
readme mentioning "download from here" ?
If that's the case, I'd want to test it without those jars too, to
make sure I'm not removing something which is actually needed: I'd add
additional integration-testing modules.
What are these woodstox libraries used for in core? Can not find them
in
our code as compile dependencies?
It's used to parse the configuration files.
10:23 a.m.
On 18 Jun 2012, at 20:32, Sanne Grinovero wrote:
On 18 June 2012 17:35, Vladimir Blagojevic
<vblagoje(a)redhat.com> wrote:
> On 12-06-18 10:42 AM, Manik Surtani wrote:
>> Everyone, please have a look and confirm that all of the dependencies
>> here are actually necessary in each module.
Almost all my dependencies are needed depending on what the user
wants, which options he chooses to enable.
For example, Infinispan Query depends on Hibernate Search "engine" and
Lucene-Core, and from that we stricly require only
hibernate-commons-annotations. But it's very likely you want to use
custom Analyzers, which then triggers Solr packages, a dozen of jars
containing the analyzer extensions, SLF4J, commons-logging,
commons-lang, etc...
Others like Apache Avro + Jackson are needed only if you want
clustering. So that's optional ?
Were should we draw the line? Should we cut them all out, and have a
readme mentioning "download from here" ?
Yeah this is a tough one. Why doesn't everyone just use Maven. ;)
I definitely think a README is necessary to detail which jars can be excluded from a
user's class path/deployment based on how a module is used, but I'm not so sure
about removing the jars from the distro.
Cheers
Manik
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Project Lead, Infinispan
http://www.infinispan.org
Platform Architect, JBoss Data Grid
http://www.redhat.com/promo/dg6beta
12:22 p.m.
On 06/18/2012 04:42 PM, Manik Surtani wrote:
Everyone, please have a look and confirm that all of the dependencies
here are actually necessary in each module.
As I said before the cassandra cachestore module is pulling in
cassandra-all because of some stupidity on my part.
I have created https://issues.jboss.org/browse/ISPN-2118 and
corresponding pull req to clean this up
Tristan
4389
days inactive
4390
days old
infinispan-dev@lists.jboss.org
7 comments
5 participants
participants (5)
-
Adrian Nistor -
Manik Surtani -
Sanne Grinovero -
Tristan Tarrant -
Vladimir Blagojevic