[hibernate-issues] [JIRA] (HSEARCH-4795) build/configuration-properties-collector should not use the public parent POM because this will get this module published on release

Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4795 ( https://hibernate.atlassian.net/browse/HSEARCH-4795?atlOrigin=eyJpIjoiM2I... ) Re: build/configuration-properties-collector should not use the public parent POM because this will get this module published on release ( https://hibernate.atlassian.net/browse/HSEARCH-4795?atlOrigin=eyJpIjoiM2I... ) I think this was done that way initially to get the Javadocs rendered using the configuration for the public modules. But yeah … Also, I have already started converting the AP to what I’ve done in ORM. ORM was a bit easier as it uses Gradle and doesn’t need all these prefixes and so on. As for the Search, the idea so far is to convert the AP into a “main method” and run it with the exec plugin (or something along these lines) ( https://hibernate.atlassian.net/browse/HSEARCH-4795#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4795#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:4a69e91 )