The build can always be done using a terminal or IDE actions bound to gradle commands. It's easy to do with Netbeans and can easily be shared (it's a nb- configuration.xml file at each project root). That must not be hard with any other IDEs, even vim or emacs :)
About IDE support, my only real concern is to have an easy way to setup classpath correctly, hence my remarks about the ~/lib directory. Netbeans has a way to "package" libraries too, it's intended only for project not using maven, ie. "netbeans projects". Distribute some kind of IDE integration like this in the SDK could be done in the future but I think a more generic concern is to provide SDK users an easy way to know what to put on their classpath. You don't want Struts, Spring, Shiro etc ... if you don't use them. /Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
