We don't currently have any plans to develop a maven2 build but that doesnn't mean we won't 
Out of interest how have you found maven2? Is it better/easier/quicker than maven 1.x?
We would certainly be interested in anything you have to offer in terms of maven build scripts, it may get integrated sooner rather than later then :wink:
Out of interest how have you found maven2? Is it better/easier/quicker than maven 1.x?
We would certainly be interested in anything you have to offer in terms of maven build scripts, it may get integrated sooner rather than later then :wink:
Maven2 is a completely different environment than maven 1.x.
Maven team claims maven2 builds faster than ant, and while I am not 100% convinced, I wouldn't shocked if it indeed is the case.
Our project contains (currently) 7 sub-projects (one of which is alfresco build for depedency management). When we were on maven 1.1 (no alfresco at that time), the build could take as long as 5 minutes when it was running online. If running it in offline mode, it would take about 3 minute. The build time included some basic junit tests.
With maven 2.x, the whole build, as well as building war/jar etc takes about minute and half. I could tweak the build setting if i don't need to run unit tests or build war, etc, and i can cut it down to 30 secs or so. Big improvement I should say.
Considering alfresco contains A LOT OF dependencies, and I don't mean to be too presumptious, but quite frankly I would suspect some of the dependencis, you guys don't even know which version you are using. (I had to track down odf_utils and compared the file size to find which version you were using). Plus if alfresco is going to pitch embeded deploy model, I think it makes a very good sense that you guys can say which depedencies you are using etc and make sure you are not breaching any license issue. For example, currently alfresco is being distributed along with some of the java specs such as java mail, activation, which from my understanding, is not allowed. So having a good snapshot of which dependencies you are using, it will help you guys I think (and in turn vendors like us).
Pros:
- Transitive depdency management (but this could be a con too)
- More structurally sound multi-project support
- More controlled management of plugins (means it lacks some plugins but thigns are more stable).
- Very good support for eclipse.
Cons:
- If the depedencies are not found in the maven central repository, you have to maintain your own repository as well.
- Unless you learn maven well, the build time could still be slow. (You need to learn the various flags as well as understanding of mirror repository sites etc to optimize your build).
- Syncing up maven build with eclipse build can still be tricky (but we are now 99% integrated with maven/eclipse/eclipse webtools currently).
- Maven 2 is a complete rewrite. The concept is same as 1.1, but you will need to learn almost from the scratch (but it's that big of a deal either).
Where can I post our maven build files?
Maven team claims maven2 builds faster than ant, and while I am not 100% convinced, I wouldn't shocked if it indeed is the case.
Our project contains (currently) 7 sub-projects (one of which is alfresco build for depedency management). When we were on maven 1.1 (no alfresco at that time), the build could take as long as 5 minutes when it was running online. If running it in offline mode, it would take about 3 minute. The build time included some basic junit tests.
With maven 2.x, the whole build, as well as building war/jar etc takes about minute and half. I could tweak the build setting if i don't need to run unit tests or build war, etc, and i can cut it down to 30 secs or so. Big improvement I should say.
Considering alfresco contains A LOT OF dependencies, and I don't mean to be too presumptious, but quite frankly I would suspect some of the dependencis, you guys don't even know which version you are using. (I had to track down odf_utils and compared the file size to find which version you were using). Plus if alfresco is going to pitch embeded deploy model, I think it makes a very good sense that you guys can say which depedencies you are using etc and make sure you are not breaching any license issue. For example, currently alfresco is being distributed along with some of the java specs such as java mail, activation, which from my understanding, is not allowed. So having a good snapshot of which dependencies you are using, it will help you guys I think (and in turn vendors like us).
Pros:
- Transitive depdency management (but this could be a con too)
- More structurally sound multi-project support
- More controlled management of plugins (means it lacks some plugins but thigns are more stable).
- Very good support for eclipse.
Cons:
- If the depedencies are not found in the maven central repository, you have to maintain your own repository as well.
- Unless you learn maven well, the build time could still be slow. (You need to learn the various flags as well as understanding of mirror repository sites etc to optimize your build).
- Syncing up maven build with eclipse build can still be tricky (but we are now 99% integrated with maven/eclipse/eclipse webtools currently).
- Maven 2 is a complete rewrite. The concept is same as 1.1, but you will need to learn almost from the scratch (but it's that big of a deal either).
Where can I post our maven build files?
We don't currently have any plans to develop a maven2 build but that doesnn't mean we won't
Out of interest how have you found maven2? Is it better/easier/quicker than maven 1.x?
We would certainly be interested in anything you have to offer in terms of maven build scripts, it may get integrated sooner rather than later then :wink:
