[buckminster-dev] Resolving latest & specified subversion tag [message #29981] |
Tue, 13 January 2009 03:20 |
Eclipse User |
|
|
|
Originally posted by: Mark.Addleman.ca.com
This is a multi-part message in MIME format.
------_=_NextPart_001_01C9752D.D642FBCD
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I have several CQUERY files that represent the various components of our
system. I'd like to have a single CQUERY file per component that
references different tagged versions in our subversion repository. I
think that means I want to parameterize the rootRequests's
versionDesignator attribute, but I can't figure out how to get that to
work. I've tried:
<cq:componentQuery=20
xmlns:cq=3D"http://www.eclipse.org/buckminster/CQuery-1.0"=20
xmlns:com=3D"http://www.eclipse.org/buckminster/Common-1.0"=20
resourceMap=3D"m365.rmap">
<cq:rootRequest name=3D"m365.messaging.receiver.feature"
componentType=3D"eclipse.feature"
versionType=3D"OSGi"
versionDesignator=3D"[${version},${version}]" />
<cq:property key=3D"${version}" value=3D"1.0.0"/>
</cq:componentQuery>
=20
This yields an error saying that "${version}" isn't a valid OSGi version
specifier. That leads me to believe the versionDesignator isn't doesn't
resolve properties. Is this so? Is this a bug or am I approaching the
problem incorrectly? I have a sneaking suspicion that I should be using
the RMAP to provide this kind of flexibility.
------_=_NextPart_001_01C9752D.D642FBCD
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
..MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal>I have several CQUERY files that represent the =
various
components of our system. I’d like to have a single CQUERY =
file per
component that references different tagged versions in our subversion =
repository.
I think that means I want to parameterize the rootRequests’s =
versionDesignator
attribute, but I can’t figure out how to get that to work. =
I’ve
tried:<o:p></o:p></p>
<p class=3DMsoNormal><cq:componentQuery <o:p></o:p></p>
<p class=3DMsoNormal>
xmlns:cq=3D"http://www.eclipse.org/buckminster/CQuery-1.0" =
<o:p></o:p></p>
<p class=3DMsoNormal>
xmlns:com=3D"http://www.eclipse.org/buckminster/Common-1.0" =
<o:p></o:p></p>
<p class=3DMsoNormal>
resourceMap=3D"m365.rmap"><o:p></o:p ></p>
<p class=3DMsoNormal> <cq:rootRequest
name=3D"m365.messaging.receiver.feature"
componentType=3D"eclipse.feature"<o:p></o:p ></p>
<p class=3DMsoNormal>
versionType=3D"OSGi"<o:p></o:p></p>
<p class=3DMsoNormal>
versionDesignator=3D"[${version},${version}]&qu ot; =
/><o:p></o:p></p>
<p class=3DMsoNormal> =
<cq:property
key=3D"${version}" =
value=3D"1.0.0"/><o:p></o:p></p>
<p class=3DMsoNormal></cq:componentQuery><o:p></o:p ></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>This yields an error saying that =
“${version}”
isn’t a valid OSGi version specifier. That leads me to =
believe the
versionDesignator isn’t doesn’t resolve properties. Is =
this
so? Is this a bug or am I approaching the problem =
incorrectly? I
have a sneaking suspicion that I should be using the RMAP to provide =
this kind
of flexibility.<o:p></o:p></p>
</div>
</body>
</html>
------_=_NextPart_001_01C9752D.D642FBCD--
|
|
|
Re: [buckminster-dev] Resolving latest & specified subversion tag [message #30012 is a reply to message #29981] |
Wed, 14 January 2009 17:26 |
|
Hi Mark,
You're right. The versoinDesignator is not subject to property
expansion. Perhaps it should be. Can you please enter a bugzilla?
Thanks,
Thomas Hallgren
Addleman, Mark J wrote:
> I have several CQUERY files that represent the various components of our
> system. I’d like to have a single CQUERY file per component that
> references different tagged versions in our subversion repository. I
> think that means I want to parameterize the rootRequests’s
> versionDesignator attribute, but I can’t figure out how to get that to
> work. I’ve tried:
>
> <cq:componentQuery
>
> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>
> xmlns:com="http://www.eclipse.org/buckminster/Common-1.0"
>
> resourceMap="m365.rmap">
>
> <cq:rootRequest name="m365.messaging.receiver.feature"
> componentType="eclipse.feature"
>
> versionType="OSGi"
>
> versionDesignator="[${version},${version}]" />
>
> <cq:property key="${version}" value="1.0.0"/>
>
> </cq:componentQuery>
>
>
>
> This yields an error saying that “${version}” isn’t a valid OSGi version
> specifier. That leads me to believe the versionDesignator isn’t doesn’t
> resolve properties. Is this so? Is this a bug or am I approaching the
> problem incorrectly? I have a sneaking suspicion that I should be using
> the RMAP to provide this kind of flexibility.
>
|
|
|
Powered by
FUDForum. Page generated in 0.03051 seconds