[Work in Progress] Issue #1815 - Added options that add missing versions to export packages #1961
+105
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following pull request draft addresses issue #1815 to add a fixed or bundled version to missing export packages. The following code changes reflect the solution my teammate @hilla-ryy and I have worked on so far.
Changes:
Obstacles: One of the obstacles my teammate @hilla-ryy and I have come across was adding the fixed and bundled versions to each package. After reviewing the codebase, we found within the Export Package Header.java file there is not a specific method for getting either a bundled or fixed version to add to the export package other than "getVersionAttribute". And in the Export Package Object.java file it looks like a bundled or fixed version is added when the export package object is created which means a new version can only be added by recreating the object. Is there a way we can add the correct version without recreating the export package object? For instance, we are working on adding the correct version directly into the manifest file of the export package.