Re: [udig-dev] Development environment

[Ivan Lucena <lucena_ivan@xxxxxxxxxxx>]

Jody,

I already posted my mvn error messages. Thanks.

I have followed the steps again with the tips from Frank and Jody and my project seems to be correct now. But I am gstill having the same error when trying to launch the application, in both Win64 and osx32 (I might try linux64 too). So I am switching to Eclipse Indigo to see how it goes. Currently I am "Loading Target Platform" on Eclipse Indigo on Win64, JRE 1.7.

Regards,

Ivan

________________________________
> Date: Tue, 28 Jan 2014 10:38:14 +1100 
> Subject: Re: [udig-dev] Development environment 
> From: jody.garnett@xxxxxxxxx 
> To: lucena_ivan@xxxxxxxxxxx 
> CC: udig-dev@xxxxxxxxxxxxxxxx 
>  
> 2. Download stuff 
>  
> mvn clean install -f pom-libs.xml 
>  
> After getting an error, I end up downloading a jar file "by hand"  
> copying the file path to a browser and then, saving it to the path  
> specified by the script. I ran the same mvn command again and at the  
> end it was all "success". 
>  
> What was the error you received? 
>  
> Option - Eclipse Build 
>  
> The instructions doesn't really sat what version of Eclipse or JRE to  
> use. Does it matter? I am trying in a Windows 7 64Bit and a OSX 10.6  
> 32Bit, Eclipse Kepler release 1, JRE 7 and 6 respectively. 
>  
> Previously we used Eclipse 3.7.2 - but my understanding is that the  
> "target platform" approach now allows us to use a newer Eclipse. 
>  
> 1. Import the targets/indigo project into workspace. 
>  
> Forgive my ignorance, but it seems like I cannot just import that thing  
> without creating a project first. Right? What kind of project that  
> would be? I tried several different options but let's say it is suppose  
> to be a regular empty Java project. 
>  
> That is what I did. I created a regular Java project and I imported  
> then I found and imported the file /udig/extras/targets/indigo" to that  
> new project. Is it the right thing to do? 
>  
> There is a wizard to import existing projects. The checkout includes  
> the .project and .classpath files needed to define a rather long list  
> of projects (one for each plugin making up the application). 
>  
> It was my intention that you only import this one project (that  
> contains the project file). 
> Should probably stop here (or backtrack) until you can sort out this step... 
>  
> 2. Open up udig-indigo-target.target and click on Set as Target Platform 
>  
> That takes forever but It concluded successful on both system, after  
> stop and continuing it a couple of times by closing Eclipse. The only  
> difference is that I only have 2296 plug-ins available on the first  
> line instead of 2306. Is that a problem? 
>  
> I am not sure will have to check, we have been working to make more use  
> of the target platform (and less use of downloading jars). 
>  
> 3. Save a copy of the target-platform locally 
>  
> I don't understand what it is, but I did it anyway.  Does it means that  
> I can close my current project where I have imported all that stuff and  
> go and open the local copy and follow the rest of instructions from  
> there? Or is ti only a place to download the external jars? 
>  
> I am not sure either, sounds like I have to try out the instructions  
> again myself. 
>  
>  
> 4. Once the target platform is finished you can import the remaining  
> uDig projects. 
>  
> A little bit of detailing here would be nice. I don't know how to  
> switch to the local project (if here is one) so I just select the  
> Import> Existing Projects into Workspace on the same project that I  
> started earlier. 
>  
> Should I check the box that says Copy projects into workspace? 
>  
> No, we are trying to leave the projects in your checkout location (so  
> any changes you made will be seen by git). 
>  
> Ivan I will be available on IRC (or Skype) if you need help getting set up.