Maven Ant Tasks Work

[Jason van Zyl <ja...@maven.org>]

Hi,

Thanks to a big push by Herve Boutemy we have a lot of improvements  
to the Maven Ant Tasks and accompanying documentation. We can  
probably do another release shortly.

Herve, if you want to continue with some work on the tasks I think if  
we focus on cleaning up the actual Ant task code and correcting the  
issues there then we can tackle some bigger issues. The one thing  
that is sorely lacking are some tests of the tasks. Is there a  
standard testing harness for Ant tasks that we could employ? Also if  
you have any categories you want to add to JIRA to make tracking  
issues easier let me know and I'll add them. For anyone interested in  
the issues you can find them here:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&mode=hide&sorter/order=DESC&sorter/ 
field=priority&resolution=-1&pid=11533&fixfor=-1

After a little more cleanup I would like to use the Embedder in the  
trunk version and create a facade for the Embedder in the branch so  
that we can at least keep the Ant task code in sync. If all access is  
then done through the embedder and embedder facade then it should be  
manageable to keep them in sync. I would like to hide all the  
artifact resolution details and after looking at the code for a we do  
need full integration with Maven itself. We need to use POMs and  
Settings and the behavior there has to be the same as it is in Maven  
so that when people migrate completely over to Maven the behavior  
remains consistent.

I think we can do a release with all the fixes that have been made in  
last few days and then we can tackle adding some testing and using  
the embedder (or embedder facade). There are some suggestions for  
some very useful features like calculating the build order so people  
can do pseudo reactor builds in Maven. This gives people another  
bridge into Maven capabilities without making the full leap which  
makes migration easier.

Thanks for all your work Herve, the Ant tasks are starting to look  
and work a lot better.

Jason

----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------




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

Re: Maven Ant Tasks Work

[Hervé BOUTEMY <he...@free.fr>]

Le lundi 28 mai 2007, Jason van Zyl a écrit :
> > This time, Maven Ant Tasks 2.0.7 could be ready before Maven 2.0.7
> > itself :)
>
> Heh, yah we should probably just stick with 2.0.6.1 not to confuse
> people ... We need to come up with a standard versioning system for
> tools based on a fixed version of another tool.
Maven 2.0.7 is so far away?
If so, effectively, 2.0.6.1 will be the next Maven Ant Tasks version.

> > MANTTASKS-18 contains some simple tests. For more extended ones,
> > AntUnit seems
> > to be a good candidate: http://ant.apache.org/antlibs/antunit/.
> > I'll have to
> > try...
>
> Cool, I'll take a quick look and see if anyone else has some
> opinions. I don't mind heavily refactoring some bits but we need some
> tests first.
I just submitted patch (+doc) for MANTTASKS-29. The core patch is a new 
feature: a VersionMapper, to remove version numbers from jar filenames. It is 
useful when you're working with Ant and an IDE, and don't want that jar 
filenames change every time a version changes.

The patch also contains some tests about dependencies resolution, that show:
- junit exclusion works well: good
- but SNAPSHOT download with uniqueVersion doesn't work: here is the start for 
MANTTASKS-18 and more unit tests...
"ant -f sample.build.xml" is slowly evolving to true regression tests

> >> Also if
> >> you have any categories you want to add to JIRA to make tracking
> >> issues easier let me know and I'll add them.
> >
> > No, I have no idea for the moment.
I finally had an idea: please create a "documentation" category.
Other categories I can think of would be a category per task: dependencies, 
install, deploy, install-provider.

> >> I think we can do a release with all the fixes that have been made in
> >> last few days and then we can tackle adding some testing and using
> >> the embedder (or embedder facade).
> >
> > I'm really interested in SNAPSHOT handling, both for download und
> > deploy:
> > MANTTASKS-18, 23, 67. I don't know if Embedder is nedded for that.
> > But unit
> > tests are a first step I'll work on for MANTTASKS-18.
>
> Not needed for it, but we should start using it. Basically if you put
> all the required download functionality in a class called Embedder in
> the branch then you'll have something like we will on the trunk.
ok, I'll look at Maven Embedder in 2.1 to discover what the facade could look 
like. If I understand well, next patches will start to go in this direction

Hervé

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

Re: Maven Ant Tasks Work

[Jason van Zyl <ja...@maven.org>]

On 28 May 07, at 4:57 PM 28 May 07, Hervé BOUTEMY wrote:

> Le lundi 28 mai 2007, Jason van Zyl a écrit :
>> Hi,
>>
>> Thanks to a big push by Herve Boutemy we have a lot of improvements
>> to the Maven Ant Tasks and accompanying documentation.
> Thanks for your time committing patches.
>
>> We can probably do another release shortly.
> This time, Maven Ant Tasks 2.0.7 could be ready before Maven 2.0.7  
> itself :)
>

Heh, yah we should probably just stick with 2.0.6.1 not to confuse  
people ... We need to come up with a standard versioning system for  
tools based on a fixed version of another tool.

