See https://builds.apache.org/job/sling-trunk-1.8/937/changes
See https://builds.apache.org/job/sling-trunk-1.6/3256/changes
Changes:
[sboehme] SLING-4555 Resource Editor: fixed e2e tests, node name handling in
the add node dialog and added an initial version of the add node e2e test
--
[...truncated 48421
[
https://issues.apache.org/jira/browse/SLING-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-4578.
-
Resolution: Fixed
Fixed in [r1671688|https://svn.apache.org/r1671688].
Incorrect Sightly JS
Hi,
somehow I managed to break the build of 'sling-trunk-1.6' by checking
something in to 'contrib/explorers/resourceeditor'. From what I
understand it should not have a dependency to that build, right?
It looks like an integration test of the Event Support project failed.
But I cannot
See https://builds.apache.org/job/sling-trunk-1.6/3257/changes
Changes:
[radu] releng: added Sightly to contrib reactor
[radu] SLING-4578 - Incorrect Sightly JS Use-API script dependency resolution
* explicitly check component inheritance when resolving script dependencies
* provided tests for
See https://builds.apache.org/job/sling-trunk-1.7/1648/changes
See https://builds.apache.org/job/sling-trunk-1.8/938/changes
Hi,
I reverted my changes in 'r1671740' and hope it fixes the build.
Best,
Sandro
Am 06.04.15 um 22:14 schrieb Sandro Boehme:
Hi,
somehow I managed to break the build of 'sling-trunk-1.6' by checking
something in to 'contrib/explorers/resourceeditor'. From what I
understand it should not
See https://builds.apache.org/job/sling-trunk-1.6/3258/changes
See https://builds.apache.org/job/sling-trunk-1.7/1649/changes
Hi,
It seems that this subject keeps popping up, and I'd like to get a
clearer image about how we split stuff between / ( aka 'the main build'
) and /contrib .
What I could gather for now is:
- there are both technical and community requirements for moving stuff
from /contrib to / , see
On Sunday 05 April 2015 21:55:31 Radu Cotescu wrote:
Hi Robert,
Hi,
I'm definitely not in favour of snapshot dependencies in the launchpad, so
we're on the same page here.
What do you mean by tangled dependencies? I know that the launchpad usually
doesn't contain bundles from contrib so I
On Mon, 2015-04-06 at 05:35 +, Bruce Edge wrote:
As I understand it, we want to pull in the master version of each
sub-module, not a specific version. This would be analogous a single
trunk checkout that we have today. The build-time bindings will still
be defined in launchpad(s), as
On Sun, 2015-04-05 at 22:03 +, Radu Cotescu wrote:
Hi Robert,
Sightly doesn't appear to be built with all the contrib modules [0].
It should be so feel free to include it.
Robert
Cheers,
Radu
[0] - https://github.com/apache/sling/blob/trunk/contrib/pom.xml
On Mon 6 Apr 2015
On Mon, Apr 6, 2015 at 12:55 AM, Radu Cotescu r...@apache.org wrote:
I'm definitely not in favour of snapshot dependencies in the launchpad, so
we're on the same page here.
What do you mean by tangled dependencies? I know that the launchpad usually
doesn't contain bundles from contrib so I
Hi Bruce,
On Fri, 2015-03-27 at 21:28 +, Bruce Edge wrote:
I'd like to make the debian package that's built by jenkins have a unique
version number that reflects the jenkins build number or some other
meaningful version string.
Currently it's stuck at 8-SNAPSHOT because this started off
[
https://issues.apache.org/jira/browse/SLING-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481140#comment-14481140
]
Robert Munteanu commented on SLING-4026:
You could use the mechanism added in
On Mon, Apr 6, 2015 at 10:58 AM, Oliver Lietz apa...@oliverlietz.de wrote:
On Sunday 05 April 2015 21:55:31 Radu Cotescu wrote:
Hi Robert,
Hi,
I'm definitely not in favour of snapshot dependencies in the launchpad, so
we're on the same page here.
What do you mean by tangled dependencies?
From: Robert Munteanu romb...@apache.orgmailto:romb...@apache.org
Reply-To: dev@sling.apache.orgmailto:dev@sling.apache.org
dev@sling.apache.orgmailto:dev@sling.apache.org
Date: Monday, April 6, 2015 at 4:12 AM
To: dev@sling.apache.orgmailto:dev@sling.apache.org
[
https://issues.apache.org/jira/browse/SLING-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481332#comment-14481332
]
Radu Cotescu commented on SLING-4447:
-
Besides [~sseif...@pro-vision.de]'s suggestion
From: Robert Munteanu romb...@apache.orgmailto:romb...@apache.org
Reply-To: dev@sling.apache.orgmailto:dev@sling.apache.org
dev@sling.apache.orgmailto:dev@sling.apache.org
Date: Monday, April 6, 2015 at 3:42 AM
To: dev@sling.apache.orgmailto:dev@sling.apache.org
hi Robert,
You're right that this deserves to be clarified.
On Mon, Apr 6, 2015 at 1:06 PM, Robert Munteanu romb...@apache.org wrote:
...- there are both technical and community requirements for moving stuff
from /contrib to / , see Bertrand's comment at [1]..
Yes, IMO the main thing is that
Radu Cotescu created SLING-4578:
---
Summary: Incorrect Sightly JS Use-API script dependency resolution
Key: SLING-4578
URL: https://issues.apache.org/jira/browse/SLING-4578
Project: Sling
Issue
23 matches
Mail list logo
