Mark,
You didn't respond -- did this not make any sense?
Glen.
Glen wrote:
> Hi Mark,
>
> > Can you expand on this with more details?
>
> Sure.
>
> If I export https://svn.cakephp.org/repo/branches/1.2.x.x to
> D:/Programming/PHP/Libraries/CakePHP, the command executed is:
>
> export -r HEAD https://svn.cakephp.org/repo/branches/1.2.x.x
> D:/Programming/PHP/Libraries/CakePHP/1.2.x.x
>
> As you can see, the last component of the URL (1.2.x.x) is appended to
> the local directory name. I would like to be able to specify a
> different name for the export, so that the command executed would be
> as follows:
>
> export -r HEAD https://svn.cakephp.org/repo/branches/1.2.x.x
> D:/Programming/PHP/Libraries/CakePHP/1.2.0.6402
>
> (Two notes: [1] '-r HEAD' is unnecessary [?] [2] It may be more
> logical to change the current working directory and then execute the
> export command, so that the full export path is not required [if
> that's possible])
>
> So, the export window would ask for:
>
> Export directory: The directory to work from.
> Export path: The path within the directory to export to, for example
> '1.2.0.6402'. This could be left empty to use the default -- no path
> results in an export to: CWD/{last component of URL = 1.2.x.x in this
> case}. See http://svnbook.red-bean.com/en/1.1/re10.html
>
> It would also be nice (but not as important), to be able to specify
> the path as: '1.2.0.$rev', for example, and to have the following
> command executed:
>
> export https://svn.cakephp.org/repo/branches/1.2.x.x
> 1.2.0.{revision being exported}
>
> (extra spaces above for clarity)
>
> Full example:
>
> Export directory: D:/Programming/PHP/Libraries/CakePHP
> Export path: 1.2.0.6402 (or 1.2.0.$rev)
>
> Resulting command, executed from 'D:/Programming/PHP/Libraries/CakePHP':
>
> export https://svn.cakephp.org/repo/branches/1.2.x.x 1.2.0.6402
>
> Hope this makes sense.
>
> > This name is based on the CVS plug-in using the name CVS Repository
> Exploring for their plug-in.
>
> Is that a 'no'? :-) ... :-(
>
> > Subclipse does not operate at this level.
>
> OK, thanks, I'll do as you suggested.
>
> Regards,
>
> Glen.
>
> Mark Phippard wrote:
>> On Jan 22, 2008 12:16 PM, Glen <glen.84_at_gmail.com> wrote:
>>
>>
>>> 1. Allow a path to be specified for the local directory name,
>>> instead of
>>> forcing the use of the last component of the URL when exporting.
>>>
>>
>> Can you expand on this with more details?
>>
>>
>>> 2. Rename the perspective from 'SVN Repository Exploring', which is cut
>>> off and displayed as 'SVN Reposito...', to 'Subclipse' or 'Subversion'.
>>>
>>
>> This name is based on the CVS plug-in using the name CVS Repository
>> Exploring for their plug-in. Ideally, we would like Eclipse to
>> someday add a common repositories view that everyone could share.
>>
>>
>>> Question:
>>>
>>> I'm getting an 'Unknown certificate issuer' message when connecting
>>> to a
>>> server with a certificate signed by Equifax Secure Inc., US. Both
>>> Internet Explorer and Firefox have no problem accepting this
>>> certificate. Which CA files does Subclipse use by default?
>>>
>>
>> Subclipse does not operate at this level. We make SVN API calls, and
>> the SVN library you are using (JavaHL or SVNKit) does the networking.
>> Native Subversion (JavaHL) uses OpenSSL and for whatever reason has
>> decided to ship with no default CA list and to not trust any certs by
>> default. This has been discussed before on their mailing lists and
>> that would be the best place to bring up the issue.
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-01-30 20:15:48 CET