Opened 13 years ago

Closed 10 years ago

#9035 closed defect (invalid)

build: scope params cannot be set in profile

Reported by: dante Owned by: dante
Priority: low Milestone: future
Component: BuildSystem Version: 1.3.0
Keywords: Cc: Rawld Gill
Blocked By: Blocking:


the kwArg scopeDjConfig cannot be passed to the profile, at least not as you'd expect to be able to. if defined in a profile as an object, eg:

dependencies = {

the build dies with "replace in [object Object] undefined", which is being called by:

buildUtil.setScopeDjConfig = function(/*String*/fileContents, /*String*/djConfigString){

if you define the param as a string, eg:

dependencies = {

the build seems to run ok. It would be more useful if one were able to define all kwArgs, though I partially understand the reasoning behind the use of strings explicitly.

Either way, I was trying to do this and didn't find anything in the way of guide of tutorial, so it should be explicitly documented whatever the outcome of this ticket is. Some kwArgs _can_ be put in the profile, scopeDjConfig _must_ be a string, etc.

Change History (4)

comment:1 Changed 12 years ago by James Burke

(In [20400]) Refs #9035: scopeDjConfig needs to be a string, for now throw with an informative error, but in the future, just allow an object definition.

comment:2 Changed 12 years ago by James Burke

Milestone: tbdfuture

comment:3 Changed 10 years ago by ben hockey

Cc: Rawld Gill added
Owner: changed from James Burke to dante
Priority: highlow
Status: newpending

Is this ticket still valid?

If there's no response within 14 days it will close automatically.

comment:4 Changed 10 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.