You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@onami.apache.org by Mikhail Mazursky <mi...@gmail.com> on 2014/02/22 15:11:41 UTC

Lets resurrect Onami!

Hello guys,

I decided to try a -SNAPSHOT of Lifecycle few days ago but it just don't
work. My maven cannot find it. We definitelly need a release.

After some investigation I found out that the build was broken [1], [2].
The first issue is fixed, the second one is not yet. I've just did some
minor fixes and closed all the resolved issues (sorry for the spam). Next I
want to update the sites for all the components and finally do a release of
at least the Lifecycle component.

I have some questions:

1. I found the release How To [3] but I'm not sure if I will be able to
perform all the steps or if I have the necessary authority. Can someone
help me?

2. It is not clear if the site should be deployed using step 3.2 or 3.3
from the How To, Finalize The Release section. For step 3.3 I haven't found
where the mentioned deploySite.sh is located.

3. Is there any interest in this project or the need for our Guice
extensions is gone? There were no commits for a long time.

What do you think?

Regards,
Mikhail.

[1]: https://issues.apache.org/jira/browse/INFRA-7360
[2]: https://issues.apache.org/jira/browse/INFRA-7362
[3]: http://onami.apache.org/committers/release-howto.html

Re: Lets resurrect Onami!

Posted by nino martinez wael <ni...@gmail.com>.

Yes a release is really really needed!
On 22 Feb 2014 15:12, "Mikhail Mazursky" <mi...@gmail.com> wrote:

> Hello guys,
>
> I decided to try a -SNAPSHOT of Lifecycle few days ago but it just don't
> work. My maven cannot find it. We definitelly need a release.
>
> After some investigation I found out that the build was broken [1], [2].
> The first issue is fixed, the second one is not yet. I've just did some
> minor fixes and closed all the resolved issues (sorry for the spam). Next I
> want to update the sites for all the components and finally do a release of
> at least the Lifecycle component.
>
> I have some questions:
>
> 1. I found the release How To [3] but I'm not sure if I will be able to
> perform all the steps or if I have the necessary authority. Can someone
> help me?
>
> 2. It is not clear if the site should be deployed using step 3.2 or 3.3
> from the How To, Finalize The Release section. For step 3.3 I haven't found
> where the mentioned deploySite.sh is located.
>
> 3. Is there any interest in this project or the need for our Guice
> extensions is gone? There were no commits for a long time.
>
> What do you think?
>
> Regards,
> Mikhail.
>
> [1]: https://issues.apache.org/jira/browse/INFRA-7360
> [2]: https://issues.apache.org/jira/browse/INFRA-7362
> [3]: http://onami.apache.org/committers/release-howto.html
>

Re: Lets resurrect Onami!

Posted by Simone Tripodi <si...@apache.org>.

Hi Mikhail! :)



> > Looks like you are talking about ONAMI-102. I'm not sure what to do about
> it. I think I forgot what the current API looks like :) So I need to try to
> use it in real application and see what improvements I can propose. BTW the
> first mention about changing this is in ONAMI-45, where the functionality
> was introduced.
>
>
yes IIRC looks like I referred to ONAMI-102; shortly, I'd rather have,
since the first release, a Lifecycle Modules API that looks like a properer
Guice module, where only a `configureLifecycle()` (or something similar)
and a small EDSL to make the binding, rather than having Modules with
multiple constructors and builder patterns.
Just have a look at how other released modules look like.


> Assuming you are talking about com.google.inject.internal package usage, I
> fixed couple of places but there is still one place
> (org.apache.onami.scopes.ConcurrentLazySingletonScopeImpl) where it is
> used. The mentioned usage can be reimplemented by using class object
> inspection instead of directly doing instanceOf check. Any better ideas?
>
>
nope sorry I should have a deep look on that :( Please apologise :(


> >   * Guice 4.0-beta has been released time ago - we need definitively be
> > prepared to integrate it :)
> >
> > I don't think that will be an issue. Probably some people wait for 4.0
> release but we can bump to -beta - I do not have any objections here.
>
>
OK thanks a lot :)


>
> >
> > > What do you think?
> > >
> >
> > let's try to find some more spare time and keep the rock rolling :)
> >
> > Sounds great! :)
>
> Kind regards,
> Mikhail.
>

All the best, have a nice weekend!
-Simo

http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi

Re: Lets resurrect Onami!

Posted by Mikhail Mazursky <mi...@gmail.com>.

Hi Simo!

Please see my comments inline.

2014-02-26 14:56 GMT+06:00 Simone Tripodi <si...@apache.org>:

> Hi Mikhail!!! :)
> see my replies inline
>
> On Sat, Feb 22, 2014 at 3:11 PM, Mikhail Mazursky <
> mikhail.mazursky@gmail.com> wrote:
>
> > Hello guys,
> >
> > I decided to try a -SNAPSHOT of Lifecycle few days ago but it just don't
> > work. My maven cannot find it. We definitelly need a release.
> >
> >
> Thanks a lot for stepping out, refreshed energies are definitively needed
> here :)
>
>
> > After some investigation I found out that the build was broken [1], [2].
> > The first issue is fixed, the second one is not yet. I've just did some
> > minor fixes and closed all the resolved issues (sorry for the spam).
> Next I
> > want to update the sites for all the components and finally do a release
> of
> > at least the Lifecycle component.
> >
> >
> +1, but before cutting a release I would kindly ask you to react to a
> couple of TODOs:
>
>   * currently the Lifecycle component is the only one that to configure
> Modules follows the Builder pattern than the usual Guice style, exposing a
> custom `configure()` method - can you modify that?
>
> Looks like you are talking about ONAMI-102. I'm not sure what to do about
it. I think I forgot what the current API looks like :) So I need to try to
use it in real application and see what improvements I can propose. BTW the
first mention about changing this is in ONAMI-45, where the functionality
was introduced.

  * there is an intense usage of Guice internal APIs, that would not work
> in an OSGi environment since internals are not exposed - can we replace
> internals with OSGi-friendly code?
>
> I'm conserned about OSGi too - in a part of our app we use Equinox.
Assuming you are talking about com.google.inject.internal package usage, I
fixed couple of places but there is still one place
(org.apache.onami.scopes.ConcurrentLazySingletonScopeImpl) where it is
used. The mentioned usage can be reimplemented by using class object
inspection instead of directly doing instanceOf check. Any better ideas?

Please note that these requests are non-blockers, take the freedom to
> choice to have them included or not in first release - code can be adjusted
> during development anyway - it is just a matter of starting with a better
> approach.
>
>
> > I have some questions:
> >
> > 1. I found the release How To [3] but I'm not sure if I will be able to
> > perform all the steps or if I have the necessary authority. Can someone
> > help me?
> >
> > 2. It is not clear if the site should be deployed using step 3.2 or 3.3
> > from the How To, Finalize The Release section. For step 3.3 I haven't
> found
> > where the mentioned deploySite.sh is located.
> >
> > 3. Is there any interest in this project or the need for our Guice
> > extensions is gone? There were no commits for a long time.
> >
> >
> Absolutely yes - the decreasing number of commits doesn't necessarily
> reflect the lack of interest but rather, at least in my case, the lack of
> spare time :( I am working on a product which relies on an OSGi container
> and no chances to have Guice involved ATM, so I don't have the reason to
> justify my work on different stuff.
>
> There are of course topics that still need to be discussed, such as:
>
>   * sandboxes still need to be discussed and promoted then released (I will
> try to send a discussion to dev@ tonight to expose the console idea);
>
>   * Guice 4.0-beta has been released time ago - we need definitively be
> prepared to integrate it :)
>
> I don't think that will be an issue. Probably some people wait for 4.0
release but we can bump to -beta - I do not have any objections here.


>
> > What do you think?
> >
>
> let's try to find some more spare time and keep the rock rolling :)
>
> Sounds great! :)

Kind regards,
Mikhail.

Re: Lets resurrect Onami!

Posted by Simone Tripodi <si...@apache.org>.

Hi Mikhail!!! :)
see my replies inline

On Sat, Feb 22, 2014 at 3:11 PM, Mikhail Mazursky <
mikhail.mazursky@gmail.com> wrote:

> Hello guys,
>
> I decided to try a -SNAPSHOT of Lifecycle few days ago but it just don't
> work. My maven cannot find it. We definitelly need a release.
>
>
Thanks a lot for stepping out, refreshed energies are definitively needed
here :)


> After some investigation I found out that the build was broken [1], [2].
> The first issue is fixed, the second one is not yet. I've just did some
> minor fixes and closed all the resolved issues (sorry for the spam). Next I
> want to update the sites for all the components and finally do a release of
> at least the Lifecycle component.
>
>
+1, but before cutting a release I would kindly ask you to react to a
couple of TODOs:

  * currently the Lifecycle component is the only one that to configure
Modules follows the Builder pattern than the usual Guice style, exposing a
custom `configure()` method - can you modify that?

  * there is an intense usage of Guice internal APIs, that would not work
in an OSGi environment since internals are not exposed - can we replace
internals with OSGi-friendly code?

Please note that these requests are non-blockers, take the freedom to
choice to have them included or not in first release - code can be adjusted
during development anyway - it is just a matter of starting with a better
approach.


> I have some questions:
>
> 1. I found the release How To [3] but I'm not sure if I will be able to
> perform all the steps or if I have the necessary authority. Can someone
> help me?
>
> 2. It is not clear if the site should be deployed using step 3.2 or 3.3
> from the How To, Finalize The Release section. For step 3.3 I haven't found
> where the mentioned deploySite.sh is located.
>
> 3. Is there any interest in this project or the need for our Guice
> extensions is gone? There were no commits for a long time.
>
>
Absolutely yes - the decreasing number of commits doesn't necessarily
reflect the lack of interest but rather, at least in my case, the lack of
spare time :( I am working on a product which relies on an OSGi container
and no chances to have Guice involved ATM, so I don't have the reason to
justify my work on different stuff.

There are of course topics that still need to be discussed, such as:

  * sandboxes still need to be discussed and promoted then released (I will
try to send a discussion to dev@ tonight to expose the console idea);

  * Guice 4.0-beta has been released time ago - we need definitively be
prepared to integrate it :)


> What do you think?
>

let's try to find some more spare time and keep the rock rolling :)

All the best,
-Simo


>
> Regards,
> Mikhail.
>
> [1]: https://issues.apache.org/jira/browse/INFRA-7360
> [2]: https://issues.apache.org/jira/browse/INFRA-7362
> [3]: http://onami.apache.org/committers/release-howto.html
>


http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi

Re: Lets resurrect Onami!

Posted by Mikhail Mazursky <mi...@gmail.com>.

Olivier,

thank you one more time! I tried snapshots today and everything works fine.


2014-02-27 4:36 GMT+06:00 Olivier Lamy <ol...@apache.org>:

> no worries!
> I reviewed all onami jenkins jobs to make them simpler.
> Now @hourly scm pooling (which deploys a new snapshot in case of any
> scm changes)
> And the sonar analysis is here:
> https://analysis.apache.org/dashboard/index/120496
>
> On 26 February 2014 13:57, Mikhail Mazursky <mi...@gmail.com>
> wrote:
> > Thanks, Olivier! I will try snapshots to see if they work now.
> >
> >
> > 2014-02-26 6:25 GMT+06:00 Olivier Lamy <ol...@apache.org>:
> >
> >> fixed see my comment.
> >>
> >> On 23 February 2014 01:11, Mikhail Mazursky <mikhail.mazursky@gmail.com
> >
> >> wrote:
> >> > Hello guys,
> >> >
> >> > I decided to try a -SNAPSHOT of Lifecycle few days ago but it just
> don't
> >> > work. My maven cannot find it. We definitelly need a release.
> >> >
> >> > After some investigation I found out that the build was broken [1],
> [2].
> >> > The first issue is fixed, the second one is not yet. I've just did
> some
> >> > minor fixes and closed all the resolved issues (sorry for the spam).
> >> Next I
> >> > want to update the sites for all the components and finally do a
> release
> >> of
> >> > at least the Lifecycle component.
> >> >
> >> > I have some questions:
> >> >
> >> > 1. I found the release How To [3] but I'm not sure if I will be able
> to
> >> > perform all the steps or if I have the necessary authority. Can
> someone
> >> > help me?
> >> >
> >> > 2. It is not clear if the site should be deployed using step 3.2 or
> 3.3
> >> > from the How To, Finalize The Release section. For step 3.3 I haven't
> >> found
> >> > where the mentioned deploySite.sh is located.
> >> >
> >> > 3. Is there any interest in this project or the need for our Guice
> >> > extensions is gone? There were no commits for a long time.
> >> >
> >> > What do you think?
> >> >
> >> > Regards,
> >> > Mikhail.
> >> >
> >> > [1]: https://issues.apache.org/jira/browse/INFRA-7360
> >> > [2]: https://issues.apache.org/jira/browse/INFRA-7362
> >> > [3]: http://onami.apache.org/committers/release-howto.html
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> Ecetera: http://ecetera.com.au
> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Re: Lets resurrect Onami!

Posted by Stephan Classen <st...@gmx.ch>.

Last November I dropped a persistence extension into sandbox before I 
got rolled over by a delayed project.
Recently I do have more time to spend on "free" code.

I could use some help:
1:
could you point me to some documentation on how to create and setup a 
web page for the persist extension under onami sandbox

2:
I had to leave some TODOs in the pom.xml file since I wasn't sure what 
to put there. Any help on these is more than appreciated.

3:
I added a first version of a new API to configure onami-persist
it is located under sandbox/persist/src/sandbox/...
There are also a few samples on how to use the API in the classes 
ApplicationManagedPersistenceUnitSamples and 
ContainerManagedPersistenceUnitSamples
I would be very grateful for some feedback on how the API feels.

Regards
Stephan



On 02/26/2014 11:36 PM, Olivier Lamy wrote:
> no worries!
> I reviewed all onami jenkins jobs to make them simpler.
> Now @hourly scm pooling (which deploys a new snapshot in case of any
> scm changes)
> And the sonar analysis is here:
> https://analysis.apache.org/dashboard/index/120496
>
> On 26 February 2014 13:57, Mikhail Mazursky <mi...@gmail.com> wrote:
>> Thanks, Olivier! I will try snapshots to see if they work now.
>>
>>
>> 2014-02-26 6:25 GMT+06:00 Olivier Lamy <ol...@apache.org>:
>>
>>> fixed see my comment.
>>>
>>> On 23 February 2014 01:11, Mikhail Mazursky <mi...@gmail.com>
>>> wrote:
>>>> Hello guys,
>>>>
>>>> I decided to try a -SNAPSHOT of Lifecycle few days ago but it just don't
>>>> work. My maven cannot find it. We definitelly need a release.
>>>>
>>>> After some investigation I found out that the build was broken [1], [2].
>>>> The first issue is fixed, the second one is not yet. I've just did some
>>>> minor fixes and closed all the resolved issues (sorry for the spam).
>>> Next I
>>>> want to update the sites for all the components and finally do a release
>>> of
>>>> at least the Lifecycle component.
>>>>
>>>> I have some questions:
>>>>
>>>> 1. I found the release How To [3] but I'm not sure if I will be able to
>>>> perform all the steps or if I have the necessary authority. Can someone
>>>> help me?
>>>>
>>>> 2. It is not clear if the site should be deployed using step 3.2 or 3.3
>>>> from the How To, Finalize The Release section. For step 3.3 I haven't
>>> found
>>>> where the mentioned deploySite.sh is located.
>>>>
>>>> 3. Is there any interest in this project or the need for our Guice
>>>> extensions is gone? There were no commits for a long time.
>>>>
>>>> What do you think?
>>>>
>>>> Regards,
>>>> Mikhail.
>>>>
>>>> [1]: https://issues.apache.org/jira/browse/INFRA-7360
>>>> [2]: https://issues.apache.org/jira/browse/INFRA-7362
>>>> [3]: http://onami.apache.org/committers/release-howto.html
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Ecetera: http://ecetera.com.au
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>
>

Re: Lets resurrect Onami!

Posted by Olivier Lamy <ol...@apache.org>.

no worries!
I reviewed all onami jenkins jobs to make them simpler.
Now @hourly scm pooling (which deploys a new snapshot in case of any
scm changes)
And the sonar analysis is here:
https://analysis.apache.org/dashboard/index/120496

On 26 February 2014 13:57, Mikhail Mazursky <mi...@gmail.com> wrote:
> Thanks, Olivier! I will try snapshots to see if they work now.
>
>
> 2014-02-26 6:25 GMT+06:00 Olivier Lamy <ol...@apache.org>:
>
>> fixed see my comment.
>>
>> On 23 February 2014 01:11, Mikhail Mazursky <mi...@gmail.com>
>> wrote:
>> > Hello guys,
>> >
>> > I decided to try a -SNAPSHOT of Lifecycle few days ago but it just don't
>> > work. My maven cannot find it. We definitelly need a release.
>> >
>> > After some investigation I found out that the build was broken [1], [2].
>> > The first issue is fixed, the second one is not yet. I've just did some
>> > minor fixes and closed all the resolved issues (sorry for the spam).
>> Next I
>> > want to update the sites for all the components and finally do a release
>> of
>> > at least the Lifecycle component.
>> >
>> > I have some questions:
>> >
>> > 1. I found the release How To [3] but I'm not sure if I will be able to
>> > perform all the steps or if I have the necessary authority. Can someone
>> > help me?
>> >
>> > 2. It is not clear if the site should be deployed using step 3.2 or 3.3
>> > from the How To, Finalize The Release section. For step 3.3 I haven't
>> found
>> > where the mentioned deploySite.sh is located.
>> >
>> > 3. Is there any interest in this project or the need for our Guice
>> > extensions is gone? There were no commits for a long time.
>> >
>> > What do you think?
>> >
>> > Regards,
>> > Mikhail.
>> >
>> > [1]: https://issues.apache.org/jira/browse/INFRA-7360
>> > [2]: https://issues.apache.org/jira/browse/INFRA-7362
>> > [3]: http://onami.apache.org/committers/release-howto.html
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Lets resurrect Onami!

Posted by Mikhail Mazursky <mi...@gmail.com>.

Thanks, Olivier! I will try snapshots to see if they work now.


2014-02-26 6:25 GMT+06:00 Olivier Lamy <ol...@apache.org>:

> fixed see my comment.
>
> On 23 February 2014 01:11, Mikhail Mazursky <mi...@gmail.com>
> wrote:
> > Hello guys,
> >
> > I decided to try a -SNAPSHOT of Lifecycle few days ago but it just don't
> > work. My maven cannot find it. We definitelly need a release.
> >
> > After some investigation I found out that the build was broken [1], [2].
> > The first issue is fixed, the second one is not yet. I've just did some
> > minor fixes and closed all the resolved issues (sorry for the spam).
> Next I
> > want to update the sites for all the components and finally do a release
> of
> > at least the Lifecycle component.
> >
> > I have some questions:
> >
> > 1. I found the release How To [3] but I'm not sure if I will be able to
> > perform all the steps or if I have the necessary authority. Can someone
> > help me?
> >
> > 2. It is not clear if the site should be deployed using step 3.2 or 3.3
> > from the How To, Finalize The Release section. For step 3.3 I haven't
> found
> > where the mentioned deploySite.sh is located.
> >
> > 3. Is there any interest in this project or the need for our Guice
> > extensions is gone? There were no commits for a long time.
> >
> > What do you think?
> >
> > Regards,
> > Mikhail.
> >
> > [1]: https://issues.apache.org/jira/browse/INFRA-7360
> > [2]: https://issues.apache.org/jira/browse/INFRA-7362
> > [3]: http://onami.apache.org/committers/release-howto.html
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Re: Lets resurrect Onami!

Posted by Olivier Lamy <ol...@apache.org>.

fixed see my comment.

On 23 February 2014 01:11, Mikhail Mazursky <mi...@gmail.com> wrote:
> Hello guys,
>
> I decided to try a -SNAPSHOT of Lifecycle few days ago but it just don't
> work. My maven cannot find it. We definitelly need a release.
>
> After some investigation I found out that the build was broken [1], [2].
> The first issue is fixed, the second one is not yet. I've just did some
> minor fixes and closed all the resolved issues (sorry for the spam). Next I
> want to update the sites for all the components and finally do a release of
> at least the Lifecycle component.
>
> I have some questions:
>
> 1. I found the release How To [3] but I'm not sure if I will be able to
> perform all the steps or if I have the necessary authority. Can someone
> help me?
>
> 2. It is not clear if the site should be deployed using step 3.2 or 3.3
> from the How To, Finalize The Release section. For step 3.3 I haven't found
> where the mentioned deploySite.sh is located.
>
> 3. Is there any interest in this project or the need for our Guice
> extensions is gone? There were no commits for a long time.
>
> What do you think?
>
> Regards,
> Mikhail.
>
> [1]: https://issues.apache.org/jira/browse/INFRA-7360
> [2]: https://issues.apache.org/jira/browse/INFRA-7362
> [3]: http://onami.apache.org/committers/release-howto.html



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy