Ticket #226 (closed administrative task: fixed)
Change project structure to support maven modules
| Reported by: | kasper | Owned by: | kasper |
|---|---|---|---|
| Priority: | high | Milestone: | DataCleaner 1.5 |
| Component: | DataCleaner-core | Keywords: | |
| Cc: | |||
| Influenced classes: | |||
Description
As it is right now, DataCleaner consists of several independent projects. This works quite alright but generates some overhead such as updating versions in several places etc.
I propose that we switch to a module based project structure. This will require a parent project (just called DataCleaner) and several sub projects (core, gui, webmonitor)
Here's some more info on module based project structures:
Also, this would make it possible for us to cut out all the packaging of the GUI component into a seperate project (or perhaps the parent project) which would make our POMs much easier to understand.
It will probably have great consequences for our SVN folder structure, but better now than later.
Change History
comment:2 Changed 3 years ago by kasper
- Status changed from assigned to closed
- Resolution set to fixed
Fixed.
The project is now SVN hosted at: http://eobjects.dk/svn/DataCleaner/trunk/ Old project has been moved to: http://eobjects.dk/svn/misc/old-datacleaner-seperate-projects/
A module based parent project has been created in SVN now. The new URL is:
This has been done in the revisions: [600] - [620].
I'll try working with the new parent project for the next couple of tickets and then evaluate which is better.