Hi Matthew,

In my workspace, here's what trunk/api20/project.xml is. I see this both from vi and from Netbeans. By the way, I changed <name> from JDO 2.0 API because the generated javadoc was adding API 2.0 to the end, resulting in JDO 2.0 API API 2.0 as the generated name.

I don't know whether your checkout/update is wrong or if I checked in something wrong...

Does this not look like yours? My file has only 77 lines in it...

Thanks,

Craig


<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2005 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at


http://www.apache.org/licenses/LICENSE-2.0


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->

<project>
<pomVersion>3</pomVersion>
<extend>../project.xml</extend>
<!-- ============== -->
<!-- Identification -->
<!-- ============== -->
<name>JDO</name>
<artifactId>jdo-api</artifactId>
<currentVersion>2.0</currentVersion>
<package>javax.jdo</package>
<shortDescription>Java Data Object (JDO) API 2.0</shortDescription>
<description>The Java Data Objects (JDO) API is a standard interface-based
Java model abstraction of persistence, developed as Java Specification
Request 243 under the auspices of the Java Community Process.</description>
<repository />
<!-- ============ -->
<!-- Dependencies -->
<!-- ============ -->
<dependencies>
<dependency>
<groupId>geronimo-spec</groupId>
<artifactId>geronimo-spec-jta</artifactId>
<version>1.0.1B-rc2</version>
</dependency>
</dependencies>
<!-- =================== -->
<!-- Build Specification -->
<!-- =================== -->
<build>
<sourceDirectory>src/java</sourceDirectory>
<unitTestSourceDirectory>test/java</unitTestSourceDirectory>
<!-- Unit test cases -->
<unitTest>
<includes>
<include>**/*Test.java</include>
</includes>
<excludes>
<exclude>javax/jdo/util/AbstractTest.java</exclude>
<exclude>javax/jdo/pc/*.java</exclude>
</excludes>
</unitTest>
<!-- J A R R E S O U R C E S -->
<!-- Resources that are packaged up inside the JAR file -->
<resources>
<resource>
<directory>${basedir}/src/java</directory>
<includes>
<include>javax/jdo/*.properties</include>
</includes>
</resource>
<resource>
<directory>${basedir}/src/dtd</directory>
<includes>
<include>javax/jdo/*.dtd</include>
</includes>
</resource>
</resources>
</build>
</project>

On Mar 28, 2005, at 2:04 PM, Matthew T. Adams wrote:

It appears as though the file trunk/api20/project.xml is now broken.
Can you have a look & fix, please? It looks like you have two copies of
a <project> in it with some non-xml characters. Looks kind of like a
diff. See lines 78 and on.

Thanks,
Matthew

-----Original Message-----
From: Craig Russell [mailto:[EMAIL PROTECTED]
Sent: Monday, March 28, 2005 12:10 PM
To: JDO Expert Group
Cc: jdo-dev@db.apache.org
Subject: JDO 2.0 API project checked in


Javadogs,

I've just checked in the JDO 2.0 API project into Apache. You can now
check out and build the jdo.jar for 2.0. Take a look at
http://wiki.apache.org/jdo for instructions on how to access the
repository.

Thanks to Michael Bouschen for his invaluable assistance on the
repository and maven.

If you have any issues, bugs, or comments, please post them on the
Apache JDO JIRA. If you don't know how to use the JIRA, you can send
them to the jdo-dev alias. This is a first checkin, so I don't expect
everything to be perfect. But I hope it's close.

Craig

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!




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!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to