[JBoss JIRA] Created: (GTNPORTAL-1001) GateIn+Opera: problem with script
by Benjamin Seyinbour (JIRA)
GateIn+Opera: problem with script
---------------------------------
Key: GTNPORTAL-1001
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1001
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 3.0.0-GA
Environment: Linux [Centos 5.4] Opera[version:10.10) Java [version 1.6.0_16]
Reporter: Benjamin Seyinbour
Fix For: 3.0.0-GA
I keep getting the following error in Opera whenever I click a command button or link in GateIn :
<localhost>
[Error:
name: TypeError
message: Statement on line 221: Type mismatch (usually non-object value supplied where object required)
]
When this happens the top half of the screen turns black and I can't see GateIn .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1311) Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively
by Minh Hoang TO (JIRA)
Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively
-----------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1311
URL: https://jira.jboss.org/browse/GTNPORTAL-1311
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Minh Hoang TO
Assignee: Minh Hoang TO
In legacy code, both UINavigationPortlet and UISitemapPortlet use UIPortalNavigation to handle the underlying navigations. That was logical in the past as before navigation portlet showed all PageNavigations as UISitemap did.
Now, the methods declared in UIPortalNavigaton belongs to two independent groups, one group consists of methods used in sitemap portlet. The other consists of methods used in navigation portlet.
On the other hand, using UIPortalNavigation in sitemap portlet requires storing template name in the PortletPreference.
Hence, it 's better to split UIPortalNavigation into two classes now
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1605) Merging PageNavigations should also merge child PageNodes
by Matt Wringe (JIRA)
Merging PageNavigations should also merge child PageNodes
---------------------------------------------------------
Key: GTNPORTAL-1605
URL: https://jira.jboss.org/browse/GTNPORTAL-1605
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Matt Wringe
The PageNavigation.merge command only merges in top level PageNodes, if a PageNode with the same name already exists, it will overwrite the previous node with a new one.
This prevents being able to add a new page node to a subnode which already exists.
For example, the administration node by default contains the app-registry and page-management PageNodes. I cannot use the extension mechanism to add an extra PageNode here, since the PageNavigation.merge will delete the current administration node and overwrite it with the one I specify in the extension. In this situation I am stuck adding it to another top level location, which is not ideal.
What should happen is that the child PageNodes get merged together, so that I can add extra nodes anywhere in the PageNode tree.
This will however change the behaviour of how extensions work. What this means is that you can no longer overwrite or remove PageNodes using the extension mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1740) GateIn 3.1.0-GA won't build with Maven 3
by Benito Bertoli (JIRA)
GateIn 3.1.0-GA won't build with Maven 3
----------------------------------------
Key: GTNPORTAL-1740
URL: https://issues.jboss.org/browse/GTNPORTAL-1740
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.1.0-GA
Environment: OS: Win7-x64 Home Premium
java jdk6
maven 3.0.1
Reporter: Benito Bertoli
I downloaded GateIn 3.1.0 src and tried to build it using maven. I used "mvn clean install" and got the following error:
[INFO] Scanning for projects...
[ERROR] The build could not read 6 projects -> [Help 1]
[ERROR]
[ERROR] The project org.exoplatform.portal:exo.portal.sample.extension.root:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\examples\extension\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 24, column 11 -> [Help 2]
[ERROR]
[ERROR] The project org.exoplatform.portal:exo.portal.sample.portal.root:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\examples\portal\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 24, column 11 -> [Help 2]
[ERROR]
[ERROR] The project org.gatein.portal.examples.portlets:parent:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\examples\portlets\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 5, column 12 -> [Help 2]
[ERROR]
[ERROR] The project org.gatein.portal.examples.skins:parent:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\examples\skins\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 5, column 12 -> [Help 2]
[ERROR]
[ERROR] The project org.exoplatform.portal:exo.portal.starter.war:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\starter\war\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 23, column 11 -> [Help 2]
[ERROR]
[ERROR] The project org.exoplatform.portal:starter-gatein:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\starter\ear\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 23, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month