Re: [higgins-dev] Updated JNDI CP

["Tom Doman" <TDoman@xxxxxxxxxx>]

I thought it was for the main project download page but I'm happy to standardize on that being a link to the jar itself.  Some of the projects we're dependant on don't even have the jar itself downloadable.  You have to get a ZIP or something.  However, the stuff we've contributed to eclipse at Novell, I can put all our dependant libraries on our bandit forge project and redistribute them from there since we already have approval to redistribute these jars.

Maybe we should make a "project" column so the project can be visited and explored especially if someone wants to try our components with a later version of a given dependant library to help them minimize versions of a given library.

Any other thoughts?

Tom

>>> Michael McIntosh <mikemci@xxxxxxxxxx> 4/4/2007 3:40 PM >>>
What is the download column for?

higgins-dev-bounces@xxxxxxxxxxx wrote on 04/04/2007 03:57:26 PM:

> There are direct links for all of those in the version column.  Did 
> those not work?
> 
> Tom
> 
> >>> Michael McIntosh <mikemci@xxxxxxxxxx> 4/4/2007 12:57 PM >>>
> The link on 
> http://wiki.eclipse.org/index.php/JNDI_Context_Provider_Dependencies 
> resolves to a generic OpenXDAS download page which currently provides 
> OpenXDAS-0.4.226.jar.
> The Eclipse project requires OpenXDAS-0.3.192. After navigating around 
the 
> site for a while I've found 
> http://sourceforge.net/project/downloading.php? 
> group_id=175511&use_mirror=easynews&filename=openxdas-0.3.192-win-
> i586-bin.zip&31739064 
> which provides a xip file containing what you need. Can please someone 
> update that link?
> 
> A similar thing happens for the Bandit jars. Why can't the link on the 
> dependancies page be to the actual download instead of a pages 
containing 
> many downloads - only a few of of which I need?
> 
> Thanks,
> Mike
> 
> 
> 
> higgins-dev-bounces@xxxxxxxxxxx wrote on 04/04/2007 12:15:25 PM:
> 
> > I have now checked in the changes I referenced two days ago, namely,
> > the removal of hard coded mappings and the addition of mapping PDPs 
> > based on JavaScript.  If the no PDPs are defined in configuration, 
> > names and types returned from the JNDI CP will look very LDAPish.
> > 
> > I have documented these PDPs and their configuration on the JNDI 
> > Context Provider page off of the higgins components page (http:
> > //wiki.eclipse.org/index.php/Components).
> > 
> > The JNDI CP now has additional dependencies, namely, two additional 
> > bandit utility jars and the Rhino JavaScript engine.  These new 
> > dependencies are documented and linked on the dependencies page, 
> > again, off the higgins components page.
> > 
> > I will try to be available throughout the next couple of days into 
> > the later evening hours.  I'll be lurking on the higgins IRC so 
> > don't hesitate to contact me if you need assistance in adjusting to 
> > this change.
> > 
> > The JavaScript Policy CP is still available to do other PDPs that I 
> > decided not to implement in the JNDI CP (if you discover a need for 
> > one of them that we'd want in the stand-alone JNDI CP, let me know).
> > The JavaScript Policy CP's available PDPs, configuration, and usage 
> > are documented on the higgins components page as well.
> > 
> > Thanks,
> > Tom
> > 
> > 
> > _______________________________________________
> > higgins-dev mailing list
> > higgins-dev@xxxxxxxxxxx 
> > https://dev.eclipse.org/mailman/listinfo/higgins-dev 
> 
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx 
> https://dev.eclipse.org/mailman/listinfo/higgins-dev 
> 
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx 
> https://dev.eclipse.org/mailman/listinfo/higgins-dev 

_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx 
https://dev.eclipse.org/mailman/listinfo/higgins-dev