[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] help with CVS
|
Hey Thomas,
I saw the bugzilla issue. I'm not getting I/O errors though, so not sure
it's the same thing.
While we do use the TortoiseCVS client (which I understand is build on
CVSNT), our server runs on a RedHat linux distro.
[leet@sam leet]$ cvs --version
Concurrent Versions System (CVS) 1.11.3 (client/server)
I'm assuming the eclipse CVS support doesn't rely on anything from
underlying CVS clients which may exist on the host, is that correct?
As for access to our cvs - I kind of doubt it, given the standard
corporate/legal implications, but I'll certainly ask. In the mean time, if
there's anythink I can test/report on for you, by all means feel free to
ask - I'd really love to get this sorted out so we can use buckminster.
Cheers
Todd
Todd Lee
Software Tools
AMI Semiconductor
Tel: +1.519.884.9696 ext 2242
Fax: +1.519.884.0228
E-mail: todd_lee@xxxxxxxx
Thomas Hallgren
<thomas@xxxxxxx>
Sent by: To
buckminster-dev-b Buckminster developer discussions
ounces@xxxxxxxxxx <buckminster-dev@xxxxxxxxxxx>
g cc
Subject
02/14/2008 12:48 Re: [buckminster-dev] help with CVS
PM
Please respond to
Buckminster
developer
discussions
<buckminster-dev@
eclipse.org>
Hi Todd,
I do have a bugzilla that indicates some difficulties pertaining to use
of CVSNT but the rpository root "/usr/local/share/projects/cvsrep" would
suggest that it's not what you're using :-)
Any chance you could give me temporary access to this repo?
Regards,
Thomas Hallgren
Todd_Lee@xxxxxxxx wrote:
> Hi Thomas - thanks for the reply...
> Curious though. I can indeed check out ALL the projects into my eclipse
> workspace using Eclipse CVS. Of course, with autobuild turned on I get
the
> following Errors/warnings
>
> Errors:
> Severity and Description Path
> Resource Location Creation Time Id
> Package 'org.demo.worlds' does not exist in this plug-in
> org.demo.xml.provider/META-INF MANIFEST.MF line 10 1203009040895
> 253
> Package 'se.tada.util.sax' does not exist in this plug-in
> org.demo.xml.provider/META-INF MANIFEST.MF line 9 1203009040895
> 252
> Project 'org.demo.xml.provider' is missing required library:
> 'jars/tada-sax.jar' org.demo.xml.provider Build path
> 1203008956345 240
> Project 'org.demo.xml.provider' is missing required library:
> 'jars/worlds.jar' org.demo.xml.provider Build path 1203008956345
> 241
> The project cannot be built until build path errors are resolved
> org.demo.xml.provider Unknown 1203009040880 251
> The project was not built since it depends on org.demo.xml.provider,
which
> has build path errors org.demo.hello.xml.world Unknown
> 1203009040926 258
>
> Warnings:
> An "source.jars/tada-sax.jar" build entry is missing
org.demo.xml.provider
> build.properties line 1 1203009040911 256
> An "source.jars/worlds.jar" build entry is missing
org.demo.xml.provider
> build.properties line 1 1203009040911 257
> The file "jars/worlds.jar" does not exist in the workspace
> org.demo.xml.provider build.properties line 6 1203009040911
255
> The folder "jars/" does not exist in the workspace
org.demo.xml.provider
> build.properties line 5 1203009040911 254
>
> Which is what I would expect until I can get buckminster working :)
>
> If you can think of anything that might cause this curious behaviour, I'd
> certainly appreciate some insight - thanks!
>
> Todd
>
>
> Todd Lee
> Software Tools
> AMI Semiconductor
> Tel: +1.519.884.9696 ext 2242
> Fax: +1.519.884.0228
> E-mail: todd_lee@xxxxxxxx
>
>
>
> Thomas Hallgren
> <thomas@xxxxxxx>
> Sent by:
To
> buckminster-dev-b Buckminster developer discussions
> ounces@xxxxxxxxxx <buckminster-dev@xxxxxxxxxxx>
> g
cc
>
>
Subject
> 02/14/2008 11:10 Re: [buckminster-dev] help with
CVS
> AM
>
>
> Please respond to
> Buckminster
> developer
> discussions
> <buckminster-dev@
> eclipse.org>
>
>
>
>
>
>
> Hi Todd,
> Buckminster has no special requirements for CVS support other then that
> the Buckminster CVS feature is installed. It uses the built in CVS
> support provided by the Eclipse IDE. If that works, Buckminster should
> also work. I can't see anything wrong with your setup. So first question
> I have to ask is - are you able to check out the
> org.demo.hello.xml.world project into your workspace using the Eclipse
CVS?
>
> - thomas
>
>
> Todd_Lee@xxxxxxxx wrote:
>
>> Hi there,
>>
>> So I tried with little success yesterday to use buckminster in our local
>> environment. After a bit of investigation, I'm wondering if it has
>> something to do with our CVS repository?
>> As a bit of background, no matter what I try to resolve, I seem to get
>> errors like the following:
>>
>> Found searchPath default for component org.demo.hello.xml.world
>> ERROR [0001] : No suitable provider for component
>> org.demo.hello.xml.world:osgi.bundle was found in searchPath default
>> ERROR [0001] : Provider
>>
>>
>
cvs(:pserver:leet@sam:/usr/local/share/projects/cvsrep,swt_root/scratch/leet/buckminstertest/helloworld/org.demo.hello.xml.world):
>
>
>> No match found for component org.demo.hello.xml.world
>>
>> After banging my head on my desk for a while, I thought I'd try to
>> eliminate possible sources of error so I elected to try a local setup
>>
> with
>
>> the 'hello world xml' demo which I know works (btw - thanks Thomas, svn
>> works now!). I exported the resolved/materialized (from eclipse svn
repo)
>> sources and added them to my local CVS for a test.
>>
>> I made a local copy of the cquery available on our network with the
>> following contents (filename: hwdemo.cquery):
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <cq:componentQuery xmlns:cq="
>>
> http://www.eclipse.org/buckminster/CQuery-1.0";
>
>> resourceMap="http://sam/ide/updates/dev/hwdemo.rmap";>
>> <cq:rootRequest name="org.demo.hello.xml.world"
>> componentType="osgi.bundle" versionType="OSGi"/>
>> </cq:componentQuery>
>>
>> I also made a local copy of the rmap likewise, changing the provider
info
>> to our local CVS (filename: hwdemo.rmap):
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <rmap
>> xmlns="http://www.eclipse.org/buckminster/RMap-1.0";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0";
>> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0";>
>>
>> <searchPath name="default">
>> <provider readerType="cvs"
>> componentTypes="eclipse.feature,osgi.bundle,buckminster" source="true">
>> <uri
>>
>>
>
format=":pserver:${user.name}@sam:/usr/local/share/projects/cvsrep,swt_root/scratch/leet/buckminstertest/helloworld/{0}">
>
>
>> <bc:propertyRef key="buckminster.component" />
>> </uri>
>> </provider>
>> </searchPath>
>>
>> <locator searchPathRef="default" pattern="^org\.demo\..*" />
>> <redirect
>> href="http://www.eclipse.org/buckminster/samples/rmaps/dogfood2.rmap";
>> pattern=".*"/>
>> </rmap>
>>
>>
>> So I get into my eclipse workbench and do File-> Open component query...
>> and enter my url. The CQUERY opens and I click 'resolve to wizard' with
>>
> my
>
>> fingers crossed - and I get the error at the start of this message. It
>> looks like it can't get the component info for this component, right? I
>>
> do
>
>> a local cvs checkout and confirm that the META-INF dir and plugin.xml
>>
> file
>
>> are where they are expected and sure enough, there they are (see
attached
>> screenshot).
>>
>> (Embedded image moved to file: pic23281.jpg)
>>
>>
>> I assumed this is everything that would be required for successful
>> resolution, but no joy...
>> I'm left to think that the only possible point of failure is the point
at
>> which buckminster trys to actually get the component info from our CVS
>> repo. Can you suggest a test that I can try locally to try and
>> confirm/ruleout this option? Are there specific requirements for
>> buckminster CVS support?
>>
>> Any help you can provide is greatly appreciated!
>>
>> Cheers
>> Todd
>> AMI Semiconductor - "Silicon Solutions for the Real World"
>> NOTICE:
>> This electronic message contains information that may be confidential or
>>
> privileged. The information is intended for the use of the individual or
> entity named above. If you are not the intended recipient, please be
aware
> that any disclosure, copying, distribution or use of the contents of this
> information is prohibited. If you received this electronic message in
> error, please notify the sender and delete the copy you received.
>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> buckminster-dev mailing list
>> buckminster-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>>
>>
>
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
>
> AMI Semiconductor - "Silicon Solutions for the Real World"
> NOTICE:
> This electronic message contains information that may be confidential or
privileged. The information is intended for the use of the individual or
entity named above. If you are not the intended recipient, please be aware
that any disclosure, copying, distribution or use of the contents of this
information is prohibited. If you received this electronic message in
error, please notify the sender and delete the copy you received.
>
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
_______________________________________________
buckminster-dev mailing list
buckminster-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/buckminster-dev
AMI Semiconductor - "Silicon Solutions for the Real World"
NOTICE:
This electronic message contains information that may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you received this electronic message in error, please notify the sender and delete the copy you received.
