[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10312:
----------------------------------------
I updated target-platform pom to have GAV changing on groups only (groups contain for
instance jbosstools-JunoSR1), and artifactId always being on of
multiple/unified/jenkins/local. This make things much more homogeneous.
I also updated parent pom to use this new convention. I introduced a property to change
target-platform, currently it's set to jbosstools-JunoSR1.
I'm wondering whether we should not use 2 properties to select a TP (one for the
group, the other for the kind), and keep only a single target profile, activated by
default.
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
Affects Versions: 4.0.0.Alpha2
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.0.0.Beta1
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
For more information on JIRA, see:
http://www.atlassian.com/software/jira