Thank you for your answer Jean-Baptiste, In fact, I've already built the JAR with ant and I'm ready to deploy it in the Jspresso Maven repository. I just wanted to check with the owner(s) of the code if he doesn't have any problem with that - even though the license(s) allows to do so.
Regards, Vincent Jean-Baptiste BRIAUD -- Novlog a écrit : > Hi, > > I'm not a big fan of Maven and so I'm not using it, but there is an > ant build.xml file if you checkout JavaRPC from SVN. > As Maven rely on ant, it may "fit the hole". > If it helps, I can provide you a jar file quickly. > > > On Jul 2, 2009, at 15:34 , Vincent Vandenschrick wrote: > > >> Hi Qooxdoo team, >> >> I'm making quite good progress in porting the Jspresso framework to >> Qooxdoo. I'm almost 100% done with it but now comes the "hard" part >> (couldn't guess it at first sight) : the Maven build integration ;-) >> >> I'm almost done with configuring the Qooxdoo toolchain (manifest + >> config) for eating a more standard maven project layout (e.g. >> src/main/js, src/main/resources, target/, ...) and the next step >> constists in allowing the developer to do as little manual setup as >> possible on the build machine. >> I dropped the idea of running the build with Jython since I could'nt >> get >> it right (the "maximum recursion depth" problem). So I made my mind on >> using a normal python interpreter so this one will have to be manually >> installed if not already there (M$...). So far, so good. >> >> The question is now to have the java RPC backend packaged and deployed >> as a Maven artifact (a jar containing the compiled classes) for later >> inclusion as a dependency in the Maven built WAR. I can manage to >> build >> the JAR from the contrib source code and my proposition is to host the >> resulting unmodified archive into the Jspresso Maven repository so >> that >> it gets publicly accessible to the build. I think that the license >> allows it but I would like to hear that you don't have any objection >> against it. >> >> Same goes for the Qooxdoo framework and toolchain. The idea I have >> is to >> make a "light" zip archive of Qooxdoo that would only contain the >> framework JS files + resources + python toolchain (I would mainly get >> rid of the "application" and "component" directories). Then again, I >> could host it into the Jspresso Maven repository so that it would get >> automatically downloaded, unpacked and used during the build of a >> Jspresso application. Of course this Qooxdoo artifact will be >> versioned >> (0.8.2, 0.8-SNAPHOT, ...) so that a target application build can run >> against a predefined Qooxdoo release depending on what has been >> declared >> into the project POM file. Same question than before : any objection / >> licensing issue against it ? >> >> If you don't see any showstopper for both points, I think I can manage >> to seamlessly integrate the Qooxdoo build into the Jspresso Maven >> build >> with only python as a requirement. Of course, all licensing, IP, site >> reference informations would be retained in both deployed artifacts. >> >> Thanks in advance, >> Vincent >> >> -- >> Vincent Vandenschrick >> Jspresso Framework >> http://www.jspresso.org >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> > > > ------------------------------------------------------------------------------ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- Vincent Vandenschrick Jspresso Framework http://www.jspresso.org ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
