ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zilvinas Kybartas (JIRA)" <>
Subject [jira] Updated: (ACE-62) Convert Ace build to Maven
Date Wed, 17 Feb 2010 21:31:28 GMT


Zilvinas Kybartas updated ACE-62:

    Attachment: ACE-62-trunk.patch

I was eager to try the project in action, and since trunk doesnt build with maven I fixed
the build by myself. There were following issues i found:
 *  "ace-log-store" project is missing - it seems to be somehwat similar to "ace-server-log-store".
My guess that both projects are actually the same, so i renamed all the log-store dependencies
to server-log-store. Im not sure is it good solutions, as I don't know what was the real intention
(just was following naming convetion of other projects)
 *  there were multiple copy/paste problems in some bnd files, which were preveting to function
properly for some osgi bundles. 

After these changes, I was able to build and run file based provisioning server and gateway.
 I'm adding the patch in case youre wondering of what exactly I've changed, hope that it will
be of any use for you.

> Convert Ace build to Maven
> --------------------------
>                 Key: ACE-62
>                 URL:
>             Project: Ace
>          Issue Type: Task
>            Reporter: Brian Topping
>            Assignee: Toni Menzel
>             Fix For: 0.8.0
>         Attachments: ACE-62-trunk.patch
> Some discussion has occurred after ACUS about converting the ACE build to Maven.  This
has some unique challenges, mostly regarding build speed.  The build is currently a highly-optimized
set of Ant tasks, which is not necessarily compatible speed-wise with a set of naturally decomposed
Maven POMs.  
> Three people have expressed interest in working on this: Toni Menzel, Jean-Baptiste Onofré,
and Brian Topping.  Toni suggested that we start a Github project so the three of us (currently
not committers) could start work on this immediately, which is a great idea.  So if
doesn't work, let's use something better suited somewhere else!
> Shall we focus the discussion here?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message