CDV ❯ BootJarTool doesn't ensure output directory exists

• Type: Bug
• Status: Closed
• Priority: 2 Major
• Resolution: As Designed
• Component/s:
• Labels:

• Assignee: gkeim
• Reporter: gkeim
• Created: November 21, 2008
• Votes: 0
• Watchers: 0
• Updated:

  December 16, 2008
• Resolved:

  November 21, 2008

Description

cd $TC_HOME rm -rf lib/dso-boot bin/make-boot-jar.sh -o lib/dso-boot -f samples/tc-config.xml Successfully created boot JAR file at ‘c:\dso\enterprise\branches\2.7\community\code\base\build\dist\terracotta-2.7.2-ee\lib\dso-boot’.

Comments

Gary Keim 2008-11-21

I’m wrong. -o foo should create a bootjar named foo if foo isn’t a directory, else it creates the appropriately named file in foo. This all came about because lib/dso-boot is no longer created in the kit in trunk and the Session Configurator was invoking make-boot-jar as above. Fix is to change the configurator script to ensure lib/dso-boot exists.