OpenShift v3 is removed from Alpha1, but still in master
by Max Rydahl Andersen
Hi,
FYI - OpenShift v3 work did not end up getting to a useful state thus
Andre and Jeff C. reverted the code in Alpha1x branch to the old v2
codebase.
I've reverted the updatesite and central changes.
master nightly builds will still have it though so now QE and others can
more easily try it out and we can get it fixed for Alpha2.
Happy Valentines,
Thanks,
/max
http://about.me/maxandersen
9 years, 11 months
New OpenShift v3 feature
by Max Rydahl Andersen
Hi,
As documented
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_...
I'm posting on behalf of Andre that we are need to add new openshift v3
feature to JBoss Tools and eventually devstudio.
This new feature (called: org.jboss.tools.openshift.feature) is what
will provide OpenShift v3 features.
The old v2 feature called org.jboss.tools.openshift.express.feature
will continue to exist and be relevant to support v2.
One tricky matter is that openshift v3 is still actively moving thus for
now we are making the V3 and V2 install separately available features in
case v3 will end up not being fully supported/completed when we go
final.
Thus I suggest that for Alpha1:
Add org.jboss.tools.openshift.feature to JBoss Tools and its openshift
central connector.
*after* Alpha1 after some feedback and stability add it to devstudio.
Central Jira for this is at
https://jira.jboss.org/jira/browse/JBIDE-19162
Thanks,
/max
http://about.me/maxandersen
9 years, 11 months
Oomph in Eclipse M5 and properties...
by Max Rydahl Andersen
Hey,
If you haven't tried Eclipse Mars M5 yet you probably haven't heard or
tried oomph yet.
oomph does a bunch of things regarding making eclipse easier to install
and configure.
One of them is managing preferences between multiple workspaces - i'm
not super fan of the UI oomph have so far, but the idea behind it is
good enough. It listens to preference changes and ask the user if a
certain preference should be applied to all your other workspaces. If
yes - it will apply them on your next workspace start.
That is all fine and well, but some of the properties just don't make
sense for users to be notified about - for example our usage tracking is
stored in preferences; not something that makes sense for oomph to care
about.
That is now fixed in M6
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=459455) after I raised
the issue.
But do please keep an eye on oomph and check if it asks for properties
you think are irrelevant or bad that we should get fixed on oomph side.
And of course - if you see other issues with oomph do open bugs on
bugs.eclipse.org so Eclipse Mars will get something better not worse ;)
thanks,
/max
http://about.me/maxandersen
9 years, 11 months
mockito now in in TP for jbosstools master
by Max Rydahl Andersen
Hi,
It probably should have happened ages ago [1] but now its there via
https://issues.jboss.org/browse/JBIDE-19110
Mockito is now available in master of jboss tools core target platform.
Meaning you can now use mocks in your tests without custom
inclusion/setup.
We do have other mocking frameworks in play, but please consider using
mockito
instead of something custom going forward.
Mind you that we are using a fork of Mockito to work around limit of
what happens when
you have multiple versions of a binary loaded in the IDE - but if you
don't have that
you shouldn't care ;)
You can read more about mockito at http://mockito.org/ or google
"eclipse mockito" to have fun with
the subtleties osgi gives you ;)
[1] I'll explain why mockito with osgi sucks over a beer :)
/max
http://about.me/maxandersen
9 years, 11 months
Suggested change for 4.50.0.Alpha1-SNAPSHOT target-platfrom: Mars M5
by Mickael Istria
Here is a proposal for a change to the JBoss Tools4.50.0.Alpha1-SNAPSHOT target platform, for JBoss Tools 4.3.0.Alpha1:
https://github.com/jbosstools/jbosstools-target-platforms/pull/125
It consists in the following changes:
* JBIDE-19174: Mars M5
p2diff reports are attached to the related JIRA(s).
Please review the above PR(s), as it will be applied ASAP.
You can use the following to build & test the target-platform locally against your component(s).
Build target-platform:
$ cd jbosstools-target-platforms
$ git fetch origin pull/125/head
$ git checkout FETCH_HEAD
$ cd jbosstools/multiple
$ mvn clean install
Try with just built target-platform:
$ cd /path/to/your/component
$ mvn clean verify -Dtpc.version=4.50.0.Alpha1-SNAPSHOT -Pmultiple.target
9 years, 11 months