A zip file could be provided as a convenience binary. If the deps are compatible from a license perspective, you could include them too.
On 23 January 2014 22:58, Kasper Sørensen <[email protected]> wrote: > Btw. a simple uber jar would not be sufficient since it would not contain > dependencies. It would maybe mean less JAR entries on your classpath but > will still not be functional without a minimum set of slf4j and maybe a few > other common libraries. > > > 2014/1/23 Kasper Sørensen <[email protected]> > >> So now I am a little bit confused... Can the zip file I created be used as >> a convenience downloadable binary item? I think it makes sense in this way? >> And it is quite consistent with e.g. how Apache Hadoop is being >> distributed.... Am I not right? >> >> >> 2014/1/23 Henry Saputra <[email protected]> >> >>> Yeah you are right there. Technically all the jar we add to the >>> staging repo for VOTE should not even considered for voting. >>> >>> As you have mentioned, ASF only vote on source files, so that is why I >>> think we could include the uber jar in the staging as part of proposed >>> release artifacts as convenience for testing and verify validity of >>> the package via hash check and sig). >>> >>> - Henry >>> >>> On Thu, Jan 23, 2014 at 11:06 AM, Noah Slater <[email protected]> wrote: >>> > The uber jar includes third-party works and is a binary file, isn't >>> > it? We only ever vote on source files. >>> > >>> > My understanding of what this uber jar is tells me that it can be >>> > prepared by anyone, at any time, and made available to our community, >>> > as long as we don't call it a "release". And make it clear it is for >>> > convenience only, and not an official product of the PMC. >>> > >>> > On 23 January 2014 19:57, Henry Saputra <[email protected]> >>> wrote: >>> >> Yes, but I think we would like to include the uber jar as part of >>> >> release artifact next time. >>> >> >>> >> For this release, we do not have to put the uber jar since it was not >>> >> included in the VOTE thread. >>> >> >>> >> I would recommend put the "deps" libraries somewhere like in >>> >> people.apache.org and update the release note to indicate this. >>> >> >>> >> Any other thoughts? >>> >> >>> >> - Henry >>> >> >>> >> On Thu, Jan 23, 2014 at 10:48 AM, Noah Slater <[email protected]> >>> wrote: >>> >>> If we're doing this, it's important to mark out the different >>> >>> locations in our download directory. One for the source *release* and >>> >>> the other for the convenience packages that project committers >>> >>> provide. We need to be careful about the wording here on the website >>> >>> too. >>> >>> >>> >>> On 23 January 2014 17:42, Henry Saputra <[email protected]> >>> wrote: >>> >>>> Ankit, could you help make sure ALL the artifacts used in the VOTE >>> are >>> >>>> released to the dist directory? Thanks! >>> >>>> >>> >>>> Kasper, we could build "uber jar" to include all the dependencies in >>> >>>> one jar. Using something like Maven shade plugin [1] should do the >>> >>>> trick. >>> >>>> >>> >>>> - Henry >>> >>>> >>> >>>> [1] http://maven.apache.org/plugins/maven-shade-plugin/ >>> >>>> >>> >>>> On Thu, Jan 23, 2014 at 12:21 AM, Kasper Sørensen >>> >>>> <[email protected]> wrote: >>> >>>>> Not sure why the md5 and sha1 files are missing. Maybe Ankit simply >>> forgot >>> >>>>> to copy them over? >>> >>>>> >>> >>>>> Regarding the dep jars ... What I am thinking about is that say I >>> have my >>> >>>>> own build setup (e.g. with Ant or so) and I want to go download the >>> Spring >>> >>>>> Framework, Hibernate or any other substantial Java library with >>> >>>>> dependencies, then I usually find a bundle which contains >>> dependencies. >>> >>>>> That's very helpful if I just want to dump them into the classpath >>> and >>> >>>>> start compiling etc. How would a MetaModel user do that if we don't >>> provide >>> >>>>> these jars somehow? >>> >>>>> >>> >>>>> Of course the Maven users are blessed with the dependency >>> management, and >>> >>>>> that's also why I put the <dependency> snippet directly on the >>> website >>> >>>>> draft as well. >>> >>>>> >>> >>>>> >>> >>>>> 2014/1/23 Henry Saputra <[email protected]> >>> >>>>> >>> >>>>>> We should not add those deps jars to the dist folder. >>> >>>>>> >>> >>>>>> We could write doc in the wiki on how to integrate with MetaModel >>> from >>> >>>>>> your project. >>> >>>>>> >>> >>>>>> Like if you use Maven the add MetaModel dependency in the pom.xml >>> that >>> >>>>>> should pull transitive dependencies on when building your Maven >>> >>>>>> project. >>> >>>>>> >>> >>>>>> - Henry >>> >>>>>> >>> >>>>>> On Wed, Jan 22, 2014 at 7:22 AM, Kasper Sørensen >>> >>>>>> <[email protected]> wrote: >>> >>>>>> > I have a new draft available then: >>> >>>>>> > http://metamodel.staging.apache.org/index.html >>> >>>>>> > >>> >>>>>> > Go to the section called "Download". >>> >>>>>> > >>> >>>>>> > One specific doubt I have: Our build did not produce a finished >>> zip file >>> >>>>>> > with all the JAR files in it (including the dependencies like >>> slf4j etc. >>> >>>>>> > which are only mentioned as maven <dependency> elements). So I >>> created >>> >>>>>> one >>> >>>>>> > manually and put it here: >>> >>>>>> > >>> >>>>>> >>> https://dist.apache.org/repos/dist/release/incubator/metamodel/metamodel-4.0.0-incubating/packaged/ >>> >>>>>> > Along with my own armor/.asc file. >>> >>>>>> > >>> >>>>>> > Is that the right way to do it? Is the contents of this file >>> correct (in >>> >>>>>> > the sense that it contains third party JARs in the lib folder)? >>> >>>>>> > >>> >>>>>> > >>> >>>>>> > 2014/1/22 Noah Slater <[email protected]> >>> >>>>>> > >>> >>>>>> >> See this: >>> >>>>>> >> >>> >>>>>> >> https://www.apache.org/dev/release-download-pages.html >>> >>>>>> >> >>> >>>>>> >> On 22 January 2014 14:23, Kasper Sørensen >>> >>>>>> >> <[email protected]> wrote: >>> >>>>>> >> > Thanks for the CouchDB example Noah. Will try to do something >>> similar. >>> >>>>>> >> > >>> >>>>>> >> > Now another "little thing" ... How do we get the downloadable >>> zip >>> >>>>>> files >>> >>>>>> >> > etc. available on the download server of Apache? I see that >>> all large >>> >>>>>> >> files >>> >>>>>> >> > go through a link like this: >>> >>>>>> >> > >>> >>>>>> >> >>> >>>>>> >>> http://www.apache.org/dyn/closer.cgi?path=/couchdb/binary/win/1.5.0/setup-couchdb-1.5.0_R16B02.exe >>> >>>>>> >> > >>> >>>>>> >> > I imagine that's to support download mirrors etc... Is that >>> kinda >>> >>>>>> stuff >>> >>>>>> >> > already taken care of by Ankit's release procedure, or do we >>> need to >>> >>>>>> do >>> >>>>>> >> > something more for the distribution part of the release? >>> >>>>>> >> > >>> >>>>>> >> > >>> >>>>>> >> > 2014/1/22 Noah Slater <[email protected]> >>> >>>>>> >> > >>> >>>>>> >> >> Congrats! >>> >>>>>> >> >> >>> >>>>>> >> >> On 21 January 2014 13:05, Ankit Kumar < >>> [email protected]> >>> >>>>>> wrote: >>> >>>>>> >> >> > HI All, >>> >>>>>> >> >> > >>> >>>>>> >> >> > The vote for Apache Metamodel 4.0.0-incubating is closed. >>> The vote >>> >>>>>> >> passes >>> >>>>>> >> >> > with 4(+1) votes. >>> >>>>>> >> >> > >>> >>>>>> >> >> > Following IPMC votes were received. >>> >>>>>> >> >> > >>> >>>>>> >> >> > *+1* >>> >>>>>> >> >> > hsaputra >>> >>>>>> >> >> > mfranklin >>> >>>>>> >> >> > arvind >>> >>>>>> >> >> > nslater >>> >>>>>> >> >> > >>> >>>>>> >> >> > >>> >>>>>> >> >> > Regards >>> >>>>>> >> >> > Ankit >>> >>>>>> >> >> >>> >>>>>> >> >> >>> >>>>>> >> >> >>> >>>>>> >> >> -- >>> >>>>>> >> >> Noah Slater >>> >>>>>> >> >> https://twitter.com/nslater >>> >>>>>> >> >> >>> >>>>>> >> >>> >>>>>> >> >>> >>>>>> >> >>> >>>>>> >> -- >>> >>>>>> >> Noah Slater >>> >>>>>> >> https://twitter.com/nslater >>> >>>>>> >> >>> >>>>>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Noah Slater >>> >>> https://twitter.com/nslater >>> > >>> > >>> > >>> > -- >>> > Noah Slater >>> > https://twitter.com/nslater >>> >> >> -- Noah Slater https://twitter.com/nslater
