September 2013 - jbosstools-dev - Jboss List Archives

JBT 4.1.1.Alpha1 weekend spin blocked by minor feature versioning problems in Server/archives and Webservices

by Nick Boldt

Aerogear is now happy, but two other projects need some minor tweaks: Server/archives: https://issues.jboss.org/browse/JBIDE-15312 Webservices: https://issues.jboss.org/browse/JBIDE-15451 In both cases I can build from my own fork if necessary, but I'd prefer to build from the jbosstools fork. Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 10 months

2
2
0 / 0

ACTION: codefreeze for 4.1.1.Alpha1

by Max Rydahl Andersen

Hi all, Today is branch/codefreeze day as planned for jbosstools-4.1.1.Alpha1 [1]. Special note: A. This only involves projects that are included in JBoss Tools Core/Developer Studio, it is *not* related to things that are part of JBoss Tools Integration Stack (i.e. bpel, esb, jbpm3, etc.) B. This is an alpha, mainly to pick up Kepler SR1 fixes and already done bugfixes/features. There is no respins or QE planned for this besides "does it install" test. By request jiras for each component have been created too: see https://issues.jboss.org/browse/JBIDE-15437 and subtasks. These jiras contains similar but less details as the instructions below: 0) Make sure your component(s) has no remaining jiras for 4.1.1.Alpha1 in jira. 1) Make sure you component(s) version number has changed micro version if it had changes since 4.1.0 was released! You can use this to change it for a subtree: mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<component-version>-SNAPSHOT 2) Make sure your component uses 4.1.1.Alpha1-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.1.Alpha1-SNAPSHOT</version> </parent> 3) Make sure your component builds and passes its tests when run locally. $ mvn clean verify -Dtpc.version=4.31.0.Alpha1 4) Make a branch for the Alpha1 builds to use. This would be made on jbosstools-4.1.x, thus the steps would be something like: $ git checkout jbosstools-4.1.x $ git pull origin jbosstools-4.1.x $ git checkout -b jbosstools-4.1.1.Alpha1x $ git push origin jbosstools-4.1.1.Alpha1x 5) Resolve the jira related to branching for your component or comment on it why it can not be done. Thank you! [1] https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... -- /max

12 years, 10 months

4
3
0 / 0

JBT 4.1.1.Alpha1 weekend spin blocked by minor bug in Aerogear plugin

by Nick Boldt

Found a problem today caused by WTP upversioning one of their plugins from 1.1.202 to 1.3 in Kepler SR1 [1]. Here's the JIRA: https://issues.jboss.org/browse/JBIDE-15466 Can someone apply the PRs attached to that JIRA so that we can continue to build JBT 4.1.1 this weekend? Once applied, please kick this job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Hopefully there won't be any other issues like this one blocking us getting a build to QE for Monday morning. [1] http://download.eclipse.org/webtools/downloads/drops/R3.5.1/M-3.5.1-20130... Thanks in advance, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 10 months

3
4
0 / 0

Paper cup, Drinking straws, fork, Knife and Other cutlery Supply shared an album with you.

by Paper cup, Drinking straws, fork, Knife and Other cutlery Supply

Dear Manager: We are a company focused on food package. and What we do is Just Helping you to save your cost. Now we can supply : 1. Single wall paper cup. Double PE .Hot Paper cups. Double Wall paper cups. Cold Drinking cups, Ripple Wall cups. Paper box. 2. Drinking straws , Flexible straws. Straight straws. 3. Plastic cups. PET cold cups 4. Plastic spoon. fork, Knife and Other cutlery. We know that buiness include: Quality. Price. Delivery time. Payment Terms. And Service. We welcome you to do customized cups and any enquiries. samples for free. Best Regards Jeff https://picasaweb.google.com/lh/sredir?uname=104731093088594747265&target...

12 years, 10 months

1
0
0 / 0

ACTION: codefreeze for JBT 4.1.1.Alpha1 / JBDS 7.1.0.Alpha1 is 5.9

by Max Rydahl Andersen

Reminder: Codefreeze for update to JBT is 5.9 (thursday next week). Please make sure you have jiras updated to 4.1.1.Alpha1 and have the pushes peerreviewed (we have to careful with not changing/breaking API's etc.) I noticed a few that have the jira set to 4.1.1.Final or 4.1.x which means they aren't showing up when reviewing. And please remember to bump the .z number in <version> of your component pom.xml if you have changes! Thanks, /max

12 years, 10 months

3
3
0 / 0

Release of Target Platforms 4.31.0.Alpha1

by Mickael Istria

|JBoss Tools Target Platform 4.31.0.Alpha1 has been released. Changes ======= * Kepler SR1 RC1/RC2 (release candidate for Kepler SR1) Usage ===== Target Platforms|||4.31.0.Alpha1| is what JBoss Tools 4.1.1.Alpha1 will use. All jobs in jenkins for *branch* have been updated to use TP 4.31.0.Alpha1. Download ======== Zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... p2 site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... Testing/Development =================== You can try it out and use it directly like this: $ mvn clean verify -Dtpc.version=4.31.0.Alpha1 If you want to build it locally to get a TP with source bundles included, do this: $ git clone https://github.com/jbosstools/jbosstools-target-platforms.git $ cd jbosstools-target-platforms $ git co 4.31.0.Alpha1 $ mvn clean verify -Dmirror-target-to-repo.includeSources=true| -- 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, 10 months

1
1
0 / 0

Problem with component version on branch 4.1.x

by Xavier Coulon

Hello, [Just sharing the story that happened to me this morning] While talking with Max, Rob and André, we realized that the current Livereload version on branch 4.1.x was '1.1.0-SNAPSHOT' while it should have been '1.0.1-SNAPSHOT'. The reason for this is that I applied the same version bump on 'master' and 'jbosstools-4.1.x' branches. This means that both branches were running the same version. Which is wrong :-/ Pushing down the version from 1.1.0 to 1.0.1 on branch 4.1.x was not an option, so we decided that the best solution was to stick to 1.1.0-SNAPSHOT on the 4.1.x branch and bump master to 1.2.0-SNAPSHOT. Max wrote a blog article in which he shared the magic mvn command to run to make the version bump is all pom.xml, feature.xml and MANIFEST.MF files at once. In my case, I just ran: mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.0-SNAPSHOT (and then mvn clean verify) So this should keep things clear in the sense that versions of the Livereload component in JBT 4.1.1 and in JBT 4.2.0 won't be the same, even though they don't follow the initial plan :-/ Best regards, /Xavier

12 years, 10 months

3
6
0 / 0

Upcoming release of Target Platforms 4.31.0.Alpha1

by Mickael Istria

Hi all, This mail is to announce you our plan to Target Platform 4.31.0.Alpha1, based on Kepler SR1 RC1/2. This version should be used in order to build JBoss Tools 4.1.1, for which code-freeze is on Thursday. Before the release, we'd like you to test it for you component using the following command: $ mvn clean verify -DTARGET_PLATFORM_VERSION=4.31.0.Alpha1-SNAPSHOT on branch jbosstools-4.1.x Can't wait for your feedback! xx -- 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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev September 2013