Clarify deployment to Sonatype

tapvanvn / odata4j

Automatically exported from code.google.com/p/odata4j

0 stars 0 forks source link

Clarify deployment to Sonatype #206

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

- Keep or remove the odata4j-fit artifact? The contained jar is empty...
- Remove odata4j-dist-x.x.x.jar from odata4j-dist artifact. I don't know where 
it comes from...
- Keep or remove the odata4j-dist artifact? Bundles are provided via 
'Downloads' section...

Original issue reported on code.google.com by philipp.sebastian.thun on 16 Aug 2012 at 3:24

GoogleCodeExporter commented 9 years ago

Keep. It's common Maven/Nexus practice that you make everything available what 
a POM produces. FIT is empty because it contains only test code which is not 
deployed. If you once add productive code (e.g. for re-using test code) then 
Maven fail if FIT is not in Nexus.

Original comment by stephan....@googlemail.com on 7 Sep 2012 at 12:22