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
When developping, devs may compile a new version of a native lib containing new code under test. We should find and document the best way for this dev to keep this lib without the "nativedependencies-maven-plugin" overwriting this lib each time.
The text was updated successfully, but these errors were encountered:
Additional info: problem arise if when the CI pushed updated native builds everyday, but the dev wants to keep working with his own hand-compiled .so/.dll. So building his local project may trigger the overwrite.
One way could be to tell him to just use offline Maven (mvn -o).
Another way would be to write (manually, or at least independantly from the nativedependencies plugin) a 'warning' flag in the json file in /taget/natives so that the nativedependencies plugin knows he should not do anything or at least not overwrite a specific lib.
When developping, devs may compile a new version of a native lib containing new code under test. We should find and document the best way for this dev to keep this lib without the "nativedependencies-maven-plugin" overwriting this lib each time.
The text was updated successfully, but these errors were encountered: