May 2012 - gatein-dev - Jboss List Archives

by Julien Viet

Hi Folks, this week we will release GateIn 3.3. The 3.3 release will feature: - SAML2 support https://community.jboss.org/en/gatein/blog/2012/05/24/gatein-and-saml2-in... - Improved javascript serving based on navigation controller to improve JS cacheability https://community.jboss.org/wiki/ResourceController - More AS7 compatibility - First version of javascript module system https://docs.jboss.org/author/display/GTNPORTAL/GDG-JavaScript+Resource+M... - JQuery out of the box / Rebase of GateIn javascript on top of JQuery https://docs.jboss.org/author/display/GTNPORTAL/GDG-JQuery The release will be performed by Trong on Friday and tomorrow the team will focus on finding obvious bugs that would prevent its normal usage. We are doing a straight 3.3 release without any prior candidate release or beta or whatsoever for several reasons: 1/ we want to provide a few features per release. 2/ we want to release more frequently 3/ we expect a 3.4 release during June (!!!) and so on later So if you are willing to help us, you can spend time to test the current gatein-portal master branch and report (here) the issues you can find. Julien

12 years, 5 months

6
19
0 / 0

Can not start server when run script outside "bin" directory on JBoss 7

by Hai Nguyen

Hi guys As my subject, I encounter it when I test GateIn for release towmorrow. The cause come from "standalone.conf" file which we used $PWD to declare "exo.conf.dir" property. I created https://issues.jboss.org/browse/GTNPORTAL-2449 and propose a patch which purpose replace $PWD to use $JBOSS_HOME. And tested on Window So, can someone help me validate patch to push to GateIn? We need it to release towmorrow

12 years, 6 months

1
0
0 / 0

Descriptor sanitization

by Julien Viet

I want soon to remove support for old XML descriptor "portlet-preferences" that is not used anymore in GateIn except for unit tests. This file is legacy of eXo Portal 2.5 was deprecated in GateIn 3.0 in favor of the inline port let preferences in a <portet-application> tag. This will remove some hack code necessary to properly support it. I want also to update the existing descriptors to use the correct XML as some of the XML is not correct. let me know if it raise any concern. cheers Julien

12 years, 6 months

2
2
0 / 0

GateIn-Portal Build improvements

by Marko Strukelj

I've done some changes on gatein-portal build that fall into the category of ergonomics. A description of the changes is here: https://issues.jboss.org/browse/GTNPORTAL-2438 There is an updated https://github.com/gatein/gatein-portal/blob/master/README.txt To simplify / clean up things there is no support for the old equivalents of the system properties. Since there is one-to-one mapping, switching should be trivial. - marko

12 years, 6 months

1
0
0 / 0

Git migration update

by Boleslaw Dawidowicz

Just a small update 1) All SVN repositories that we planned to move are currently on github. Full list here: https://community.jboss.org/wiki/GateInPortal-GitMigrationAndUsage 2) There is a dedicated mailing list called gatein-pull-requests(a)lists.jboss.org. Each repository on our http://github.com/gatein space has this mailing list configured with email service hook. This means all pull requests and push notifications go there. You can subscribe here: https://lists.jboss.org/mailman/listinfo/gatein-pull-requests Ideally in the future this lists should also be a place to communicate about pull request (for example when one needs to be corrected). 3) Each repository on github has an IRC service hook pointing to #gatein channel on free node. This is other way in which you can track push and pull requests activities. Bolek

12 years, 6 months

1
0
0 / 0

SVN to Git migration - current status

by Boleslaw Dawidowicz

Hi, I would like to give you some status about migration from svn to git and ask for your help in the process. 1) I just switched off svn write access to anything besides EPP bits. Let me know if you have any urgent commits to make 2) Today we migrated most of svn repositories to github - as previews. https://github.com/mstruk/gatein-wci-STAGING https://github.com/bdaw/gatein-wsrp-preview https://github.com/bdaw/gatein-mop-preview https://github.com/bdaw/gatein-sso-preview https://github.com/bdaw/gatein-simplecaptcha-preview https://github.com/bdaw/gatein-common-preview https://github.com/bdaw/gatein-packager-preview https://github.com/bdaw/gatein-dep-preview https://github.com/bdaw/gatein-parent-preview Once it is verified that those were migrated properly we will promote them (meaning renaming and donating to "gatein" organization on github). This can happen this week - depends on how fast we are able to verify all the bits. 3) We need help with verification process. Any extra eyes are welcome. Here are some notes about what should be checked for each repository I) If "git branch -a" matches list of branches in svn II) If "git tag -l" matches list of tags in svn. It can be both not all or too much entries in git - sometimes some "junk" pass thru. III) If master builds… IV) If pom.xml contains proper "<scm>" definition pointing to github and proper release plugin properties. Here is the example: <scm> <connection>scm:git:git://github.com/gatein/gatein-pc.git</connection> <developerConnection>scm:git:ssh://git@github.com/gatein/gatein-pc.git</developerConnection> <url>https://github.com/gatein/gatein-pc</url> </scm> <properties> …  <useReleaseProfile>false</useReleaseProfile> <arguments>-Prelease</arguments> <version.release.plugin>2.2.1</version.release.plugin> <pushChanges>false</pushChanges> <autoVersionSubmodules>true</autoVersionSubmodules>  <version.buildnumber.plugin>1.0</version.buildnumber.plugin> </properties> I updated only pom.xml in master with those. Not in branches. V) Check out whole svn structure of the component and compare random tags and branches between svn and git. Example: git checkout 2.1.0-CR02 diff -qr . /some/path/svn/gatein/components/pc/tags/2.1.0-CR02 | grep -v -e 'DS_Store' -e 'Thumbs' -e '.git*' -e '.svn' Bolek

12 years, 6 months

2
1
0 / 0

/admin security constraint in portal.war

by Ken Finnigan

All, Wanted to find out whether there is still a need to have the below security constraint within web.xml of portal.war: <security-constraint> <web-resource-collection> <web-resource-name>admin authentication</web-resource-name> <url-pattern>/admin/*</url-pattern> <http-method>POST</http-method> <http-method>GET</http-method> </web-resource-collection> <auth-constraint> <role-name>admin</role-name> </auth-constraint> <user-data-constraint> <transport-guarantee>NONE</transport-guarantee> </user-data-constraint> </security-constraint> If not, any objections to removing it? Thanks Ken Finnigan

12 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-dev May 2012