Beta3 Respin-a status #2: Base, Server, WS, Central, Openshift, VPE, JavaEE, JST, Forge, Hibernate, Discovery are being rebuilt this weekend
by Nick Boldt
To avoid unnecessary rebuilds between Beta3 and its respin(s) (and make
it easier to diff the changes between builds), I have disabled all jobs
until we need them.
According to this query [1] the only jobs that need to be enabled are:
* Base
* Server
* Webservices
* Central
* VPE
* Openshift
* JavaEE
Additionally, these jobs have been re-enabled to collect &/or verify the
above changes, or to automatically fire should any of the 9 unresolved
JIRAs [1] be fixed before Sunday night:
* JST
* Forge
* Hibernate
* Central Discovery
* JBoss Tools composite install test
* JBoss Tools aggregate update sites (4 jobs)
* JBDS installer
* JBDS versionwatch
* p2 director install test
* install grinder install test
The following jobs are *STILL DISABLED*. If you require a fresh build to
be included in respin-a, please make sure you re-enable your job & kick
it off yourself.
* Aerogear
* BIRT
* Browsersim
* Freemarker
* Livereload
* Portlet
If you push in a fix for your Beta3x branch, please remember to enable
and kick your job. This will guarantee that your code change will be
built and aggregated into JBT & JBDS correctly.
[1]
https://issues.jboss.org/issues/?jql=project%20in%20%28JBIDE%2C%20JBDS%29...
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12 years
Nice AngularJS story
by Fred Bricon
Hi,
my Twitter TL got me to watch this Netbeans demo of building a web app
with JAX-RS backend + AngularJS front-end :
https://www.youtube.com/watch?v=2B3qL7XtKnE
I wonder how our tooling fares compared to this demo. My guts tells me
(take that with a grain of salt) that :
* for the back-end, we could use reverse engineering with Forge 2,
although I don't really know its level of maturity
* we have nothing similar to the CrossOriginResourceSharingFilter (seen
at 2'14")
* we have no equivalent for seeding a stock angularjs project, AFAIK
(unless F2 brings someting here too, idk). We could prolly create a
Maven archetype containing the same thing though.
* overall their angularjs tooling felt underwhelming. angularjs-eclipse
probably brings a stronger UX, with its navigation capabilities and its
inference engine
WDYT?
I count on Burr, to come up with a demo showcasing a similar story with
our stuff :-)
Fred
12 years
Beta3 Respin-a status: Base, Server, WS, Central, and Discovery are being rebuilt
by Nick Boldt
To avoid unnecessary rebuilds between Beta3 and its respin(s) (and make
it easier to diff the changes between builds), I have disabled all jobs
until we need them.
According to this query [1] the only jobs that need to be enabled are:
* Base
* Server
* Webservices
* Central
Additionally, these jobs have been re-enabled to collect &/or verify the
above changes:
* Central Discovery
* JBoss Tools composite install test
* JBoss Tools aggregate update sites (4 jobs)
* JBDS installer
* JBDS versionwatch
* p2 director install test
* install grinder install test
If you push in a fix for your Beta3x branch, please either let me know
(so I can enable and kick your job), or do so yourself. This will
guarantee that your code change will be built and aggregated into JBT &
JBDS correctly.
[1]
https://issues.jboss.org/issues/?jql=project%20in%20%28JBIDE%2C%20JBDS%29...
Thanks,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12 years
Target Platform 4.40.0.Beta4 for JBoss Tools 4.2.0.Beta3 has been released
by Mickael Istria
Target Platform 4.40.0.Beta4 for JBoss Tools 4.2.0.Beta3 has been released
Changes
=======
Here is the list of changes since 4.40.0.Beta3 release: https://issues.jboss.org/issues/?jql=project%3DJBIDE%20and%20component%3D...
Usage
=====
Target platform 4.40.0.Beta4 is what JBoss Tools 4.2.0.Beta3 should have used, and what it will use for next builds and respins.
All Jenkins jobs for branch jbosstools-4.2.0.Beta3x and parent pom 4.2.0.Beta3-SNAPSHOT have been updated to use target platform 4.40.0.Beta4.
The following p2 repositories *will be modified* to point to this new target platform once JBoss Tools 4.2.0.Beta3 is released:
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/
* http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/
Until then, you can access the target platform at the URLs below.
Download
========
Update site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
Update site zip: http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar...
Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta4
Testing/Development
===================
If your root pom correctly specifies the latest parent pom version as 4.2.0.Beta3-SNAPSHOT, you need only this:
$ mvn clean verify
If you're using a different parent pom, use this:
$ mvn clean verify -Dtpc.version=${TARGET_PLATFORM_VERSION}
For usage and help (using in IDE, building a mirror locally, using a zip), see: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
What's next?
============
jbosstools-target-platforms project branch 4.40.x has been prepared for potential upgrades, and its version is now 4.40.0.CR1-SNAPSHOT. We can at least expect for this version:
* Adoption of Eclipse THyM
* Update or Tern plugins
* Shall you need anything else, please follow those instructions to request a change ASAP: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
Deadline for changes in target platform 4.40.0.Beta4-SNAPSHOT is**Monday, August 25th**
All Jenkins jobs for *master* and parent pom 4.2.0.CR1-SNAPSHOT have been updated to use target platform 4.40.0.CR1-SNAPSHOT
--
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>
12 years
