[
https://jira.codehaus.org/browse/MNG-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290303#comment-290303
]
Joerg Schaible commented on MNG-5235:
-
This is by design. Properties are explicitly not mentioned
[
https://jira.codehaus.org/browse/MNG-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290293#comment-290293
]
Jérôme Verstrynge commented on MNG-5235:
The pom.xml contains false statements I
forgot to r
Jérôme Verstrynge created MNG-5235:
--
Summary: Profiles not activated according to property values
Key: MNG-5235
URL: https://jira.codehaus.org/browse/MNG-5235
Project: Maven 2 & 3
Issue Type
[
https://jira.codehaus.org/browse/MWAR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290287#comment-290287
]
Thomas Vandahl commented on MWAR-267:
-
I thought this was too much to ask...
This is actually a
James Nord created SUREFIRE-823:
---
Summary: Surefire needs distinct (from failsafe) test skip
Key: SUREFIRE-823
URL: https://jira.codehaus.org/browse/SUREFIRE-823
Project: Maven Surefire
Issue T
[
https://jira.codehaus.org/browse/SCM-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290275#comment-290275
]
Robert Scholte commented on SCM-637:
Patch as provided by MRELEASE-624 doesn't work anymore, the t
[
https://jira.codehaus.org/browse/SCM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed SCM-662.
--
Resolution: Duplicate
Assignee: Robert Scholte (was: Mark Struberg)
Duplicate of SCM-637
[
https://jira.codehaus.org/browse/SCM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte moved MRELEASE-624 to SCM-662:
-
Complexity: Intermediate
Component/s: (was: perform)
[
https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290268#comment-290268
]
Robert Scholte commented on MRELEASE-719:
-
This might be a svn server-side issue. I can c