Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0018384Openbravo ERPA. Platformpublic2011-08-30 09:472011-08-30 12:40
Reporterroklenardic 
Assigned Tomarvintm 
PrioritylowSeverityminorReproducibilityN/A
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0018384: copy.file ant task
DescriptionWhen doing client development (javascript development) one often makes minor changes to JS and needs to test them right away. Currently, this is VERY time consuming since it requires two things:
1) ant smartbuild that copies the changed JS files to context
2) restart tomcat, another minute or two of lost time

It would be great if:
1) there would be an "ant copy.files"-like task that quickly copies such static resources over to context
2) if there was a setting that tomcat would not cache those resources so no restart is needed.

Since I envision more and more development will be done in javascript on the client side, this would be very welcomed by developers.
Steps To Reproducesee above
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Filestxt copy_jscript.txt (1,915) 2011-08-30 09:52
https://issues.openbravo.com/file_download.php?file_id=4493&type=bug
Issue History
Date ModifiedUsernameFieldChange
2011-08-30 09:47roklenardicNew Issue
2011-08-30 09:47roklenardicAssigned To => mtaal
2011-08-30 09:47roklenardicModules => Core
2011-08-30 09:51mtaalNote Added: 0040551
2011-08-30 09:52mtaalFile Added: copy_jscript.txt
2011-08-30 09:52mtaalAssigned Tomtaal => marvintm
2011-08-30 10:56iperdomoNote Added: 0040554
2011-08-30 10:56iperdomoPrioritynormal => low
2011-08-30 12:40shuehnerIssue Monitored: shuehner

Notes
(0040551)
mtaal   
2011-08-30 09:51   
Another nice function would be a copy function the other way around, from the context back to the modules. See the attached script.

Or maybe we should use this as the recommended way, change in the context, refresh the browser, copy files from the context to the modules.
(0040554)
iperdomo   
2011-08-30 10:56   
@roklenardic:
As Martin suggests. There is no need to work in the modules folder. You can work directly in WebContent/web/your.java.package/js/somefile.js

The resource is automatically refreshed, and you only need to refresh your browser window.

After developing you need to remember to copy the modified files back to the sources (modules folder)