I have a Maven automation testing BDD-Cucumber framework project where the main folder contains essential testing configurations and reusable components. I want to allow clients to use these components and extend classes from the main folder, but I need to prevent them from viewing the implementation details available in main folder.
What would be the best approach or set of configurations to achieve this level of access restriction in a Maven project? Any insights or suggestions would be greatly appreciated.
I've explored various Maven configuration options and access control mechanisms, but haven't found a specific solution that addresses this scenario. I've looked into Maven's build profiles and resource filtering, but they don't seem to provide the level of access restriction I'm aiming for.
I'm looking for a way to configure my Maven automation testing BDD-Cucumber project so that clients can utilize the reusable components and extend classes from the main folder, but they shouldn't be able to view the implementation details within the main folder. This would provide a level of abstraction and protect sensitive information.
If you allow someone to extend a class, then you give them access to the implementation details.
There is no real way around that.