[
http://jira.jboss.com/jira/browse/JBPM-1053?page=comments#action_12379547 ]
Tom Baeyens commented on JBPM-1053:
-----------------------------------
Christopher, please explain your requirements a bit more concrete.
This is what we currently have: a cvs structure that performs a full build with defaults
in cvs. The idea is that during continious integration, the cvs sources are fetched as is
so that the complete sources can be cleaned and fetched again. So any specific build
configurations by default have to go outside the cvs sources structure. That is why I
don't get your request. You don't *have* to have a custom build.properties file.
It's only necessary when you want to override default properties. Maybe the defaults
that we have are not as you want. In that case, be more specific.
jBPM Build Files Search for build.properties in
${user.home}/jbpm/build.properties
----------------------------------------------------------------------------------
Key: JBPM-1053
URL:
http://jira.jboss.com/jira/browse/JBPM-1053
Project: JBoss jBPM
Issue Type: Release
Reporter: Christopher Brock
Assigned To: Tom Baeyens
This has become a pretty serious problem in our attempts to create automated build and
patches for SOA. It creates a mess by forcing us to have our scripts create directories
outside the build structure.
It would be helpful if the either a delegate configuration file was introduced to allow
us to override this, or better yet, if jBPM simply defaulted to a sensible configuration
file inside it's source structure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira