Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 92278 invoked from network); 10 Aug 2007 21:02:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Aug 2007 21:02:07 -0000 Received: (qmail 26337 invoked by uid 500); 10 Aug 2007 21:02:05 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 26121 invoked by uid 500); 10 Aug 2007 21:02:05 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 26110 invoked by uid 99); 10 Aug 2007 21:02:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Aug 2007 14:02:05 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [81.169.146.160] (HELO mo-p00-ob.rzone.de) (81.169.146.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Aug 2007 21:02:04 +0000 Received: from [127.0.0.1] (p548FC261.dip.t-dialin.net [84.143.194.97]) by post.webmailer.de (klopstock mo56) (RZmta 10.3) with ESMTP id 506349j7AKIOAq for ; Fri, 10 Aug 2007 23:01:39 +0200 (MEST) Message-ID: <46BCD26F.1020802@labeo.de> Date: Fri, 10 Aug 2007 23:02:39 +0200 From: Stefan Zoerner User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: Geronimo plugin for apacheds 1.5.0 References: <46BCC96E.1080901@labeo.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RZG-AUTH: kR2YrGeU3i5GJZNxbYfAbITnBeX/YWiFZ/RSZNN7D9RkvGeL2HlWAxNi X-RZG-CLASS-ID: mo00 X-Virus-Checked: Checked by ClamAV on apache.org Hi David! Thank you very much for the detailed instructions. I will definitely try this out tomorrow (too late for me now). Sorry again for reporting the wrong version, our mails overlapped. Greetings from Hamburg, Stefan David Jencks wrote: > > On Aug 10, 2007, at 1:24 PM, Stefan Zoerner wrote: > >> David Jencks wrote: >>> I thought people here might like to know that I recently updated >>> Geronimo's apacheds support from where it's been stuck in pre-1.0 >>> land to 1.5.0/1.5.1 and made it a plugin for easier updating. >> >> This is really good news! Thanks to you, David. >> >> I have downloaded the current Geronimo 2.0 milestone (M6) and was able >> to browse to the plugin entry for ApacheDS 1.0 > > I didn't know about any such plugin -- where did you find it? >> >> Please note that the URL used in the description >> http://directory.apache.org/subprojects/apacheds/index.html >> does not work any longer. Is it possible to change it to >> http://directory.apache.org/ >> which will likely be stable for a long time? > > I don't know... I'm not sure where that plugin came from, it's not the > one I worked on :-) >> >>> It works best with geronimo trunk (I found a couple of errors in the >>> 2.0 plugin installer right after the release was cut) but can be made >>> to work in 2.0. I expect after 2.0 is actually out we'll try to iron >>> out the wrinkles in the geronimo plugin system and actually release >>> this, it will be the first official geronimo plugin release (separate >>> from a server release). >> >> I must confess that I have not informed myself about the plugin >> features of G. The installation with M6 does not work, because all >> plugins say ("(Not available; View Details)"). Does this mean I have >> to build the trunk of G, as you have pointed out? > > The plugin features of geronimo don't work all that well yet, and the > plugin I worked on for geronimo 2+ and apacheds 1.5.0 isn't released > yet. It's significantly easier to get the plugin to run on geronimo > trunk or the branches/2.0 versions than the > about-to-be-officially-released (we hope) geronimo 2.0 which > unfortunately has a couple of bugs in the plugin installer that I > discovered a few minutes after the release was tagged. > > Here's what to do: > > geronimo: get 2.0 or build server/trunk or server/branches/2.0 > > plugin: check out and build plugins/directory/trunk (for apacheds > 1.5.1-SNAPSHOT) or plugins/directory/branches/2.0 (for apacheds 1.5.0). > > make your local maven repo look like a geronimo plugin repo: When you > built the plugin, maven will have copied a file geronimo-plugin.xml to > directory/target/classes/META-INF/geronimo-plugin.xml. Copy this file > to ~/.m2/repository/geronimo-plugins.xml and edit it so it looks like: > > > xmlns="http://geronimo.apache.org/xml/ns/plugins-1.2"> > > > Apache Directory 1.5.1-SNAPSHOT for Geronimo > ... > > > file:///Users/david/.m2/repository/ > > > > If you are using geronimo 2.0, change > > name="DirectoryService"> > name="configFile">var/directory/server.xml > > > > to > > name="DirectoryService"> > name="configFile">var/directory/server.xml > > > > (different namespace) > > > ok... now for the fireworks :-) > Start geronimo and look in the admin console under "plugins". Click the > "add new plugin repository" link and add the file:// url for your local > maven repo: for me it's file://Users/david/.m2/repository > > Now click the Search For Plugins button and you should get a page with > the directory plugin shown. If not there might be something wrong with > the "supported versions" in the geronimo-plugin.xml, try editiing it to > whatever version you are using. Click the install buttons at the bottom > of the pages until if finally installs.... > > On branches/2.0 and trunk the plugin should install and start without > problems. You can check by looking at the bottom of the System Modules > page. On 2.0, you have to do some more work. > > from the root of your geronimo install: > mkdir var/directory > cp > repository/org/apache/geronimo/plugins/directory/2.0-SNAPSHOT/directory-2.0-SNAPSHOT.car/META-INF/server.xml > var/directory/server.xml > > Now you should be able to start the plugin from the system modules page > in the admin console. > > I checked that it was working ok by using LDAP Studio to connect: I > could see some plausible entries and appeared to be able to add and edit > entries, so I figured it was working properly. > > Obviously this procedure is not yet incredibly convenient :-) but I > think improving it is going to be an immediate focus of a couple of the > geronimo developers. Having a really useful plugin will hopefully spur > this process on :-) > > thanks! > david jencks > > >> >> Thanks in advance, >> Stefan >> >> > > >