[jira] Commented: (CONTINUUM-574) Checkout failure in Windows

2006-01-31 Thread Ignacio G. Mac Dowell (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-574?page=comments#action_57419 
] 

Ignacio G. Mac Dowell commented on CONTINUUM-574:
-

Hi, this is not a bug. Using cvsnt you need to prefix your root repository 
location.

SCM tokenizes the scm url using ':' so your connection url is not correct as it 
has more tokens than expected.

try to google prefix cvsnt repository

best regards,

nacho


 Checkout failure in Windows
 ---

  Key: CONTINUUM-574
  URL: http://jira.codehaus.org/browse/CONTINUUM-574
  Project: Continuum
 Type: Bug

 Reporter: clojinted



 Hello there,
 I've just set up Continuum but the following command fails to check out the 
 project:
 mvn -e -DconnectionUrl=scm:cvs:pserver:username:[EMAIL 
 PROTECTED]:f:/cvs-repository:itraxspring scm:checkout 
 -DcheckoutDirectory=itraxspring
 This is part of the error message:
 [ERROR] BUILD ERROR
 [INFO] ---
 [INFO] Cannot run checkout command :
 Embedded error: Can't load the scm provider.
 For input string: f
 I'm using cvsnt so I logged in manually but the problem still arises.
 Any help would be greatly appreciated,
 Ger

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (CONTINUUM-574) Checkout failure in Windows

2006-01-31 Thread Ignacio G. Mac Dowell (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-574?page=comments#action_57426 
] 

Ignacio G. Mac Dowell commented on CONTINUUM-574:
-

Hi, it will save you a lot of headaches to prefix your windows repository 
location. It's easy and your cvs server will be more unix-like. You'll find 
help on any other issues that may arise regarding cvs much easier as well.

If you are using the latest cvsnt version, repositories are given a unix-like 
name (without f: in your case) by default. In other versions is simple as well. 
If you need further assistance don't hesitate to contact me privately.

best regards

nacho 

 Checkout failure in Windows
 ---

  Key: CONTINUUM-574
  URL: http://jira.codehaus.org/browse/CONTINUUM-574
  Project: Continuum
 Type: Bug

 Reporter: clojinted



 Hello there,
 I've just set up Continuum but the following command fails to check out the 
 project:
 mvn -e -DconnectionUrl=scm:cvs:pserver:username:[EMAIL 
 PROTECTED]:f:/cvs-repository:itraxspring scm:checkout 
 -DcheckoutDirectory=itraxspring
 This is part of the error message:
 [ERROR] BUILD ERROR
 [INFO] ---
 [INFO] Cannot run checkout command :
 Embedded error: Can't load the scm provider.
 For input string: f
 I'm using cvsnt so I logged in manually but the problem still arises.
 Any help would be greatly appreciated,
 Ger

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (CONTINUUM-574) Checkout failure in Windows

2006-01-31 Thread clojinted (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-574?page=comments#action_57427 
] 

clojinted commented on CONTINUUM-574:
-

I have it working now. I did just that and renamed the repository. 

Thanks very much for all the help.

Ger

 Checkout failure in Windows
 ---

  Key: CONTINUUM-574
  URL: http://jira.codehaus.org/browse/CONTINUUM-574
  Project: Continuum
 Type: Bug

 Reporter: clojinted



 Hello there,
 I've just set up Continuum but the following command fails to check out the 
 project:
 mvn -e -DconnectionUrl=scm:cvs:pserver:username:[EMAIL 
 PROTECTED]:f:/cvs-repository:itraxspring scm:checkout 
 -DcheckoutDirectory=itraxspring
 This is part of the error message:
 [ERROR] BUILD ERROR
 [INFO] ---
 [INFO] Cannot run checkout command :
 Embedded error: Can't load the scm provider.
 For input string: f
 I'm using cvsnt so I logged in manually but the problem still arises.
 Any help would be greatly appreciated,
 Ger

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



