You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Sam Berlin <sb...@gmail.com> on 2009/03/24 19:35:52 UTC
rereport, exclude dependencies
I would like to list dependencies in rereport that only contain a
certain organization. This is to be able to see the dependency graph
of our local components. Including all the other dependencies makes
for a huge mess of a graph.
According to the documentation there doesn't seem to be a way to make
repreport do this (and I'm pretty certain I don't want to use report,
since I want a single graph of all local dependencies). Am I missing
something? Does Ivy use XSL to transform the xml into a graphml or
dot file? If so, do you think it would work to modify that XSL?
Any other suggestions for how this can be done?
Thanks!
Sam
RE: rereport, exclude dependencies
Posted by Nascif Abousalh-Neto <Na...@sas.com>.
Hi Sam,
I need to clean it up first, but sure. I will add it to Jira and post the link back here.
Cheers,
Nascif
-------------------------------------------------------------------
Nascif Abousalh-Neto
Software Development Manager
Query and Reporting ▪ Business Intelligence Clients
Tel: + 1 919 531 0123 - Nascif.AbousalhNeto@sas.com
www.sas.com
SAS® … THE POWER TO KNOW®
-----Original Message-----
From: Sam Berlin [mailto:sberlin@gmail.com]
Sent: Wednesday, March 25, 2009 11:45 AM
To: ivy-user@ant.apache.org
Subject: Re: rereport, exclude dependencies
Are you able to share your ant task, Nascif? I managed to hack up a
very custom XSL file [1] that includes only the organization I'm
looking for, but it's a complete hack & it doesn't lend itself to
other things I'd like to implement too.
Sam
[1] https://www.limewire.org/fisheye/browse/~raw,r=1.2/limecvs/lib/jars/ant/ivy-limewire-dot.xsl
On Tue, Mar 24, 2009 at 9:53 PM, Nascif Abousalh-Neto
<Na...@sas.com> wrote:
> The problem with the XSL approach is that you will still produce and iterate over all the repo interdependencies, even the ones you don't care about. My experience is that for a large repo, and specially if you are using a resource-heavy resolver like HTTP, this will kill your build performance before you can get to the XSL task.
>
> Another major problem IMHO with the current rereport is that it doesn't take advantage of the download option in the ResolveOptions API. So when you run this query you will effectively download *all* the artifaces in your repositiory (for their latest versions) - just to get their metadata to figure out the dependency graph. A huge wast of time and disk space.
>
> I ended up coding my own version where I exposed most of the ResolveOptions API.
>
> ________________________________________
> From: Archie Cobbs [archie.cobbs@gmail.com]
> Sent: Tuesday, March 24, 2009 9:43 PM
> To: ivy-user@ant.apache.org
> Subject: Re: rereport, exclude dependencies
>
> This is specific to Ivy RoundUp, and so may not be useful to you, but anyway
> here is an XSL that we use to generate dependency graphs:
>
> http://ivyroundup.googlecode.com/svn/trunk/src/xsl/modgraph.xsl
>
> You would have to hack on it. It requires the existence of a modules.xml
> "directory" file.
>
> FWIW.
>
> -Archie
>
> On Tue, Mar 24, 2009 at 1:35 PM, Sam Berlin <sb...@gmail.com> wrote:
>
>> I would like to list dependencies in rereport that only contain a
>> certain organization. This is to be able to see the dependency graph
>> of our local components. Including all the other dependencies makes
>> for a huge mess of a graph.
>>
>> According to the documentation there doesn't seem to be a way to make
>> repreport do this (and I'm pretty certain I don't want to use report,
>> since I want a single graph of all local dependencies). Am I missing
>> something? Does Ivy use XSL to transform the xml into a graphml or
>> dot file? If so, do you think it would work to modify that XSL?
>>
>> Any other suggestions for how this can be done?
>>
>> Thanks!
>>
>> Sam
>>
>
>
>
> --
> Archie L. Cobbs
Re: rereport, exclude dependencies
Posted by Sam Berlin <sb...@gmail.com>.
Are you able to share your ant task, Nascif? I managed to hack up a
very custom XSL file [1] that includes only the organization I'm
looking for, but it's a complete hack & it doesn't lend itself to
other things I'd like to implement too.
Sam
[1] https://www.limewire.org/fisheye/browse/~raw,r=1.2/limecvs/lib/jars/ant/ivy-limewire-dot.xsl
On Tue, Mar 24, 2009 at 9:53 PM, Nascif Abousalh-Neto
<Na...@sas.com> wrote:
> The problem with the XSL approach is that you will still produce and iterate over all the repo interdependencies, even the ones you don't care about. My experience is that for a large repo, and specially if you are using a resource-heavy resolver like HTTP, this will kill your build performance before you can get to the XSL task.
>
> Another major problem IMHO with the current rereport is that it doesn't take advantage of the download option in the ResolveOptions API. So when you run this query you will effectively download *all* the artifaces in your repositiory (for their latest versions) - just to get their metadata to figure out the dependency graph. A huge wast of time and disk space.
>
> I ended up coding my own version where I exposed most of the ResolveOptions API.
>
> ________________________________________
> From: Archie Cobbs [archie.cobbs@gmail.com]
> Sent: Tuesday, March 24, 2009 9:43 PM
> To: ivy-user@ant.apache.org
> Subject: Re: rereport, exclude dependencies
>
> This is specific to Ivy RoundUp, and so may not be useful to you, but anyway
> here is an XSL that we use to generate dependency graphs:
>
> http://ivyroundup.googlecode.com/svn/trunk/src/xsl/modgraph.xsl
>
> You would have to hack on it. It requires the existence of a modules.xml
> "directory" file.
>
> FWIW.
>
> -Archie
>
> On Tue, Mar 24, 2009 at 1:35 PM, Sam Berlin <sb...@gmail.com> wrote:
>
>> I would like to list dependencies in rereport that only contain a
>> certain organization. This is to be able to see the dependency graph
>> of our local components. Including all the other dependencies makes
>> for a huge mess of a graph.
>>
>> According to the documentation there doesn't seem to be a way to make
>> repreport do this (and I'm pretty certain I don't want to use report,
>> since I want a single graph of all local dependencies). Am I missing
>> something? Does Ivy use XSL to transform the xml into a graphml or
>> dot file? If so, do you think it would work to modify that XSL?
>>
>> Any other suggestions for how this can be done?
>>
>> Thanks!
>>
>> Sam
>>
>
>
>
> --
> Archie L. Cobbs
RE: rereport, exclude dependencies
Posted by Nascif Abousalh-Neto <Na...@sas.com>.
The problem with the XSL approach is that you will still produce and iterate over all the repo interdependencies, even the ones you don't care about. My experience is that for a large repo, and specially if you are using a resource-heavy resolver like HTTP, this will kill your build performance before you can get to the XSL task.
Another major problem IMHO with the current rereport is that it doesn't take advantage of the download option in the ResolveOptions API. So when you run this query you will effectively download *all* the artifaces in your repositiory (for their latest versions) - just to get their metadata to figure out the dependency graph. A huge wast of time and disk space.
I ended up coding my own version where I exposed most of the ResolveOptions API.
________________________________________
From: Archie Cobbs [archie.cobbs@gmail.com]
Sent: Tuesday, March 24, 2009 9:43 PM
To: ivy-user@ant.apache.org
Subject: Re: rereport, exclude dependencies
This is specific to Ivy RoundUp, and so may not be useful to you, but anyway
here is an XSL that we use to generate dependency graphs:
http://ivyroundup.googlecode.com/svn/trunk/src/xsl/modgraph.xsl
You would have to hack on it. It requires the existence of a modules.xml
"directory" file.
FWIW.
-Archie
On Tue, Mar 24, 2009 at 1:35 PM, Sam Berlin <sb...@gmail.com> wrote:
> I would like to list dependencies in rereport that only contain a
> certain organization. This is to be able to see the dependency graph
> of our local components. Including all the other dependencies makes
> for a huge mess of a graph.
>
> According to the documentation there doesn't seem to be a way to make
> repreport do this (and I'm pretty certain I don't want to use report,
> since I want a single graph of all local dependencies). Am I missing
> something? Does Ivy use XSL to transform the xml into a graphml or
> dot file? If so, do you think it would work to modify that XSL?
>
> Any other suggestions for how this can be done?
>
> Thanks!
>
> Sam
>
--
Archie L. Cobbs
Re: rereport, exclude dependencies
Posted by Archie Cobbs <ar...@gmail.com>.
This is specific to Ivy RoundUp, and so may not be useful to you, but anyway
here is an XSL that we use to generate dependency graphs:
http://ivyroundup.googlecode.com/svn/trunk/src/xsl/modgraph.xsl
You would have to hack on it. It requires the existence of a modules.xml
"directory" file.
FWIW.
-Archie
On Tue, Mar 24, 2009 at 1:35 PM, Sam Berlin <sb...@gmail.com> wrote:
> I would like to list dependencies in rereport that only contain a
> certain organization. This is to be able to see the dependency graph
> of our local components. Including all the other dependencies makes
> for a huge mess of a graph.
>
> According to the documentation there doesn't seem to be a way to make
> repreport do this (and I'm pretty certain I don't want to use report,
> since I want a single graph of all local dependencies). Am I missing
> something? Does Ivy use XSL to transform the xml into a graphml or
> dot file? If so, do you think it would work to modify that XSL?
>
> Any other suggestions for how this can be done?
>
> Thanks!
>
> Sam
>
--
Archie L. Cobbs