As part of the deployment process for JavaApplications on RemotePlatforms, Bedrock may create numerous "deployment" jars in the LocalPlatform temporary folder, each jar consisting of local classes/resources on the ClassPath. After these "deployment" jars are deployed to a RemotePlatform, they are left in the LocalPlatform temporary folder. Ideally these should be immediately cleaned up once a RemoteApplication has been deployed.
Usually this isn't a problem as the LocalPlatform operating system will often automatically clean up these files. However on some operating systems (like Windows) this may not happen, leading to a large number of files, potentially filling up the temporary folder.
As part of the deployment process for JavaApplications on RemotePlatforms, Bedrock may create numerous "deployment" jars in the LocalPlatform temporary folder, each jar consisting of local classes/resources on the ClassPath. After these "deployment" jars are deployed to a RemotePlatform, they are left in the LocalPlatform temporary folder. Ideally these should be immediately cleaned up once a RemoteApplication has been deployed.
Usually this isn't a problem as the LocalPlatform operating system will often automatically clean up these files. However on some operating systems (like Windows) this may not happen, leading to a large number of files, potentially filling up the temporary folder.