> Being able to modify the .css files and having tomcat notice this "on > the fly" removes this problem all together. And I think this is > something we should try to achieve.
Tomcat does. Atleast for me.
Yes a build is required, but that takes 20 seconds on our largest skin
genericno.sesam.no, and 10 seconds on a small skin.
Is this really a efficient development problem?
You could make a simple macro in netbeans:
- save file
- build project
and assign it the CTL-s shortcut.
That gives you virtually want you want.
> I'm really more interesting in a way of not having to build the whole
> war file every time. I feel it often should be enough to compile just
> the java file(s) that's been modified, and copy the new class file(s)
> to tomcat.
I appreciate the problem with java files. It's a little more complicated
as they are bundled within library jarfiles within the war file.
Maybe someone could provide an alternative way of building these war
files so the MANIFEST.MF contains a Class-Path entry pointing to the
project's various target/classes directories.
This in conjunction with a reload=all|java request and building with
just "mvn compiler:compile" would work.
> after a short test netbeans, at least, doesn't seem to compile java
> files instantly as they're modified and saved.
NetBeans keeps its own cache of class files in relation to editor error
annotations.
Using the macro mentioned above overriding the save shortcut would make
it work your way though. Extending the macro you could:
- save file
- jump to current file in project tab (CTL-SHIFT-1)
- navigate to project root (left arrow)
- build current project ("mvn compiler:compile" or "mvn webapp:webapp")
- go back to current file in editor (CTL-0)
~mck
--
"Microsoft has done for software what McDonald's did for the hamburger."
PC MAGAZINE, June 1997
| semb.wever.org | sesat.no | sesam.no |
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
