You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rupert Smith (JIRA)" <qp...@incubator.apache.org> on 2006/12/21 17:06:20 UTC
[jira] Created: (QPID-227) Would be nice if Maven created
properties file with version info and build #.
Would be nice if Maven created properties file with version info and build #.
-----------------------------------------------------------------------------
Key: QPID-227
URL: http://issues.apache.org/jira/browse/QPID-227
Project: Qpid
Issue Type: New Feature
Components: Maven build system
Reporter: Rupert Smith
Priority: Minor
Would be nice if Maven created properties file with version info and build # in it. The client and broker could then log the version info at startup time as a sanity check when running tests. The version info could also be easily examined and added to bug reports to avoid confusion.
As subversion is so good at reporting the version, the results of running the 'svnversion' command during a build can be used as an accurate build # reference that everyone can standardize on.
Attached is a path to add this to the Maven build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Updated: (QPID-227) Would be nice if Maven created properties file with version info and build #.
Posted by Rupert Smith <ru...@googlemail.com>.
Actually, it has already been applied by Bhupendra. I am just about to add a
comment to that effect and close the JIRA.
Rupert
On 12/21/06, Steve Vinoski <vi...@iona.com> wrote:
>
> Thanks Rupert, this looks useful. Unless anyone has any objections,
> I'll apply the patch later today.
>
> --steve
>
> On Dec 21, 2006, at 11:08 AM, Rupert Smith (JIRA) wrote:
>
> > [ http://issues.apache.org/jira/browse/QPID-227?page=all ]
> >
> > Rupert Smith updated QPID-227:
> > ------------------------------
> >
> > Attachment: QPID-227.diff
> >
> > Here is the patch for version stamping.
> >
> >> Would be nice if Maven created properties file with version info
> >> and build #.
> >> ---------------------------------------------------------------------
> >> --------
> >>
> >> Key: QPID-227
> >> URL: http://issues.apache.org/jira/browse/QPID-227
> >> Project: Qpid
> >> Issue Type: New Feature
> >> Components: Maven build system
> >> Reporter: Rupert Smith
> >> Priority: Minor
> >> Attachments: QPID-227.diff
> >>
> >>
> >> Would be nice if Maven created properties file with version info
> >> and build # in it. The client and broker could then log the
> >> version info at startup time as a sanity check when running tests.
> >> The version info could also be easily examined and added to bug
> >> reports to avoid confusion.
> >> As subversion is so good at reporting the version, the results of
> >> running the 'svnversion' command during a build can be used as an
> >> accurate build # reference that everyone can standardize on.
> >> Attached is a path to add this to the Maven build.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the
> > administrators: http://issues.apache.org/jira/secure/
> > Administrators.jspa
> > -
> > For more information on JIRA, see: http://www.atlassian.com/
> > software/jira
> >
> >
>
>
Re: [jira] Updated: (QPID-227) Would be nice if Maven created properties file with version info and build #.
Posted by Steve Vinoski <vi...@iona.com>.
Thanks Rupert, this looks useful. Unless anyone has any objections,
I'll apply the patch later today.
--steve
On Dec 21, 2006, at 11:08 AM, Rupert Smith (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/QPID-227?page=all ]
>
> Rupert Smith updated QPID-227:
> ------------------------------
>
> Attachment: QPID-227.diff
>
> Here is the patch for version stamping.
>
>> Would be nice if Maven created properties file with version info
>> and build #.
>> ---------------------------------------------------------------------
>> --------
>>
>> Key: QPID-227
>> URL: http://issues.apache.org/jira/browse/QPID-227
>> Project: Qpid
>> Issue Type: New Feature
>> Components: Maven build system
>> Reporter: Rupert Smith
>> Priority: Minor
>> Attachments: QPID-227.diff
>>
>>
>> Would be nice if Maven created properties file with version info
>> and build # in it. The client and broker could then log the
>> version info at startup time as a sanity check when running tests.
>> The version info could also be easily examined and added to bug
>> reports to avoid confusion.
>> As subversion is so good at reporting the version, the results of
>> running the 'svnversion' command during a build can be used as an
>> accurate build # reference that everyone can standardize on.
>> Attached is a path to add this to the Maven build.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators: http://issues.apache.org/jira/secure/
> Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/
> software/jira
>
>
[jira] Updated: (QPID-227) Would be nice if Maven created
properties file with version info and build #.
Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-227?page=all ]
Rupert Smith updated QPID-227:
------------------------------
Attachment: QPID-227.diff
Here is the patch for version stamping.
> Would be nice if Maven created properties file with version info and build #.
> -----------------------------------------------------------------------------
>
> Key: QPID-227
> URL: http://issues.apache.org/jira/browse/QPID-227
> Project: Qpid
> Issue Type: New Feature
> Components: Maven build system
> Reporter: Rupert Smith
> Priority: Minor
> Attachments: QPID-227.diff
>
>
> Would be nice if Maven created properties file with version info and build # in it. The client and broker could then log the version info at startup time as a sanity check when running tests. The version info could also be easily examined and added to bug reports to avoid confusion.
> As subversion is so good at reporting the version, the results of running the 'svnversion' command during a build can be used as an accurate build # reference that everyone can standardize on.
> Attached is a path to add this to the Maven build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (QPID-227) Would be nice if Maven created
properties file with version info and build #.
Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-227?page=comments#action_12460301 ]
Rupert Smith commented on QPID-227:
-----------------------------------
Bhupendra has applied the patch.
> Would be nice if Maven created properties file with version info and build #.
> -----------------------------------------------------------------------------
>
> Key: QPID-227
> URL: http://issues.apache.org/jira/browse/QPID-227
> Project: Qpid
> Issue Type: New Feature
> Components: Maven build system
> Reporter: Rupert Smith
> Priority: Minor
> Attachments: QPID-227.diff
>
>
> Would be nice if Maven created properties file with version info and build # in it. The client and broker could then log the version info at startup time as a sanity check when running tests. The version info could also be easily examined and added to bug reports to avoid confusion.
> As subversion is so good at reporting the version, the results of running the 'svnversion' command during a build can be used as an accurate build # reference that everyone can standardize on.
> Attached is a path to add this to the Maven build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (QPID-227) Would be nice if Maven created
properties file with version info and build #.
Posted by "Bhupendra Bhardwaj (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-227?page=all ]
Bhupendra Bhardwaj resolved QPID-227.
-------------------------------------
Fix Version/s: M2
Resolution: Fixed
Assignee: Bhupendra Bhardwaj
> Would be nice if Maven created properties file with version info and build #.
> -----------------------------------------------------------------------------
>
> Key: QPID-227
> URL: http://issues.apache.org/jira/browse/QPID-227
> Project: Qpid
> Issue Type: New Feature
> Components: Maven build system
> Reporter: Rupert Smith
> Assigned To: Bhupendra Bhardwaj
> Priority: Minor
> Fix For: M2
>
> Attachments: QPID-227.diff
>
>
> Would be nice if Maven created properties file with version info and build # in it. The client and broker could then log the version info at startup time as a sanity check when running tests. The version info could also be easily examined and added to bug reports to avoid confusion.
> As subversion is so good at reporting the version, the results of running the 'svnversion' command during a build can be used as an accurate build # reference that everyone can standardize on.
> Attached is a path to add this to the Maven build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira