> Hi Christoph, > >> repositories won't be possible from what I understand since >> the jars are >> bound the developer key. > > The developer key should have been installed on the machine of the > developer who gets > ULC jars from the Maven repository. As per the ULC license agreement, a > ULC Developer > license must be purchased for using ULC jars in the classpath. > >> that. I have no objections writing this plugin under a free license >> (i.e. GPL-2) so that it could be hosted at Canoo at a later point. > > Can you please tell us what are the requirements for ULC to be hosted in > Maven repository? > We may then consider supporting it.
One concept behind maven is that all dependecies are hosted in a repository. There are 2 types of repositories: remote and local. Remote repositories contain "public accessible" libraries (like the one for JBoss at http://repository.jboss.com/maven2/). Local repositories contain "a partily mirror" of the remote repositories which contains the libraries you actually use (i.e. noone needs all the libraries the JBoss repository provides, just a few of them). One of the main ideas of maven is to solve the issues with dependency management for you. But that means: Maven needs to manage your dependencies. And therefore it has to contain the ULC libraries in the local repository. Once you have your local repository filled with ULC libraries you just add the following to your projects pom.xml. <dependency> <groupId>ulc</groupId> <artifactId>ulc-base-server</artifactId> <version>6.2.3</version> </dependency> Maven will then read from the local repository the jar file groupId/artifactId/version/artifactId-version.jar and the (optional) meta data groupId/artifactId/version/artifactId-version.pom So more or less it's just placing the jar in the right directory. It could even be done as a part of the ULC installer. It's a real benefit to access libraries this way but a bit difficult to use these from maven. The shell script I provided uses "the simple way" to fill the local repository. But one downside of this method is that it lacks meta information (like the license or dependencies). That's why I'm trying to build a maven plugin to do it "the right way". My main goals are: * install the jars (as done by the script) * extract meta information from the ulc installation (i.e. license) * install the metadata along with the jars Getting this plugin do work should be rather trivial but I need to get the time to actually write it. Regards, Christoph Brill > Thanks and regards, > > Janak > > ----------------------------------------- > Janak Mulani > > email: [EMAIL PROTECTED] > url: http://www.canoo.com > > Beyond AJAX - Java Rich Internet Applications > > http://www.canoo.com/ulc > ----------------------------------------- > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Christoph Brill >> Sent: Tuesday, August 19, 2008 7:28 AM >> To: [email protected] >> Subject: [ULC-developer] ULC Maven2 Repository >> >> Hi list, >> >> has anyone set up a private ULC Maven2 repository? I think public >> repositories won't be possible from what I understand since >> the jars are >> bound the developer key. >> >> I personally like to see this task automated. Right now I have a small >> bash-script to create a lokal maven repository with all jar files plus >> corresponding pom-files. I'm currently thinking about writing a >> Maven2-plugin to handle this process. The idea would be to be able to >> run: >> >> mvn ulc:bootstrap -Dversion=2008 -Dulcdir=/home/ulctest/ulc-2008 >> >> This would populate the local repository with all entries so >> that these >> would be available for the developer. This would be the best solution >> (IMO). >> >> I'd like to get some thoughts on this one before I start working on >> that. I have no objections writing this plugin under a free license >> (i.e. GPL-2) so that it could be hosted at Canoo at a later point. >> >> Regards, >> Christoph Brill >> >> _______________________________________________ >> ULC-developer mailing list >> [email protected] >> http://lists.canoo.com/mailman/listinfo/ulc-developer >> > _______________________________________________ > ULC-developer mailing list > [email protected] > http://lists.canoo.com/mailman/listinfo/ulc-developer > > _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
