You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@sling.apache.org by Nicolas Delsaux <ni...@gmail.com> on 2010/03/29 10:15:23 UTC
issue with projects available at http://svn.apache.org/repos/asf/sling/trunk/
hi all,
We're currently trying to evaluate sling and, for that, we downloaded
sources according to
http://sling.apache.org/site/getting-and-building-sling.html and found
various compile issues.
As an example, the maven dependencies for maven-launchpad-plugin are
not correct : apache felix is not declared as a dependency (which
makes use of import org.apache.felix.framework.Logger; not compiling).
As a consequence, we add this dependency in this project's pom like this :
<dependency>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.framework</artifactId>
<version>2.0.4</version>
</dependency>
Besides, there are various compile issues, although we use Eclipse 3.5
with maven 2.2.1 and Java 1.6 (particularly in Scala module), JSP
issues (like undeclared tld at
http://sling.apache.org/taglibs/sling/1.0). Are these issues in
experimental projects ? And if so, is it appropriated to let users use
svn trunk branch as playground ?
Cheers
--
Nicolas Delsaux
Re: issue with projects available at http://svn.apache.org/repos/asf/sling/trunk/
Posted by Nicolas Delsaux <ni...@gmail.com>.
On Mon, Mar 29, 2010 at 3:11 PM, Justin Edelson <ju...@gmail.com> wrote:
> These aren't fatal errors by any stretch of the imagination. The JSP errors
> arise from the fact that Sling's JSP support doesn't follow JavaEE standards
> with respect to TLDs. The web.xml error is trivial to fix (and has been
> fixed in r928763) although it caused no runtime problems as this file is
> ignored by Sling.
>
> Justin
>
Going a little further, i replaced my settings.xml, which used an
enterprise proxy (as sliung seems to use maven-assembly-plugin 2.2
beta 5) and was able to let sling build. unfortunatly, the build ends
due to test errors :
Tests run: 312, Failures: 312, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
I perfectly know I could disable test, but I find rather disturbing to
have all tests failing.
As a consequence, like Bertrand told me, I will use a tagged build
version, for which tests ran successfully.
--
Nicolas Delsaux
Re: issue with projects available at http://svn.apache.org/repos/asf/sling/trunk/
Posted by Justin Edelson <ju...@gmail.com>.
These aren't fatal errors by any stretch of the imagination. The JSP
errors arise from the fact that Sling's JSP support doesn't follow
JavaEE standards with respect to TLDs. The web.xml error is trivial to
fix (and has been fixed in r928763) although it caused no runtime
problems as this file is ignored by Sling.
Justin
Nicolas Delsaux wrote:
> On Mon, Mar 29, 2010 at 11:21 AM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
>
>> Note that launchpad/testing is the core of the overall integration
>> testing, if tests fail in there that's bad news.
>>
>>
> FYI, When I open the tests projects, I get errors in the following projects :
>
> - org.apache.sling.launchpad.contrib-testing
> - org.apache.sling.launchpad.testing
> - org.apache.sling.launchpad.test-services
> - org.apache.sling.launchpad.test-services-war
>
> The errors typically are
>
> Can not find the tag library descriptor for
> "http://sling.apache.org/taglibs/sling/1.0" b-b.jsp /org.apache.sling.launchpad.contrib-testing/src/test/resources/integration-test/issues/sling457 line
> 22 JSP Problem (encountered around 20 times)
>
> I guess the file may have been accidentaly (re)moved, and fixing this
> error would also fix the following one.
>
> currentNode cannot be
> resolved forward-forced.jsp /org.apache.sling.launchpad.contrib-testing/src/test/resources/integration-test line
> 26 JSP Problem (encountered around 20 times)
>
> cvc-attribute.3: The value 'Test Services Webapp' of attribute 'id' on
> element 'web-app' is not valid with respect to its type,
> 'ID'. web.xml /org.apache.sling.launchpad.test-services-war/src/main/webapp/WEB-INF line
> 5 XML Problem
>
> which can easily be fixed by removing all whitespaces characters from
> the id element (notice fixing this error also fix the following one)
>
> cvc-datatype-valid.1.2.1: 'Test Services Webapp' is not a valid value
> for 'NCName'. web.xml /org.apache.sling.launchpad.test-services-war/src/main/webapp/WEB-INF line
> 5 XML Problem
>
>
>
>
Re: issue with projects available at http://svn.apache.org/repos/asf/sling/trunk/
Posted by Nicolas Delsaux <ni...@gmail.com>.
On Mon, Mar 29, 2010 at 11:21 AM, Bertrand Delacretaz
<bd...@apache.org> wrote:
>
> Note that launchpad/testing is the core of the overall integration
> testing, if tests fail in there that's bad news.
>
FYI, When I open the tests projects, I get errors in the following projects :
- org.apache.sling.launchpad.contrib-testing
- org.apache.sling.launchpad.testing
- org.apache.sling.launchpad.test-services
- org.apache.sling.launchpad.test-services-war
The errors typically are
Can not find the tag library descriptor for
"http://sling.apache.org/taglibs/sling/1.0" b-b.jsp /org.apache.sling.launchpad.contrib-testing/src/test/resources/integration-test/issues/sling457 line
22 JSP Problem (encountered around 20 times)
I guess the file may have been accidentaly (re)moved, and fixing this
error would also fix the following one.
currentNode cannot be
resolved forward-forced.jsp /org.apache.sling.launchpad.contrib-testing/src/test/resources/integration-test line
26 JSP Problem (encountered around 20 times)
cvc-attribute.3: The value 'Test Services Webapp' of attribute 'id' on
element 'web-app' is not valid with respect to its type,
'ID'. web.xml /org.apache.sling.launchpad.test-services-war/src/main/webapp/WEB-INF line
5 XML Problem
which can easily be fixed by removing all whitespaces characters from
the id element (notice fixing this error also fix the following one)
cvc-datatype-valid.1.2.1: 'Test Services Webapp' is not a valid value
for 'NCName'. web.xml /org.apache.sling.launchpad.test-services-war/src/main/webapp/WEB-INF line
5 XML Problem
--
Nicolas Delsaux
Re: issue with projects available at http://svn.apache.org/repos/asf/sling/trunk/
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Mar 29, 2010 at 11:16 AM, Nicolas Delsaux
<ni...@gmail.com> wrote:
>> ...The most important/most tested modules are those in the "bundles"
>> folder, the other folders contain extensions/samples/optional
>> components that might not be always stable.
>
> Yeah, i've already closed all the test* projects, as well as the
> *scala* which brings lots of compile issues.
> After having closed all those, there were no more issues....
Note that launchpad/testing is the core of the overall integration
testing, if tests fail in there that's bad news.
-Bertrand
Re: issue with projects available at http://svn.apache.org/repos/asf/sling/trunk/
Posted by Michael Dürig <mi...@day.com>.
> Yeah, i've already closed all the test* projects, as well as the
> *scala* which brings lots of compile issues.
> After having closed all those, there were no more issues.
The Scala scripting modules should build fine with Maven. There is one
integration test for the Scala scripting engine which fails
(org.apache.sling.launchpad.webapp.integrationtest.scala.testIgnore).
This is a know issue.
For importing the Scala modules into Eclipse you need to have the Scala
plugin installed [1]. However, IDE support is somewhat shaky and the
modules might no compile before fixing the project setup manually.
Michael
[1] http://www.scala-lang.org/node/94
Re: issue with projects available at http://svn.apache.org/repos/asf/sling/trunk/
Posted by Nicolas Delsaux <ni...@gmail.com>.
On Mon, Mar 29, 2010 at 11:03 AM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Hi Nicolas,
>
> The trunk is supposed to be stable at all times, but we're not
> religious about it so it can be broken from time to time (and whoever
> broke it should fix it, hint, hint ;-)
Yeah, I know what software development usually is ...
>
> The best way to find out about the latest SVN revision that passed all
> of our tests (which have a reasonably good coverage, at least for the
> core things) is to look at our Hudson continuous integration builds.
>
> Looking at http://hudson.zones.apache.org/hudson/view/Sling/job/sling-trunk-1.6/
> now, for example, shows that the latest build had a number of failed
> tests, but build #348 was all green.
I was ready to tell you to give more visibility to this hudson link,
but saw that it is already mentionned on sling website.
Anyway, I guess the informations provided in this mail would be of
great interest to other sling users.
>
> The most important/most tested modules are those in the "bundles"
> folder, the other folders contain extensions/samples/optional
> components that might not be always stable.
Yeah, i've already closed all the test* projects, as well as the
*scala* which brings lots of compile issues.
After having closed all those, there were no more issues.
>
> Hope this helps - we really should to a launchpad release soon, for
> people like you who want to play with a stable release.
I guess it could be more reassuring to work on so-called "stable"
branches, at least for the on-site demos, even if it would more work
for you when performing a release (since you would have to update some
site pages (but I guess they use a sling instance with some good
"variables").
--
Nicolas Delsaux
Re: issue with projects available at http://svn.apache.org/repos/asf/sling/trunk/
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Nicolas,
On Mon, Mar 29, 2010 at 10:15 AM, Nicolas Delsaux
<ni...@gmail.com> wrote:
> We're currently trying to evaluate sling and, for that, we downloaded
> sources according to
> http://sling.apache.org/site/getting-and-building-sling.html and found
> various compile issues....
> ...Are these issues in
> experimental projects ? And if so, is it appropriated to let users use
> svn trunk branch as playground ?...
The trunk is supposed to be stable at all times, but we're not
religious about it so it can be broken from time to time (and whoever
broke it should fix it, hint, hint ;-)
The best way to find out about the latest SVN revision that passed all
of our tests (which have a reasonably good coverage, at least for the
core things) is to look at our Hudson continuous integration builds.
Looking at http://hudson.zones.apache.org/hudson/view/Sling/job/sling-trunk-1.6/
now, for example, shows that the latest build had a number of failed
tests, but build #348 was all green.
You can then find which SVN revision was used for that build, and use
that for your evaluation. Looking at
http://hudson.zones.apache.org/hudson/view/Sling/job/sling-trunk-1.6/changes
(not sure if there's a better way) will tell you the number of the
last SVN revision created before a given build. For build #348 that's
revision 927092, so if you svn export that revision you should get a
clean build with JDK 1.6 (using Maven at the command-line like Hudson
does).
The most important/most tested modules are those in the "bundles"
folder, the other folders contain extensions/samples/optional
components that might not be always stable.
Hope this helps - we really should to a launchpad release soon, for
people like you who want to play with a stable release.
-Bertrand