Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Team Project Set

I was trying to reuse the Team Project File directly.  I think this method requires copy / pasting each item in the Team Project File into the repository-configuration.  The only way to share the Team Repository File is through a SCM.  The SCM reference is to access the Team Project File.    The example below does sharing of the Team Project File by “importing” it into a repository-configuration.  I think it would be easier to somehow directly use the Team Project File.

 

Glenn Everitt

 


From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Thursday, August 03, 2006 4:59 AM
To: Corona development
Subject: Re: [corona-dev] Team Project Set

 

If we keep it in the format you suggest we still need to know how to map the method, host, user, etc to the proper reference string and http://www.eclipse.org/corona/accessTypes/cvs to provider id. In other words we would have to provide an extension for each SCM to map connection parameters to a proper reference string. If we were to keep in generic way I would make the repository like this:

<repository-descriptor name="CVS.org.eclipse.corona.TeamProject" uri="org.eclipse.corona/CoronaTeamProject"

content-type="http://www.eclipse.org/corona/contentTypes/workbenchTeamProjectContent">

      <description>Attempt to model Eclipse Team Project File as a repository</description>

      <repository-configurations default-configuration-name="CoronaTeamProjectRepositoryConfiguration" >

            <repository-configuration name=" CoronaTeamProjectRepositoryConfiguration ">

                  <repository-connection-parameters access-type="http://www.eclipse.org/corona/accessTypes/teamProject">

                        <repository-connection-parameter name="provider-id" value="org.eclipse.team.cvs.core.cvsnature" />

                        <repository-connection-parameter name="reference" value="1.0,:extssh:206.191.52.50:/home/technology,org.eclipse.corona/incubator/org.eclipse.corona.model.container,org.eclipse.corona.model.container" />

                  </repository-connection-parameters>

            </repository-configuration>

      </repository-configurations>

</repository-descriptor>     


Only in this way we can take advantage of generic approach, without even knowing what kind of SCM we are dealing with.

Marcin


Could we think of the Team Project File as a Repository?  Using the content-type to decide how to process it once retrieved from CVS.  It seems like there may be a general requirement to pull something from SCM (source code management) system and then delegate processing of the file to something else other than a view.  The Mapper object could be used to map repositories with content-type=…/workbenchTeamProjectContent to class that processes the Team Project Set.  Would this be a resource processor extension point? or would it be more like a builder?

 

repository-descriptor example below:

 

<repository-descriptor name="CVS.org.eclipse.corona.TeamProject" uri="org.eclipse.corona/CoronaTeamProject"

content-type="http://www.eclipse.org/corona/contentTypes/workbenchTeamProjectContent">

      <description>Attempt to model Eclipse Team Project File as a repository</description>

      <repository-configurations default-configuration-name="CoronaTeamProjectRepositoryConfiguration" >

            <repository-configuration name=" CoronaTeamProjectRepositoryConfiguration ">

                  <repository-connection-parameters access-type="http://www.eclipse.org/corona/accessTypes/cvs">

                        <repository-connection-parameter name="Method" value="pserver" />

                        <repository-connection-parameter name="Host" value="206.191.52.50" />

                        <repository-connection-parameter name="User" value=" anonymous" />

                        <repository-connection-parameter name="RepositoryPath" value="/home/technology" />

                        <repository-connection-parameter name="Module" value="org.eclipse.corona" />

                        <resource-subset selection-criteria="HEAD" type="CVS-TAG"/>

                  </repository-connection-parameters>

            </repository-configuration>

      </repository-configurations>

</repository-descriptor>     

 

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

Back to the top