EPICS V4 institutional build. WAS: Re: Maven for pvService

[Greg W. <gre...@ps...>]

Ok, Matej there are 2 big things that worry me about Maven for institutions. If we're going to
recommend use of Maven in places like PSI or SLAC

1) How to handle build when behind a "firewall" - that is, when Maven can't simply download
dependencies. This is the case at SLAC, and I think PSI too. Expect it to be common.
 
2) Who's going to write the installation guide? It's going to have to be you Matej. We can't
really go forward with Maven unless there is a document that walks a lab's infrastructure team
through setting it up for their institution. I can do that for make (helped by the fact
that all infrastructure people will already know the make story), but I can't do it for maven.

Also, use of version numbers for dependency specification seems too explicit to me.
Is see lots of lines like <version>2.3.2</version> indicating A is dependent on
version 2.3.2 of B. But I'm not aware of any globally recognised standard for the
meaning of these digits. So, how can Maven possibly know what implies a new entry point,
or what implies forward and backward incompatibility. Without knowing what the 
digits mean for a given dependency, what use is it? Can I express the interpretation 
to Maven in some metalanguage?

 
Greg


This is going to have to be you Matej. It has to be 2 or 3 pages at least, of explicit 
instructions about use of Maven, including about setup and coice of repo  
On 10 Nov 2011, at 15:19, Matej Sekoranja wrote:

>> Thanks, but I don't understand. I want to create the epics v4 java distribution. If I did what
>> I want in make, I would create a makefile with something like:
>> 
>> epicsv4 : epicsv4.jar
>> 
>> epicsv4.jar : FORCE
>>        jar -cvf epicsv4.jar `find pvDataJava/bin -name "*.class" -print
>>        jar -uvf epicsv4.jar `find pvAccessJava/bin -name "*.class" -print
>>        jar -uvf epicsv4.jar `find pvServiceJava/bin -name "*.class" -print
>> 
>> 
>> Is there some pom file that already does this?
> 
> No.
> 
>> I'm not asking how you run a java program, though, you know, thanks! I'm asking whether the poms that
>> have been written for the EPICs v4 sourceforge project include or do not
>> include a standard way to *execute* services and clients that have been built
>> with those poms! Should I be doing something like the following when I run the , and if so, where is it documented
>> 
>> mvn -arch:execute -… yada yada pvService:org.epics.pvService.example.ExampleClient
>> 
>> The answer may well be "no, no execution support is included in the poms". But I want to verify.
> 
> You are right, we do not have execution support inside.
> 
> Matej