History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-2307
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: 3 3
Assignee: Unassigned
Reporter: Daniel Ostermeier
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

Clone with env variable: java.lang.NullPointerException

Created: 28/Jan/10 05:46 PM   Updated: 02/Feb/10 12:44 AM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.1.16

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
Another bug I just found in ver. 2.15

1. create a template with default recipes and msbuild task with ENV variable! (probably any type of task would work)
2. create a project as child.
3. try to clone the msbuild task within the recipes.. (try it within template or project too)
4. notice the error: java.lang.NullPointerException

- doing the same works if the task has no environment variables (or when I hide the inherited one and then it works)
- probably the template not even required to reproduce it

 All   Comments   Work Log   Change History      Sort Order:
Daniel Ostermeier - 28/Jan/10 07:04 PM
and another one regarding cloning:

1. create a template
2. create a build stage (ie. release)
3. clone the stage (ie. debug)
4. create a child project
5. go to the project build stages:
6. notice that it is impossible to view/modify the stages, the list tree not even shows the configurations, and the detailed build stage views shows different actions for the orig and cloned stage

- removing the clone from template and create a new stage (but not clone) works well


Daniel Ostermeier - 01/Feb/10 09:55 PM
Regarding the first of the two issues, the problem is that the cloning process is running the cloning as if the type being cloned is of the base type of the collection item being cloned, not its specific type. The result is the NPE whenever the cloning process clones something that is not part of the base type in the collection. In the case mentioned, it was the environment variable was not part of the base definition.

Daniel Ostermeier - 02/Feb/10 12:43 AM
Resolved pending review.

This is the first of the two issues that is fixed. I have asked for more details regarding the second case which I can not reproduce. When further details come in, I will open a separate issue.

Daniel Ostermeier - 02/Feb/10 12:44 AM
Review 547, revision 7706