Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335913 - "Element not initialised" error in AutotoolsConfigurePropertyPage
Summary: "Element not initialised" error in AutotoolsConfigurePropertyPage
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Autotools (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 0.8.0   Edit
Assignee: Jeff Johnston CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-31 17:26 EST by Mat Booth CLA
Modified: 2011-06-02 18:34 EDT (History)
0 users

See Also:

Attachments
Screenshot is (140.37 KB, image/png)
2011-01-31 17:27 EST, Mat Booth CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mat Booth CLA 2011-01-31 17:26:03 EST 
Build Identifier: 

For some reason the Autotools plug-in adds a AutotoolsConfigurePropertyPage to SVN repository resources in the Subclipse "SVN Repositories" view. When you view the properties of a repository, there is a "Configure Settings" page that probably shouldn't be there...

Reproducible: Always

Steps to Reproduce:
1. Install Subclipse + Autotools plug-ins
2. Open the "SVN Repositories" view (or SVN Browsing perspective)
3. Right-click a repo and show properties and try and look at the "Configure Settings" property page.

See attached screenshot for an illustration.
Comment 1 Mat Booth CLA 2011-01-31 17:27:04 EST 
Created attachment 188013 [details]
Screenshot is
Comment 2 Jeff Johnston CLA 2011-02-01 17:12:03 EST 
(In reply to comment #1)
> Created attachment 188013 [details]
> Screenshot is

A fix was already made to the repository, but post 0.6.1 release.  The problem was that the Property pages did not have proper enabledWhen and filter attributes to prevent them from being shown in various views.

The next Helios and Indigo updates will have the fix.  You should be able to get a fix for Helios if you use our Helios nightly update site:

http://download.eclipse.org/technology/linuxtools/updates-helios-nightly