ArchUnit defines those which won't work when you change the build directory.

Regarding the original ticket scope, not to depend on target, there's a couple of complications: You can load any custom native lib using at runtime. You only need to compile the native lib, not the Java project. I have proprietary SQLite for which I would like to compile JDBC Therefore, it would be handy to be able to change maven output directory not to overwrite target directory with the second run of mvn. So, I would like to inject my SQLite native libraries and not to use native libraries from src/main/resources.

And unfortunatelly, I have two completelly different proprietary SQLite libraries per each platform for which I need to compile JDBC. I have proprietary SQLite for which I would like to compile JDBC. Maybe the important thing to mention is that I don't have public SQLite. Thanks! I know I have a peculiar use case. I still don't understand what you are doing, but hey, we do accept PRs :) So in another words, I would like to have two different output directories for one JDBC project. I rename the output directory target to targetBĮverything should be done automatically in some script to be able to use it in CI.

I compile JDBC driver with libsqlitejdbcB.so.I rename the output directory target to targetA.I compile JDBC driver with libsqlitejdbcA.so.I would like to compile the same JDBC driver sources twice to get sqlite-jdbc-A.jar and sqlite-jdbc-B.jar. Let's say libsqlitejdbcA.so and libsqlitejdbcB.so. I have two different SQLite native libraries for one platform. That would be 2 different projects, in 2 different directory. My use case is that I have two different proprietary SQLite distributions (for the same platform) for which I would like to compile corresponding JDBC driver.įrom sqlite-jdbc. I would like to change default maven output directory target to something elseįrom sqlite-jdbc. Comments (11) gotson commented on March 5, 2023

Maven microsoft sql server jdbc driver