I'm pretty sure the JPA tests fail because of line ending issues. I
think the test suite was written on a *nix system and won't load
properly on Windows. I'd have to double-check this. There was a
thread about this around 3.0M3 or 3.0M4.
--
Kevin
On Wed, Dec 10, 2008 at 10:02 AM, Andrus Ada
>
> The JPA tests do not run in Windows. This is a known issue. You need
>
to run with -DskipTests=true in order to build/install those
>
artifacts.
>
Great, I see it now! Personally I don't need those artifacts, I just wanted
to set up everything to avoid in future yesterday situation, when I b
On Dec 10, 2008, at 4:56 PM, Kevin Menard wrote:
The JPA tests do not run in Windows. This is a known issue. You need
to run with -DskipTests=true in order to build/install those
artifacts.
Or one can investigate why it fails :-)
When packaging up 3.0M5, I also had problems with the Windo
The JPA tests do not run in Windows. This is a known issue. You need
to run with -DskipTests=true in order to build/install those
artifacts.
When packaging up 3.0M5, I also had problems with the Windows profile.
It is looking for a missing modeler-win directory. Renaming the
modeler directory
Doh, we have instructions for this already (see "Windows Woes" down
the middle of that page)
http://cayenne.apache.org/building-cayenne.html
I totally forgot about this... although it says the issue is fixed in
surefire 2.4. Go figure :-/
Anyways does this approach work for you?
Andrus
Seems that's because maven repo path contains spaces:
http://mail-archives.apache.org/mod_mbox/tuscany-dev/200808.mbox/[EMAIL
PROTECTED]
2008/12/10 Andrus Adamchik <[EMAIL PROTECTED]>
> Got the same error on Windows. Sure enough everything works ok on Mac :-/
> Will need to investigate...
>
> An
Got the same error on Windows. Sure enough everything works ok on
Mac :-/ Will need to investigate...
Andrus
On Dec 10, 2008, at 3:10 PM, Andrey Razumovsky wrote:
Sorry, I misprinted - i'm doing exactly "mvn clean install". BTW I
had the
JAR in my repo in exact same path
2008/12/10 Andrus
Sorry, I misprinted - i'm doing exactly "mvn clean install". BTW I had the
JAR in my repo in exact same path
2008/12/10 Andrus Adamchik <[EMAIL PROTECTED]>
> Hi Andrey,
>
> Could you try "mvn clean install" instead of "mvn clean build"? I think
> cayenne-agent is bootstrapped from the Maven repo
Hi Andrey,
Could you try "mvn clean install" instead of "mvn clean build"? I
think cayenne-agent is bootstrapped from the Maven repo during the
build.
Andrus
On Dec 10, 2008, at 2:55 PM, Andrey Razumovsky wrote:
I finally found the problem - I had to put proxy's connection
settings in
I finally found the problem - I had to put proxy's connection settings in
Maven's settings.xml.
But now I get the following problem when I try to do 'maven clean build'. I
tried with Java 5 and 6, Maven 2.0.9. I searched for similiar problems, it
seems many projects got them, but I didn't find the
BTW, I almost feel like we should setup our own Maven repo on
objectstyle.org and block the main one. This will guarantee consistent
builds. I wish the repo managers out there were a bit more user-
friendly though. I am using Artifactory for commercial development. It
serves its purpose, but
These are coming from the ObjectStyle repo:
http://objectstyle.org/maven2/
There's a little hack involved in setting it up. To prevent checking
this repo for the artifacts that are not there (99% of them) and speed
up things, instead of adding it to the top level pom I placed it under
"bui
12 matches
Mail list logo
