Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse SmartHome » ESH TP Version
ESH TP Version [message #1753712] Thu, 09 February 2017 08:36 Go to next message
Sebastian Janzen is currently offline Sebastian JanzenFriend
Messages: 7
Registered: February 2017
Junior Member
Hi!

I found out, that if I create a binding which not has the version of the parent pom, e.g. ESH has 0.9.0-SNAPSHOT and my binding should have 2.0.0-SNAPSHOT, I got a targetplatform problem.

Thats because the inherited config is to use target-platform-configuration with a version ${project.version}. That variable is evaluated for each sub-module. So on building my binding, it tries to load the targetplatform with version 2.0.0-SNAPSHOT which of course not exist.

I suggest to either add a property in the parent-pom like <tp.version>0.9.0-SNAPSHOT</tp.version> with the drawback, that this var has to be kept up to date.
Another approach would be to have some sort of override per bundle. But I'm not sure how to achieve this.

Best
Sebastian
Re: ESH TP Version [message #1753994 is a reply to message #1753712] Mon, 13 February 2017 17:30 Go to previous messageGo to next message
Kai Kreuzer is currently offline Kai KreuzerFriend
Messages: 648
Registered: December 2011
Senior Member
Not sure I understand your problem. If I look at https://repo.eclipse.org/content/repositories/snapshots/org/eclipse/smarthome/targetplatform/0.9.0-SNAPSHOT/targetplatform-0.9.0-20170114.095339-57.pom, I cannot see any specific version references that should in any way impact your build. I would assume it is safe to reference this artifact as the tp for your build. How does your pom.xml look like?
Re: ESH TP Version [message #1754126 is a reply to message #1753994] Tue, 14 February 2017 16:03 Go to previous messageGo to next message
Markus Rathgeb is currently offline Markus RathgebFriend
Messages: 100
Registered: August 2014
Senior Member

I assume Sebastian refers to this line:
https://github.com/eclipse/smarthome/blob/e7fa3baedf8f8296c8c26915ef1f982e6524d324/pom.xml#L170

If your bundle uses another versioning in your binding (so only consumes ESH stuff and be not part of the ESH tree itself) I don't think you should use the ESH binding POM as parent at all (IMHO).
If you still want to do it, you could override the target platform configuration in your (child) POM yourself.
Re: ESH TP Version [message #1754133 is a reply to message #1754126] Tue, 14 February 2017 16:31 Go to previous message
Sebastian Janzen is currently offline Sebastian JanzenFriend
Messages: 7
Registered: February 2017
Junior Member
Yes, I was talking about that line.

Ok, maybe you're right about my parent-pom. I did not find an elegant way to override that. And I did not want to add that override to every pom I have.
Previous Topic:Changing of channels state and options on build, how?
Next Topic:Write only channel
Goto Forum:
  


Current Time: Mon Jun 25 04:44:22 GMT 2018

Powered by FUDForum. Page generated in 0.02067 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top