Daniel Kulp wrote:
MOST of this tree looks to be stuff that falls into test dependencies,
not runtime dependencies. Is it possible to redo the graph with
runtime dependencies only?
Thank you Dan (and others) for pointing that out... The srpm that I
started with includes the client, the
Runtime deps for the java broker and client should look like:
relaxngDatatype-20020414.jar
isorelax-20020414.jar
mina-core-1.0.0.jar
log4j-1.2.12.jar
commons-collections-3.1.jar
qpid-client-1.0-incubating-M2-SNAPSHOT.jar
commons-codec-1.3.jar
backport-util-concurrent-2.2.jar
xercesImpl-2.2.1.jar
Rupert Smith wrote:
Runtime deps for the java broker and client should look like: [...]
That list looks a lot more manageable, but I'm also interested in
tracking buildtime dependencies, because for our purposes we need to
provide everything that's required to build the binary rpm from
Nuno,
MOST of this tree looks to be stuff that falls into test dependencies,
not runtime dependencies. Is it possible to redo the graph with
runtime dependencies only?
For example: the big tree on the left that extends from
easymock-classextensions. Easymock is used by the unit tests to
Nuno,
That is a nice diagram.
Are you looing to reduce the runtime dependancies or just dependancies
in general?
Easymock is only referenced by the pom AFAIK. It was left in as there
was desire to use it for testing but we haven't gone that route yet.
Backport will be removed when we upgrade
Hi All,
I think there's probably something to be said for a more detailed discussion
on the list of dependencies
Afaik we're not using easymock ? Please let us know if you are using it on
the Java side. Iirc Steve introduced it as potentially useful in the future,
but I'm not aware that we
The retrotranslator runtime stuff, had to be declared as provided to get the
retrotranslator plugin to work. It is onyl actually used in retotranslated
java clients. I think maybe, I need to move the retrotransaltion of client
and common into seperate packages, so as not to pollute the originals
