On 12-Feb-09, at 8:49 AM, Paul Benedict wrote:
Oleg, thank you for volunteering. j/k
My only concern is that building a project successfully does not
guarantee backwards compatibility. Things like property resolution,
etc. need to either be eye balled or loaded into an application to
show it works or bombs.
Mmmm, that's would be where your integration tests kick in.
Binaries, sure, maybe that's overkill. But if I can compare the
target/war-output directory between two builds, that would help :-)
Paul
On Wed, Feb 11, 2009 at 9:54 PM, Jason van Zyl
<[email protected]> wrote:
On 11-Feb-09, at 10:28 PM, Oleg Gusakov wrote:
I have a tool that compares resolved dependency lists between
Mercury and
Maven2, not binaries. Will not be hard to modify to add binary
comparison.
There you go, Oleg will check them for you :-)
Paul Benedict wrote:
Does any tool exist that can build a project in Maven 2 and Maven 3
and then compare the binaries to see if they are equal? Assuming
v3 is
fully backwards compatible with v2, I hope there would be only
superficial differences.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.
-- Eric Hoffer, Reflections on the Human Condition
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