>>
>> Herve, if you want to continue with some work on the tasks I think if
>> we focus on cleaning up the actual Ant task code and correcting the
>> issues there then we can tackle some bigger issues. The one thing
>> that is sorely lacking are some tests of the tasks.
> That's the rationale behind MANTTASKS-69, then MANTTASKS-18 (I'll  
> have to
> rework it after MANTTASKS-69 has been commited).
>
>> Is there a standard testing harness for Ant tasks that we could  
>> employ?
> MANTTASKS-18 contains some simple tests. For more extended ones,  
> AntUnit seems
> to be a good candidate: http://ant.apache.org/antlibs/antunit/.  
> I'll have to
> try...
>

Cool, I'll take a quick look and see if anyone else has some  
opinions. I don't mind heavily refactoring some bits but we need some  
tests first.

>> Also if
>> you have any categories you want to add to JIRA to make tracking
>> issues easier let me know and I'll add them.
> No, I have no idea for the moment.
>
>> For anyone interested in the issues you can find them here:
>>
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?
>> reset=true&mode=hide&sorter/order=DESC&sorter/
>> field=priority&resolution=-1&pid=11533&fixfor=-1
>>
>> After a little more cleanup I would like to use the Embedder in the
>> trunk version and create a facade for the Embedder in the branch so
>> that we can at least keep the Ant task code in sync. If all access is
>> then done through the embedder and embedder facade then it should be
>> manageable to keep them in sync. I would like to hide all the
>> artifact resolution details and after looking at the code for a we do
>> need full integration with Maven itself. We need to use POMs and
>> Settings and the behavior there has to be the same as it is in Maven
>> so that when people migrate completely over to Maven the behavior
>> remains consistent.
> I don't really understand what the Embedder is, but the intend is very
> interesting.
>

Single point of entry for any Maven functionality.

>>
>> I think we can do a release with all the fixes that have been made in
>> last few days and then we can tackle adding some testing and using
>> the embedder (or embedder facade).
> I'm really interested in SNAPSHOT handling, both for download und  
> deploy:
> MANTTASKS-18, 23, 67. I don't know if Embedder is nedded for that.  
> But unit
> tests are a first step I'll work on for MANTTASKS-18.
>

Not needed for it, but we should start using it. Basically if you put  
all the required download functionality in a class called Embedder in  
the branch then you'll have something like we will on the trunk.

>> There are some suggestions for
>> some very useful features like calculating the build order so people
>> can do pseudo reactor builds in Maven. This gives people another
>> bridge into Maven capabilities without making the full leap which
>> makes migration easier.
>>
>> Thanks for all your work Herve, the Ant tasks are starting to look
>> and work a lot better.
> Thanks for your help.

No problem, thanks for all the patches and patience.

>
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------




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

Re: Maven Ant Tasks Work

[Hervé BOUTEMY <he...@free.fr>]

Le lundi 28 mai 2007, Jason van Zyl a écrit :
> Hi,
>
> Thanks to a big push by Herve Boutemy we have a lot of improvements
> to the Maven Ant Tasks and accompanying documentation.
Thanks for your time committing patches.

> We can probably do another release shortly.
This time, Maven Ant Tasks 2.0.7 could be ready before Maven 2.0.7 itself :)

>
> Herve, if you want to continue with some work on the tasks I think if
> we focus on cleaning up the actual Ant task code and correcting the
> issues there then we can tackle some bigger issues. The one thing
> that is sorely lacking are some tests of the tasks.
That's the rationale behind MANTTASKS-69, then MANTTASKS-18 (I'll have to 
rework it after MANTTASKS-69 has been commited).

> Is there a standard testing harness for Ant tasks that we could employ?
MANTTASKS-18 contains some simple tests. For more extended ones, AntUnit seems 
to be a good candidate: http://ant.apache.org/antlibs/antunit/. I'll have to 
try...

> Also if 
> you have any categories you want to add to JIRA to make tracking
> issues easier let me know and I'll add them.
No, I have no idea for the moment.

> For anyone interested in the issues you can find them here:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&mode=hide&sorter/order=DESC&sorter/
> field=priority&resolution=-1&pid=11533&fixfor=-1
>
> After a little more cleanup I would like to use the Embedder in the
> trunk version and create a facade for the Embedder in the branch so
> that we can at least keep the Ant task code in sync. If all access is
> then done through the embedder and embedder facade then it should be
> manageable to keep them in sync. I would like to hide all the
> artifact resolution details and after looking at the code for a we do
> need full integration with Maven itself. We need to use POMs and
> Settings and the behavior there has to be the same as it is in Maven
> so that when people migrate completely over to Maven the behavior
> remains consistent.
I don't really understand what the Embedder is, but the intend is very 
interesting.

>
> I think we can do a release with all the fixes that have been made in
> last few days and then we can tackle adding some testing and using
> the embedder (or embedder facade).
I'm really interested in SNAPSHOT handling, both for download und deploy: 
MANTTASKS-18, 23, 67. I don't know if Embedder is nedded for that. But unit 
tests are a first step I'll work on for MANTTASKS-18.

> There are some suggestions for 
> some very useful features like calculating the build order so people
> can do pseudo reactor builds in Maven. This gives people another
> bridge into Maven capabilities without making the full leap which
> makes migration easier.
>
> Thanks for all your work Herve, the Ant tasks are starting to look
> and work a lot better.
Thanks for your help.

>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org



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