I have used repository.a.o for preparing the Shindig release, and can
confirm, bar the issues of having the GPG and ssh/svn passwords in the
settings.xml every thing works just fine and it makes it a lot easier.
(fortunately as I have done it a lot of times now :) )
The settings.xml issues ca
Hi all,
Lets pick up the repository.a.o discussion again now that we have
released Sling 5.
I have created a patch for our parent pom and attached it to the tracker
issue SLING-917 [1]. The important changes:
* Use Apache parent pom 6
* Drop most of our apache-release profile
(for
[
https://issues.apache.org/jira/browse/SLING-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-917:
Attachment: SLING-917.patch
Proposed changes to the parent pom to leverage the repository.a.
[
https://issues.apache.org/jira/browse/SLING-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-980.
---
Resolution: Fixed
Changed the snapshot repository reference in the parent pom at Rev. 776852.
[
https://issues.apache.org/jira/browse/SLING-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-917:
Affects Version/s: Parent 5
Fix Version/s: Parent 6
Relating this issue to the paren
Refer to the snapshot repository at repository.a.o in the parent pom
Key: SLING-980
URL: https://issues.apache.org/jira/browse/SLING-980
Project: Sling
Issue Type: Improvem
Hi,
Christian Sprecher schrieb:
>> Well, in JSP you have you have two options: include pieces of code
>> (fragements) upon JSP build time (<%...@include>) and RequestDispatcher
>> based include with . I assume you mean the former here,
>> right ?
>>
>>
> Yes, exactly. I did have a look at it a
[
https://issues.apache.org/jira/browse/SLING-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711306#action_12711306
]
Felix Meschberger commented on SLING-979:
-
Updated reference to the API and Engine b
[
https://issues.apache.org/jira/browse/SLING-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711304#action_12711304
]
Felix Meschberger commented on SLING-979:
-
Implemented the Adaptable interface in th
[
https://issues.apache.org/jira/browse/SLING-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711302#action_12711302
]
Felix Meschberger commented on SLING-979:
-
Extended the Sling API in Rev 776815:
[
https://issues.apache.org/jira/browse/SLING-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-979:
---
Assignee: Felix Meschberger
> Make Sling HTTP Servlet Request and Response Adaptable
>
Hi Carl,
nothing else ;) Right now the wiki is the only way to participate (beside
contributing patches in JIRA).
Mike Müller recently was accepted as documentation commiter, it might be
worth asking him which parts he currently is refactoring/writing and which
parts really need some more document
In my attempts to learn more about Sling's internal workings, I'd like
to start contributing documentation. Should I just add/edit to the
wiki or is there something else going on for docs?
On Mon, May 18, 2009 at 11:56 AM, Felix Meschberger wrote:
> ...The main source artifacts have the following checksums:
>
> org.apache.sling.commons.mime-2.1.0-incubator-project.zip
> MD5: a3b4135a0cd6a9a3f779bba34cf335da
> SHA1: 0f1c866ef65a29433f1fae06aa3a898515c32c7e
>
> org.apache.sling.c
Make Sling HTTP Servlet Request and Response Adaptable
--
Key: SLING-979
URL: https://issues.apache.org/jira/browse/SLING-979
Project: Sling
Issue Type: New Feature
Components: AP
+1
Carsten
--
Carsten Ziegeler
cziege...@apache.org
[
https://issues.apache.org/jira/browse/SLING-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711058#action_12711058
]
Bertrand Delacretaz commented on SLING-931:
---
Fixed in revision 776361, leaving thi
17 matches
Mail list logo