-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Low
-
None
-
Affects Version/s: 3.4.2
-
Component/s: None
-
Environment:
Java Version 1.4.2_03
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.4.2_03-b02
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Server VM
User Timezone MET
User Locale English
System Encoding ISO646-US
Operating System SunOS 5.8
OS Architecture sparc
Application Server Container Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)
Database type oracle10gJava Version 1.4.2_03 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.4.2_03-b02 Java Runtime Java(TM) 2 Runtime Environment, Standard Edition Java VM Java HotSpot(TM) Server VM User Timezone MET User Locale English System Encoding ISO646-US Operating System SunOS 5.8 OS Architecture sparc Application Server Container Oracle Application Server Containers for J2EE 10g (9.0.4.0.0) Database type oracle10g
-
3.04
When using the URI link below and RFC-630 being an existing issue-number, the link does not work. Only the issue-number part of the URI (RFC-630)is a link (to the isue concerned).
file://Athens/Release%20Management/RFC-630%20CC0232024%20%20ipb-spaties.doc
This problem occurs since the latest versionupdate we had recently. In our previous version: professional 3.2.2, this problem did not occur.
This problem causes a lot of discomfort and indignation because we are using a lot of URI-Links while the linked documents are being changed very frequently.
- is related to
-
JRASERVER-9758 Allow generalized URI in link
- Closed
