Opened 11 years ago

Closed 9 years ago

#36 closed enhancement (fixed)

distinction for cms2 vs using sandbox as is

Reported by: Bryan Gartner Owned by:
Priority: minor Milestone: 0.10.1
Component: pb Version: 0.9.4
Keywords: Cc:

Description

When doing the cms2 commands, I would have expected the operation to grab the specified version from cms, rather than using my current sandbox of a project. In fact the way it behaves now, it much more implements a sandbox2 or local2 functionality (which itself is useful). However, I'd like both modes to be available, and certainly the cms2 modes to actually refresh what gets built/packaged to match what the specified CMS repository has. And the new sandbox2 or local2 operation to rely on what you have in place (modified or not) to be the source (which is really useful for local and/or offline testing).

Change History (7)

comment:1 in reply to:  description Changed 11 years ago by Bruno Cornec

Hello Bryan again !

Replying to bryang:

When doing the cms2 commands, I would have expected the operation to grab the specified version from cms, rather than using my current sandbox of a project.

Is there a way for me to make it more explicit in the documentation what the command really does ?

In fact the way it behaves now, it much more implements a sandbox2 or local2 functionality (which itself is useful).

True and that was on purpose in fact.

However, I'd like both modes to be available, and certainly the cms2 modes to actually refresh what gets built/packaged to match what the specified CMS repository has.

In fact both modes *are* already available. If you point your local repo to a new dir, cms2 cmds will again extract content from the CMS to that new dir, doing also what you want in parallel.

And the new sandbox2 or local2 operation to rely on what you have in place (modified or not) to be the source (which is really useful for local and/or offline testing).

I think it's all linked with the way you use you CMS t develop as well. I generally test locally my mods with cms2 cmds, and then commit them back to the CMS. But I'm using SVN. For usage it may be interesting to have different way of doing.

So I do not say a definitive no to your request, but I'm not yet convince it brings really something, as you can already do it. Maybe an option ?

comment:2 Changed 11 years ago by Bruno Cornec

Milestone: 0.9.50.9.6

comment:3 Changed 11 years ago by Bruno Cornec

Milestone: 0.9.60.9.7

comment:4 Changed 10 years ago by Bruno Cornec

Milestone: 0.9.70.9.8

comment:5 Changed 10 years ago by Bruno Cornec

Milestone: 0.9.90.9.10

Bryan,

Do you think this BR is still valid with your familiarity with the tool now ?

comment:6 Changed 9 years ago by Bruno Cornec

Milestone: 0.9.100.9.11

comment:7 Changed 9 years ago by Bruno Cornec

Resolution: fixed
Status: newclosed

Adds sbx2 targets to support this feature. Agreed this is indeed useful and added as of rev [1097]

Only checked with SVN for now. Please test with CVS for the new cms2 targets.

Note: See TracTickets for help on using tickets.