> ...or have a proper "minimal target" platform to build
against. Take your pick.
>
>
>
https://issues.jboss.org/browse/JBIDE-10287
>
>
> A small innocent dependency and PDE annoying default behavior of putting in the very
exact version used and suddenly you can't install plugins into SR0.
>
> Our automating tests should help catch these.
>
It does:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....
link seem to be dead,
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....
is better
so thats cool but there are a few problems here:
1) I can see the build is red - but no info about what failed.
(I found it after doing ~7 clicks to reach
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....
which is actually pretty precise)
2) how do i run this test before I commit to trunk so i can see if my changes affected
...apparently the build is using later versions since otherwise this should have failed in
build.
Thus as a minimum this build job should be one of those sent to jbosstools-dev IMO. That
would make everyone aware something is wrong in dependencies. wdyt?
Yes? this is the jira I pointed to - didn't
/max