You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should create platform file specifications in EFileSpecification for JAR/ZIP and in-memory file systems. Those platform specs would allow to create files that match the restriction of their respective file system.
JAR is used eg to distribute the source files of a project. Can also be used to export the .class files though this is not really the use of JCodeModel. The specification is here
Inmemory is used to directly compile the .java files into the .class files, which can then be placed in another file system, or fed to a ClassLoader . I don't know the limitations of such a system, should work on them.
priority : very low.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
follow #74
Should create platform file specifications in EFileSpecification for JAR/ZIP and in-memory file systems. Those platform specs would allow to create files that match the restriction of their respective file system.
JAR is used eg to distribute the source files of a project. Can also be used to export the .class files though this is not really the use of JCodeModel. The specification is here
Inmemory is used to directly compile the .java files into the .class files, which can then be placed in another file system, or fed to a ClassLoader . I don't know the limitations of such a system, should work on them.
priority : very low.
The text was updated successfully, but these errors were encountered: