sculptor-parent version

[Pavel Tavoda]

Can we have common version number for ALL projects including sculptor-parent? What is reason to have different version for parent (1.0 instead of 3.0)?

/Pavel

[Torsten Juergeleit]

The plan was that the stuff in "/releng/" has its own release cycle (if any). This stuff is (re)used in different contexts (Eclipse, Maven) which has its own release cycle as well. After the first few releases the parent POM should be changing very rarely.

Not sure if this approach (different release cycle of ParentPOM, Eclipse and Maven stuff) is working out.

Any thoughts?
/Torsten

[Pavel Tavoda]

If we would like to have different release cycle for Sculptor, Eclipse and Maven than we need different parent.pom. However I suggest to separate only Sculptor + Eclipse as one group and Maven as another. Maven will not change a lot. However I don't expect we will change Sculptor version without changing Eclipse. At least DSL will change between releases and for this you need also new Eclipse and it will make everything much cleaner even if we will not change Eclipse I would like to release it together with Sculptor.

Other idea is to release everything together. Maven plugin is not big deal even if we release under new version without really changing code. And I guess this is best because of simplicity.

What do you think?

Pavel

[Torsten Juergeleit]

Releasing the Eclipse and Maven stuff together makes the build and release process easier. And the Xtend guys are using this "release all together" approach as well.

So let's move the parent pom into the root folder. To get rid of the releng folder we have to merge the Maven profile from the distribution pom into the parent pom.

I'll have a look...

/Torsten

[Torsten Juergeleit]

Fixed in #61.

/Torsten

[Pavel Tavoda]

Great fix, I like it. A lot of 'magic' removed.

Thanks