[jira] [Updated] (ISIS-1767) JEE 7+ Support
[
https://issues.apache.org/jira/browse/ISIS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber updated ISIS-1767:
-
Description:
Collective tasks for Java EE 7+ support.
Designated branch ...
{code}dev/2.0.0/ISIS-1767-jee-7{code}
+Tests+
* *Server*: JEE 7+ implementation (or similar), launched with JDK8 (Version
1.8.0_152); for deployment we use the HelloWorld artifact 1.15.1 with minor
modifications
* *fat-war*: deploy all dependencies with single war (hsqldb in memory)
* *skinny-war*: prepare container with shared libraries and shared domain
objects, deploy only a subset of domain classes with single war (hsqldb in
memory)
* *restEasy*: check whether restEasy responds
* managed connection pool (*con.pool*): use mysql db connection pool managed by
the JEE container and provided via JNDI
* domain events (*dom.events*): test whether domain events are emitted and
handled using AxonFramework's SimpleEventBus
* *swagger-ui*: test whether the static index.html from swagger-ui is served
and verify that a request for '//restful/swagger/private' returns
a JSON, that has the 'basePath' set to '//restful'
* *redeploy*: test whether all previous tests succeed if we do a
deploy-undeploy-deploy process
||Server ||fat-war ||skinny-war
||restEasy ||con.pool ||dom.events
||swagger-ui||redeploy||
|Payara (full 4.1.2.173) |{color:green}*OK*{color}
|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}(6)|
|Payara (web 4.1.2.173) |{color:green}*OK*{color}
|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}(6)|
|Glassfish (full 4.1.2) |*OK*(1) |*OK*(1)
|{color:green}*OK*{color}|todo
|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}(6)|
|Glassfish (web 5.0.1 beta)|{color:green}*OK*{color}
|{color:green}*OK*{color}|*OK*(5)|todo
|{color:green}*OK*{color}|{color:green}*OK*{color}|todo|
|Glassfish (full 5.0) |{color:red}*FAILED*(2){color}|todo
|todo|todo|todo
|todo|todo|
|Wildfly (full 11.0.0)|{color:red}*FAILED*(3){color}|todo
|todo|todo|todo
|todo|todo|
|TomEE (plume 7.0.4) |*OK*(4) |todo
|{color:green}*OK*{color}|todo|todo
|todo|todo|
Notes:
(1)
Guava version conflict: GF 4.2.1 has Guava-13, Isis has Guava-19;
WORKAROUND modify your glassfish installation ...
* in glassfish/modules/ replace guava.jar with that which comes packaged with
Payara-4.1.2.173 (Guava-19)
* you need to clear the OSGI cache: delete the folder
glassfish/domains/domainXXX/osgi-cache/felix
(2)
ON-HOLD waiting for GF 5.0.1 release!
class-loading issues with Hibernate Validator, though library is included in
war ... java.lang.ClassNotFoundException: org.joda.time.ReadableInstant;
using patch https://github.com/hibernate/hibernate-validator/pull/857/files
does not help: introduces new class-loading issues;
(3)
class-loading issues, though library is included in war ...
javax.persistence.PersistenceException: WFLYJPA0057: PersistenceProvider
'org.apache.isis.core.webapp.jee.PersistenceUnitNoopProvider' not found;
(4)
requires CXF to be disabled, see
https://stackoverflow.com/questions/41496204/tomee-7-0-2-how-to-disable-cxf-rs
throws exceptions on undeploy
(5)
JAX-RS API version clash
requires 4.0.0.Beta1
see https://issues.apache.org/jira/browse/ISIS-1779
(6)
successfully tested against DN-5.1.5-SNAPSHOT (dedicated issue
https://issues.apache.org/jira/browse/ISIS-1754)
was:
Collective tasks for Java EE 7+ support.
Designated branch ...
{code}dev/2.0.0/ISIS-1767-jee-7{code}
+Tests+
* *Server*: JEE 7+ implementation (or similar), launched with JDK8 (Version
1.8.0_152); for deployment we use the HelloWorld artifact 1.15.1 with minor
modifications
* *fat-war*: deploy all dependencies with single war (hsqldb in memory)
* *skinny-war*: prepare container with shared libraries and shared domain
objects, deploy only a subset of domain classes with single war (hsqldb in
memory)
* *restEasy*: check whether restEasy responds
* managed connection pool (*con.pool*): use mysql db connection pool managed by
the JEE container and provided via JNDI
* domain events (*dom.events*): test whether domain events are emitted and
handled using AxonFramework's SimpleEventBus
* *swagger-ui*: test whether the static index.html from
[jira] [Created] (ISIS-1790) Concurrent modification exception at startup
Vladimir Nisevic created ISIS-1790:
--
Summary: Concurrent modification exception at startup
Key: ISIS-1790
URL: https://issues.apache.org/jira/browse/ISIS-1790
Project: Isis
Issue Type: Bug
Components: Core
Affects Versions: 1.15.1
Reporter: Vladimir Nisevic
I have occasionally next exception during startup
{code}
1) Error in custom provider, java.lang.RuntimeException: An error occurred
while executing code in a temporary session
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSessionFactory(IsisInjectModule.java:109)
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSessionFactory(IsisInjectModule.java:109)
while locating org.apache.isis.core.runtime.system.session.IsisSessionFactory
for field at
org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.isisSessionFactory(IsisWicketApplication.java:155)
while locating domainapp.webapp.BgwWebApplication
1 error
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:455)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:353)
at
org.eclipse.jetty.servlet.FilterHolder.initialize(FilterHolder.java:139)
at
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:725)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:348)
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799)
at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
at org.eclipse.jetty.server.Server.start(Server.java:452)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
at org.eclipse.jetty.server.Server.doStart(Server.java:419)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.apache.isis.core.webserver.WebServer.start(WebServer.java:179)
at org.apache.isis.core.webserver.WebServer.run(WebServer.java:131)
at org.apache.isis.core.webserver.WebServer.main(WebServer.java:98)
at org.apache.isis.WebServer.main(WebServer.java:25)
Caused by: com.google.inject.ProvisionException: Unable to provision, see the
following errors:
1) Error in custom provider, java.lang.RuntimeException: An error occurred
while executing code in a temporary session
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSessionFactory(IsisInjectModule.java:109)
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSessionFactory(IsisInjectModule.java:109)
while locating org.apache.isis.core.runtime.system.session.IsisSessionFactory
for field at
org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.isisSessionFactory(IsisWicketApplication.java:155)
while locating domainapp.webapp.BgwWebApplication
1 error
at
com.google.inject.internal.Errors.throwProvisionExceptionIfErrorsExist(Errors.java:486)
at
com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:67)
at
com.google.inject.internal.InjectorImpl.injectMembers(InjectorImpl.java:987)
at
org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.init(IsisWicketApplication.java:368)
at domainapp.webapp.BgwWebApplication.init(BgwWebApplication.java:41)
at org.apache.wicket.Application.initApplication(Application.java:953)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:429)
... 20 more
Caused by: java.lang.RuntimeException: An error occurred while executing code
in a temporary session
at
org.apache.isis.core.runtime.system.session.IsisSessionFactory.doInSession(IsisSessionFactory.java:355)
at
org.apache.isis.core.runtime.system.session.IsisSessionFactory.doInSession(IsisSessionFactory.java:319)
at
org.apache.isis.core.runtime.system.session.IsisSessionFactory.doInSession(IsisSessionFactory.java:306)
at
org.apache.isis.core.runtime.system.session.IsisSessionFactoryBuilder.buildSessionFactory(IsisSessionFactoryBuilder.java:201)
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSessionFactory(IsisInjectModule.java:118)
at
[jira] [Created] (ISIS-1789) Metamodel validator thinks SQL query is a JDOQL query and fails
Gerrie Myburgh created ISIS-1789:
Summary: Metamodel validator thinks SQL query is a JDOQL query and
fails
Key: ISIS-1789
URL: https://issues.apache.org/jira/browse/ISIS-1789
Project: Isis
Issue Type: Bug
Components: Core
Affects Versions: 1.15.1
Environment: LINUX
Reporter: Gerrie Myburgh
Priority: Minor
the following SQL Query definition :
{code:java}
@javax.jdo.annotations.Queries(Array(
new javax.jdo.annotations.Query(
name = "findByDescriptiveName",
value = "SELECT "
+ "FROM domainapp.modules.system.dom.impl.FileObject "
+ "WHERE descriptiveName.indexOf(:descriptiveName) >= 0 "),
new javax.jdo.annotations.Query(
name = "findByApplicationComponent",
language="SQL",
value = "select fo.* " +
" from " +
"FileObject fo, " +
" Component_File cf, " +
" ComponentObject co, " +
" Application_Component ac, " +
" ApplicationObject ao " +
" where " +
"ao.name = :application and " +
" ao.application_id = ac.application_id and " +
" co.component_id = ac.component_id and " +
" co.name = :component and " +
" co.component_id = cf.component_id and " +
" cf.file_id = fo.file_id ",
resultClass=classOf[FileObject] )
)
)
{code}
makes the metamodel validator fail thinking that the query type is JDOQL.
{noformat}
domainapp.modules.system.dom.impl.FileObject: error in JDOQL query, class name
for FROM clause not recognized (JDOQL : select fo.* from FileObject
fo, Component_File cf, ComponentObject co, Application_Component
ac, ApplicationObject ao where ao.name = :application and
ao.application_id = ac.application_id and co.component_id =
ac.component_id and co.name = :component and co.component_id =
cf.component_id and cf.file_id = fo.file_id )
Please inspect the above messages and correct your domain model.
{noformat}
The validator should ignore SQL query types and let DataNucleus handle it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ISIS-1788) Reduce the number of calls on a dependent choices field
Dan Haywood created ISIS-1788: - Summary: Reduce the number of calls on a dependent choices field Key: ISIS-1788 URL: https://issues.apache.org/jira/browse/ISIS-1788 Project: Isis Issue Type: Improvement Affects Versions: 1.15.1 Reporter: Dan Haywood Fix For: 1.16.0 , should only be called when the preceding param changes. ref: ECP-396 (editSeller on IncomingDocAsViewModel), in-line prompt. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1786) Allow the default defaultView for collections to be configured globally.
[ https://issues.apache.org/jira/browse/ISIS-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274274#comment-16274274 ] ASF subversion and git services commented on ISIS-1786: --- Commit 04a7edc964bef1e66ec8367171ab5b8693fdb9f4 in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=04a7edc ] ISIS-1786: fixes unit test > Allow the default defaultView for collections to be configured globally. > > > Key: ISIS-1786 > URL: https://issues.apache.org/jira/browse/ISIS-1786 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > > The current default is officially "hidden"; ie need to annotate with > @CollectionLayout(defaultView="table") or the equivalent in the .layout.xml. > This ticket is to introduce a new configuration property that would allow the > default used to be set to "table", thus obviating the need to explicitly > configure everywhere. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1786) Allow the default defaultView for collections to be configured globally.
[ https://issues.apache.org/jira/browse/ISIS-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274252#comment-16274252 ] ASF subversion and git services commented on ISIS-1786: --- Commit ba12bafffad33b603f63b0b782909584c6e0fe71 in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ba12baf ] ISIS-1786: adds support for isis.viewers.collectionLayout.defaultView config property > Allow the default defaultView for collections to be configured globally. > > > Key: ISIS-1786 > URL: https://issues.apache.org/jira/browse/ISIS-1786 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > > The current default is officially "hidden"; ie need to annotate with > @CollectionLayout(defaultView="table") or the equivalent in the .layout.xml. > This ticket is to introduce a new configuration property that would allow the > default used to be set to "table", thus obviating the need to explicitly > configure everywhere. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1787) Property named 'Active' conflicts with Bootstrap CSS class
[
https://issues.apache.org/jira/browse/ISIS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sander Ginn updated ISIS-1787:
--
Description:
Property names are added as a class to the corresponding HTML element:
!cssclass.png!
For a property named 'Active', this conflicts with the CSS class {{.active}} of
Bootstrap, indicating a selected/active element in the UI. In my example, this
results in the column of this property in tables being highlighted:
!highlighted.png!
was:
Property names are added as a class to the corresponding HTML element:
!cssclass.png|thumbnail!
For a property named 'Active', this conflicts with the CSS class {{.active}} of
Bootstrap, indicating a selected/active element in the UI. In my example, this
results in the column of this property in tables being highlighted:
!highlighted.png|thumbnail!
> Property named 'Active' conflicts with Bootstrap CSS class
> --
>
> Key: ISIS-1787
> URL: https://issues.apache.org/jira/browse/ISIS-1787
> Project: Isis
> Issue Type: Bug
>Affects Versions: 1.15.1
>Reporter: Sander Ginn
>Priority: Trivial
> Attachments: cssclass.png, highlighted.png
>
>
> Property names are added as a class to the corresponding HTML element:
> !cssclass.png!
> For a property named 'Active', this conflicts with the CSS class {{.active}}
> of Bootstrap, indicating a selected/active element in the UI. In my example,
> this results in the column of this property in tables being highlighted:
> !highlighted.png!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1787) Property named 'Active' conflicts with Bootstrap CSS class
[
https://issues.apache.org/jira/browse/ISIS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sander Ginn updated ISIS-1787:
--
Attachment: (was: Screen Shot 2017-12-01 at 11.37.19.png)
> Property named 'Active' conflicts with Bootstrap CSS class
> --
>
> Key: ISIS-1787
> URL: https://issues.apache.org/jira/browse/ISIS-1787
> Project: Isis
> Issue Type: Bug
>Affects Versions: 1.15.1
>Reporter: Sander Ginn
>Priority: Trivial
> Attachments: cssclass.png, highlighted.png
>
>
> Property names are added as a class to the corresponding HTML element:
> !cssclass.png|thumbnail!
> For a property named 'Active', this conflicts with the CSS class {{.active}}
> of Bootstrap, indicating a selected/active element in the UI. In my example,
> this results in the column of this property in tables being highlighted:
> !highlighted.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1787) Property named 'Active' conflicts with Bootstrap CSS class
[
https://issues.apache.org/jira/browse/ISIS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sander Ginn updated ISIS-1787:
--
Attachment: (was: Screen Shot 2017-12-01 at 11.17.41.png)
> Property named 'Active' conflicts with Bootstrap CSS class
> --
>
> Key: ISIS-1787
> URL: https://issues.apache.org/jira/browse/ISIS-1787
> Project: Isis
> Issue Type: Bug
>Affects Versions: 1.15.1
>Reporter: Sander Ginn
>Priority: Trivial
> Attachments: cssclass.png, highlighted.png
>
>
> Property names are added as a class to the corresponding HTML element:
> !cssclass.png|thumbnail!
> For a property named 'Active', this conflicts with the CSS class {{.active}}
> of Bootstrap, indicating a selected/active element in the UI. In my example,
> this results in the column of this property in tables being highlighted:
> !highlighted.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1787) Property named 'Active' conflicts with Bootstrap CSS class
[
https://issues.apache.org/jira/browse/ISIS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sander Ginn updated ISIS-1787:
--
Attachment: cssclass.png
highlighted.png
Description:
Property names are added as a class to the corresponding HTML element:
!cssclass.png|thumbnail!
For a property named 'Active', this conflicts with the CSS class {{.active}} of
Bootstrap, indicating a selected/active element in the UI. In my example, this
results in the column of this property in tables being highlighted:
!highlighted.png|thumbnail!
was:
Property names are added as a class to the corresponding HTML element:
!Screen Shot 2017-12-01 at 11.17.41.png|thumbnail!
For a property named 'Active', this conflicts with the CSS class {{.active}} of
Bootstrap, indicating a selected/active element in the UI. In my example, this
results in the column of this property in tables being highlighted:
!Screen Shot 2017-12-01 at 11.17.41.png|thumbnail!
> Property named 'Active' conflicts with Bootstrap CSS class
> --
>
> Key: ISIS-1787
> URL: https://issues.apache.org/jira/browse/ISIS-1787
> Project: Isis
> Issue Type: Bug
>Affects Versions: 1.15.1
>Reporter: Sander Ginn
>Priority: Trivial
> Attachments: Screen Shot 2017-12-01 at 11.17.41.png, Screen Shot
> 2017-12-01 at 11.37.19.png, cssclass.png, highlighted.png
>
>
> Property names are added as a class to the corresponding HTML element:
> !cssclass.png|thumbnail!
> For a property named 'Active', this conflicts with the CSS class {{.active}}
> of Bootstrap, indicating a selected/active element in the UI. In my example,
> this results in the column of this property in tables being highlighted:
> !highlighted.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ISIS-1787) Property named 'Active' conflicts with Bootstrap CSS class
Sander Ginn created ISIS-1787:
-
Summary: Property named 'Active' conflicts with Bootstrap CSS class
Key: ISIS-1787
URL: https://issues.apache.org/jira/browse/ISIS-1787
Project: Isis
Issue Type: Bug
Affects Versions: 1.15.1
Reporter: Sander Ginn
Priority: Trivial
Attachments: Screen Shot 2017-12-01 at 11.17.41.png, Screen Shot
2017-12-01 at 11.37.19.png
Property names are added as a class to the corresponding HTML element:
!Screen Shot 2017-12-01 at 11.17.41.png|thumbnail!
For a property named 'Active', this conflicts with the CSS class {{.active}} of
Bootstrap, indicating a selected/active element in the UI. In my example, this
results in the column of this property in tables being highlighted:
!Screen Shot 2017-12-01 at 11.17.41.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ISIS-1786) Allow the default defaultView for collections to be configured globally.
Dan Haywood created ISIS-1786: - Summary: Allow the default defaultView for collections to be configured globally. Key: ISIS-1786 URL: https://issues.apache.org/jira/browse/ISIS-1786 Project: Isis Issue Type: Improvement Reporter: Dan Haywood The current default is officially "hidden"; ie need to annotate with @CollectionLayout(defaultView="table") or the equivalent in the .layout.xml. This ticket is to introduce a new configuration property that would allow the default used to be set to "table", thus obviating the need to explicitly configure everywhere. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-1786) Allow the default defaultView for collections to be configured globally.
[ https://issues.apache.org/jira/browse/ISIS-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood reassigned ISIS-1786: - Assignee: Dan Haywood Affects Version/s: 1.15.1 Fix Version/s: 1.16.0 > Allow the default defaultView for collections to be configured globally. > > > Key: ISIS-1786 > URL: https://issues.apache.org/jira/browse/ISIS-1786 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > > The current default is officially "hidden"; ie need to annotate with > @CollectionLayout(defaultView="table") or the equivalent in the .layout.xml. > This ticket is to introduce a new configuration property that would allow the > default used to be set to "table", thus obviating the need to explicitly > configure everywhere. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1784) Support for the builder pattern for fixtures, along with more flexibility in fixture setup using ValueFixtureScript
[ https://issues.apache.org/jira/browse/ISIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274151#comment-16274151 ] ASF subversion and git services commented on ISIS-1784: --- Commit 03acbe20d2b6e6346c7b6fcbb7a8f7321067e035 in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=03acbe2 ] ISIS-1784: renames EnumWith and toFixtureScript to PersonaWith and toBuilderScript > Support for the builder pattern for fixtures, along with more flexibility in > fixture setup using ValueFixtureScript > --- > > Key: ISIS-1784 > URL: https://issues.apache.org/jira/browse/ISIS-1784 > Project: Isis > Issue Type: New Feature >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > > ... and return the previously executed script where necessary whenever a SKIP > occurs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
