hello, after some day testing, I found that when the compling has some errors, it will pop up this windows ( java exit code =1 ) after the compiling via command line.
scenario 1:
1). open S32 Design studio and switch to a new workspace as E:\00_SoftWare_Program\NXP\nxp_s32_workspace
2). import a project in local disk dirve, as in E:\000_ProjectShare\honglin.liang\loop2test\
PS: the project folder is extracted from a zip file, which is sent by my colleague
3). clean the project via right click menu
4). build the project
5). no errors appear in "Problem View“

6). exit the S32 Design Studio
7). open cmd window, and goes into the path where the project locates, E:\000_ProjectShare\honglin.liang\loop2test\
8). build with command line: <s32ds install path>\eclipse\s32ds.exe -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data E:\00_SoftWare_Program\NXP\nxp_s32_workspace -cleanBuild <project name>/Debug
9). wait until the building finished, no "Java was started but returned exit code = 1" dialog pops up.
10). as a comparion, I also used eclipsec.exe to build the project, the result is same as using s32ds.exe
scenario 2:
1). base on scenario 1, switch to a new s32 design studio workspace, as E:\00_SoftWare_Program\NXP\s32ds_workspace
2). copy the same project folder to a new place, as in E:\jenkins_workspace\loop2test
3). import the project into S32 design studio
4). clean the project via right click menu
5). build the project
6). after the building finished, we can see that there are some errors in the Problem view of S32 Design Studio, and these errors has no relation with the project, and I can not find these files that errors indicating in the system local drives.

7). Exit S32 design Studio
8). open cmd window, and goes into the path where the project locates, E:\jenkins_workspace\loop2test
9). build with command line: <s32ds install path>\eclipse\s32ds.exe -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data E:\00_SoftWare_Program\NXP\s32ds_workspace -cleanBuild <project name>/Debug
10). wait until the building finished, and the "Java was started but returned exit code = 1" dialog will pop up

11) . as a comparion, I also used eclipsec.exe to build the project, the result is same as using s32ds.exe
so I try to repeat scenario 2 with a s32 design studio and another new project location, the result is approximately the same, the difference is that the error number
and I try to go a further investigation, then I do below experiments:
a). Use scenario 1's S32 Design Studio workspace and scenario 2's project location to build
1). delete the .metadata under the s32 design studio root path
2). open S32 design studio and import the project
3). do the steps to build as described in scenario.
4). some erros appear in the Problem view of S32 Design Studio
5) and ""Java was started but returned exit code = 1" dialog" pops up when build using command line.
b). Use scenario 2's S32 Design Studio workspace and scenario 1's project location to build
1). delete the .metadata under the s32 design studio root path
2). open S32 design studio and import the project
3). do the steps to build as described in scenario.
4). no errors a in the Problem view of S32 Design Studio
5) and no ""Java was started but returned exit code = 1" dialog" pops up when build using command line.
so base on these experiments, does it means that the error has something to do with the project folder location, and none business about the S32 design studio worksapce ?