[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10312:
------------------------------------
So when you say "minimal" you don't mean minimal size / fewest IUs, but
*oldest compatible version level*?
eg., we COULD be building against Indigo SR0 instead of SR1 or SR2, but we tend to build
against the latest/greatest available in order to stay current w/ the latest upstream
releases and be able to feedback to upstream / get fixes in upstream.
Would simply building against an older version of the TP be sufficient? For example...
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/e...
http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.in...
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: Critical
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