|
| Re: Build Process [message #901578 is a reply to message #895714] |
Mon, 13 August 2012 13:51   |
 Herbert Neureiter
Messages: 3
Registered: August 2012 |
Junior Member |
|
|
Hi Florian,
the reason for the usage of Ivy is twofold:
- Ivy is used for generating POMs needed to publish build artifacts. At the time when the build process was designed, Maven had some shortcomings in this area. This is why we decided to use Ivy for this kind of tasks.
- The original build files that evolved into what now is the Stardust build were plain ant files without any Maven or Ivy usage. These contain quite some procedural logic that is not trivial to describe in Maven terms. For time constraints we decided to do the migration to Maven peacemeal and use Ivy as a bridge technology to make both approaches compatible.
Mid-term we are planning to migrate to a full Maven build and eliminate Ivy. To my regret, currently other threads are somewhat higher in priority which is why this has not been completed yet.
Your offer to help with the conversion is very welcome, though. However, it might not be an easy topic to get into, especially if one looks at the build process as a whole. Concentrating on only one part or component at a time would likely make things easier. Do you have any favourite components or parts of the build process that are particularaly important or already well known to you?
Herbert
[Updated on: Mon, 13 August 2012 13:53] Report message to a moderator |
|
|
|
|
Powered by
FUDForum. Page generated in 0.03003 seconds
] 
Search
Help
Register
Login
Home
