return 0

  	fi

  	_jar_filename=`basename $1`

  	_search_name=`basename $1`

  	_search_name=`echo $_search_name | sed -r -e s/-[[:digit:].]*\\\.jar//g | sed -r -e s/\\\.jar$//g`

  			continue

  		fi

  		_jar_filename=`basename $file`

  		_search_name=`basename $file`

  		_search_name=`echo $_search_name | sed -r -e s/-[[:digit:].]*\\\.jar//g | sed -r -e s/\\\.jar$//g`

  Apache Ant is probably second most used Java build tool right after Apache

  Maven. The main difference between these two tools is that Ant is procedural and

  processes which lead to the result. It means that one needs to specify where the

  source files are, what needs to be done and when it needs to be done. On the

  other hand, Maven relies on conventions and doesn't require specifying most

  Details:

      - The publish target may be named differently. Search the `build.xml`

      - `%mvn_install` will install all the published artifacts.

  The Java packaging tooling on Fedora provides automatic Requires and

  Provides generation for packages built using XMvn. The Provides are based

  on Maven artifact coordinates of artifacts that were installed by the

  separately. They follow a general format

  `mvn(groupId:artifactId:extension:classifier:version)`, where the

  extension is omitted if it's `jar` and classifier is omitted if empty.

  --------

  `log4j` corresponds to `log4j.jar` stored in `%{_javadir}`. If the JAR

  pass `subdirectory/jarname` as an argument to `build-classpath`.

  Example:

  .Make

  While unlikely, it's still possible that you encounter a project whose

  build is managed by plain old Makefiles. They contain a list of targets

  are invoked by `make` _target_ or simply `make` to run the default

  target.

  In the real world the same project can appear under different names as it was

  evolving or released differently. Therefore other projects may refer to those

  ===== Artifact aliases

  XMvn provides a way to attach multiple artifact coordinates to a single

  package to the new version and create new package representing the old

  version (called compat package). The compat package needs to have the

  version number (usually only the major number, unless further

  different name from RPM's point of view. Such compat package needs to

  perform some additional steps to ensure that it can be installed and

  used along the non-compat one.

  %prep

  # The default location for installing JAR files is %{_javadir}/%{name}/

  # Because our original specfile put the JAR directly to %{_javadir}, we

  # install the groupId:artifactId artifact as %{_javadir}/%{name}.jar

  %mvn_file groupId:artifactId %{name}

  See <<mvn_alias,Additional Mappings>> for more information on `%mvn_alias`.

  [source,shell]

  ------

      # try to find it from java command

      # try javac first, or we might get the location of the jre instead - djw

      case "${_prefer_jre}" in

  	1|[Yy][Ee][Ss]|[Tt][Rr][Uu][Ee])

  	    cmds=java

  }

  find_jar()

  {

      local IFS=:

  # This macro causes given artifact(s) to be installed in given subpackage.

  #

  # GId, aId and ver can contain wildcards and alternatives, which allows

  # then any value will match the respective part. In particular a bare :

  # symbol will match any artifact.

  #

  # resolve any of aliases will result in resolving the original artifact.

  #

  # GId, aId and ver can contain wildcards and alternatives, which allows

  # then any value will match the respective part. In particular a bare :

  # symbol will match any artifact.

  #

  # Usage: %mvn_file [gId]:[aId[:ver]] <file1> [file2 ...]

  #

  # GId, aId and ver can contain wildcards and alternatives, which allows

  # then any value will match the respective part. In particular a bare :

  # symbol will match any artifact.

  #

  # Usage: %mvn_compat_version [gId]:[aId[:ver]] <version1> [version2 ...]

  #

  # GId, aId and ver can contain wildcards and alternatives, which allows

  # then any value will match the respective part. In particular a bare :

  # symbol will match any artifact.

  #

  # Maven artifact.

  #

  # groupId and artifactId are identifiers of Maven group and artifact of the

  # identifiers are matched.

  #

  # POM location can be either a full path to the POM file, or a path to the

  # Maven plugin.

  #

  # groupId and artifactId are identifiers of Maven group and artifact of the

  # identifiers are matched.

  #

  # POM location can be either a full path to the POM file, or a path to the

  # project module.

  #

  # Module name is the exact name of the module to be disabled. It must not be

  #

  # POM location can be either a full path to the POM file, or a path to the

  # directory containing pom.xml. If POM location is not given then pom.xml from

  # current working directory is used.

  #

  # Extra XML is additional XML code to be added into the <dependency> node. This

  #

  %pom_add_dep()        %{expand: %{__pom_call}add_dep        %*

  }

  # groupId and artifactId.

  #

  # groupId and artifactId are identifiers of Maven plugin artifact of which

  # "org.apache.maven.plugins" is used as default. artifactId must be

  # specified. If version is not specified then default value of "any" is used.

  #

  # current working directory is used.

  #

  # Extra XML is additional XML code to be added into the <plugin> node. This

  #

  %pom_add_plugin()     %{expand: %{__pom_call}add_plugin     %*

  }

  processed. You can specify more file locations which will be processed.

  Extra XML is additional XML code to be added into the *<dependency>*

  appended.

  EXAMPLES

  given groupId and artifactId.

  groupId and artifactId are identifiers of Maven plugin artifact of

  case value of "org.apache.maven.plugins" is used as default.

  artifactId must be specified.  If version is not specified then

  default value of "any" is used.

  file locations which will be processed.

  Extra XML is additional XML code to be added into the *<plugin>* node.

  EXAMPLES

  --------

  processed. You can specify more file locations which will be processed.

  Extra XML is additional XML code to be added into the *<dependency>*

  appended.

  EXAMPLES

  given project module.

  Module name is the exact name of the module to be disabled. It must

  POM location can be either a full path to the POM file, or a path to

  the directory containing *pom.xml*.  If POM location is not given then

  given Maven artifact.

  groupId and artifactId are identifiers of Maven group and artifact of

  then all identifiers are matched.

  When modifying Ivy modules, the org and name correspond to the Maven

  used. When both *pom.xml* and *ivy.xml* are present, *pom.xml* is

  processed. You can specify more file locations. If the dependency is not

  found in all of given files, the command raises an error. This can be

  EXAMPLES

  given Maven plugin.

  groupId and artifactId are identifiers of Maven group and artifact of

  then all identifiers are matched.

  POM location can be either a full path to the POM file, or a path to

  -----------

  *shade-jar* utility is means for changing JAR file namespaces.

  replacement.  The replacament is performed on class file names and

  inside the class files themselves.  This is commonly known as

  _shading_.

  --------

  *shade-jar org.apache.log4j com.example.shaded.log4j

  /usr/share/java/log4j.jar lib/shaded-log4j.jar* will replace all

  */usr/share/java/log4j.jar* with *com.example.shaded.log4j* and store

  the resulting JAR in *lib/shaded-log4j.jar*.