[Bug 1091711] New: sbt does not work if I go into the console
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1091711
Bug ID: 1091711
Summary: sbt does not work if I go into the console
Product: Fedora
Version: 20
Component: sbt
Severity: urgent
Assignee: willb(a)redhat.com
Reporter: rwobben(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org, s(a)shk.io,
willb(a)redhat.com
Description of problem:
When I start sbt and do the command console. The console starts up and I see
the scala prompt. And then the terminal does not respond anymore to the
keyboard.
See ths output:
[info] Starting scala interpreter...
[info]
Welcome to Scala version
2.10.3-20130923-e2fec6b28dfd73482945ffab85d9b582d0cb9f17 (OpenJDK 64-Bit Server
VM, Java 1.7.0_55).
Type in expressions to have them evaluated.
Type :help for more information.
scala>
Version-Release number of selected component (if applicable):
sbt launcher version 0.13.1
How reproducible: every time
Steps to Reproduce:
1. start sbt
2. enter console
3.
Actual results:
Prompt does not respond to anything
Expected results:
Prompt responds and I can test some things.
Additional info:
--
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=zybqdVFyQJ&a=cc_unsubscribe
8 years, 6 months
[Bug 1043158] New: zookeeper-server service silently fails while starting on FC20
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1043158
Bug ID: 1043158
Summary: zookeeper-server service silently fails while starting
on FC20
Product: Fedora
Version: 20
Component: zookeeper
Assignee: tstclair(a)redhat.com
Reporter: rudcy(a)broadbandninja.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jeff(a)ocjtech.us, skottler(a)redhat.com,
tstclair(a)redhat.com
Description of problem:
zookeeper-server on fc20 silently fails to start after a fresh install
due to unit file precondition on missing file .
Version-Release number of selected component (if applicable):
zookeeper-server-3.4.5-12.fc20.noarch
Steps to Reproduce:
1. Fresh install of fc20
2. install zookeeper-server (and zookeeper?)
3. sudo cp /etc/zoo-sample.cfg /etc/zoo.cfg
4. sudo systemctl start zookeeper
5. journalctl -f shows:
```
Dec 14 14:18:32 localhost.localdomain systemd[1]: Started Apache ZooKeeper.
```
Actual results:
The service has aborted when trying to start, the errors it
reported are not logged to the journal nor /var/log/zookeeper/*
Expected results:
the service should be running, or log an error to the journal.
Additional info:
```
% cat /usr/lib/systemd/system/zookeeper.service
...
ConditionPathExists=/var/lib/zookeeper/data/myid
```
Creating /var/lib/zookeeper/data/myid and chowning it over to zookeeper makes
the next restart "stick" and zookeeper then logs to the journal (too verbosely,
btw).
I've found nothing on setting up zookeeper-server on fedora on google,
but I'm new here, I may have missed it.
So no docs on what is myid or what's it for, zookeeper runs fine without
it if it's launched manually.
--
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=ItjXVYdpch&a=cc_unsubscribe
8 years, 6 months
[Bug 1076927] New: Solr - Hadoop missing support for ARM arch
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1076927
Bug ID: 1076927
Summary: Solr - Hadoop missing support for ARM arch
Product: Fedora
Version: rawhide
Component: solr
Assignee: puntogil(a)libero.it
Reporter: puntogil(a)libero.it
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
puntogil(a)libero.it
solr has broken dependencies in the rawhide tree:
On armhfp:
solr-4.7.0-1.fc21.noarch requires mvn(org.apache.hadoop:hadoop-hdfs)
solr-4.7.0-1.fc21.noarch requires mvn(org.apache.hadoop:hadoop-common)
solr-4.7.0-1.fc21.noarch requires mvn(org.apache.hadoop:hadoop-auth)
solr-4.7.0-1.fc21.noarch requires mvn(org.apache.hadoop:hadoop-annotations)
--
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=snDZpFQcdi&a=cc_unsubscribe
8 years, 7 months
[Bug 753201] New: when javac is java-1.5.0-gcj ant seems to not be able to access environmental variables
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: when javac is java-1.5.0-gcj ant seems to not be able to access environmental variables
https://bugzilla.redhat.com/show_bug.cgi?id=753201
Summary: when javac is java-1.5.0-gcj ant seems to not be able
to access environmental variables
Product: Fedora
Version: 15
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: ant
AssignedTo: pcheung(a)redhat.com
ReportedBy: caolanm(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: pcheung(a)redhat.com, akurtako(a)redhat.com,
mmatejov(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: ---
Created attachment 533096
--> https://bugzilla.redhat.com/attachment.cgi?id=533096
sample build.xml
Description of problem:
ant doesn't seem to be able to resolve environment variables (or something
clears the env) if the java in use is gcj rather than openjdk
Version-Release number of selected component (if applicable):
ant-1.8.2-3.fc15
How reproducible:
100%
Steps to Reproduce:
1. alternatives --set javac /usr/lib/jvm/java-1.6.0-openjdk.x86_64/bin/javac
2. ant -f build.xml gives the contents of $USERNAME as expected
3. alternatives --set javac /usr/lib/jvm/java-1.5.0-gcj/bin/javac
4. ant -f build.xml gives "${env.USERNAME}"
Actual results:
username
Expected results:
${env.USERNAME} string
Additional info:
--
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.
8 years, 8 months
[Bug 1098509] New: all jpackage following lunchers are using by defalt JDK instead of JRE
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1098509
Bug ID: 1098509
Summary: all jpackage following lunchers are using by defalt
JDK instead of JRE
Product: Red Hat Enterprise Linux 7
Version: 7.1
Component: jpackage-utils
Severity: high
Assignee: java-maint(a)redhat.com
Reporter: jvanek(a)redhat.com
QA Contact: qe-baseos-apps(a)redhat.com
CC: akurtako(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, mizdebsk(a)redhat.com,
msrb(a)redhat.com, sochotni(a)redhat.com
Depends On: 1098508
+++ This bug was initially created as a clone of Bug #1098508 +++
Description of problem:
When alternatives are used to change jre (alternatives --config java) the all
jpackage compatible java apps, are still using the java specified by JDK
(alternatives --config javac)
This is wrong. Especially for case when I have one JDK and one JRE. Then I can
use alternatives as , and still only JDK will
be selected.
Version-Release number of selected component (if applicable):
All fedoras and rhels till now
How reproducible:
Steps to Reproduce on f20:
1. $ install java-1.7.0-openjdk-devel, and java-1.8.0-oepnjdk
2. $ alternatives --configure java
3. select java 8
4. # run some packed java app
Expected results:
java8 will be used
Actual results:
java 7 is still used
To use java 8 you ust install java-1.8.0-openjdk-devel
and select java 8 via $alternatives --config javac
Additional info:
Currently jpackage-utils are using JDK by default. Any app which wonts to use
only JRE must specifi _prefer_jre=true to luncher.
Well this is wrong in design. All apps should use JRE by default, and only few
(10?) apps using whole JDK should specifi _prefer_jre=false.
Another workarouds ae set JAVA_HOME or edit /etc/java/java.conf But htose are
far away from compfortable alternatives solution.
As reason not to do the change was introduced ant - that it needs whole JDK to
run. IMHO it is one of the few apps which should specifu _prefer_jre=false...
Fix is quite simple
Change /usr/share/java-utils/java-functions to use /usr/lib/jvm/jre instead of
/usr/lib/java
However, the consequences may be really huge.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1098508
[Bug 1098508] all jpackage following lunchers are using by defalt JDK
instead of JRE
--
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=2mmm5RWXNA&a=cc_unsubscribe
8 years, 8 months
[Bug 1098508] New: all jpackage following lunchers are using by defalt JDK instead of JRE
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1098508
Bug ID: 1098508
Summary: all jpackage following lunchers are using by defalt
JDK instead of JRE
Product: Fedora
Version: rawhide
Component: jpackage-utils
Severity: high
Assignee: mizdebsk(a)redhat.com
Reporter: jvanek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, mizdebsk(a)redhat.com,
msrb(a)redhat.com, sochotni(a)redhat.com
Description of problem:
When alternatives are used to change jre (alternatives --config java) the all
jpackage compatible java apps, are still using the java specified by JDK
(alternatives --config javac)
This is wrong. Especially for case when I have one JDK and one JRE. Then I can
use alternatives as , and still only JDK will
be selected.
Version-Release number of selected component (if applicable):
All fedoras and rhels till now
How reproducible:
Steps to Reproduce on f20:
1. $ install java-1.7.0-openjdk-devel, and java-1.8.0-oepnjdk
2. $ alternatives --configure java
3. select java 8
4. # run some packed java app
Expected results:
java8 will be used
Actual results:
java 7 is still used
To use java 8 you ust install java-1.8.0-openjdk-devel
and select java 8 via $alternatives --config javac
Additional info:
Currently jpackage-utils are using JDK by default. Any app which wonts to use
only JRE must specifi _prefer_jre=true to luncher.
Well this is wrong in design. All apps should use JRE by default, and only few
(10?) apps using whole JDK should specifi _prefer_jre=false.
Another workarouds ae set JAVA_HOME or edit /etc/java/java.conf But htose are
far away from compfortable alternatives solution.
As reason not to do the change was introduced ant - that it needs whole JDK to
run. IMHO it is one of the few apps which should specifu _prefer_jre=false...
Fix is quite simple
Change /usr/share/java-utils/java-functions to use /usr/lib/jvm/jre instead of
/usr/lib/java
However, the consequences may be really huge.
--
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=g42lptd4V6&a=cc_unsubscribe
8 years, 8 months
[Bug 1076949] New: tomcat: don't provide javax.jsp-api and javax.servlet.jsp-api
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1076949
Bug ID: 1076949
Summary: tomcat: don't provide javax.jsp-api and
javax.servlet.jsp-api
Product: Fedora
Version: rawhide
Component: tomcat
Assignee: ivan.afonichev(a)gmail.com
Reporter: msimacek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com
Description of problem:
javax.jsp:jsp-api and javax.servlet.jsp:javax.servlet.jsp-api artifacts are
provided by both tomcat-jsp-2.2-api and glassfish-jsp[-api]. Because requires
generator doesn't specify versions, there should be only one provide of given
artifact. If the artifact is provided by multiple packages, it can lead to
breakage of packages that depend on different version of the artifact than the
version pulled in by yum (which is not predictable). Glassfish is the preferred
implementation according to Java Packaging Guidelines [1].Please drop the
aliases.
[1] http://fedoraproject.org/wiki/Packaging:Java#EE_API_List
--
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=xRWmTHaZWE&a=cc_unsubscribe
8 years, 9 months