Maven 2.x Ant Tasks

Maven 2.0.5 needs Maven 2.0.5 Tasks for Ant and Maven 2.0.5 Embedder for everything to remain sane

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0.6
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    2

Description

I am moving my project from Maven plus Antlib to pure Maven, maybe.

Right now I have a super pom with a dependencyManagement element. When I copied it and pasted that tag to the child pom used by Antlib it did not work. Now, because I am using Maven 2.0.5 and Antlib 2.0.4 I don't know whether the model format has changed or whether dependencyManagement never worked for Antlib.

Similarly we are using TeamCity 2.0EAP. Because of problems in 2.04 they upgraded to the prerelease 2.1, skipping 2.05 which of course does not exist. Now we have a problem that occurs in 2.1 which does not happen in 2.0.5. This has forced us back to TeamCity 1.2.

But the issue is that the Maven family should remain compatible. The only way to do that is to release all together. Instead we are using three versions of Maven, each with their idiosyncratic bugs and features.

I think it is an error to release a new version of core Maven without the others, which is why this is a bug and not a feature request.

The following email exchange mentions Jason will create a JIRA. I went looking for it but could not find it, so created this one.

Re: Ant Maven Tasks
Jason van Zyl
Wed, 21 Feb 2007 06:40:26 -0800

On 21 Feb 07, at 2:54 AM 21 Feb 07, Paul King wrote:

Hi,

I couldn't find any info regarding the status of the ant maven tasks
wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?

As already pointed out they will be released separately from Maven itself. They need some love, the Ant code itself has not changed at all so we simply could do a release with the new 2.0.5 code. If there is a lot of demand I'll look into it. I'll JIRA for it later this week and people can vote. We're making lots of headway doing plugin releases and I would still like to get 2.0.6 and 2.1-alpha-1 out relatively shortly so I probably won't have a ton of time to prepare a release. Someone else might though.

Jason.

Cheers, Paul.

Attachments

  1. Text File
    maven-ant-tasks.patch
    24/Mar/07 2:30 PM
    9 kB
    Herve Boutemy

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ben Speakmon added a comment -

My company is preparing a release, and our build system is already 2.0.5. Some bits of it are older and still use ant and getting rid of them isn't an option. Is this a priority for anyone right now?

If not, well, I'm going to have to get the ant tasks working with 2.0.5 for our builds anyway, probably sooner rather than later. My company is willing to let me contribute my fixes upstream as well, assuming the time investment isn't too large. Can someone point me in the right direction?

Show
Ben Speakmon added a comment - My company is preparing a release, and our build system is already 2.0.5. Some bits of it are older and still use ant and getting rid of them isn't an option. Is this a priority for anyone right now? If not, well, I'm going to have to get the ant tasks working with 2.0.5 for our builds anyway, probably sooner rather than later. My company is willing to let me contribute my fixes upstream as well, assuming the time investment isn't too large. Can someone point me in the right direction?
Hide
Permalink
Ben Speakmon added a comment -

Took a whirl at this, and after running mvn assembly:assembly in the maven-artifact-ant directory, I got my jar. Seems to work fine.

Are there any code changes required for this, or is it just a question of someone finding the time to run the release?

For us devs, I just wanted to point out that building it yourself is trivial.

Show
Ben Speakmon added a comment - Took a whirl at this, and after running mvn assembly:assembly in the maven-artifact-ant directory, I got my jar. Seems to work fine. Are there any code changes required for this, or is it just a question of someone finding the time to run the release? For us devs, I just wanted to point out that building it yourself is trivial.
Hide
Permalink
Herve Boutemy added a comment -

Here is a Maven Ant Tasks build for 2.0.5, built by:
1. exporting 2.0.5 tag for maven-artifact-ant
2. modifying pom.xml: changed every 2.0.2 dependancy to 2.0.5
3. running "mvn assembly:assembly"
Et voila, maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar

I tested it on a simple case, and it worked fine.
I'll do more intensive tests on monday, wih Ant buildfiles that fail with Maven Ant Tasks 2.0.4.

Show
Herve Boutemy added a comment - Here is a Maven Ant Tasks build for 2.0.5, built by: 1. exporting 2.0.5 tag for maven-artifact-ant 2. modifying pom.xml: changed every 2.0.2 dependancy to 2.0.5 3. running "mvn assembly:assembly" Et voila, maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar I tested it on a simple case, and it worked fine. I'll do more intensive tests on monday, wih Ant buildfiles that fail with Maven Ant Tasks 2.0.4.
Hide
Permalink
Jason van Zyl added a comment -

These don't live in maven-artifact-ant anymore. I would love some help cleaning them up. But they are here now:

http://svn.apache.org/repos/asf/maven/ant-tasks/trunk/

Show
Jason van Zyl added a comment - These don't live in maven-artifact-ant anymore. I would love some help cleaning them up. But they are here now: http://svn.apache.org/repos/asf/maven/ant-tasks/trunk/
Hide
Permalink
Herve Boutemy added a comment -

ok, I made same changes on maven-ant-tasks, reverting its dependancy from Maven 2.1-SNAPSHOT to 2.0.5.
The resulting maven-ant-tasks-1.0-SNAPSHOT-dep.jar is totally equivalent to my previous maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar.

I don't know what you meant by "cleaning them up": I don't find that I cleaned anything, but just made it work with Maven 2.0.5.
Hope this is what you expected...

Show
Herve Boutemy added a comment - ok, I made same changes on maven-ant-tasks, reverting its dependancy from Maven 2.1-SNAPSHOT to 2.0.5. The resulting maven-ant-tasks-1.0-SNAPSHOT-dep.jar is totally equivalent to my previous maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar. I don't know what you meant by "cleaning them up": I don't find that I cleaned anything, but just made it work with Maven 2.0.5. Hope this is what you expected...
Hide
Permalink
Herve Boutemy added a comment -

FYI my "more intensive tests on monday" have been done with success: maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar works better than Maven Ant Tasks 2.0.4 for me.
Now let's work on maven-ant-tasks to get a 1.0 release...

Show
Herve Boutemy added a comment - FYI my "more intensive tests on monday" have been done with success: maven-artifact-ant-2.0.5-SNAPSHOT-dep.jar works better than Maven Ant Tasks 2.0.4 for me. Now let's work on maven-ant-tasks to get a 1.0 release...
Hide
Permalink
Jason van Zyl added a comment -

I have updated the tasks to match what is in 2.0.6. Created an uber jar and deployed here:

http://idisk.maven.org/jvanzyl/Public/maven/

Give them a whirl, they appear to be working.

Show
Jason van Zyl added a comment - I have updated the tasks to match what is in 2.0.6. Created an uber jar and deployed here: http://idisk.maven.org/jvanzyl/Public/maven/ Give them a whirl, they appear to be working.
Hide
Permalink
Jason van Zyl added a comment -

Patch applied and this will go out with 2.0.6.

Show
Jason van Zyl added a comment - Patch applied and this will go out with 2.0.6.
Hide
Permalink
Herve Boutemy added a comment -

working perfectly for me: great!!!

Show
Herve Boutemy added a comment - working perfectly for me: great!!!

People

Vote (4)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.