[jboss-dev] Re: AOP Mavenization

[Kabir Khan]

Hi Paul,

I'll try to take a proper look over the next few days, but here are a 
few initial points/questions:

* Does the build-tests-jdk50-maven.xml file basically work the same as 
the old build file, apart from referencing stuff from the maven 
repository? I am glad that we stuck with ant for the tests since they 
are quite complex.

*Regarding this
    !-- TODO: does this still need to be imported? -->
    <import file="base-tests-maven.xml"/>
The answer is yes, although I think it should still reference 
"base-tests.xml". This file lists all the tests that can be run in all 
weaving configurations.

- In the build/ folder we have a task to build and package a full 
release, how will that be managed? We want everything to be named the 
same as they are in that release at present, i.e. we don't want to have 
to update all the scripts that are part of the distribution etc. to use 
the maven naming conventions with a version on the end. Or will we still 
be packaging the releases with ant?

Cheers,

Kabir

Paul Gier wrote:
> Hey Kabir and Flavia,
> When you have a chance this week can either of you take a look at the 
> maven build and the ant script that I created to run the tests against 
> the maven generated files?  From the aop subdirectory, just do "mvn 
> install" followed by "ant -f build-tests-jdk50-maven.xml".
> 
> Also let me know if there is anything missing from the build that still 
> needs to be mavenized.  I'd like to finish migration to maven for  aop 
> within the next week or two.
> 
> Thanks!

-- 
Kabir Khan
JBoss AOP Lead
JBoss, a division of Red Hat