Re: [ide] Moving the IDE tools to contrib
In general I think we can move the stuff to trunk as long as it doesn't break the build for everyone, even if the stuff is in flux and might be completely changed over time. We ahve consensus that we want to do this in the Sling project and having it in trunk gives it more visibility and the sooner other people join the effort the better. However, this means we can't use vlt in trunk unless it is in jackrabbit *and* we have a released version of it. I don't want to have a snapshot dependency to an external project. And we have to check with jackrabbit when we can expect a first release. Carsten 2013/7/25 Antonio Sanso asa...@adobe.com On Jul 24, 2013, at 11:33 PM, Robert Munteanu wrote: On Thu, Jul 25, 2013 at 12:12 AM, Antonio Sanso asa...@adobe.com wrote: sorry for misunderstanding but what I really meant is : would it be impossible to have ONLY one API that is agnostic of VLT vs resource based? regards If what you mean is having three bundles * ide-api * resource-impl * vlt-impl and then having the eclipse plugin work with only the ide-api bundle, not knowing what the implementations are, yes I meant that :) regards antonio then I think it is possible. Robert antonio On Jul 24, 2013, at 10:23 PM, Robert Munteanu wrote: On Wed, Jul 24, 2013 at 10:11 PM, Antonio Sanso asa...@adobe.com wrote: just taking a stab here , would it be impossible to have an API that is agnostic of VLT vs resource based? From a technical point of view it's possible, and that's why I tried to separate things into API + implementation. I think that there is a concern that from a support / development effort point of view it makes no sense to support two APIs at the same time. On the long term we should (probably) pick one. But we also need to see which of those has the better IDE embedding story, or at least we'll find out how to drive VLT towards better IDE embeddability. Robert regards antonio On Jul 24, 2013, at 7:54 PM, Robert Munteanu wrote: On Wed, Jul 24, 2013 at 8:44 PM, Justin Edelson jus...@justinedelson.com wrote: +1 to tooling and moving Maven stuff there. -0 to moving IDE out of the whiteboard until we have a consensus on a serialization/transport form. My understanding is that the current IDE codebase is being used to prototype a serialization form and transport protocol and that we will eventually be trying to reach consensus on using that, vlt, or something else. I've waited to propose move out of whiteboard until we had a solid module structure which can be used to evolve the IDE stuff into what we want it to be. The serialization form is more or less a draft which I'm using until FileVault is accepted into Jackrabbit. The transport protocol is based on the Sling HTTP Get/Post servlets, which is a de facto standard for Sling applications, at least for those not using FileVault. The point here is that I don't have vlt to work with _now_ and I can evolve the Eclipse mechanisms ( UI , servers, modules, change detection ) - which are not trivial - without waiting for vlt. And I can gather feedback from people brave enough to try it without waiting for vlt. Once we can use VLT, we'll see what fits best. I admit that I have an inclination towards the resource-based API, but it's not my personal decision to make. Of course, I can put a hold on moving the codebase to trunk/tooling, but that would not gain anything for now, since the codebase is in flux anyway. Instead, my suggestion is not to make any sort of releases, not even technology previews, until we have consensus on the VLT vs Resource-based implementation. WDYT? Robert An alternative would be to create the tooling top-level directory and then put the IDE in a branch. Justin On Wed, Jul 24, 2013 at 10:42 AM, Robert Munteanu rob...@lmn.ro wrote: On Wed, Jul 24, 2013 at 5:15 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wed, Jul 24, 2013 at 4:02 PM, Felix Meschberger fmesc...@adobe.com wrote: ...create a top level tooling (or so) folder and put the ide and maven stuff in there ?... I've created [0] to track this move and will do that later on today - lots of stuff to adjust in the poms under maven. Robert [0]: https://issues.apache.org/jira/browse/SLING-2978 -- Sent from my (old) computer -- Sent from my (old) computer -- Sent from my (old) computer -- Carsten Ziegeler cziege...@apache.org
Re: [ide] Moving the IDE tools to contrib
+1 On Wed, Jul 24, 2013 at 10:42 AM, Robert Munteanu rob...@lmn.ro wrote: On Wed, Jul 24, 2013 at 5:15 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wed, Jul 24, 2013 at 4:02 PM, Felix Meschberger fmesc...@adobe.com wrote: ...create a top level tooling (or so) folder and put the ide and maven stuff in there ?... I've created [0] to track this move and will do that later on today - lots of stuff to adjust in the poms under maven. Robert [0]: https://issues.apache.org/jira/browse/SLING-2978 -- Sent from my (old) computer
[jira] [Commented] (SLING-2666) [Tooling] Checking out resources fails if the DefaultGetServlet does not serve the content
[ https://issues.apache.org/jira/browse/SLING-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719366#comment-13719366 ] Stefan Egli commented on SLING-2666: Hi [~rombert], I like both suggestions, esp the idea to use dedicated servlets for the ide support. I guess a question to ask here though is do we want to take the resource way, the jcr/vault way, or both. I think we need a decision here at some point.. [Tooling] Checking out resources fails if the DefaultGetServlet does not serve the content -- Key: SLING-2666 URL: https://issues.apache.org/jira/browse/SLING-2666 Project: Sling Issue Type: Sub-task Components: Extensions Reporter: Antonio Sanso Assignee: Robert Munteanu see discussion at [0] [0] http://sling.markmail.org/message/rsmysnx6ombk4u4s -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719368#comment-13719368 ] Carsten Ziegeler commented on SLING-2789: - I think we should follow our own conventions, and use 0.1.0-SNAPSHOT and not 0.1.0.BUILD-SNAPSHOT and we shouldn't rely on snapshots of external stuff - as this might break on some machines and causes unnecessary trouble. So once these two things are resolved, we can apply the patch deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.2013-06-04.patch, SLING-2789.2013-07-17.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[ide] VLT vs Resource-based (was: [ide] Moving the IDE tools to contrib)
Hi, On 7/24/13 11:42 PM, Justin Edelson jus...@justinedelson.com wrote: On Wed, Jul 24, 2013 at 1:54 PM, Robert Munteanu rob...@lmn.ro wrote: Once we can use VLT, we'll see what fits best. I admit that I have an inclination towards the resource-based API, but it's not my personal decision to make. I think to make an apples-to-apples comparison, the packaging format and installaion services will also need to be at least defined (better yet would be to have prototypes available). I thought that was the outcome of the prior thread we had on this subject. As I said at that point, the advantage of leveraging VLT is that the existing packaging tool ecosystem would not need to be recreated. Seems still to be a hot topic - VLT vs Resource-based. And I think we should soon get to a decision on this. I think the decision which one to choose is not only related to how well it fits into the IDE, but also related to the impact on the overall picture. Especially given that there is quite some existing packaging ecosystem around, as Justin mentioned. So IMHO if the tooling chooses to go another direction than VLT, that either means that the packaging ecosystem should switch as well - or it ends up not being used by many people. For the short term I dont see a problem having the possibility to play with both - but I think we are in some sort of agreement that in the end result there should only be one way. Cheers, Stefan
[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Attachment: SLING-2789.20130725.patch adjust/update versions deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.2013-06-04.patch, SLING-2789.2013-07-17.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Deleted] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Comment: was deleted (was: adjust/update versions) deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.2013-06-04.patch, SLING-2789.2013-07-17.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Attachment: (was: SLING-2789.20130725.patch) deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.2013-06-04.patch, SLING-2789.2013-07-17.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Attachment: SLING-2789.2013-07-25.patch adjust/update versions deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.2013-06-04.patch, SLING-2789.2013-07-17.patch, SLING-2789.2013-07-25.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Build Failure in Trunk
On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler cziege...@apache.orgwrote: The first error you reported is fixed - now you're running into a new issue which I can't reproduce on my machine. I'm usually doing a full clean build with tests Hi Carsten Sorry for the inconvenience. The initial error I posted was doing the build in inside some sub module (Because the error I am getting when building in parent level is not very descriptive. Hence I went in side the failing module and build it specifically and posted the log.). The latest error log is the one I get when building from parent level. Still I am getting the same when I go inside and build. Carsten 2013/7/25 Dishara Wijewardana ddwijeward...@gmail.com Hi all, Does any body could build the trunk in clean repo with/without tests ? On Thu, Jul 25, 2013 at 6:28 AM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Wed, Jul 24, 2013 at 1:18 PM, Carsten Ziegeler cziege...@apache.org wrote: Should be fixed now This is not yet fixed. I tried both ways. With tests and without tests. My revision is 1506788. I am building from root level. And fails with following. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.506s [INFO] Finished at: Thu Jul 25 06:27:09 IST 2013 [INFO] Final Memory: 89M/975M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test (default-integration-test) on project sling-servlet-archetype: [ERROR] Archetype IT 'normal' failed: Cannot run additions goals. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :sling-servlet-archetype 2013/7/24 Ian Boston i...@tfd.co.uk This looks like an unfixed bug [1], try without disabling tests. Ian 1. https://issues.apache.org/jira/browse/SLING-2804 On 24 July 2013 03:02, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi all, I am building the trunk to build a latest pack to try deploy the implementation. I am seeing following when building the trunk with -Dtest.skip=true. Is this a known issue? [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Sling Servlet Archetype 1.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ sling-servlet-archetype --- [INFO] Deleting /home/dishara/mystuff/sling/svn/sling/maven/archetypes/servlet/target [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ sling-servlet-archetype --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ sling-servlet-archetype --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 6 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ sling-servlet-archetype --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ sling-servlet-archetype --- [INFO] Not copying test resources
[jira] [Commented] (SLING-920) Jenkins continuous integration setup
[
https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719590#comment-13719590
]
Robert Munteanu commented on SLING-920:
---
Updated sling-trunk-{1.6,1.7} to ignore changes on
/repos/asf/sling/trunk/contrib/tooling/ide.* , to prevent triggering builds
which don't include any real changes.
Jenkins continuous integration setup
Key: SLING-920
URL: https://issues.apache.org/jira/browse/SLING-920
Project: Sling
Issue Type: Task
Components: Testing
Reporter: Bertrand Delacretaz
Use this issue to record changes to the Hudson continuous environment setup
at http://hudson.zones.apache.org/hudson/view/Sling/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2978) Create tooling top-level directory and move maven and ide under it
[ https://issues.apache.org/jira/browse/SLING-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719592#comment-13719592 ] Robert Munteanu commented on SLING-2978: Moved the IDE tooling in http://svn.apache.org/viewvc?view=revisionrevision=1506951 Create tooling top-level directory and move maven and ide under it -- Key: SLING-2978 URL: https://issues.apache.org/jira/browse/SLING-2978 Project: Sling Issue Type: Task Components: General Reporter: Robert Munteanu Assignee: Robert Munteanu As discussed at [0], we should create a top-level directory named tooling and * move maven to tooling/maven * move http://svn.apache.org/repos/asf/sling/whiteboard/asanso/plugins/eclipse to tooling/ide [0]: http://markmail.org/thread/cnqjs45h4ovwdzlv -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-920) Jenkins continuous integration setup
[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719599#comment-13719599 ] Robert Munteanu commented on SLING-920: --- Added sling-ide-1.6 job, set to build hourly. Jenkins continuous integration setup Key: SLING-920 URL: https://issues.apache.org/jira/browse/SLING-920 Project: Sling Issue Type: Task Components: Testing Reporter: Bertrand Delacretaz Use this issue to record changes to the Hudson continuous environment setup at http://hudson.zones.apache.org/hudson/view/Sling/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ide] Moving the IDE tools to contrib
Given the discussions, I've moved the codebase from the whiteboard to
tooling/ide. I've created a Sling job at
https://builds.apache.org/view/S-Z/view/Sling/job/sling-ide-1.6/ and
also applied exclusions for tooling/ide when building the
sling-trunk-{1.6,1.7} jobs.
The tooling/ide reactor is not yet part of the default reactor. It's a
good question whether it should be – or rather whether the whole
tooling directory should be part of the default reactor. But that's
another topic.
For now, it builds separately and I'll follow up on different Jira
issues/discussions for incremental improvements.
BTW, should we have a Jira component for it or keep using 'Extensions'
like we did so far?
Thanks,
Robert
On Wed, Jul 24, 2013 at 6:49 PM, Daniel Klco daniel.k...@gmail.com wrote:
+1
On Wed, Jul 24, 2013 at 10:42 AM, Robert Munteanu rob...@lmn.ro wrote:
On Wed, Jul 24, 2013 at 5:15 PM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
On Wed, Jul 24, 2013 at 4:02 PM, Felix Meschberger fmesc...@adobe.com
wrote:
...create a top level tooling (or so) folder and put the ide and
maven stuff in there ?...
I've created [0] to track this move and will do that later on today -
lots of stuff to adjust in the poms under maven.
Robert
[0]: https://issues.apache.org/jira/browse/SLING-2978
--
Sent from my (old) computer
--
Sent from my (old) computer
Re: Build Failure in Trunk
Hi Dishara, mvn clean install worked for me thismorning at On 25 July 2013 13:04, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler cziege...@apache.org wrote: The first error you reported is fixed - now you're running into a new issue which I can't reproduce on my machine. I'm usually doing a full clean build with tests Hi Carsten Sorry for the inconvenience. The initial error I posted was doing the build in inside some sub module (Because the error I am getting when building in parent level is not very descriptive. Hence I went in side the failing module and build it specifically and posted the log.). The latest error log is the one I get when building from parent level. Still I am getting the same when I go inside and build. Carsten 2013/7/25 Dishara Wijewardana ddwijeward...@gmail.com Hi all, Does any body could build the trunk in clean repo with/without tests ? On Thu, Jul 25, 2013 at 6:28 AM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Wed, Jul 24, 2013 at 1:18 PM, Carsten Ziegeler cziege...@apache.org wrote: Should be fixed now This is not yet fixed. I tried both ways. With tests and without tests. My revision is 1506788. I am building from root level. And fails with following. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.506s [INFO] Finished at: Thu Jul 25 06:27:09 IST 2013 [INFO] Final Memory: 89M/975M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test (default-integration-test) on project sling-servlet-archetype: [ERROR] Archetype IT 'normal' failed: Cannot run additions goals. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :sling-servlet-archetype 2013/7/24 Ian Boston i...@tfd.co.uk This looks like an unfixed bug [1], try without disabling tests. Ian 1. https://issues.apache.org/jira/browse/SLING-2804 On 24 July 2013 03:02, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi all, I am building the trunk to build a latest pack to try deploy the implementation. I am seeing following when building the trunk with -Dtest.skip=true. Is this a known issue? [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Sling Servlet Archetype 1.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ sling-servlet-archetype --- [INFO] Deleting /home/dishara/mystuff/sling/svn/sling/maven/archetypes/servlet/target [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ sling-servlet-archetype --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ sling-servlet-archetype --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 6 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ sling-servlet-archetype --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782
[jira] [Resolved] (SLING-2978) Create tooling top-level directory and move maven and ide under it
[ https://issues.apache.org/jira/browse/SLING-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-2978. Resolution: Fixed Create tooling top-level directory and move maven and ide under it -- Key: SLING-2978 URL: https://issues.apache.org/jira/browse/SLING-2978 Project: Sling Issue Type: Task Components: General Reporter: Robert Munteanu Assignee: Robert Munteanu As discussed at [0], we should create a top-level directory named tooling and * move maven to tooling/maven * move http://svn.apache.org/repos/asf/sling/whiteboard/asanso/plugins/eclipse to tooling/ide [0]: http://markmail.org/thread/cnqjs45h4ovwdzlv -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Build Failure in Trunk
On 25 July 2013 14:17, Ian Boston i...@tfd.co.uk wrote: Hi Dishara, mvn clean install worked for me thismorning at oops somehow hit send. at: r1506645 I had to restart the build once because I hit a timeout in an integration test in org.apache.sling.event Ian On 25 July 2013 13:04, Dishara Wijewardana ddwijeward...@gmail.comwrote: On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler cziege...@apache.org wrote: The first error you reported is fixed - now you're running into a new issue which I can't reproduce on my machine. I'm usually doing a full clean build with tests Hi Carsten Sorry for the inconvenience. The initial error I posted was doing the build in inside some sub module (Because the error I am getting when building in parent level is not very descriptive. Hence I went in side the failing module and build it specifically and posted the log.). The latest error log is the one I get when building from parent level. Still I am getting the same when I go inside and build. Carsten 2013/7/25 Dishara Wijewardana ddwijeward...@gmail.com Hi all, Does any body could build the trunk in clean repo with/without tests ? On Thu, Jul 25, 2013 at 6:28 AM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Wed, Jul 24, 2013 at 1:18 PM, Carsten Ziegeler cziege...@apache.org wrote: Should be fixed now This is not yet fixed. I tried both ways. With tests and without tests. My revision is 1506788. I am building from root level. And fails with following. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.506s [INFO] Finished at: Thu Jul 25 06:27:09 IST 2013 [INFO] Final Memory: 89M/975M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test (default-integration-test) on project sling-servlet-archetype: [ERROR] Archetype IT 'normal' failed: Cannot run additions goals. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :sling-servlet-archetype 2013/7/24 Ian Boston i...@tfd.co.uk This looks like an unfixed bug [1], try without disabling tests. Ian 1. https://issues.apache.org/jira/browse/SLING-2804 On 24 July 2013 03:02, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi all, I am building the trunk to build a latest pack to try deploy the implementation. I am seeing following when building the trunk with -Dtest.skip=true. Is this a known issue? [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Sling Servlet Archetype 1.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ sling-servlet-archetype --- [INFO] Deleting /home/dishara/mystuff/sling/svn/sling/maven/archetypes/servlet/target [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ sling-servlet-archetype --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ sling-servlet-archetype --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 6 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ sling-servlet-archetype --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set
Re: Build Failure in Trunk
On Thu, Jul 25, 2013 at 3:04 PM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler cziege...@apache.orgwrote: The first error you reported is fixed - now you're running into a new issue which I can't reproduce on my machine. I'm usually doing a full clean build with tests Hi Carsten Sorry for the inconvenience. The initial error I posted was doing the build in inside some sub module (Because the error I am getting when building in parent level is not very descriptive. Hence I went in side the failing module and build it specifically and posted the log.). The latest error log is the one I get when building from parent level. Still I am getting the same when I go inside and build. 1. Does the build work with -DskipTests for you? 2. Can you paste somewhere ( pastebin, github gist etc ) the full command and build output? Robert Carsten 2013/7/25 Dishara Wijewardana ddwijeward...@gmail.com Hi all, Does any body could build the trunk in clean repo with/without tests ? On Thu, Jul 25, 2013 at 6:28 AM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Wed, Jul 24, 2013 at 1:18 PM, Carsten Ziegeler cziege...@apache.org wrote: Should be fixed now This is not yet fixed. I tried both ways. With tests and without tests. My revision is 1506788. I am building from root level. And fails with following. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.506s [INFO] Finished at: Thu Jul 25 06:27:09 IST 2013 [INFO] Final Memory: 89M/975M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test (default-integration-test) on project sling-servlet-archetype: [ERROR] Archetype IT 'normal' failed: Cannot run additions goals. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :sling-servlet-archetype 2013/7/24 Ian Boston i...@tfd.co.uk This looks like an unfixed bug [1], try without disabling tests. Ian 1. https://issues.apache.org/jira/browse/SLING-2804 On 24 July 2013 03:02, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi all, I am building the trunk to build a latest pack to try deploy the implementation. I am seeing following when building the trunk with -Dtest.skip=true. Is this a known issue? [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Sling Servlet Archetype 1.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ sling-servlet-archetype --- [INFO] Deleting /home/dishara/mystuff/sling/svn/sling/maven/archetypes/servlet/target [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ sling-servlet-archetype --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ sling-servlet-archetype --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 6 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ sling-servlet-archetype --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo]
[jira] [Commented] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719610#comment-13719610 ] Robert Munteanu commented on SLING-2789: I've applied the patch but we still have the BUILD part referenced in snapshots. I've removed them and the build works, but can you double-check the attached diff? deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.2013-06-04.patch, SLING-2789.2013-07-17.patch, SLING-2789.2013-07-25.patch, SLING-2789.patch, SLING-2789-remove-BUILD-from-version.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2789: --- Attachment: SLING-2789-remove-BUILD-from-version.patch deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.2013-06-04.patch, SLING-2789.2013-07-17.patch, SLING-2789.2013-07-25.patch, SLING-2789.patch, SLING-2789-remove-BUILD-from-version.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SLING-2979) Scheduled task should only run on leader
Carsten Ziegeler created SLING-2979: --- Summary: Scheduled task should only run on leader Key: SLING-2979 URL: https://issues.apache.org/jira/browse/SLING-2979 Project: Sling Issue Type: New Feature Components: Commons Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Scheduler 2.3.6 With the new topology api we have support for leader election. In many cases scheduled tasks should only run on a single instance in a cluster. So far this can only be done by manually adding the task through the Scheduler interface but not with the whiteboard support. We should add a new property scheduler.leaderonly which defaults to false but can be set to true. IN this case the task is only started on the leader. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2980) Update to latest quartz scheduler 2.2.0
[ https://issues.apache.org/jira/browse/SLING-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2980. - Resolution: Fixed Update to latest quartz scheduler 2.2.0 --- Key: SLING-2980 URL: https://issues.apache.org/jira/browse/SLING-2980 Project: Sling Issue Type: New Feature Components: Commons Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Scheduler 2.3.6 We could udpate to version 2.2.0 of the quartz library to get the latest version including bug fixes etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2912) Update to latest quartz scheduler 2.1.7
[ https://issues.apache.org/jira/browse/SLING-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2912: Summary: Update to latest quartz scheduler 2.1.7 (was: Update to latest quartz scheduler) Update to latest quartz scheduler 2.1.7 --- Key: SLING-2912 URL: https://issues.apache.org/jira/browse/SLING-2912 Project: Sling Issue Type: Improvement Components: Commons Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Minor Fix For: Commons Scheduler 2.3.6 We're currently embedding quartz scheduler v2.1.1 - which is very old, since then there were several releases with improvements and bug fixes, so I think we should update to the latest v2.1.7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SLING-2980) Update to latest quartz scheduler 2.2.0
Carsten Ziegeler created SLING-2980: --- Summary: Update to latest quartz scheduler 2.2.0 Key: SLING-2980 URL: https://issues.apache.org/jira/browse/SLING-2980 Project: Sling Issue Type: New Feature Components: Commons Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Scheduler 2.3.6 We could udpate to version 2.2.0 of the quartz library to get the latest version including bug fixes etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[
https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-2789:
Attachment: SLING-2789.2013-07-25.a.patch
What do you mean with BUILD part referenced in snapshots?
some more minor tweaks in SLING-2789.2013-07-25.a.patch:
- use ${project.version} in features.xml
- update parent from 16 to 17
- use org.apache.sling/org.apache.sling.jcr.contentloader/2.1.6 (please see
SLING-2917)
deploying Sling 7-SNAPSHOT on Karaf fails
-
Key: SLING-2789
URL: https://issues.apache.org/jira/browse/SLING-2789
Project: Sling
Issue Type: Bug
Components: Launchpad
Affects Versions: Launchpad Builder 7
Environment: Karaf 3.0.0.*
Reporter: Oliver Lietz
Assignee: Carsten Ziegeler
Attachments: SLING-2789.2013-06-04.patch,
SLING-2789.2013-07-17.patch, SLING-2789.2013-07-25.a.patch,
SLING-2789.2013-07-25.patch, SLING-2789.patch,
SLING-2789-remove-BUILD-from-version.patch, sling-launchpad-karaf.tar.gz
$ ./apache-karaf-3.0.0-SNAPSHOT/bin/start
$ ssh -p 8101 karaf@localhost
karaf@root() feature:install http
karaf@root() feature:install webconsole
karaf@root() feature:repo-add
mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features
karaf@root() feature:install sling
no errors on startup but JCR is nearly empty
to prevent errors:
- add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to
features.xml
- remove org.apache.felix/org.apache.felix.webconsole.plugins.* from
features.xml
- remove management from featuresBoot in org.apache.karaf.features.cfg or
remove org.apache.aries.* from features.xml
setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true
does not help
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Testing #1770
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/1770/ -- [...truncated 348 lines...] INFO: Bundle org.apache.sling.scripting.javascript installed from slinginstall:org.apache.sling.scripting.javascript-2.0.12.jar INFO: Bundle org.apache.sling.commons.classloader installed from slinginstall:org.apache.sling.commons.classloader-1.3.0.jar INFO: Bundle org.apache.sling.junit.scriptable installed from slinginstall:org.apache.sling.junit.scriptable-1.0.8.jar INFO: Bundle org.apache.sling.installer.core installed from slinginstall:org.apache.sling.installer.core-3.4.7-SNAPSHOT.jar INFO: Bundle org.apache.sling.launchpad.installer installed from slinginstall:org.apache.sling.launchpad.installer-1.2.0.jar INFO: Bundle org.apache.sling.commons.scheduler installed from slinginstall:org.apache.sling.commons.scheduler-2.3.5-SNAPSHOT.jar INFO: Bundle org.apache.commons.lang installed from slinginstall:commons-lang-2.5.jar INFO: Bundle org.apache.sling.fsresource installed from slinginstall:org.apache.sling.fsresource-1.1.2.jar INFO: Bundle org.apache.sling.auth.core installed from slinginstall:org.apache.sling.auth.core-1.1.3-SNAPSHOT.jar INFO: Bundle org.apache.sling.commons.mime installed from slinginstall:org.apache.sling.commons.mime-2.1.4.jar INFO: Bundle org.apache.commons.codec installed from slinginstall:commons-codec-1.6.jar INFO: Bundle org.apache.sling.scripting.api installed from slinginstall:org.apache.sling.scripting.api-2.1.4.jar INFO: Bundle org.apache.commons.io installed from slinginstall:commons-io-1.4.jar INFO: Bundle org.apache.geronimo.bundles.jstl installed from slinginstall:jstl-1.2_1.jar INFO: Started startup handler with target start level=30, and expected bundle count=108 INFO: Startup progress 1/108 INFO: Startup progress 2/108 INFO: Startup progress 3/108 INFO: Startup progress 4/108 25.07.2013 14:45:10.307 *INFO* [FelixStartLevel] org.mortbay.log Logging to org.apache.sling.commons.log.internal.slf4j.SlingLogger@1998635 via org.mortbay.log.Slf4jLog INFO: Startup progress 4/108 INFO: Startup progress 4/108 INFO: Startup progress 5/108 INFO: Startup progress 5/108 25.07.2013 14:45:10.323 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice Service [org.apache.sling.commons.logservice.internal.LogServiceFactory,8] ServiceEvent REGISTERED 25.07.2013 14:45:10.323 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice Service [org.apache.sling.commons.logservice.internal.LogReaderServiceFactory,9] ServiceEvent REGISTERED 25.07.2013 14:45:10.323 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice BundleEvent STARTED INFO: Startup progress 5/108 25.07.2013 14:45:10.324 *INFO* [FelixStartLevel] org.apache.sling.commons.log BundleEvent STARTING INFO: Startup progress 5/108 INFO: Startup progress 6/108 INFO: Startup progress 6/108 INFO: Startup progress 7/108 INFO: Startup progress 8/108 INFO: Startup progress 9/108 INFO: Startup progress 10/108 INFO: Startup progress 10/108 INFO: Startup progress 11/108 INFO: Startup progress 11/108 INFO: Startup progress 12/108 INFO: Startup progress 12/108 INFO: Startup progress 13/108 INFO: Startup progress 14/108 INFO: Startup progress 14/108 INFO: Startup progress 15/108 INFO: Startup progress 16/108 INFO: Startup progress 17/108 INFO: Startup progress 18/108 INFO: Startup progress 19/108 INFO: Startup progress 19/108 INFO: Startup progress 19/108 INFO: Startup progress 20/108 INFO: Startup progress 20/108 INFO: Startup progress 21/108 INFO: Startup progress 21/108 INFO: Startup progress 22/108 INFO: Startup progress 22/108 INFO: Startup progress 23/108 INFO: Startup progress 24/108 INFO: Startup progress 25/108 INFO: Startup progress 26/108 INFO: Startup progress 27/108 INFO: Startup progress 28/108 INFO: Startup progress 29/108 INFO: Startup progress 30/108 INFO: Startup progress 31/108 INFO: Startup progress 32/108 INFO: Startup progress 32/108 INFO: Startup progress 33/108 INFO: Startup progress 33/108 INFO: Startup progress 34/108 INFO: Startup progress 34/108 INFO: Startup progress 34/108 INFO: Startup progress 35/108 INFO: Startup progress 36/108 INFO: Startup progress 37/108 INFO: Startup progress 37/108 INFO: Startup progress 38/108 INFO: Startup progress 38/108 INFO: Startup progress 39/108 INFO: Startup progress 40/108 INFO: Startup progress 40/108 INFO: Startup progress 40/108 INFO: Startup progress 41/108 INFO: Startup progress 41/108 INFO: Startup progress 41/108 INFO: Startup progress 42/108 INFO: Startup progress 42/108 INFO: Startup progress 42/108 INFO: Startup progress 43/108 INFO: Startup progress 43/108 INFO: Startup progress 43/108 INFO: Startup progress 43/108 INFO: Startup progress 43/108 INFO: Startup progress 44/108 INFO: Startup progress 45/108 INFO: Startup progress 46/108 INFO: Startup progress 46/108 INFO: Startup progress 46/108 INFO: Startup progress 47/108 INFO: Startup progress 47/108
Build failed in Jenkins: sling-trunk-1.6 #1770
See https://builds.apache.org/job/sling-trunk-1.6/1770/changes Changes: [cziegeler] SLING-2980 : Update to latest quartz scheduler 2.2.0 [cziegeler] Remove unused configuration property [rombert] SLING-2978 - Create tooling top-level directory and move maven and ide under it Moved the current IDE tooling from whiteboard/asanso to trunk/tooling/ide. -- [...truncated 32817 lines...] INFO: Startup progress 89/108 INFO: Startup progress 89/108 ERROR: Bundle org.apache.sling.event [80] Error starting slinginstall:org.apache.sling.event-3.1.5-SNAPSHOT.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.sling.event [80]: Unable to resolve 80.0: missing requirement [80.0] osgi.wiring.package; ((osgi.wiring.package=org.apache.sling.commons.scheduler)(version=2.1.0)(!(version=3.0.0))) [caused by: Unable to resolve 99.0: missing requirement [99.0] osgi.wiring.package; (osgi.wiring.package=commonj.work)]) org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.sling.event [80]: Unable to resolve 80.0: missing requirement [80.0] osgi.wiring.package; ((osgi.wiring.package=org.apache.sling.commons.scheduler)(version=2.1.0)(!(version=3.0.0))) [caused by: Unable to resolve 99.0: missing requirement [99.0] osgi.wiring.package; (osgi.wiring.package=commonj.work)] at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3962) at org.apache.felix.framework.Felix.startBundle(Felix.java:2025) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1279) at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304) at java.lang.Thread.run(Thread.java:662) INFO: Startup progress 90/108 INFO: Startup progress 90/108 INFO: Startup progress 91/108 INFO: Startup progress 91/108 INFO: Startup progress 91/108 INFO: Startup progress 92/108 INFO: Startup progress 92/108 INFO: Startup progress 93/108 INFO: Startup progress 94/108 INFO: Startup progress 94/108 INFO: Startup progress 94/108 INFO: Startup progress 94/108 INFO: Startup progress 94/108 INFO: Startup progress 94/108 INFO: Startup progress 94/108 INFO: Startup progress 94/108 INFO: Startup progress 95/108 INFO: Startup progress 95/108 INFO: Startup progress 96/108 INFO: Startup progress 96/108 INFO: Startup progress 97/108 INFO: Startup progress 97/108 INFO: Startup progress 97/108 INFO: Startup progress 98/108 INFO: Startup progress 98/108 INFO: Startup progress 98/108 INFO: Startup progress 99/108 [WARNING] un-handlable path resources [WARNING] un-handlable path resources/config/integrationTestsConfig.cfg [WARNING] un-handlable path resources/install ERROR: Bundle org.apache.sling.commons.scheduler [99] Error starting slinginstall:org.apache.sling.commons.scheduler-2.3.5-SNAPSHOT.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.sling.commons.scheduler [99]: Unable to resolve 99.0: missing requirement [99.0] osgi.wiring.package; (osgi.wiring.package=commonj.work)) org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.sling.commons.scheduler [99]: Unable to resolve 99.0: missing requirement [99.0] osgi.wiring.package; (osgi.wiring.package=commonj.work) at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3962) at org.apache.felix.framework.Felix.startBundle(Felix.java:2025) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1279) at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304) at java.lang.Thread.run(Thread.java:662) INFO: Startup progress 99/108 INFO: Startup progress 99/108 INFO: Startup progress 100/108 INFO: Startup progress 100/108 INFO: Startup progress 100/108 INFO: Startup progress 100/108 INFO: Startup progress 100/108 INFO: Startup progress 100/108 INFO: Startup progress 100/108 INFO: Startup progress 101/108 INFO: Apache Sling started INFO: Startup progress 101/108 INFO: Startup progress 102/108 INFO: Startup finished. [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS]
Re: Build Failure in Trunk
Still getting the same error. 1. Command is mvn clean install -DskipTests. 2. Please find the link [1] for the pastebin build log. [1] - http://pastebin.com/12x8F4UG On Thu, Jul 25, 2013 at 6:53 PM, Robert Munteanu rob...@lmn.ro wrote: On Thu, Jul 25, 2013 at 3:04 PM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler cziege...@apache.org wrote: The first error you reported is fixed - now you're running into a new issue which I can't reproduce on my machine. I'm usually doing a full clean build with tests Hi Carsten Sorry for the inconvenience. The initial error I posted was doing the build in inside some sub module (Because the error I am getting when building in parent level is not very descriptive. Hence I went in side the failing module and build it specifically and posted the log.). The latest error log is the one I get when building from parent level. Still I am getting the same when I go inside and build. 1. Does the build work with -DskipTests for you? 2. Can you paste somewhere ( pastebin, github gist etc ) the full command and build output? Robert Carsten 2013/7/25 Dishara Wijewardana ddwijeward...@gmail.com Hi all, Does any body could build the trunk in clean repo with/without tests ? On Thu, Jul 25, 2013 at 6:28 AM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Wed, Jul 24, 2013 at 1:18 PM, Carsten Ziegeler cziege...@apache.org wrote: Should be fixed now This is not yet fixed. I tried both ways. With tests and without tests. My revision is 1506788. I am building from root level. And fails with following. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.506s [INFO] Finished at: Thu Jul 25 06:27:09 IST 2013 [INFO] Final Memory: 89M/975M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test (default-integration-test) on project sling-servlet-archetype: [ERROR] Archetype IT 'normal' failed: Cannot run additions goals. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :sling-servlet-archetype 2013/7/24 Ian Boston i...@tfd.co.uk This looks like an unfixed bug [1], try without disabling tests. Ian 1. https://issues.apache.org/jira/browse/SLING-2804 On 24 July 2013 03:02, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi all, I am building the trunk to build a latest pack to try deploy the implementation. I am seeing following when building the trunk with -Dtest.skip=true. Is this a known issue? [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Sling Servlet Archetype 1.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ sling-servlet-archetype --- [INFO] Deleting /home/dishara/mystuff/sling/svn/sling/maven/archetypes/servlet/target [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ sling-servlet-archetype --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ sling-servlet-archetype --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 6 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ sling-servlet-archetype --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782)
Re: Build Failure in Trunk
Hi all, I checked out the trunk code to a new location and removed my existing M2 repository and do a mvn clean install. Still fails in same place. So I believe this should fail in clean repo. I am compiling this code in 1.6 JDK in Ubuntu 11.10. These are the only facts left for me to compare with if this is local to me. On Fri, Jul 26, 2013 at 6:30 AM, Dishara Wijewardana ddwijeward...@gmail.com wrote: Still getting the same error. 1. Command is mvn clean install -DskipTests. 2. Please find the link [1] for the pastebin build log. [1] - http://pastebin.com/12x8F4UG On Thu, Jul 25, 2013 at 6:53 PM, Robert Munteanu rob...@lmn.ro wrote: On Thu, Jul 25, 2013 at 3:04 PM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler cziege...@apache.orgwrote: The first error you reported is fixed - now you're running into a new issue which I can't reproduce on my machine. I'm usually doing a full clean build with tests Hi Carsten Sorry for the inconvenience. The initial error I posted was doing the build in inside some sub module (Because the error I am getting when building in parent level is not very descriptive. Hence I went in side the failing module and build it specifically and posted the log.). The latest error log is the one I get when building from parent level. Still I am getting the same when I go inside and build. 1. Does the build work with -DskipTests for you? 2. Can you paste somewhere ( pastebin, github gist etc ) the full command and build output? Robert Carsten 2013/7/25 Dishara Wijewardana ddwijeward...@gmail.com Hi all, Does any body could build the trunk in clean repo with/without tests ? On Thu, Jul 25, 2013 at 6:28 AM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Wed, Jul 24, 2013 at 1:18 PM, Carsten Ziegeler cziege...@apache.org wrote: Should be fixed now This is not yet fixed. I tried both ways. With tests and without tests. My revision is 1506788. I am building from root level. And fails with following. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.506s [INFO] Finished at: Thu Jul 25 06:27:09 IST 2013 [INFO] Final Memory: 89M/975M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:integration-test (default-integration-test) on project sling-servlet-archetype: [ERROR] Archetype IT 'normal' failed: Cannot run additions goals. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :sling-servlet-archetype 2013/7/24 Ian Boston i...@tfd.co.uk This looks like an unfixed bug [1], try without disabling tests. Ian 1. https://issues.apache.org/jira/browse/SLING-2804 On 24 July 2013 03:02, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi all, I am building the trunk to build a latest pack to try deploy the implementation. I am seeing following when building the trunk with -Dtest.skip=true. Is this a known issue? [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Sling Servlet Archetype 1.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ sling-servlet-archetype --- [INFO] Deleting /home/dishara/mystuff/sling/svn/sling/maven/archetypes/servlet/target [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ sling-servlet-archetype --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ sling-servlet-archetype --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ sling-servlet-archetype --- [INFO] [INFO] ---
