Enrique Rodriguez a écrit :
On 3/22/07, David Jencks <[EMAIL PROTECTED]> wrote:
...
What next? Should I commit this while we figure out what to do next?
Turns out I only needed 2 hrs. to replace BC with JDK JCE. I have the
BC dep removed locally with all tests passing. I am ready to comm
On 3/22/07, David Jencks <[EMAIL PROTECTED]> wrote:
...
What next? Should I commit this while we figure out what to do next?
Turns out I only needed 2 hrs. to replace BC with JDK JCE. I have the
BC dep removed locally with all tests passing. I am ready to commit.
At this point I only need to
Getting improved code would be great :-)
Meanwhile Rick added the classes to geronimo 2.0 (GERONIMO-3004, rev
521413, I deployed a snapshot, and attached a patch to DIRSERVER-877
that uses geronimo-util: all the integration tests pass.
The only problem I can see is that geronimo-util is a sn
[
https://issues.apache.org/jira/browse/DIRSERVER-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated DIRSERVER-877:
---
Attachment: DIRSERVER-877-2.patch
Rick added the necessary classes to geronimo-util, and I
[
https://issues.apache.org/jira/browse/DIRSERVER-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrique Rodriguez resolved DIRSERVER-867.
-
Resolution: Fixed
This is fixed in the SASL branch, awaiting merge to trunk fo
On 3/22/07, David Jencks <[EMAIL PROTECTED]> wrote:
...
apacheds appears to use bouncycastle for some kerberos support. Some
of the classes they need are already in geronimo-util, but these are
missing so far:
org.bouncycastle.crypto.digests.SHA1Digest
org.bouncycastle.crypto.modes.CBCBlockCiph
This turned out to be a trivial update. Committed revision 521413.
Rick
David Jencks wrote:
I talked with Rick McGuire who set up our original geronimo-util jar
and he thinks it will be pretty easy to pull these classes in or
convert to using platform JCE and he's offered to see about adding
Ole,
On 3/21/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
> The logger.jar in the bin directory is the log4j dependency right?
>
>
> Yep it is.
>
> Once the classloading is redone, can we load the logging classes
from
>
> /usr/share/hava/logger-verrsion.jar or does it have to be in
>
In server-main, you can use 'apacheds.sh'. I use it all the time to
launch the server to test interop with Linux CLI tools for LDAP and
Kerberos. Is this what you're looking for?
Enrique
On 3/22/07, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote:
Thanks for carrying the script issues, Ole.
Just
I talked with Rick McGuire who set up our original geronimo-util jar
and he thinks it will be pretty easy to pull these classes in or
convert to using platform JCE and he's offered to see about adding
them while he waits for various other problems to get solved.
thanks
david jencks
(more o
[
https://issues.apache.org/jira/browse/DIRSERVER-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-750.
---
> update commons-lang from 2.0 to 2.1
> ---
>
>
[
https://issues.apache.org/jira/browse/DIRSERVER-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-750.
-
Resolution: Fixed
1.0.1 already use only commons-lang 2.1
There were some rema
The project Apache - Directory Server Shared Trunk has the following 1 change
by 1 author:
*elecharny* made the following changes at 01:32 PM, 22 March 2007
Comment:
Switched to commons-lang-2.1
> /directory/shared/trunk/ldap/pom.xml (521397)
-
I recently realized apacheds was using bouncy castle which IIUC is
not distributable with apache stuff, so I looked into whether they
could switch to our geronimo-util.
apacheds appears to use bouncycastle for some kerberos support. Some
of the classes they need are already in geronimo-uti
[
https://issues.apache.org/jira/browse/DIRSERVER-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated DIRSERVER-877:
---
Attachment: DIRSERVER-877-broken-1.patch
I took a look at substituting the geronimo-util j
[
https://issues.apache.org/jira/browse/DIRSERVER-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483252
]
Emmanuel Lecharny commented on DIRSERVER-760:
-
Now that we have a 1.5.0 (almost) version in which the
[
https://issues.apache.org/jira/browse/DIRSERVER-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-763:
Fix Version/s: 1.0.3
1.5.1
Should be investigated...
> Suppo
[
https://issues.apache.org/jira/browse/DIRSERVER-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-777.
---
> update of shell script in the schema-archetype directory
>
[
https://issues.apache.org/jira/browse/DIRSERVER-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-777.
-
Resolution: Fixed
Fixed in 1.0.2 :
http://svn.apache.org/viewvc?view=rev&rev=5
[
https://issues.apache.org/jira/browse/DIRSERVER-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-805:
Fix Version/s: pre-2.0
Not sure that it worth the effort right now... Chars abov
[
https://issues.apache.org/jira/browse/DIRSERVER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-798:
Fix Version/s: 1.5.2
> Configurable ApacheDS OSGi bundles require schema oid as
[
https://issues.apache.org/jira/browse/DIRSERVER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-798:
OSGi should be integrated in 1.5.2, if everything is ready.
> Configurable ApacheD
[
https://issues.apache.org/jira/browse/DIRSERVER-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-767:
Fix Version/s: 1.0.3
1.5.1
Agreed. Should be fixed in the nex
[
https://issues.apache.org/jira/browse/DIRSERVER-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-807:
Fix Version/s: 1.5.2
Waiting for the next version, I doubt we can include this i
[
https://issues.apache.org/jira/browse/DIRSERVER-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-817:
Fix Version/s: 1.5.1
What about including this patch in the next version ?
> Si
[
https://issues.apache.org/jira/browse/DIRSERVER-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-833:
Fix Version/s: 1.5.1
> Attribute(s)Impl usage and API
>
[
https://issues.apache.org/jira/browse/DIRSERVER-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-840:
Fix Version/s: 1.5.1
> Double modification on a modify ?
> -
[
https://issues.apache.org/jira/browse/DIR-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483216
]
Emmanuel Lecharny commented on DIR-206:
---
note : Moved to the DIR project, as it's not a Directory Server specific
[
https://issues.apache.org/jira/browse/DIRSERVER-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-858.
---
Assignee: Emmanuel Lecharny
> Allow subclassing LdapDN
>
[
https://issues.apache.org/jira/browse/DIRSERVER-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-858.
-
Resolution: Won't Fix
The LdapDN class is intended for internal use only. It i
BouncyCastle IP issues with IDEA algo included in jars
--
Key: DIRSERVER-877
URL: https://issues.apache.org/jira/browse/DIRSERVER-877
Project: Directory ApacheDS
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/DIRSERVER-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-865:
Fix Version/s: 1.0.3
> errors when importing ACI from LDIF file containing tabs
[
https://issues.apache.org/jira/browse/DIRSERVER-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-865:
Affects Version/s: 1.0
Fix Version/s: 1.5.1
Needs some more investigatio
[
https://issues.apache.org/jira/browse/DIRSERVER-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-867:
Affects Version/s: (was: 1.5.1)
1.5.0
Fix Vers
[
https://issues.apache.org/jira/browse/DIRSERVER-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-871:
Fix Version/s: 1.5.2
Not really urgent. Let's fix it in 1.5.2
> NPE when runnin
[
https://issues.apache.org/jira/browse/DIRSERVER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-874:
Fix Version/s: 1.5.1
> Entries should be normalized in the NormalizationService
[
https://issues.apache.org/jira/browse/DIRSERVER-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-876:
Fix Version/s: 1.5.1
To be added in 1.5.1
> Add a new 'supportedExtension' or '
David Jencks a écrit :
OK, I have an actual concern too, that I could actually investigate
if we had proposed release artifacts :-)
What exactly is apacheds's use of bouncy castle code? My
understanding of the status of the bouncy castle jar situation is
that apache projects cannot redis
OK, I have an actual concern too, that I could actually investigate
if we had proposed release artifacts :-)
What exactly is apacheds's use of bouncy castle code? My
understanding of the status of the bouncy castle jar situation is
that apache projects cannot redistribute bouncy castle jar
David Jencks a écrit :
On Mar 21, 2007, at 7:33 PM, Emmanuel Lecharny wrote:
I would add that we could follow more or less the process described
in http://cocoon.apache.org/devinfo/releasing.html
This seems to be pretty reasonable. Tagging the trunk is not really
complicated.
wdyt ?
On Mar 21, 2007, at 7:33 PM, Emmanuel Lecharny wrote:
I would add that we could follow more or less the process described
in http://cocoon.apache.org/devinfo/releasing.html
This seems to be pretty reasonable. Tagging the trunk is not really
complicated.
wdyt ?
I think that's pretty muc
Thanks for carrying the script issues, Ole.
Just a question : do you have time to think about a script which can
launch the server without the daemon ? Sometime I want to launch the
server standalone in command line without installing it, but it's not
currently an option.
wdyt ?
Emmanuel
Trustin Lee a écrit :
On 3/22/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
BTW, I think it's great to tag first before a vote.
Otherwise, we could think of the vote period as our vacation, that is,
a committer is not allowed to check in any code unless if it fixes any
concern raised during
Ole Ersoy a écrit :
Hey Guys,
I just read my mail over again:
===
Just wanted to see if anyone had any thoughts on handling updates
to Java beans (Service Data Objects - but basically the same thing)
persisted with ADS.
==
44 matches
Mail list logo
