[WFCORE-6241] Adding 'quickly' profile for fast maven builds with quick profile

[khermano]

Issue: https://issues.redhat.com/browse/WFCORE-6241

My machine:

mvn clean install -DskipTests -> 02:00 min
mvn -Dquickly -> 01:24 min
mvnd -Dquickly -> 46.530 s (7 threads)

[yersan]

Is there any reason to add assembly.skipAssembly with 'false'? If so, don't add it to the profile, otherwise, I would expect it to be true

[yersan]

I also found the following ones as relevant, could you add them and share your opinion?

<maven.buildNumber.skip>true</maven.buildNumber.skip>
<maven.test.skip>true</maven.test.skip>
<license.skipDownloadLicenses>true</license.skipDownloadLicenses>

[yersan]

Forget about license.skipDownloadLicenses, it fails on a full build since the license file is required to allow the galleon-maven-plugin to do the provisioning

[khermano]

assembly.skipAssembly - I saw it in the description so I thought for some reason it needs to be explicitly defined in the pom, sorry about that :)
maven.test.skip - when I was talking with Martin he told me that this option was later removed from the wildly wildfly/wildfly#16416 ... this option was also skipping compiling tests and it brought some failures on CI, but when I tried mvn -Dquickly -Dmaven.repo.local=/tmp/localWfcore it looked okay, with no failures there, so I think in this case should be fine and I will use it, what do you think?
maven.buildNumber.skip - that looks great, thank you

[khermano]

So now, the original configuration runs on my machine mvn -Dquickly in 1:40 min and the new one in 1:20. mvn -Dquickly -Dmaven.repo.local=/tmp/localWfcoreQuickly also looks good without any failures.

[yersan]

Thank @khermano for pointing out the related WildFly PR.

I tried mvn -Dquickly -Dmaven.repo.local=/tmp/localWfcore it looked okay, with no failures there, so I think in this case should be fine and I will use it, what do you think?

Well, if we want to use the quickly profile to get builds ready to be tested, then we should switch the strategy and remove maven.test.skip and also assembly.skipAssembly since the Zip files generated will be used as artifacts for the WildFly integration test suite.

I'm sorry for the back-and-forth, but yes, now I think we should be consistent with the WildFly full quickly profile and follow the same approach allowing using this profile for building and testing WildFly Core. If you don't need the build for testing, you can manually assembly.skipAssembly and maven.test.skip.

Would you mind removing both to keep the consistency with WildFly full?

[khermano]

Not at all,
I will remove it right away. I understand that it should be consistent as much as possible.
Thank you very much for your help.