All of the scripts we use to publish Spark releases are in the Spark repo itself, so you could follow these as a guideline. The publishing process in Maven is similar to in SBT:
https://github.com/apache/spark/blob/master/dev/create-release/create-release.sh#L65 On Mon, Jul 28, 2014 at 12:39 PM, Koert Kuipers <ko...@tresata.com> wrote: > ah ok thanks. guess i am gonna read up about maven-release-plugin then! > > > On Mon, Jul 28, 2014 at 3:37 PM, Sean Owen <so...@cloudera.com> wrote: >> >> This is not something you edit yourself. The Maven release plugin >> manages setting all this. I think virtually everything you're worried >> about is done for you by this plugin. >> >> Maven requires artifacts to set a version and it can't inherit one. I >> feel like I understood the reason this is necessary at one point. >> >> On Mon, Jul 28, 2014 at 8:33 PM, Koert Kuipers <ko...@tresata.com> wrote: >> > and if i want to change the version, it seems i have to change it in all >> > 23 >> > pom files? mhhh. is it mandatory for these sub-project pom files to >> > repeat >> > that version info? useful? >> > >> > spark$ grep 1.1.0-SNAPSHOT * -r | wc -l >> > 23 >> > >> > >> > >> > On Mon, Jul 28, 2014 at 3:05 PM, Koert Kuipers <ko...@tresata.com> >> > wrote: >> >> >> >> hey we used to publish spark inhouse by simply overriding the publishTo >> >> setting. but now that we are integrated in SBT with maven i cannot find >> >> it >> >> anymore. >> >> >> >> i tried looking into the pom file, but after reading 1144 lines of xml >> >> i >> >> 1) havent found anything that looks like publishing >> >> 2) i feel somewhat sick too >> >> 3) i am considering alternative careers to developing... >> >> >> >> where am i supposed to look? >> >> thanks for your help! >> > >> > > >
