facebook

Deploying with dependent projects seems to forget projects

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #220336 Reply

    jkara
    Member

    I’m running MyEclipse 3.8.2 and am having some problems with deployment to Tomcat 5.5. I’ve searched around on the forums and haven’t found a definitive answer.

    My workspace structure is basically this:
    Project A – (just some jars)
    Project B – References A, and contains code and config files, exports itself and Project A
    Project C – Is a web-app project, which reference Project B. This deploys correctly, including Project A and B
    Project D – Is a web-app project that is based upon the code of Project C, but a completely different user interface. I would like to reference Project C, and thus be able to inherit Project A, Project B and all of the code for Project B.

    Is this possible, or is the fact that Project C is also a web-application going to prevent the deployment of java classes from Project C reaching Project D?

    #220337 Reply

    Riyad Kalla
    Member

    Is this possible, or is the fact that Project C is also a web-application going to prevent the deployment of java classes from Project C reaching Project D?

    Not currently support and bingo. We had another user request something like this recently… we may look into dependent web projects for 3.9 or 4.0.

    Can you better explain how you would envision MyEclipse should handle deploying D when it will obviously contain elements that overlap with C? Should all the D elements just simply overwrite the C elements? (e.g. web.xml, struts-config.xml ,etc.)

    #220343 Reply

    jkara
    Member

    I don’t recall the actual topic, or user that started it. However, I do agree with his idea, in that the projects could NOT contain circular references, and it is a stacking effect. So, Project D would overwrite anything that existed in Project C, and so on.

    I believe this behavior would be very intuitive for developers as the behavior would be conceptually similar to how the classpath works.

    As an aside, I don’t really want all of the other web-app related code (web.xml, jsps, etc.). I just want to be able to access the java classes implemented within Project C, without having to pull it out into a separate project. So, an option to include (not include) web-content would also be nice.

    Thanks

    #220346 Reply

    Riyad Kalla
    Member

    I will add your comments to the request.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Deploying with dependent projects seems to forget projects

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