Re: [JPP-Devel] next maintenance OJ 2.1.1 release?

[edgar . soldin]

On 27.11.2022 22:14, Michaud Michael wrote:


1. sf.net files readme.txt needs current changes appended manually (just 
updated the ojwiki accordingly)

http://sourceforge.net/projects/jump-pilot/files/OpenJUMP/2.1.1/
compare with
http://sourceforge.net/projects/jump-pilot/files/OpenJUMP/2.1/

2. after upgrading launch4j you will need to git remove/tag 2.1.1 again to 
reflect the state built

If you want to manage it from maven instead of loading launch4j in the project 
it will need another commit/push/tag isn't it ?


yes, will do it next week.



3. wanted to test, but cannot find OJ-2.1.1 release files on
https://sourceforge.net/projects/jump-pilot/files/OpenJUMP2_snapshots/
where did you put em?


I really put them there. I still have the upload window opended with the 
following url :

https://sourceforge.net/projects/jump-pilot/upload/OpenJUMP2_snapshots/ 


Is it possible that files are deleted by the automatic snapshot build process ?


*lol* right, there is a cleanup routine to keep a limited number of files 
online only. everything else get's deleted. just put em up under 
'https://sourceforge.net/projects/jump-pilot/files/OpenJUMP/2.1.1.rc1' they 
will be safe there.

..ede



___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] next maintenance OJ 2.1.1 release?

[Michaud Michael]

1. sf.net files readme.txt needs current changes appended manually (just updated the ojwiki accordingly)http://sourceforge.net/projects/jump-pilot/files/OpenJUMP/2.1.1/compare withhttp://sourceforge.net/projects/jump-pilot/files/OpenJUMP/2.1/2. after upgrading launch4j you will need to git remove/tag 2.1.1 again to reflect the state builtIf you want to manage it from maven instead of loading launch4j in the project it will need another commit/push/tag isn't it ? 3. wanted to test, but cannot find OJ-2.1.1 release files on https://sourceforge.net/projects/jump-pilot/files/OpenJUMP2_snapshots/where did you put em?I really put them there. I still have the upload window opended with the following url :https://sourceforge.net/projects/jump-pilot/upload/OpenJUMP2_snapshots/Is it possible that files are deleted by the automatic snapshot build process ?Michaël ..edeOn 26.11.2022 20:05, Michaud Michael wrote:Thank you, Ede,There is no renaming problem, I did not see the "recompress" repository.I just uploaded the 6 bundles into OpenJUMP 2 snapshot repository on sourceforge.Please have one more test for linux/mac (on linux, I get a problem during my test with the sh file which hadCRLF eof on my box. I could change it but I could not commit the change. I think it is OK on github and thatgit accept different eof between origin and local repository. Just hope that it will not change my local file backto CRLF inadvertentlyMichaël>> envoyé : 26 novembre 2022 à 19:14>> de : edgar.sol...@web.de>> à : OpenJump develop and use >> objet : Re: [JPP-Devel] next maintenance OJ 2.1.1 release?>>>>>> On 26.11.2022 13:54, Michaud Michael wrote:>>>>> Hi Ede,>>>>>> I upgraded the launch4j library because I had problem to define the minimum java version with the older (openjump installer could not recognized my java install).>>>>> good catch. seem to recall that that was the reason i didn't upload executable installers earlier.>>>>> I tested on windows and did a quick try on linux but cannot test on mac.>>>>> will do in a vm and come back.>>>>> Also I noticed that we usually uplaod a OpenJUMP-portable version but none of the version I produce with maven has this name.>>>>> if you package profile *portable* like `mvn package -P release,portable,installer,srczip,javadoc` then the portable distro files should be under `target/recompress/` . it's documented on https://ojwiki.soldin.de/index.php?title=Creating_an_OJ_release_version>>>> main difference is some jar recompression (keep distro small) and permisson fixing for executables. you can have a look in the pom.xml>>>>> Tell me if I missed something about file naming. Files are ready to be uploaded on sourceforge except this naming problem.>>>>> sorry? what naming issue? feel free to upload to sf.net/files in a release candidate folder and i can have a look :) . we can rename it if it's fine or upload again in case something needs to be changed.>>>> regards ..ede>>>>>>>> ___>> Jump-pilot-devel mailing list>> Jump-pilot-devel@lists.sourceforge.net>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel>>___Jump-pilot-devel mailing listJump-pilot-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/jump-pilot-devel___Jump-pilot-devel mailing listJump-pilot-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] next maintenance OJ 2.1.1 release?

