Quantcast

buildnumber plugin - last revision vs revision

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

buildnumber plugin - last revision vs revision

j.tosovsky
Dear All,

I'd like to implement versioning of my builds based on actual SVN revisions.

However, when using buildnumber plugin, it returns the revision of top level
folder (repository root), not my subfolder.

When running the following command in console, which seems to be executed
via plugin during the build process:

svn --non-interactive info C:\trunk\liferay\test-portlet

I am getting the following outcome:

Path: C:\trunk\liferay\test-portlet
Working Copy Root Path: C:\trunk
URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet
Relative URL: ^/trunk/liferay/test-portlet
Repository Root: https://svn.doctribute.org/svn/dev
Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a
Revision: 44044
Node Kind: directory
Schedule: normal
Last Changed Author: j.tosovsky
Last Changed Rev: 43992
Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017)


For my use I'd prefer using 'Last Changed Rev' and 'Last Changed Date' for
the final buildNumber and timestamp respectively. Currently I am getting
44044, which is not the revision of my code, but the revision of other
(sister) project.

I've tried to modify this option (with both true/false values), but the
result is same:
<useLastCommittedRevision>false</useLastCommittedRevision>
(I am not sure I understand the meaning of this feature)

Is there any chance to utilize 'Last Changed XXX' entries?

Thanks,

Jan



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: buildnumber plugin - last revision vs revision

Karl Heinz Marbaise-3
Hi Jan,

On 30/03/17 22:01, Jan Tosovsky wrote:

> Dear All,
>
> I'd like to implement versioning of my builds based on actual SVN revisions.
>
> However, when using buildnumber plugin, it returns the revision of top level
> folder (repository root), not my subfolder.
>
> When running the following command in console, which seems to be executed
> via plugin during the build process:
>
> svn --non-interactive info C:\trunk\liferay\test-portlet
>
> I am getting the following outcome:
>
> Path: C:\trunk\liferay\test-portlet
> Working Copy Root Path: C:\trunk
> URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet
> Relative URL: ^/trunk/liferay/test-portlet
> Repository Root: https://svn.doctribute.org/svn/dev
> Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a
> Revision: 44044
> Node Kind: directory
> Schedule: normal
> Last Changed Author: j.tosovsky
> Last Changed Rev: 43992
> Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017)
>
>
> For my use I'd prefer using 'Last Changed Rev' and 'Last Changed Date' for
> the final buildNumber and timestamp respectively. Currently I am getting
> 44044, which is not the revision of my code, but the revision of other
> (sister) project.
>
> I've tried to modify this option (with both true/false values), but the
> result is same:
> <useLastCommittedRevision>false</useLastCommittedRevision>
> (I am not sure I understand the meaning of this feature)
>
> Is there any chance to utilize 'Last Changed XXX' entries?

which version of the buildnumber-maven-plugin do you use?

Kind regards
Karl Heinz Marbaise

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: buildnumber plugin - last revision vs revision

j.tosovsky
On 2017-03-30 Karl Heinz Marbaise wrote:

> On 30/03/17 22:01, Jan Tosovsky wrote:
> >
> > I'd like to implement versioning of my builds based on actual SVN
> > revisions.
> >
> > However, when using buildnumber plugin, it returns the revision of
> > top level folder (repository root), not my subfolder.
> >
> > When running the following command in console, which seems to be
> > executed via plugin during the build process:
> >
> > svn --non-interactive info C:\trunk\liferay\test-portlet
> >
> > I am getting the following outcome:
> >
> > Path: C:\trunk\liferay\test-portlet
> > Working Copy Root Path: C:\trunk
> > URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet
> > Relative URL: ^/trunk/liferay/test-portlet
> > Repository Root: https://svn.doctribute.org/svn/dev
> > Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a
> > Revision: 44044
> > Node Kind: directory
> > Schedule: normal
> > Last Changed Author: j.tosovsky
> > Last Changed Rev: 43992
> > Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017)
> >
> >
> > For my use I'd prefer using 'Last Changed Rev' and 'Last Changed
> > Date' for the final buildNumber and timestamp respectively.
> > Currently I am getting 44044, which is not the revision of my code,
> > but the revision of other (sister) project.
> >
> > I've tried to modify this option (with both true/false values), but
> > the result is same:
> > <useLastCommittedRevision>false</useLastCommittedRevision>
> > (I am not sure I understand the meaning of this feature)
> >
> > Is there any chance to utilize 'Last Changed XXX' entries?
>
> which version of the buildnumber-maven-plugin do you use?

oops, it is 1.4.

In meantime I found GitHub Pages and my issue resembles
https://github.com/mojohaus/buildnumber-maven-plugin/issues/36

and also (fixed, but not released yet)
https://github.com/mojohaus/buildnumber-maven-plugin/issues/38

But there is also a pull request mentioning the support for the Last Changed Date (what I need as well):
https://github.com/mojohaus/buildnumber-maven-plugin/pull/16


So I most likely need to integrate that pull request and to build the custom version from sources to get correct behavior. Or is there planned any new build (the last one was in 2015)?

Thanks, Jan


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: buildnumber plugin - last revision vs revision

Karl Heinz Marbaise-3
Hi Jan,

On 31/03/17 00:18, Jan Tosovsky wrote:

