What is the desired behavior when junit is missing in project classpath ? 1 - ignore test ? maybe with a message @info level ? 2 - configure the plugin to use junit version specified in the project. and if no one is specified use the one specified by us in the plugin itself ?
2013/4/15 Jean-Louis Boudart <jeanlouis.boud...@gmail.com> > Hi Xavier, > > Thanks for your feedback ! > > > 2013/4/15 Xavier Hanin <xavier.ha...@gmail.com> > >> >> I've been playing a little bit with easyant 0.9 this wek-end, and I have >> some feedback: >> - I have some issues with the multi module example: >> - if I run "easyant verify" at the root I get an error: "The <classpath> >> for <junit> must include junit.jar if not in Ant's own classpath" >> - if I run "easyant publish-local" I get another error: "bad revision >> found in ivy file (Revision: 0.2-local-20130415094618). Use forcedeliver >> or >> update" >> > Good catch i'll fix this now > > >> >> - from a documentation point of view, I have not found the documentation >> of >> plugins. Having links from the plugins and standard build types pages >> would >> be really nice. To change the compiler source and target version I had to >> check the source files. >> > > >> >> - the source files of plugins are pretty easy to read and understand, I >> think providing links to them or documentation on where to find them would >> be useful for people used to plain ant (maybe I just missed this part of >> the doc, I didn't read everything). >> > Plugin documentation is not online yet. We didn't took time to find how to > publish them as we may have differences in future plugin releases. > We already have a way to generate plugin documentation. Adding links to > plugin sources could be a good too. > > >> - I've written a small tool to convert basic (very basic I mean) pom files >> to module.ivy, and the result is interesting: on a bunch of modules, not >> only the build run perfectly well (it's really nice to use the same >> conventions), but also it's slightly faster: on a 22 multi module build, a >> "easyant package" take 19s against 23s for "mvn -DskipTests=true install" >> > Nice to hear that it's easy to move from a standard maven build with > multimodules to easyant. Will you share your tool to convert pom files to > module.ivy ? > > >> >> To conclude there's room for improvement, but you've done a very good work >> especially on the maven compatibility side, which is great for people >> having a maven build. >> > I plan to continue improving support for maven users. In early days of > easyant we wrote a plugin to emulate maven publication (generating a pom > and related metadatas) [1] . I saw ivy improvements on makepom task [2] and > i believe we have work to do on both project to make life easier for maven > users to reuse publicated artifacts by ivy/easyant. > > > > >> For the bugs and documentation improvements, I know I could contrbute >> myself, but I have to admit I don't have enough time to dedicate. >> > No problem :) > > > [1] > https://svn.apache.org/repos/asf/ant/easyant/plugins/trunk/maven-publication/ > [2] http://ant.apache.org/ivy/history/trunk/use/makepom.html > > -- > Jean Louis Boudart > Independent consultant > Apache EasyAnt commiter http://incubator.apache.org/easyant/ > -- Jean Louis Boudart Independent consultant Apache EasyAnt commiter http://incubator.apache.org/easyant/
