]
Max Rydahl Andersen commented on JBIDE-20025:
---------------------------------------------
nick - are you volunteering to monitor portlet for when builds makes sense ?
Why is it a problem to build master when the code changes no matter if included somewhere
or not ?
new commits in master branch == portlet must be upversioned
-----------------------------------------------------------
Key: JBIDE-20025
URL:
https://issues.jboss.org/browse/JBIDE-20025
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: portal-gatein
Affects Versions: 4.3.0.Beta1
Reporter: Nick Boldt
Assignee: Snjezana Peco
Fix For: 4.3.0.Beta2
[~dgolovin] reports that whenever he builds Portlet from master branch, it fails because
it's got the same plugin/feature versions as the previous baseline release, but there
are new commits / SHAs since that baseline.
So, portlet should be upversioned so that the version validation test won't fail.
cc: [~mickael_istria] [~maxandersen] [~snjeza]
(The reason this happened is that people committed changes to a branch of code which is
no longer being developed. Since not being developed, no one upversioned the code along
with those commits.)
The alternative solution to this issue is that @dgolovin should simply stop building
portlet locally. We don't build it in Jenkins for the same reason. :D