| Summary: | Investigate the possibility of using a brms maven profile to generate brms distribution for SOA-P release. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jervis Liu <jliu> |
| Component: | Build Process | Assignee: | Jervis Liu <jliu> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 CR1 | CC: | mproctor |
| Target Milestone: | --- | ||
| Target Release: | 5.0.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/BRMS-29 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-03-10 00:54:55 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jervis Liu
2009-01-09 15:27:32 UTC
Security: Removed: Public Moved here because it's really a BRMS issue. Rolling back change on drools-eclipse/drools-eclipse-build/pom.xml because it breaks normal eclipse build. Also, it does not seem to make sense to have soa be the default profile and have the normal build define as a special profile with custom build. Should also try to avoid duplication in the pom.xml. This should be done. Need a double-check. |