Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-YMail-OSG:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer;
  b=RaOkOZt03rk+r025cE+DSnteS9dGKkebRA4AWUdN3Gqa8eCyZskpLzf7URKPbGlXRlDZN/vJlyuDXJM4HK7IjGgQzz/OzIZxWxdZbtgR2d+Z2ByD0SD/uWeCdMi3URhaLS8htmawH0N4nX9EN4w0b6tHhfRqNfIESt9VYW1j73U=
  ;
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <07E40C2B-2F53-4C1D-B98E-F6A228C6AC1E@gmail.com>
References: <5cfc026d0708131425x69f234b0g337e86998962840d@mail.gmail.com>
 <07E40C2B-2F53-4C1D-B98E-F6A228C6AC1E@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <F8285FBE-8BD4-4E28-83A2-04EB15F16E76@yahoo.com>
Content-Transfer-Encoding: quoted-printable
From: David Jencks <david_jencks@yahoo.com>
Subject: Re: Apache Directory Plugin - missing files
Date: Mon, 13 Aug 2007 16:11:41 -0700
To: user@geronimo.apache.org


On Aug 13, 2007, at 2:49 PM, Paul McMahan wrote:

> The directory plugin has not been deployed to the online repository =20=

> so it's not available for download yet.  It has now been removed =20
> from the 2.0 catalog so others won't encounter this error and =20
> should be added back when the plugin is deployed.  In the meantime =20
> I think you can build the plugin locally from the source at http://=20
> svn.apache.org/repos/asf/geronimo/plugins/directory/trunk/ and =20
> install it from the command line using bin/deploy.sh install-=20
> plugin.   I haven't tried this but I think it should work.

hah!

here's some instructions I posted to the apacheds list recently.

The plugin features of geronimo don't work all that well yet, and the =20=

plugin I worked on for geronimo 2+ and apacheds 1.5.0 isn't released =20
yet.  It's significantly easier to get the plugin to run on geronimo =20
trunk or the branches/2.0 versions than the about-to-be-officially-=20
released (we hope) geronimo 2.0 which unfortunately has a couple of =20
bugs in the plugin installer that I discovered a few minutes after =20
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 =20
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 =20
you built the plugin, maven will have copied a file geronimo-=20
plugin.xml to  directory/target/classes/META-INF/geronimo-=20
plugin.xml.  Copy this file to ~/.m2/repository/geronimo-plugins.xml =20
and edit it so it looks like:

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<geronimo-plugin-list xmlns=3D"http://geronimo.apache.org/xml/ns/=20
plugins-1.2">

<plugin>
     <name>Apache Directory 1.5.1-SNAPSHOT for Geronimo</name>
...
   </plugin>
   <default-repository>file:///Users/david/.m2/repository/</default-=20
repository>
</geronimo-plugin-list>

If you are using geronimo 2.0, change
     <config-xml-content>
         <gbean xmlns=3D"http://geronimo.apache.org/xml/ns/attributes-1.2"=

                 name=3D"DirectoryService">
             <attribute name=3D"configFile">var/directory/server.xml</=20=

attribute>
         </gbean>
     </config-xml-content>

to
     <config-xml-content>
         <gbean xmlns=3D"http://geronimo.apache.org/xml/ns/attributes-1.1"=

                 name=3D"DirectoryService">
             <attribute name=3D"configFile">var/directory/server.xml</=20=

attribute>
         </gbean>
     </config-xml-content>

(different namespace)


ok... now for the fireworks :-)
Start geronimo and look in the admin console under "plugins".  Click =20
the "add new plugin repository" link and add the file:// url for your =20=

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 =20
with the directory plugin shown.  If not there might be something =20
wrong with  the "supported versions" in the geronimo-plugin.xml, try =20
editiing it to whatever version you are using.  Click the install =20
buttons at the bottom of the pages until if finally installs....

On branches/2.0 and trunk the plugin should install and start without =20=

problems.  You can check by looking at the bottom of the System =20
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/=20
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 =20
page in the admin console.

I checked that it was working ok by using LDAP Studio to connect: I =20
could see some plausible entries and appeared to be able to add and =20
edit entries, so I figured it was working properly.

Obviously this procedure is not yet incredibly convenient :-) but I =20
think improving it is going to be an immediate focus of a couple of =20
the geronimo developers.  Having a really useful plugin will =20
hopefully spur this process on :-)

thanks!
david jencks

>
> Best wishes,
> Paul
>
> On Aug 13, 2007, at 5:25 PM, Rodrigo Rodrigues da Silva wrote:
>
>> I am trying to install apache directory plugin 1.5.0-SNAPSHOT on =20
>> geronimo 2.0. But when I choose the plugin and click "Install =20
>> Plugin" the progress bar won't change and no plugins is installed. =20=

>> I get error messages saying some files are missing in repository. =20
>> The error messages are attached to this e-mail.
>>
>> Thanks in advance,
>>
>> --=20
>> Rodrigo Rodrigues da Silva
>> Engenharia de Computa=E7=E3o - Coop8
>> http://www.coop8.rg.com.br
>> Gr=EAmio Polit=E9cnico - Gest=E3o Colabora
>> http://www.gremio.poli.usp.br
>>
>> "N=E3o importa como morre o home, importa como vive." Carij=F3, velho =
=20
>> do rio.
>>
>> "To the person with only a hammer, everything looks like a nail." =20
>> bussdriver
>> <error.txt>
>