[Bug 998322] New: javapackages-tools: add_pom_dep_mgmt injects incorrect xml
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=998322
Bug ID: 998322
Summary: javapackages-tools: add_pom_dep_mgmt injects incorrect
xml
Product: Fedora
Version: rawhide
Component: javapackages-tools
Assignee: sochotni(a)redhat.com
Reporter: mspaulding06(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msrb(a)redhat.com,
sochotni(a)redhat.com
Created attachment 787875
--> https://bugzilla.redhat.com/attachment.cgi?id=787875&action=edit
Patch against upstream repository to fix add_pom_dep_mgmt macro
Description of problem:
The add_pom_dep_mgmt macro does not inject the correct xml into the pom file,
since it does not include "dependencies" in the xpath when doing the injection.
Version-Release number of selected component (if applicable):
2.0.1-1
How reproducible:
Always
Steps to Reproduce:
1. Use the add_pom_dep_mgmt macro in an RPM spec file.
Actual results:
RPM build will fail since the pom file is incorrect. The "dependency" node is
injected right after the "dependencyManagement" node in the pom file.
Expected results:
The dependency gets injected inside the "dependencies" node which is under the
"dependencyManagement" node.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=13NM7CRSvW&a=cc_unsubscribe
10 years, 7 months
[Bug 957181] New: hawtjni: missing barriers in cache initialization
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=957181
Bug ID: 957181
Summary: hawtjni: missing barriers in cache initialization
Product: Fedora
Version: rawhide
Component: hawtjni
Severity: unspecified
Priority: unspecified
Assignee: mgoldman(a)redhat.com
Reporter: fweimer(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mgoldman(a)redhat.com, mizdebsk(a)redhat.com
Blocks: 957130
Category: ---
The following code is generated from the example:
void cachebarFields(JNIEnv *env, jobject lpObject)
{
if (barFc.cached) return;
barFc.clazz = env->GetObjectClass(lpObject);
barFc.a = env->GetFieldID(barFc.clazz, "a", "I");
barFc.b = env->GetFieldID(barFc.clazz, "b", "J");
barFc.c = env->GetFieldID(barFc.clazz, "c", "[B");
barFc.c5 = env->GetFieldID(barFc.clazz, "c5", "B");
barFc.prev = env->GetFieldID(barFc.clazz, "prev", "J");
barFc.cached = 1;
}
There are no barriers, so readers may observe the write to the "cached" member
before the other members.
(One of the barFc.cached checks is redundant, BTW.)
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=eKi1w394jB&a=cc_unsubscribe
10 years, 7 months
[Bug 998463] New: javapackages-tools: whitespace breaks XML node matching for pom macros
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=998463
Bug ID: 998463
Summary: javapackages-tools: whitespace breaks XML node
matching for pom macros
Product: Fedora
Version: 18
Component: javapackages-tools
Assignee: msimacek(a)redhat.com
Reporter: sochotni(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msrb(a)redhat.com,
sochotni(a)redhat.com
Description of problem:
When artifactId (or other node which is being matched) contains whitespace such
as new line it will break XML node matching causing pom modification to fail.
Example snippet:
<build>
...
<plugins>
...
<plugin>
<artifactId>maven-compiler-plugin
</artifactId> <!-- HERE -->
<configuration>
<source>1.4</source>
<target>1.4</target>
</configuration>
</plugin
...
</plugins>
...
</build>
This example was taken from plexus-sec-dispatcher which currently suffers from
this problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=pyVCP1X17C&a=cc_unsubscribe
10 years, 7 months
[Bug 1002223] New: No splash screen shown on launch of Myrtle
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1002223
Bug ID: 1002223
Summary: No splash screen shown on launch of Myrtle
Product: Fedora
Version: 19
Component: snifflib
Severity: medium
Assignee: msimacek(a)redhat.com
Reporter: mray271(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, mray271(a)gmail.com,
msimacek(a)redhat.com, msrb(a)redhat.com,
sochotni(a)redhat.com
Created attachment 791459
--> https://bugzilla.redhat.com/attachment.cgi?id=791459&action=edit
Proposed patch to /usr/bin/myrtle
Description of problem:
Launching Myrtle spreadsheet by /usr/bin/myrtle script should produce splash
image.
Version-Release number of selected component (if applicable):
1.8.12-1.fc19.noarch
currently available from the fedora-updates-testing repository
How reproducible:
Always
Steps to Reproduce:
1. yum install myrtle
2. myrtle
3.
Actual results:
Spreadsheet application opens as intended, but no splash shown.
Expected results:
Splash image should be shown briefly prior to application launch.
Additional info:
The splash image is a resource in in snifflib.jar
(/usr/share/java/snifflib.jar) and has path
com/mockturtlesolutions/snifflib/spreadsheets/images/myrtlesplash.png
See attached patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ha0RKcnMwt&a=cc_unsubscribe
10 years, 7 months
[Bug 959454] New: plexus-digest: do not use algorithm name as regular expression
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=959454
Bug ID: 959454
Summary: plexus-digest: do not use algorithm name as regular
expression
Product: Fedora
Version: rawhide
Component: plexus-digest
Severity: unspecified
Priority: unspecified
Assignee: sochotni(a)redhat.com
Reporter: fweimer(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jcapik(a)redhat.com, mizdebsk(a)redhat.com,
msrb(a)redhat.com, overholt(a)gmail.com,
sochotni(a)redhat.com, tradej(a)redhat.com
Blocks: 959453
Category: ---
In org.codehaus.plexus.digest.DigestUtils.cleanChecksum(String, String,
String), the second parameter is used as part of the regular expression.
Compiling the resulting regular expression can result in a VM error with a
crafted algorithm name. The regular expression should be a constant, with a
capture group for the algorithm name, and the name should be checked after
matching.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=k7YPjOe1Ue&a=cc_unsubscribe
10 years, 7 months
[Bug 912333] New: mvn-rpmbuild if F19 does not export M2_HOME
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=912333
Bug ID: 912333
Summary: mvn-rpmbuild if F19 does not export M2_HOME
Product: Fedora
Version: rawhide
Component: javapackages-tools
Severity: unspecified
Priority: unspecified
Reporter: mattias.ellert(a)fysast.uu.se
Description of problem:
mvn-rpmbuild on Fedora 19 does not export M2_HOME
Version-Release number of selected component (if applicable):
javapackages-tools.noarch 0:0.12.0-1.fc19
How reproducible:
Packages in the f19 rebuild failed due to M2_HOME not set. See e.g.
https://koji.fedoraproject.org/koji/taskinfo?taskID=4996219
Error message is:
"Maven application directory was not specified, and ${maven.home} is not
provided in the system properties. Please specify at least on of these."
The code generating this error message is:
if ( ( mavenHome == null ) && ( System.getProperty( "maven.home" ) == null ) )
{
if ( !getSystemEnvVars().containsKey( "M2_HOME" ) )
{
throw new IllegalStateException( "Maven application directory was
+ "specified, and ${maven.home} is not provided in the system "
+ "properties. Please specify at least on of these." );
}
}
I.e. if M2_HOME is set (like in mvn-rpmbuild for Fedora 18 and earlier) the
exception is not thrown.
Actual results:
Failed builds due to M2_HOME not set
Expected results:
Working build
Additional info:
mvn-rpmbuild on Fedora 17 contains the line
export M2_HOME=/usr/share/maven
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=U9jVwfslmC&a=cc_unsubscribe
10 years, 7 months
[Bug 875817] New: Port velocity not to use werken-xpath
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=875817
Bug ID: 875817
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: rawhide
Priority: unspecified
CC: devrim(a)gunduz.org,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, sochotni(a)redhat.com
Assignee: sochotni(a)redhat.com
Summary: Port velocity not to use werken-xpath
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: sochotni(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: velocity
Product: Fedora
Description of problem:
werken is an old unmaintained library. Velocity should be ported away and just
use standard Java interfaces preferably. Needs getting in touch with upstream
of course
Slightly related bugreports upstream:
https://issues.apache.org/jira/browse/VELOCITY-757
https://issues.apache.org/jira/browse/VELOCITY-694
--
You are receiving this mail because:
You are on the CC list for the bug.
10 years, 7 months