Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find & document a way to enable devs to keep the natives they compile themselves for testing/coding #18

Open
fmarot opened this issue Jan 24, 2016 · 1 comment

Comments

@fmarot
Copy link
Owner

fmarot commented Jan 24, 2016

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.

@fmarot
Copy link
Owner Author

fmarot commented Feb 4, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant