perfsonar development work

[Roman Lapacz <>]

Michael Bischoff wrote:
> Hello all,
>
> About dependency management, would anyone have complains/objections if I
> would supply the perfsonar-base with a .pom-file. I have one configured
> for flowsa that confirms with the agreed-upon perfsonar directory
> structure, and (thus) doesn't break the ant-build scripts. It would also
> allow me to collect some metrics and run some quality-checks on the
> code-base. And give better insight into the dependency-tree.
>   

From my side I don't see any problem (I think Maven might be 
interesting alternative to Ant and convenient for those who prefer it).
Only one mu suggestion is to have the same version numbers of 
dependencies in both solutions.

Roman

> Regards,
>
> Michael.
>
>   
> > Hi Szymon,
> > I've finished to move all authn libraries to perfsonar base (in the
> > new structure) and the authentication service to the new structure too.
> > But, how I saw, updating the perfsonar base could be a critical
> > process, so I want to describe the steps that I'm going to do and advise me
> > if I'm doing something wrong: 1. Updating the svn branch. Changes are:
> > + Updating all authn libraries. It's not a critical process.
> > + Updating jar dependencies. The most interesting thing is some
> > updates in XML libraries: xerces to version 2.8.0 and xalan to 2.7.0. I've
> > tested with the AuthService and it's all right. + Updating the class
> > org.perfsonar.service.base.web.RequestHandler. It contains the
> > authentication component but it was in the trunk version and it was ok.
> > So, I think it's not a critical change.  I've
> > tested with the AuthService and it's all right. + Moving the Authentication
> > Service.
> > 2. Upload to jar-repository the new perfsonar-base-ant and perfsonar-
> > base jars. 3. ¿Remove the previous version of those jars?
> >