[URGENT] Release Candidate Target Platform 4.30.5.Alpha5-SNAPSHOT
by Mickael Istria
Hi all,
Because of various issues we've met with the Kepler M7 mirrors we've set
up, we need to fix target platform and to release a new one, that we'll
use in order to build JBT 4.1.0.Beta1 / JBDS 7.0.0.Beta1.
This target-platform is 4.30.5.Alpha5-SNAPSHOT, it's available on Nexus,
and Hudson is already using it.
I'd like you to try to build your branched component locally and check
whether everything is fine. To do so, please try "mvn clean verify
-Dtpc.version=4.30.5.Alpha".
Also, I'd like you to have a look at the CI jobs for your component and
to ring a bell if something seems wrong because of this new target-platform.
This is an urgent message as this target-platform is currently blocking
the continuation of Beta1 release.
Cheers
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
11 years, 9 months
ACTION REQUIRED: Beta1 branch/codefreeze today - steps inside
by Max Rydahl Andersen
Hi all,
Today is branch/codefreeze day as planned [1].
Special note:
Newcomers to this came is jbosstools-arquillian and jbosstools-aerogear - Snjezan/Gorkem, speak up if any issues doing this.
A quick reminder what that means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta1 in jira.
If anything left over (besides New and noteworthy writing issues) that would
be done in respins which we wish to keep to a bare minimum, hopefully
completely avoid.
1) Make sure your component uses 4.1.0.Beta1-SNAPSHOT as the version for jboss tools parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta1-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the beta1 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta1x
$ git push origin jbosstools-4.1.0.Beta1x
4) Respond to this mail before end of today with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze today because of
<jira issues> must be done first"
Thank you!
[1] https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
11 years, 9 months
Roofing thatch
by Fiberglass; FRP
Waterproof, Fireproof Synthetic Thatch,
professional manufactory
Keba GM Group Co., Ltd, the biggest synthetic thatch supplier in china.
Keba synthetic thatch can be made in different kinds Of thatch leaves which can be similar with nature thatch.
All the synthetic thatch tile color & shape are on our website,
Welcome to visit our website: www.kebagm.com; www.kebajt.com to get more details.
Reply this email can get best price and FREE samples.
Best Regards!
Porter Guo
CHINA KEBAGM GROUP CO.,LTD
Beihai Park.,No 1 Long Jing Rd,Bao an,Shenzhen China.
www.kebagm.com
www.chinabeihai.com
Email: sales(a)chinabeihai.com
11 years, 9 months
Missing cordovasim feature on VPE site
by Mickael Istria
Hi all,
As we are integrating all new features into JBoss Tools aggregation at
the very last time, we notice some issues very late.
One of these issue is that the new CordovaSim feature is not published
on VPE site, so it cannot be aggregated. So in order to make it easier
to have a good code freeze, it would be nice if someone could merge this
PR soon: https://github.com/jbosstools/jbosstools-vpe/pull/78
In general, whenever you create a new feature that is meant to be
distributed as part of JBoss Tools, make sure it's published on your
component so it can be consumed. This can be achieved by simply running
a "mvn clean verify" in your component, and checking the output of
site/target/repository. Then make sure build crew is aware that this
features need to be aggregated, and feel free to harass Nick or I until
the feature is actually integrated. It will be less annoying than fixing
it in the few hours before a code freeze. If you understand enough of
the aggregation process, feel free to contribute pull request to this
file:
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
But in any case, do it as early as possible!
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
11 years, 9 months
