| Author | Message | 
		
		  | sarathkumar1988 | 
			  
				|  Posted: Thu Nov 21, 2019 2:36 am    Post subject: Regarding Bar File Properties |   |  | 
		
		  | Newbie
 
 
 Joined: 21 Nov 2019Posts: 4
 
 
 | 
			  
				| Hi all, Can you help in my below query. 
 I have created a bar file (say on Jan 2) and i have applied override on the bar file(modified bar) (say on Jan 4). When i deploy this modified bar through toolkit in EG i see as Jan 4. The created bar(Jan 2), if just modify the properties and save the bar file it will show the present date but when i deploy in EG it will show as Jan 2.
 
 Is there any command for this to be achieved? like the way toolkit is achieving.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | abhi_thri | 
			  
				|  Posted: Thu Nov 21, 2019 3:18 am    Post subject: |   |  | 
		
		  |  Knight
 
 
 Joined: 17 Jul 2017Posts: 516
 Location: UK
 
 | 
			  
				| hi...sorry, are you asking whether it is possible to check by a command the 'Deployment Time' and 'Last Modified' properties of deployed artefacts? |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | sarathkumar1988 | 
			  
				|  Posted: Thu Nov 21, 2019 4:38 am    Post subject: |   |  | 
		
		  | Newbie
 
 
 Joined: 21 Nov 2019Posts: 4
 
 
 | 
			  
				| @abhi_thri I m looking for the command to achieve the same timestamp that a save of a bar file does in toolkit
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Thu Nov 21, 2019 5:39 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| Have you tried running the apply bar override without specifying an output bar i.e. against the existing bar file? I believe this would preserve the created date.  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | sarathkumar1988 | 
			  
				|  Posted: Thu Nov 21, 2019 10:19 pm    Post subject: |   |  | 
		
		  | Newbie
 
 
 Joined: 21 Nov 2019Posts: 4
 
 
 | 
			  
				| @fjb_saper 
 Thanks for the response. No Luck. I have tried applying override over the existing barfile. When i deployed this bar file in EG through toolkit, it is showing the last modified(when the applyoverride date) has been done.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | timber | 
			  
				|  Posted: Fri Nov 22, 2019 3:30 am    Post subject: |   |  | 
		
		  |  Grand Master
 
 
 Joined: 25 Aug 2015Posts: 1292
 
 
 | 
			  
				| Why does the date matter so much. For me, the important information is the tag or commit id from which the BAR file was built. That should be in the keywords.txt. |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | sarathkumar1988 | 
			  
				|  Posted: Fri Nov 22, 2019 4:22 am    Post subject: |   |  | 
		
		  | Newbie
 
 
 Joined: 21 Nov 2019Posts: 4
 
 
 | 
			  
				| The requirement is in such a way that, they should know the date of the bar file. So that they can refer to this bar file as and when required |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Fri Nov 22, 2019 6:52 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| 
   
	| sarathkumar1988 wrote: |  
	| The requirement is in such a way that, they should know the date of the bar file. So that they can refer to this bar file as and when required |  You should revise the requirement. The bar file is not important because, if you have a correct source control system, you should be able to rebuild it, at any time. What it important, is to refer to the source control tag from which it was built!
 Have fun
  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Vitor | 
			  
				|  Posted: Sun Nov 24, 2019 10:39 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| 
   
	| fjb_saper wrote: |  
	| 
   
	| sarathkumar1988 wrote: |  
	| The requirement is in such a way that, they should know the date of the bar file. So that they can refer to this bar file as and when required |  You should revise the requirement. The bar file is not important because, if you have a correct source control system, you should be able to rebuild it, at any time. What it important, is to refer to the source control tag from which it was built!
 |  
 
   
 The bar file is simply a deployment mechanism. There's no explicit correlation between a bar file and what it contains; the bar file name & contents are arbitrary. There's no reason why you couldn't build a bar file called bar.bar every time and deploy that.
 
 The explicit (and useful) correlation is the source tag it was build from, as mentioned above.
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |