Thanks Rohit! The following link gives a clear picture and guide as well. http://jroller.com/holy/entry/releasing_a_project_to_maven
> -----Original Message----- > From: Rohit Yadav [mailto:[email protected]] > Sent: Wednesday, January 09, 2013 5:52 PM > To: [email protected] > Subject: RE: NetScaler lib/sdk jars are apache licensed > > Just like python has pypi, perl has then cpan, maven has maven central or > "the central repository" [0] [1] where one can publish their artifacts. > Other ways are to host a remote maven repo to publish 3rd party (oss, > nonoss) plugins [2]. > > Hope this helps. > > [0] http://search.maven.org/ > [1] http://maven.apache.org/guides/mini/guide-central-repository- > upload.html > [2] http://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html > ________________________________________ > From: Vijay Venkatachalam [[email protected]] > Sent: Wednesday, January 09, 2013 5:43 PM > To: [email protected] > Subject: RE: NetScaler lib/sdk jars are apache licensed > > Hugo/Chip/David, > The NetScaler build team is looking at ways to upload the SDK files > for > each release online. This archive zip file will be uploaded online for each > release of NetScaler and will contain License, Java src, Java Samples, SDK > jars, > SDK html docs. > For the second part of uploading the jar files to a maven repository > what > should be done to automate? > Is there a public repository which can be updated for each release of > netscaler with its jar files? > Or Is it good to have Citrix host its own maven repository? How to do > that? Also, what is the procedure to make CS build refer to this repository as > well during its build. > Thanks, > Vijay V. > > > -----Original Message----- > > From: Hugo Trippaers [mailto:[email protected]] > > Sent: Wednesday, January 02, 2013 3:10 PM > > To: [email protected] > > Subject: RE: NetScaler lib/sdk jars are apache licensed > > > > Hey Vijay, > > > > Great news! > > > > Comments inline. > > > > > -----Original Message----- > > > From: Vijay Venkatachalam [mailto:[email protected]] > > > Sent: Monday, December 31, 2012 7:27 AM > > > To: [email protected] > > > Subject: NetScaler lib/sdk jars are apache licensed > > > > > > Chip, etal, > > > > > > Netscaler libs (nitro) are apache licensed now. It > > > is based on > > > Apache2.0 license. > > > The jar files along with their source can be downloaded from the > > > NetScaler UI after installing a NetScaler appliance. > > > > > > Some questions for next steps: > > > > > > 1. Is it necessary to upload these SDK files to an internet > > > downloadable > > > site for the build to work? > > > > While not 100% required, this would make life easier for everybody > involved. > > Especially developers should not be required to install the appliance > > and download the jar before being able to compile the code (I'm > > assuming here we are moving the netscaler code to the main build). > > > > Internet downloadable is great, but publishing it in a maven repo (or > > even on > > central) would be completely awesome. This would mean that we can > move > > the netscaler stuff to the main build and nobody would have to worry > > about obtaining the jar file and running obscure commands to get the > > jar into the repo. This would also make version management easier as > > new versions would be published in the repo and we can just update the > > version number in the pom.xml. > > > > I realize that this would put some extra strain on whoever is making > > the netscaler jar files, but it would be great (so great I will > > happily buy anyone that makes this happen a beer ;-) ) > > > > > > > > > > 2. How to get the integration done, any instructions? > > > > Edit the pom files to remove the dependency on the nonoss flag from > > any components that depend on the netscaler.jar. This only works if > > maven can find the jar in some repository. > > > > > > > > Thanks, > > > Vijay V. > > > > > > I'll be happy to help with setting up a repo, dealing with central or > > make modifications to the pom.xml. Let me know what I can help with. > > > > Cheers, > > > > Hugo
