On Mon, Sep 12, 2011 at 3:13 AM, Paolo Castagna <[email protected]> wrote: > Hi Benson > > Benson Margulies wrote: >> You can't release something with snapshot deps, and that pom Ross just >> poked me about has snapshot depts to arq and tdb. > > Yep. At release time, I'll remove any SNAPSHOT dependency. > > The maven-release-plugin explicitly forbids you to release an artifact with > SNAPSHOT dependencies, which is good to avoid human errors. > >> >> If you fix that, sure, by all means, run a release to run this process. >> >> If you do run a release of just LARQ, you'll need a dist package. >> Typically, made with the maven-assembly-plugin. > > Is it possible to avoid publishing dist packages for a small Jena module > such as LARQ and use the Jena distribution (which will include all modules) > for this?
Absolutely. Inside the Maven project, 90% of the releases are 'maven only' releases of plugins. The only thing that gets released to dist is maven itself. It would make sense to me for you-all to release the individual modules that way, facilitating focussed bug-fixing releases, but it's for you to decide that. > >> Don't forget code-signing :-). > > Yep. > >> >> >> On Thu, Sep 8, 2011 at 4:18 PM, Paolo Castagna >> <[email protected]> wrote: >>> Benson Margulies wrote: >>>> An Apache release, in the formal sense, is a collection of buildable >>>> source. Binary package (and pushes to maven) are formally considered >>>> gravy. >>> Hi Benson, >>> this is related to my latest comment on JENA-63: >>> https://issues.apache.org/jira/browse/JENA-63 >>> and the exact semantic of gravy! :-) >>> >>> Could we call a vote to release just LARQ (as a test-drive for the Apache >>> release process) and run just a mvn deploy to get just the binary package >>> pushed to the Apache Maven repository? >>> >>> LARQ is just one of the modules which will be included in tar.gz|zip >>> files to be put here: http://www.apache.org/dist/incubator/jena/. >>> >>> A more general question is: can a multi module project decide to release >>> one of its module as gravy only publishing the binary package to the >>> Maven repository only? Or, each time a single module needs to be released, >>> some stuff needs to be put on http://www.apache.org/dist/incubator/jena/? >>> >>> Thanks, >>> Paolo >>> >>>> Typically, if you want to release modules on different schedules, >>>> you'd set up a conformant package format for each module, and hold a >>>> vote for each release of each module. >>>> >>>> If you happen to have N modules ready for release at the same time, I >>>> suppose you could make a batch, but it would be, I think, more >>>> conventional to just start N VOTE threads. >>>> >>>> >>>> On Thu, Jun 16, 2011 at 1:19 PM, Paolo Castagna >>>> <[email protected]> wrote: >>>>> Hi mentors, hi all, >>>>> how the release process works with a multi module project? >>>>> >>>>> Jena is currently composed by different and separate (although >>>>> interdependent) modules: ARQ, Eyeball, Fuseki, IRI, Joseki, LARQ, >>>>> SDB, TDB and jena. These modules have different version numbers >>>>> and different life cycles. >>>>> >>>>> Let's say, just to make an example, I would like to make a release >>>>> of the LARQ module. Do I need to start an VOTE? I guess so. >>>>> >>>>> But, do we need a separate VOTE process for each module or we need >>>>> to synchronize and release all the modules together with a single >>>>> VOTE process? >>>>> >>>>> How other Apache projects address this situation? >>>>> Do you have a good example I can learn from? >>>>> >>>>> Thank you, >>>>> Paolo >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>> >
