Hello, Maven, Is there a need for a Maven lifecycle supporting interactive development tasks?
The default Maven lifecycle is designed to support statically-compiled languages like Java. But the rise of alternative languages on the JVM languages has led to plugins that perform tasks outside of the default lifecycle. Groovy, Scala, and Clojure all have plugins with custom goals for tasks like launching an interactive console, running a script, or evaluating an expression. Would it be possible to standardize around a custom lifecycle that would support some or all these tasks? Thanks for listening, comments welcome. -Stuart Sierra clojure.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
