Reto !
Ha ok, miss that parent contain version of each module.
That lead to release the parent each time we release a module.
If I well understood, Fabian remove Stanbol's dependencies from the
parent and only let widely shared version of externals dependencies...
With the drawback of taking care in each module of other's modules
versions...
This situation may be mitigate with more "top level reactors" (aka
rdf,plateform,etc...), but not ideal.
Got your point on the single source release, that's accurate, but really
not clear in the svn /tags.
Could be interesting to escalate this problems to @incubator or @maven.
As this considerations are for the most cosmetics, and seemed that no
simple solution can be found right now. here comes my +1.
Thanks Reto.
++
On 08/22/2012 01:10 PM, Reto Bachmann-Gmür wrote:
Hi Florent
I ask myself a question about the "reactor".
He will be also released with all the commented module. This will not cause
problems ?
I just think about the time of we want to do another release of the all
plateform... If we decide it to be 0.3-incubating... Could it lead to
problems ? (as reactor already released as 0.3-incubating but with modules
commented).
I'm happy to learn about other models for partial releases, but with
the scheme proposed with this release the reactor is something that
increases on every release of more than one module.
I find also pretty strange the content of
http://svn.apache.org/repos/asf/incubator/clerezza/tags/clerezza-0.3-incubating/
And I was mostly dubitative when try to compile from the source (like : "??
there is a 0.3 version of Clerezza ? Hummm... How many beers yesterdays ?"
:) )...
As this is just a release about parent and shell, why not have a structure
like that :
http://svn.apache.org/repos/asf/incubator/clerezza/tags/parent-0.3-incubating
http://svn.apache.org/repos/asf/incubator/clerezza/tags/shell-0.3-incubating
This can be done if the modules are independent of each other, here we
have the new shell version in the parents dependency management and
the shell uses the new parent. I think we often release modules
together where only a combined review makes sense (e.g.: improve
parser api and adapt various implementations and clients) in this case
I think have maven create a single source zip is much more convenient.
Not having it include the reactor and creating branches only for the
included modules would of course be nice, an RFE for the release
plugin?
Cheers,
Reto
