Subproject versions have diverged
fdlk opened this issue · comments
It's currently hard to stabilize and release to maven cause the subproject versions have diverged.
I've stabilized the master pom but the child poms have different version numbers from the master.
Is there a reason why this was done?
These version numbers have always been different. We use these version
number for our binary release such as:
https://github.com/molgenis/systemsgenetics/wiki/Genotype-Harmonizer-Download
Changing these version numbers now would be very confusing. Previous
releases where also done with different version number from the master.
On Sun, Mar 20, 2016 at 4:48 PM, Fleur Kelpin notifications@github.com
wrote:
It's currently hard to stabilize and release to maven cause the subproject
versions have diverged.
I've stabilized the master pom but the child poms have different version
numbers from the master.
Is there a reason why this was done?—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#447
I'm still fiddling with the subproject interdependencies. Are all subprojects supposed to depend on the latest versions of each other or is it possible that one subproject depends on a previous version of another subproject?
Too the best of my knowledge all project should depend on the latest
versions of each other.
Regards
Patrick Deelen
••••••••••••••••••••••••••••
Sent using my phone
On Mar 20, 2016 9:56 PM, "Fleur Kelpin" notifications@github.com wrote:
I'm still fiddling with the subproject interdependencies. Are all
subprojects supposed to depend on the latest versions of each other or is
it possible that one subproject depends on a previous versions of another
subproject?—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#447 (comment)