[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ]
Max Rydahl Andersen updated ERT-62:
-----------------------------------
Sprint: devex #1 February 2016, devex #2 February 2016, devex #3 February 2016 (was: devex #1 February 2016, devex #2 February 2016)
> Refactor JSDT Code Completion [EBZ#486776]
> ------------------------------------------
>
> Key: ERT-62
> URL: https://issues.jboss.org/browse/ERT-62
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Assignee: Ian Stewart-Binks
> Labels: General, bzira
>
> The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions.
> A proposal base for the code completion engine should include, but is not necessarily limited to:
> - Keywords
> - Identifiers (declared variables and functions in currently open JS file)
> - Recently used methods of functions (currently open JS file as a bare minimum)
> All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-4) Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097]
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/ERT-4?page=com.atlassian.jira.plugin.syst... ]
Max Rydahl Andersen updated ERT-4:
----------------------------------
Sprint: devex #1 February 2016, devex #2 February 2016, devex #3 February 2016 (was: devex #1 February 2016, devex #2 February 2016)
> Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097]
> ---------------------------------------------------------------------------------------
>
> Key: ERT-4
> URL: https://issues.jboss.org/browse/ERT-4
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
> Labels: bzira, wst.html
> Fix For: Neon (4.6) M6
>
>
> I'm developping a plugin for AngularJS https://github.com/angelozerr/angularjs-eclipse which is based on WTP.
> I have implemented validation for Angular which ignores (ng-* attributes, etc) with Java code without using your feature https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980
> But there is some limitation and it should be fantastic if WTP provides an extension point like this :
> ---------------------------------------------------
> public interface IHTMLIgnoreValidator {
> boolean shouldValidateAttributeName(IProject project, Element target, String attrName);
> boolean shouldValidateElementName((IProject project, Element target);
> }
> ---------------------------------------------------
> For more information please read https://github.com/angelozerr/angularjs-eclipse/issues/80#issuecomment-53...
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-19) JSDT should support the use of sourcevalidation extension point [EBZ#481344]
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/ERT-19?page=com.atlassian.jira.plugin.sys... ]
Max Rydahl Andersen updated ERT-19:
-----------------------------------
Sprint: devex #1 February 2016, devex #2 February 2016, devex #3 February 2016 (was: devex #1 February 2016, devex #2 February 2016)
> JSDT should support the use of sourcevalidation extension point [EBZ#481344]
> ----------------------------------------------------------------------------
>
> Key: ERT-19
> URL: https://issues.jboss.org/browse/ERT-19
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
> Priority: Trivial
> Labels: 3.8_M6, General, bzira
> Fix For: Neon (4.6) M6
>
>
> JSDT editor does not activate org.eclipse.wst.sse.ui.sourcevalidation extension point. We should enable the use of sourcevalidation extension point as a way for third party validators to extend/augment JSDT validation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-36) Disable TypeBinding and deprecate internal ast model [EBZ#484598]
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/ERT-36?page=com.atlassian.jira.plugin.sys... ]
Max Rydahl Andersen updated ERT-36:
-----------------------------------
Sprint: devex #1 February 2016, devex #2 February 2016, devex #3 February 2016 (was: devex #1 February 2016, devex #2 February 2016)
> Disable TypeBinding and deprecate internal ast model [EBZ#484598]
> -----------------------------------------------------------------
>
> Key: ERT-36
> URL: https://issues.jboss.org/browse/ERT-36
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
> Labels: 3.8_M5, General, bzira
> Fix For: Neon (4.6) M6
>
>
> Disable type binding to allow the replacement for a new Parser.
> maintaining 2 ast models is wasteful deprecate org.eclipse.wst.jsdt.internal.compiler.ast model in favor of dom ast model.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21788) Jenkins: builds for master and jbosstools-4.3.x are failing for openshift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21788?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21788:
-------------------------------------
Priority: Critical (was: Major)
> Jenkins: builds for master and jbosstools-4.3.x are failing for openshift
> -------------------------------------------------------------------------
>
> Key: JBIDE-21788
> URL: https://issues.jboss.org/browse/JBIDE-21788
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Nick Boldt
> Priority: Critical
> Labels: build, jenkins
>
> Both jenkins builds for [jbosstools-4.3.x|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbo...] and [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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: org.apache.maven.plugin.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490)
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21788) Jenkins: builds for master and jbosstools-4.3.x are failing for openshift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21788?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21788:
----------------------------------------
Assignee: Nick Boldt
> Jenkins: builds for master and jbosstools-4.3.x are failing for openshift
> -------------------------------------------------------------------------
>
> Key: JBIDE-21788
> URL: https://issues.jboss.org/browse/JBIDE-21788
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Nick Boldt
> Labels: build, jenkins
>
> Both jenkins builds for [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] and [jbosstools|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstool...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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: org.apache.maven.plugin.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490)
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21788) Jenkins: builds for master and jbosstools-4.3.x are failing for openshift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21788?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21788:
-------------------------------------
Description:
Both jenkins builds for [jbosstools-4.3.x|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbo...] and [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
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: org.apache.maven.plugin.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490)
at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{code}
was:
Both jenkins builds for [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] and [jbosstools|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstool...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
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: org.apache.maven.plugin.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490)
at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{code}
> Jenkins: builds for master and jbosstools-4.3.x are failing for openshift
> -------------------------------------------------------------------------
>
> Key: JBIDE-21788
> URL: https://issues.jboss.org/browse/JBIDE-21788
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Nick Boldt
> Labels: build, jenkins
>
> Both jenkins builds for [jbosstools-4.3.x|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbo...] and [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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: org.apache.maven.plugin.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490)
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month