Uploaded image for project: 'Forge: MOP'
  1. Forge: MOP
  2. MOP-45

MOP repository does not seem to be updated properly. Stale meshkeeper bits stay around.

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Environment:

      Windows XP SP2 Sun Java 1.5.0_17

      Description

      I seem to be having an issue where the MOP repository is not being updated with latest bits from fusesource repo or my local Maven repo. To prove this point, Colin put an updated meshkeeper-api-1.0-SNAPSHOT jar on the fusesource repo. Running my test did not pick up the new bits. So I made a change locally to Meshkeeper, rebuilt it, and reran my test. The change was not picked up.

      I can workaround by deleting my meshkeeper folder in my MOP repo for now.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jjacobs1 Jean Jacobs
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: