Jerome Dochez wrote:
> Also, can you clarify why "admin gui needs to be built before v3" ? Is
> this because they have a few OSGi modules that always ship in V3 ? If
> that's the case, that code should move from admin gui build process to
> the v3.
We include 2 .jar files as part of web.zip:
console-plugin-service-10.0-SNAPSHOT.jar
console-web-plugin-10.0-SNAPSHOT.jar
I would like to install these are part of the IPS package that is
responsible for delivering the admingui.war file. We spoke w/ Snjezana
about this yesterday, however, the IPS work won't be completed for at
least 1 week. In addition to these files, we have 2 more that need to be
present right now (jsftemplating / dataprovider) that aren't currently
part of web.zip and 2 more that will be created soon (gui util, gui base
plugin). We would like to add these to web.zip until the IPS details can
be worked out, then remove all admingui.war dependencies.
Ken
>
> jerome
>
> On Jul 22, 2008, at 6:28 PM, Sahoo wrote:
>
>> Simple answer is they all should be part of same build. We shall do
>> it after SCF.
>>
>> Or, if you have cycles to do so, let me know. We can do it before SCF
>> as well.
>>
>> Thanks,
>> Sahoo
>>
>> Bhakti Mehta wrote:
>>> Jerome/Koshuke/Sahoo and others,
>>> Not sure if you have already discussed this.
>>> What are the reasons
>>> 1. admin gui is not built part of v3 workspace/
>>> We ran into an issue today where Terena could not build and all I
>>> did was create
>>> this new job http://hudson.sfbay/job/admingui-prelude-m1a/1/console
>>> which built admin gui and pushed to maven repo using
>>> mirror-glassfish-repository and that helped but
>>> we need to know the main cause. Also this creates a circular
>>> dependency where v3 needs to be built before admin gui and admin gui
>>> needs to be built before v3. I think Anissa and Ken removed some
>>> references but still it showed today
>>> that if admin gui makes changes to its dependencies it needs to be
>>> pushed out before the web bundle is created?
>>> Why is admin gui so different from others?
>>>
>>> 2. jspimpl is still snapshot? When all other external workspaces are
>>> release based why are we still following snapshots for jspimpl?
>>>
>>> Pls can you clarify. These will help reduce problems we encounter
>>> and maybe we can find better solutions here
>>> Regards,
>>> Bhakti
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>