Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <433BB0C0.3040706@apache.org>
Date: Thu, 29 Sep 2005 10:15:44 +0100
From: Steve Loughran <stevel@apache.org>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
MIME-Version: 1.0
To: Ant Developers List <dev@ant.apache.org>
Subject: Re: suggestion refactor SCM
References: <EA9D95F907E2924A9A32F274114BCDEF731516@perth.Cellectivity.local>
 <1127924669.30888.40.camel@echidna.inamo.no>
 <9e3862d805092816396bbd69fd@mail.gmail.com>
 <847C2ADC-41F9-4A1E-ADA2-F71326A8F5F6@gmail.com>
In-Reply-To: <847C2ADC-41F9-4A1E-ADA2-F71326A8F5F6@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Kev Jackson wrote:
> 
> On 29 Sep 2005, at 06:39, Brett Porter wrote:
> 
>> I'd also agree with that. We fully intended to make Maven2 plugins
>> work as Ant tasks :)
>>
>> So with a wrapper,
>> http://maven.apache.org/maven2/scm/maven-scm-plugin/
>> these goals would become tasks and their parameters would match up
>> what's on the individual pages.
>>
>> Thoughts?
> 
> 
> Just a worry about dependencies.  If Ant has to rely on other code  from 
> within maven for a set of maven plugins to run, we end up with a  
> horrible interdependency (Maven needs Ant <-> Ant needs some % of  
> Maven) just to compile ant.  Could get nasty.  But I agree if the  work 
> is there and the code can be taken and made common between  projects, 
> why not?


Not needed to build, only to run the SCM stuff. I'm already working with 
stuff from many places, which is the main reason my gump projects are so 
unreliable (that and the XmlBeans willingness to remove attributes from 
shipping tasks, but the forthcoming <hasMethod> condition will deal with 
that)

...
<project name="sftasks"
   xmlns:ac="antlib:net.sf.antcontrib"
   xmlns:sf="antlib:org.smartfrog.tools.ant"
   xmlns:m2="antlib:org.apache.maven.artifact.ant"
   >

One thing we do have to have is ant task tests in maven, which means 
that the ant team has to put the ant-testutils.jar up on the repository, 
and work out how to run those tests under m2

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org