Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[udig-devel] Problem compiling udig for the first time
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!

  1. Open the MANIFEST.MF runtime tab
  2. Find the list of runtime jars - all except the first library.jar and delete them all
  3. Use the Add button; navigate to the lib folder; and select all the jars the refresh.xml script downloaded
  4. 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.

  1. 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).
  2. 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)

  1. 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:

--------------------------------------

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

Back to the top