This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 131965 - allow subsets of the app to be redeployed... remotely...
Summary: allow subsets of the app to be redeployed... remotely...
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Petr Hejl
Depends on:
Reported: 2008-04-03 17:19 UTC by jjjjjj
Modified: 2008-04-26 05:21 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description jjjjjj 2008-04-03 17:19:22 UTC
When deploying a large project over a slow network(vpn) you get:

Deployment error:
Deployment timeout has exceeded.
See the server log for details.

This means I must get into my car, drive 500 miles at the current fuel price which by the time I need to get back has
doubled; or instead use some other ftp application and deploy the ear locally - why did we bother with remote deployment
support if messages like this appear.

In this case I only changed one line of code - now it wants to deploy the entire project including all libraries again
over and over; which by the way I can not change as they are in a jar and I've put the lid on them (deployed them before
to the server). 

When unpicking deploy in the libraries tab for the project, it only deploys my code but nothing works as when
redeploying it removes everything in the application including all the libraries.

Further more this strategy of bluntly removing everything in the application path adds unnecessary complexity to the
management of the UploadFile control and the like; as it now needs to put files outside of the web application domain.
Comment 1 Petr Hejl 2008-04-04 09:42:29 UTC
I suppose you are talking about specific server... Please assign the proper subcomponent of serverplugins component.

You can configure deployment timeout for GF in properties tab.
Comment 2 jjjjjj 2008-04-04 22:38:52 UTC
My apology - I did not know about the deployment timeout setting; and yes it's for a specific server - so; Thank You.

For now I'm packing most jars into the domain lib folder; and only deploying what really needs to get deployed - it
seems to do the trick.

However I'd still like to be able to "replace-deploy" instead of "clean-deploy" applications.