ENGAGE-70: The fluid-all externals are named ambiguously and the Eclipse projects for engage-server and engage-client are incorrectly named

Metadata

Source
ENGAGE-70
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Colin Clark
Reporter
Colin Clark
Created
2009-09-16T15:38:29.000-0400
Updated
2009-11-23T15:21:31.000-0500
Versions
N/A
Fixed Versions
  1. 0.3b
Component
  1. Kettle
  2. Mobile

Description

At the moment, the externals in fluid all are named like this:

engage/ -> the client-side for Engage (JS code, components etc.)
kettle/ -> the server-side for Engage, including the server-side portions of the Artifact VIew component and Kettle

These should be renamed:

engage-client/
engage-server

Also, the Eclipse projects for both are misleading. Here's how they should be renamed:

MobileFSS -> fluid-engage-client
fluid-engage-sketches -> fluid-engage-server

Comments

  • Antranig Basman commented 2009-10-05T11:50:43.000-0400

    Some experimentation shows that it is unreliable to name directories differently to project files within Eclipse - so to ensure consistency, the externals, as well as the project names align. It should not be necessary to rename the base SVN paths themselves - from the channel today:

    (09:18:05) colinclark: So we're all on the same page, you proposal is:

    (09:18:14) colinclark: fluid-all/
    (09:18:31) colinclark: fluid-infusion/ -> https://source.fluidproject.org/svn/fluid/infusion
    (09:19:15) colinclark: fluid-engage-client/ -> http://source.fluidproject.org/svn/incubator/engage-client/trunk/
    (09:19:33) colinclark: fluid-engage-server/ -> http://source.fluidproject.org/svn/incubator/engage-sketches/
    (09:20:00) colinclark: And to go with this, we'll ensure that the client and server directories are properly named when we promote them from the incubator to core.

    (09:18:13) Bosmo1: But we would have to make sure that any project "cross-links" were made assuming the fluid- prefix was in place
    (09:18:36) Bosmo1: So, I left some things behind in the ENGAGE-96 work that still assume the "inter-project relative path" is simply "infusion"

  • Justin Obara commented 2009-10-05T18:48:49.000-0400

    Bug Parade Engage 0.1

  • Michelle D'Souza commented 2009-10-19T12:32:13.000-0400

    When this is done, the build scripts for Engage will need to be updated