I think a sync in both directions is problematic and I wouldn't go there -
but I know that there only a few having this opinion.
In my opinion, when I'm talking about a developer that's someone who
develops code including scripts and usually Java - this might also include
coding in client side
Carsten Ziegeler created SLING-2896:
---
Summary: Job might be executed twice if a topology event occurs
Key: SLING-2896
URL: https://issues.apache.org/jira/browse/SLING-2896
Project: Sling
Hi Carsten,
On 2 June 2013 18:41, Carsten Ziegeler cziege...@apache.org wrote:
I think a sync in both directions is problematic and I wouldn't go there -
but I know that there only a few having this opinion.
In my opinion, when I'm talking about a developer that's someone who
develops code
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/1679/
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/1679/
--
[...truncated 1024 lines...]
at java.lang.Thread.run(Thread.java:662)
2013-06-02 11:45:34.788:INFO:/:sling: Apache Sling successfully
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/52/
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/52/
See https://builds.apache.org/job/sling-trunk-1.7/changes
On Jun 2, 2013, at 10:41 AM, Carsten Ziegeler wrote:
I think a sync in both directions is problematic and I wouldn't go there -
but I know that there only a few having this opinion.
In my opinion, when I'm talking about a developer that's someone who
develops code including scripts and
Bjoern Weide created SLING-2897:
---
Summary: [LOG] Enhance web console plugin with edit feature
Key: SLING-2897
URL: https://issues.apache.org/jira/browse/SLING-2897
Project: Sling
Issue Type:
[
https://issues.apache.org/jira/browse/SLING-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bjoern Weide updated SLING-2897:
Attachment: org.apache.sling.commons.log.patch
The patch is extending the webconsole and the
I'm trying to summarize my thoughts including the several opinions
scenarios stated:
a) The main usecase seems to be development from IDE (persisted to FS and
therefore to be integreated with any FS based versioning tool of choice)
b) a (on save) sync the application from FS to Sling via IDE
I was trying to dumb down the example with 'content', however, in the CQ
world there are a couple of areas where the tool comes with an editor
for certain functionalities, for example workflows. While I can manage
them in XML, it would be much nicer to manage them in CQ (or in the IDE,
maybe
Eric Norman created SLING-2898:
--
Summary: Failed integration tests for the new Resource Access Tags
Key: SLING-2898
URL: https://issues.apache.org/jira/browse/SLING-2898
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-2898.
Resolution: Fixed
Fix Version/s: JCR Resource 2.2.10
Launchpad Testing 7
Personally, I'm not a big fan of hiding flaky/failing tests since it tends
to remove some of the motivation to stabilize/fix them in a timely manner.
That's my 2 cents.
Regards,
Eric
On Fri, May 31, 2013 at 12:14 PM, Robert Munteanu romb...@apache.orgwrote:
Hi,
It seems that the
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/1680/
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/1680/
See https://builds.apache.org/job/sling-trunk-1.6/1680/changes
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.installer.provider.jcr/53/
--
[...truncated 473 lines...]
23:10:44.426 INFO [main] TransientRepository.java:423 Session closed
23:10:44.428 INFO [main]
I agree here: Disabling the test and having an issue keeps the build green but
bears the danger of forgetting about it ...
Regards
Felix
Am 02.06.2013 um 16:04 schrieb Eric Norman:
Personally, I'm not a big fan of hiding flaky/failing tests since it tends
to remove some of the motivation to
See https://builds.apache.org/job/sling-trunk-1.7/53/changes
Changes:
[enorman] SLING-2898 fixed failed integration tests for the new Resource Access
Tags
--
[...truncated 21067 lines...]
[INFO] Apache Sling JCR Resource Resolver SUCCESS
[
https://issues.apache.org/jira/browse/SLING-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672716#comment-13672716
]
Felix Meschberger commented on SLING-2897:
--
Thank you very much for the patch.
Hi Ian,
2013/6/2 Ian Boston i...@tfd.co.uk
If by true dev you mean IDE only, then I will find that too restrictive,
others may too. I use whatever is most efficient to get the job done,
sometimes thats the IDE (refactoring), sometimes its the command line
(branch management, full scale
For c) java code and bundles, I would suggest to leave this out for now and
see if we can integrate other tooling for that work. I'm currently
exploring options and maybe we can leverage other peoples work for that
Carsten
2013/6/2 Dominik Süß dominik.su...@gmail.com
I'm trying to summarize
25 matches
Mail list logo
