Dan Becker wrote:
Also FWIW, I updated and am building successfully also.
ant elder wrote:
Just as a FWIW with all the recent build problems, a clean build for me
right now everything is building fine with no errors
It does not build for me from an empty maven repo. This is caused by
some changes within downloaded eclipse poms that have created an
incompatibility between the poms for org.eclipse.core:runtime and
org.eclipse.equinox:app (see [1]). I fixed this by "hacking" the
org.eclipse.core:runtime pom in my local repo to change the dependency
version for org.eclipse.equinox:app to a specific version rather than
a range, but this does not feel like a good solution.
[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg00572.html
Simon
...ant
On Tue, Aug 5, 2008 at 12:11 PM, Simon Laws
<[EMAIL PROTECTED]>wrote:
On Tue, Aug 5, 2008 at 11:37 AM, Mike Edwards <
[EMAIL PROTECTED]> wrote:
Folks,
Today - 11:00am UK time - I updated from trunk and then built and I get
none of the errors listed in this thread. I do get an error - but
it is in
one of the itests: validation
Failed tests:
testCalculator(binding.jms.DoesntProcessHeadersTestCase)
I've attached the detailed failure info at the bottom of this note,
since
it's so long.
If anyone can work out why it fails, I'd appreciate knowing...
I'm using Windows XP, Sun JDK 1.6.0_06 and Maven 2.0.8.
If there is one thing I would like to whinge about it's that this
testcase
(itest\validation) contains a load of actual tests and that working out
what's failed is a pain. Why do we have to have a test like this,
which is
in fact a very large pile of "subtests"?
Yours, Mike.
Simon Nash wrote:
I did a complete checkout and build from the latest trunk. The build
failed with the following error. Rerunning the build gave the same
error, so it's not a transient maven repo problem. Any ideas?
Simon
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache Tuscany SCA Extensibility for Eclipse Equinox
[INFO] task-segment: [install]
[INFO]
Mike
I think Ant just fixed this one.
Re. the tests, what would you prefer? All the tests within a single
JUnit
test?
Simon
