On 07.02.2008 11:11, Alfred Nathaniel wrote:
I now added exclusion rules to all our explicit dependencies which pick
up the old avalon-framework through transitive dependencies.
Thanks very much, Alfred. That's really appreciated!
Joerg
On Mon, 2007-11-26 at 08:45 +0100, Reinhard Poetz wrote:
> The problem is that the groupId of the Avalon framework changed and that's
> the
> root of all evil in this case. We ever never need a dependency on Avalon
> 4.1.3
> but how to express this in the managedDependencies section?
>
> The o
Joerg Heinicke pisze:
> On 25.11.2007 10:45 Uhr, Grzegorz Kossakowski wrote:
>
>
>> Just check file target/site/dependencies.html. You will find
>> everything (or even more) you need there.
>
> Oh man, I have not even had the idea of looking into an output
> directory, I just expected it on the
Can you point me at the poms I should look at to see this?
Reinhard Poetz wrote:
Ralph Goers wrote:
Is the cocoon build really trying to rely on transitive dependency
verions? Very bad idea. Versions of every dependency cocoon uses
directly or indirectly should be specified in the managedDepen
Ralph Goers wrote:
Is the cocoon build really trying to rely on transitive dependency
verions? Very bad idea. Versions of every dependency cocoon uses
directly or indirectly should be specified in the managedDependencies.
The problem is that the groupId of the Avalon framework changed and that
Is the cocoon build really trying to rely on transitive dependency
verions? Very bad idea. Versions of every dependency cocoon uses
directly or indirectly should be specified in the managedDependencies.
Joerg Heinicke wrote:
Found this thread on the user list which has the same symptoms:
http
On 25.11.2007 23:47 Uhr, Joerg Heinicke wrote:
PS: There is also an error somewhere with the dependencies I think. XSP
block includes Avalon Framework 4.1.3 instead of 4.3.1 which causes
bunch of problems in Eclipse. How to trace the dependencies? Grek sent
once a mail with "mvn project-info-rep
