[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
14 years, 5 months
[JBoss JIRA] Created: (GTNPORTAL-1720) Rename the confusing methods setFullRender/getFullRender in PortalRequestHandler
by Minh Hoang TO (JIRA)
Rename the confusing methods setFullRender/getFullRender in PortalRequestHandler
---------------------------------------------------------------------------------
Key: GTNPORTAL-1720
URL: https://jira.jboss.org/browse/GTNPORTAL-1720
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Minh Hoang TO
{code:java}
/**
* Sets a boolean value to force whether portal will be fully rendered
* and it is only effective to an Ajax request.<p/>
*
* if the value is set to <code>true</code>, it means :<br/>
*
* 1) Only portal ui components are rendered <br/>
* 2) Portlets will be fully rendered if are inner of the portal ui components being updated
*
* @param forceFullUpdate
*/
final public void setFullRender(boolean forceFullUpdate)
{
this.forceFullUpdate = forceFullUpdate;
}
{code}
As mentioned in the Javadoc, while AJAX update is used, the forceFullUpdate decide whether only component of portal (ie: The components outside portlet window UIPortlet such as UIMaskWorkspace, UIWorkingWorkspace,...)
The name of method is very confusing. If we wish to update only components of portal, we have to call setFullRender(true) (I'm sure that most developers think of setFullRender(false) )
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (GTNPORTAL-1762) Wrong configuration to setup gatein with CAS server
by houssem njah (JIRA)
Wrong configuration to setup gatein with CAS server
---------------------------------------------------
Key: GTNPORTAL-1762
URL: https://issues.jboss.org/browse/GTNPORTAL-1762
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 3.1.0-GA
Environment: tomcat pacakge
Reporter: houssem njah
Assignee: Luc Texier
Priority: Critical
Hi,
when i want to setup gatein with cas server, i follow the documentation found here: http://docs.jboss.com/gatein/portal/3.1.0-FINAL/reference-guide/en-US/htm...
there was an error when we edit the jass.conf:
in documentation, we ask to edit this file to be like this:
org.gatein.sso.agent.login.SSOLoginModule required
org.exoplatform.services.security.j2ee.TomcatLoginModule required
portalContainerName=portal
realmName=gatein-domain
but it doesn't work.
i change this file to:
org.gatein.sso.agent.login.SSOLoginModule required;
org.exoplatform.services.security.j2ee.TomcatLoginModule required;
and the authentication work.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (GTNPORTAL-1450) Priority for skin modules
by Patrice Lamarque (JIRA)
Priority for skin modules
-------------------------
Key: GTNPORTAL-1450
URL: https://jira.jboss.org/browse/GTNPORTAL-1450
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 3.1.0-GA
Reporter: Patrice Lamarque
The css stylesheets declared in gatein-resources.xml files get merged in no specific order.
Sometimes, it is useful to control the order in which the resulting css markup appears in the merged file in order to apply css overrides.
This is typically the kind of things you would like to do in an extension.
By implementing a priority on skin module we should be able to give more control to the overrides.
--
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
14 years, 6 months
[JBoss JIRA] Created: (GTNPORTAL-1008) Gadget permissions are not working correctly (gagdet with restricted access in the AppReg are visible)
by Tugdual Grall (JIRA)
Gadget permissions are not working correctly (gagdet with restricted access in the AppReg are visible)
------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1008
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1008
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 3.0.0-GA
Reporter: Tugdual Grall
When in the App registry a gadget as been set to visible only to a restricted audience this permission is not used when in the portlet/gadget catalog.
Use case:
1- Connect as Root
2- Go in the App Registry
3- Select one gadget, for example ToDo
4- Set the permission to /platform/administrators usrs
5- log out
6- connect as mary/gtn
7- go to your dashboard
8- click add gadget:
9 - BUG: you can see the ToDo Gadget and you can add it to the page ( You are not supposed to)
10 - Edit your page
11- Click on Gadget:
12- BUG: you can see the ToDo gadget (same bug as before)
13-BUG Add it on the page, you can drop it but it wil not be visible (protected content) since you are not allowed to do it.
FIX: we need to hide the gadget from the catalog when the permissions are set.
--
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
14 years, 6 months