[JBoss JIRA] (DROOLS-3120) [DMN Designer] Validation Error State remains active
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3120:
-----------------------------------
Summary: [DMN Designer] Validation Error State remains active
Key: DROOLS-3120
URL: https://issues.jboss.org/browse/DROOLS-3120
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.13.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: Screenshot from 2018-10-11 17-50-01.png
The is sequence of steps the error validation state of node remains active. It is shown in the attachment.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3032:
-------------------------------------
[~jomarko] Thanks for checking it out!
* +1 to plus sign, thanks. :)
* WRT language maybe [~stetson.robinson] can helps us?
> [DMN Designer] UX "empty" state for custom data types
> -----------------------------------------------------
>
> Key: DROOLS-3032
> URL: https://issues.jboss.org/browse/DROOLS-3032
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-10-11 at 10.56.18 AM.png, Screenshot from 2018-09-24 18-12-02.png
>
>
> There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3032:
-------------------------------------
[~uxdlc] Thanks, looks nice for me, just two nitpicks.
- In empty project, we use "plus sign" as icon, shouldn't we do the same here?
- Shouldn't we be more explicit? "Add a custom data type. Press Add button above." instead of "Add a custom data type."? Really don't know, just discussing. I am fine if we keep as it is.
> [DMN Designer] UX "empty" state for custom data types
> -----------------------------------------------------
>
> Key: DROOLS-3032
> URL: https://issues.jboss.org/browse/DROOLS-3032
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-10-11 at 10.56.18 AM.png, Screenshot from 2018-09-24 18-12-02.png
>
>
> There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (SECURITY-995) JDK 11, unable to compile Picketbox
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/SECURITY-995?page=com.atlassian.jira.plug... ]
Martin Choma commented on SECURITY-995:
---------------------------------------
Mainly because of unit tests inside project. If it is easy so probably worth fixing.
> JDK 11, unable to compile Picketbox
> -----------------------------------
>
> Key: SECURITY-995
> URL: https://issues.jboss.org/browse/SECURITY-995
> Project: PicketBox
> Issue Type: Bug
> Affects Versions: PicketBox_5_1_1.Beta1
> Reporter: Martin Choma
> Assignee: Stefan Guilhen
> Priority: Major
> Labels: Java11
>
> It is not possible to compile PicketBox with jdk 11
> {noformat}
> git clone git@github.com:picketbox/picketbox.git
> cd picketbox
> java -version
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
> mvn install
> {noformat}
> {noformat}
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] java.lang.NoClassDefFoundError: javax/annotation/Generated
> at org.jboss.logging.processor.generator.model.ClassModel.generateModel(ClassModel.java:134)
> at org.jboss.logging.processor.generator.model.MessageBundleImplementor.generateModel(MessageBundleImplementor.java:58)
> at org.jboss.logging.processor.generator.model.ClassModel.generateAndWrite(ClassModel.java:119)
> at org.jboss.logging.processor.apt.ImplementationClassGenerator.processTypeElement(ImplementationClassGenerator.java:63)
> at org.jboss.logging.processor.apt.LoggingToolsProcessor.process(LoggingToolsProcessor.java:179)
> at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:972)
> at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:888)
> at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1214)
> at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1326)
> at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1258)
> at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:936)
> at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:104)
> at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:147)
> at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100)
> at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94)
> at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:174)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:943)
> at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:137)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:954)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.ClassNotFoundException: javax.annotation.Generated
> at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 41 more
> [ERROR] java.lang.NoClassDefFoundError: javax/annotation/Generated
> at org.jboss.logging.processor.generator.model.ClassModel.generateModel(ClassModel.java:134)
> at org.jboss.logging.processor.generator.model.MessageLoggerImplementor.generateModel(MessageLoggerImplementor.java:108)
> at org.jboss.logging.processor.generator.model.ClassModel.generateAndWrite(ClassModel.java:119)
> at org.jboss.logging.processor.apt.ImplementationClassGenerator.processTypeElement(ImplementationClassGenerator.java:63)
> at org.jboss.logging.processor.apt.LoggingToolsProcessor.process(LoggingToolsProcessor.java:179)
> at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:972)
> at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:888)
> at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1214)
> at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1326)
> at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1258)
> at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:936)
> at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:104)
> at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:147)
> at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100)
> at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94)
> at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:174)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:943)
> at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:137)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:954)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3032:
-------------------------------------
[~jomarko][~karreiro] Here is an initial mockup for an empty state. While it is somewhat non-standard there is a precedent in the workbench (please refer to associated jira.) I did initially mock this up using an inline error message, but for a variety of nuanced reasons decided the "empty state" approach offered a clearer path for the user. Please let me know what you think, thanks. [~mstevens1] for awareness/feedback.
!Screen Shot 2018-10-11 at 10.56.18 AM.png|thumbnail!
> [DMN Designer] UX "empty" state for custom data types
> -----------------------------------------------------
>
> Key: DROOLS-3032
> URL: https://issues.jboss.org/browse/DROOLS-3032
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-10-11 at 10.56.18 AM.png, Screenshot from 2018-09-24 18-12-02.png
>
>
> There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3109) [DMN Designer] Add additional Properties to drill-down
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3109?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3109:
-------------------------------------
[~manstis] Please file separate jira for each Expression type and link them to [epic|https://issues.jboss.org/browse/BAPL-1084]. I believe will facilitate clarification of what is and what is not implemented. I believe I will be able to do more valuable review then.
> [DMN Designer] Add additional Properties to drill-down
> ------------------------------------------------------
>
> Key: DROOLS-3109
> URL: https://issues.jboss.org/browse/DROOLS-3109
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
> h3. Literal expression
> ||Selected item||Properties panel items||type||
> |Cell|ExpressionLanguage|URI|
> h3. Context
> ||Selected item||Properties panel items||type||
> |Row|type Ref|ItemDefinition ref (same which applies to Key Cell|
> |Column|n/a|n/a|
> |Key Cell|type Ref|ItemDefinition ref|
> |Value Cell|ExpressionLanguage|URI|
> h3. Decision Table
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> | Input Column|Constraints|Text field|
> |Output Column|Output values|Unary tests|
> |Output Column|Default Output|expression|
> |Cell|ExpressionLanguage|URI|
> h3. Relation
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|type Ref|ItemDefinition ref|
> |Cell|ExpressionLanguage|URI|
> h3. Function
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|n/a|n/a|
> |Cell|ExpressionLanguage|URI|
> h3. Invocation
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|n/a|n/a|
> |Cell|ExpressionLanguage|URI|
> h2. Manual Acceptance Test
> - Switching between DRG and Grid editor, check proper fields shown
> - Switching between rows, columns, cells in Grid editor, check proper fields
> -- In same expression kind
> -- Across different expression kinds
> - Clear expression kind
> - Read only mode - older asset version
> - All Grid specific properties saved
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months