Fwd: [ANN] Apache JDO 2.0 beta released

2006-01-31 Thread Brett Porter
we should switch to this - not sure if its in the repo yet.

- Brett

-- Forwarded message --
From: Craig L Russell [EMAIL PROTECTED]
Date: Feb 1, 2006 5:47 AM
Subject: [ANN] Apache JDO 2.0 beta released
To: general@db.apache.org
Cc: JDO Expert Group [EMAIL PROTECTED], Apache JDO project
jdo-dev@db.apache.org


The Apache JDO project http://db.apache.org/jdo is pleased to announce
the release of Apache JDO 2.0 beta, a preview release of Apache JDO 2.0.
Apache JDO is a subproject of the Apache DB project.

JDO is a JCP standard interface for persistence of Java objects.
It is datastore-agnostic and supports relational and non-relational
databases. For details, please see http://jcp.org/en/jsr/detail?id=243

The Apache JDO project builds the JDO API jars used by application
programmers and the JDO TCK jars, used to verify compliance with
the specification. The Apache JDO project does not build an implementation
of JDO 2.0. The JDO 2.0 Reference Implementation is JPOX,
which is available via its own download: http://jpox.org

Apache JDO API and TCK are available as a source download from mirrors
http://www.apache.org/dyn/closer.cgi
/db/jdo/2.0-beta. The jar files are available in binary form as maven form
from mirrors /java-repository/javax.jdo and
/java-repository/org.apache.jdo

JDO 2.0 builds on the JDO 1 API. Applications built to use JDO 1 need only
to be recompiled to run with JDO 2.0.

Features in the JDO 2.0 release include:

- Standard mapping from objects to relational databases
- Multi-tier support without use of Data Transfer Objects
- Improved query support including projections and aggregates
- Stored queries in metadata
- Deletion by query
- Optimized fetching of object graphs without writing special queries
- Extensive List and Map support
- Lazy loading of large collections
- Better support for single-field primary keys
- Object lifecycle event monitoring
- Improved support for bidirectional relationships




Craig Russell

Architect, Sun Java Enterprise System http://java.sun.com/products/jdo

408 276-5638 mailto:[EMAIL PROTECTED]

P.S. A good JDO? O, Gasp!


Re: Fwd: [ANN] Apache JDO 2.0 beta released

2006-01-31 Thread Emmanuel Venisse

it is there : http://www.ibiblio.org/maven2/javax/jdo/jdo2-api/2.0-beta/

Thanks. I'll switch.

Emmanuel

Brett Porter a écrit :

we should switch to this - not sure if its in the repo yet.

- Brett

-- Forwarded message --
From: Craig L Russell [EMAIL PROTECTED]
Date: Feb 1, 2006 5:47 AM
Subject: [ANN] Apache JDO 2.0 beta released
To: general@db.apache.org
Cc: JDO Expert Group [EMAIL PROTECTED], Apache JDO project
jdo-dev@db.apache.org


The Apache JDO project http://db.apache.org/jdo is pleased to announce
the release of Apache JDO 2.0 beta, a preview release of Apache JDO 2.0.
Apache JDO is a subproject of the Apache DB project.

JDO is a JCP standard interface for persistence of Java objects.
It is datastore-agnostic and supports relational and non-relational
databases. For details, please see http://jcp.org/en/jsr/detail?id=243

The Apache JDO project builds the JDO API jars used by application
programmers and the JDO TCK jars, used to verify compliance with
the specification. The Apache JDO project does not build an implementation
of JDO 2.0. The JDO 2.0 Reference Implementation is JPOX,
which is available via its own download: http://jpox.org

Apache JDO API and TCK are available as a source download from mirrors
http://www.apache.org/dyn/closer.cgi
/db/jdo/2.0-beta. The jar files are available in binary form as maven form
from mirrors /java-repository/javax.jdo and
/java-repository/org.apache.jdo

