Re: [VOTE RESULT] Release Apache Sling 5
Hi, Ian Boston schrieb: Sorry to be a pain, ;-) Sling 5 appears to be binding to Web Console 1.2.8 and so has [1], the fix for which has not been released. (fix reported as being in 1.2.10) Do you want to release with the web console configuration unusable? It makes sling a bit harder to configure. I, suggest we continue releasing with what we have. Re WebConsole, there a small number of open issues for WebConsole, I would like to consider before deciding on 1.2.10. I know the NPE issue is a tough one and will strongly influence the decision. Anyway, as soon as 1.2.10 has been released, it will also be available from the OBR and as such installable through the web console. Hope this helps. Regards Felix We(sakai) can easily bind to a snapshot of webconsole, but others might get a bit confused at first. Could be a known issue I guess. Ian [1] https://issues.apache.org/jira/browse/FELIX-1135 On 9 May 2009, at 18:22, Carsten Ziegeler wrote: The vote to release Apache Sling 5 finished successfully with six +1 votes from: - Felix Meschberger (*) - Jukka Zitting (*) - Juan José Vázquez Delgado (*) - Vidar Ramdal (*) - Carsten Ziegeler (*) - Bertrand Delacretaz (*) The people marked with * are members of the PPMC No other votes were cast. Thanks for taking the time to check the release! Regards Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] Created: (SLING-958) Provide Aggregate JavaDoc for the latest Sling Source Release 5
Provide Aggregate JavaDoc for the latest Sling Source Release 5 --- Key: SLING-958 URL: https://issues.apache.org/jira/browse/SLING-958 Project: Sling Issue Type: Task Components: General Reporter: Felix Meschberger Assignee: Felix Meschberger Now that the Sling 5 release is coming close to an official release -- Sling project vote has succeeded, pending Incubator PMC approval -- the aggegrate JavaDoc of the public API of Sling 5 should also be published to the site. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-958) Provide Aggregate JavaDoc for the latest Sling Source Release 5
[ https://issues.apache.org/jira/browse/SLING-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12707922#action_12707922 ] Felix Meschberger commented on SLING-958: - Committed the generated apidocs to our site SVN at Rev. 773487 and updated the site base on people.a.o. The Sling 5 API docs have been generated as follows: $ svn export http://svn.apache.org/repos/asf/incubator/sling/tags/sling-5-incubator-source-release/ sling5 $ # Fix root pom.xml (see below) $ cd sling5 $ mvn -DexcludePackageNames=*.impl:*.internal:*.jsp:sun.misc:*.juli org.apache.maven.plugins:maven-javadoc-plugin:2.5:aggregate Provide Aggregate JavaDoc for the latest Sling Source Release 5 --- Key: SLING-958 URL: https://issues.apache.org/jira/browse/SLING-958 Project: Sling Issue Type: Task Components: General Reporter: Felix Meschberger Assignee: Felix Meschberger Now that the Sling 5 release is coming close to an official release -- Sling project vote has succeeded, pending Incubator PMC approval -- the aggegrate JavaDoc of the public API of Sling 5 should also be published to the site. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-958) Provide Aggregate JavaDoc for the latest Sling Source Release 5
[ https://issues.apache.org/jira/browse/SLING-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-958. --- Resolution: Fixed Linked the API docs from the main navigation which completes this task for now. Provide Aggregate JavaDoc for the latest Sling Source Release 5 --- Key: SLING-958 URL: https://issues.apache.org/jira/browse/SLING-958 Project: Sling Issue Type: Task Components: General Reporter: Felix Meschberger Assignee: Felix Meschberger Now that the Sling 5 release is coming close to an official release -- Sling project vote has succeeded, pending Incubator PMC approval -- the aggegrate JavaDoc of the public API of Sling 5 should also be published to the site. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Sling 5 API Docs
Hi all, Now that the Sling release is approaching official status (pending Incubator PMC approval) I also published the aggregate API JavaDoc for this Sling 5 Source Release at [1] (Please allow for a few hours for the site to sync). I also linked to the API docs from the main navigation of the Site. Regards Felix [1] http://incubator.apache.org/sling/apidocs/sling5/index.html
Re: [CONF] Apache Sling: Incubator Status Report (May 2009) (page edited)
Hi Felix, On Sat, May 9, 2009 at 10:14 PM, Felix Meschberger fmesc...@gmail.com wrote: ...Usually I copy it there just before the reporting deadline and mark the one here as read-only ... Ok, sorry about that. Copied the report back and made it read-only. -Bertrand conflue...@apache.org schrieb: Page Edited : SLING http://cwiki.apache.org/confluence/display/SLING : Incubator Status Report (May 2009) http://cwiki.apache.org/confluence/display/SLING/Incubator+Status+Report+%28May+2009%29 Incubator Status Report (May 2009) http://cwiki.apache.org/confluence/display/SLING/Incubator+Status+Report+%28May+2009%29 has been edited by Bertrand Delacretaz http://cwiki.apache.org/confluence/display/~bdelacretaz (May 08, 2009). (View changes) http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=116778originalVersion=4revisedVersion=5 Content: Report moved to http://wiki.apache.org/incubator/May2009^ Powered by Atlassian Confluence http://www.atlassian.com/software/confluence/default.jsp?clicked=footer (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request http://jira.atlassian.com/secure/BrowseProject.jspa?id=10470 Unsubscribe or edit your notifications preferences http://cwiki.apache.org/confluence/users/viewnotifications.action
Re: [VOTE RESULT] Release Apache Sling 5
Ok, no problem, I am binding to webconsole 1.2.9-SNAPSHOT from trunk at the moment. We will track the Felix trunk until there is a release of 1.2.10, and then revert back to the Sling release presumably at 2.0.8 (assuming even subminor == release) Thanks for your help and the pointers. Ian On 11 May 2009, at 07:04, Felix Meschberger wrote: Hi, Ian Boston schrieb: Sorry to be a pain, ;-) Sling 5 appears to be binding to Web Console 1.2.8 and so has [1], the fix for which has not been released. (fix reported as being in 1.2.10) Do you want to release with the web console configuration unusable? It makes sling a bit harder to configure. I, suggest we continue releasing with what we have. Re WebConsole, there a small number of open issues for WebConsole, I would like to consider before deciding on 1.2.10. I know the NPE issue is a tough one and will strongly influence the decision. Anyway, as soon as 1.2.10 has been released, it will also be available from the OBR and as such installable through the web console. Hope this helps. Regards Felix We(sakai) can easily bind to a snapshot of webconsole, but others might get a bit confused at first. Could be a known issue I guess. Ian [1] https://issues.apache.org/jira/browse/FELIX-1135 On 9 May 2009, at 18:22, Carsten Ziegeler wrote: The vote to release Apache Sling 5 finished successfully with six +1 votes from: - Felix Meschberger (*) - Jukka Zitting (*) - Juan José Vázquez Delgado (*) - Vidar Ramdal (*) - Carsten Ziegeler (*) - Bertrand Delacretaz (*) The people marked with * are members of the PPMC No other votes were cast. Thanks for taking the time to check the release! Regards Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] Created: (SLING-959) NPE in webconsole/config
NPE in webconsole/config Key: SLING-959 URL: https://issues.apache.org/jira/browse/SLING-959 Project: Sling Issue Type: Bug Components: Console Reporter: Bertrand Delacretaz The Sling 5 release uses the Felix webconsole 1.2.8, which throws an NPE when accessing system/console/configMgr The root cause is FELIX-1028 The current workaround is to use a trunk build of the Felix webconsole - using the broken webconsole that's present in Sling 5 to update to that should work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-960) Need webconsole smoke tests
Need webconsole smoke tests Key: SLING-960 URL: https://issues.apache.org/jira/browse/SLING-960 Project: Sling Issue Type: Test Components: Console Reporter: Bertrand Delacretaz Priority: Minor SLING-959 wasn't detected by our test suite, we should add some simple webconsole integration testing to catch such problems in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Vote] Release Apache Sling 5 - webconsole config is broken
Hi, On Fri, May 8, 2009 at 6:14 PM, Ian Boston i...@tfd.co.uk wrote: I am seeing the following running the standalone launchpad with a clean build of the sling-5-incubator-source-release tag, (and a clear local repo for both o.a.sling and o.a.felix) should it be happening ? HTTP ERROR 500 ... java.lang.NullPointerException: Filter cannot be null at org.apache.felix.framework.FilterImpl.(FilterImpl.java:59)... Although there will soon be a workaround, having that in the release is ugly. And the fact that we missed it also indicates that something's missing in our release testing process - I have created SLING-960 about that. For now I have created SLING-959 - what do people think of releasing with that ugly bug? I know recutting and revoting on the release is a pain, so we might want to go ahead, as long as we document known issues with this release. Maybe a link to a JIRA query from http://incubator.apache.org/sling/site/downloads.cgi would be good, to display know issues in the current release and point to workarounds? -Bertrand
Re: [Vote] Release Apache Sling 5 - webconsole config is broken
Hi, On Mon, May 11, 2009 at 11:26 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: For now I have created SLING-959 - what do people think of releasing with that ugly bug? I know recutting and revoting on the release is a pain, so we might want to go ahead, as long as we document known issues with this release. There'll never be a perfect release and in many cases having even a buggy release with known workarounds is much better than having no release at all. So I say we shouldn't cancel this release because of this issue. We can always create a new release as soon as the problem is solved. Release often! BR, Jukka Zitting
Re: [Vote] Release Apache Sling 5 - webconsole config is broken
Hi, Jukka Zitting schrieb: Hi, On Mon, May 11, 2009 at 11:26 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: For now I have created SLING-959 - what do people think of releasing with that ugly bug? I know recutting and revoting on the release is a pain, so we might want to go ahead, as long as we document known issues with this release. There'll never be a perfect release and in many cases having even a buggy release with known workarounds is much better than having no release at all. So I say we shouldn't cancel this release because of this issue. We can always create a new release as soon as the problem is solved. Release often! +1 Regards Felix
Re: [Vote] Release Apache Sling 5 - webconsole config is broken
+1 On Mon, May 11, 2009 at 11:40 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Mon, May 11, 2009 at 11:26 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: For now I have created SLING-959 - what do people think of releasing with that ugly bug? I know recutting and revoting on the release is a pain, so we might want to go ahead, as long as we document known issues with this release. There'll never be a perfect release and in many cases having even a buggy release with known workarounds is much better than having no release at all. So I say we shouldn't cancel this release because of this issue. We can always create a new release as soon as the problem is solved. Release often! BR, Jukka Zitting
[jira] Updated: (SLING-959) NPE in webconsole/config
[ https://issues.apache.org/jira/browse/SLING-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Boston updated SLING-959: - Attachment: org.apache.felix.webconsole-1.2.9-SNAPSHOT.jar This is a known good snapshot of the web console. If you replace the 1.2.8 version of web console that comes with the Sling 5 release, the configuartion screen will work. However, this *might* introduce other problems as its a SNAPSHOT jar. This was built from trunk Felix NPE in webconsole/config Key: SLING-959 URL: https://issues.apache.org/jira/browse/SLING-959 Project: Sling Issue Type: Bug Components: Console Reporter: Bertrand Delacretaz Attachments: org.apache.felix.webconsole-1.2.9-SNAPSHOT.jar The Sling 5 release uses the Felix webconsole 1.2.8, which throws an NPE when accessing system/console/configMgr The root cause is FELIX-1028 The current workaround is to use a trunk build of the Felix webconsole - using the broken webconsole that's present in Sling 5 to update to that should work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-960) Need webconsole smoke tests
[ https://issues.apache.org/jira/browse/SLING-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12707987#action_12707987 ] Carsten Ziegeler commented on SLING-960: I don't want to prevent anyone from doing additional tests, but I think this is not the core business of Sling - the web console is just one way of managing an OSGi installation; and more important the web console is developed at another problem, so I can imagine it will be hard to keep track of changes and adjust the tests accordingly. Just my 2 cents, but if someone wants to add tests, welcome! Need webconsole smoke tests Key: SLING-960 URL: https://issues.apache.org/jira/browse/SLING-960 Project: Sling Issue Type: Test Components: Console Reporter: Bertrand Delacretaz Priority: Minor SLING-959 wasn't detected by our test suite, we should add some simple webconsole integration testing to catch such problems in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-960) Need webconsole smoke tests
[ https://issues.apache.org/jira/browse/SLING-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12707996#action_12707996 ] Bertrand Delacretaz commented on SLING-960: --- I agree that it's not our business to test the webconsole itself, but when everybody votes +1 on a release without noticing that something as basic as the config console is broken, we have a problem. Those tests could manual tests part of a release test procedure document on the wiki, they don't necessarily need to be automated. Or we might contribute tests to the Felix project. Need webconsole smoke tests Key: SLING-960 URL: https://issues.apache.org/jira/browse/SLING-960 Project: Sling Issue Type: Test Components: Console Reporter: Bertrand Delacretaz Priority: Minor SLING-959 wasn't detected by our test suite, we should add some simple webconsole integration testing to catch such problems in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-960) Need webconsole smoke tests
[ https://issues.apache.org/jira/browse/SLING-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708017#action_12708017 ] Carsten Ziegeler commented on SLING-960: Non-automated tests tend to be forgotten during the release process; and I still think this is not a blocker for a Sling release. Contributing the tests to the Felix project might make sense; however in this particular case, the problem arises because of a specific Felix version and a specifc web console version; other combinations work. Need webconsole smoke tests Key: SLING-960 URL: https://issues.apache.org/jira/browse/SLING-960 Project: Sling Issue Type: Test Components: Console Reporter: Bertrand Delacretaz Priority: Minor SLING-959 wasn't detected by our test suite, we should add some simple webconsole integration testing to catch such problems in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-960) Need webconsole smoke tests
[ https://issues.apache.org/jira/browse/SLING-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708033#action_12708033 ] John Norman commented on SLING-960: --- I am really qualified to comment, but I manage a non-Java-developer resource who was blocked from making progress on a UX project in front of Sling because he was relying on part of the web console to map a folder on his hard drive to a Jackrabbit URL space. I agree that with the workaround, it may not be a blocker. But without the workaround I think it could be considered a blocker from a Sling-user point of view... Need webconsole smoke tests Key: SLING-960 URL: https://issues.apache.org/jira/browse/SLING-960 Project: Sling Issue Type: Test Components: Console Reporter: Bertrand Delacretaz Priority: Minor SLING-959 wasn't detected by our test suite, we should add some simple webconsole integration testing to catch such problems in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-960) Need webconsole smoke tests
[ https://issues.apache.org/jira/browse/SLING-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708043#action_12708043 ] Carsten Ziegeler commented on SLING-960: Hmm, yes, but we are currently trying to get a big bang release from Sling out of the doors. Once this is through we can easily and quickly release single modules like the launchpad stuff. Need webconsole smoke tests Key: SLING-960 URL: https://issues.apache.org/jira/browse/SLING-960 Project: Sling Issue Type: Test Components: Console Reporter: Bertrand Delacretaz Priority: Minor SLING-959 wasn't detected by our test suite, we should add some simple webconsole integration testing to catch such problems in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-960) Need webconsole smoke tests
[ https://issues.apache.org/jira/browse/SLING-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708055#action_12708055 ] John Norman commented on SLING-960: --- That would be great :-) Need webconsole smoke tests Key: SLING-960 URL: https://issues.apache.org/jira/browse/SLING-960 Project: Sling Issue Type: Test Components: Console Reporter: Bertrand Delacretaz Priority: Minor SLING-959 wasn't detected by our test suite, we should add some simple webconsole integration testing to catch such problems in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Web Console broken (was: [VOTE RESULT] Release Apache Sling 5)
Hi all, Just FYI: I just started a release vote for the Web Console 1.2.10 over in the Apache Felix project. Once through, you may upgrade to that version, which includes the configuration fix. Regards Felix Ian Boston schrieb: Ok, no problem, I am binding to webconsole 1.2.9-SNAPSHOT from trunk at the moment. We will track the Felix trunk until there is a release of 1.2.10, and then revert back to the Sling release presumably at 2.0.8 (assuming even subminor == release) Thanks for your help and the pointers. Ian On 11 May 2009, at 07:04, Felix Meschberger wrote: Hi, Ian Boston schrieb: Sorry to be a pain, ;-) Sling 5 appears to be binding to Web Console 1.2.8 and so has [1], the fix for which has not been released. (fix reported as being in 1.2.10) Do you want to release with the web console configuration unusable? It makes sling a bit harder to configure. I, suggest we continue releasing with what we have. Re WebConsole, there a small number of open issues for WebConsole, I would like to consider before deciding on 1.2.10. I know the NPE issue is a tough one and will strongly influence the decision. Anyway, as soon as 1.2.10 has been released, it will also be available from the OBR and as such installable through the web console. Hope this helps. Regards Felix We(sakai) can easily bind to a snapshot of webconsole, but others might get a bit confused at first. Could be a known issue I guess. Ian [1] https://issues.apache.org/jira/browse/FELIX-1135 On 9 May 2009, at 18:22, Carsten Ziegeler wrote: The vote to release Apache Sling 5 finished successfully with six +1 votes from: - Felix Meschberger (*) - Jukka Zitting (*) - Juan José Vázquez Delgado (*) - Vidar Ramdal (*) - Carsten Ziegeler (*) - Bertrand Delacretaz (*) The people marked with * are members of the PPMC No other votes were cast. Thanks for taking the time to check the release! Regards Carsten -- Carsten Ziegeler cziege...@apache.org
Re: Sling 5 API Docs
Felix Meschberger wrote: Hi all, Now that the Sling release is approaching official status (pending Incubator PMC approval) I also published the aggregate API JavaDoc for this Sling 5 Source Release at [1] (Please allow for a few hours for the site to sync). I also linked to the API docs from the main navigation of the Site. Regards Felix [1] http://incubator.apache.org/sling/apidocs/sling5/index.html Can we later on have a tarball with the docs for download? Carsten -- Carsten Ziegeler cziege...@apache.org
Releases in the future
Hi all, Carsten and I have been reasoning about the releases in the future, mainly the ones for end-users who just want to grab a binary and fire it off. Basically, we will start releasing single bundles using the regular ASF release process. This should enable us to release much quicker than with big release we have done until now. For the consumer releases we are talking about 4 projects mainly: * launchpad/base - contains the launcher code, Felix framework and the OSGi core and compendium libraries. * launchpad/bundles - a very simple project to just pack together existing bundles * launchpad/app, launchpad/webapp - projects to create final app and web app from the base and bundles projects So to release a consumer product we update the launchpad/bundles project with all the bundles we want to include and prepare the releases of the launchpad/bundles, launchpad/app and launchpad/webapp projects. I know this is kind of weird in the Apache World, but in essence these releases are not mainly targeted at developers and manual builders but at consumers, who just want to grab-and-run it. WDYT ? Regards Felix
Re: Releases in the future
Roy T. Fielding wrote: On May 11, 2009, at 12:03 PM, Felix Meschberger wrote: Carsten and I have been reasoning about the releases in the future, mainly the ones for end-users who just want to grab a binary and fire it off. Basically, we will start releasing single bundles using the regular ASF release process. This should enable us to release much quicker than with big release we have done until now. For the consumer releases we are talking about 4 projects mainly: * launchpad/base - contains the launcher code, Felix framework and the OSGi core and compendium libraries. * launchpad/bundles - a very simple project to just pack together existing bundles * launchpad/app, launchpad/webapp - projects to create final app and web app from the base and bundles projects So to release a consumer product we update the launchpad/bundles project with all the bundles we want to include and prepare the releases of the launchpad/bundles, launchpad/app and launchpad/webapp projects. I know this is kind of weird in the Apache World, but in essence these releases are not mainly targeted at developers and manual builders but at consumers, who just want to grab-and-run it. WDYT ? Apache only releases source code packages. Those other things you build are not releases -- they are binaries that individuals build and upload. Yes, that's right - now, we think that even for those things voting etc. is a good thing. While legaly everything might be correct, but I don't think that users are really able (or willing) to distinguish between a release (source) and a downloadable binary. So it makes sense that those binaries are checked and handled properly as well. Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] Updated: (SLING-962) Unused imports and missing serialVersionUID
[ https://issues.apache.org/jira/browse/SLING-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Boston updated SLING-962: - Description: There are some weird imports in http auth including java.awt, all unused patch to follow. was: There are some weird imports in http auth including java.awt, all unsed patch to follow. Unused imports and missing serialVersionUID Key: SLING-962 URL: https://issues.apache.org/jira/browse/SLING-962 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Extensions httpauth 2.0.4 Reporter: Ian Boston There are some weird imports in http auth including java.awt, all unused patch to follow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-962) Unused imports and missing serialVersionUID
Unused imports and missing serialVersionUID Key: SLING-962 URL: https://issues.apache.org/jira/browse/SLING-962 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Extensions httpauth 2.0.4 Reporter: Ian Boston There are some weird imports in http auth including java.awt, all unsed patch to follow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-961) Parent pom should not include org.osgi.foundation artifact to allow compiling in eclipse
[ https://issues.apache.org/jira/browse/SLING-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-961: - Attachment: parent_patch_090512.patch Parent pom should not include org.osgi.foundation artifact to allow compiling in eclipse Key: SLING-961 URL: https://issues.apache.org/jira/browse/SLING-961 Project: Sling Issue Type: Bug Components: General Affects Versions: Parent 5 Reporter: Stefan Seifert Attachments: parent_patch_090512.patch the artifact org.osgi.compendium 1.2.0 includes another artifact org.osgi.foundation as dependency, which contains several classes included in current JDK release, but as non-generic versions. this prevents compiling most eclipse projects in the current project. the org.osgi.foundation transitive dependency should be excluded in parent pom to prevent this - sling is compiling happily without out. patch attached. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-961) Parent pom should not include org.osgi.foundation artifact to allow compiling in eclipse
Parent pom should not include org.osgi.foundation artifact to allow compiling in eclipse Key: SLING-961 URL: https://issues.apache.org/jira/browse/SLING-961 Project: Sling Issue Type: Bug Components: General Affects Versions: Parent 5 Reporter: Stefan Seifert Attachments: parent_patch_090512.patch the artifact org.osgi.compendium 1.2.0 includes another artifact org.osgi.foundation as dependency, which contains several classes included in current JDK release, but as non-generic versions. this prevents compiling most eclipse projects in the current project. the org.osgi.foundation transitive dependency should be excluded in parent pom to prevent this - sling is compiling happily without out. patch attached. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-962) Unused imports and missing serialVersionUID
[ https://issues.apache.org/jira/browse/SLING-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Boston updated SLING-962: - Attachment: SLING-962.patch Unused imports and missing serialVersionUID Key: SLING-962 URL: https://issues.apache.org/jira/browse/SLING-962 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Extensions httpauth 2.0.4 Reporter: Ian Boston Attachments: SLING-962.patch There are some weird imports in http auth including java.awt, all unused patch to follow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-961) Parent pom should not include org.osgi.foundation artifact to allow compiling in eclipse
[ https://issues.apache.org/jira/browse/SLING-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-961: - Description: the artifact org.osgi.compendium 1.2.0 includes another artifact org.osgi.foundation as dependency, which contains several classes included in current JDK release, but as non-generic versions. this prevents compiling most sling projects in trunk in eclipse. the org.osgi.foundation transitive dependency should be excluded in parent pom to prevent this - sling is compiling happily without it. patch attached. was: the artifact org.osgi.compendium 1.2.0 includes another artifact org.osgi.foundation as dependency, which contains several classes included in current JDK release, but as non-generic versions. this prevents compiling most eclipse projects in the current project. the org.osgi.foundation transitive dependency should be excluded in parent pom to prevent this - sling is compiling happily without out. patch attached. Parent pom should not include org.osgi.foundation artifact to allow compiling in eclipse Key: SLING-961 URL: https://issues.apache.org/jira/browse/SLING-961 Project: Sling Issue Type: Bug Components: General Affects Versions: Parent 5 Reporter: Stefan Seifert Attachments: parent_patch_090512.patch the artifact org.osgi.compendium 1.2.0 includes another artifact org.osgi.foundation as dependency, which contains several classes included in current JDK release, but as non-generic versions. this prevents compiling most sling projects in trunk in eclipse. the org.osgi.foundation transitive dependency should be excluded in parent pom to prevent this - sling is compiling happily without it. patch attached. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-963) maven-sling-plugin fix for targetPath without trailing slash
maven-sling-plugin fix for targetPath without trailing slash Key: SLING-963 URL: https://issues.apache.org/jira/browse/SLING-963 Project: Sling Issue Type: Bug Components: Maven Plugins Affects Versions: Maven Sling Plugin 2.0.2, Maven Sling Plugin 2.0.4 Reporter: Stefan Seifert Attachments: slingplugin_patch_090512.patch this is a follow-up from SLING-876, which is fixed, but left one cosmetic problem: if the path is defined in pom without a trailing slash, the path matching does not work. the patch attached fixes this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-963) maven-sling-plugin fix for targetPath without trailing slash
[ https://issues.apache.org/jira/browse/SLING-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-963: - Attachment: slingplugin_patch_090512.patch maven-sling-plugin fix for targetPath without trailing slash Key: SLING-963 URL: https://issues.apache.org/jira/browse/SLING-963 Project: Sling Issue Type: Bug Components: Maven Plugins Affects Versions: Maven Sling Plugin 2.0.2, Maven Sling Plugin 2.0.4 Reporter: Stefan Seifert Attachments: slingplugin_patch_090512.patch this is a follow-up from SLING-876, which is fixed, but left one cosmetic problem: if the path is defined in pom without a trailing slash, the path matching does not work. the patch attached fixes this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
