ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Topping (JIRA)" <>
Subject [jira] Commented: (ACE-62) Convert Ace build to Maven
Date Thu, 03 Dec 2009 00:49:20 GMT


Brian Topping commented on ACE-62:

Hi gang, sorry I've been AWOL, I'm just getting a new client squared away from a narrowly-avoided

I'm not much of a git user, Toni, do you need to push something?  I am cloned off github,
and if I look at, I don't see any of your
changes. I'm grateful you did the import and can manage that though, because I have no experience
with this svn<->git coexistence thing yet.

Otherwise, your approach looks great to me.  Maybe we should use this jira issue for module
synchronization so we don't step on each other.

Question about source moves:  Under SVN, the history is kept with a move, but will that history
be kept in git or will it need to be done again manually in svn once we have the POM set finished?
 Just curious, seems like we can manage it in any event.

Anyway, I am checked out, looking forward to putting in some time on this now that this client
has some tasks to do on their end.

Cheers, Brian

> Convert Ace build to Maven
> --------------------------
>                 Key: ACE-62
>                 URL:
>             Project: Ace
>          Issue Type: Task
>            Reporter: Brian Topping
>            Assignee: Toni Menzel
> 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