<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>A Day At The Races &#187; scripts</title>
	<atom:link href="http://blog.jetztgrad.net/category/scripts/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jetztgrad.net</link>
	<description>Programming was my first love, and it will be my last.</description>
	<lastBuildDate>Thu, 05 May 2011 08:21:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Updated bash completion script for OSX and Grails 1.1 &amp; 1.2</title>
		<link>http://blog.jetztgrad.net/2010/01/updated-bash-completion-script-for-osx-and-grails-1-1-1-2/</link>
		<comments>http://blog.jetztgrad.net/2010/01/updated-bash-completion-script-for-osx-and-grails-1-1-1-2/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 12:03:16 +0000</pubDate>
		<dc:creator>Wolfgang Schell</dc:creator>
				<category><![CDATA[grails]]></category>
		<category><![CDATA[scripts]]></category>

		<guid isPermaLink="false">http://blog.jetztgrad.net/?p=174</guid>
		<description><![CDATA[Fernando Takai wrote an excellent bash completion script (also available here, originally from Ted Naleid), which makes calling Grails commands much easier. Some examples: Within a Grails application directory, listing all available commands: myapp&#62; grails [tab][tab] bootstrap create-integration-test generate-controller list-plugins_ set-version bug-report create-plugin_ generate-views package shell clean create-script help_ package-plugin_ stats compile create-service init plugin-info_ [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://fernandotakai.wordpress.com/2008/08/05/grails-auto-complete/">Fernando Takai</a> wrote an excellent bash completion script (also available <a href="http://www.grails.org/Grails+Bash+Completion+Script">here</a>, originally from <a href="http://naleid.com/blog/2008/03/25/autocomplete-grails-script-names-in-bashzsh/">Ted Naleid</a>), which makes calling Grails commands much easier. </p>
<p>Some examples: </p>
<p>Within a Grails application directory, listing all available commands:</p>
<p><code>myapp&gt; grails [tab][tab]<br />
bootstrap                create-integration-test  generate-controller      list-plugins_            set-version<br />
bug-report               create-plugin_           generate-views           package                  shell<br />
clean                    create-script            help_                    package-plugin_          stats<br />
compile                  create-service           init                     plugin-info_             test-app<br />
console                  create-tag-lib           install-dependency       release-plugin           tomcat<br />
create-app_              create-unit-test         install-plugin           run-app                  uninstall-plugin<br />
create-controller        dependency-report        install-templates        run-war                  upgrade<br />
create-domain-class      doc                      integrate-with           schema-export            war<br />
create-filters           generate-all             list-plugin-updates      set-proxy_<br />
</code></p>
<p>Within a Grails application directory, completing a command:</p>
<p><code>myapp&gt; grails run-[tab][tab]<br />
run-app  run-war<br />
</code></p>
<p>Outside of a Grails application directory, listing all available commands:</p>
<p><code>home&gt; grails [tab][tab]<br />
create-app      create-plugin   help            list-plugins    package-plugin  plugin-info     set-proxy<br />
</code></p>
<p><b>Changes</b></p>
<p>I updated the script to adapt it to new Grails versions and made some minor changes:</p>
<p>* works with plugin provided scripts in Grails version >= 1.1, were plugins are stored under <code>$HOME/.grails/<em>grailsversion</em>/projects/<em>appname</em>/plugins</code>.<br />
* detects the Grails version from <code>$GRAILS_HOME</code> instead of choosing the latest version from <code>$HOME/.grails</code>.<br />
* adapts to different locations of <code>plugins-list.xml</code>, which changed with newer Grails versions<br />
* does not need gawk (which is not installed by default on OSX)</p>
<p>My version of the script was tested with Grails 1.2 and OSX Snow Leopard and can be found at <a href="http://gist.github.com/270209">GitHub</a> or below.</p>
<p><b>Installation</b></p>
<p>Save the script to an appropriate path (e.g. <code>~/bin/grails-bash-completion.sh</code>)<br />
<code>[ -r ~/bin/grails-bash-completion.sh ] &#038;&#038; source ~/bin/grails-bash-completion.sh</code></p>
<p><b>The complete Script</b></p>
<script src="http://gist.github.com/270209.js"></script>
]]></content:encoded>
			<wfw:commentRss>http://blog.jetztgrad.net/2010/01/updated-bash-completion-script-for-osx-and-grails-1-1-1-2/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Script to inspect jar and war files, Grails applications and plugins</title>
		<link>http://blog.jetztgrad.net/2010/01/script-to-inspect-jar-and-war-files-grails-applications-and-plugins/</link>
		<comments>http://blog.jetztgrad.net/2010/01/script-to-inspect-jar-and-war-files-grails-applications-and-plugins/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 12:42:57 +0000</pubDate>
		<dc:creator>Wolfgang Schell</dc:creator>
				<category><![CDATA[grails]]></category>
		<category><![CDATA[scripts]]></category>

		<guid isPermaLink="false">http://blog.jetztgrad.net/?p=162</guid>
		<description><![CDATA[I just wrote a little script to inspect jar and war files, Grails applications and plugins. Installation Simply copy the script to somewhere in your path (e.g. ~/bin) and make it executable using chmod +x jinspect I tested the script on OSX Snow Leopard, but it should run on other versions of OSX and Linux, [...]]]></description>
			<content:encoded><![CDATA[<p>I just wrote a <a href="http://gist.github.com/268474">little script</a> to inspect jar and war files, Grails applications and plugins.</p>
<p><b>Installation</b></p>
<p>Simply copy the script to somewhere in your path (e.g. <code>~/bin</code>) and make it executable using<br />
<code>chmod +x jinspect</code></p>
<p>I tested the script on OSX Snow Leopard, but it should run on other versions of OSX and Linux, too. </p>
<p><b>Examples:</b></p>
<p>List all files in a war/jar/zip:<br />
<code>jinspect -l myapp.war</code></p>
<p>Show contents of some files in a jar/war/zip:<br />
<code>jinspect myapp.war index.html another.txt</code></p>
<p>List gsp and jsp files in a war:<br />
<code>jinspect -JG myapp.war</code></p>
<p>Show contents of web.xml file in a war:<br />
<code>jinspect -w myapp.war</code></p>
<p>Extract and save web.xml file in a war:<br />
<code>jinspect -Xw myapp.war</code></p>
<p>Show contents of the Plugin class of a Grails plugin:<br />
<code>jinspect -P grails-osgi-0.1.zip</code></p>
<p><b>Available options:</b><br />
<code><br />
jinspect [-hHvxXoawmISMWjJrgGcCpPlLZZZ] jarfile [filename ...]<br />
Options:<br />
-h show help<br />
-v be more verbose<br />
-X save specified files (including path) to the current directory instead of printing them<br />
-l list war contents; specify again to include more information<br />
-x list xml files<br />
-o list properties files<br />
-c list class files<br />
-j list java files<br />
-J list jsp files<br />
-S list js files<br />
-g list groovy files<br />
-G list gsp files<br />
-H list html files<br />
-C list css files<br />
-I list image files<br />
-L list files in lib directory<br />
-M list files in META-INF directory<br />
-W list files in WEB-INF directory<br />
-a show WEB-INF/applicationContext.xml<br />
-w show WEB-INF/web.xml<br />
-r show WEB-INF/grails.xml<br />
-m show META-INF/MANIFEST.MF<br />
-p show plugin.xml<br />
-P show *GrailsPlugin.groovy<br />
-d show manifest headers in nicely formatted way; implies -m<br />
-D <name> display named manifest header; can be used multiple times, implies -m<br />
</code></p>
<p><b>Script</b><br />
(also available on <a href="http://gist.github.com/268474">GitHub</a>)<br />
<script src="http://gist.github.com/268474.js"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jetztgrad.net/2010/01/script-to-inspect-jar-and-war-files-grails-applications-and-plugins/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

