Source control and .emx files
11 answers
Could you expand a bit on "refused to do that"?
For example, what operation did you perform, and what error message did
you get?
Cheers,
Geoff
On 5/18/2010 11:53 AM, MarcoB wrote:
For example, what operation did you perform, and what error message did
you get?
Cheers,
Geoff
On 5/18/2010 11:53 AM, MarcoB wrote:
I am running RTC on RSA and when I tried to use Jazz source control on
a Model-project, RTC refused to do this. Is there any way to work
around that?
Hi Marco,
versioning model projects and .emx files definitely works - just tried that with 2.0.0.2.
You need to share the project, select Jazz SCM etc (being connected to a Team Area) and it will version the files including .emx.
Of course you can't just click on the .emx to share just that. You share the project first. And make sure .emx is not accidentally on the .jazzignore list.
Please provide more info on versions, what you did and what the messages where you got so that we can help.
Ralph
versioning model projects and .emx files definitely works - just tried that with 2.0.0.2.
You need to share the project, select Jazz SCM etc (being connected to a Team Area) and it will version the files including .emx.
Of course you can't just click on the .emx to share just that. You share the project first. And make sure .emx is not accidentally on the .jazzignore list.
Please provide more info on versions, what you did and what the messages where you got so that we can help.
Ralph
I am running RTC on RSA and when I tried to use Jazz source control on a Model-project, RTC refused to do this. Is there any way to work around that?
Thanks a lot for your answer:
The error Message is: Internal Error / Cannot nest CFAs
@Ralph: I did choose the project to be shared and verified that .emx files are not on the ignore list.
Marco
The error Message is: Internal Error / Cannot nest CFAs
@Ralph: I did choose the project to be shared and verified that .emx files are not on the ignore list.
Marco
Could you expand a bit on "refused to do that"?
For example, what operation did you perform, and what error message did
you get?
Cheers,
Geoff
On 5/18/2010 11:53 AM, MarcoB wrote:
I am running RTC on RSA and when I tried to use Jazz source control on
a Model-project, RTC refused to do this. Is there any way to work
around that?
Marco,
exactly when does that happen?
How does the structure of your project look like on disk? Is the model broken up into pieces?
Can you just create a simple modeling project with just one simple model in it in your workspace and try to share that. You could share into a repository workspace if you don't want to deliver to a stream.
Ralph
exactly when does that happen?
How does the structure of your project look like on disk? Is the model broken up into pieces?
Can you just create a simple modeling project with just one simple model in it in your workspace and try to share that. You could share into a repository workspace if you don't want to deliver to a stream.
Ralph
Thanks a lot for your answer:
The error Message is: Internal Error / Cannot nest CFAs
Marco
Could you expand a bit on "refused to do that"?
For example, what operation did you perform, and what error message did
you get?
Cheers,
Geoff
On 5/18/2010 11:53 AM, MarcoB wrote:
I am running RTC on RSA and when I tried to use Jazz source control on
a Model-project, RTC refused to do this. Is there any way to work
around that?
That's what I thought it was, at least: But then there is the next error:
Error during upload
Failed to upload File /Jazz/RTC.emx
CRJAZ1247I The request to the server failed. The server returned the http error 400 with error text "Bad Request".
The file structure is quite simple, just the project folder and one .emx file in it.
In fact I do have two .emx files now for testing and the small one gets uploaded very easily.
If I create a new project and copy the both models to it, I even get the problem for both of them
Error during upload
Failed to upload File /Jazz/RTC.emx
CRJAZ1247I The request to the server failed. The server returned the http error 400 with error text "Bad Request".
The file structure is quite simple, just the project folder and one .emx file in it.
In fact I do have two .emx files now for testing and the small one gets uploaded very easily.
If I create a new project and copy the both models to it, I even get the problem for both of them
Marco,
the 400 does not look like a normal behavior.
I don't think that is related to what you did. That looks more like a connection problem.
Ralph
the 400 does not look like a normal behavior.
I don't think that is related to what you did. That looks more like a connection problem.
Ralph
That's what I thought it was, at least: But then there is the next error:
Error during upload
Failed to upload File /Jazz/RTC.emx
CRJAZ1247I The request to the server failed. The server returned the http error 400 with error text "Bad Request".
The file structure is quite simple, just the project folder and one .emx file in it.
In fact I do have two .emx files now for testing and the small one gets uploaded very easily.
If I create a new project and copy the both models to it, I even get the problem for both of them
Marco,
the 400 does not look like a normal behavior.
I don't think that is related to what you did. That looks more like a connection problem.
Ralph
That's what I thought it was, at least: But then there is the next error:
Error during upload
Failed to upload File /Jazz/RTC.emx
CRJAZ1247I The request to the server failed. The server returned the http error 400 with error text "Bad Request".
The file structure is quite simple, just the project folder and one .emx file in it.
In fact I do have two .emx files now for testing and the small one gets uploaded very easily.
If I create a new project and copy the both models to it, I even get the problem for both of them
I agree with Ralph - more like a connection problem. Is your server local, or remote? If it is local - check it really is running. If it is remote - check it is still up. Next - try the metronome in the RTC client to check the network connection - you may need to adjust the network timeout on the repo connection.
regards
anthony
I agree with Ralph - more like a connection problem. Is your server local, or remote? If it is local - check it really is running. If it is remote - check it is still up. Next - try the metronome in the RTC client to check the network connection - you may need to adjust the network timeout on the repo connection.
regards
anthony
Thanks for the hint. I am averaging 14ms, on local, so it's supposed to be quite good. And the largest part of my stuff is correctly uploaded. It took a plugin project as a whole and just refused one .epx file (once again a Model thing).
page 1of 1 pagesof 2 pages