You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/03/02 09:27:11 UTC
[GitHub] [camel-quarkus] ppalaga opened a new issue #831: Move Groovy
executions under the enforce profile
ppalaga opened a new issue #831: Move Groovy executions under the enforce profile
URL: https://github.com/apache/camel-quarkus/issues/831
I profiled maven builds that I execute quite often and i found that enforcer and Groovy make ~18% of the build time. enforcer is easy to skip via `-Denforce=false` but we do not have anything like that for Groovy. Given that our Groovy scripts serve a purpose quite similar to the enforcer, I propose to move the Groovy executions under the `enforce` profile, so that they all can be skipped together. WDYT?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [camel-quarkus] ppalaga commented on issue #831: Move Groovy
executions under the enforce profile
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #831: Move Groovy executions under the enforce profile
URL: https://github.com/apache/camel-quarkus/issues/831#issuecomment-593308493
Actually we do that in `poms/build-parent/pom.xml` for `validate-dependencies.groovy` already. So we should do that for the other two validation groovy scripts too.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [camel-quarkus] lburgazzoli commented on issue #831: Move Groovy
executions under the enforce profile
Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #831: Move Groovy executions under the enforce profile
URL: https://github.com/apache/camel-quarkus/issues/831#issuecomment-593308735
I did propose to make at least some of them proper enforce extensions so they would obey to the enforcer semantics, a profile would be good enough but it may be something to think about.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [camel-quarkus] oscerd closed issue #831: Move Groovy executions
under the enforce profile
Posted by GitBox <gi...@apache.org>.
oscerd closed issue #831: Move Groovy executions under the enforce profile
URL: https://github.com/apache/camel-quarkus/issues/831
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #831: Move
Groovy executions under the enforce profile
Posted by GitBox <gi...@apache.org>.
lburgazzoli edited a comment on issue #831: Move Groovy executions under the enforce profile
URL: https://github.com/apache/camel-quarkus/issues/831#issuecomment-593308735
Some time ago I did propose to make at least some of them proper enforce extensions so they would obey to the enforcer semantics, a profile would be good enough but it may be something to think about.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services