On 05.04.2013 10:34, Uwe Dalluege wrote:
> Hi,
> 
> the big advantage of OJ is that it is written in Java.
> Java should be platform-independent.
> But if we (the developer of OJ) write code
> that is not pure Java and contains tricky code
> for svn, maven and so on...
> we make life hard for new developers!

old dogs have to learn new tricks sometimes, sorry 'bout that. it's a small 
sacrifice for the sake of automation.

> As I suggested some mails before
> please write your code IDE-independent
> so every developer who likes to develop
> OJ can use its own IDE.

i am sure there is a plugin for your ide to have the vars automatically filled 
if it  is so important for you. alternatively pretty much all java ide's 
support maven nowadays.

> The ideal case would be
> only download the sourcecode and the libs
> to build a runable OpenJUMP.
> But I think, this is a pipe-dream.

well, your approach of downloading svn archives seems to work. doesn't it now? 
..ede 

..ede

> Regards
> 
> Uwe
> 
> 
> Am 05.04.2013 09:22, schrieb edgar.sol...@web.de:
>> On 05.04.2013 09:08, Michaël Michaud wrote:
>>> Hi,
>>>>> after compiling and run OJ in eclipse from
>>>>> http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/
>>>>> the splash-window shows
>>>>> Version ${version.number} ${version.release} rev.${version.revision}
>>>>> and the readme.txt file also.
>>>>>
>>>>> What is the secret to get the right version numbers to the variables?
>>>>> What have I do, to configure eclipse, that the version-variables get the
>>>>> right values?
>>> As a side note, these variables and some others (useJvmChmod,
>>> recompress.folder...)
>>> are viewed as errors in the IntelliJ IDEA interface ("cannot resolve
>>> symbol").
>>> Not a big problem, but I don't know if there is a way to make it
>>> understand everything
>>> is fine. Are these parameters only defined on the command line ? Would
>>> it be better
>>> to have them declared/defined at one place ?
>>>
>>
>> well, you cannot define them. svn revision e.g. is only known during compile 
>> time.
>>
>> having placeholders like such is pretty common. i have another project that 
>> also sports these until you properly package it (actually a python app).
>>
>> the only way to "get rid" of them is to implement their replacement in the 
>> build process. still, however it looks under the hood. it makes it pretty 
>> easy to fill in version values in several places and i see no alternative 
>> currently.
>>
>> ..ede
>>
>>
>> ------------------------------------------------------------------------------
>> Minimize network downtime and maximize team effectiveness.
>> Reduce network management and security costs.Learn how to hire
>> the most talented Cisco Certified professionals. Visit the
>> Employer Resources Portal
>> http://www.cisco.com/web/learning/employer_resources/index.html
>> _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to