RE: [Hibernate] Release naming conventions
I added a Practices and Jar Manifest Headers section to the JBossProductVersioning page to discuss issues such as how nightly builds could be versioned. The headers section still needs to be completed. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: Tuesday, February 07, 2006 10:22 AM > To: Max Andersen; Christian Bauer; development Hibernate; > [EMAIL PROTECTED] > Cc: jboss-development@lists.sourceforge.net > Subject: RE: [Hibernate] Release naming conventions > > Any place the version is actually used. This is the manifest > headers (these should also be spelled out and standardized > including the osgi conventions for projects that need to > comply with these headers), the repository > component-info.xml, and the project build files. Really only > the project build file should be where a project makes > version changes and this should just propagated to artifacts > based on the build tools. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Release naming conventions
Any place the version is actually used. This is the manifest headers (these should also be spelled out and standardized including the osgi conventions for projects that need to comply with these headers), the repository component-info.xml, and the project build files. Really only the project build file should be where a project makes version changes and this should just propagated to artifacts based on the build tools. > -Original Message- > From: Max Andersen > Sent: Tuesday, February 07, 2006 10:14 AM > To: Scott M Stark; Christian Bauer; development Hibernate; > [EMAIL PROTECTED] > Subject: Re: [Hibernate] Release naming conventions > > > so where do you want the name applied ? > > in the eclipse plugins it make sense for the jar's since that > is the part being used to identify it + the > plugin.xml/MANIFEST.MF osgi version part. > > /max > > > This has nothing to do with the actual jar names. The > version in the > > jar name is a poor convention as it propagates the version to users > > unnecessarily, and is not verifiable via a signed manifest. > The jars > > checked into the repository should not have any explicit version > > information in the name. I don't care what naming > conventions are used > > by projects elsewhere. > > > >> -Original Message- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] On > Behalf Of Max > >> Rydahl Andersen > >> Sent: Tuesday, February 07, 2006 10:01 AM > >> To: Christian Bauer; development Hibernate; > >> [EMAIL PROTECTED] > >> Subject: Re: [Hibernate] Release naming conventions > >> > >> >> > >> >> I'm not a big fan of all minor releases needing to append > >> '.ga' (i.e. > >> >> 3.1.3.ga.jar). I really wish there was a way to define > ordering > >> >> amongst "qualifiers". > >> > > >> > AFAIK these conventions are for package names and not > necessarily > >> > library names? > >> > >> it's the version branded into the application - meaning what goes > >> into MANIFEST.MF and distribution name; for me it would > make sense to > >> have that on the jar file too... > >> > >> And yes, would be great with an "ordering" that said 3.1.3 > is "newer" > >> than 3.1.3.alpha, 3.1.3.beta..but what is 3.1.3.2 then ? > >> > >> p.s. i'm planning on following this in the eclipse plugins > too since > >> it actually is very usefull there to have the update manager > >> functionallity work together with alpha/beta/etc. > >> > >> /max > >> > >> > > >> > --- > >> > This SF.net email is sponsored by: Splunk Inc. Do you grep > >> through log > >> > files for problems? Stop! Download the new AJAX search > >> engine that > >> > makes searching your log files as easy as surfing the web. > >> DOWNLOAD > >> > SPLUNK! > >> > > >> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121 > >> 6 > >> > 42 ___ > >> > hibernate-devel mailing list > >> > hibernate-devel@lists.sourceforge.net > >> > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > >> > >> > >> > >> -- > >> -- > >> Max Rydahl Andersen > >> callto://max.rydahl.andersen > >> > >> Hibernate > >> [EMAIL PROTECTED] > >> http://hibernate.org > >> > >> JBoss Inc > >> [EMAIL PROTECTED] > >> > >> > >> --- > >> This SF.net email is sponsored by: Splunk Inc. Do you grep through > >> log files for problems? Stop! Download the new AJAX > search engine > >> that makes searching your log files as easy as surfing the web. > >> DOWNLOAD SPLUNK! > >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&; > >> dat=121642 > >> ___ > >> hibernate-devel mailing list > >> hibernate-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/hibernate-devel > >> > > > > -- > -- > Max Rydahl Andersen > callto://max.rydahl.andersen > > Hibernate > [EMAIL PROTECTED] > http://hibernate.org > > JBoss Inc > [EMAIL PROTECTED] > --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Release naming conventions
so where do you want the name applied ? in the eclipse plugins it make sense for the jar's since that is the part being used to identify it + the plugin.xml/MANIFEST.MF osgi version part. /max This has nothing to do with the actual jar names. The version in the jar name is a poor convention as it propagates the version to users unnecessarily, and is not verifiable via a signed manifest. The jars checked into the repository should not have any explicit version information in the name. I don't care what naming conventions are used by projects elsewhere. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Tuesday, February 07, 2006 10:01 AM To: Christian Bauer; development Hibernate; [EMAIL PROTECTED] Subject: Re: [Hibernate] Release naming conventions >> >> I'm not a big fan of all minor releases needing to append '.ga' (i.e. >> 3.1.3.ga.jar). I really wish there was a way to define ordering >> amongst "qualifiers". > > AFAIK these conventions are for package names and not necessarily > library names? it's the version branded into the application - meaning what goes into MANIFEST.MF and distribution name; for me it would make sense to have that on the jar file too... And yes, would be great with an "ordering" that said 3.1.3 is "newer" than 3.1.3.alpha, 3.1.3.beta..but what is 3.1.3.2 then ? p.s. i'm planning on following this in the eclipse plugins too since it actually is very usefull there to have the update manager functionallity work together with alpha/beta/etc. /max > > --- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that > makes searching your log files as easy as surfing the web. DOWNLOAD > SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=1216 > 42 ___ > hibernate-devel mailing list > hibernate-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&; dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Release naming conventions
Yes, I plan to start using these conventions starting with 3.2. I'm not a big fan of all minor releases needing to append '.ga' (i.e. 3.1.3.ga.jar). I really wish there was a way to define ordering amongst "qualifiers". -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Bauer Sent: Tuesday, February 07, 2006 11:44 AM To: development Hibernate; [EMAIL PROTECTED] Subject: [Hibernate] Release naming conventions JBoss finalized some naming conventions for release packages, and both Hibernate and NHibernate packages should follow these conventions. The benefit of this is stability and the ability to compare packages. As far as I can see, nothing much changes for Hibernate except that some of the confusion in the past around alpha/ beta/rc releases is avoided. http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Release naming conventions
This has nothing to do with the actual jar names. The version in the jar name is a poor convention as it propagates the version to users unnecessarily, and is not verifiable via a signed manifest. The jars checked into the repository should not have any explicit version information in the name. I don't care what naming conventions are used by projects elsewhere. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Max Rydahl Andersen > Sent: Tuesday, February 07, 2006 10:01 AM > To: Christian Bauer; development Hibernate; > [EMAIL PROTECTED] > Subject: Re: [Hibernate] Release naming conventions > > >> > >> I'm not a big fan of all minor releases needing to append > '.ga' (i.e. > >> 3.1.3.ga.jar). I really wish there was a way to define ordering > >> amongst "qualifiers". > > > > AFAIK these conventions are for package names and not necessarily > > library names? > > it's the version branded into the application - meaning what > goes into MANIFEST.MF and distribution name; for me it would > make sense to have that on the jar file too... > > And yes, would be great with an "ordering" that said 3.1.3 is > "newer" than 3.1.3.alpha, 3.1.3.beta..but what is 3.1.3.2 then ? > > p.s. i'm planning on following this in the eclipse plugins > too since it actually is very usefull there to have the > update manager functionallity work together with alpha/beta/etc. > > /max > > > > > --- > > This SF.net email is sponsored by: Splunk Inc. Do you grep > through log > > files for problems? Stop! Download the new AJAX search > engine that > > makes searching your log files as easy as surfing the web. > DOWNLOAD > > SPLUNK! > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=1216 > > 42 ___ > > hibernate-devel mailing list > > hibernate-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > > > > -- > -- > Max Rydahl Andersen > callto://max.rydahl.andersen > > Hibernate > [EMAIL PROTECTED] > http://hibernate.org > > JBoss Inc > [EMAIL PROTECTED] > > > --- > This SF.net email is sponsored by: Splunk Inc. Do you grep > through log files for problems? Stop! Download the new AJAX > search engine that makes searching your log files as easy as > surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&; > dat=121642 > ___ > hibernate-devel mailing list > hibernate-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Release naming conventions
I'm not a big fan of all minor releases needing to append '.ga' (i.e. 3.1.3.ga.jar). I really wish there was a way to define ordering amongst "qualifiers". AFAIK these conventions are for package names and not necessarily library names? it's the version branded into the application - meaning what goes into MANIFEST.MF and distribution name; for me it would make sense to have that on the jar file too... And yes, would be great with an "ordering" that said 3.1.3 is "newer" than 3.1.3.alpha, 3.1.3.beta..but what is 3.1.3.2 then ? p.s. i'm planning on following this in the eclipse plugins too since it actually is very usefull there to have the update manager functionallity work together with alpha/beta/etc. /max --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Release naming conventions
On Feb 7, 2006, at 6:51 PM, Steve Ebersole wrote: Yes, I plan to start using these conventions starting with 3.2. I'm not a big fan of all minor releases needing to append '.ga' (i.e. 3.1.3.ga.jar). I really wish there was a way to define ordering amongst "qualifiers". AFAIK these conventions are for package names and not necessarily library names? --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Release naming conventions
JBoss finalized some naming conventions for release packages, and both Hibernate and NHibernate packages should follow these conventions. The benefit of this is stability and the ability to compare packages. As far as I can see, nothing much changes for Hibernate except that some of the confusion in the past around alpha/ beta/rc releases is avoided. http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
