Question #2 seems to be on the track: everything in
JBOSS_HOME/server/default/deploy/nuxeo.ear/plugins was
version 1.1, with a date of January 19th.

Just ran ant deploy from services/trunk/services and we now have 1.7
versions of all jars, including group. Restarting nuxeo now.

On Thu, Jun 2, 2011 at 12:37 PM, Aron Roberts aron@socrates.berkeley.eduwrote:

Hi Joe,

Good to hear progress is being made!

Quick question; did you explode both tarballs from the FTP server, or
only the cspace one?

Thanks,

Kasper
On 06/02/2011 01:23 PM, Joe Slag wrote:

Yes, I just doublechecked and there are files in my jboss dir that are only
found in the jboss-4.2.3.GA-default-5.3.2.tar.gz tarball.

On Thu, Jun 2, 2011 at 1:32 PM, Kasper Galschiot Markus
kasper2@markus.dkwrote:

OK, once nuxeo and cspace started up, the group problem seems to have
resolved itself -- the groups_common table is there now, and I'm not seeing
any group-related errors.

However, the collectionspace_core table is still out of whack:

mysql> describe collectionspace_core;
+-----------+--------------+------+-----+---------+-------+
| Field    | Type        | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| id        | varchar(36)  | NO  | PRI | NULL    |      |
| updatedat | datetime    | YES  |    | NULL    |      |
| createdat | datetime    | YES  |    | NULL    |      |
| tenantid  | varchar(500) | YES  |    | NULL    |      |
+-----------+--------------+------+-----+---------+-------+
4 rows in set (0.00 sec)

And presumably as a consequence, I'm still getting a bunch of errors when
trying to initialize vocabularies.

Patrick, I did check services out from the 1.7 tag, as you can see here:

v1.7/services$ svn info
Path: .
URL:
https://source.collectionspace.org/collection-space/src/services/tags/v1.7/services
Repository Root: https://source.collectionspace.org/collection-space
Repository UUID: 632a04b0-194a-439a-a497-68f405da15a8
Revision: 4898
Node Kind: directory
Schedule: normal
Last Changed Author: laramie
Last Changed Rev: 4865
Last Changed Date: 2011-05-25 02:38:15 -0500 (Wed, 25 May 2011)

Wondering if there might have been something missing from the 1.7 tag that
was in the branch, I did notice the following -- possibly related?

svc/v1.7$ svn diff
https://source.collectionspace.org/collection-space/src/services/branches/v1.7
https://source.collectionspace.org/collection-space/src/services/tags/v1.7
Index: services/taxonomy/build.xml

---=
--- services/taxonomy/build.xml (.../branches/v1.7)    (revision 4899)
+++ services/taxonomy/build.xml (.../tags/v1.7) (revision 4899)
@@ -117,6 +117,7 @@
<target name="dist" depends="package" description="distribute taxonomy service">
<ant antfile="3rdparty/build.xml" target="dist" inheritall="false"/>

•    <ant antfile="import/build.xml" target="dist" inheritall="false"/>
  

  </target>

  <target name="dist_installer" depends="package"
  @@ -126,6 +127,7 @@
  <fileset dir="${basedir}/installer/"/>
  </copy>
  <ant antfile="3rdparty/build.xml" target="dist_installer" inheritall="false"/>

•    <ant antfile="import/build.xml" target="dist_installer"
  

inheritall="false"/>
</target>

On Thu, Jun 2, 2011 at 1:23 PM, Joe Slag joe@slagwerks.com wrote:

At 13:51 -0500 2011-06-02, Joe Slag wrote:

Regarding this: Kasper discovered a bug in the recently-added
Taxonomy service, in the services 1.7 tagged release, in which a
non-existent 'import' folder was referenced in an Ant buildfile
(below).

This was fixed in a change made in services trunk and to the 1.7
release branch, and a new 1.7.1 tag was created
(https://source.collectionspace.org/collection-space/src/services/tags/v1.7https://source.collectionspace.org/collection-space/src/services/tags/v1.7.1)
from the updated 1.7 release branch specifically to include that one
fix.

To the best of my knowledge, you'd encounter that bug only if you
ran 'ant dist', or a target that depended on 'dist', such as 'ant
dist-jboss-domains.'  I don't believe this would have anything to do
with deployment, or with the possible collectionspace core schema
discrepancy you've mentioned.

Aron