4:40 p.m.
Is there any document anywhere, or does anyone know why things are
placed in the current maven module structure? ie what makes something a
'component' what should go under 'web', etc...
It gets a bit confusing to try and figure out where new things should
go.
Thanks,
Matt Wringe
4:44 p.m.
I think there is not specific rule, anything new should be discussed and debated.
On Mar 28, 2012, at 4:40 PM, Matt Wringe wrote:
Is there any document anywhere, or does anyone know why things are
placed in the current maven module structure? ie what makes something a
'component' what should go under 'web', etc...
It gets a bit confusing to try and figure out where new things should
go.
Thanks,
Matt Wringe
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
5:28 p.m.
On Wed, 2012-03-28 at 16:44 +0200, Julien Viet wrote:
I think there is not specific rule, anything new should be discussed
and debated.
Ok so lets discuss then for the mobile stuff. There are a couple of
things going on here:
1) jsp page which does the device detection (plus any images, etc.)
2) the WebRequestHandler
3) integration with the web nav controller
4) configuration (goes into conf/gatein) and other configuration files
Right now I have stuff added under /web/portal (configuration files for
the mobile service and the configuration for integration into the nav
controller). Also the device detection jsp is here as well.
The conf/gatein configuration files in /packaging.
and the jar which contains the service in a separate module.
It touches a bunch of different things in the portal, and its not always
clear where things like the jar to create the mobile services should go.
On Mar 28, 2012, at 4:40 PM, Matt Wringe wrote:
> Is there any document anywhere, or does anyone know why things are
> placed in the current maven module structure? ie what makes something a
> 'component' what should go under 'web', etc...
>
> It gets a bit confusing to try and figure out where new things should
> go.
>
> Thanks,
>
> Matt Wringe
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
6:11 p.m.
Could it be packaged as an extension? Not sure that's the way we'd want to go but
curious about feasibility…
On Mar 28, 2012, at 5:28 PM, Matt Wringe wrote:
On Wed, 2012-03-28 at 16:44 +0200, Julien Viet wrote:
> I think there is not specific rule, anything new should be discussed and debated.
Ok so lets discuss then for the mobile stuff. There are a couple of
things going on here:
1) jsp page which does the device detection (plus any images, etc.)
2) the WebRequestHandler
3) integration with the web nav controller
4) configuration (goes into conf/gatein) and other configuration files
Right now I have stuff added under /web/portal (configuration files for
the mobile service and the configuration for integration into the nav
controller). Also the device detection jsp is here as well.
The conf/gatein configuration files in /packaging.
and the jar which contains the service in a separate module.
It touches a bunch of different things in the portal, and its not always
clear where things like the jar to create the mobile services should go.
> On Mar 28, 2012, at 4:40 PM, Matt Wringe wrote:
>
>> Is there any document anywhere, or does anyone know why things are
>> placed in the current maven module structure? ie what makes something a
>> 'component' what should go under 'web', etc...
>>
>> It gets a bit confusing to try and figure out where new things should
>> go.
>>
>> Thanks,
>>
>> Matt Wringe
>>
>> _______________________________________________
>> gatein-dev mailing list
>> gatein-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/gatein-dev
>
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn: http://blog.gatein.org / http://twitter.com/gatein
Follow me: http://metacosm.info/metacosm / http://twitter.com/metacosm
6:42 p.m.
On Wed, 2012-03-28 at 18:11 +0200, Christophe Laprun wrote:
Could it be packaged as an extension? Not sure that's the way
we'd want to go but curious about feasibility…
It doesn't lend itself well to be packaged as an extension, it needs to
make changes to the configuration files (like the nav controller) and
integration in some other areas.
If we were to make some changes and make it possible to add things like
this in an extension, then it might make sense to do it as a separate
extension. I would like to keep things in separate extensions as much as
possible.
On Mar 28, 2012, at 5:28 PM, Matt Wringe wrote:
> On Wed, 2012-03-28 at 16:44 +0200, Julien Viet wrote:
>> I think there is not specific rule, anything new should be discussed and
debated.
>
> Ok so lets discuss then for the mobile stuff. There are a couple of
> things going on here:
>
> 1) jsp page which does the device detection (plus any images, etc.)
> 2) the WebRequestHandler
> 3) integration with the web nav controller
> 4) configuration (goes into conf/gatein) and other configuration files
>
> Right now I have stuff added under /web/portal (configuration files for
> the mobile service and the configuration for integration into the nav
> controller). Also the device detection jsp is here as well.
>
> The conf/gatein configuration files in /packaging.
>
> and the jar which contains the service in a separate module.
>
> It touches a bunch of different things in the portal, and its not always
> clear where things like the jar to create the mobile services should go.
>
>> On Mar 28, 2012, at 4:40 PM, Matt Wringe wrote:
>>
>>> Is there any document anywhere, or does anyone know why things are
>>> placed in the current maven module structure? ie what makes something a
>>> 'component' what should go under 'web', etc...
>>>
>>> It gets a bit confusing to try and figure out where new things should
>>> go.
>>>
>>> Thanks,
>>>
>>> Matt Wringe
>>>
>>> _______________________________________________
>>> gatein-dev mailing list
>>> gatein-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/gatein-dev
>>
>
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn: http://blog.gatein.org / http://twitter.com/gatein
Follow me: http://metacosm.info/metacosm / http://twitter.com/metacosm
6:30 p.m.
I would say:
for the code : a new component in components/web like components/web/mobile
and as you said
for the internal configuration of services : web/portal
for the public configuration : gatein/conf
On Mar 28, 2012, at 5:28 PM, Matt Wringe wrote:
On Wed, 2012-03-28 at 16:44 +0200, Julien Viet wrote:
> I think there is not specific rule, anything new should be discussed and debated.
Ok so lets discuss then for the mobile stuff. There are a couple of
things going on here:
1) jsp page which does the device detection (plus any images, etc.)
2) the WebRequestHandler
3) integration with the web nav controller
4) configuration (goes into conf/gatein) and other configuration files
Right now I have stuff added under /web/portal (configuration files for
the mobile service and the configuration for integration into the nav
controller). Also the device detection jsp is here as well.
The conf/gatein configuration files in /packaging.
and the jar which contains the service in a separate module.
It touches a bunch of different things in the portal, and its not always
clear where things like the jar to create the mobile services should go.
> On Mar 28, 2012, at 4:40 PM, Matt Wringe wrote:
>
>> Is there any document anywhere, or does anyone know why things are
>> placed in the current maven module structure? ie what makes something a
>> 'component' what should go under 'web', etc...
>>
>> It gets a bit confusing to try and figure out where new things should
>> go.
>>
>> Thanks,
>>
>> Matt Wringe
>>
>> _______________________________________________
>> gatein-dev mailing list
>> gatein-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/gatein-dev
>
4420
days inactive
4420
days old
5 comments
3 participants
participants (3)
-
Christophe Laprun -
Julien Viet -
Matt Wringe