[
https://issues.apache.org/jira/browse/MYFACES-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916483#action_12916483
]
Jakob Korherr commented on MYFACES-2933:
----------------------------------------
IMO this is a NetBeans bug and we don't really have to fix it. We've used this
configuration for a long time now and there were never any problems..
> 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.
