Eclipse Community Forums: Buckminster dev » [buckminster-dev] CQuery and "svn update" operation

Help

Home

Home » Eclipse Projects » Buckminster dev » [buckminster-dev] CQuery and "svn update" operation

Show: Today's Messages :: Show Polls :: Message Navigator

[buckminster-dev] CQuery and "svn update" operation [message #25618]

Tue, 23 September 2008 18:38

Eclipse User

Originally posted by: Mark.Addleman.ca.com

This is a multi-part message in MIME format.

------_=_NextPart_001_01C91DAB.9F16551A
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi, folks -

=20

We're trying to hook up Buckminster to do our headless build. We'd like
Buckminster to control as much of the process as possible including
checking out from Subversion. It appears that Buckminster does a great
job of checking out from Subversion into a clean workspace but it does
not perform the equivalent of an "svn update" if the necessary projects
already exist in the workspace.

=20

>From the documentation, it looks like an MSpec has a conflictResolution
node that will perform an update, but we can't get that to work, either.

=20

Below is our CQuery:

=20

<?xml version=3D"1.0" encoding=3D"UTF-8"?>

<cq:componentQuery
xmlns:cq=3D"http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap=3D"file:/C:/Documents%20and%20Settings/ADDMA03/Desktop/m365.r=
m
ap">

<cq:rootRequest name=3D"m365.reports" =
componentType=3D"osgi.bundle"/>

</cq:componentQuery>

=20

Here is our RMap:

<?xml version=3D"1.0" encoding=3D"UTF-8"?>

<rmap

xmlns=3D"http://www.eclipse.org/buckminster/RMap-1.0"

xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"

xmlns:mp=3D"http://www.eclipse.org/buckminster/MavenProvider-1.0"

xmlns:bc=3D"http://www.eclipse.org/buckminster/Common-1.0">

=20

<searchPath name=3D"m365">

<provider

readerType=3D"svn"

componentTypes=3D"eclipse.feature,osgi.bundle"

source=3D"true" mutable=3D"true">

<uri

format=3D"https://machine/svn/m365subversion/trunk/{0}">

<bc:propertyRef key=3D"buckminster.component" />

</uri>

</provider>

</searchPath>

=20

<locator searchPathRef=3D"m365" pattern=3D"^lib.*" />

<locator searchPathRef=3D"m365" pattern=3D"^m365.*" />

<locator searchPathRef=3D"m365" pattern=3D"^com.*" />

<locator searchPathRef=3D"m365" pattern=3D"^org.apache.commons.dbcp" =
/>

<locator searchPathRef=3D"m365" pattern=3D"^wily.*" />

=20

<redirect

=
href=3D" http://www.eclipse.org/buckminster/samples/rmaps/dogfood2.rm ap"

pattern=3D".*" />

</rmap>

=20

=20

=20

=20

------_=_NextPart_001_01C91DAB.9F16551A
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=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>

</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3D"#606420">

<div class=3DSection1>

Hi, folks –<o:p></o:p>

<o:p> </o:p>

We’re trying to hook up Buckminster to do our =
headless
build.  We’d like Buckminster to control as much of the =
process as
possible including checking out from Subversion.  It appears that
Buckminster does a great job of checking out from Subversion into a =
clean
workspace but it does not perform the equivalent of an “svn =
update”
if the necessary projects already exist in the =
workspace.<o:p></o:p>

<o:p> </o:p>

From the documentation, it looks like an MSpec has a
conflictResolution node that will perform an update, but we can’t =
get
that to work, either.<o:p></o:p>

<o:p> </o:p>

Below is our CQuery:<o:p></o:p>

<o:p> </o:p>

<?xml
version=3D"1.0" =
encoding=3D"UTF-8"?><o:p></o:p>

<cq:componentQuery
xmlns:cq=3D"http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap=3D"file:/C:/Documents%20and%20Settings/ ADDMA03/Desktop/m=
365.rmap"><o:p></o:p>

   
<cq:rootRequest name=3D"m365.reports" =
componentType=3D"osgi.bundle"/><o:p ></o:p>=

</cq:componentQuery><o:p></o:p>

<o:p> </o:p>

Here is our RMap:<o:p></o:p>

<?xml
version=3D"1.0" =
encoding=3D"UTF-8"?><o:p></o:p>

<rmap<o:p></o:p>

 xmlns=3D"http://www.eclipse.org/buckminster/RMap-1.0&quo=
t;<o:p></o:p>

 xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance&q=
uot;<o:p></o:p>

 xmlns:mp=3D"http://www.eclipse.org/buckminster/MavenProv=
ider-1.0"<o:p></o:p>

 xmlns:bc=3D"http://www.eclipse.org/buckminster/Common-1.=
0"><o:p></o:p>

<o:p> </o:p>

  =
<searchPath
name=3D"m365"><o:p></o:p> 

   
<provider<o:p></o:p>

    
readerType=3D"svn"<o:p></o:p>

    
componentTypes=3D"eclipse.feature,osgi.bundle&q uot; <o:p></o:p></span=
>

    
source=3D"true" =
mutable=3D"true"><o:p></o:p>

     
<uri<o:p></o:p>

       
format=3D"https://machine/svn/m365subversion/trunk/{0}"><o:p=
></o:p>

         
<bc:propertyRef key=3D"buckminster.component" =
/><o:p></o:p>

     
</uri><o:p></o:p>

   
</provider><o:p></o:p>

  =
</searchPath><o:p></o:p>

<o:p> </o:p>

  <locator
searchPathRef=3D"m365" pattern=3D"^lib.*" =
/><o:p></o:p>

  <locator =
searchPathRef=3D"m365"
pattern=3D"^m365.*" /><o:p></o:p>

  <locator
searchPathRef=3D"m365" pattern=3D"^com.*" =
/><o:p></o:p>

  <locator
searchPathRef=3D"m365" =
pattern=3D"^org.apache.commons.dbcp"
/><o:p></o:p>

  <locator
searchPathRef=3D"m365" pattern=3D"^wily.*" =
/><o:p></o:p>

<o:p> </o:p>

  =
<redirect<o:p></o:p>

  
href=3D" http://www.eclipse.org/buckminster/samples/rmaps/dogfood2.rm =
ap"<o:p></o:p>

  
pattern=3D".*" /><o:p></o:p>

</rmap><o:p></o:p>

<o:p> </o:p>

<o:p>  </o:p></fo=
nt>

<o:p>  </o:p></fo=
nt>

<o:p> </o:p>

</div>

</body>

</html>

------_=_NextPart_001_01C91DAB.9F16551A--

Report message to a moderator

Re: [buckminster-dev] CQuery and "svn update" operation [message #25658 is a reply to message #25618]

Wed, 24 September 2008 10:23

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

Hi Mark,
The MSPEC approach does not work properly at present (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=192657) but you can still make it happen. If
you define an AdvisorNode in you cquery that covers the components in question and where
you prohibit resolution against the workspace, then SVN check-outs will be made always.
The check-out command will detect the current content and perform an update.

Regards,
Thomas Hallgren

Addleman, Mark J wrote:
> Hi, folks –
>
>
>
> We’re trying to hook up Buckminster to do our headless build. We’d like
> Buckminster to control as much of the process as possible including
> checking out from Subversion. It appears that Buckminster does a great
> job of checking out from Subversion into a clean workspace but it does
> not perform the equivalent of an “svn update” if the necessary projects
> already exist in the workspace.
>
>
>
> From the documentation, it looks like an MSpec has a conflictResolution
> node that will perform an update, but we can’t get that to work, either.
>
>
>
> Below is our CQuery:
>
>
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <cq:componentQuery
> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
> resourceMap=" file:/C:/Documents%20and%20Settings/ADDMA03/Desktop/m365.rma p ">
>
> <cq:rootRequest name="m365.reports" componentType="osgi.bundle"/>
>
> </cq:componentQuery>
>
>
>
> Here is our 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="m365">
>
> <provider
>
> readerType="svn"
>
> componentTypes="eclipse.feature,osgi.bundle"
>
> source="true" mutable="true">
>
> <uri
>
> format="https://machine/svn/m365subversion/trunk/{0}">
>
> <bc:propertyRef key="buckminster.component" />
>
> </uri>
>
> </provider>
>
> </searchPath>
>
>
>
> <locator searchPathRef="m365" pattern="^lib.*" />
>
> <locator searchPathRef="m365" pattern="^m365.*" />
>
> <locator searchPathRef="m365" pattern="^com.*" />
>
> <locator searchPathRef="m365" pattern="^org.apache.commons.dbcp" />
>
> <locator searchPathRef="m365" pattern="^wily.*" />
>
>
>
> <redirect
>
> href=" http://www.eclipse.org/buckminster/samples/rmaps/dogfood2.rm ap"
>
> pattern=".*" />
>
> </rmap>
>
>
>
>
>
>
>
>
>

Report message to a moderator

RE: [buckminster-dev] CQuery and "svn update" operation [message #25690 is a reply to message #25658]

Wed, 24 September 2008 16:01

Eclipse User

Originally posted by: Mark.Addleman.ca.com

Thanks, Thomas.

I just want to say that Buckminster has turned our eclipse headless
build from a nightmare to set up to nearly a pleasure. It took us about
two man-weeks to set up the traditional Eclipse headless build. It took
us about one man-day to reach the same state with Buckminster. Thanks!
Keep up the good work.

-----Original Message-----
From: buckminster-dev-bounces@eclipse.org
[mailto:buckminster-dev-bounces@eclipse.org] On Behalf Of Thomas
Hallgren
Sent: Wednesday, September 24, 2008 3:24 AM
To: Buckminster developer discussions
Subject: Re: [buckminster-dev] CQuery and "svn update" operation

Hi Mark,
The MSPEC approach does not work properly at present (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=192657) but you can still
make it happen. If
you define an AdvisorNode in you cquery that covers the components in
question and where
you prohibit resolution against the workspace, then SVN check-outs will
be made always.
The check-out command will detect the current content and perform an
update.

Regards,
Thomas Hallgren

Addleman, Mark J wrote:
> Hi, folks -
>
>
>
> We're trying to hook up Buckminster to do our headless build. We'd
like
> Buckminster to control as much of the process as possible including
> checking out from Subversion. It appears that Buckminster does a
great
> job of checking out from Subversion into a clean workspace but it does

> not perform the equivalent of an "svn update" if the necessary
projects
> already exist in the workspace.
>
>
>
> From the documentation, it looks like an MSpec has a
conflictResolution
> node that will perform an update, but we can't get that to work,
either.
>
>
>
> Below is our CQuery:
>
>
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <cq:componentQuery
> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>
resourceMap="file:/C:/Documents%20and%20Settings/ADDMA03/Desktop/m365.rm
ap">
>
> <cq:rootRequest name="m365.reports" componentType="osgi.bundle"/>
>
> </cq:componentQuery>
>
>
>
> Here is our 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="m365">
>
> <provider
>
> readerType="svn"
>
> componentTypes="eclipse.feature,osgi.bundle"
>
> source="true" mutable="true">
>
> <uri
>
> format="https://machine/svn/m365subversion/trunk/{0}">
>
> <bc:propertyRef key="buckminster.component" />
>
> </uri>
>
> </provider>
>
> </searchPath>
>
>
>
> <locator searchPathRef="m365" pattern="^lib.*" />
>
> <locator searchPathRef="m365" pattern="^m365.*" />
>
> <locator searchPathRef="m365" pattern="^com.*" />
>
> <locator searchPathRef="m365" pattern="^org.apache.commons.dbcp" />
>
> <locator searchPathRef="m365" pattern="^wily.*" />
>
>
>
> <redirect
>
>
href=" http://www.eclipse.org/buckminster/samples/rmaps/dogfood2.rm ap"
>
> pattern=".*" />
>
> </rmap>
>
>
>
>
>
>
>
>
>

_______________________________________________
buckminster-dev mailing list
buckminster-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/buckminster-dev

Report message to a moderator

Previous Topic:	Re: [buckminster-dev] PDE headless build of RCP headless product ... "The System Bundle's start
Next Topic:	E4 Resources discussions

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 12:15:42 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter