[
https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123133#comment-15123133
]
Jan Sindberg edited comment on FC-143 at 1/29/16 7:27 AM:
--
I think that I made a last
[
https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123133#comment-15123133
]
Jan Sindberg edited comment on FC-143 at 1/29/16 7:25 AM:
--
I think that I made a last
Like Kerby, I agree for the moment it may be good to use the same mailing list
for Fortress for all the Fortress specific discussions.
Regards,
Kai
-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com]
Sent: Thursday, January 28, 2016 11:40 PM
To: Apache Directory
Thanks for the great work, Emmanuel.
I have some questions. As discussed previously, it's hard to recreate the
database corrupt issue. Did you include a test with a sample corrupt database
image and show if it's can be repaired? All the work in a unit test or
integration test. Does the repair
Le 29/01/16 03:18, Zheng, Kai a écrit :
> I don't know the mentioned "CMS plugin" either. Would anyone give a hint?
> Thanks.
The CMS system in use at Apache works in two phases :
- first you commit your updates into SVN/git, and it is published on a
staging site. You can control the rendering
Thanks Emmanuel for the details!
Regards,
Kai
-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com]
Sent: Friday, January 29, 2016 2:10 PM
To: Apache Directory Developers List
Subject: Re: About project site
Le 29/01/16 03:18, Zheng, Kai a
Le 29/01/16 07:41, Zheng, Kai a écrit :
> Thanks for the great work, Emmanuel.
>
> I have some questions. As discussed previously, it's hard to recreate the
> database corrupt issue. Did you include a test with a sample corrupt database
> image and show if it's can be repaired?
There is no need
[
https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123133#comment-15123133
]
Jan Sindberg commented on FC-143:
-
I think that I made a last minute change that I shouldn't have done. I
Le 29/01/16 07:41, Zheng, Kai a écrit :
> Thanks for the great work, Emmanuel.
>
> I have some questions. As discussed previously, it's hard to recreate the
> database corrupt issue. Did you include a test with a sample corrupt database
> image and show if it's can be repaired? All the work in a
[
https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123133#comment-15123133
]
Jan Sindberg edited comment on FC-143 at 1/29/16 7:30 AM:
--
I think that I made a last
[
https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123133#comment-15123133
]
Jan Sindberg edited comment on FC-143 at 1/29/16 7:29 AM:
--
I think that I made a last
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122037#comment-15122037
]
Stefan Seelmann commented on DIRSTUDIO-1088:
Did you upgrade from an previous Studio
This is not about everybody following all mailing lists. I don't believe
that the majority of our combined sub communities does that. This is about
communicating to the entire community. So that everybody gets the same
message when it is appropriate.
Pierre Smits
ORRTIZ.COM
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122544#comment-15122544
]
Ken Walenga commented on DIRSTUDIO-1088:
Thank you. That fixed it for me!
Kenneth
[
https://issues.apache.org/jira/browse/DIRSTUDIO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121103#comment-15121103
]
Daniel Buschke commented on DIRSTUDIO-695:
--
Hi,
I'd like to "upvote" this. I miss a option
On 01/28/2016 03:59 PM, Pierre Smits wrote:
> My viewpoint is that we should always target all the lists when
> contributors are onboarded into the privileged groups. This ensures that
> the entire project community is in the loop and it shows that we are one
> (community), albeit that we have
[
https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-143.
---
Resolution: Fixed
Fix Version/s: 1.0.0-RC41
Applied the patch. Had to correct a minor error where
[
https://issues.apache.org/jira/browse/FC-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-142.
---
Resolution: Fixed
changed to:
config.setProperty( GlobalIds.LDAP_ADMIN_POOL_MAX, szValue);
>
[
https://issues.apache.org/jira/browse/FC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121616#comment-15121616
]
Shawn McKinney commented on FC-140:
---
another good catch
> System properties cannot override values for
[
https://issues.apache.org/jira/browse/FC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-140.
---
Resolution: Fixed
Fix Version/s: 1.0.0-RC41
applied change as recommended
> System properties
[
https://issues.apache.org/jira/browse/DIRKRB-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiajia Li resolved DIRKRB-272.
--
Resolution: Fixed
Assignee: Jiajia Li
> Fix issues in Kerby-kerb Util module found in code
I don't know the mentioned "CMS plugin" either. Would anyone give a hint?
Thanks.
Regards,
Kai
-Original Message-
From: Li, Jiajia [mailto:jiajia...@intel.com]
Sent: Thursday, January 28, 2016 4:13 PM
To: ke...@directory.apache.org
Subject: RE: About project site
-Original
Fellow Dev's,
We’ve just added a new committer to fortress, and my goal is to add a few more
before long. My question is which list to use for communicating? In the past,
with our limited discussions, we’ve used the fortress list. But that list is
(supposed to be) for users. We could use
[
https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121552#comment-15121552
]
Shawn McKinney commented on FC-143:
---
I think this is a good idea.
> Let LdapClientTrustStoreManager read
On Thu, Jan 28, 2016 at 7:41 PM, Shawn McKinney
wrote:
> Fellow Dev's,
>
> We’ve just added a new committer to fortress, and my goal is to add a few
> more before long. My question is which list to use for communicating? In
> the past, with our limited discussions, we’ve
[
https://issues.apache.org/jira/browse/FC-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121565#comment-15121565
]
Shawn McKinney commented on FC-141:
---
nice catch
> Config from repository is adding instead of overriding
>
[
https://issues.apache.org/jira/browse/FC-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-141.
---
Resolution: Fixed
changed to setProperty as recommended.
> Config from repository is adding instead of
My viewpoint is that we should always target all the lists when
contributors are onboarded into the privileged groups. This ensures that
the entire project community is in the loop and it shows that we are one
(community), albeit that we have various sub groups. But also that we are
communicating
28 matches
Mail list logo