[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] headless resolve with properties
|
Pressing on, I substituted hardcoded username/password in my rmap until I
find a resolution as to why the properties don't work.
Running my small headless test case (resolving a feature which has two
plugin dependencies) it seems to churn away okay (uses the hardcoded
authentication) for all my local components, but then it ends up failing
out on some eclipse components (looks like org.eclipse.ui and
org.eclipse.jface) ultimately throwing an exception (looks like probably a
bad exception string format returning null).
Note: my rmap contains a 'last-resort' redirect to the buckminster
dogfood2.rmap to pick up non-local components
My headless resolve bails out with:
Errors and Warnings
[0][0003] : Rejecting provider
eclipse.import(http://download.eclipse.org/eclipse/updates/3.3?importType=binary):
No component match was found
Caused by: [0][0][0003] : PDEMapProvider
cvs(:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/eclipse,org.eclipse.releng/maps):
Unable to find org.eclipse.ui:osgi.bundle/[3.2.0,4.0.0)#OSGi in map
[0][0008] : Rejecting provider
eclipse.import(http://download.eclipse.org/eclipse/updates/3.3?importType=binary):
No component match was found
Caused by: [0][0][0008] : PDEMapProvider
cvs(:pserver:anonymous@xxxxxxxxxxxxxxx:
/cvsroot/eclipse,org.eclipse.releng/maps): Unable to find
org.eclipse.jface:osgi.bundle/[3.2.0,4.0.0)#OSGi in map
[0][0003] : Rejecting provider
eclipse.import(http://download.eclipse.org/eclipse/updates/3.3?importType=binary):
No component match was found
Caused by: [0][0][0003] : PDEMapProvider
cvs(:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/eclipse,org.eclipse.releng/maps):
Unable to find org.eclipse.ui:osgi.bundle/[3.2.0,4.0.0)#OSGi in map
Exception in thread "Thread-14" java.lang.NullPointerException
at
org.eclipse.buckminster.core.helpers.LocalizedException.getLocalizedFormat(LocalizedException.java:26)
at
org.eclipse.buckminster.core.helpers.LocalizedException.getLocalizedMessage(LocalizedException.java:76)
at java.lang.Throwable.toString(Throwable.java:343)
at
org.eclipse.buckminster.core.helpers.FileUtils$1.run(FileUtils.java:8
00)
Now I noticed that the map file entries for the above components at
dev.eclipse.org have integration build version qualifiers:
plugin@org.eclipse.jface=I20080312-1200,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/eclipse,
...
plugin@xxxxxxxxxxxxxx=I20080312-1200,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/eclipse,
Could that be throwing off the pde map provider? Looking inside the
repository, eg - org.eclipse.jface, the 3.4.0 version does seem to be
available, which suggests it should match if it finds it's way there via
the pde map.
I gather that there are people out there running headless (as gruesome as
it sounds :) ) with more success than I. Can anyone confirm
success/experience with the 1.0.0.r08941 product package? Is a prior
product package perhaps considered more stable?
Any suggestions welcome,
Thanks
T
Todd_Lee@xxxxxxxx
Sent by:
buckminster-dev-b To
ounces@xxxxxxxxxx Buckminster developer discussions
g <buckminster-dev@xxxxxxxxxxx>
cc
03/12/2008 10:46 Subject
AM Re: [buckminster-dev] headless
resolve with properties
Please respond to
Buckminster
developer
discussions
<buckminster-dev@
eclipse.org>
As a follow up,
I tried opening a new workspace and running buckminster from the IDE with
the same CQUERY, using the properties for user.name and user.pass in the
CQUERY file - no problem. Resolve and materialize were completed using the
cvs authenication credentials provided (new workspace, so no cached
credentials).
As an aside - it looks like the property substitution doesn't take place
until the 'metadata refresh' stage, so I guess it does the component match
before 'filling in all the blanks' for the cvs provider containing
properties?
Any idea why my headless resolve would be failing where the IDE succeeds?
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
Todd_Lee@xxxxxxxx
Sent by:
buckminster-dev-b To
ounces@xxxxxxxxxx Buckminster developer discussions
g <buckminster-dev@xxxxxxxxxxx>
cc
03/11/2008 06:20 Subject
PM Re: [buckminster-dev] headless
resolve with properties
Please respond to
Buckminster
developer
discussions
<buckminster-dev@
eclipse.org>
Hey Thomas,
Thanks for the response. To try and narrow down the issue, I've changed the
rmap to skip the pde maps and hit cvs directly. Still get error on no CVS
Authenticator
): No component match was found
com.amis.platform:eclipse.feature: No provider was found that could resolve
the request
ERROR [0001] : No suitable provider for component
com.amis.platform:eclipse.feature was found in searchPath amis.components
ERROR [0001] : Rejecting provider
cvs(:pserver:{0}:{1}@host:/path/to/cvsrep,path/to/module/{2}): No component
match was found
Authentication error: No CVS authenticator is registered
I'm still curious as to why the error strings contain unsubstituted
properties. Should they be substituted at this point? I would think that
the substitution would need to take place before CVS Authentication could
be accomplished (otherwise, what username/password do we use?)
Thanks
Todd
Thomas Hallgren
<thomas@xxxxxxx>
Sent by: To
buckminster-dev-b Buckminster developer discussions
ounces@xxxxxxxxxx <buckminster-dev@xxxxxxxxxxx>
g cc
Subject
03/11/2008 05:52 Re: [buckminster-dev] headless
PM resolve with properties
Please respond to
Buckminster
developer
discussions
<buckminster-dev@
eclipse.org>
Hi Todd,
I see that you're using a pde map provider. Could it be that the first
cvs access (the one that retrieves the map files) works OK and that the
error occurs when an attempt is made to access one of components in the
map file?
If so, you might try adding user names and passwords to the entries in
the map files.
Regards,
Thomas Hallgren
Todd_Lee@xxxxxxxx wrote:
> As a follow up,
> In addition to trying the cmdline -D"property.key=property.value"
indicated
> below (which, to be precise, should actually be "buckminster command
> options -vmargs -Dproperty..." still didn't work) I tried direct property
> substitution in the CQUERY. I'll include some snips below for
illustration:
>
> -- CQUERY --
> <?xml version="1.0" encoding="UTF-8"?>
> <cq:componentQuery
> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0";
> resourceMap="http://path/to/test.rmap"; >
> <cq:rootRequest name="com.amis.platform"
> componentType="eclipse.feature" />
> <cq:property key="user.name" value="leet" />
> <cq:property key="user.pass" value="xxxxx" />
> </cq:componentQuery>
>
>
> -- RMAP SNIP --
> ...
> <searchPath name="amis.pde.maps">
> <provider xsi:type="pmp:PDEMapProvider" readerType="cvs"
> componentTypes="osgi.bundle,eclipse.feature,buckminster" mutable="true"
> source="true">
> <uri
> format=":pserver:{0}:{1}@host:/path/to/cvsrep,path/to/maps">
> <bc:propertyRef key="user.name" />
> <bc:propertyRef key="user.pass" />
> </uri>
> </provider>
> <provider readerType="cvs"
> componentTypes="osgi.bundle,eclipse.feature,buckminster" mutable="true"
> source="true">
> <uri
> format=":pserver:{0}:{1}@host:/path/to/cvsrep,path/to/projects/{2}">
> <bc:propertyRef key="user.name" />
> <bc:propertyRef key="user.pass" />
> <bc:propertyRef key="buckminster.component" />
> </uri>
> </provider>
> </searchPath>
> ...
>
> -- HEADLESS OUTPUT --
> C:\>buckminster -L DEBUG -data C:\autobuild_root\temp resolve
> http://path/to/test.cquery
> resolve 'http://path/to/test.cquery'
> Platform install location: C:\autobuild_root\buckminster
> Target platform provided by class
> org.eclipse.buckminster.pde.internal.PDETarget Platform
> com.amis.platform:eclipse.feature: Using resolver rmap
> com.amis.platform:eclipse.feature: Rejecting provider
> eclipse.platform(feature/${buckminster.component}): No component match
was
> found
> com.amis.platform:eclipse.feature: Using resource map
> http://path/to/test.rmap
> com.amis.platform:eclipse.feature: Using search path amis.pde.maps
> com.amis.platform:eclipse.feature: Trying provider
> cvs(:pserver:{0}:{1}@host:/path/to/cvsrep,path/to/maps)
> blocked(class org.eclipse.core.internal.events.AutoBuildJob[Building
> workspace])
>
> Authentication error: No CVS authenticator is registered
> com.amis.platform:eclipse.feature: Trying provider
> cvs(:pserver:{0}:{1}@host:/path/to/cvsrep,path/to/projects/{2})
> com.amis.platform:eclipse.feature: trunk/head will be searched
> com.amis.platform:eclipse.feature: Rejecting provider
> cvs(:pserver:{0}:{1}@host:/path/to/cvsrep,path/to/projects/{2}): No
> component match was found
> com.amis.platform:eclipse.feature: No provider was found that could
resolve
> the request
> ERROR [0001] : No suitable provider for component
> com.amis.platform:eclipse.feature was found in searchPath amis.pde.maps
> ERROR [0001] : Authentication error: No CVS authenticator is
registered
> ERROR [0001] : Rejecting provider
> cvs(:pserver:{0}:{1}@host:/path/to/cvsrep,path/to/projects/{2}): No
> component match was found
> Errors and Warnings
> [0][0001] : Authentication error: No CVS authenticator is registered
> [0][0001] : Rejecting provider
> cvs(:pserver:{0}:{1}@host:/path/to/cvsrep,path/to/projects/{2}): No
> component match was found
>
> Caused by: [0][0]Authentication error: No CVS authenticator is registered
>
>
>
> So it doesn't seem to be that either method works for me. Is there
> something that I'm missing? One curious thing I noticed - in the debug
> headless output, the buckminster.component isn't even being substituted
> ({2}) - shouldn't this be substituted at this point as well? Still leaves
> me wondering if there's an issue with the headless resolve when using
> properties...
>
> Any insight is more than welcome! :)
> T
>
>
>
>
>
> Todd_Lee@xxxxxxxx
> Sent by:
> buckminster-dev-b
To
> ounces@xxxxxxxxxx Buckminster developer discussions
> g <buckminster-dev@xxxxxxxxxxx>
>
cc
>
> 03/11/2008 01:51
Subject
> PM Re: [buckminster-dev] headless
> resolve with properties
>
> Please respond to
> Buckminster
> developer
> discussions
> <buckminster-dev@
> eclipse.org>
>
>
>
>
>
>
> Sorry, I should add that I did see this:
>
http://dev.eclipse.org/newslists/news.eclipse.technology.buckminster/msg00507.html
>
> which suggests that headless authentication should be possible using
> properties in the RMAP (though the case in point uses svn instead of cvs,
> I'm guessing it's still applicable).
>
> The problem is I tried using the method of propertyrefs in the rmap :
>
> <uri
> format=":pserver:{0}:{1}@host:/path/to/cvsrep,path/to/module/{2}">
> <bc:propertyRef key="user.name" />
> <bc:propertyRef key="user.pass" />
> <bc:propertyRef key="buckminster.component" />
> </uri>
>
> and then substituting the system properties on the command line using:
>
> buckminster -D"user.name=<myusername>"
>
> But I get a buckminster exception:
> C:\>buckminster -D"user.name=<myusername>" -data C:\autobuild_root\temp
> resolve http://host/build.cquery
> org.eclipse.buckminster.cmdline.parser.InvalidOptionException: The option
> '-Duser.name=<myusername>' is invalid
>
> Has the handling of cmdline args (specifically for system props) changed?
I
> just updated to 1.0.0.r08941
>
> FYI -
> C:\>buckminster listsite
> Features:
> org.eclipse.buckminster.core.headless.feature_1.0.0.r08974 (Buckminster
-
> Core Headless)
> org.eclipse.buckminster.cvs.headless.feature_1.0.0.r08953 (Buckminster
-
> CVS support for headless operation)
> org.eclipse.buckminster.maven.feature_1.0.0.r08939 (Buckminster - Maven
> support)
> org.eclipse.buckminster.pde.headless.feature_1.0.0.r08961 (Buckminster
-
> PDE support for headless operation)
> org.eclipse.buckminster.product_1.0.0.r08941 (Buckminster Product)
>
> Thanks
> Todd
>
>
>
>
> Todd_Lee@xxxxxxxx
> Sent by:
> buckminster-dev-b
To
> ounces@xxxxxxxxxx buckminster-dev@xxxxxxxxxxx
> g
cc
>
>
Subject
> 03/11/2008 01:22 [buckminster-dev] headless resolve
> PM with properties
>
>
> Please respond to
> Buckminster
> developer
> discussions
> <buckminster-dev@
> eclipse.org>
>
>
>
>
>
>
>
> Just wondering what the best way to go about executing a headless resolve
> might be where properties are involved?
> e.g. - in my rmap, I've got ${user.name} specified in the :pserver string
> to authenticate my CVSROOT.
> The IDE has provided this in the UI mode, but I'm not sure how to handle
it
> when running headless. Suggestions?
>
> Thanks
> 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
>
>
> 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
>
>
> 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
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
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.
