You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/01/18 16:43:28 UTC

[jira] Created: (MNG-112) m2 reactor recurses too deep

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-112

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-112
    Summary: m2 reactor recurses too deep
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2

   Assignee: 
   Reporter: Dan Diephouse

    Created: Tue, 18 Jan 2005 10:42 AM
    Updated: Tue, 18 Jan 2005 10:42 AM

Description:
It'd be great if when I have a reactory build, m2 didn't dig too deep to find poms.  For instance, say I have a sub project which holds a template pom in src/main/resources/pom.xml - currently m2 will try to execute the goal for that pom. This shouldn't happen IMO.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Updated: (MNG-112) m2 reactor recurses too deep

Posted by ji...@codehaus.org.
The following issue has been updated:

    Updater: Jason van Zyl (mailto:jvanzyl@maven.org)
       Date: Thu, 27 Jan 2005 4:40 PM
    Changes:
             Fix Version changed to 1.0-alpha-1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MNG-112?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-112

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-112
    Summary: m2 reactor recurses too deep
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:
             1.0-alpha-1

   Assignee: 
   Reporter: Dan Diephouse

    Created: Tue, 18 Jan 2005 10:42 AM
    Updated: Thu, 27 Jan 2005 4:40 PM

Description:
It'd be great if when I have a reactory build, m2 didn't dig too deep to find poms.  For instance, say I have a sub project which holds a template pom in src/main/resources/pom.xml - currently m2 will try to execute the goal for that pom. This shouldn't happen IMO.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Updated: (MNG-112) m2 reactor recurses too deep

Posted by ji...@codehaus.org.
The following issue has been updated:

    Updater: Jason van Zyl (mailto:jvanzyl@maven.org)
       Date: Thu, 27 Jan 2005 4:41 PM
    Changes:
             Version changed to 1.0-alpha-1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MNG-112?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-112

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-112
    Summary: m2 reactor recurses too deep
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:
             1.0-alpha-1
   Versions:
             1.0-alpha-1

   Assignee: 
   Reporter: Dan Diephouse

    Created: Tue, 18 Jan 2005 10:42 AM
    Updated: Thu, 27 Jan 2005 4:41 PM

Description:
It'd be great if when I have a reactory build, m2 didn't dig too deep to find poms.  For instance, say I have a sub project which holds a template pom in src/main/resources/pom.xml - currently m2 will try to execute the goal for that pom. This shouldn't happen IMO.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Closed: (MNG-112) m2 reactor recurses too deep

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-112?page=history ]
     
Brett Porter closed MNG-112:
----------------------------

    Resolution: Won't Fix

use modules

> m2 reactor recurses too deep
> ----------------------------
>
>          Key: MNG-112
>          URL: http://jira.codehaus.org/browse/MNG-112
>      Project: m2
>         Type: Bug
>     Versions: 1.0-alpha-1
>     Reporter: Dan Diephouse
>     Priority: Minor
>      Fix For: 1.0-alpha-1

>
>
> It'd be great if when I have a reactory build, m2 didn't dig too deep to find poms.  For instance, say I have a sub project which holds a template pom in src/main/resources/pom.xml - currently m2 will try to execute the goal for that pom. This shouldn't happen IMO.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Updated: (MNG-112) m2 reactor recurses too deep

Posted by ji...@codehaus.org.
The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Sun, 6 Feb 2005 6:19 PM
    Changes:
             priority changed from Major to Minor
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MNG-112?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-112

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-112
    Summary: m2 reactor recurses too deep
       Type: Bug

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:
             1.0-alpha-1
   Versions:
             1.0-alpha-1

   Assignee: 
   Reporter: Dan Diephouse

    Created: Tue, 18 Jan 2005 10:42 AM
    Updated: Sun, 6 Feb 2005 6:19 PM

Description:
It'd be great if when I have a reactory build, m2 didn't dig too deep to find poms.  For instance, say I have a sub project which holds a template pom in src/main/resources/pom.xml - currently m2 will try to execute the goal for that pom. This shouldn't happen IMO.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MNG-112) m2 reactor recurses too deep

Posted by ji...@codehaus.org.
The following comment has been added to this issue:

     Author: Brett Porter
    Created: Tue, 18 Jan 2005 3:04 PM
       Body:
yes, it picks up stuff in target in maven-scm too.

Maybe the algorithm should be:
1. find all poms in subdirectories of current (*/pom.xml)
2. for each of these poms, run 1. and 2. again

That's assuming a bit though. Maybe we need to discuss a different method altogether. Currently, the POMs are used as parent poms, and there is no master build pom (it is implied in -r). If the master build required settings, that'd be a problem.

Perhaps we should have a master build that declares all the poms it aggregates. This would remove the need for -r altogether and allow configuration to be set for the aggregation project.

That said, I think Jason wants -r to be able to arbitrarily build a set of projects easily, so maybe both are needed, and -r uses the algorithm above.


---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MNG-112?page=comments#action_29048

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-112

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-112
    Summary: m2 reactor recurses too deep
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2

   Assignee: 
   Reporter: Dan Diephouse

    Created: Tue, 18 Jan 2005 10:42 AM
    Updated: Tue, 18 Jan 2005 3:04 PM

Description:
It'd be great if when I have a reactory build, m2 didn't dig too deep to find poms.  For instance, say I have a sub project which holds a template pom in src/main/resources/pom.xml - currently m2 will try to execute the goal for that pom. This shouldn't happen IMO.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira