On Fri, Feb 2, 2018 at 4:22 PM, Guillaume Smet
wrote:
> On Fri, Feb 2, 2018 at 4:00 PM, Steve Ebersole
> wrote:
>
>> See you cheated though. You "just happened" to use a project that has a
>> dedicated groupId. If we used a dedicated groupId for ORM
>> (`org.hibernate.orm` e.g.) then its not a
Merged to production. Steve, you can add 5.3.0.Beta2 the usual way,
whenever you're ready.
On Fri, 2 Feb 2018 at 16:44 Guillaume Smet wrote:
> On Fri, Feb 2, 2018 at 4:27 PM, Steve Ebersole
> wrote:
>
>> Pretty sure you are still more impressed with it than I am with Nexus ;)
>>
>
> That's the
On Fri, Feb 2, 2018 at 4:27 PM, Steve Ebersole wrote:
> Pretty sure you are still more impressed with it than I am with Nexus ;)
>
That's the message I wanted to convey: we don't use the Nexus UI anymore
with the changes made by Yoann.
And that doesn't prevent you from using Bintray for publish
>
> Yeah, sorry, I'm not impressed.
>
Pretty sure you are still more impressed with it than I am with Nexus ;)
Bintray is in fact in the middle of a UI/UX rewrite, so...
>>
>> And selecting the "main" artifact used in the drop down is one of those
>> items
>>
>
> OK, let's hope it's going to be
On Fri, Feb 2, 2018 at 4:00 PM, Steve Ebersole wrote:
> See you cheated though. You "just happened" to use a project that has a
> dedicated groupId. If we used a dedicated groupId for ORM
> (`org.hibernate.orm` e.g.) then its not a big deal either way.
>
I didn't cheat. I gave a random link. Y
> Should I make those changes on top of yours?
I will do it and merge.
Thanks all for the feedback.
On Fri, 2 Feb 2018 at 16:23 Guillaume Smet wrote:
> On Fri, Feb 2, 2018 at 4:00 PM, Steve Ebersole
> wrote:
>
>> See you cheated though. You "just happened" to use a project that has a
>> dedi
There is one thing that should change though - that initial Bintray link
really ought to go to the Bintray hibernate-orm package. We already have
the version-specific Bintray links below.
Thanks for working on this. Should I make those changes on top of yours?
On Fri, Feb 2, 2018 at 8:06 AM Yoa
So... It's a yes for the current state of staging (with Bintray links)?
On Fri, 2 Feb 2018 at 16:07 Steve Ebersole wrote:
> On Fri, Feb 2, 2018 at 8:36 AM Guillaume Smet
> wrote:
>
>> On Fri, Feb 2, 2018 at 3:06 PM, Yoann Rodiere
>> wrote:
>>
>>> @Guillaume, all: I also changed the links of ot
On Fri, Feb 2, 2018 at 8:36 AM Guillaume Smet
wrote:
> On Fri, Feb 2, 2018 at 3:06 PM, Yoann Rodiere wrote:
>
>> @Guillaume, all: I also changed the links of other projects to point to
>> Maven Central instead of the JBoss Nexus, because the JBoss Nexus requires
>> authentication. And, well, als
On Fri, Feb 2, 2018 at 3:06 PM, Yoann Rodiere wrote:
> @Guillaume, all: I also changed the links of other projects to point to
> Maven Central instead of the JBoss Nexus, because the JBoss Nexus requires
> authentication. And, well, also because... Nexus.
>
Frankly, I find the new Maven Central
> IIUC, a "switch based on the project" is not going to be enough. For the
orm project we'd also then need to know whether a series is "5.3 or later":
It's even worse, as 5.3.0.Beta1 is on the JBoss Nexus but Beta2 is on
Bintray,,,
Anyway, I managed to get something. It's on staging, please give
On Fri, Feb 2, 2018 at 2:19 PM, Steve Ebersole wrote:
> I'm not sure how to do that `series >= 5.3` piece. I guess I'll look at
> what you do on staging
What I have done so far to manage this sort of things is to add metadata to
the series files.
--
Guillaume
Couldn't we just have "All Hibernate libraries are available in Maven Central" ?
I'd like to keep things simple, both for us and for users.
On 2 February 2018 at 13:19, Steve Ebersole wrote:
> IIUC, a "switch based on the project" is not going to be enough. For the
> orm project we'd also then
IIUC, a "switch based on the project" is not going to be enough. For the
orm project we'd also then need to know whether a series is "5.3 or later":
if ( page.project == "orm" && series >= 5.3 ) {
// bintray
...
}
else {
// as before
}
I'm not sure how to do that `series >= 5.3` piece. I guess
> Is this going to be as simple as adding a
new layout (`project-releases-series-bintray.html.haml`?) and using that as
the layout for http://hibernate.org/orm/releases/5.3/ ?
It should be, yes. Though a better option might be to introduce switches
based on the project, especially if you only wan
Like I said, that is exactly what I end up doing now. When I do a release
I write the blog directly in the in.relation.to repo via the GitHub UI
editor. Same for the release descriptor in hibernate.org. SO I am
familiar with that approach.
On Fri, Apr 22, 2016 at 10:34 AM Sanne Grinovero
wrot
Hi Steve, yes I understand you just want to write some content.
But then why not give the approach I just mentioned a try?
You can totally skip the staging branch and docker stuff.
I will *personally* keep using staging when I'm not sure about formatting
and/or am working on something which I wan
Right, this is actually exactly what I end up doing for any dealing with
hibernate.org or in.relation.to...
Keep in mind I just want to author come content :)
Personally I find the whole process just gets in the way. Generally right
out of the chute we have to deal with forced pushes on staging
There's a middle-ground strategy which might be cool to try.
Go here:
- https://github.com/hibernate/hibernate.org/edit/production/orm/roadmap.adoc
edit the doc within the browser, confirm the changes with a brief
commit message and CI should pick it up, then publish within 5
minutes.
I just di
Hi Steve,
what problems are you having with hibernate.org?
I agree with Gunnar that we should try to stick with one look & feel if
possible.
On Thu, Apr 21, 2016 at 9:00 PM, Steve Ebersole wrote:
> Because I find it incredibly easier to work with GitHub wiki as opposed to
> hibernate.org for aut
Because I find it incredibly easier to work with GitHub wiki as opposed to
hibernate.org for authoring.
On Thu, Apr 21, 2016, 12:42 PM Gunnar Morling wrote:
> Hey,
>
> What's the reason for maintaining the roadmap in the wiki rather than
> hibernate.org itself?
>
> I hoped we'd centralize this k
Hey,
What's the reason for maintaining the roadmap in the wiki rather than
hibernate.org itself?
I hoped we'd centralize this kind of information on hibernate.org; Looks a
tad more professional to have everything with the same look & field rather
than pointing to other resources as the wiki... Al
Chris just point out that the roadmap target URL is part of the site
config. So I can just update that for ORM. Disregard :)
On Thu, Apr 21, 2016 at 12:36 PM Steve Ebersole wrote:
> I have started maintaining[1] the ORM Roadmap external to hibernate.org
> itself. I'd like to adjust the link
Hi,
On Sat, Aug 22, 2015 at 02:22:01PM +, Steve Ebersole wrote:
> I went ahead for now with your first (1) option. So for ORM, the left-hand
> "Documentation" link now becomes 3: "Documentation (5.0)", "Documentation
> (4.3)", "Documentation (4.2)".
Right, definitely the easiest.
> Not idea
I went ahead for now with your first (1) option. So for ORM, the left-hand
"Documentation" link now becomes 3: "Documentation (5.0)", "Documentation
(4.3)", "Documentation (4.2)".
Not ideal long term, but as you said, the easiest solution for now and it
works. But it got me thinking that a lot o
Worked great for me locally from upstream!
On Thu, Aug 20, 2015 at 10:57 AM Steve Ebersole wrote:
> Hardy, this is awesome! Thanks for getting this pushed upstream. I am
> about to work with this upstream today :)
>
>
>
> On Thu, Aug 20, 2015 at 8:08 AM Hardy Ferentschik
> wrote:
>
>> Hi all
Hardy, this is awesome! Thanks for getting this pushed upstream. I am
about to work with this upstream today :)
On Thu, Aug 20, 2015 at 8:08 AM Hardy Ferentschik
wrote:
> Hi all,
>
> I just pushed some changes to the hibernate.org site. The changes allow
> you to run
> the hibernate.org Awes
Hi,
I am not a great expert on the templating side either, but I can tell you how it
is put together atm.
The left hand menu items for the different projects (About, Downloads,
Documentation, etc)
are actually generated from the site config.
If you look into _config/site.yml, you see that each
On Fri, 26 Feb 2010 21:56:07 -0300, Steve Ebersole
wrote:
> Another thought is to handle metamodel generator as a module in core. I
> think we need to make that decision based on whether it makes sense
> rather than what looks good on the website or what is 'easy' in the
> build tool (as
Another thought is to handle metamodel generator as a module in core. I think
we need to make that decision based on whether it makes sense rather than what
looks good on the website or what is 'easy' in the build tool (as long as it
possible of course).
Does it rely on core at all?
-- Se
I updated the subproject spaces for Validator, Search and Shards (for the
latter I just copied
what we had, we might add somewhere a note that there is currently no
active development on this
project)
For the links "Community->Chat" and "Community->Mailinglist" I am
currently linking to the
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 movin
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 wi
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 g
On Mon, 20 Apr 2009 13:43:35 +0200, Sanne Grinovero
wrote:
did you get any information about what's going on on the forums?
"caught us doing a little maintenance" is a bit silly after 3 days,
my expectations are rising to expect a very cool new website?
Nope. No new information. :(
--Hardy
Hello Hardy,
did you get any information about what's going on on the forums?
"caught us doing a little maintenance" is a bit silly after 3 days,
my expectations are rising to expect a very cool new website?
Sanne
2009/4/18 Hardy Ferentschik :
> Hi,
>
> Are there any news regarding hibernate.org?
36 matches
Mail list logo
