| [buckminster-dev] problems with resolve - uncaught exception [message #5299] |
Fri, 22 February 2008 22:15  |
 Todd Lee
Messages: 44
Registered: July 2009 |
Member |
|
|
Hi there,
Before I go and file a bug, I just want to check with you to see if you've
seen this before. I'm trying to set up a rmap for use in materializing a
developer's workbench which will contain a number of features and plugins
among other things. Providers are PDEMapProviders and CVS. Resolve for a
select group of plugins (they all reside in the same directory in the cvs
repository) fails with a message like this:
com.amis.skt.debug:osgi.bundle/[2.2.0,3.0.0)#OSGi: Found match
:2008-01-28T22:34:35.000+0000
com.amis.skt.debug:osgi.bundle/[2.2.0,3.0.0)#OSGi: Using provider
cvs(org.eclipse.buckminster.core.common.model.Format@bf2a6e81)
Metadata refetch from Fri Feb 22 16:24:21 EST 2008 for
:pserver:leet@sam :/usr/local/share/projects/cvsrep/swt_root/host_code/ide/cod e/projects/com.amis.sk2.doc.user
java.util.MissingFormatArgumentException: Format specifier 's'
ERROR [0010] : java.util.MissingFormatArgumentException: Format specifier
's'
I'm assuming the missing format arg exception is from the fact that the
first line pasted above is missing the version number. Most 'found match'
lines seem to be like:
com.amis.skt.build:osgi.bundle/[2.2.0,3.0.0)#OSGi: Found match
2.3.0.qualifier:2008-01-28T22:34:31.000+0000
This is a bit of a curiosity, but I certainly wouldn't rule out the fact
that I could be doing something wrong with my rmap :)
What is the recommended method for resolving where you're using PDE maps
with cvs readers in the case where you may have multiple cvs paths to
contend with?
eg:
We might have dependencies to resolve like the following:
/path/to/cvs/moduleA/root/buckminster.component
/path/to/cvs/moduleB/root/buckminster.component
is it best to try a match/replace with properties? Or can we use multiple
cvs providers in a search path to coordinate with the PDE map provider?
Your help is appreciated.
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.
|
|
|
| Re: [buckminster-dev] problems with resolve - uncaught exception [message #6838 is a reply to message #5299] |
Sat, 23 February 2008 10:00  |
|
Todd_Lee@amis.com wrote:
> Hi there,
>
> Before I go and file a bug... This is a bit of a curiosity, but I certainly wouldn't rule out the fact
> that I could be doing something wrong with my rmap :)
>
I'm sure this is a bug in the new extended resolver decision logging. Please file this in the bugzilla.
> What is the recommended method for resolving where you're using PDE maps
> with cvs readers in the case where you may have multiple cvs paths to
> contend with?
>
> eg:
>
> We might have dependencies to resolve like the following:
>
> /path/to/cvs/moduleA/root/buckminster.component
> /path/to/cvs/moduleB/root/buckminster.component
>
> is it best to try a match/replace with properties? Or can we use multiple
> cvs providers in a search path to coordinate with the PDE map provider?
>
A PDE map can have multiple entries pointing all over the place. One single map may even appoint
completely different CVS repositories using different protocols. The important thing is to find the
map. From there on, it will build it's internal catalog of component mappings and delegate using
that. So my recommendation would be to use one map folder and put all maps there. Point to that map
folder with a PDEMapProvider and you're all set.
Perhaps your set-up already contain several different map folders? If that's the case, then you can
do one of two things:
1. If it is possible to select the map folder to use from some characteristic of the component name,
then you should use several search paths, one for each map folder that you want to find. Create
locator entries that will cause the resolver to choose the correct search path based on the
component name.
2. If component names have no characteristic that will help you do #1, then create one search path
and add several map providers to that search path. One for each map folder. Order the providers so
that the most commonly used map folder is placed first. The resolver will use all the map folders,
one at a time, to try and resolve the request.
#2 is slightly slower since the scope for the resolution becomes less focused at the end. Given the
nature of the map provider I don't think it will matter that much. Once all maps are read into
memory, it's just hashmap lookups anyway.
Regards,
Thomas Hallgren
|
|
|
|
Powered by
FUDForum. Page generated in 0.01934 seconds
] 
Search
Help
Register
Login
Home
