[ http://jira.codehaus.org/browse/CONTINUUM-165?page=comments#action_40155 ] Bj�rn Sk�ld commented on CONTINUUM-165: ---------------------------------------
It is not a null goal, it's the cmdline arguments. They seem to be initialized to the empty string, and then changed to null when project settings are changed. I solved this on my install by adding a nullcheck in MavenOneBuildExecutor.java. I'll attach a patch with my changes. The patch also fixes a problem that the goals are reinitialized to the defaults after each build. > goal null after editing a project > --------------------------------- > > Key: CONTINUUM-165 > URL: http://jira.codehaus.org/browse/CONTINUUM-165 > Project: Continuum > Type: Bug > Versions: 1.0-alpha-2 > Reporter: Aleksander Blomsk�ld > Fix For: 1.0-beta-1 > Attachments: CONTINUUM-165.diff > > > If I go to the edit-page and press submit (I don't really need to edit > anything) this error is printed at console: > 2005-05-26 11:29:45,085 [PoolThread-0] ERROR VelocityComponent - RHS of #set > statement is null. Context will not be modified. screens/Summary.vm [line 1, > column 1] > A null-goal (which is not visible at the edit page) is added when I try to > build the project: > 2005-05-26 11:36:12,167 [Thread-4] INFO ShellCommandHelper - Executing: > maven null clean:clean jar:install -- 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
