[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-devel] Problems with the quickstart
|
Iñigo Telleria Elola wrote:
So if my goal is develop new plugins, it's better I use the SDK
version. I know that no SDK version involves a SVN checkout, but which
are the reasons to use SDK version?
The SDK version that is uploaded right now has a problem (see the email
I sent to Jesse yesterday) and we can both wait for a re release.
The reasons to use this the SDK release?
You don't have to compile uDig all the time, only the one or two plugins
you are working againt (so development is much faster). The source code
is still all available to you, works out quite well. Oh and it takes
about half the time to set up (there are no annoying cycles of compiling
and running PDE > create classpath).
The real question is why wouldn't you use the SDK release:
- if you are hacking on something broken in uDig
- and the current download did not show the extention point information
correctly
Cheers,
Jody
*********************************************************************
Iñigo Telleria Elola wrote:
After reading the quickstart, I have followed all the steps
to get a build. But I have had some problems when I import the source
code to Eclipse. The uDig's fles have the names of the incorrect
packages. For example:
CGDICatalog.java is located in this package: package
net.refractions.udig.catalog.cgdi;
But in the "Package Explorer" I can see its package is
src.net.refractions.udig.catalog.cgdi.
I don't know why they have different names. I think that I have
followed the steps of quickstart correctly.
It looks like you are following the "Quickstart" that involves an SVN
checkout? There is also an "SDK Quickstart" if you are just interested
in developing plug-ins to extend uDig (it is a bit faster to set up
and a lot less trouble).
But lets work on your problem :-)
There is a page here that explains how to fix a broken build:
-<http://udig.refractions.net/confluence/display/UDIG/How+to+fix+a+broken+build>
From the sounds of it you need to udpate the classpath .... right
click on
the plug-in and select PDE > update classpath, you may as well update
the classpath for all plugins.
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
