Romain, Jason, I have already looked at polyglot maven and unless I missed something you can execute some specific code but it has to be inside the pom. This should be ok for simple cases but to do more complex things I find it more convenient to be able to structure the code as classes in a specific source folder. In the exemples of polyglot maven I have seen only some hello world specific code exemples. Do you have other exemples with more complex things? Le 8 mai 2016 20:47, "Jason van Zyl" <[email protected]> a écrit : > > It has worked out of the box since 3.3.1 and the Maven Wrapper stuff. But the fact is most users don’t really care, developers are looking at the build all that often that it matters much. I think it’s pretty cool that it works but in the grand scheme of things most things should work with a plugin the exception being building runtimes. There I agree a DSL of sorts would be useful, but for the main build I think most find in practice there isn’t a huge win in a large organization. >
On mvn side yes, not on the whole ecosystem side and tools mimicing mvn meta read process like a lot of companie did. Main issue is for frontend stuff which is often custom by project and should be integrated with pre-package phase. Often got a hard time with groovy task to order front steps. Also having a src/build makes any of custom doc+build possible which is more and more common - workaround is mvn exec today but miss its build scope. Of course custom mojo are always possible but a lot of effort for nothing in final artifacts when not a big company. Just my 2cts > > On May 8, 2016, at 12:43 PM, Romain Manni-Bucau <[email protected]> wrote: > > > > Well having it working ootb everywhere - including ideS - is a must and why > > polyglot maven didnt get as must market as it should IMHO. > > > > Also being able to order in the pom itself execution by reference would > > solve a lot of headaches. > > Le 8 mai 2016 17:04, "Jason van Zyl" <[email protected]> a écrit : > > > >> There is also: > >> https://github.com/takari/polyglot-maven-examples/blob/master/groovy/pom.groovy > >> > >> and the equivalent for ruby: > >> https://github.com/takari/polyglot-maven-examples/blob/master/ruby/hello/pom.rb > >> > >> Both the Groovy and Ruby dialect allow inline of plugins. > >> > >> Similar ideas but you might be able to reuse code in such a way it meshes > >> with what exists. > >> > >>> On May 6, 2016, at 3:55 AM, Francois-Xavier Bonnet < [email protected]> > >> wrote: > >>> > >>> Hi, > >>> > >>> I wrote a Maven plugin that lets you execute java code directly from the > >>> project and bind it to build cycle phases. I believe this can be helpful > >>> when you want to do something specific in your project without having to > >>> develop your own custom plugin (or before spending time packaging it as a > >>> plugin if it happens to be reusable). > >>> > >>> I will be happy if this plugin can be useful to other people. Also if > >>> someone wants to help me improve it, any thought or advice would be > >> greatly > >>> appreciated. > >>> The plugin is released on Maven central and already used on a few > >> projects. > >>> It is on Github under Apache 2 License. > >>> > >>> https://javabuild.java.net/ > >>> https://github.com/javabuild/builder-maven-plugin > >>> > >>> Regards, > >>> Francois-Xavier Bonnet > >> > >> Thanks, > >> > >> Jason > >> > >> ---------------------------------------------------------- > >> Jason van Zyl > >> Founder, Takari and Apache Maven > >> http://twitter.com/jvanzyl > >> http://twitter.com/takari_io > >> --------------------------------------------------------- > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Takari and Apache Maven > http://twitter.com/jvanzyl > http://twitter.com/takari_io > --------------------------------------------------------- > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