[edgar . soldin]

some comments,

1. sf.net files readme.txt needs current changes appended manually (just 
updated the ojwiki accordingly)

http://sourceforge.net/projects/jump-pilot/files/OpenJUMP/2.1.1/
compare with
http://sourceforge.net/projects/jump-pilot/files/OpenJUMP/2.1/

2. after upgrading launch4j you will need to git remove/tag 2.1.1 again to 
reflect the state built

3. wanted to test, but cannot find OJ-2.1.1 release files on
 https://sourceforge.net/projects/jump-pilot/files/OpenJUMP2_snapshots/
where did you put em?

..ede

On 26.11.2022 20:05, Michaud Michael wrote:

Thank you, Ede,

There is no renaming problem, I did not see the "recompress" repository.

I just uploaded the 6 bundles into OpenJUMP 2 snapshot repository on 
sourceforge.

Please have one more test for linux/mac (on linux, I get a problem during my 
test with the sh file which had

CRLF eof on my box. I could change it but I could not commit the change. I 
think it is OK on github and that

git accept different eof between origin and local repository. Just hope that it 
will not change my local file back

to CRLF inadvertently

Michaël


envoyé : 26 novembre 2022 à 19:14
de : edgar.sol...@web.de
à : OpenJump develop and use 
objet : Re: [JPP-Devel] next maintenance OJ 2.1.1 release?


On 26.11.2022 13:54, Michaud Michael wrote:


Hi Ede,

I upgraded the launch4j library because I had problem to define the minimum 
java version with the older (openjump installer could not recognized my java 
install).


good catch. seem to recall that that was the reason i didn't upload executable 
installers earlier.


I tested on windows and did a quick try on linux but cannot test on mac.


will do in a vm and come back.


Also I noticed that we usually uplaod a OpenJUMP-portable version but none of 
the version I produce with maven has this name.


if you package profile *portable* like `mvn package -P 
release,portable,installer,srczip,javadoc` then the portable distro files 
should be under `target/recompress/` . it's documented on 
https://ojwiki.soldin.de/index.php?title=Creating_an_OJ_release_version

main difference is some jar recompression (keep distro small) and permisson 
fixing for executables. you can have a look in the pom.xml


Tell me if I missed something about file naming. Files are ready to be uploaded 
on sourceforge except this naming problem.


sorry? what naming issue? feel free to upload to sf.net/files in a release 
candidate folder and i can have a look :) . we can rename it if it's fine or 
upload again in case something needs to be changed.

regards ..ede



___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel




___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel




___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] next maintenance OJ 2.1.1 release?

[edgar . soldin]

On 26.11.2022 20:05, Michaud Michael wrote:

Thank you, Ede,


np


There is no renaming problem, I did not see the "recompress" repository.

I just uploaded the 6 bundles into OpenJUMP 2 snapshot repository on 
sourceforge.

Please have one more test for linux/mac


will do


