Should BeDivFuzz use different package/artifact name?

[aoli-al]

BeDivFuzz still uses package and artifact names from JQF, which makes it unavailable on Maven Central. Is it possible to change the package/artifact names of BeDivFuzz and publish it to Maven Central for better usability?

[hoanglam-nguyen]

Hi,

yes it should be possible. I'm not familiar with publishing projects to Maven Central so I'll need some time to look into it. I suppose the recommended approach would be to refactor the project to use JQF as a dependency? The project also contains some changes to JQF internals to facilitate our experiments (e.g., collection of diversity metrics), which needs to be considered.

[aoli-al]

I see. I don't see a good solution. If the changes are generic, you may submit them to the upstream JQF repo. Or you may rename the entire JQF repo to de.hub.se.jqf

[hoanglam-nguyen]

I have cleaned up the repo in the standalone branch. The project now only consists of the core guidance implementation and a maven plugin with separate package/artifact names, using upstream JQF as a dependency. I will probably move our experimental infrastructure to a separate project.

Let me know if you are missing any other functionality. I still have to look into publishing the project to Maven Central, but I hope a local installation works for you in the meantime.