You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Mark Proctor (JIRA)" <ji...@codehaus.org> on 2005/11/27 05:21:06 UTC
[jira] Created: (MNG-1694) Build execution order control in fine grained projects.
Build execution order control in fine grained projects.
-------------------------------------------------------
Key: MNG-1694
URL: http://jira.codehaus.org/browse/MNG-1694
Project: Maven 2
Type: Wish
Components: maven-compiler-plugin
Reporter: Mark Proctor
Currently in multi module projects you can only work in 2 modes.
1) Build everything
2) Build a single module, IF you have built and installed all its dependency modules
I would like to be able to work the following way:
1) Build everything
2) Build an individual module, will build all the modules prior to it in the reactor list.
3) Build a module module and all modules after it in the reactor list, will build missing prior modules.
Use Case
1) perform checkout and build
2) module fails
3) keep fixing module and running just its unit tests
3) once all its unit tests pass build it and all modules after it in the reactor list. I don't need to build ones prior as they are unnaffected by the changes.
In large mutli module projects this will save a LOT of time especially when you are gearing up for deployment and want to check that everything works - currently this is time consuming and repetitive, with much of the repetition uneeded.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1694) Build execution order control in fine grained projects.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1694?page=comments#action_52112 ]
Brett Porter commented on MNG-1694:
-----------------------------------
I think what you really want here is
- build this project and its *dependencies* inside this workspace
- continue from last failed build
Both reasonable ideas, but I also worry about introducing this kind of multi-mode operation too much. I would prefer to work on the ability to make some builds simply skip by as the files are unchanged. This makes the behaviour the same always and protects the user from their own error in not knowing what is updated.
> Build execution order control in fine grained projects.
> -------------------------------------------------------
>
> Key: MNG-1694
> URL: http://jira.codehaus.org/browse/MNG-1694
> Project: Maven 2
> Type: Wish
> Components: maven-compiler-plugin
> Reporter: Mark Proctor
>
>
> Currently in multi module projects you can only work in 2 modes.
> 1) Build everything
> 2) Build a single module, IF you have built and installed all its dependency modules
> I would like to be able to work the following way:
> 1) Build everything
> 2) Build an individual module, will build all the modules prior to it in the reactor list.
> 3) Build a module module and all modules after it in the reactor list, will build missing prior modules.
> Use Case
> 1) perform checkout and build
> 2) module fails
> 3) keep fixing module and running just its unit tests
> 3) once all its unit tests pass build it and all modules after it in the reactor list. I don't need to build ones prior as they are unnaffected by the changes.
> In large mutli module projects this will save a LOT of time especially when you are gearing up for deployment and want to check that everything works - currently this is time consuming and repetitive, with much of the repetition uneeded.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1694) Build execution order control in fine grained projects.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1694?page=all ]
Brett Porter updated MNG-1694:
------------------------------
Component: (was: maven-compiler-plugin)
Reactor and workspace
> Build execution order control in fine grained projects.
> -------------------------------------------------------
>
> Key: MNG-1694
> URL: http://jira.codehaus.org/browse/MNG-1694
> Project: Maven 2
> Type: Wish
> Components: Reactor and workspace
> Reporter: Mark Proctor
>
>
> Currently in multi module projects you can only work in 2 modes.
> 1) Build everything
> 2) Build a single module, IF you have built and installed all its dependency modules
> I would like to be able to work the following way:
> 1) Build everything
> 2) Build an individual module, will build all the modules prior to it in the reactor list.
> 3) Build a module module and all modules after it in the reactor list, will build missing prior modules.
> Use Case
> 1) perform checkout and build
> 2) module fails
> 3) keep fixing module and running just its unit tests
> 3) once all its unit tests pass build it and all modules after it in the reactor list. I don't need to build ones prior as they are unnaffected by the changes.
> In large mutli module projects this will save a LOT of time especially when you are gearing up for deployment and want to check that everything works - currently this is time consuming and repetitive, with much of the repetition uneeded.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1694) Build execution order control in fine grained projects.
Posted by "Mark Proctor (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1694?page=comments#action_52114 ]
Mark Proctor commented on MNG-1694:
-----------------------------------
skipping is fine by me, as long as its fast. Thats what I did for M1, I implemented my own build goal that iterates the reactor and calls jar:jar if a jar doesn't exist.
> Build execution order control in fine grained projects.
> -------------------------------------------------------
>
> Key: MNG-1694
> URL: http://jira.codehaus.org/browse/MNG-1694
> Project: Maven 2
> Type: Wish
> Components: Reactor and workspace
> Reporter: Mark Proctor
>
>
> Currently in multi module projects you can only work in 2 modes.
> 1) Build everything
> 2) Build a single module, IF you have built and installed all its dependency modules
> I would like to be able to work the following way:
> 1) Build everything
> 2) Build an individual module, will build all the modules prior to it in the reactor list.
> 3) Build a module module and all modules after it in the reactor list, will build missing prior modules.
> Use Case
> 1) perform checkout and build
> 2) module fails
> 3) keep fixing module and running just its unit tests
> 3) once all its unit tests pass build it and all modules after it in the reactor list. I don't need to build ones prior as they are unnaffected by the changes.
> In large mutli module projects this will save a LOT of time especially when you are gearing up for deployment and want to check that everything works - currently this is time consuming and repetitive, with much of the repetition uneeded.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org