 |
|
|
 |
|
 |
|
| Author |
Message |
|
|
Post subject: Library Deployment Policies not honoured
 Posted: Jan 22, 2009 - 09:14 PM
|
|
Registered Member
Joined: Jan 22, 2009
Posts: 16
|
|
I have several projects that are referenced by my web application. Each of those projects reference user libraries and I have set my library policy in my webapp to include Jars in the dependent projects. However, those jars never get deployed with my app.
Am I missing something? |
|
|
| |
|
|
|
 |
|
|
|
Post subject: Yes, I was missing something
Posted: Jan 22, 2009 - 09:18 PM
|
|
Registered Member
Joined: Jan 22, 2009
Posts: 16
|
|
I never clued into the whole "exported" keyword. When I set my user library to be exported in my dependent project, my jars got included in the deployment. |
|
|
| |
|
|
|
|
|
|
|
Post subject: A web project can't be exported
Posted: Jan 22, 2009 - 10:22 PM
|
|
Registered Member
Joined: Jan 22, 2009
Posts: 16
|
|
I finally found the culprit to my problem. One of my dependent projects was marked as a web project. It seems that myEclipse does not export the compiled classes of a dependent web project. I had to remove the web capabilities and then my classes were deployed into my main webapp.
Is this by design? |
|
|
| |
|
|
|
|
|
|
|
Post subject: RE: A web project can
Posted: Jan 26, 2009 - 07:15 PM
|
|
Registered Member
Joined: Apr 18, 2007
Posts: 8013
|
|
| Quote: |
Is this by design?
|
Yes. The dependent project should be a Java Project with the libraries. |
_________________
Nipun
MyEclipse Support
|
| |
|
|
|
|
|
|
| |
|
|
 |
|
 |
|
|
|
|
Search
Register
Log in to check your private messages
