| General approaches for providing materializations [message #546694] |
Tue, 13 July 2010 15:21  |
Eclipse User |
|
|
|
Hi,
I'm wondering what people are doing for providing the easiest possible paths to users for workspace setup. I have two issues I'm thinking about right now. My goal is to have a sort of team project set on steroids. (Actually, that's a bad example because steroids are not sustainable in long term!)
1. Is it possible to provide a single artifact to users? Right now I'm down to a cspec and rmap but it would be ideal for them to be able to simply go to a single URL. Although, I guess I could simply fully specify a URL for the rmap.
2. Is there a way to handle SVN / CVS credentials if cooresponding repos haven't already been created? the only way it works for me now is with the repos, which means asking the users to put in the svn, which is really half the battle.
I see big advantages to this to using a .psf file, not least is that generally speaking they should never go out of date.
|
|
|
|
|
|
| Re: General approaches for providing materializations [message #546773 is a reply to message #546694] |
Wed, 14 July 2010 03:32  |
| Eclipse User |
|
|
|
Am 13.07.2010 21:21, schrieb Miles Parker:
> 1. Is it possible to provide a single artifact to users? Right now I'm
> down to a cspec and rmap but it would be ideal for them to be able to
> simply go to a single URL. Although, I guess I could simply fully
> specify a URL for the rmap.
>
You don't need to fully specify the URL in the cquery, a relative
location works just fine. e.g. put both files in the same location of
the webserver and just use the name of the rmap.
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap="your.rmap">
> 2. Is there a way to handle SVN / CVS credentials if cooresponding repos
> haven't already been created? the only way it works for me now is with
> the repos, which means asking the users to put in the svn, which is
> really half the battle.
In my rmap I refer to properties like cvs.user for the SCM username.
These properties are not defined in the rmap, but in the cquery. In my
case use the property user.name as value of cvs.user.
That's a litle environment dependent, but at least for us the
os-username usually matches the SCM username, so this works pretty well.
<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap="your.rmap">
<cq:rootRequest name="org.example.some.feature"
componentType="eclipse.feature"/>
<cq:property key="cvs.user" value="${user.name}" />
</cq:componentQuery>
If for some reason user.name is not the right username for the SCM the
developer can easily adjust the property value in the CQuery Editor.
Given a correct username, Buckminster will either reuse an existing SCM
location, or create a new one with the given username and prompt for the
password.
Best regards,
Johannes
|
|
|
Powered by
FUDForum. Page generated in 0.08861 seconds
Home