[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to apply maven build system (Was: How to use Debian packaged freehep instead of upstream provided freehep.jar)



Hi.

On 16/02/2011 23:03, Andreas Tille wrote:
>   mvn archetype:generate -DgroupId=Patristic -DartifactId=patristic -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false
> 
> as it is suggested here[3]

There's something funny about this command: I executed it and it had to
download about 30 different files before being able to do something
really dump (copy some simple templates in the working directory).

>> Anyway, unfortunately, you still have to put hands on upstream's code,
>> because maven requires the projects it's working on to have a specific
>> directory structure.
> 
> That's fine in the case of patristic - I'd need to repack the code in
> any case - so why not applying the maven directory layout?

Actually I checked it, and this is not really necessary: you can
configure it[1]. Anyway, I really think that it's better to user
standard layout, to make your more idiomatic for others.

 [1] http://maven.apache.org/pom.html#Directories

> I'm actually not very keen on really using maven as long as I can
> get the package working at all - but I actually have no real clue
> what command line would trigger the build process (and upstream)
> seems to be dead.  So in principle the most simple help would be
> a command line which builds the JAR.

As Torsten suggests, once you have your working POM the command you need
in "mvn package".

Here[2] you can a sample POM package for patristic, which unfortunately
doesn't compile because of missing dependencies I don't know where to get.

 [2] http://people.debian.org/~gio/packages/patristic-maven.tar.gz

BTW, working on this just made me notice that some new versions of
FreeHEP were released some months ago. These releases were deployed on
maven repositories, but I didn't notice them because they were not
deployed on the site where development happened before. This is one of
the many things I don't like of maven: it doesn't teach developers to
have clean and clear release cycle and habits (for instance, where to
publish the release), because the magic of maven will (try to) solve any
problem.

Ciao, Giovanni.
-- 
Giovanni Mascellani <mascellani@poisson.phc.unipi.it>
Pisa, Italy

Web: http://poisson.phc.unipi.it/~mascellani
Jabber: g.mascellani@jabber.org / giovanni@elabor.homelinux.org

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: