Hi,
We could provide a way to download the hibernate jar file on first usage
(like it was done for JUnit iirc) and like I keep on promising I'll do for
WildFly ;)
I can ping some of the hibernate team if you need it.
Cheers,
Emmanuel
--
Emmanuel Hugonnet
http://www.ehsavoie.com
http://twit
I see, discoverability is a good point.
The DTDs don't seem a blocker to me. It's doable to create a clean room
implementation for those DTDs based on the existing body of Hibernate
configuration XML files.
We are also in talks with them to see if they could relicense the DTDs.
The big problem i
Hi,
On Wed, May 31, 2017 at 10:38 AM Emilian Bold
wrote:
> There is an older thread about the Plugin Portal which will be handled
> outside Apache.
>
> You could revive that thread or start another one.
>
Sorry, I wasn't intending that question to be entirely devoid of the
context of this threa
There is an older thread about the Plugin Portal which will be handled outside
Apache.
You could revive that thread or start another one.
--emi
Pe 31 mai 2017, la 12:17, Neil C Smith a scris:
> Hi,
>
> On Wed, May 31, 2017 at 10:01 AM Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> w
This sounds good. If it reaches the Apache repo it will be under the Apache
license and forked as such. Then we have the option of re-adding the modules in
the future.
My concerns was that the modules are not donated and remain under the old
licenses which might complicate future inclusion.
--
Hi,
On Wed, May 31, 2017 at 10:01 AM Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> And then, whoever cares about that code, i.e., about those
> features, which could be me personally or anyone else personally, would put
> that code in GitHub and work on it there with anyone else
The owner will be whoever decides to do this -- and it will definitely not
be ASF and definitely not Oracle.
I.e., I would propose that we remove all Hibernate-related code, i.e., the
tooling, wizards, whatevers, as soon as we have the code in the Apache
repository. And then, whoever cares about t
If it's not just about the DTDs but the JAR too the we should move it outside
the repo.
Still, relicensing the code would help.
How will be the owner of the Hibernate related code: the ASF or Oracle?
--emi
Pe 31 mai 2017, la 11:18, Geertjan Wielenga
a scris:
> Not only do we have these thre
Not only do we have these three DTDs that are licensed LGPL, we also have
the LGPL Hibernate 4.3.1 JAR in the Java cluster.
Sooner or later we're going to have to deal with that. I'd be in favor of
removing Hibernate completely from Apache NetBeans and making it available
as some kind of separate
On Tue, May 30, 2017 at 10:05 AM, Geertjan Wielenga
wrote:
> ...4. We could ask Apache for a legal decision on whether these DTDs could be
> included, since we're not distributing them -- we're only using them to
> build NetBeans
I think the (P)PMC can make that decision, best is to create a
nonical URL instead of including the resources in the JAR? Of course,
> > this will require network access...
> >
> >
> >
> > --emi
> >
> > On Tue, May 30, 2017 at 9:26 AM, Geertjan Wielenga <
> > geertjan.wiele...@googlemail.com> wrote:
> >
>
instead of including the resources in the JAR? Of course,
> this will require network access...
>
>
>
> --emi
>
> On Tue, May 30, 2017 at 9:26 AM, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
>> Hi all,
>>
>> Does anyone have insi
including the resources in the JAR? Of course,
this will require network access...
--emi
On Tue, May 30, 2017 at 9:26 AM, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> Hi all,
>
> Does anyone have insight into the status of Hibernate in Apache.
>
> The reaso
Hi all,
Does anyone have insight into the status of Hibernate in Apache.
The reason I am asking this is because Oracle is unable to donate these
files to Apache, since these files do not belong to Oracle:
hibernate/src/org/netbeans/modules/hibernate/resources/hibernate-configuration-3.0.dtd
14 matches
Mail list logo
