11:30 a.m.
Hi *,
I have finally found out why the hell the ported [1] Sample Portal did
not work.
The clue was that the sample portal built within the standard GateIn
build process is only as-if built by maven. The deployable directory is
in fact built by an ad-hoc Ant script and in various ways combined with
resources outside examples/portal.
I could make the quickstart Sample Portal build pure maven, see [2].
Should I do the same for the gatein tree and it's build?
[1] Porting to quickstarts means making the build independent from the
GateIn tree, happening under [2]
[2] https://github.com/gatein/gatein-portal-quickstart
Best,
Peter
2:22 p.m.
I actually didn't realize that :)
It should be made buildable the same way as the portal extension.
Thomas
On 10/19/2012 06:30 PM, Peter Palaga wrote:
Hi *,
I have finally found out why the hell the ported [1] Sample Portal did
not work.
The clue was that the sample portal built within the standard GateIn
build process is only as-if built by maven. The deployable directory is
in fact built by an ad-hoc Ant script and in various ways combined with
resources outside examples/portal.
I could make the quickstart Sample Portal build pure maven, see [2].
Should I do the same for the gatein tree and it's build?
[1] Porting to quickstarts means making the build independent from the
GateIn tree, happening under [2]
[2] https://github.com/gatein/gatein-portal-quickstart
Best,
Peter
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
6:37 a.m.
Hi Thomas,
It should be made buildable the same way as the portal extension.
Both are similarly broken, so if do not veto me, I fix them both.
I'd perform these changes to make maven produce the same what is
currently done with ANT ad hoc copying thus making the build proces more
transparent:
(1) Config projects
Maven jar packager does not include
src/main/java/conf/configuration.xml
This is a problem in both portal and extension config projects.
conf/configuration.xml needs to be moved from src/main/java to
src/main/resources
(2) EAR
(2.1) Delete src/main/application/META-INF/gatein-jboss-beans.xml
(2.2) Move MANIFEST.MF from
packaging/jboss-as7/pkg/src/main/resources/jboss/samples/gatein/extensions/*/META-INF
to src/main/resources of the respective projects and configure
maven-ear-plugin to use
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
(2.3) remove the two application.xml files from
packaging/jboss-as7/pkg/src/main/resources/jboss/samples/gatein/extensions/*/META-INF
and configure maven-ear-plugin to reach the same result which can be
done very easily.
(2.4) Adjust the the ant code in
packaging/jboss-as7/pkg/package.xml
to the changes done in (2.3) and (2.4).
Open question:
* Is it OK to make the GateIn build process to use EAR archives instead
of *.ear directories to deploy the samples?
Best,
Peter
On 2012-10-19 21:22, Thomas Heute wrote:
I actually didn't realize that :)
It should be made buildable the same way as the portal extension.
Thomas
On 10/19/2012 06:30 PM, Peter Palaga wrote:
> Hi *,
>
> I have finally found out why the hell the ported [1] Sample Portal did
> not work.
>
> The clue was that the sample portal built within the standard GateIn
> build process is only as-if built by maven. The deployable directory is
> in fact built by an ad-hoc Ant script and in various ways combined with
> resources outside examples/portal.
>
> I could make the quickstart Sample Portal build pure maven, see [2].
>
> Should I do the same for the gatein tree and it's build?
>
> [1] Porting to quickstarts means making the build independent from the
> GateIn tree, happening under [2]
>
> [2] https://github.com/gatein/gatein-portal-quickstart
>
> Best,
>
> Peter
> _______________________________________________
> gatein-dev mailing list
> gatein-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
5113
days inactive
5116
days old
2 comments
2 participants
participants (2)
-
Peter Palaga -
Thomas Heute