[kepler-dev] Build Problems

[Dan Higgins]

Just to confuse things more:  ;-)

I moved my Kepler and PTII directories to a location under a directory 
containing a space in the name ("Program Files"), changed my environment 
variables to point to this new location, and then used ant to rebuild 
Kepler. No problems - the build worked with no errors. So apparently the 
'space' in path problem does not occur in all cases !?

Dan

-----

Kenneth Evans wrote:
> Ilkay,
>
>   
>>> Try changing the direction of the slashes to back slash in your KEPLER
>>>       
> and PTII env var path.
>
> It's already that way.  The problem is probably spaces in the path names.
>
>   
>>> I also suggest carrying this discussion to Kepler irc channel. (Info  
>>>       
> at: http://kepler-project.org/Wiki.jsp?page=GettingInvolved) It would  
> be more effective.
>
> It is my understanding our IT would have to open ports to do that.  They
> don't like that.  Tell me if I'm wrong.  If so, what do you recommend for a
> Windows client?
>
> Thanks,
>
>         -Ken
>
> -----Original Message-----
> From: Ilkay Altintas [mailto:altintas at sdsc.edu] 
> Sent: Tuesday, October 30, 2007 2:23 PM
> To: Kenneth Evans
> Cc: 'Kepler Developers'
> Subject: Re: [kepler-dev] Build Problems
>
> Try changing the direction of the slashes to back slash in your  
> KEPLER and PTII env var path.
>
> I also suggest carrying this discussion to Kepler irc channel. (Info  
> at: http://kepler-project.org/Wiki.jsp?page=GettingInvolved) It would  
> be more effective.
>
> Cheers,
> -ilkay
>
> On Oct 30, 2007, at 12:03 PM, Kenneth Evans wrote:
>
>   
>> Hi,
>>
>>     
>>>> I've not tried building Kepler with a space in the path.
>>>>         
>> Oh.  Ok, I tried the whole thing another way.  I checked out using:
>>
>> Select "Check out as a project in the workspace" (Don't use the  
>> wizard)
>> Uncheck "Use default workspace location"
>> Browse to somewhere that doesn't have spaces in the name.
>>
>> The result of this is two projects:
>>   C:\Somewhere\kepler
>>   C:\Somewhere\ptII
>>
>> These projects appear in my Eclipse workspace which is in "My  
>> Documents"
>> (where it has been happy for several years. ;-)  Neither has  
>> a .classpath,
>> Builders, or Java Build Path.  Perhaps this can be fixed later.   
>> They should
>> be as would be checked out without using Eclipse.
>>
>> I tried the ant build with the 4 targets, extra memory, KEPLER and  
>> PTII
>> defined, etc.  It got much further and actually started Kepler.  It  
>> then got
>> an exception.  The output is attached.  This is likely a problem you
>> probably know how to fix, so I'll send this now before hacking on  
>> it myself.
>>
>> I can't make a launcher in Eclipse as these projects do not appear as
>> options for "Location:".  I could make an external launcher, but I  
>> would
>> rather see if we can get this scenario fixed up.  I can also use  
>> the target
>> run-dev, which is the part that failed.  Perhaps you can give me some
>> guidance.
>>
>> Thanks,
>>
>>         -Ken
>>
>> <kepler.build.2.output>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at ecoinformatics.org
>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/ 
>> kepler-dev
>>     
>
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>   


-- 
*******************************************************************
Dan Higgins                                  higgins at nceas.ucsb.edu
http://www.nceas.ucsb.edu/    Ph: 805-893-5127
National Center for Ecological Analysis and Synthesis (NCEAS) Marine Science Building - Room 3405
Santa Barbara, CA 93195
*******************************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20071030/7fe77ca8/attachment.html>