|Recommended Use of Target Platform Definition File [message #990644]
||Thu, 13 December 2012 15:01
| Erik Englund
Registered: July 2009
This is more of a best practices question.|
Currently our organization uses the '.target' files to share target platform definitions with our development teams. We have the '.target' point to internal update sites. This works great except for one thing.
Some of the update sites we point to contains code that is the result of continuous integration. Therefore, the qualifier, and thus the version, are constantly changing.
This makes the '.target' file constantly complain that it can't find a particular feature. It forces us to open the editor, edit the site, select the exact same feature and on we go.
My question is, is there a way around this or is there a better way we should be doing this?
One solution we thought of would be to repo2runnable the update sites as part of a build/setup script that developers would need to run. This seems slow and clunky though.
Anyway, just wondering if anyone else has run into this problem and how they handled sharing target definitions among their developers.
Powered by FUDForum
. Page generated in 0.02067 seconds