facebook

Dependent libraries not deployed

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

    I have a single web project that has two dependent java projects. I have all the library deployment options selected, which I assume should deploy the jars on my dependent projects’ build paths. However, when I deploy the web project, it does not deploy the jars of the other projects, while it does deploy the dependent projects’ class files.

    I have tried undeplying and redeploying several times but I never get the jars.

    Anything I can do to automate the procedure, short of adding the dependent jars to the web projects build path? I don’t want to do that, since the auto deployment is actually working for another developer on my team and I don’t want to mess up the .classpath files to work around this.

    Thanks.
    Robin.

    p.s. here’s my machine config:
    *** Date: Thu Jan 05 11:00:44 EST 2006

    *** System properties:
    OS=WindowsXP
    OS version=5.1
    Java version=1.5.0_06

    *** MyEclipse details:
    MyEclipse Enterprise Workbench

    Version: 4.0.200 M2
    Build id: 20051205-4.1-Milestone2

    *** Eclipse details:
    Eclipse SDK

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse Platform

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse RCP

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse Java Development Tools

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse Plug-in Development Environment

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse Project SDK

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -launcher
    C:\eclipse\eclipse.exe
    -name
    Eclipse
    -showsplash
    600
    -exitdata
    154_68
    -vm
    C:\WINDOWS\system32\javaw.exe

    #244068 Reply

    I had the other developer check again and his jars are not getting deployed.

    Are dependent projects’ jars suposed to get automatically deployed or is this just wishful thinking?

    THanks.
    Robin.

    #252739 Reply

    Is anyone out there?

    I have a follow-up that is related. Why are the J2EE Library Container jars not deployed with the web-app that has them referenced in its build path? Do I need to manually insert every jar I want, as opposed to using the myEclipse packaged jars, which get added automatically when making a web project?

    #252751 Reply

    Check the preference page MyEclipse/J2EE Project/Web Project -> Deployment. There is a group of checkboxes named “Library Deployment Policies”. Check respective checkboxes to get referenced jars deployed. In 5.0.0M1 these checkboxes are checked by default so you are unlikely to encounter such issues.

    #252776 Reply

    Thanks for the response but I guess I should have offered more detail – I have all the checkboxes checked. And since my original post, I have upgraded to myEclipse 4.1.1GA under Eclipse 3.1.1.

    To get around my orginal problem of being unable to deploy jars in dependent-projects’ build paths, I folded those projects into my web-app. However, my current question still stands: should I expect that jars listed under the myEclipse J2EE 1.4 Library Container be deployed automatically? In particular, the activation.jar is included in the myEclipse plugin but does not get deployed. I assume deployment takes only the jars it finds in the lib folder and will not include the jars from the myEclipse plugin folder?

    I just need to know the expected behaviour, so I know whether to just include the jars in my web-app directly and not use the myEclipse library, to import those jars from the external plugins directory.

    Thanks.

    #252778 Reply

    @maplesoft wrote:

    Thanks for the response but I guess I should have offered more detail – I have all the checkboxes checked. And since my original post, I have upgraded to myEclipse 4.1.1GA under Eclipse 3.1.1.

    To get around my orginal problem of being unable to deploy jars in dependent-projects’ build paths, I folded those projects into my web-app. However, my current question still stands: should I expect that jars listed under the myEclipse J2EE 1.4 Library Container be deployed automatically? In particular, the activation.jar is included in the myEclipse plugin but does not get deployed. I assume deployment takes only the jars it finds in the lib folder and will not include the jars from the myEclipse plugin folder?

    I just need to know the expected behaviour, so I know whether to just include the jars in my web-app directly and not use the myEclipse library, to import those jars from the external plugins directory.

    Thanks.

    I’m sorry, I thought your problem is another one common problem 🙂
    J2EE 1.4 library container is not deployed to an app. server as it is expected that those classes will be provided by the application server itself.

    #252779 Reply

    Thanks, that’s what I figured. Tomcat 5.5 doesn’t include the activation.jar.

    Thanks.

Viewing 7 posts - 1 through 7 (of 7 total)
Reply To: Dependent libraries not deployed

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