On Apr 25, 2012, at 11:34 AM, Mattmann, Chris A (388J) wrote: > Hi Suresh, > > On Apr 25, 2012, at 8:31 AM, Suresh Marru wrote: > >>> [..snip...] >>> >>> Whether it should block a release however, versus something that should be >>> done before >>> we exit the Incubator, is up for debate. I don't feel strongly that this >>> should block an Incubator >>> release, however I do feel strongly it should be dealt with before we get >>> out of the Incubator. >> >> Thanks Chris. This is laborious task for sure, but in the interest of >> speeding up the build and to adhere to compliance, I vote for getting rid of >> this now. Unless some one else can get it to it before tomorrow, I will >> start on this one tomorrow and will take care of it. If you have pointers to >> any other documentation on getting external jars into maven central please >> send them. > > I appreciate your enthusiasm here, but getting external 3rd party jars into > Maven Central is not > a finish-in-a-week task even. It took me *over 6 months* to get the NetCDF > jars into Maven > Central and I had to basically become a contributor to the NetCDF project to > do so at UCAR :)
Hi Chris, Wow!, its scary. Good to hear you already have the netcdf jars in maven central, we might need them in the near future. I will start and how far we go. I will for sure be not uploading others jars, but a significant number of the non-apache jars Airavata depends are from extreme lab at Indiana University. I am a co-author on those software and we have a apache like license on them, so I will upload them to maven central to start with. But Suresh > I also contributed some patches to them to get them on Maven and to start > publishing the release. > Google my name, Tika and NetCDF for a ton of conversation around that. > > That being said, I know a lot of the grid jars from the community aren't in > Central. So getting them > there could take months, even years to fully get community buy in on their > end. And we can't > start publishing other people's jars. That's going to lead to bad form and > there have been a ton > of discussions in Apache lately about how that's a "no no" (Google Lucene > Commons Csv). > > So like I said, I am +1 to move forward, even with minimal deps on external > repos. It's just > something that should be an Incubator exit criteria IMHO as it's going to > take time. One way > to deal with it would be to generate a prioritized list of "must be removed > as external dep" and > then also bin the other set into "we could live with this being external dep > and here's why." > > Make sense? > > Cheers, > Chris > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >
