| Author |
Message
|
| youto |
 Posted: Thu Oct 04, 2012 3:59 am Post subject: How to add Version to .appzip in WMB8 |
 |
|
Novice
Joined: 07 Feb 2012
Posts: 16
|
Hi guys,
this is what infocenter tells me:
Adding version information to an application or library at deployment time
At deployment time, you can manually assign a version to an application or library. That version is not necessarily associated with the content of a particular file in the source control system. You can manually assign a version by creating a file called META-INF/keywords.txt inside the .appzip or .libzip file in the BAR file. You can add a literal string to the text file; for example, $MQSI_VERSION=v1.0 MQSI$. You can use this method to assign to an application or library a version that is independent of the versions of the resources in the application or library.
But how do I get the keywords.txt file in the .appzip?
If I manually open the barfile with winrar I can see that there is a folder named META-INF, but I should be able to insert the keywords.txt file from toolkit, right?
Cheers |
|
| Back to top |
|
 |
| ganesh |
| Posted: Thu Oct 04, 2012 4:11 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| Use ant scripts to build the bar and add the keywords.txt file. |
|
| Back to top |
|
|
| youto |
| Posted: Thu Oct 04, 2012 4:18 am Post subject: |
|
|
Novice
Joined: 07 Feb 2012
Posts: 16
|
Seems like alot of work for such a simple task...
Shouldn't it be possible to do from toolkit? |
|
| Back to top |
|
|
| ganesh |
| Posted: Thu Oct 04, 2012 4:26 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| Sometime back i had to add versioning for message sets and the only way to do it was by adding keyword.txt file inside the bar file and since we had CI tools to build bar the only option was to add few more lines of ant script to unzip the bar and insert the keywords.txt file. |
|
| Back to top |
|
|
| youto |
| Posted: Thu Oct 04, 2012 4:37 am Post subject: |
|
|
Novice
Joined: 07 Feb 2012
Posts: 16
|
all right, but we don't use any tool to build the bar-file.
We'll that's not completely true since I'm the one who builds them 
But seriously though, isn't anyone out there using the keywords.txt file in bar-files? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 04, 2012 4:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Another solution is to use whatever substitution facilties exist for your source control package. For example, coding $MQSI Version = $Revision$ MQSI$ causes SubVersion to replace that value with the revision held in the repository. This is usually a good enough use of the term "version", as what you usually need to know is what code was used to create the flow you're looking at at 3am when you've been woken by the production support people!
It's also not surprising that the Toolkit doesn't do this. The majority of sites don't allow Toolkit created bar files to be deployed out to non-development environments, but require them to be either deployed out via ant or similar script from a controlled repository. The ideal position (and aspirational in many sites) is for the bar file to be built from checked in code, thereby eliminating the developer's Toolkit from the process.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Oct 04, 2012 4:47 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
|
|
