Making Executable File Post: 302204802

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

pls hlp: making .sh files executable

I've got a file named jdictd.sh containing the following: --- begin file contents --- #! /bin/csh echo I\'m running! java -cp jdictd.jar org.dict.server.JDictd data/dict.ini # Use the following line instead if JRE 1.1 is used # jre -cp jdictd.jar org.dict.server.JDictd data/dict.ini ---end...

2. UNIX for Dummies Questions & Answers

Making UNIX script executable

Hello, I am very new to UNIX and I have been learning about writing scripts and making them executable. I created a script called myscript. It has three lines: #! /bin/sh # This is my first shell script echo friendsjustfriends Now I try to run it using the sh command and it works Next I...

3. UNIX for Dummies Questions & Answers

need help making a script executable

making a script in vi to create a shell script called wherearethey by entering the following script: echo -n "Who are you looking for: "read userif then list=`w | grep $user | cut -c19-30` if then echo "The user $user is logged in from $list" else echo "The user $user is not logged in...

4. Shell Programming and Scripting

problem in making Awk executable script

Guys I placed #!path/awk -f placed awk script and used $1 to call 1st inputfile inside the script. But some where I did mistake. Could you please help me run this script as executable I forgot to mention I also used BEGIN before placing awk script. But nothing worked out. Script ...

5. UNIX for Dummies Questions & Answers

Making file executable

Hi guys, i'm trying to make a file called 'run-all-tests' executable but it is not letting me for some reason. I am presented with the following error: chmod: cannot access `./run-tests': No such file or directory Basically i have a folder called ex3 and within that there are task folders:...

6. Shell Programming and Scripting

Making a perl script executable

Hello, I have a perl program called snp_hwe.pl I have another program called hwe_test.run which contains the following: for file in *.inp do cp $file genotype_counts_c.txt ./snp_hwe.exe > $file'.res' done I want to change my perl program to an executable program while changing...

7. UNIX for Advanced & Expert Users

What choice when "making" an executable on FreeBSD?

I should make an executable on our server, and are having some problem (I changed this question cause I found out that anser). I'm getting this error when trying to do make: In file included from... /usr/include/sys/file.h:161: error: expected specifier-qualifier-list before 'u_int' *** Error...

8. Shell Programming and Scripting

Making any script executable

Hi all, I'm new to Unix so just wanted some help. I've been self learning and came accross a question online that I was trying. It is to make any shell script executable, the name of the file is to be made executable. I would use nano and type in something like #! /bin/bash Chmod +x...

9. Shell Programming and Scripting

Making bash script allways executable when transfer ?

Does it possible to make some bash script automatic to be a executable when transfered to another pc...?

LEARN ABOUT DEBIAN

mh_installjar

MAVEN(1)							   User Commands							  MAVEN(1)

NAME

       Maven - Installs a jar into /usr/share/maven-repo.

SYNOPSIS

       mh_installjar [option]... [pom] [jar] [link]...

DESCRIPTION

       Installs the jar file in /usr/share/maven-repo, at the correct location for Maven. The jar is copied into the build directory.  It can also
       create additional links to the jar, usually located in /usr/share/java.

       Where

	      [pom] is the location of the POM associated with the jar to install.

	      GroupId, artifactId and version will be extracted from this file.

	      [jar] is the path to the jar to install, usually located in the build

	      folder.

	      [link] is an additional link to the jar to install, usually there should

	      be a link to usr/share/java/$jar.jar and usr/share/java/$jar-$version.jar to comply with the Java packaging  guidelines.	Note  that
	      there is no need to specify those particular links if the --java-lib option is used.

OPTIONS

       -h --help: show this text

       -V --version: show the version

       -p<package> --package=<package>: name of the Debian package which

	      will contain this jar file

       -e<version>, --set-version=<version>: set the version for the jar,

	      do not use the version declared in the POM file.

       -r<rules> --rules=<rules>: path to the file containing the

	      rules to apply when cleaning the POM.  Optional, the default location is debian/maven.rules Maven rules are used here to extract the
	      groupId, artifactId and version from the POM file.

       -l --java-lib: Optional, if given it will install the jar into

	      /usr/share/java to comply with the Debian Java specification.  The jar will be installed as /usr/share/java/$name-$version.jar and a
	      versionless link /usr/share/java/$name.jar will point to it, as well as the links installed in /usr/share/maven-repo

       -n<name> --usj-name=<name>: Optional, the name to use when installing the

	      library in /usr/share/java when --java-lib is used.  Defaults to the artifact id found in the POM.

       -j<version> --usj-version=<version>: Optional, the version to use when

	      installing the library in /usr/share/java when --java-lib is used.  Defaults to the version found in the POM.

       -s --no-usj-versionless: Optional, don't install the versionless link

	      in /usr/share/java.  This flag is used only when the -l or --java-lib option is given.

       -d<path> --dest-jar=<path>: Optional, the destination for the real jar.

	      The  other  places  where  the  jar  appears,  in the repository or in the list of links, will be symlinks to this jar.  Defaults to
	      /usr/share/java/$name-$version.jar if --java-lib is used, otherwise the jar is installed in the versioned path in the Maven  reposi-
	      tory.

       -c<classifier> --classifier=<classifier>: Optional, the classifier for

	      the jar. Empty by default.

       -v --verbose: show more information while running

       -n --no-act: don't actually do anything, just print the results

       --skip-clean-pom: don't clean the pom, assume that a previous action ran

	      mh_cleanpom with the correct options. mh_cleanpom is run only to extract the groupId, artifactId and version of the jar

       See also: mh_installpom(1), mh_installsite(1)

Maven Repo Helper version 1.7.1 				   January 2012 							  MAVEN(1)