(on linux, I get a problem during my test with the sh file which had

CRLF eof on my box. I could change it but I could not commit the change. I 
think it is OK on github and that

git accept different eof between origin and local repository. Just hope that it 
will not change my local file back

to CRLF inadvertently


hmm, i don't see any enforcement git-wise. no properties enforcing any kind of 
ending. also, in my experience, even if dos endings look weird with some 
viewers/editors on linux, shell scripts run fine regardless.

finally. dos2unix says it has unix endings just now

$  dos2unix.exe -ih /cygdrive/e/proj_oj-core_git/scripts/*
 DOSUNIX MAC  BOM   TXTBIN  FILE
  12 279 252  no_bombinary  
/cygdrive/e/proj_oj-core_git/scripts/OpenJUMP.exe
1902   0   0  no_bomtext
/cygdrive/e/proj_oj-core_git/scripts/default-plugins.xml
   0 369   0  no_bomtext
/cygdrive/e/proj_oj-core_git/scripts/oj_linux.sh
   0  30   0  no_bombinary  
/cygdrive/e/proj_oj-core_git/scripts/oj_macosx.command
 425   0   0  no_bomtext
/cygdrive/e/proj_oj-core_git/scripts/oj_windows.bat

regards ..ede


___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] next maintenance OJ 2.1.1 release?

[Michaud Michael]

Thank you, Ede,There is no renaming problem, I did not see the "recompress" repository.I just uploaded the 6 bundles into OpenJUMP 2 snapshot repository on sourceforge.Please have one more test for linux/mac (on linux, I get a problem during my test with the sh file which hadCRLF eof on my box. I could change it but I could not commit the change. I think it is OK on github and thatgit accept different eof between origin and local repository. Just hope that it will not change my local file back to CRLF inadvertentlyMichaël     envoyé : 26 novembre 2022 à 19:14de : edgar.sol...@web.deà : OpenJump develop and use objet : Re: [JPP-Devel] next maintenance OJ 2.1.1 release?On 26.11.2022 13:54, Michaud Michael wrote:Hi Ede,I upgraded the launch4j library because I had problem to define the minimum java version with the older (openjump installer could not recognized my java install).good catch. seem to recall that that was the reason i didn't upload executable installers earlier.I tested on windows and did a quick try on linux but cannot test on mac.will do in a vm and come back.Also I noticed that we usually uplaod a OpenJUMP-portable version but none of the version I produce with maven has this name.if you package profile *portable* like `mvn package -P release,portable,installer,srczip,javadoc` then the portable distro files should be under `target/recompress/` . it's documented on https://ojwiki.soldin.de/index.php?title=Creating_an_OJ_release_versionmain difference is some jar recompression (keep distro small) and permisson fixing for executables. you can have a look in the pom.xmlTell me if I missed something about file naming. Files are ready to be uploaded on sourceforge except this naming problem.sorry? what naming issue? feel free to upload to sf.net/files in a release candidate folder and i can have a look :) . we can rename it if it's fine or upload again in case something needs to be changed.regards ..ede___Jump-pilot-devel mailing listJump-pilot-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] next maintenance OJ 2.1.1 release?

[edgar . soldin]

On 26.11.2022 13:54, Michaud Michael wrote:

Hi Ede,

I upgraded the launch4j library because I had problem to define the minimum 
java version with the older (openjump installer could not recognized my java 
install).


good catch. seem to recall that that was the reason i didn't upload executable 
installers earlier.


I tested on windows and did a quick try on linux but cannot test on mac.


will do in a vm and come back.


Also I noticed that we usually uplaod a OpenJUMP-portable version but none of 
the version I produce with maven has this name.


if you package profile *portable* like `mvn package -P 
release,portable,installer,srczip,javadoc` then the portable distro files 
should be under `target/recompress/` . it's documented on 
https://ojwiki.soldin.de/index.php?title=Creating_an_OJ_release_version

main difference is some jar recompression (keep distro small) and permisson 
fixing for executables.  you can have a look in the pom.xml


Tell me if I missed something about file naming. Files are ready to be uploaded 
on sourceforge except this naming problem.


sorry? what naming issue? feel free to upload to sf.net/files in a release 
candidate folder and i can have a look :) . we can rename it if it's fine or 
upload again in case something needs to be changed.

regards ..ede



___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] next maintenance OJ 2.1.1 release?

[Michaud Michael]

Hi Ede,I upgraded the launch4j library because I had problem to define the minimum java version with the older (openjump installer could not recognized my java install).I tested on windows and did a quick try on linux but cannot test on mac.Also I noticed that we usually uplaod a OpenJUMP-portable version but none of the version I produce with maven has this name.Tell me if I missed something about file naming. Files are ready to be uploaded on sourceforge except this naming problem.Michaëlenvoyé : 21 octobre 2022 à 12:30de : edgar.sol...@web.deà : OpenJump develop and use objet : [JPP-Devel] next maintenance OJ 2.1.1 release?we got some bugfixes in by nowhttps://ojsnaps.soldin.de/readme.txtshould we, could we, Mike do you wanna? just adapted https://ojwiki.soldin.de/index.php?title=Creating_an_OJ_release_version#The_release_step_by_step_listsunny regards.. ede___Jump-pilot-devel mailing listJump-pilot-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] next maintenance OJ 2.1.1 release?

[Giuseppe Aruta]

Hi Ede,
It is Ok for me. I still have a couple of modifications I did on OpenJUMP
1.16 but not implemented yet in OpenJUMP 2.X.
I start today to do the modifications
Peppe

Il giorno ven 21 ott 2022 alle ore 12:31  ha scritto:

> we got some bugfixes in by now
> https://ojsnaps.soldin.de/readme.txt
>
> should we, could we, Mike do you wanna? just adapted
> https://ojwiki.soldin.de/index.php?title=Creating_an_OJ_release_version#The_release_step_by_step_list
>
> sunny regards.. ede
>
>
> ___
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel