facebook

Problem with jar and smart deployment of dependent projects

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

    prisoner
    Member

    We recently upgraded some of our developers from 3.8.2 to 3.8.4. Those on 3.8.4 discovered that some dependent projects named things such as “foo.bar.baz” were being deployed (either through jar or smart deployment) into the lib directory using this exact name. Other projects, even in the same workspace, correctly have a .jar added to them.

    We are not seeing this with 3.8.2. All developers are using Windows and JDK 1.4.2.

    #229909 Reply

    Riyad Kalla
    Member

    This was a new feature added to 3.8.4 to support custom project deployments for app servers that support specially named projects, like JBoss and it’s support for RAR, SAR, LAR, BLAR, etc. etc. files. This way if you have a dot in your project name, MYEclipse will honor the name of the project and deploy it appropriately, so for example:

    Persistence.sar

    will ge deployed correctly as a SAR file to JBoss, as opposed to the old way which made it Persistence.sar.jar which caused it not to be found or loaded by the app server.

    #229928 Reply

    prisoner
    Member

    I take it there is no way to override this behaviour and our only recourse is to rename the project?

    #229930 Reply

    Riyad Kalla
    Member

    There is currently no way to override the behavior we are sorry for the inconvenience and certainly have that enhancement filed. Alternatively you could add the .jar extension to the name of the projects, that should work around the issue.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Problem with jar and smart deployment of dependent projects

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