Hey guys,
have you ever thought about changing your build environment from Ant to Maven? Maven has a lot of usefull features recoder really needs, e.g. no libraries in svn, publishing recoder to maven central, simpler build system, ...
Regards,
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sounds like a great idea, and it has actually been on my (internal)
suggestion list. However, I currently don't have time to do it - would you
be interested in contributing?
Hey guys,
have you ever thought about changing your build environment from Ant to
Maven? Maven has a lot of usefull features recoder really needs, e.g. no
libraries in svn, publishing recoder to maven central, simpler build
system, ...
I would be glad to do it. Don't know how much you know about maven, but the migration would change the directory structure. Shall I just do the migration and send it to you as a patch so you can try it?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would be glad to do it. Don't know how much you know about maven, but
the migration would change the directory structure. Shall I just do the
migration and send it to you as a patch so you can try it?
While working on the migration I detected some problems. The tests depend on the examples.
I would suggest the following maven structure:
recoder-all // aggregation pom
|
|---- recoder
|
|---- recoder-examples
To implement this structure the dependencies to the examples have to be resolved. This should be done before the migration.
What do you think?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just remove the test cases that make trouble for now (but pleaes document
which those are, though I suppose that it's the "very old ones"). So,
please go ahead and make the necessary changes as you seem fit. I'll re-add
the tests later on.
Personally, I run tests from within Eclipse, and the ANT-scripts are not
maintained (I use them only to make the release builds).
While working on the migration I detected some problems. The tests depend
on the examples.
I would suggest the following maven structure:
recoder-all // aggregation pom
|
|---- recoder
|
|---- recoder-examples
To implement this structure the dependencies to the examples have to be
resolved. This should be done before the migration.
What do you think?
I moved the according tests to recorder-examples instead of deleting them. But I have to rework some of them so they don't fail because of the new structure.
PS: It would be easyier and and safer to work with git or mercurial. Are you interested in changing the VCS?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I gave it some thought. I see git's advantage in improved branch handling,
so I don't see that a big advantage using it for recoder right now. There
simply isn't that much concurrent programming going on. I have never used
Mercurial so I can't say anything about it.
I moved the according tests to recorder-examples instead of deleting them.
But I have to rework some of them so they don't fail because of the new
structure.
PS: It would be easyier and and safer to work with git or mercurial. Are
you interested in changing the VCS?
Hey guys,
have you ever thought about changing your build environment from Ant to Maven? Maven has a lot of usefull features recoder really needs, e.g. no libraries in svn, publishing recoder to maven central, simpler build system, ...
Regards,
Simon
Hi,
Sounds like a great idea, and it has actually been on my (internal)
suggestion list. However, I currently don't have time to do it - would you
be interested in contributing?
Regards,
Tobias
On Wed, Mar 12, 2014 at 2:23 PM, Simon E. Silva Lauinger simonsilvalauin@users.sf.net wrote:
I would be glad to do it. Don't know how much you know about maven, but the migration would change the directory structure. Shall I just do the migration and send it to you as a patch so you can try it?
Yes, please do so.
I am familiar with Maven so I know what to expect. Shouldn't take too much
time but there may be pitfalls, as always ;-)
/Tobias
On Wed, Mar 26, 2014 at 10:53 PM, Simon E. Silva Lauinger simonsilvalauin@users.sf.net wrote:
While working on the migration I detected some problems. The tests depend on the examples.
I would suggest the following maven structure:
recoder-all // aggregation pom
|
|---- recoder
|
|---- recoder-examples
To implement this structure the dependencies to the examples have to be resolved. This should be done before the migration.
What do you think?
Hi,
Just remove the test cases that make trouble for now (but pleaes document
which those are, though I suppose that it's the "very old ones"). So,
please go ahead and make the necessary changes as you seem fit. I'll re-add
the tests later on.
Personally, I run tests from within Eclipse, and the ANT-scripts are not
maintained (I use them only to make the release builds).
Regards,
Tobias
On Wed, Apr 9, 2014 at 9:06 PM, Simon E. Silva Lauinger simonsilvalauin@users.sf.net wrote:
I moved the according tests to recorder-examples instead of deleting them. But I have to rework some of them so they don't fail because of the new structure.
PS: It would be easyier and and safer to work with git or mercurial. Are you interested in changing the VCS?
Hi,
I gave it some thought. I see git's advantage in improved branch handling,
so I don't see that a big advantage using it for recoder right now. There
simply isn't that much concurrent programming going on. I have never used
Mercurial so I can't say anything about it.
Regards,
Tobias
On Wed, Apr 16, 2014 at 10:07 AM, Simon E. Silva Lauinger simonsilvalauin@users.sf.net wrote: