Once the generator supports crossreferencing between EPackages (#5), it becomes relevant how to treat legacy plugin URLs. The generator does not understand plugin URL as it does not run inside Eclipse. In future version, the generator will handle it like this:
In a pre-validation phase it gets all URLs for the source ecore file it is not able to resolve.
It generates a configuration file that maps the unresolved URL to a relative or absolute file path.
The user has to complete the relative or absolute file path manually.
In any subsequent runs of the generator, it will use the configuration file.
Once the generator supports crossreferencing between EPackages (#5), it becomes relevant how to treat legacy plugin URLs. The generator does not understand plugin URL as it does not run inside Eclipse. In future version, the generator will handle it like this:
In a pre-validation phase it gets all URLs for the source ecore file it is not able to resolve.
It generates a configuration file that maps the unresolved URL to a relative or absolute file path.
The user has to complete the relative or absolute file path manually.
In any subsequent runs of the generator, it will use the configuration file.