|
| Re: Materialization problem from the IDE [message #661453 is a reply to message #661434] |
Thu, 24 March 2011 17:28   |
|
It's likely that you have some problem with your local SVN server. You need to resolve what's causing this:
"org.eclipse.team.svn.core.connector.SVNConnectorException: svn: Malformed network data"
- thomas
On 2011-03-24 17:33, Joaquin Morcate wrote:
> Trunk/Head rejected: org.eclipse.team.svn.core.connector.SVNConnectorException: svn: Malformed network data
|
|
|
|
| Re: Materialization problem from the IDE [message #661584 is a reply to message #661567] |
Fri, 25 March 2011 13:40 |
|
On 2011-03-25 12:48, Joaquin Morcate wrote:
> Hi Thomas,
>
> Thank you for your answer. I have been working this morning on the problem and there are some things that I can not
> understand.
> I have three different repositories. One of the is where I store my sources and the releng project. In the other two I
> have sources from other people in my company.
>
> 1) If I check out my releng project using a URL with svn+ssh and I try to resolve my project, Buckminster fails because
> it tries to use the svn+ssh protocol without provided credentials (user and password). I think that the svn exception
> comes from there.
Set up a correct key pair or add the needed credentials to the svn+ssh repository that you have registered in your
workspace and you'll be fine.
> 2) If I check out the releng project using svn instead of svn+ssh I am able to resolve the project. But Buckminster
> still fails to materialize the project in the IDE. This is the console output:
>
> Problem during meta-data refresh: Resource '/.buckminster/tp' is not local.
> org.eclipse.core.internal.resources.ResourceException: Resource '/.buckminster/tp' is not local.
That bug was fixed a couple of days ago so please update your Buckminster.
>
> 3) Another problem with the materialization is that it adds to the Eclipse SVN Repositories list a new repository with
> url:svn://localhost/var/repo/svn, that is: the common part of all my repositories URLs.
>
And that is a problem because ... ?
> 4)Otherwise all my projects are checkout but not all are imported in the workspace. Which projects are imported varies,
> I think that it depends when the error mentioned above takes places.
> Basically I don't know what is failing.
> * Why if Buckminster is reading my rmap insists in using svn+ssh?
It doesn't insist. But if you have an svn+ssh registered in your workspace it will automatically switch to using that.
If you have such an entry it must have the needed credentials (or, you'll need a proper key-pair).
- thomas
|
|
|
|
| Re: Materialization problem from the IDE [message #661881 is a reply to message #661859] |
Mon, 28 March 2011 11:46 |
|
On 2011-03-28 12:12, Joaquin Morcate wrote:
> 1) Why my target platform is not selected after the materialization?
>
Buckminster never selects the target platform. It uses the currently active target platform. Both before, during, and
after materialization.
> 2) Why if I provide a rmap where I say to Buckminster that should use svn to retrieve my sources, it will ignore me and
> try before svn+ssh just because I have set that access protocol in the IDE. where is the advantage on that?
>
If you have an explicit entry for a repository in your workspace that has elevated privileges compared to the one
specified in the rmap, Buckminster chooses that because it's assumed that you will want full write access.
This set-up makes it possible for you to share the rmap with people that doesn't normally have write access. Since you
don't need to specify ssh+svn in the rmap, others will still be able to use it and create patches. They will however not
have write access.
If you don't want ssh+svn access to a repository, then why specify it in your workspace?
- thomas
|
|
|
|
Powered by
FUDForum. Page generated in 0.02795 seconds
] 
Search
Help
Register
Login
Home
