RVM

Building classpath 0.96.1 or below with --disable-gconf-peer does not choose a different peer

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Won't Fix
  • Affects Version/s: 2.9.0, 2.9.0.1, 2.9.1, 2.9.2
  • Fix Version/s: None
  • Component/s: Infrastructure: Build
  • Labels:
    None
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

There's a bug in Classpath (fixed in CVS) which means that if it is configured with --disable-gconf-peer, the gconf peer is still the default preferences peer.
As a result, it fails if code tries to initialise the preferences factory as it is unable to find libgconfpeer.

public class TestGConf
{
public static void main(String[] args)

{ System.out.println(java.util.prefs.Preferences.userRoot()); }

}

The solution is to also add the --enable-default-preferences-peer=file into build.xml until a more recent Classpath is available and in use.
Additionally, disabling gconf should be an option not a static part of the build.

  1. Java Source File
    TestGConf.java
    21/Jan/08 10:12 AM
    0.1 kB
    Andrew John Hughes

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew John Hughes added a comment -

Testcase

Show
Andrew John Hughes added a comment - Testcase
Hide
Permalink
Andrew John Hughes added a comment -

This is irrelevant now we are using 0.97.

Show
Andrew John Hughes added a comment - This is irrelevant now we are using 0.97.
Hide
Permalink
Andrew John Hughes added a comment -

It is of course still relevant to versions that ship with 0.96. If there are any, maybe they could be patched?

Show
Andrew John Hughes added a comment - It is of course still relevant to versions that ship with 0.96. If there are any, maybe they could be patched?

People

  • Assignee:
    Andrew John Hughes
    Reporter:
    Andrew John Hughes
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: