Generate profile-specific components.properties definitions through seam-gen ---------------------------------------------------------------------------- Key: JBSEAM-3157 URL: http://jira.jboss.com/jira/browse/JBSEAM-3157 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Priority: Optional Seam-gen profiles provides a great way for Ant users to enable environment-specific configuration. It would be great to also provide the option to configure Seam components based on profile without having to edit the build (currently seam-gen is using filter tokens to swap out env-config reported at JBSEAM-3031). The approach is described here: http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-con... Essentially creation of the following in a seam-gen'd project: components-dev.properties components-test.properties components-prod.properties and using the build to pick the appropriate properties file based on the current profile. Dependendent on JBSEAM-3031.

Generate profile-specific components.properties definitions through seam-gen ---------------------------------------------------------------------------- Key: JBSEAM-3157 URL: http://jira.jboss.com/jira/browse/JBSEAM-3157 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Priority: Optional Attachments: components-dev.properties, components-prod.properties, components-test.properties, JBSEAM-3157-ear-v1.patch, JBSEAM-3157-war-v1.patch Seam-gen profiles provides a great way for Ant users to enable environment-specific configuration. It would be great to also provide the option to configure Seam components based on profile without having to edit the build (currently seam-gen is using filter tokens to swap out env-config reported at JBSEAM-3031). The approach is described here: http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-con... Essentially creation of the following in a seam-gen'd project: components-dev.properties components-test.properties components-prod.properties and using the build to pick the appropriate properties file based on the current profile. Dependendent on JBSEAM-3031.

Generate profile-specific components.properties definitions through seam-gen ---------------------------------------------------------------------------- Key: JBSEAM-3157 URL: http://jira.jboss.com/jira/browse/JBSEAM-3157 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Priority: Optional Attachments: components-dev.properties, components-prod.properties, components-test.properties, JBSEAM-3157-ear-v1.patch, JBSEAM-3157-war-v1.patch Seam-gen profiles provides a great way for Ant users to enable environment-specific configuration. It would be great to also provide the option to configure Seam components based on profile without having to edit the build (currently seam-gen is using filter tokens to swap out env-config reported at JBSEAM-3031). The approach is described here: http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-con... Essentially creation of the following in a seam-gen'd project: components-dev.properties components-test.properties components-prod.properties and using the build to pick the appropriate properties file based on the current profile. Dependendent on JBSEAM-3031.

Generate profile-specific components.properties definitions through seam-gen ---------------------------------------------------------------------------- Key: JBSEAM-3157 URL: https://jira.jboss.org/jira/browse/JBSEAM-3157 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Assignee: Jacob Orshalick Priority: Optional Fix For: 2.1.0.BETA1 Attachments: components-dev.properties, components-prod.properties, components-test.properties, JBSEAM-3157-ear-v1.patch, JBSEAM-3157-war-v1.patch Seam-gen profiles provides a great way for Ant users to enable environment-specific configuration. It would be great to also provide the option to configure Seam components based on profile without having to edit the build (currently seam-gen is using filter tokens to swap out env-config reported at JBSEAM-3031). The approach is described here: http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-con... Essentially creation of the following in a seam-gen'd project: components-dev.properties components-test.properties components-prod.properties and using the build to pick the appropriate properties file based on the current profile. Dependendent on JBSEAM-3031.

Generate profile-specific components.properties definitions through seam-gen ---------------------------------------------------------------------------- Key: JBSEAM-3157 URL: https://jira.jboss.org/jira/browse/JBSEAM-3157 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Assignee: Jacob Orshalick Priority: Optional Fix For: 2.1.0.BETA1 Attachments: components-dev.properties, components-prod.properties, components-test.properties, JBSEAM-3157-ear-v1.patch, JBSEAM-3157-war-v1.patch Seam-gen profiles provides a great way for Ant users to enable environment-specific configuration. It would be great to also provide the option to configure Seam components based on profile without having to edit the build (currently seam-gen is using filter tokens to swap out env-config reported at JBSEAM-3031). The approach is described here: http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-con... Essentially creation of the following in a seam-gen'd project: components-dev.properties components-test.properties components-prod.properties and using the build to pick the appropriate properties file based on the current profile. Dependendent on JBSEAM-3031.