Barrel Refresh

DaveBrillhart 11 days ago

Is this normal?

I make a change to a barrel, and I compile it to the folder to which my Field's barrels,jungle points.

Now I make changes to my field, and I run it. But it does NOT use the current barrel.

What I have to do is go into the field's manifest.xml file, and remove the Barrel Dependency and re-add the Barrel.

Now when I run the field, it does use the updated Barrel.

I assume the same steps are needed to ensure the field's PRG file is also using the updated Barrel before publishing?

I don't recall this being needed in Eclipse, but I'm using VSC now.

0 FlowState 11 days ago

Not saying this isn't a bug, but I think the expected workflow is:

- you make a change to barrel source

- you compile the project which uses the barrel (as opposed to compiling the barrel itself)

I realize this breaks down if you have more than one project which uses a barrel

EDIT: actually, the thread I linked somewhat contradicts what I said above haha sorry. It seems that building the project which uses the barrel will only cause the barrel itself to be recompiled under certain circumstances (like if the project jungle is changed.)

This thread is kinda similar (but not exactly the same): forums.garmin.com/.../is-there-a-way-to-detect-changes-in-a-barrel-during-development-and-rebuild-it-when-i-run-my-app

What you posted does sound like a bug, so I would def file a bug report. At the very least, if you provide a detailed recreation procedure in the bug report, the CIQ team should be able to confirm or deny whether it's expected behavior.