fulcrum-yaafi / fulcrum-testcontainer

[seade]

yaafi and testcontainer have inconsistent builds between m1 and m2, with
different version numbers, dependencies and test failures.

The longer we try and keep the m1 builds around the longer we will have
inconsistencies such as these.  I suggest we consign the m1 project
descriptors to the scrap heap and only support m2 from here on.

Can we look at releasing a version of fulcrum-parent sooner rather than
later?

yaafi has a dependency jamon:jamon:jar:2.7.0 - I believe this should
actually be com.jamonapi:jamon:jar:2.7 and this really needs to be
available in the m2 repository (I don't think we could allow a release
without jamon being automagically available).

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.

I get the impression that we are overusing the "provided" scope in our
poms - comments?

Scott


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Thomas Vandahl-2]

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.

> 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...

Bye, Thomas.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[seade]

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: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Siegfried Goeschl]

Hi Scott,

see my comments below

Siegfried Goeschl

Scott Eade wrote:
> yaafi and testcontainer have inconsistent builds between m1 and m2,
> with different version numbers, dependencies and test failures.
>
I'm currently bootstrapping the m2 build and the different versions were
used to separate my test builds from proper artifacts more cleanly but
it is currently work in progress
> The longer we try and keep the m1 builds around the longer we will
> have inconsistencies such as these.  I suggest we consign the m1
> project descriptors to the scrap heap and only support m2 from here on.
>
> Can we look at releasing a version of fulcrum-parent sooner rather
> than later?
No problem with releasing - I will start a discussion about it tommorrow
>
> yaafi has a dependency jamon:jamon:jar:2.7.0 - I believe this should
> actually be com.jamonapi:jamon:jar:2.7 and this really needs to be
> available in the m2 repository (I don't think we could allow a release
> without jamon being automagically available).
Cool - I did not know that JAMON artifacts are available on M2 repo - I
will pick jamon-2.4.jar
>
>
> 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.
>
> I get the impression that we are overusing the "provided" scope in our
> poms - comments?
>
Mhmm, what I tried to do was to separate required from optional jars but
I was not aware of the <optional> thingie in m2 - I will check tommorrow
> Scott
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...