Just make a second run config with only "compile" as maven goal. 2009/3/13 Luther Baker <lutherba...@gmail.com>
> Hey Howard, > > > I know I must be missing a setting in IntelliJ - thoughts? > > Who's complaining? My original post asked for thoughts ... > > The majority of my second post was was in <pulpit> brackets. Don't take > that > too too seriously - your response to my original question - with another > question was essentially asking "well, why would you want to do a thing > like > that?" ... so, I elaborated :) Again - it was in brackets so you'd know I > was preaching, big ideals, big picture stuff ... > > No insult taken - I didn't know Maven bothered you so. We've not had to > tweak, refactor or worry about plugins with Maven. I just type mvn > jetty:run > and everything downloads and has worked well. Luntbuild, Cruise Conrol, > Netbeans, Eclipse and IntelliJ all run from the same project build and been > doing so without custom tweaks for the past year. > > In this specific case, I was just looking for the magic flag inside of > IntelliJ to push changes out ... not complaining about it. > > -Luther > > > > On Fri, Mar 13, 2009 at 4:08 PM, Howard Lewis Ship <hls...@gmail.com> > wrote: > > > Ok, then, why are you then complaining on the Tapestry mailing list > > about your Maven stuff not working correctly? I don't mean to be > > insulting ... I'm just saying that the myth of Maven seems to far > > outdistance the reality. It's always just one more little tweak, one > > more refactoring, one more update to a plugin ... and it never ends! > > > > I think the core idea: versioned dependencies with transitive > > relationships, is very, very good. I just want to get away from using > > the build portion. > > > > On Fri, Mar 13, 2009 at 11:48 AM, Luther Baker <lutherba...@gmail.com> > > wrote: > > > Thanks Richard. That helps and I'll take a look ... > > > > > > <pulpit> > > > One build process. Cross platform. IDE agnostic. That is our motto. > > > > > > Our continuous integration / build process is IDE agnostic. Maven > builds, > > > runs and tests the app on Unix servers, windows boxes and Macs. > > > Additionally, NetBeans has native support for Maven projects. Most of > our > > > team uses Eclipse and the Maven plugin works without any Eclipse > specific > > > config. I fired up IntelliJ and the app built and deployed right out of > > the > > > box ... I'm just wondering where the flag is to automatically update > apps > > > running via that plugin. > > > > > > I can/will look at the IDE specific plugin - but it is not my first > > choice - > > > and it's alot more than just *simplicity*. > > > > > > By leveraging Maven, configuration and classpaths are always built the > > same > > > way - dev, test and prod builds (cruise control, luntbuild, etc) and > can > > be > > > built and deployed without IDE dependencies. It forms the baseline and > > > everything else works around that foundation. As soon as I have to > custom > > > configure Eclipse WTP, MyEclipse or IntelliJ specific Jetty plugins, I > > have > > > to setup the IDE with IDE specific classpaths, etc that don't always > work > > > out of the box in the other builds. Maven takes care of all of that for > > us. > > > > > > I've developed with Emacs and Maven on the command line. NetBeans opens > > > Maven projects natively. Maven and Eclipse work almost seamlessly > > (updating > > > classes as source changes). Out of the box, IntelliJ works for the most > > part > > > if I restart the app manually - but I thought I'd check to see if there > > were > > > a flag to auto-restart on changes to source. > > > > > > If one of these IDE editors need special handling, sobeit - but it > isn't > > the > > > first thing I'd try or want to do since the general process around > Maven > > > works so well. It might be considered forward (or backward) thinking > .... > > > but alot of it works now - and it is quite simple to setup. Just > download > > > and unzip Maven :) > > > </pulpit> > > > > > > Honestly, once you embrace and use it regularly, Maven becomes very > > > powerful. IDEs become arbitrary since all of them import or open Maven > > > projects. Continuous Integration, Testing and Standard Build processes > > can > > > now define project structure and lifecycle - and IDEs simply adhere to > it > > - > > > not the other way around. > > > > > > -Luther > > > > > > > > > > > > > > > On Fri, Mar 13, 2009 at 12:55 PM, Richard Clark <rdcl...@gmail.com> > > wrote: > > > > > >> P.S. http://wiki.apache.org/tapestry/Tapestry5_Run_Jetty_From_IDEA > > >> > > >> (5 minutes and 2 page loads later) > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > >> For additional commands, e-mail: users-h...@tapestry.apache.org > > >> > > >> > > > > > > > > > > > -- > > Howard M. Lewis Ship > > > > Creator Apache Tapestry and Apache HiveMind > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
