You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/05/21 02:40:57 UTC

[jira] Commented: (CONTINUUM-63) "update pom" action updates whole source tree

     [ http://jira.codehaus.org/browse/CONTINUUM-63?page=comments#action_39454 ]
     
Brett Porter commented on CONTINUUM-63:
---------------------------------------

I don't understand...

There used to be an "Update POM" action in Continuum (I don't think I've seen it this year though), which was handy to update your project descriptor from the accompanying codebase.

The problem it had was it updated the entire source tree, instead of doing an SCM update on just the pom then reloading it, which was much too slow for a web based action, and unnecessary because the SCM update would happen next build.

So what is the solution to this now - where the pom has changed and you want continuum to pick up the changes? just run another build?

> "update pom" action updates whole source tree
> ---------------------------------------------
>
>          Key: CONTINUUM-63
>          URL: http://jira.codehaus.org/browse/CONTINUUM-63
>      Project: Continuum
>         Type: Improvement
>   Components: continuum-core
>     Reporter: Brett Porter
>     Assignee: Trygve Laugstol
>     Priority: Minor
>      Fix For: 1.0-alpha-2

>
>
> this should instead just update the pom itself for speed. The project need only be updated when building

-- 
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