Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Eclipse RCP plugins automated version number increment
Eclipse RCP plugins automated version number increment [message #525727] Wed, 07 April 2010 11:24 Go to next message
nitesh  is currently offline nitesh
Messages: 8
Registered: December 2009
Junior Member
Hi There,

I am working on to set-up a build server for our OSS project UNICASE (http://code.google.com/p/unicase/) using hudson + buckminster.

I have a small problem as i am quite new to Buckminster.

Our project consists of several plugin based projects and they are combined together as one final product. Now the problem which i have is that i want to automate the version number increment within the Manifest file for each of the plugin before it proceeds to build the final product.
Now as the plugin within our project have cross dependency, i want this new version number to get reflected within the dependency section of the other plugins as well once changed in the Manifest of one.

I hope i was clear enough with the problem statement.

Any help or guidance is welcome!

Thanks in advance,
Nitesh
Re: Eclipse RCP plugins automated version number increment [message #525827 is a reply to message #525727] Wed, 07 April 2010 17:25 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2492
Registered: July 2009
Senior Member
An effective way of handling this is to use a revision number obtained
from the SCM, but it does not work with all SCM types. So, first
question - which SCM are you using?

- henrik

On 4/7/10 5:24 PM, nitesh wrote:
> Hi There,
>
> I am working on to set-up a build server for our OSS project UNICASE
> (http://code.google.com/p/unicase/) using hudson + buckminster.
>
> I have a small problem as i am quite new to Buckminster.
> Our project consists of several plugin based projects and they are
> combined together as one final product. Now the problem which i have is
> that i want to automate the version number increment within the Manifest
> file for each of the plugin before it proceeds to build the final product.
> Now as the plugin within our project have cross dependency, i want this
> new version number to get reflected within the dependency section of the
> other plugins as well once changed in the Manifest of one.
>
> I hope i was clear enough with the problem statement.
>
> Any help or guidance is welcome!
>
> Thanks in advance,
> Nitesh
Re: Eclipse RCP plugins automated version number increment [message #525886 is a reply to message #525827] Thu, 08 April 2010 03:56 Go to previous messageGo to next message
nitesh  is currently offline nitesh
Messages: 8
Registered: December 2009
Junior Member
Hello Henrik,

Thanks for the reply!

We are using subversion and our project is currently hosted at Google code.
Please let me know if you need some more information in order to suggest something.

Regards,
Nitesh
Re: Eclipse RCP plugins automated version n umber increment [message #525907 is a reply to message #525886] Thu, 08 April 2010 04:52 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2492
Registered: July 2009
Senior Member
That is good! SVN has revisions, and the buckminster builds of itself
makes use of the SVN revisions. So you may want to take a look at how
'qualifier replacement' is done in buckminster's build. There is also
info in the buckminster book on this. I think there are other posts in
this forum on this topic as well.

I am on a handheld device at the moment and it is a bit difficult to
give you links to examples, but maybe someone else can paste a couple of
links...

Regards
- Henrik

nitesh <connect2nitesh@gmail.com> wrote:
> Hello Henrik,
>
> Thanks for the reply!
>
> We are using subversion and our project is currently hosted at Google
> code.
> Please let me know if you need some more information in order to
> suggest something.
>
> Regards,
> Nitesh
>


--
- henrik
Re: Eclipse RCP plugins automated version n umber increment [message #525973 is a reply to message #525907] Thu, 08 April 2010 08:59 Go to previous messageGo to next message
nitesh  is currently offline nitesh
Messages: 8
Registered: December 2009
Junior Member
Hello Henrik,

I followed the following tutorial to setup qualifier replacement and now finally i am getting the error given below. Any clue to fix the problem!

Doing full workspace refresh
Waiting for jobs to end
perform '-D' 'target.os=*' '-D' 'target.ws=*' '-D' 'target.arch=*' '-D' 'qualifier.replacement.*=N20100408-1 org.unicase.emfstore.feature.site#site.p2'
Doing full workspace refresh
Waiting for jobs to end
No attributes specified
Help text for org.eclipse.buckminster.core.perform:This command performs actions on components

usage: perform
       [{ -? | --help }]
       [{-D | --define} <key>[=<value>]]
       [{-P | --properties} <URL or Path>]
       [{-W | --maxWarnings} <n>]
       <component>#<action> [<component>#<action> ...]

 -?
--help
  Show this help text
 -D
--define
  Defines a property as a key=value pair. The value may include ant-style expansion constructs
  that will be expanded using both System properties and other properties that has been set.

 -P <URL or Path>
--properties <URL or Path>
  The URL or file system path of a properties file. The values in the file may include ant-style
  expansion constructs that will be expanded using both System properties and other properties
  that has been set.

 -W
--maxwarnings
  Give the number of warnings acceptable. If the number of warnings are higher,
  treat as error and exit with 1.
  Default is infinite warnings.

 -F
--forced
  Force all actions regardless of timestamps

 -Q
--quiet
  Don't print errors and warnings. Just exit with a non zero exit code on failure

<component>#<action>
  The component name and the action name to perform.
  Can be given multiple times in order to perform many actions in the most
  optimized way.Archiving artifacts
Finished: FAILURE


Thanks in advance.
Re: Eclipse RCP plugins automated version n umber increment [message #526112 is a reply to message #525973] Thu, 08 April 2010 13:36 Go to previous message
Achim Demelt is currently offline Achim Demelt
Messages: 160
Registered: July 2009
Senior Member
Nitesh,

It seems your arguments are incorrectly quoted:

perform '-D' 'target.os=*' '-D' 'target.ws=*' '-D' 'target.arch=*' '-D'
'qualifier.replacement.*=N20100408-1
org.unicase.emfstore.feature.site#site.p2'

should be

perform '-D' 'target.os=*' '-D' 'target.ws=*' '-D' 'target.arch=*' '-D'
'qualifier.replacement.*=N20100408-1'
'org.unicase.emfstore.feature.site#site.p2'

Note the quotes to separate the arguments between '...N20100408-1' and
'org.unicase...'

Achim



nitesh wrote:

> Hello Henrik,
>
> I followed the following
> http://swissdev.blogspot.com/2010/03/building-products-with. html to setup
> qualifier replacement and now finally i am getting the error given below.
> Any clue to fix the problem!
>
> Doing full workspace refresh
> Waiting for jobs to end
> perform '-D' 'target.os=*' '-D' 'target.ws=*' '-D' 'target.arch=*' '-D'
> 'qualifier.replacement.*=N20100408-1
> org.unicase.emfstore.feature.site#site.p2' Doing full workspace refresh
> Waiting for jobs to end No attributes specified
> Help text for org.eclipse.buckminster.core.perform:This command performs
> actions on components
>
> usage: perform
> [{ -? | --help }]
> [{-D | --define} <key>[=<value>]]
> [{-P | --properties} <URL or Path>]
> [{-W | --maxWarnings} <n>]
> <component>#<action> [<component>#<action> ...]
>
> -?
> --help
> Show this help text
> -D
> --define
> Defines a property as a key=value pair. The value may include ant-style
> expansion constructs that will be expanded using both System properties
> and other properties that has been set.
>
> -P <URL or Path>
> --properties <URL or Path>
> The URL or file system path of a properties file. The values in the file
> may include ant-style expansion constructs that will be expanded using
> both System properties and other properties that has been set.
>
> -W
> --maxwarnings
> Give the number of warnings acceptable. If the number of warnings are
> higher, treat as error and exit with 1.
> Default is infinite warnings.
>
> -F
> --forced
> Force all actions regardless of timestamps
>
> -Q
> --quiet
> Don't print errors and warnings. Just exit with a non zero exit code on
> failure
>
> <component>#<action>
> The component name and the action name to perform.
> Can be given multiple times in order to perform many actions in the most
> optimized way.Archiving artifacts
> Finished: FAILURE
>
>
> Thanks in advance.
Previous Topic:Building Products with Buckminster/Hudson
Next Topic:Custom builders are not invoked in headless build
Goto Forum:
  


Current Time: Wed Apr 23 02:52:34 EDT 2014

Powered by FUDForum. Page generated in 0.02041 seconds