Hi, I've tried to reverted this commit https://github.com/gatein/gatein-portal/commit/f4542dda3a8e02847ced97a3ffc4de6c7bf611cc 
and it works

for gatein jboss-as720 packaging issue, it also happens on gatein master, so I guess this issue is not related to GTNPORTAL-3390


On Fri, Feb 7, 2014 at 4:16 PM, Phuong Viet VU <phuongvv@exoplatform.com> wrote:
Hi, I've tested the branch https://github.com/gatein/gatein-portal/commits/GTNPORTAL-3390

- It works well for tomcat7, but doesn't work for Jboss-AS711, there is exception when the server's started:
Caused by: java.lang.NoClassDefFoundError: org/infinispan/configuration/parsing/ParserRegistry

- There are compilation errors for GateIn-Jboss-AS720 packaging:
master/packaging/jboss-as7/extension/src/main/java/org/gatein/integration/jboss/as7/portal/PortalResourceDescriptions.java:[33,50] error: cannot find symbol
[ERROR] package org.jboss.as.controller.descriptions.common



On Fri, Jan 31, 2014 at 5:40 PM, Julien Viet <julien@julienviet.com> wrote:
so this is going on thansk to the kind help of the *reks

gatein-dep / gatein-common have been release
I will achieve pc/mop and marek wci/sso
and hopefully I can push a migration branch in gatein-portal by today that Marko should look at soon.



Julien Viet

On Friday 31 January 2014 at 10:40, Julien Viet wrote:

thanks! let’s continue :-)

Julien Viet

On Friday 31 January 2014 at 10:37, Bolesław Dawidowicz wrote:

Released

On 01/31/2014 10:06 AM, Julien Viet wrote:
it starts well, I am not able to release gatein-dep 1.3.0-Beta01 :-)

can someone with the appropriate power help us ? (release the repo, make
a new release, change system right, whatever will help).

let me know when this is achieved

ps : this is a blocker thing, in the meantime I’ll play Tetris until it
is resolved

Julien Viet

On Friday 31 January 2014 at 09:47, Julien Viet wrote:

Hi,

I migrated the Tomcat version of GateIn and I need the help of a
qualified person maintaining GateIn for JBoss AS to port those changes
for JBoss AS / Wildly .

On my side I will proceed to:
- release new gatein-dep 1.3.0.Beta01
- release gatein common 2.2.0.Beta01 + wci + portlet + mop
- push my current master work in a branch

let me know how / when you can proceed.

Julien

Julien Viet

On Thursday 30 January 2014 at 15:44, Julien Viet wrote:

I updated the gatein-dep artifact here :


please review / comment

Julien Viet

On Wednesday 29 January 2014 at 08:29, Julien Viet wrote:

so this thirdparty upgrade means to have a new gatein-dep (as said
before) and branch all projects using it (which means
common,wci,portlet,etc…).

unless there is an objection or veto, I will start with common today
and then proceed to wci / pc .

can someone take care of doing it for SSO as I don’t think I have
the proper rights to do it on the JIRA side… (also there may be
things to check I’m not aware of).

Then I would proceed to gatein master.

I recall that the main change of this upgrade beside JCR itself is
the abandon of JBoss Cache in favor of Infinispan.

Julien Viet

On Tuesday 28 January 2014 at 17:12, Julien Viet wrote:

I pushed those third parties upgrade :


Julien Viet

On Tuesday 28 January 2014 at 16:57, Julien Viet wrote:

I can do the release with the new gatein-dep.

I’ll post gatein-dep for review here before. Tomorrow probably.

shall you review it ?

Julien Viet

On Tuesday 28 January 2014 at 16:53, Marek Posolda wrote:

Ok, sent PR to WCI just to ensure that it won't be forgotten

Marek

On 28.1.2014 16:38, Julien Viet wrote:
actually I need to upgrade the full gatein-dep first and then we
need to upgrade everthing….

dependencies like SLF have changed and many others.

I’m working first on gatein-dep and will make a 1.3.0.Beta01 first.

Julien Viet

On Tuesday 28 January 2014 at 15:04, Marek Posolda wrote:

Hi,

Just a reminder that I will likely need new WCI release and
update WCI in gatein-master for impersonation. And AFAIK
exo-kernel (and some other gatein components like PC, SSO etc)
has dependency on WCI. So it seems that GateIn master will have
dependency on different WCI version than kernel and other
components.

I am pretty confident that everything will be fine at runtime,
just not sure if it is not a problem from productization
perspective or whatever. Just wanted to point this, hope it's
not big issue at all;-)

Marek

On 28.1.2014 11:47, Julien Viet wrote:
Hi,

I am working on integrating JCR 1.16.0-Alpha4 in GateIn master.

For this purpose I will integrate it in MOP first and thus
create a branch in this code base for 1.2.x and have master
use 1.3.0-Beta01-SNAPSHOT.

Then I will proceed to GateIn upgrade itself.

let me know if that raise any issue.

Julien Viet



_______________________________________________
gatein-dev mailing list



_______________________________________________
gatein-dev mailing list



--
Bolesław Dawidowicz
JBoss Portal Platform Architect | GateIn Portal Project Lead
_______________________________________________
gatein-dev mailing list



_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev