Skip to Content.
Sympa Menu

perfsonar-dev - Re: jar-repository and release process

Subject: perfsonar development work

List archive

Re: jar-repository and release process


Chronological Thread 
  • From: Loukik Kudarimoti <>
  • To: Roman Lapacz <>
  • Cc: "Jeff W. Boote" <>, Luís Marta <>, "" <>
  • Subject: Re: jar-repository and release process
  • Date: Thu, 07 Dec 2006 13:16:50 +0000

Roman,

This is a good point. Thanks for bringing it up.

I think I see this topic under a different light. I am more concerned about us depending on public repositories maintained by other project groups. What if this external project is shelved? What if the server of this external project goes down for maintenance during days which are crucial for us?
Also, these repositories provide more than one version of the same jar file. How are we going to make sure that our developers use one version of the same jar file?

In my opinion, we should have our own repository. All our source code should use jar libraries which are present within our repository. If anybody needs any other jar files or versions, it should be approved by a named individual/group in charge of maintaining the repository. (This is how CERN/EGEE does it)

The answer to your question:

" For example, if I want to create branch STABLE for RRD MA should I include also our all jar-repository or just those two directories created by us? What do you think? "

depends on how the installation scripts are written. During the build process, do your build targets assume that jars are already present in the lib directory or do they try to download them from somewhere?

I don't think we should copy required libraries for every micro-STABLE branches. STABLE branches should contain some description on the list of jars and version numbers of each jar that the service depends on. Ideally they should contain targets which can fetch the jars from the repository and put them in the lib directory before building. If not, the user of this branch will have to make use of the list/description and copy the jars from the repository before building the micro-STABLE branches.

However, I feel that micro-release tags should be treated differently. They should contain the complete lib directory with all the required jars (but the required jars should be copied over from our repository only - not anywhere else).

Loukik.


Roman Lapacz wrote:

Hi,

we haven't thought about jar-repository in the release process. I wouldn't see the problem if we used only public repository with libraries maintained by other project groups. But unfortunately we created new two directories in our repository (axis and rrdjtool, the rest are copied from the public repository) and I think now we should tie them somehow with service releases. For example, if I want to create branch STABLE for RRD MA should I include also our all jar-repository or just those two directories created by us? What do you think?

Roman





Archive powered by MHonArc 2.6.16.

Top of Page