April 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPC-99) Artifacts that used to be published are not anymore

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/GTNPC-99?page=com.atlassian.jira.plugin.s... ] Chris Laprun resolved GTNPC-99. ------------------------------- Resolution: Duplicate Issue Duplicated by GTNPC-104 > Artifacts that used to be published are not anymore > --------------------------------------------------- > > Key: GTNPC-99 > URL: https://issues.jboss.org/browse/GTNPC-99 > Project: GateIn Portlet Container > Issue Type: Feature Request > Affects Versions: 2.4.0.Final, 2.4.1.CR01 > Reporter: Chris Laprun > Priority: Minor > Fix For: 2.4.1.CR04 > > > In particular, WSRP relies on the org.gatein.pc/pc-samples/war/google-portlet artifact that used to be published up to version 2.3.2-GA but is not anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-40) Implement public cache scope

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/GTNPC-40?page=com.atlassian.jira.plugin.s... ] Boleslaw Dawidowicz updated GTNPC-40: ------------------------------------- Fix Version/s: 2.4.1.CR04 (was: 2.4.1.CR03) > Implement public cache scope > ---------------------------- > > Key: GTNPC-40 > URL: https://issues.jboss.org/browse/GTNPC-40 > Project: GateIn Portlet Container > Issue Type: Task > Reporter: Julien Viet > Assignee: Julien Viet > Fix For: 2.4.1.CR04 > > > This will be useful for more efficient caching. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-63) Determine which modules need to be exported as maven artifacts and update the release profile consequently.

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/GTNPC-63?page=com.atlassian.jira.plugin.s... ] Boleslaw Dawidowicz updated GTNPC-63: ------------------------------------- Fix Version/s: 2.4.1.CR04 (was: 2.4.1.CR03) > Determine which modules need to be exported as maven artifacts and update the release profile consequently. > ----------------------------------------------------------------------------------------------------------- > > Key: GTNPC-63 > URL: https://issues.jboss.org/browse/GTNPC-63 > Project: GateIn Portlet Container > Issue Type: Sub-task > Affects Versions: 2.3.0-Beta03 > Reporter: Chris Laprun > Fix For: 2.4.1.CR04 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-64) Update maven profiles.

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/GTNPC-64?page=com.atlassian.jira.plugin.s... ] Boleslaw Dawidowicz updated GTNPC-64: ------------------------------------- Fix Version/s: 2.4.1.CR04 (was: 2.4.1.CR03) > Update maven profiles. > ---------------------- > > Key: GTNPC-64 > URL: https://issues.jboss.org/browse/GTNPC-64 > Project: GateIn Portlet Container > Issue Type: Feature Request > Affects Versions: 2.3.0-Beta03 > Reporter: Chris Laprun > Fix For: 2.4.1.CR04 > > > Profiles seem to be outdated. They should be updated to reflect proper module information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-71) FederatingPortletInvoker cannot properly be used in a distributed context

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/GTNPC-71?page=com.atlassian.jira.plugin.s... ] Boleslaw Dawidowicz updated GTNPC-71: ------------------------------------- Fix Version/s: 2.4.1.CR04 (was: 2.4.1.CR03) > FederatingPortletInvoker cannot properly be used in a distributed context > ------------------------------------------------------------------------- > > Key: GTNPC-71 > URL: https://issues.jboss.org/browse/GTNPC-71 > Project: GateIn Portlet Container > Issue Type: Bug > Affects Versions: 2.3.0-Beta05 > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.4.1.CR04 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-101) When importing a portlet, the portlet id used for the associated state should refer to the original portlet

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/GTNPC-101?page=com.atlassian.jira.plugin.... ] Boleslaw Dawidowicz updated GTNPC-101: -------------------------------------- Fix Version/s: 2.4.1.CR04 (was: 2.4.1.CR03) > When importing a portlet, the portlet id used for the associated state should refer to the original portlet > ----------------------------------------------------------------------------------------------------------- > > Key: GTNPC-101 > URL: https://issues.jboss.org/browse/GTNPC-101 > Project: GateIn Portlet Container > Issue Type: Feature Request > Affects Versions: 2.3.1-GA, 2.3.2-GA, 2.4.1.CR01 > Reporter: Chris Laprun > Fix For: 2.4.1.CR04 > > > If the PortletContext passed to the import method refers to a clone, then import currently creates a state that refers to the clone portlet id, which cannot be resolved anymore by the portlet container. Instead, the import method should look at the associated state to figure out what which portlet the cloned PortletContext refers to so that the state associated with the import properly refers to a portlet id that can always be resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-99) Artifacts that used to be published are not anymore

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/GTNPC-99?page=com.atlassian.jira.plugin.s... ] Boleslaw Dawidowicz updated GTNPC-99: ------------------------------------- Fix Version/s: 2.4.1.CR04 (was: 2.4.1.CR03) > Artifacts that used to be published are not anymore > --------------------------------------------------- > > Key: GTNPC-99 > URL: https://issues.jboss.org/browse/GTNPC-99 > Project: GateIn Portlet Container > Issue Type: Feature Request > Affects Versions: 2.4.0.Final, 2.4.1.CR01 > Reporter: Chris Laprun > Priority: Minor > Fix For: 2.4.1.CR04 > > > In particular, WSRP relies on the org.gatein.pc/pc-samples/war/google-portlet artifact that used to be published up to version 2.3.2-GA but is not anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2903) GateIn Redirect Admin UI: Node mapping list is empty when creating new redirect

by Alexandre Mendonça (JIRA)

Alexandre Mendonça created GTNPORTAL-2903: --------------------------------------------- Summary: GateIn Redirect Admin UI: Node mapping list is empty when creating new redirect Key: GTNPORTAL-2903 URL: https://issues.jboss.org/browse/GTNPORTAL-2903 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alexandre Mendonça Assignee: Alexandre Mendonça Fix For: 3.6.0.Beta02 When adding a new redirect, the nodes list in the node mapping (both for origin and redirect) are not filled. Only after saving and editing the redirect, they are made available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-105) Calling PortletApplicationDeployer.removeListener() attempts to add the listener instead.

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/GTNPC-105?page=com.atlassian.jira.plugin.... ] Boleslaw Dawidowicz resolved GTNPC-105. --------------------------------------- Resolution: Done > Calling PortletApplicationDeployer.removeListener() attempts to add the listener instead. > ----------------------------------------------------------------------------------------- > > Key: GTNPC-105 > URL: https://issues.jboss.org/browse/GTNPC-105 > Project: GateIn Portlet Container > Issue Type: Bug > Affects Versions: 2.4.1.CR02 > Reporter: Ken Finnigan > Fix For: 2.4.1.CR03 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2871) An overriding gtmpl does not see classes from its own war

by Vu Viet Phuong (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2871?page=com.atlassian.jira.pl... ] Vu Viet Phuong commented on GTNPORTAL-2871: ------------------------------------------- We have discussed about this, and the main problem is the limitation of our extension machanism (provided by kernel). It only allow to override resources files like templates, the PortalContainerClassloader (that is written as a merged classloader of all the extension dependencies) but it only provide machanism to overwrite resource file in conclusion, can't fix this in GateIn for now > An overriding gtmpl does not see classes from its own war > --------------------------------------------------------- > > Key: GTNPORTAL-2871 > URL: https://issues.jboss.org/browse/GTNPORTAL-2871 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > > Probably a class loading issue. Steps to reproduce will follow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues April 2013