Re: [JPP-Devel] OJ EXE

2017-12-04 Thread Arun Bharathi
Hi, I am getting following error [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.4:create (generate-buildnumber) on project OpenJUMP: Cannot get the revision information from the scm repository : [ERROR] Exception while executing SCM command. svn: E155007: 'G:\JUMP\1.11

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread edgar . soldin
Jukka, that depends on what he wants. the wiki page says correctly " release builds of core and plus targeted for release, which can be named via -D version.number=X.X.X -D version.release=release they mainly differ from snapshots because they - do not contain source code

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread Rahkonen Jukka (MML)
Hi, Read this rather new thread about building OJ snapshot with maven https://www.mail-archive.com/jump-pilot-devel@lists.sourceforge.net/msg18320.html I did not try with "release", I am remembering that I had some problems with that earlier. -Jukka Rahkonen- -Alkuperäinen viesti- Läh

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread edgar . soldin
then please "re"read the wikipage again http://ojwiki.soldin.de/index.php?title=Creating_an_OJ_release_version it clearly states that you need to give profiles mvn package -P ,,... and later on it states the actually used cmd line for releases usesd by us mvn package -P release[,portable[,i

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread Arun Bharathi
Hi ede, I have used command line "clean package -P release -D version.number=1.11" Thanks and Regards. P.Arun Bharathi On Mon, Dec 4, 2017 at 8:22 PM, wrote: > wrt. 2. > > what is the _full_ command line you used for that output.txt? > > ..ede > > On 04.12.2017 15:35, Arun Bharathi wrote: > >

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread edgar . soldin
wrt. 2. what is the _full_ command line you used for that output.txt? ..ede On 04.12.2017 15:35, Arun Bharathi wrote: > Hi ede, > > I have ran this command in maven "clean package -P release -D > version.number=1.11". > > /*1. can you list the folders/files it resulted in?*/ > > G:\JUMP\SVN\

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread edgar . soldin
Arun, 1. can you list the folders/files it resulted in? 2. list the steps you do to run OJ currently that result in the windows without plugins? begin with the moment you have started your computer and you have logged in and see your desktop. ..ede On 04.12.2017 15:08, Arun Bharathi wrote: >

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread Arun Bharathi
Hi ede, Yes. I have read and also implement the commands used in that. Thanks and Regards. P.Arun Bharathi On Mon, Dec 4, 2017 at 7:37 PM, wrote: > Arun, > > did your read the wiki article and run the commands mentioned there?` > > ..ede > > On 04.12.2017 15:03, Arun Bharathi wrote: > > Hi, >

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread edgar . soldin
Arun, did your read the wiki article and run the commands mentioned there?` ..ede On 04.12.2017 15:03, Arun Bharathi wrote: > Hi, > Thank you for your reply. > My problem I was facing, while I am trying to create OJ package (source: > svn://svn.code.sf.net/p/jump-pilot/code/core/tags/1.11 >

Re: [JPP-Devel] OJ EXE

2017-12-04 Thread Arun Bharathi
Hi, Thank you for your reply. My problem I was facing, while I am trying to create OJ package (source: svn://svn.code.sf.net/p/jump-pilot/code/core/tags/1.11) using maven, I am getting the output as in attachment 1 (No menus are displaying). I have not made any changes in pom.xml file. Although I a

Re: [JPP-Devel] SVN: [5608] core/trunk

2017-12-04 Thread edgar . soldin
Mike, On 04.12.2017 09:06, Michaël Michaud wrote: > Ede, > > Not so fine as jar files were probably intentionally sealed by G. Roy, but as > far as I understand sealed, the files did not follow the requirements. well, it's a precaution to not accidentally have a second class definition in the

Re: [JPP-Devel] SVN: [5608] core/trunk

2017-12-04 Thread Michaël Michaud
Ede, Not so fine as jar files were probably intentionally sealed by G. Roy, but as far as I understand sealed, the files did not follow the requirements. I removed sealed instruction directly from jar file, but we must find a more permanent solution either with Geoffrey Roy, the original aut