[
https://issues.jboss.org/browse/SEAM-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637882#comment-12637882
]
Jason Porter commented on SEAM-115:
-----------------------------------
For the Security stuff, I wonder if it may be better to simply include the bom
in the dependencyManagement section with the seam.version from the security
parent. That should keep the faces deps up to date and still use a managed
dependency without having to explicitly state which version we're using in the
parent.
> Release has dependencies on an older release
> --------------------------------------------
>
> Key: SEAM-115
> URL: https://issues.jboss.org/browse/SEAM-115
> Project: Seam 3 Distribution
> Issue Type: Bug
> Affects Versions: 3.1.0.Beta4
> Reporter: Ondrej Skutka
> Assignee: Shane Bryzak
> Priority: Blocker
> Fix For: 3.1.0.CR1
>
>
> In Seam 3.1.0.Beta4 there are following dependencies/references
> on 3.1.0-Beta3:
> security/pom.xml
> persistence/pom.xml
> jcr/pom.xml
> on 3.1.0-Beta2:
> seam-3.1.0.Beta4-build/faces/examples/viewconfig/pom.xml
> on 3.1.0-SNAPSHOT:
> security/examples/saml-sp/pom.xml
> security/examples/saml-idp/pom.xml
> security/examples/openid-op/pom.xml
> persistence/tests/jetty-hibernate/pom.xml
> persistence/tests/jetty-openjpa/pom.xml
> persistence/tests/jbossas-hibernate/pom.xml
> faces/examples/viewaction/pom.xml
> jms/testsuite/pom.xml
> solder/examples/princess-rescue/pom.xml
> solder/examples/quiz/pom.xml
> on 3.0.0-SNAPSHOT:
> jms/modules/activemq/pom.xml
> jms/modules/hornetq/pom.xml
> jms/modules/openmq/pom.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
