Chetan Mehrotra created SLING-2719:
--
Summary: Deadlock in
ResourceResolverFactoryActivator.checkFactoryPreconditions
Key: SLING-2719
URL: https://issues.apache.org/jira/browse/SLING-2719
Project:
[
https://issues.apache.org/jira/browse/SLING-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13567643#comment-13567643
]
Chetan Mehrotra commented on SLING-2719:
Thread stacks referred in notes
[5]
[
https://issues.apache.org/jira/browse/SLING-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated SLING-2719:
---
Attachment: error-log-threaddump.zip
Attached is a zip which contains the two set of logs
Robert Munteanu created SLING-2720:
--
Summary: Update exported versions for extension fragments to match
well-known JAX-WS, JAXB, StAX and JAF versions
Key: SLING-2720
URL:
[
https://issues.apache.org/jira/browse/SLING-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-2720:
---
Attachment: SLING-2720.patch
Update exported versions for extension fragments to match
[
https://issues.apache.org/jira/browse/SLING-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-2719:
---
Assignee: Carsten Ziegeler
Deadlock in
Hi,
I've noticed that JAXB marshaling works out of the box, given that the proper
framework extension bundles are available. Since IIUC this has been a tricky
issue, I'd like to make sure that we keep this functionality working, by
creating an integration test.
I wanted to add it to
Hi
I think we discussed this already. But maybe we should just come to a
conclusion, that Sling requires Java 6.
WDYT ?
Regards
Felix
Am 31.01.2013 um 10:39 schrieb Robert Munteanu:
Hi,
I've noticed that JAXB marshaling works out of the box, given that the proper
framework extension
On Thu, Jan 31, 2013 at 5:42 PM, Felix Meschberger fmesc...@adobe.com wrote:
...I think we discussed this already. But maybe we should just come to a
conclusion, that Sling requires Java 6
We could probably use JUnit categories to segregate tests...but I was
going to say the exact same
Hi,
we see more and more problems with supporting Java 5 and we discussed
this several times in the past year(s?). So let's finally call a vote
and see where we all are.
I propose to drop Java 5 support in general - we should try to stick
to it where possible for supporting existing
On Thu, Jan 31, 2013 at 5:47 PM, Carsten Ziegeler cziege...@apache.org wrote:
...I propose to drop Java 5 support in general - we should try to stick
to it where possible for supporting existing installations, but each
module should be free to set the base to Java 6 if it makes sense
That
+1
Carsten
2013/1/31 Carsten Ziegeler cziege...@apache.org:
Hi,
we see more and more problems with supporting Java 5 and we discussed
this several times in the past year(s?). So let's finally call a vote
and see where we all are.
I propose to drop Java 5 support in general - we should try
+1
Antonio
On Jan 31, 2013, at 5:47 PM, Carsten Ziegeler wrote:
Hi,
we see more and more problems with supporting Java 5 and we discussed
this several times in the past year(s?). So let's finally call a vote
and see where we all are.
I propose to drop Java 5 support in general - we
[
https://issues.apache.org/jira/browse/SLING-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-2719:
Fix Version/s: Resource Resolver 1.0.4
Deadlock in
+1
Jeff.
-Original Message-
From: Carsten Ziegeler [mailto:cziege...@apache.org]
Sent: 31 January 2013 16:48
To: dev@sling.apache.org
Subject: [VOTE] Drop Java 5 Support in General
Hi,
we see more and more problems with supporting Java 5 and we discussed
this several times
+1
Thanks/Regards
Felix
Am 31.01.2013 um 10:47 schrieb Carsten Ziegeler:
Hi,
we see more and more problems with supporting Java 5 and we discussed
this several times in the past year(s?). So let's finally call a vote
and see where we all are.
I propose to drop Java 5 support in general
[
https://issues.apache.org/jira/browse/SLING-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2719.
-
Resolution: Fixed
I rewrote the whole register/unregister code to not hold any locks
See https://builds.apache.org/job/sling-trunk-1.6/1564/changes
+1
Ian
On Friday, February 1, 2013, Felix Meschberger wrote:
+1
Thanks/Regards
Felix
Am 31.01.2013 um 10:47 schrieb Carsten Ziegeler:
Hi,
we see more and more problems with supporting Java 5 and we discussed
this several times in the past year(s?). So let's finally call a vote
[
https://issues.apache.org/jira/browse/SLING-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13567925#comment-13567925
]
Andrew Khoury commented on SLING-2166:
--
It would also be nice to be able to configure
+1
Best regards
mike
-Original Message-
From: Carsten Ziegeler [mailto:cziege...@apache.org]
Sent: Thursday, January 31, 2013 5:48 PM
To: dev@sling.apache.org
Subject: [VOTE] Drop Java 5 Support in General
Hi,
we see more and more problems with supporting Java 5 and we
-0
Why even try to support Java 5? Let's just say Java 6 as a minimum across
the board and be done with it.
On Thu, Jan 31, 2013 at 11:47 AM, Carsten Ziegeler cziege...@apache.orgwrote:
Hi,
we see more and more problems with supporting Java 5 and we discussed
this several times in the
If we set Java 6 as the minimum for all modules, this creates
unnecessary work to ship a bugfix or enhancements to users running on
Java 5. And we have a lot of them.
The difference between Java 5 and Java 6 in terms of the languange or
the libraries is not that huge, so I think there is rarely a
On 2013-01-31 19:58, Justin Edelson wrote:
-0
Why even try to support Java 5? Let's just say Java 6 as a minimum across
the board and be done with it.
Indeed.
Or even Java7.
Best regards, Julian
Hi
In reality, the Sling Launchpad will not support Java 5 at all.
We could just as well have the parent POM setup API checks for Java 6 and
configure the Bundle-RequiredExecutionEnvironment appropriately.
Regards
Felix
Am 31.01.2013 um 12:58 schrieb Justin Edelson:
-0
Why even try to
Yeah, but if I want to fix something let's say in commons scheduler
and this is targetted for existing installations using Java 5 and I
don't need any Java 5 stuff, why should I have to go through the hasle
and create my own release just to have a bundle working with Java 5?
Having launchpad
Would saying we dont support Java 5 evidenced by not having a CI
build, but in the modules avoiding using Java6 features (eg
@Overrides) be enough ?
That could still be enforced by keeping source and target to 1.5
It would probably be good to keep the jdk5.properties around in
launchepad so you
I understand the use case, but it just seems like a hassle and makes
potential contributions like Robert was suggesting harder than they need to
be.
I want people to be able to checkout the Sling source code and make changes
to it and contribute those changes back. I don't want them wasting time
I don't see why this makes contributions harder: develop however you
want and contribute. The only minor thing is, as by default we still
target java 5 for a module and you use java 6, the build will fail,
you update the pom (a single property), build again and are happy. Not
really hard.
But I
On Thu, Jan 31, 2013 at 9:19 PM, Justin Edelson
jus...@justinedelson.com wrote:
...I want people to be able to checkout the Sling source code and make changes
to it and contribute those changes back. I don't want them wasting time
worry about (a) how to write Java 5-compatible code or (b)
2013/1/31 Bertrand Delacretaz bdelacre...@apache.org:
On Thu, Jan 31, 2013 at 9:19 PM, Justin Edelson
jus...@justinedelson.com wrote:
...I want people to be able to checkout the Sling source code and make
changes
to it and contribute those changes back. I don't want them wasting time
worry
Well again, I'm looking at Robert sending an email rather than just
creating a patch.
How about this - put this information (modules build against Java 5 by
default, but feel free to change it by doing XYZ) in the root README.
If no one asks about it again, then my concern will have been
Deal
Carsten
2013/1/31 Justin Edelson jus...@justinedelson.com:
Well again, I'm looking at Robert sending an email rather than just
creating a patch.
How about this - put this information (modules build against Java 5 by
default, but feel free to change it by doing XYZ) in the root README.
+1
On Thu, Jan 31, 2013 at 5:06 PM, Carsten Ziegeler cziege...@apache.orgwrote:
Deal
Carsten
2013/1/31 Justin Edelson jus...@justinedelson.com:
Well again, I'm looking at Robert sending an email rather than just
creating a patch.
How about this - put this information (modules build
34 matches
Mail list logo
