[jboss-jira] [JBoss JIRA] (DROOLS-186) Enforce maven 3.0.5+ to build droolsjbpm
Geoffrey De Smet (JIRA)
jira-events at lists.jboss.org
Wed Jul 3 06:41:20 EDT 2013
[ https://issues.jboss.org/browse/DROOLS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoffrey De Smet updated DROOLS-186:
------------------------------------
Description:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.5,)</version>
</requireMavenVersion>
{code}
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
was:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.3,)</version>
</requireMavenVersion>
{code}
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
> Enforce maven 3.0.5+ to build droolsjbpm
> ----------------------------------------
>
> Key: DROOLS-186
> URL: https://issues.jboss.org/browse/DROOLS-186
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Fix For: 6.0.0.CR1
>
>
> Reasons:
> - To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
> - Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
> TODO list:
> - The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
> {code}
> <requireMavenVersion>
> <version>[3.0.5,)</version>
> </requireMavenVersion>
> {code}
> - Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
> - Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list