Quoting Niclas Hedhman <[email protected]>: > Anyone else have any thoughts on this??
Hi, First, I'm really curious and interested in the result of this refactoring. I'll continue to use maven for several projects, some depending on Qi4j. Gradle seems to provide interoperability in this regard so, I'm glad :) I won't use the (bin | src) distributions a lot but I have a few thoughts. Classpath in java can easily become a mess. A big directory containing all dependencies of all modules and submodules feels bad to me. As a developer, how do I know which jar to include in my classpath depending on what qi4j modules I use? That's what maven & gradle can do for me but isn't the (bin | src) distributions for people that don't want to go the super-build-tool way? I'm concerned about IDE support too, I use Netbeans and gradle projects are not supported yet, neither by gradle or netbeans. I'll have to live with that and go through long wizards to set up qi4j projects in my IDE until gradle fix GRADLE-112 . Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
