[jira] [Updated] (ISIS-1741) ConcurrentModificationException during startup when launching packaged webapp with jetty

[Vladimir Nisevic (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ISIS-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Nisevic updated ISIS-1741:
---
Description: 
I get this exception (see attachment [^1741_applog.txt]) only when launching 
the version packaged with jetty, exception doesn't occur when launching within 
IDE (IntelliJ).

Maybe any idea? Not sure how could I reproduce it with simpleapp

  was:
I get this exception (see attachment [^1741_applog.txt]) only when launch the 
packaged version, exception doesn't occur when launching from IDE (IntelliJ)





> ConcurrentModificationException during startup when launching packaged webapp 
> with jetty
> 
>
> Key: ISIS-1741
> URL: https://issues.apache.org/jira/browse/ISIS-1741
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vladimir Nisevic
> Attachments: 1741_applog.txt
>
>
> I get this exception (see attachment [^1741_applog.txt]) only when launching 
> the version packaged with jetty, exception doesn't occur when launching 
> within IDE (IntelliJ).
> Maybe any idea? Not sure how could I reproduce it with simpleapp



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ISIS-1741) ConcurrentModificationException during startup when launching packaged webapp with jetty

[Vladimir Nisevic (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ISIS-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Nisevic updated ISIS-1741:
---
Description: 
I get this exception (see attachment [^1741_applog.txt]) only when launch the 
packaged version, exception doesn't occur when launching from IDE (IntelliJ)




  was:
I observe this exception (see attachment) only when launch the packaged 
version, exception doesn't occur when launching from IDE (IntelliJ)





> ConcurrentModificationException during startup when launching packaged webapp 
> with jetty
> 
>
> Key: ISIS-1741
> URL: https://issues.apache.org/jira/browse/ISIS-1741
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vladimir Nisevic
> Attachments: 1741_applog.txt
>
>
> I get this exception (see attachment [^1741_applog.txt]) only when launch the 
> packaged version, exception doesn't occur when launching from IDE (IntelliJ)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ISIS-1741) ConcurrentModificationException during startup when launching packaged webapp with jetty

[Vladimir Nisevic (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ISIS-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Nisevic updated ISIS-1741:
---
Attachment: 1741_applog.txt

> ConcurrentModificationException during startup when launching packaged webapp 
> with jetty
> 
>
> Key: ISIS-1741
> URL: https://issues.apache.org/jira/browse/ISIS-1741
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vladimir Nisevic
> Attachments: 1741_applog.txt
>
>
> I observe this exception (see attachment) only when launch the packaged 
> version, exception doesn't occur when launching from IDE (IntelliJ)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ISIS-1741) ConcurrentModificationException during startup when launching packaged webapp with jetty

[Vladimir Nisevic (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ISIS-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Nisevic updated ISIS-1741:
---
Summary: ConcurrentModificationException during startup when launching 
packaged webapp with jetty  (was: ConcurrentModificationException on startup 
when launching packaged webapp with jetty)

> ConcurrentModificationException during startup when launching packaged webapp 
> with jetty
> 
>
> Key: ISIS-1741
> URL: https://issues.apache.org/jira/browse/ISIS-1741
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vladimir Nisevic
>
> I observe this exception (see attachment) only when launch the packaged 
> version, exception doesn't occur when launching from IDE (IntelliJ)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ISIS-1741) ConcurrentModificationException on startup when launching packaged webapp with jetty

[Vladimir Nisevic (JIRA)]

Vladimir Nisevic created ISIS-1741:
--

 Summary: ConcurrentModificationException on startup when launching 
packaged webapp with jetty
 Key: ISIS-1741
 URL: https://issues.apache.org/jira/browse/ISIS-1741
 Project: Isis
  Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Vladimir Nisevic


I observe this exception (see attachment) only when launch the packaged 
version, exception doesn't occur when launching from IDE (IntelliJ)






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Looking towards Apache Isis 2.0.0 - deprecated stuff to remove.

[Jayesh Prajapati]

Make sense to me.

Cheers,
Jayesh

On 30-Sep-2017 11:15 AM, "Dan Haywood"  wrote:

> Hi folks,
>
>
> I've started work on Apache Isis 1.16.0 in which we'll be updating
> DataNucleus to 5.1.  This in turn requires moving to Java 8 as the minimum
> to run an Isis app.  Now that Java 9 is out, I think that's a reasonable
> minimum.
>
>
> Moving to Java 8 is in itself probably a good enough reason to rename this
> release as Apache Isis 2.0.0 (rather than 1.16.0).  But in any case, one of
> the DN classes - TypeSafeQuery - is exposed from the Apache Isis applib and
> in DN 5.1 that class is renamed ... so backward compatibility is broken
> anyway.  Since we aim to follow semver, we ought anyway to call this next
> release Apache Isis 2.0.0.  Do people agree?
>
> ~~~
>
> And, if that's the case, then we probably should look to remove other
> features that have been deprecated for a while.  I've created a wiki page
> [1] and identified what I think should be removed, based on stuff currently
> deprecated in the applib, along with some "softer" stuff, such as the old
> Xxx.layout.json format.
>
>
> If you have any opinions on this stuff, please edit that wiki page.
>
> I'm intending for 2.0.0 to be done by the end of year.
>
>
> Thx
>
> Dan
>
> [1]
> https://cwiki.apache.org/confluence/display/ISIS/
> ApplibCandidatesForRemovalInApacheIsis2
>

Re: Looking towards Apache Isis 2.0.0 - deprecated stuff to remove.

[Vladimir Nišević]

Hi Dan, great plan, looking forward to version 2.0.0!

Regards, Vladimir

Am 30.09.2017 07:45 schrieb "Dan Haywood" :

> Hi folks,
>
>
> I've started work on Apache Isis 1.16.0 in which we'll be updating
> DataNucleus to 5.1.  This in turn requires moving to Java 8 as the minimum
> to run an Isis app.  Now that Java 9 is out, I think that's a reasonable
> minimum.
>
>
> Moving to Java 8 is in itself probably a good enough reason to rename this
> release as Apache Isis 2.0.0 (rather than 1.16.0).  But in any case, one of
> the DN classes - TypeSafeQuery - is exposed from the Apache Isis applib and
> in DN 5.1 that class is renamed ... so backward compatibility is broken
> anyway.  Since we aim to follow semver, we ought anyway to call this next
> release Apache Isis 2.0.0.  Do people agree?
>
> ~~~
>
> And, if that's the case, then we probably should look to remove other
> features that have been deprecated for a while.  I've created a wiki page
> [1] and identified what I think should be removed, based on stuff currently
> deprecated in the applib, along with some "softer" stuff, such as the old
> Xxx.layout.json format.
>
>
> If you have any opinions on this stuff, please edit that wiki page.
>
> I'm intending for 2.0.0 to be done by the end of year.
>
>
> Thx
>
> Dan
>
> [1]
> https://cwiki.apache.org/confluence/display/ISIS/
> ApplibCandidatesForRemovalInApacheIsis2
>