Hi Robert,
Am 28.11.16 um 23:32 schrieb Robert Munteanu:
On Fri, 2016-11-18 at 00:22 +0100, Sandro Boehme wrote:
Hi Julian,
I like the idea of individual Jenkins jobs for the reasons you
pointed out!
If we would have a "nightly" build (whatever time that would be) we
could link it at the
On Fri, 2016-11-18 at 00:22 +0100, Sandro Boehme wrote:
> Hi Julian,
>
> I like the idea of individual Jenkins jobs for the reasons you
> pointed out!
> If we would have a "nightly" build (whatever time that would be) we
> could link it at the Getting and building Sling page. We could write
>
Hi Sandro,
On Sun, Nov 27, 2016 at 11:39 PM, Sandro Boehme wrote:
> ...Is there a launchpad version somewhere that compiles the latest
> snapshots to the standalone jar?...
We've been discussing generating that [1] along with a "stable"
launchpad but that's not done yet.
Am 19.11.16 um 21:56 schrieb Sandro Boehme:
Am 17.11.16 um 23:22 schrieb Robert Munteanu:
On Thu, 2016-11-17 at 14:53 +0100, Julian Sedding wrote:
Hi Sandro
You are right. However, the full build on Jenkins failed too often.
Partly due to issues or flaky tests in Sling, partly due to e.g.
Am 17.11.16 um 23:22 schrieb Robert Munteanu:
On Thu, 2016-11-17 at 14:53 +0100, Julian Sedding wrote:
Hi Sandro
You are right. However, the full build on Jenkins failed too often.
Partly due to issues or flaky tests in Sling, partly due to e.g.
infrastructure issues. This made the Jenkins
Am 17.11.16 um 23:22 schrieb Robert Munteanu:
On Thu, 2016-11-17 at 14:53 +0100, Julian Sedding wrote:
Hi Sandro
You are right. However, the full build on Jenkins failed too often.
Partly due to issues or flaky tests in Sling, partly due to e.g.
infrastructure issues. This made the Jenkins
Hi Julian,
I like the idea of individual Jenkins jobs for the reasons you pointed out!
If we would have a "nightly" build (whatever time that would be) we
could link it at the Getting and building Sling page. We could write
there that in case the build does currently not work (e.g. because
On Thu, 2016-11-17 at 14:53 +0100, Julian Sedding wrote:
> Hi Sandro
>
> You are right. However, the full build on Jenkins failed too often.
> Partly due to issues or flaky tests in Sling, partly due to e.g.
> infrastructure issues. This made the Jenkins builds almost useless,
> because chances
Hi Sandro
You are right. However, the full build on Jenkins failed too often.
Partly due to issues or flaky tests in Sling, partly due to e.g.
infrastructure issues. This made the Jenkins builds almost useless,
because chances were that it weren't your changes that made the build
fail.
Therefore
According to our Jenkins job
https://builds.apache.org/job/sling-launchpad-builder-1.8/
the launchpad should work without issues.
A couple of additional questions:
- what Java version do you use for building and running Sling?
- what happens if you try to build the project with "-U", to
Hi Julian,
thanks for the changes! It works for me as well now.
Best,
Sandro
Am 16.11.16 um 13:29 schrieb Julian Sedding:
Hi Sandro
I have committed my changes to these modules and run the full build
multiple times. So I expect that you should be able to run a
successful trunk build now.
Hi Sandro
I have committed my changes to these modules and run the full build
multiple times. So I expect that you should be able to run a
successful trunk build now.
Regards
Julian
On Wed, Nov 16, 2016 at 1:18 PM, Robert Munteanu wrote:
> On Tue, 2016-11-15 at 15:51
On Tue, 2016-11-15 at 15:51 +0100, Sandro Boehme wrote:
> Hi Julian,
>
> thanks for your feedback!
>
> Am 15.11.16 um 10:47 schrieb Julian Sedding:
> > Hi Sandro
> >
> > org/apache/sling/jcr/base/LoginAdminWhitelist looks like your
> > checkout
> > or snapshots on your machine are not quite up
Hi Julian,
thanks for your feedback!
Am 15.11.16 um 10:47 schrieb Julian Sedding:
Hi Sandro
org/apache/sling/jcr/base/LoginAdminWhitelist looks like your checkout
or snapshots on your machine are not quite up to date. I removed the
I'am at the latest trunk, did 'mvn clean ...' and created a
Hi Sandro
org/apache/sling/jcr/base/LoginAdminWhitelist looks like your checkout
or snapshots on your machine are not quite up to date. I removed the
method AbstractSlingRepositoryManager.getLoginAdminWhitelist(), so
maybe you need to first build a local snapshot of bundles/jcr/base and
then try
Am 14.11.16 um 23:02 schrieb Robert Munteanu:
On Mon, 2016-11-14 at 21:50 +0100, Sandro Boehme wrote:
Hi Robert,
It took me a while to get the trunk to build. I had to disable
the
Rat
checks and update the dependency to org.apache.sling.jcr.base
version
2.4.3-SNAPSHOT in
On Mon, 2016-11-14 at 21:50 +0100, Sandro Boehme wrote:
> Hi Robert,
>
> > > It took me a while to get the trunk to build. I had to disable
> > > the
> > > Rat
> > > checks and update the dependency to org.apache.sling.jcr.base
> > > version
> > > 2.4.3-SNAPSHOT in
Hi Robert,
It took me a while to get the trunk to build. I had to disable the
Rat
checks and update the dependency to org.apache.sling.jcr.base
version
2.4.3-SNAPSHOT in org.apache.sling.jcr.oak.server.
Why isn't there a build job anymore for trunk? Should I build Sling
differently than
18 matches
Mail list logo