Yup. I don't think I understand the problem, and shouldn't comment.
On Sat, Jun 24, 2017 at 4:59 PM, Petar Tahchiev
wrote:
> Hi Paul,
>
> I think you misunderstood. The [BOM] is a separate project and the
> [PLATFORM] and [DEMO_STORE] are also separate projects, both of which
> declare as their
Hi Paul,
I think you misunderstood. The [BOM] is a separate project and the
[PLATFORM] and [DEMO_STORE] are also separate projects, both of which
declare as their parent the [BOM].
@Robert: I have added the test-case:
https://github.com/apache/maven-release/pull/18/commits/
Release-aggregator is
Am 2017-06-21 um 20:16 schrieb Karl Heinz Marbaise:
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12332979
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20re
What we're still missing is a release-aggregator, which can release
multiple release-roots at once. That would probably be the preferred fix,
the suggested patch is just an easy work-around.
It is still on my todo-list.
Robert
On Sat, 24 Jun 2017 12:42:22 +0200, Paul Hammant wrote:
Easy t
Easy to fix. Have a profile 'platformOnly' in the root module (I'm not
sure if 'BOM' should mean anything to me) that includes only 'platform' as
a child module.
mvn release:prepare -PplatformOnly # etc
Later when you're ready to do the demo store release, use another (from
root):
mvn rel
+1
On Wed, 21 Jun 2017 20:16:08 +0200, Karl Heinz Marbaise
wrote:
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12332979
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2
Hi Peter,
This fix looks good to me, but I would appreciate one integration test to
confirm it and to prevent regression in the future.
thanks,
Robert
On Sat, 24 Jun 2017 08:58:58 +0200, Petar Tahchiev
wrote:
Hey guys,
I'm facing a number of challenges when I release the project at my
Using JobDSL is effectively another approach
It's main avantage is to easily keep the control at Jenkins Admin level of
what is done instead of delegating it to projects developers
On Sat, Jun 24, 2017 at 8:44 AM, Hervé BOUTEMY
wrote:
> I was thinking at something like the Maven Jenkins Seeding
Hey guys,
I'm facing a number of challenges when I release the project at my company.
Here's my setup:
[BOM]
/\
[PLATFORM] [DEMO_STORE]
I have a master BOM project which holds all the version as defined
properties. This B
