[jbosstools-issues] [JBoss JIRA] (JBIDE-10312) Define a minimal target platform as opposed to the recommend one we have now for builds
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon May 28 01:44:18 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBIDE-10312:
-------------------------------
Fix Version/s: 3.4.x
(was: 3.3.0.CR1)
> Define a minimal target platform as opposed to the recommend one we have now for builds
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-10312
> URL: https://issues.jboss.org/browse/JBIDE-10312
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 3.4.x
>
>
> Seeing JBIDE-10311 made me realize that we actually could catch these by having a *minimal* target platform to either build or test against.
> The problem here is that a plugin got a plugin dependency based on the target platform - but the target platform have the latest 3.7.1 version meaning those users running 3.7.0 would have problems installing it.
> If we had a minimal target platform (.target) we could actually install/verify these issues against it.
> Not necessarily every night - but like once a week run the build or install the updatesite against the minimal target platform would
> reveal these dependency issues.
> WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list