Re: [hibernate-dev] Hibernate.org
I think content wise the current sub project approach will work. Looking at search.hibernate.org and validator.hibernate.org one can see that there is not so much content for this content pages. The bulk of information is really in the wiki which is a different thing (Clearspace). Btw, what's going to happen with the domains search.hibernate.org and validator.hibernate.org? Will they forward to the corresponding sub project page on JBoss.org? Will EM and Annotations still be listed as sub projects though. I guess from a current point of view we could combine them into Core. Not sure whether we have to consider long time users though who might be looking for these projects. We also have to consider the new Static Metamodel Generator. Currently it does not have its own project page. Will we just add it to Core or will it be its own standalone sub project? Maybe we should even consider moving the actual source code into a maven module. If I remember right the main issue stopping us from doing so were build problems, right? Shards I know nothing about. I am not even sure who does. Seems the best we can do there is to move the current content from shards.hibernate.org. --Hardy On Mon, 22 Feb 2010 21:53:37 -0300, Steve Ebersole wrote: > After months of sitting in limbo it looks like there may finally be > movement on getting hibernate.org content moved over to the > magnolia/clearspace setup. > > We need to figure out what all still needs to be done in terms of > content. For core (+ annotations/em) I have a good idea of the work > still to do. But in terms of search, validator, shards and tools > (nhibernate?) I have no idea. > > This will not happen until next week at the earliest as I have a meet up > scheduled with the JBoss design team here in Austin to go over LnF, > navigation, etc later this week. > > Like one specific thing I know we have to iron out is navigation and > side bar content for the various subprojects. Will the various > subprojects "be under" hibernate? The infrastructure is really built so > that all projects are at the same level. I think it comes down to how > much content (pages) we see for each sub project and how y'all want the > nav and menus to work. If a unified set of nav and menus along with a > minimal set of content pages is acceptable then its probably doable to > just create sub content pages under the main set of hibernate pages. If > y'all want something more elaborate or separate nav/menus than we are > going to have to split these up I think (I'll verify to make sure this > is still the case). > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] 3.5.0-CR-2 set up in JIRA
Steve, I'm done with the Infinispan 2LC fix for this. I believe Brian might be already but you might wanna double check with him. Cheers, On Mon, 22 Feb 2010 00:14:33 +0100, Brian Stansberry wrote: > Galder found a flaw in the fix for > http://opensource.atlassian.com/projects/hibernate/browse/HHH-3817 that > affects second level caching with both JBoss Cache and Infinispan. I'm > working on a fix that I plan to finish by the 23rd at latest (goal is > tomorrow.) > > On 02/16/2010 03:56 PM, Steve Ebersole wrote: >> Just wanted to point out to everyone that 3.5.0-CR-2 has been set up in >> JIRA ( >> http://opensource.atlassian.com/projects/hibernate/browse/HHH/fixforversion/11011 >> ) and tentatively scheduled for Feb 24 2010. I say tentatively because >> I am not sure I will wait that long; lets see how things go. >> >> In the meantime, I moved all unresolved issues not in progress to 3.5.x. >>Please take the time asap to mark any issues you want in 3.5.0-CR-2. >> I completely expect this to be the last CR before 3.5.0 >> >> Thanks >> > > -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate.org
On 02/23/2010 08:43 AM, Hardy Ferentschik wrote: > I think content wise the current sub project approach will work. Looking > at search.hibernate.org and validator.hibernate.org one can see that > there is > not so much content for this content pages. The bulk of information is > really in > the wiki which is a different thing (Clearspace). Btw, what's going to > happen > with the domains search.hibernate.org and validator.hibernate.org? Will > they forward > to the corresponding sub project page on JBoss.org? Well the "sub domains" are apprently not really sub domains at all. They are simple redirects. So for example, http://core.hibernate.org simply directs the browser to https://www.hibernate.org/344.html ; https://annotations.hibernate.org/ directs to https://www.hibernate.org/397.html ; etc. The point though is that these "sub domains" really just identify single information pages, one per "sub domain". And yes redirects from the old urls to the new targets will all be handled. This was the gist of my question below. Is this what we want to keep? For the sub-projects, is a single sub-page enough? Again this is no different than what we have today. Here is an example of incorporating sub-projects in this infrastructure: http://jboss.org/gatein http://jboss.org/gatein/portletcontainer.html The fact that the banner goes away between the 2 is coincidental. We can set it up either way. And we can have each sub-project define its own nav items (overview/pages, download, community, etc). The real question becomes when or whether we want these sub-projects accessible from the main site navigation. > Will EM and Annotations still be listed as sub projects though. I guess > from a current > point of view we could combine them into Core. Not sure whether we have > to consider > long time users though who might be looking for these projects. I planned on not having them as separate sub-projects. The main page has an announcement about them (and envers) being combined into the main project. > We also have to consider the new Static Metamodel Generator. Currently > it does not have its > own project page. Will we just add it to Core or will it be its own > standalone > sub project? > Maybe we should even consider moving the actual source code into a maven > module. If I remember > right the main issue stopping us from doing so were build problems, right? No idea. > Shards I know nothing about. I am not even sure who does. Seems the best > we can do there > is to move the current content from shards.hibernate.org. Yep, which will be the default for anything I don't hear about. > --Hardy > > On Mon, 22 Feb 2010 21:53:37 -0300, Steve Ebersole > wrote: > >> After months of sitting in limbo it looks like there may finally be >> movement on getting hibernate.org content moved over to the >> magnolia/clearspace setup. >> >> We need to figure out what all still needs to be done in terms of >> content. For core (+ annotations/em) I have a good idea of the work >> still to do. But in terms of search, validator, shards and tools >> (nhibernate?) I have no idea. >> >> This will not happen until next week at the earliest as I have a meet up >> scheduled with the JBoss design team here in Austin to go over LnF, >> navigation, etc later this week. >> >> Like one specific thing I know we have to iron out is navigation and >> side bar content for the various subprojects. Will the various >> subprojects "be under" hibernate? The infrastructure is really built so >> that all projects are at the same level. I think it comes down to how >> much content (pages) we see for each sub project and how y'all want the >> nav and menus to work. If a unified set of nav and menus along with a >> minimal set of content pages is acceptable then its probably doable to >> just create sub content pages under the main set of hibernate pages. If >> y'all want something more elaborate or separate nav/menus than we are >> going to have to split these up I think (I'll verify to make sure this >> is still the case). >> > -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate.org
On Tue, 23 Feb 2010 14:07:55 -0300, Steve Ebersole wrote: >> We also have to consider the new Static Metamodel Generator. Currently >> it does not have its >> own project page. Will we just add it to Core or will it be its own >> standalone >> sub project? >> Maybe we should even consider moving the actual source code into a maven >> module. If I remember >> right the main issue stopping us from doing so were build problems, >> right? > No idea. I guess there is also the issue of license. Currently the annotation processor uses the Apache License (version 2). Partly out of historic reasons, since in the beginnings it was a prototype for Sun and partly out of the idea that using APL would make it easier for IDE/Tools to make use of it. So in order to integrate it into Core we would have to change that. Somehow having a separate project seems wrong given the very specific problem the tool solves. Thoughts? --Hardy ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
