[
https://issues.apache.org/jira/browse/MYFACES-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916480#action_12916480
]
Leonardo Uribe commented on MYFACES-2933:
-----------------------------------------
Hi Werner
There is no problem. Personally I like to have something like this one:
http://svn.apache.org/repos/asf/myfaces/myfaces-build-tools/trunk/maven2-archetypes/myfaces-archetype-helloworld/src/main/resources/archetype-resources/pom.xml
In this case we have jetty plugin registered on top:
<build>
<finalName>${artifactId}</finalName>
<plugins>
<plugin>
<!--This plugin allows to run the example using mvn jetty:run
-->
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>${symbol_dollar}{maven.jetty.plugin.version}</version>
<configuration>
<scanIntervalSeconds>10</scanIntervalSeconds>
</configuration>
</plugin>
</plugins>
</build>
And the additional profile jettyConfig:
<profile>
<!-- Debug profile for myfaces and jetty.
It allows to see debug messages using -PjettyConfig -->
<id>jettyConfig</id>
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
</resource>
<resource>
<directory>src/main/log4j</directory>
</resource>
</resources>
<plugins>
<plugin>
<!--This plugin allows to run the example using mvn
jetty:run -->
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>${symbol_dollar}{maven.jetty.plugin.version}</version>
<configuration>
<scanIntervalSeconds>10</scanIntervalSeconds>
<systemProperties>
<systemProperty>
<name>org.apache.commons.logging.Log</name>
<value>org.apache.commons.logging.impl.Log4JLogger</value>
</systemProperty>
</systemProperties>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>${symbol_dollar}{log4j.version}</version>
<type>jar</type>
</dependency>
</dependencies>
</profile>
To have jetty with additional information. The important is have a param to
prevent mojarra and myfaces be on the classpath at the same time.
> Our archetype poms are not entirely correctly understood by Netbeans
> --------------------------------------------------------------------
>
> Key: MYFACES-2933
> URL: https://issues.apache.org/jira/browse/MYFACES-2933
> Project: MyFaces Core
> Issue Type: Bug
> Components: Archetype
> Affects Versions: 2.0.2
> Environment: all
> Reporter: Werner Punz
>
> We have a small structural problem in the myfaces archetypes. This is not a
> bug in our code, but nevertheless easily fixable. The problem is the way we
> handle the profiles which is not correctly understood by Netbeans 6.9.
> We have following code:
> <profiles>
> <profile>
> <id>myfaces</id>
> <activation>
> <property>
> <name>!jsf</name>
> </property>
> </activation>
> and
> <profile>
> <!-- Activate by adding -Djsf=mojarra -->
> <id>mojarra</id>
> <activation>
> <property>
> <name>jsf</name>
> <value>mojarra</value>
> </property>
> </activation>
> No this structure just should ensure that if no jsf=... is set myfaces is
> chosen automatically. This makes netbeans go haiwire if you chosse mojarra as
> profile because suddenly we have the mojarra and myfaces dependencies
> parallely in the project.
> Since this structure is mostly a hack we should replace it with the correct
> way to do things here:
> <activation>
> <activeByDefault>true</activeByDefault>
> <property>
> <name>jsf</name>
> <value>myfaces</value>
> </property>
> </activation>
> instead of !jsf so if no value is given we activate the myfaces profile by
> default
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
