19.06.2010, 14:14
I had a look at the file structure of the swt OSX application you pointed me to.
I experiemented a little and I now have the most simple structure you can imagine. I think it will also work with the maven plugin structure. Currently the pom.xml for the Apps is very complicated. I don't know yet how to simplify that. We do not need the extensive plugin structure or JavaApplicationStub at all. Maybe there is a way to describe a pom.xml that will not build an OSX application, like it does now, but that will build a directory structure instead. Maven already builds that structure already, only doing more things.
An OSX application is actually nothing more than a special directory structure. Currently the Info.plist is built within the pom.xml using some maven variables. I think it should be possible to build the same file from maven without specifying a bundle as goal.
The only drawback of the new simplified structure is that the JavaStub also checks for the required java version (1.6+) and the simplified structure doesn't. Maybe that could be solved with a mini java app that checks for the java version.
The shell script could simply do an if-then-else as well. If stderr=0 execute the "exec java -XStart......" , else quit and show error message.
Please find "my" application here. I put the 64bit 19 June prerelease jar inside it.
I experiemented a little and I now have the most simple structure you can imagine. I think it will also work with the maven plugin structure. Currently the pom.xml for the Apps is very complicated. I don't know yet how to simplify that. We do not need the extensive plugin structure or JavaApplicationStub at all. Maybe there is a way to describe a pom.xml that will not build an OSX application, like it does now, but that will build a directory structure instead. Maven already builds that structure already, only doing more things.
An OSX application is actually nothing more than a special directory structure. Currently the Info.plist is built within the pom.xml using some maven variables. I think it should be possible to build the same file from maven without specifying a bundle as goal.
The only drawback of the new simplified structure is that the JavaStub also checks for the required java version (1.6+) and the simplified structure doesn't. Maybe that could be solved with a mini java app that checks for the java version.
Code:
If 1.6+ then stderr = 0
else stderr =1Please find "my" application here. I put the 64bit 19 June prerelease jar inside it.
