Hello Tom
Le 02/11/10 05:48, Tom Kunicki a écrit :
I would vote for a minimal NetCDF artifact with dependencies listed in the pom.
Yes, this is exactly what I'm proposing :)
I have it on my list to convert the IOSP from explicit registration to a
javax.imageio.spi style registration (i.e. just drop it in the class path).
This would play well with maven, just add the dependency for the IOSPs you want.
I confirm that javax.imageio.spi style registration works well with Maven :).
The most difficult task however is to determine which class has precedence when
there is many implementations available for the same service.
From the looks of the source tree layout it appears that build was migrating
towards maven at some point. It might not be too difficult to finish that up
or create a pom.xml to build and deploy from source.
Yes, that would make the process easier for future versions. However I think
that for current and historical versions (it would be nice to have at least
NetCDF 4.1 in addition to 4.2 on Maven central), it may be easier to deploy them
with "mvn deploy:deploy-file"...
Regards,
Martin
