[Hibernate] jacc-1_0-fr.jar source
Where did the jacc-1_0-fr.jar come from? --- 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] Is Proxol actually needed in the dist?
What I mean is that no advertised feature of Hibernate depends upon Proxool. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gavin King Sent: Tuesday, February 07, 2006 11:25 PM To: Scott M Stark; Hibernate development Subject: RE: [Hibernate] Is Proxol actually needed in the dist? Yep, some users are using it. But it is completely optional and non-default, so I'm not sure if that license requirement would be triggered. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Tuesday, February 07, 2006 11:20 PM To: Hibernate development Subject: [Hibernate] Is Proxol actually needed in the dist? Is the Proxool library actually used? It uses the old bsd style license that has a silly requirement regarding all advertising acknowledgment: http://proxool.sourceforge.net/licence.html 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the Proxool Project (http://proxool.sourceforge.net/)." --- 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=k&kid3432&bid#0486&dat1642 ___ 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=k&kid3432&bid#0486&dat1642 ___ 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] Is Proxol actually needed in the dist?
Yep, some users are using it. But it is completely optional and non-default, so I'm not sure if that license requirement would be triggered. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Tuesday, February 07, 2006 11:20 PM To: Hibernate development Subject: [Hibernate] Is Proxol actually needed in the dist? Is the Proxool library actually used? It uses the old bsd style license that has a silly requirement regarding all advertising acknowledgment: http://proxool.sourceforge.net/licence.html 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the Proxool Project (http://proxool.sourceforge.net/)." --- 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=k&kid3432&bid#0486&dat1642 ___ 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
[Hibernate] Is Proxol actually needed in the dist?
Is the Proxool library actually used? It uses the old bsd style license that has a silly requirement regarding all advertising acknowledgment: http://proxool.sourceforge.net/licence.html 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the Proxool Project (http://proxool.sourceforge.net/)." --- 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] default HEM key generator
Steve and Emmanuel are already working on this problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Tuesday, February 07, 2006 7:15 PM To: Hibernate development Subject: [Hibernate] default HEM key generator Can we have a default HEM key generator that will not force an insert when using FlushMode.NEVER? Like Table or Sequence or some other hibernate specific generator? I've been working through some example applications for my book and am finding that I have to modify pre-existing entity code to use a table generator because I want to take advantage of the FlushMode.NEVER semantics. Bill --- 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
[Hibernate] default HEM key generator
Can we have a default HEM key generator that will not force an insert when using FlushMode.NEVER? Like Table or Sequence or some other hibernate specific generator? I've been working through some example applications for my book and am finding that I have to modify pre-existing entity code to use a table generator because I want to take advantage of the FlushMode.NEVER semantics. Bill --- 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] Do antlr exception leak to users?
On Tue, 07 Feb 2006 20:55:52 +0100, Scott M Stark <[EMAIL PROTECTED]> wrote: fixing the antlr exception svuid won't help us if the client is using an older version, right ? It will if the serialVersionUID is set to the implicit value from the previous version. This can be done if the version is still serializable compatible. which it isn't afaik. the antlr version started to include more data in the exception over time. calling printStackTrace() on every exception sounds overkill for me...and will turn basic logging into something very verbose. Should be no different from now as logging generally includes the cause. well, for me that is showing the exception message in a dialog in the ui I would be very disappointed to have a full stack trace in the message output. I understand the issue, but don't find the suggested solutions any good ;( Would be nice to have an option to have any exposed remote exception do the serialization of the "cause". Would make it a non-issue where it actually matters. This can't be done without modifying the exception either via source or bytecode manipulation. And bytecode manipulation or simple modification of the exception in the jboss serialization/remoting layer have that option, correct ? -- -- 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] Do antlr exception leak to users?
> fixing the antlr exception svuid won't help us if the client > is using an older version, right ? > It will if the serialVersionUID is set to the implicit value from the previous version. This can be done if the version is still serializable compatible. > calling printStackTrace() on every exception sounds overkill > for me...and will turn basic logging into something very verbose. > Should be no different from now as logging generally includes the cause. > I understand the issue, but don't find the suggested > solutions any good ;( > > Would be nice to have an option to have any exposed remote > exception do the serialization of the "cause". > Would make it a non-issue where it actually matters. > This can't be done without modifying the exception either via source or bytecode manipulation. --- 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] Do antlr exception leak to users?
fixing the antlr exception svuid won't help us if the client is using
an older version, right ?
calling printStackTrace() on every exception sounds overkill for me...and
will turn basic logging into something very verbose.
I understand the issue, but don't find the suggested solutions any good ;(
Would be nice to have an option to have any exposed remote exception do
the serialization of the "cause".
Would make it a non-issue where it actually matters.
/max
The problem is the source of the cause not providing a stable api for
the exception, not the inclusion of the cause itself. The solution is to
fix the antlr exceptions to specify the serialVersionUID to avoid
trivial changes showing up as version incompatibilities.
You can always work around this by explicitly incorporating the cause
into the exception message string:
try
{
...
}
catch(Exception e)
{
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter();
pw.println("... cause:");
e.printStackTrace(pw);
pw.close();
String msg = sw.toString();
throw new Xception(msg);
}
-Original Message-
From: Max Andersen
Sent: Tuesday, February 07, 2006 10:34 AM
To: Scott M Stark; jboss-development@lists.sourceforge.net;
Hibernate development
Subject: Re: [Hibernate] Do antlr exception leak to users?
On Tue, 07 Feb 2006 19:24:38 +0100, Scott M Stark
<[EMAIL PROTECTED]>
wrote:
> I'm a little concerned that this will lead to unnecessary
coupling of
> client and server versions of antlr then. How often does an antlr
> exception as a cause show up in practise as an exception seen by an
> external client?
hmm..whenever a syntax error occur in a HQL/EJBQL statement.
But how else can we provide the cause of an exception ?
This is a pretty critical part of debugging hibernate applications.
Not just for antlr exceptions, but jdbc driver exceptions,
sqlexceptions and any other external "cause".
/max
--
--
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
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] Do antlr exception leak to users?
The problem is the source of the cause not providing a stable api for
the exception, not the inclusion of the cause itself. The solution is to
fix the antlr exceptions to specify the serialVersionUID to avoid
trivial changes showing up as version incompatibilities.
You can always work around this by explicitly incorporating the cause
into the exception message string:
try
{
...
}
catch(Exception e)
{
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter();
pw.println("... cause:");
e.printStackTrace(pw);
pw.close();
String msg = sw.toString();
throw new Xception(msg);
}
> -Original Message-
> From: Max Andersen
> Sent: Tuesday, February 07, 2006 10:34 AM
> To: Scott M Stark; jboss-development@lists.sourceforge.net;
> Hibernate development
> Subject: Re: [Hibernate] Do antlr exception leak to users?
>
> On Tue, 07 Feb 2006 19:24:38 +0100, Scott M Stark
> <[EMAIL PROTECTED]>
> wrote:
>
> > I'm a little concerned that this will lead to unnecessary
> coupling of
> > client and server versions of antlr then. How often does an antlr
> > exception as a cause show up in practise as an exception seen by an
> > external client?
>
> hmm..whenever a syntax error occur in a HQL/EJBQL statement.
>
> But how else can we provide the cause of an exception ?
> This is a pretty critical part of debugging hibernate applications.
> Not just for antlr exceptions, but jdbc driver exceptions,
> sqlexceptions and any other external "cause".
>
> /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&kid3432&bid#0486&dat1642
___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Do antlr exception leak to users?
On Tue, 07 Feb 2006 19:24:38 +0100, Scott M Stark <[EMAIL PROTECTED]> wrote: I'm a little concerned that this will lead to unnecessary coupling of client and server versions of antlr then. How often does an antlr exception as a cause show up in practise as an exception seen by an external client? hmm..whenever a syntax error occur in a HQL/EJBQL statement. But how else can we provide the cause of an exception ? This is a pretty critical part of debugging hibernate applications. Not just for antlr exceptions, but jdbc driver exceptions, sqlexceptions and any other external "cause". /max -Original Message- From: Max Andersen Sent: Monday, February 06, 2006 11:53 AM To: Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: Re: [Hibernate] Do antlr exception leak to users? On Mon, 06 Feb 2006 20:49:08 +0100, Scott M Stark <[EMAIL PROTECTED]> wrote: > I'm seeing some incompatible serial version uid changes in the latest > antlr, but I don't know if antlr exceptions every leak to users > outside of the vm such that this is an issue. Do the ql grammar > exception get exposed or are they always converted to a hibernate exception? it is always converted, but of course it can be inside as a cause exception. /max -- -- 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] Do antlr exception leak to users?
I'm a little concerned that this will lead to unnecessary coupling of client and server versions of antlr then. How often does an antlr exception as a cause show up in practise as an exception seen by an external client? > -Original Message- > From: Max Andersen > Sent: Monday, February 06, 2006 11:53 AM > To: Scott M Stark; jboss-development@lists.sourceforge.net; > Hibernate development > Subject: Re: [Hibernate] Do antlr exception leak to users? > > On Mon, 06 Feb 2006 20:49:08 +0100, Scott M Stark > <[EMAIL PROTECTED]> > wrote: > > > I'm seeing some incompatible serial version uid changes in > the latest > > antlr, but I don't know if antlr exceptions every leak to users > > outside of the vm such that this is an issue. Do the ql grammar > > exception get exposed or are they always converted to a > hibernate exception? > > it is always converted, but of course it can be inside as a > cause exception. > > /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&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
[Hibernate] Re: its done
On Tue, 07 Feb 2006 11:35:58 +0100, Thomas Heute <[EMAIL PROTECTED]> wrote: Tried and fixed the templates. Thanks ! care to share if/what issues there were ? I don't see the commits ? /max On Monday 06 February 2006 10.09, Max Rydahl Andersen wrote: It's done - tools head now has freemarker instead of velocity as its template engine. All unittests passes, still would be great to get verification from seam'ers that the output still runs ok. -- -- 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
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
