-
1. Re: What is target platform for archetypes
ppitonak Feb 5, 2014 9:26 AM (in response to jhuska)What kind of change is needed for simpleapp to be deployable to Tomcat? Are there currently some profiles for various containers?
IMHO archetype with no profile selected should generate a project for EE environment, i.e. for AS/WildFly/EAP.
Pavol
-
Original Message -
Hello guys,
I would like to ask you what servlet/application server should be a default
platform for the archetypes ?
Currently for example simpleapp can be deployed only to AS/WildFly/EAP
without further modification in the code.
Is that our intention or we want to support following scenario:
no maven profile selected --> built .war for servlet containers
jee6 maven profile selected ---> AS/EAP/WildFly.
Regards
Juro
Posted by forums
Original post: https://community.jboss.org/message/855892#855892
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev
-
2. Re: What is target platform for archetypes
jhuska Feb 6, 2014 6:06 AM (in response to ppitonak)To run simpleapp on Tomcat one needs to add javax.faces:javax.faces-api and org.glassfish:javax.faces compile time dependencies.
There are two profiles, jee and release --> they both target to JEE app server.
When no profile selected than .war aimed for JEE is still built.
I agree with Pavol. IMHO we should add Tomcat profile there and update docs.
-
3. Re: What is target platform for archetypes
At some point we were thinking about dropping pure servlet containers and
require on EE web profile instead.
But I'm not sure how this idea stands now, @Brian?
On Thu, Feb 6, 2014 at 12:06 PM, Juraj Húska <jhuska@redhat.com> wrote:
To run simpleapp on Tomcat one needs to add
javax.faces:javax.faces-api and org.glassfish:javax.faces compile time
dependencies.
There are two profiles, jee and release --> they both target to JEE
app server.
When no profile selected than .war aimed for JEE is still built.
I agree with Pavol. IMHO we should add Tomcat profile there and update
docs.
Posted by forums
Original post: https://community.jboss.org/message/856507#856507
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev
-
4. Re: What is target platform for archetypes
bleathem Feb 12, 2014 3:50 PM (in response to Lukáš Fryč )I'd like to see us support both servlet and EE containers with our
archetypes at generation time. We'd build in the archetype conditional
asking the user if the generated project should target EE or servlet
containers. This should also be done in our Forge plugin.
Most users are targeting a single container with their app. Taking a
profile approach leaves a lot of unnecessary clutter in their pom.xml.
whereas asking at archetype evaluation time we can trim the unnecessary
pieces out of the pom.xml.
We can proceed with this for the simpleapp archetype, but we will have
problems introducing this approach to the kitchensink-rf archetype, as
that is tied heavily to the downstream jsf quickstart and archetype.
Let's leave the kitchensink archetype targeting only EE containers for
now.
Brian
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev
-
5. Re: What is target platform for archetypes
jhuska Feb 13, 2014 3:30 AM (in response to bleathem)I have created following issues to track the effort:
Simple app: https://issues.jboss.org/browse/RF-13545
RichFaces Forge plugin: [RF-13546] Forge plugin: support for Servlet or JavaEE containers - JBoss Issue Tracker