Regarding Maven, I did a complete build of Tuscany 2.0-beta2 RC1 with Maven
3 and I've been surprised to see the performance improvement. Beside that,
you can use it with something like "-T 5C" (5 threads per core) and it does
parallel builds where possible. All I had to do is to remove the
<layout>legacy</layout> line for the Maven 1 Repo and it worked. It seems
like we can make our poms both Maven 2 and Maven 3 compliant with minimal
changes so we won't affect any of our users.

I've also tried to run the itests from the root of the itest folder and
Maven 3 complained about each and every pom that had incorrect parent
relativePath (parents are not required anymore in Maven 3 but accepts them
for backwards compatibility) so that will also help detecting our parent
path problems.

I'm going to proceed with the necessary changes in order to enable us to use
Maven 2 or 3 without any changes. Let me know your thoughts on this. Is the
ASF Hudson able to run Maven 3 builds? That could improve the build time...

On Wed, Jan 26, 2011 at 12:04 PM, ant elder <[email protected]> wrote:

> On Sat, Jan 22, 2011 at 2:25 PM, ant elder <[email protected]> wrote:
>
> > The problem with doing that is that now the OASIS repo is also checked
> > for every artifact when building online which could add significantly
> > to the total build time.
> >
> > Looking at the current repository definitions i think most of those
> > are old historical ones which we don't even need anymore so i'm going
> > to have a go a cleaning them up. For the ones we do still need i think
> > we should change to define them in the modules that actually require
> > them instead of the top level pom.xml as that should avoid them being
> > queried for irrelevant artifacts.
> >
>
> I've just committed a change to do that and remove a lot of the other
> repository definitions. A full build from an empty repo is working for
> me and i'll kick off a hudson one to see how that goes. I had to do
> quite a lot of builds with an empty repo to find all the issues and it
> does seem faster a more reliable now without those. There's one
> module, testing\itest\ws\external-client, that still uses the java.net
> Maven 1.x Repository which is really slow and often times out, its
> required to get jaxws-rt 2.1.7 so it would be good to try to get the
> test working with a more recent jaxws-rt version that is in the
> central repo.
>
>   ...ant
>

Reply via email to