No problem:
The first think that needs to be done is switching the reference in the
binaries-list. In the beginning of the transition phase the Downloader task was
modified to recognize the pattern `group:name:version:classifier@extension`
(classifier + extension are optional). If the pattern is found, the file is
downloaded from maven central. See for example
`libs.amazon/external/binaries-list`.
The external files are referenced from the containing project in different
ways, as the file name will probably change, references need to be updated.
Check `project.properties`. The properties, that begin with `release.` specify
filemapping from the module into the release. So:
`release.external/glassfish-logging-2.0.jar=modules/ext/glassfish-logging-2.0.jar`
means, that the file `external/glassfish-logging-2.0.jar` (left-hand) will end
up in `<cluster>/modules/ext/glassfish-logging-2.0.jar` (right-hand).
You will also want to look in `project.xml`. The file you are changing might be
referenced and in this case it is so:
```xml
<class-path-extension>
<runtime-relative-path>ext/glassfish-logging-2.0.jar</runtime-relative-path>
<binary-origin>external/glassfish-logging-2.0.jar</binary-origin>
</class-path-extension>
```
I think you are able to deduce where the paths come from (hint: match them to
the `project.properties`).
If other code refers to files, this potentially needs to be adjusted - that
needs decisions case-by-case. Grep is your fried :-)
Hope that helps a bit.
[ Full content available at:
https://github.com/apache/incubator-netbeans/pull/828 ]
This message was relayed via gitbox.apache.org for [email protected]
