wow - okay I was working with a developer using Eclipse 3.7.1 today - and he also had all kinds of Java problems out of the box (like it was trying to use Java 1.4 settings or some other crazy ...).
Please check what version of eclipse you are using; we use 3.7.0 until we go through the QA process of upgrading. Link to 3.7.0: - http://www.eclipse.org/downloads/packages/release/indigo/r With the modelling stuff being here: - http://www.eclipse.org/downloads/packages/eclipse-modeling-tools/indigor -- Jody Garnett On Friday, 16 December 2011 at 7:22 AM, Jody Garnett wrote: > Morning Can: > > I was working on those instructions yesterday due to some questions. However > it is looking like it is tripping up over perhaps a difference in version of > Java? > > Things to look for: > - Can I ask you what version of Java you are using; sometimes it shows up as > "JRE System Library [...]" in the Package Explorer? > - Go over the compiler settings? Is it set for Java 6? We used to ask people > explicitly set this; but since people use Java 6 now it shows up as the > default? > - What version of Eclipse? I have some reports on the GeoTools project of > people getting new creative compile errors around generics (i.e. exactly your > problem) using the latest Eclipse 3.7.1 ? > > As an example the NavigationPreferenceInitializer is very short and compiles > with out error for me: > > public class NavigationPreferenceInitializer extends > AbstractPreferenceInitializer { > @Override > public void initializeDefaultPreferences() { > Preferences node = DefaultScope.INSTANCE.getNode(ToolsPlugin.ID); > <--- LINE 17 > node.putBoolean(NavigationToolPreferencePage.SCALE,false); > node.putBoolean(NavigationToolPreferencePage.TILED,false); > } > } > > That code is very simple so I am hard pressed to see where the problem is? > But I suppose that will make it easier to fix ... > Could you check DefaultScope.INSTANCE - is that showing up for you? > Could you check ToolsPlugin.ID and check that it exists? > > Other than that drop by on IRC and we can try and help? > -- > Jody Garnett > > > On Friday, 16 December 2011 at 12:12 AM, Can Baldan wrote: > > > Hello everybody, > > > > Sorry I am a newbie in the udig developer world. I have completed all the > > steps except "running the main application" at > > http://udig.refractions.net/confluence/display/ADMIN/02+Development+Environment > > > > > > I have been getting compile errors > > > > ---------------------------- > > > > INSTANCE cannot be resolved or is not a field > > NavigationPreferenceInitializer.java > > /net.refractions.udig.tool.default/src/net/refractions/udig/tools/internal > > line 17 Java Problem > > > > INSTANCE cannot be resolved or is not a field > > SelectionToolPreferenceInitializer.java > > /net.refractions.udig.tool.select/src/net/refractions/udig/tool/select line > > 16 Java Problem > > > > The method getServiceReference(String) in the type BundleContext is not > > applicable for the arguments (Class<PreferencesService>) > > LoadSearchCatalogs.java /eu.udig.catalog.csw/src/eu/udig/catalog/csw line > > 18 Java Problem > > > > The type ServiceReference is not generic; it cannot be parameterized with > > arguments <PreferencesService> LoadSearchCatalogs.java > > /eu.udig.catalog.csw/src/eu/udig/catalog/csw line 18 Java Problem > > > > ---------------------------- > > > > At http://udig.refractions.net/confluence/display/ADMIN/08+Libs+Refresh > > > > The probable reasons for build errors are listed as > > > > > > -------------------------------------- > > > > Manifest.MF > > > > Occasionally (after downloading the jars) the MANIFEST.MF file will still > > list errors. There are three main categories of errors. > > > > New Jars > > > > The maven repository has newer jars then the ones listed in the MANIFEST.MF > > - normally a uDig developer will update the list of jars on the runtime tab > > and commit the result - but you may be the first developer to notice! > > > > Open the MANIFEST.MF runtime tab > > Find the list of runtime jars - all except the first library.jar and delete > > them all > > Use the Add button; navigate to the lib folder; and select all the jars the > > refresh.xml script downloaded > > When you Save the MANIFEST.MF file; the java ".classpath" file will be > > recreated and all these new jars you identified will be placed on the > > CLASSPATH when compiling or running > > > > Stale Packages > > > > Specific Packages are no longer available and show up as errors. > > > > This occurs (after the ".classpath" is updated and we have clue about what > > is in the jars) when a jar from the internet has removed or renamed a > > package; or when a jar is no longer in used (and thus the packages it > > supplied are no longer available to be published). > > You can go through the MANIFEST.MF and remove each problem package; or you > > can right click on the the plugin and choose *PDE Tools > Organized > > Manifest". This will attempt to publish all the packages that are found on > > the .classpath > > > > Duplicate Jars > > > > Duplicate jars show up (usually after you have run refresh.xml more then > > once) > > > > This occurs when jars from the internet are updated with a newer version; > > you can either delete the older version; or run the refresh.xml "full > > build" target which removes the lib folder and downloads everything from > > scratch > > > > > > ---------------------------------------- > > > > And at > > http://udig.refractions.net/confluence/display/ADMIN/01+How+to+fix+a+broken+build#01Howtofixabrokenbuild-net.refractions.udig.core > > > > > > Further potential problems are listed: > > > > subversion update > > (http://www.refractions.net:8080/confluence/display/ADMIN/01+How+to+fix+a+broken+build#01Howtofixabrokenbuild-subversionupdate) > > - is everything up to date? > > net.refractions.udig.libs > > (http://www.refractions.net:8080/confluence/display/ADMIN/01+How+to+fix+a+broken+build#01Howtofixabrokenbuild-net.refractions.udig.libs) > > - is everything downloaded? > > net.refractions.udig.core > > (http://www.refractions.net:8080/confluence/display/ADMIN/01+How+to+fix+a+broken+build#01Howtofixabrokenbuild-net.refractions.udig.core) > > - is libs exporting everything needed? > > net.refractions.udig.catalog > > (http://www.refractions.net:8080/confluence/display/ADMIN/01+How+to+fix+a+broken+build#01Howtofixabrokenbuild-net.refractions.udig.catalog) > > net.refractions.udig.project > > (http://www.refractions.net:8080/confluence/display/ADMIN/01+How+to+fix+a+broken+build#01Howtofixabrokenbuild-net.refractions.udig.project) > > Build errors indicating that JAI is missing > > (http://www.refractions.net:8080/confluence/display/ADMIN/01+How+to+fix+a+broken+build#01Howtofixabrokenbuild-BuilderrorsindicatingthatJAIismissing) > > - is default compatible JRE with enabled JAI for J2SE-1.5 set? > > > > > > -------------------------------------- > > > > I really need a jumpstart here, I have no clue so far about what exactly > > might the problem(s) might be. Would anybody have suggestions? > > > > Thank you in advance... > > > > Can > > _______________________________________________ > > User-friendly Desktop Internet GIS (uDig) > > http://udig.refractions.net > > http://lists.refractions.net/mailman/listinfo/udig-devel > > > > > > > >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
