[JBoss JIRA] (DROOLS-2165) Upgrade revapi-maven-plugin from 0.9.4 to 0.9.5
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-2165:
----------------------------------------
Summary: Upgrade revapi-maven-plugin from 0.9.4 to 0.9.5
Key: DROOLS-2165
URL: https://issues.jboss.org/browse/DROOLS-2165
Project: Drools
Issue Type: Task
Components: build
Reporter: Geoffrey De Smet
Assignee: Michael Biarnes Kiefer
It's a good thing to just do,
but hopefully this message goes away on the jenkins job for drools:
{code}
09:33:13 [INFO] ------------------------------------------------------------------------
09:33:13 [INFO] Building KIE :: Maven Archetypes 7.6.0-SNAPSHOT
09:33:13 [INFO] ------------------------------------------------------------------------
09:33:13 [WARNING] *****************************************************************
09:33:13 [WARNING] * Your build is requesting parallel execution, but project *
09:33:13 [WARNING] * contains the following plugin(s) that have goals not marked *
09:33:13 [WARNING] * as @threadSafe to support parallel building. *
09:33:13 [WARNING] * While this /may/ work fine, please look for plugin updates *
09:33:13 [WARNING] * and/or request plugins be made thread-safe. *
09:33:13 [WARNING] * If reporting an issue, report it against the plugin in *
09:33:13 [WARNING] * question, not against maven-core *
09:33:13 [WARNING] *****************************************************************
09:33:13 [WARNING] The following plugins are not marked @threadSafe in KIE :: Public API:
09:33:13 [WARNING] org.revapi:revapi-maven-plugin:0.9.4
09:33:13 [WARNING] Enable debug to see more precisely which goals are not marked @threadSafe.
09:33:13 [WARNING] *****************************************************************
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ]
Ingo Weiss commented on WFCORE-3450:
------------------------------------
IIRC, bold requires some sort of terminal support as well. I need to do some research on that.
> CLI - avoid required attributes to be hard to see when using tab completion
> ----------------------------------------------------------------------------
>
> Key: WFCORE-3450
> URL: https://issues.jboss.org/browse/WFCORE-3450
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Reporter: Miroslav Novak
>
> This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in:
> {code}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add(
> ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier
> allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors*
> call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection
> call-timeout connection-ttl max-hops notification-attempts retry-interval
> {code}
> it's not clear at the first look how many required attributes there are.
> Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>.
> Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ]
Miroslav Novak commented on WFCORE-3450:
----------------------------------------
Another possibly less painful option might be to use *bold* text for attributes but it depends whether Aesh can do it. wdyt?
> CLI - avoid required attributes to be hard to see when using tab completion
> ----------------------------------------------------------------------------
>
> Key: WFCORE-3450
> URL: https://issues.jboss.org/browse/WFCORE-3450
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Reporter: Miroslav Novak
>
> This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in:
> {code}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add(
> ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier
> allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors*
> call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection
> call-timeout connection-ttl max-hops notification-attempts retry-interval
> {code}
> it's not clear at the first look how many required attributes there are.
> Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>.
> Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month