> On 2017-03-30 Karl Heinz Marbaise wrote:
>> On 30/03/17 22:01, Jan Tosovsky wrote:
>>>
>>> I'd like to implement versioning of my builds based on actual SVN
>>> revisions.
>>>
>>> However, when using buildnumber plugin, it returns the revision of
>>> top level folder (repository root), not my subfolder.
>>>
>>> When running the following command in console, which seems to be
>>> executed via plugin during the build process:
>>>
>>> svn --non-interactive info C:\trunk\liferay\test-portlet
>>>
>>> I am getting the following outcome:
>>>
>>> Path: C:\trunk\liferay\test-portlet
>>> Working Copy Root Path: C:\trunk
>>> URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet
>>> Relative URL: ^/trunk/liferay/test-portlet
>>> Repository Root: https://svn.doctribute.org/svn/dev
>>> Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a
>>> Revision: 44044
>>> Node Kind: directory
>>> Schedule: normal
>>> Last Changed Author: j.tosovsky
>>> Last Changed Rev: 43992
>>> Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017)
>>>
>>>
>>> For my use I'd prefer using 'Last Changed Rev' and 'Last Changed
>>> Date' for the final buildNumber and timestamp respectively.
>>> Currently I am getting 44044, which is not the revision of my code,
>>> but the revision of other (sister) project.
>>>
>>> I've tried to modify this option (with both true/false values), but
>>> the result is same:
>>> <useLastCommittedRevision>false</useLastCommittedRevision>
>>> (I am not sure I understand the meaning of this feature)
>>>
>>> Is there any chance to utilize 'Last Changed XXX' entries?
>>
>> which version of the buildnumber-maven-plugin do you use?
>
> oops, it is 1.4.

Just fine that is the latest release of it...

>
> In meantime I found GitHub Pages and my issue resembles
> https://github.com/mojohaus/buildnumber-maven-plugin/issues/36
>
> and also (fixed, but not released yet)
> https://github.com/mojohaus/buildnumber-maven-plugin/issues/38
>
> But there is also a pull request mentioning the support for the Last Changed Date (what I need as well):
> https://github.com/mojohaus/buildnumber-maven-plugin/pull/16
>
>
> So I most likely need to integrate that pull request and to build the custom version from sources to get correct behavior. Or is there planned any new build (the last one was in 2015)?
>
> Thanks, Jan

At the moment I'm working on such issues...and trying to fix some of
them...cause the 3.0.0 milestone has a large number of fixes in the
meantime...I'm thinking of making a release of it within the next few
weeks...


Kind regards
Karl Heinz Marbaise

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: buildnumber plugin - last revision vs revision

j.tosovsky
Hi Karl Heinz,

On 2017-03-31 Karl Heinz Marbaise wrote:

> On 31/03/17 00:18, Jan Tosovsky wrote:
> > On 2017-03-30 Karl Heinz Marbaise wrote:
> >> On 30/03/17 22:01, Jan Tosovsky wrote:
> >>>
> >>> I'd like to implement versioning of my builds based on actual SVN
> >>> revisions.
> >>>
> >>> However, when using buildnumber plugin, it returns the revision of
> >>> top level folder (repository root), not my subfolder.
> >>>
> >>> When running the following command in console, which seems to be
> >>> executed via plugin during the build process:
> >>>
> >>> svn --non-interactive info C:\trunk\liferay\test-portlet
> >>>
> >>> I am getting the following outcome:
> >>>
> >>> Path: C:\trunk\liferay\test-portlet
> >>> Working Copy Root Path: C:\trunk
> >>> URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet
> >>> Relative URL: ^/trunk/liferay/test-portlet
> >>> Repository Root: https://svn.doctribute.org/svn/dev
> >>> Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a
> >>> Revision: 44044
> >>> Node Kind: directory
> >>> Schedule: normal
> >>> Last Changed Author: j.tosovsky
> >>> Last Changed Rev: 43992
> >>> Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017)
> >>>
> >>>
> >>> For my use I'd prefer using 'Last Changed Rev' and 'Last Changed
> >>> Date' for the final buildNumber and timestamp respectively.
> >>> Currently I am getting 44044, which is not the revision of my code,
> >>> but the revision of other (sister) project.
> >>>
> >>> I've tried to modify this option (with both true/false values), but
> >>> the result is same:
> >>> <useLastCommittedRevision>false</useLastCommittedRevision>
> >>> (I am not sure I understand the meaning of this feature)
> >>>
> >>> Is there any chance to utilize 'Last Changed XXX' entries?
> >>
> >> which version of the buildnumber-maven-plugin do you use?
> >
> > oops, it is 1.4.
>
> Just fine that is the latest release of it...
>
> >
> > In meantime I found GitHub Pages and my issue resembles
> > https://github.com/mojohaus/buildnumber-maven-plugin/issues/36
> >
> > and also (fixed, but not released yet)
> > https://github.com/mojohaus/buildnumber-maven-plugin/issues/38
> >
> > But there is also a pull request mentioning the support for the
> > Last Changed Date (what I need as well):
> > https://github.com/mojohaus/buildnumber-maven-plugin/pull/16
> >
> >
> > So I most likely need to integrate that pull request and to build
> > the custom version from sources to get correct behavior. Or is
> > there planned any new build (the last one was in 2015)?
> >
>
> At the moment I'm working on such issues...and trying to fix some of
> them...cause the 3.0.0 milestone has a large number of fixes in the
> meantime...I'm thinking of making a release of it within the next
> few weeks...
>

I'll wait then (even it will take even longer). Thanks a lot!

Btw, I'd be grateful for implementing especially this one:
https://github.com/mojohaus/buildnumber-maven-plugin/issues/17

;-)

Jan


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...