facebook

Invalid deployment target [Closed]

  1. MyEclipse Archived
  2.  > 
  3. UML Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #232863 Reply

    kinjalsonpal
    Member

    Hi there.

    Today I downloaded and installed eclipse 3.1. Then downloaded and installed myeclipseide 4.0M2. Following is config details in brief:

    ——
    WinXP Pro SP1
    P4 – 383MB RAM
    ——
    java version “1.5.0_02”
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
    Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode, sharing)
    ——
    Tomcat version: Apache Tomcat/5.5.9
    Tomcat built: Mar 26 2005 02:21:04
    Tomcat number: 5.5.9.0
    ——
    Eclipse SDK

    Version: 3.1.0
    Build id: I20050627-1435
    ——
    MyEclipse JSF Support

    Version: 3.9.210
    Build id: 20050627-4.0-Milestone-2
    ——-

    After configuring Tomcat Server entry in ME, I imported my existing project (from ME3.8.4). Went smooth.

    In New Deployment dialog, selected Tomcat 5 as deployment target. Deloy Location is empty and Finish button disabled for Exploded Archive. Selected Packaged Archive option, Finish is enabled, clicking on it doesn’t seem to do anything. Snaps back to previos dialog with deployment status as Out of Date and still empty location. Instead of clicking on Finish, if I choose Exploded Archive again, Finish remains enabled but there’s a validation error (at the top of the page) saying ‘Undefined exploded archive location’.

    Pl. help out.

    Thanks and regards,
    Kinjal Sonpal

    #232875 Reply

    Scott Anderson
    Participant

    In New Deployment dialog, selected Tomcat 5 as deployment target. Deloy Location is empty and Finish button disabled for Exploded Archive.

    I ran into an issue with this yesterday that we need to investigate. Basically what happened was that the .mymetadata file (see in Navigator view) became invalid due to the import. Simply dragging and dropping the original file from the Windows Explorer into the workbench and refreshing should resolve the issue. The specific problem was that the context-root entry was removed and the webroot-dir was changed to be invalid. We’ll get it fixed in the next build. Sorry for the inconvenience.

    #232958 Reply

    kinjalsonpal
    Member

    Bingo ! After dropping the file, I just restarted ME and I was on my way.

    Thanks and regards,
    Kinjal

    #273827 Reply

    alex.king
    Member

    I am using ME 6.0.0. And it still has this problem.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Invalid deployment target [Closed]

You must be logged in to post in the forum log in