On Thu, 2004-05-13 at 00:50, Arnaud Heritier wrote:
> .... 
> > I think you're reaching an interesting point here.
> > 
> > The developer information should be retrieved from an external
> > repository, this being an LDAP or a simple global XML file shared by all
> > projects.
> > 
> > Otherwise you have a maintenance burdain on big projects.
> > 
> > Furthermore, it introduces unnecessary dependencies. If I travel for a
> > while, and my timezone is affected I don't see why I should modify the
> > project files. Sounds counterproductive to me.
> > 
> 
> Hello Jerome,
> 
> It's exactly what I have in mind. 
> 
> I think that in a project file we only need to have an id to retrieve the
> user and his roles.
> I didn't found yet haw we can describe the unique id but I think it is
> possible.
> For example with an LDAP Directory :
> <developer>
>       <type>LDAP</type>
>       <id>cn=aheritier.....</id>
>       <property>
>               <name>ldapServerUrl</name>
>               <value>....</value>
>       </property>
>       ....
> </developer>

I would have thought perhaps of something like this:

in the project file, only contains either the developer ID either the
developer info (to stay backward compatible).

Somewhere else in the project file, have a way to define the developer
sources.

something like 
<developersSource>
  <developerSource>
    <property> 
      <name>type</name>
      <value>LDAP</value>
    </property>
    <property> 
      <name>name</name>
      <value>My LDAP Server</value>
    </property>
    <property> 
      <name>host</name>
      <value>xxxxx</value>
    </property>
    <property> 
      <name>mapping-id-property</name> <!-- something to map the id to a
property in the LDAP server? -->
      <value>cn</value>
    </property>
  </developerSource>
  <developerSource>
  <developerSource>
    <property> 
      <name>type</name>
      <value>XML</value>
    </property>
    <property> 
      <name>name</name>
      <value>Company XXX developers</value>
    </property>
    <property> 
      <name>uri</name>
      <value>xxxx</value>
    </property>
  </developerSource>
</developersSource>

Then the build process tries to find the developer in the sources,
iteratively in the list order.

Or maybe we need to use a sort of URI to define the ID?

ldap:cn=aheritier

xml:lacostej

and the build process searches according to the matching source
locations.

etc... 

It's just a thought, it needs to be refined. It think we need to explore
the URI way, it sounds flexible enough to just require a single line in
the project file and has supposedly good support in Java.

I don't have time until early June, but would be happy to help you if
you need by then.

> > Jerome
> > 
> > PS: Arnaud I noticed that your reply-to field seems to default to your
> > email instead of the list's one when you use your laposte.net account or
> > apache.org account. Probably because you override it there. Doesn't do
> > it with your axway account. I am not sure if it's a bug or a setting in
> > ezmlm. Sound strange to me reply-to should default to the list,
> > shouldn't it?
> 
> At home, I overrided the reply-to laposte.net with apache.org to subscribe
> to the mailing lists with my apache @.
> It's weird because I thought that ezmlm automatically overrided it with the
> ML @.  


strange.

Maybe we should look at 

http://www.ezmlm.org/faq-0.40/FAQ-9.html#ss9.8

Do you want to follow up with that? I am not an Apache developer, and I
guess you can find out more what's going on by yourself.

J



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to