Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0018384
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. PlatformminorN/A2011-08-30 09:472011-08-30 12:40
ReporterroklenardicView Statuspublic 
Assigned Tomarvintm 
PrioritylowResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0018384: 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
TagsNo tags attached.
Attached Filestxt file icon copy_jscript.txt [^] (1,915 bytes) 2011-08-30 09:52 [Show Content]

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0040551)
mtaal (manager)
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 (reporter)
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)

- Issue History
Date Modified Username Field Change
2011-08-30 09:47 roklenardic New Issue
2011-08-30 09:47 roklenardic Assigned To => mtaal
2011-08-30 09:47 roklenardic Modules => Core
2011-08-30 09:51 mtaal Note Added: 0040551
2011-08-30 09:52 mtaal File Added: copy_jscript.txt
2011-08-30 09:52 mtaal Assigned To mtaal => marvintm
2011-08-30 10:56 iperdomo Note Added: 0040554
2011-08-30 10:56 iperdomo Priority normal => low
2011-08-30 12:40 shuehner Issue Monitored: shuehner


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker