Thomas Vandahl wrote:
Scott Eade wrote:
I would also like to rm -rf the turbine m1 repo - please take a look
and let me know if you feel you can justify its continued existence.
There are a couple of things which are not available elsewhere nor
could I find the source of them. Some Hibernate-Avalon libs used in
Fulcrum-Security come to my mind. I'd ask to carefully check before
blowing this up.
And that is a good justification. I would comment though that depending
on such jars is not a very good situation and will rapidly become a
blocker to transitioning to m2. If we are relying on jars that are not
in the main repositories we need to take action to organise for them to
be available.
I have cleared out everything that is available in the main m1 repository.
I get the impression that we are overusing the "provided" scope in
our poms - comments?
I'm not really sure how to handle dependencies in Maven2 correctly at
all. My impression is that not many artifacts have a decent dependency
management so that you spent lots of time "excluding" stuff that comes
in through inherited deps. I have yet to make my applications build
with M2 and contain the same dependencies as before...
It certainly seems to add complexity without resolving all possible
dependency problems. All we can do is try and configure the scope and
optional tags correctly ourselves and hope that others will do the same.
Yes, it is often necessary to add exclusions to strip out dependencies
that we know we do not need.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
