Cool! Thanks a lot. Graphviz is low tech enough for me. I will give a try
at both.
Bertrand
Le lundi 28 juillet 2014 16:38:52 UTC+2, Andy Fingerhut a écrit :
>
> You can try Eastwood's :unused-namespaces linter for #2. It is disabled
> by default, so you need to give an option on the command line to enable
> it. If you want to try *only* that linter, and none of the other warnings,
> first follow the simple install instructions in the README, then change to
> the home dir of your project and type:
>
> lein eastwood '{:linters [:unused-namespaces]}'
>
> Eastwood will not currently help you with your request #1, but it would
> not be difficult to add such a feature to it, since it determines
> dependencies between namespaces already using tools.namespace. There are
> other tools that can do this for you, e.g. nephila [2] will create a
> graphics image of your project's namespace dependencies, but you must have
> graphviz installed. I don't know of a similar tool that only creates text
> dependency output.
>
> Andy
>
> [1] https://github.com/jonase/eastwood
>
> [2] https://github.com/timmc/nephila
>
>
> On Mon, Jul 28, 2014 at 4:58 AM, Bertrand Dechoux <dech...@gmail.com
> <javascript:>> wrote:
>
>> Hello,
>>
>> I am trying to tidy up a project and I have two actions that could be
>> somehow be automatized.
>>
>> *1) Display the dependencies between the namespace of my project as a
>> graph (text graph being good enough).*
>> One would want to break dependencies which do not make sense and
>> sometimes to create indirection in order to lessen the impact of changes.
>>
>> *2) Find out which dependencies are not required.*
>> Splitting a namespace might be quite easy (the complex part is on the
>> consumer side) but often I find out that dependencies were not pruned
>> correctly.
>> And so there are useless remaining dependencies that were not removed.
>>
>> I understand that a 100% bullet proof solution might be really hard to do.
>> But I was wondering, is there any tools that allows to do these tasks for
>> common cases?
>>
>> Regards
>>
>> Bertrand Dechoux
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clo...@googlegroups.com
>> <javascript:>
>> Note that posts from new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+u...@googlegroups.com <javascript:>
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+u...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