JDO 2.0 builds on the JDO 1 API. Applications built to use JDO 1 need only
to be recompiled to run with JDO 2.0.

Features in the JDO 2.0 release include:

- Standard mapping from objects to relational databases
- Multi-tier support without use of Data Transfer Objects
- Improved query support including projections and aggregates
- Stored queries in metadata
- Deletion by query
- Optimized fetching of object graphs without writing special queries
- Extensive List and Map support
- Lazy loading of large collections
- Better support for single-field primary keys
- Object lifecycle event monitoring
- Improved support for bidirectional relationships




Craig Russell

Architect, Sun Java Enterprise System http://java.sun.com/products/jdo

408 276-5638 mailto:[EMAIL PROTECTED]

P.S. A good JDO? O, Gasp!







Re: Fwd: [ANN] Apache JDO 2.0 beta released

2006-01-31 Thread Carlos Sanchez
Is it right to be in javax.jdo when the reference implementation seems
to be jpox?

On 1/31/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:
 it is there : http://www.ibiblio.org/maven2/javax/jdo/jdo2-api/2.0-beta/

 Thanks. I'll switch.

 Emmanuel

 Brett Porter a écrit :
  we should switch to this - not sure if its in the repo yet.
 
  - Brett
 
  -- Forwarded message --
  From: Craig L Russell [EMAIL PROTECTED]
  Date: Feb 1, 2006 5:47 AM
  Subject: [ANN] Apache JDO 2.0 beta released
  To: general@db.apache.org
  Cc: JDO Expert Group [EMAIL PROTECTED], Apache JDO project
  jdo-dev@db.apache.org
 
 
  The Apache JDO project http://db.apache.org/jdo is pleased to announce
  the release of Apache JDO 2.0 beta, a preview release of Apache JDO 2.0.
  Apache JDO is a subproject of the Apache DB project.
 
  JDO is a JCP standard interface for persistence of Java objects.
  It is datastore-agnostic and supports relational and non-relational
  databases. For details, please see http://jcp.org/en/jsr/detail?id=243
 
  The Apache JDO project builds the JDO API jars used by application
  programmers and the JDO TCK jars, used to verify compliance with
  the specification. The Apache JDO project does not build an implementation
  of JDO 2.0. The JDO 2.0 Reference Implementation is JPOX,
  which is available via its own download: http://jpox.org
 
  Apache JDO API and TCK are available as a source download from mirrors
  http://www.apache.org/dyn/closer.cgi
  /db/jdo/2.0-beta. The jar files are available in binary form as maven form
  from mirrors /java-repository/javax.jdo and
  /java-repository/org.apache.jdo
 
  JDO 2.0 builds on the JDO 1 API. Applications built to use JDO 1 need only
  to be recompiled to run with JDO 2.0.
 
  Features in the JDO 2.0 release include:
 
  - Standard mapping from objects to relational databases
  - Multi-tier support without use of Data Transfer Objects
  - Improved query support including projections and aggregates
  - Stored queries in metadata
  - Deletion by query
  - Optimized fetching of object graphs without writing special queries
  - Extensive List and Map support
  - Lazy loading of large collections
  - Better support for single-field primary keys
  - Object lifecycle event monitoring
  - Improved support for bidirectional relationships
 
 
 
 
  Craig Russell
 
  Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
 
  408 276-5638 mailto:[EMAIL PROTECTED]
 
  P.S. A good JDO? O, Gasp!
 
 
 




[continuum build - FAILED - checkout] Wed Feb 1 01:30:00 GMT 2006

2006-01-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060201.013001.txt


[continuum build - FAILED - update] Wed Feb 1 02:30:00 GMT 2006

2006-01-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060201.023000.txt


[continuum build - FAILED - update] Wed Feb 1 03:00:00 GMT 2006

2006-01-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060201.03.txt


[continuum build - FAILED - update] Wed Feb 1 03:30:00 GMT 2006

2006-01-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060201.033000.txt