|
| Re: Simple question about deployment assembly [message #1279241 is a reply to message #1278757] |
Fri, 28 March 2014 12:53  |
 Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
On 3/28/2014 8:23 AM, William Phillips wrote:
> In my workspace, I have a web application project and a library project.
>
> The web application project depends on the library.
>
> In my project setup, I have:
>
>
> Added the library project to the build path ("Projects" tab) of the web app
> Added the library project to the deployment assembly of the web app
>
>
>
> Right when I add the deployment assembly and "apply":
> a jar of my library project is created and it is put into the
> WEB-INF/lib directory
> When I change the library project, however, the jar is never rebuilt
> with updated content
>
> I have tried the following and neither causes the jar to rebuild:
>
> clean/republish the server
> clean workspace
>
>
> The only thing I have found that works is to remove the deployment
> assembly and add it back in. This takes a long time and seems like a
> poor workflow.
>
> ---
>
> Can anyone tell me how this is supposed to work?
> Is their a hot key or a something to cause the jar to rebuild?
>
> I am using Indigo SR2.
> When I run, "check for updates" nothing appears, so I assume software is
> up to date.
>
>
> Thanks
Try not adding the library project on the "Projects" tab. This is
unnecessary and may be interfering with normal behavior. Adding the
library project in Deployment Assembly should handle the Java Build Path
issues for you automatically. With the web application added to a
server in the Servers view, you can click "Publish", then make a change
to the library project and see the state of the server and webapp change
from "Synchronized" to "Republish". Publishing again should update the
jar in the published webapp.
Cheers,
Larry
|
|
|
Powered by
FUDForum. Page generated in 0.03571 seconds
] 
Search
Help
Register
Login
Home
