Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 615079 Details for
Bug 758051
[abrt] jpackage-utils-1.7.5-15.fc16: maven_depmap.py:79:_get_jpp_from_filename:IOError: Jar path doesn't exist
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
Patch to handle full path jar argument
macros.fjava (text/plain), 7.25 KB, created by
Clément DAVID
on 2012-09-20 19:26:08 UTC
(
hide
)
Description:
Patch to handle full path jar argument
Filename:
MIME Type:
Creator:
Clément DAVID
Created:
2012-09-20 19:26:08 UTC
Size:
7.25 KB
patch
obsolete
># Copyright (c) 2011, Red Hat, Inc ># ># All rights reserved. ># ># Redistribution and use in source and binary forms, with or without modification, ># are permitted provided that the following conditions are met: ># ># * Redistributions of source code must retain the above copyright notice, this ># list of conditions and the following disclaimer. ># * Redistributions in binary form must reproduce the above copyright notice, ># this list of conditions and the following disclaimer in the documentation ># and/or other materials provided with the distribution. ># * Neither the name of the <ORGANIZATION> nor the names of its contributors ># may be used to endorse or promote products derived from this software ># without specific prior written permission. ># ># THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ''AS IS'' AND ANY ># EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED ># WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE ># DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY ># DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES ># (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; ># LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ># ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT ># (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS ># SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ># ># Authors: Stanislav Ochotnicky <sochotnicky@redhat.com> ># Mikolaj Izdebski <mizdebsk@redhat.com> > > >#============================================================================== ># ># add_maven_depmap is simplified version of jpackage-style add_to_maven_depmap ># -f addition to fragment name ># -a is "g1:a1,g2:a2" formatted string with additional depmaps (groupId:artifactId,...) ># %1 is the pom filename relative to mavenpomdir ># %2 is the path to jar file (when omitted we deal with parent pom file without jar) ># ># add_maven_depmap automatically parses pom file and it will fail with incorrect pom ># or jar filename ># > >%add_maven_depmap(f:a:) \ ># default values \ >%if %# == 0 \ > _pompart="JPP-%{name}.pom" \ > _jarpart="%{name}.jar" \ >%else \ > _pompart="%1" \ > _jarpart="%2" \ >%endif \ >install -dm 755 $RPM_BUILD_ROOT/%{_mavendepmapfragdir}\ >_jpath="$_jarpart" \ >if [ -f $_jarpart ]; then \ > _jpath="$_jarpart" \ >if [ -f %{buildroot}/%{_javadir}/$_jarpart ]; then \ > _jpath="%{buildroot}/%{_javadir}/$_jarpart" \ >elif [ -f %{buildroot}/%{_javajnidir}/$_jarpart ]; then \ > _jpath="%{buildroot}/%{_javajnidir}/$_jarpart" \ >elif [ -f %{buildroot}/%{_jnidir}/$_jarpart ]; then \ > _jpath="%{buildroot}/%{_jnidir}/$_jarpart" \ >fi \ >python -m %{_datadir}/java-utils/maven_depmap %{-a} \\\ > %{buildroot}%{_mavendepmapfragdir}/%{name}%{-f*:-%{-f*}} \\\ > %{buildroot}%{_mavenpomdir}/$_pompart \\\ >%if %# == 2 \ > "${_jpath}" \\\ >%endif \ >%if %# == 0 \ > "${_jpath}" \\\ >%endif \ >\ >%{nil} > >#============================================================================== > > > >#============================================================================== ># ># %pom_* -- macros for batch editing of POM files ># ># These macros can be used to edit Maven POM files directly from RPM spec ># file. Using these macros it is possible to alter Maven dependency management, ># change plugin invocation, or even inject or remove arbitrary XML code to/from ># nodes described by an XPath expression. ># ># See comments preceding individual macros for more detailed documentation. ># > ># Private macro, shouldn't be used directly >%__pom_call . %{_datadir}/java-utils/pom_editor.sh; pom_ > > ># %pom_remove_dep - remove dependency on Maven artifact from POM file ># ># Usage: %pom_remove_dep [groupId]:[artifactId] [POM location] ># ># This macro patches specified POM file not to contain dependencies on given ># Maven artifact. ># ># groupId and artifactId are identifiers of Maven group and artifact of the ># module on which dependency is to be removed. If they are ommited then all ># identifiers are matched. ># ># 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. ># >%pom_remove_dep() %{expand: %{__pom_call}remove_dep %* >} > > ># %pom_remove_plugin - remove Maven plugin invocation from POM file ># ># Usage: %pom_remove_plugin [groupId]:[artifactId] [POM location] ># ># This macro patches specified POM file not to contain invocations of given ># Maven plugin. ># ># groupId and artifactId are identifiers of Maven group and artifact of the ># plugin which invocation is to be removed. If they are ommited then all ># identifiers are matched. ># ># 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. ># >%pom_remove_plugin() %{expand: %{__pom_call}remove_plugin %* >} > > ># %pom_disable_module - disable given project module in POM file ># ># Usage: %pom_disable_module <module name> [POM location] ># ># This macro patches specified POM file not to contain reference to given ># project module. ># ># Module name is the exact name of the module to be disabled. It must not be ># ommited. ># ># 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. ># >%pom_disable_module() %{expand: %{__pom_call}disable_module %* >} > > ># %pom_xpath_remove - remove an XML node from POM file ># ># Usage: %pom_xpath_remove <XPath> [POM location] ># ># This macro patches specified POM file removing all XML nodes described by the ># XPath expression. ># ># XPath is an expression describing a set of XML nodes to be removed from the ># POM file. It must be a properly formated XPath 1.0 expression, as described ># in <http://www.w3.org/TR/xpath/>. ># ># 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. ># ># NOTE: POM files use a specific namespace - http://maven.apache.org/POM/4.0.0. ># The easiest way to respect this namespace in XPath expressions is prefixing ># all node names with "pom:". For example, "pom:environment/pom:os" will work ># because it selects nodes from pom namespace, but "environment/os" won't find ># anything because it looks for nodes that don't belong to any XML namespace. ># >%pom_xpath_remove() %{expand: %{__pom_call}xpath_remove %* >} > > ># %pom_xpath_inject - inject XML code into POM file ># ># Usage: %pom_xpath_inject <XPath> [XML code] [POM location] ># ># This macro patches specified POM file appending some code as childreen of all ># XML nodes described by the XPath expression. ># ># XPath is an expression describing a set of XML nodes in the POM file to which ># child code is to be appended. It must be a properly formated XPath 1.0 ># expression, as described in <http://www.w3.org/TR/xpath/>. ># ># 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. ># >%pom_xpath_inject() %{expand: %{__pom_call}xpath_inject %* >}
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 758051
: 615079