Maven 2.x Ant Tasks

<artifact:dependencies> spawns non-daemon thread

Details

  • Number of attachments :
    0

Description

When <artifact:dependencies> is run, DefaultArtifactResolver creates a thread pool using non-daemon threads. Thus live threads are left in the thread group after the task supposedly finishes. This can cause problems in containers such as NetBeans.

The fix MNG-4738 is already in Maven 3.0; you just need to use Maven 3 in the task's dependencies, rather than 2.2.1 as now.

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. MNG-4738 DefaultArtifactResolver forks non-daemon threads

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is depended upon by

Bug - A problem which impairs or prevents the functions of the product. GROOVY-4562 antbuilder does not work well with maven-ant-tasks

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Hide
Permalink
Paul King added a comment -

I suspect it affects all embedded usage of the maven ant tasks.
It certainly affects Groovy's AntBuilder as per:

http://jira.codehaus.org/browse/GROOVY-4562

Show
Paul King added a comment - I suspect it affects all embedded usage of the maven ant tasks. It certainly affects Groovy's AntBuilder as per: http://jira.codehaus.org/browse/GROOVY-4562

People

  • Assignee:
    Unassigned
    Reporter:
    Jesse Glick
Vote (2)
Watch (3)

Dates

  • Created:
    Updated: