Szczepan Faber a écrit : >Are you using 'maven IDE' plugin? The doc says >(http://mevenide.codehaus.org/mevenide-ui-eclipse/features.html) that >proxy is not supported as well in this plugin. > >How did you make it work in proxied network? I pass vm args >(-DproxySet, ...) to startup.jar but still with no effect. > > As said, I run maven from console. So it downloads it dependencies from console :)
> > >>Everything else (build, run, jar:install, tests) is >>run with 'maven xyz' from command line, it's easier to manage. >> >> > >Can you explain how com it may be easier to manage? In my opinion it >is just inconvenient. Imagine working this way with ant, which is >tightly incorporated into Eclipse JDT. > > 1) as someone else stated, it guarantees the maven build process do work outside ide (i have co-workers which ran unit tests inside eclipse and dicovered later they didn't run in pure maven because the working directory was not the same) 2) I find it way faster to do <alt tab> ma<tab> test (which translates to switch to console, execute maven with target test) than playing with mouse to right click on project.xml, select maven, select run, and type 'test' inside target area. 3) Console has an good history of my commands, and i can easily go back in history to reexecute a command. 4) I can type things like 'for i in project1 project2 project3; do cd $i; maven jar:install; cd ..; done' :D Am not a fanatic of the mouse, i like to use the keyboard for everything. Each time my hand need to go from keyboard to mouse, it's wasted time. When i can avoid it without requiring too much keyboard time, i avoid it :) > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
