|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
maven-build-number buggyIt seems to me that the API only supports execution of the 'svn'
command and it's various parameters and switches. The problem is that in subversion, a different executable command is used to retrieve a proper detailed version number of the local copy, that being 'svnversion'. Using this command, I can tell if I have a mixed version, a modified version, etc. For example: [jim@localhost sb_rc1 993]$ svn info | grep Revision Revision: 51159 [jim@localhost sb_rc1 994]$ svnversion 51159M [jim@localhost sb_rc1 994]$ Guess what? 'svn info' is lying to me here. My local copy is modified from the original 51159 which is why 'svnversion' reports the version number with an M attached to it. What if I'm experimenting with a branch that contains a mixed version? 'svnversion' can handle this. 'svn info' cannot. Worse, as shown above, it will provide misleading and potentially disastrous information if, for example, I'm basing a release or some other important suppositions off of the bad info. Jim C. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: maven-build-number buggyHi Jim,
In fact, as the main role of buildnumber plugin is to retrieve the current version of a project, I guess using svnversion would be a better choice than using svn info. Moreover, svnversion has the advantage to not thow an exception when the projet isn't versionned, it just displayed "exported" and it seems to me it's also a better choice. So, what you say is very interesting. I think you should really file it an issue for buildnumber plugin. Cheers. 2009/11/4 Jim Collings <jlistnews@...> > It seems to me that the API only supports execution of the 'svn' > command and it's various parameters and switches. The problem is that > in subversion, a different executable command is used to retrieve a > proper detailed version number of the local copy, that being > 'svnversion'. Using this command, I can tell if I have a mixed > version, a modified version, etc. For example: > > [jim@localhost sb_rc1 993]$ svn info | grep Revision > Revision: 51159 > [jim@localhost sb_rc1 994]$ svnversion > 51159M > [jim@localhost sb_rc1 994]$ > > Guess what? 'svn info' is lying to me here. My local copy is modified > from the original 51159 which is why 'svnversion' reports the version > number with an M attached to it. What if I'm experimenting with a > branch that contains a mixed version? 'svnversion' can handle this. > 'svn info' cannot. Worse, as shown above, it will provide misleading > and potentially disastrous information if, for example, I'm basing a > release or some other important suppositions off of the bad info. > > > Jim C. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! |
|
|
Re: maven-build-number buggyOK, I'll give that a whirl. :-)
> Hi Jim, > In fact, as the main role of buildnumber plugin is to retrieve the current > version of a project, I guess using svnversion would be a better choice than > using svn info. Moreover, svnversion has the advantage to not thow an > exception when the projet isn't versionned, it just displayed "exported" and > it seems to me it's also a better choice. > > So, what you say is very interesting. I think you should really file it an > issue for buildnumber plugin. > > Cheers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: maven-build-number buggyCan't find where bugs are reported for maven-buildnumber-plugin. Clue?
Jim C. > Hi Jim, > In fact, as the main role of buildnumber plugin is to retrieve the current > version of a project, I guess using svnversion would be a better choice than > using svn info. Moreover, svnversion has the advantage to not thow an > exception when the projet isn't versionned, it just displayed "exported" and > it seems to me it's also a better choice. > > So, what you say is very interesting. I think you should really file it an > issue for buildnumber plugin. > > Cheers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: maven-build-number buggyhttp://jira.codehaus.org/browse/MOJO
Cheers 2009/11/5 Jim Collings <jlistnews@...> > Can't find where bugs are reported for maven-buildnumber-plugin. Clue? > > Jim C. > > > Hi Jim, > > In fact, as the main role of buildnumber plugin is to retrieve the > current > > version of a project, I guess using svnversion would be a better choice > than > > using svn info. Moreover, svnversion has the advantage to not thow an > > exception when the projet isn't versionned, it just displayed "exported" > and > > it seems to me it's also a better choice. > > > > So, what you say is very interesting. I think you should really file it > an > > issue for buildnumber plugin. > > > > Cheers. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! |
|
|
Re: maven-build-number buggyThanks. :-)
OK, I have an account now. Which project is it? I don't see any references to maven-build-number-plugin. Clue? > http://jira.codehaus.org/browse/MOJO > > Cheers > > 2009/11/5 Jim Collings <jlistnews@...> > >> Can't find where bugs are reported for maven-buildnumber-plugin. Clue? >> >> Jim C. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: maven-build-number buggyIt is a component of the MOJO project. So, create a new issue on the MOJO
project and select the right component, ie. buildnumber. Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Nov 5, 2009 at 4:41 PM, Jim Collings <jlistnews@...> wrote: > Thanks. :-) > OK, I have an account now. Which project is it? I don't see any > references to maven-build-number-plugin. > Clue? > > > http://jira.codehaus.org/browse/MOJO > > > > Cheers > > > > 2009/11/5 Jim Collings <jlistnews@...> > > > >> Can't find where bugs are reported for maven-buildnumber-plugin. Clue? > >> > >> Jim C. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > |
|
|
Re: maven-build-number buggyI figured it out. It's Mojo Buildnumber.
On Thu, Nov 5, 2009 at 10:41 AM, Jim Collings <jlistnews@...> wrote: > Thanks. :-) > OK, I have an account now. Which project is it? I don't see any > references to maven-build-number-plugin. > Clue? > >> http://jira.codehaus.org/browse/MOJO >> >> Cheers >> >> 2009/11/5 Jim Collings <jlistnews@...> >> >>> Can't find where bugs are reported for maven-buildnumber-plugin. Clue? >>> >>> Jim C. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| Free embeddable forum powered by Nabble | Forum Help |