[Bug 842611] New: lucene - compile with -target 1.5 or greater
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=842611
Bug ID: 842611
QA Contact: extras-qa(a)fedoraproject.org
Severity: medium
Version: rawhide
Priority: medium
CC: akurtako(a)redhat.com, hicham.haouari(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
kdaniel(a)redhat.com
Assignee: akurtako(a)redhat.com
Summary: lucene - compile with -target 1.5 or greater
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: mizdebsk(a)redhat.com
Type: ---
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: lucene
Product: Fedora
Package lucene appears to be using Java generics,
but generates class files in format older than 49.0,
which corresponds to J2SE 5.0, in which generics were introduced.
Please update this package to generate classes in format 49.0 or
above. This corresponds to -target 1.5 option of javac (or ecj).
For more information, see bug #842394
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 2 months
[Bug 830762] New: lucene ships POMs with uninitialized version properties
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=830762
Bug ID: 830762
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: 17
Priority: unspecified
CC: akurtako(a)redhat.com, hicham.haouari(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
kdaniel(a)redhat.com
Assignee: akurtako(a)redhat.com
Summary: lucene ships POMs with uninitialized version
properties
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: michel+fdr(a)sylvestre.me
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: lucene
Product: Fedora
Created attachment 590902
--> https://bugzilla.redhat.com/attachment.cgi?id=590902&action=edit
POM file for clucy
Description of problem:
The latest Lucene RPM ships with POMs that have unitialized version properties,
thus causing mvn-rpmpackage to fail when building a package that uses Lucene as
a dependency.
Version-Release number of selected component (if applicable):
lucene-2.9.4-8.fc17.noarch
How reproducible:
Always
Steps to Reproduce:
1. grep "<version>@version@</version>" *lucene*.pom | wc -l
2. Attempt to build clucy (https://github.com/weavejester/clucy) using the
attached POM file
Actual results:
1. => 59
2. => fails with
[ERROR] Failed to execute goal on project clucy: Could not resolve dependencies
for project clucy:clucy:jar:0.3.0: The following artifacts could not be
resolved
: org.apache.lucene:lucene-highlighter:jar:latest,
org.apache.lucene:lucene-memo
ry:jar:@version@: The repository system is offline but the artifact
org.apache.l
ucene:lucene-highlighter:jar:latest is not available in the local repository.
->
[Help 1]
Expected results:
1. => 0
2. => succeeds
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 2 months
[Bug 880282] New: Licence file missing
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=880282
Bug ID: 880282
Summary: Licence file missing
Product: Fedora
Version: rawhide
Component: plexus-cli
Severity: unspecified
Priority: unspecified
Reporter: tradej(a)redhat.com
The package is missing a licence file, which must be present to satisfy
paragraph 4., bullet 1. of the Apache Licence v2.0, which it is licensed under.
Please, provide it.
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 2 months
[Bug 786881] New: 'cat: command not found' in install.log file after installation
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: 'cat: command not found' in install.log file after installation
https://bugzilla.redhat.com/show_bug.cgi?id=786881
Summary: 'cat: command not found' in install.log file after
installation
Product: Fedora
Version: 16
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: low
Priority: unspecified
Component: plexus-interpolation
AssignedTo: sochotni(a)redhat.com
ReportedBy: liebundartig(a)freenet.de
QAContact: extras-qa(a)fedoraproject.org
CC: sochotni(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jcapik(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Created attachment 559082
--> https://bugzilla.redhat.com/attachment.cgi?id=559082
anaconda kickstart and install.log files
Description of problem:
after installation of f16 using attached kickstart file
there is an error message in
/root/install.log
Not sure if that is a problem, though.
Version-Release number of selected component (if applicable):
date of writing: 02. February 2012
How reproducible:
100%
Steps to Reproduce:
1. install fedora 16 with attached kickstart file
2. review /root/install.log
Actual results:
22:46:08 Installing plexus-interpolation-1.14-1.fc16.noarch
/var/tmp/rpm-tmp.FbugDW: line 4: cat: command not found
Expected results:
plexus-interpolation should install without the message
or
if the error message is not important, should state that the message is not
important
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 3 months
[Bug 784816] New: Maven uses the wrong xerces version
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Maven uses the wrong xerces version
https://bugzilla.redhat.com/show_bug.cgi?id=784816
Summary: Maven uses the wrong xerces version
Product: Fedora
Version: 16
Platform: Unspecified
OS/Version: All
Status: NEW
Severity: unspecified
Priority: unspecified
Component: maven
AssignedTo: sochotni(a)redhat.com
ReportedBy: cdewolf(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, sochotni(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Created attachment 557637
--> https://bugzilla.redhat.com/attachment.cgi?id=557637
upstream vs installed
Description of problem:
When developing a Maven extension that uses DOM you run into trouble if you do
not load the default installed extension libraries.
/usr/share/maven/lib/ext contains xml-commons-apis.jar to hide the fact that
/usr/share/maven/lib/xerces-j2.jar is not the same as xercesMinimal-1.9.6.2.jar
which comes with the upstream distribution.
Version-Release number of selected component (if applicable):
maven-3.0.3-15.fc16.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Write an extension that does not incorporate the default lib/ext
2. Use the extension
Actual results:
Observe the java.lang.ClassNotFoundException: org.w3c.dom.ElementTraversal
Expected results:
A working extension.
Additional info:
In the attachment there is a diff between a run with upstream and a run with
installed maven.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 3 months
[Bug 759470] New: resolver - latest vs. LATEST
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: resolver - latest vs. LATEST
https://bugzilla.redhat.com/show_bug.cgi?id=759470
Summary: resolver - latest vs. LATEST
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: ASSIGNED
Severity: unspecified
Priority: unspecified
Component: maven
AssignedTo: sochotni(a)redhat.com
ReportedBy: sochotni(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, sochotni(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: ---
Description of problem:
mvn-rpmbuild has problems with some dependencies when returning "latest" as
available versions. "LATEST" works though.
See if this change makes sense in the code and make a fix
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 3 months
[Bug 870395] New: maven: fails to resolve versioned artifacts
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=870395
Bug ID: 870395
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: rawhide
Priority: unspecified
CC: akurtako(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, sochotni(a)redhat.com
Assignee: sochotni(a)redhat.com
Summary: maven: fails to resolve versioned artifacts
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: mizdebsk(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: ASSIGNED
Component: maven
Product: Fedora
Description of problem:
maven fails to resolve versioned artifacts if dependency version doesn't match
exactly version specified in JPP depmap, even if the artifact file suffix
matches version of the dependency.
Version-Release number of selected component (if applicable):
maven-3.0.4-14.fc19.noarch
How reproducible:
Pseudo-randomly (depends on depmap order)
Steps to Reproduce:
mvn-rpmbuild example:example:1.0:foo
pom.xml contains:
> <dependency>
> <groupId>example</groupId>
> <artifactId>example</artifactId>
> <version>1.0</version>
> </dependency>
depmap.xml contains:
> <dependency>
> <maven>
> <groupId>example</groupId>
> <artifactId>example</artifactId>
> <version>1.0-Final</version>
> </maven>
> <jpp>
> <groupId>JPP/example1</groupId>
> <artifactId>example</artifactId>
> <version>1.0-Final</version>
> </jpp>
> </dependency>
> <dependency>
> <maven>
> <groupId>example</groupId>
> <artifactId>example</artifactId>
> <version>2.0-Final</version>
> </maven>
> <jpp>
> <groupId>JPP/example</groupId>
> <artifactId>example</artifactId>
> <version>2.0-Final</version>
> </jpp>
> </dependency>
File system contains:
> /usr/share/java/example1/example-1.0.jar
> /usr/share/java/example/example.jar
Actual results:
maven resolves either of 2 jars (depeding on semi-random factors).
In the above case /usr/share/java/example/example.jar is resolved.
Expected results:
maven resolves /usr/share/java/example1/example-1.0.jar
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 3 months