March 2013 - jbosstools-dev - Jboss List Archives

Release of Target-Platfroms 4.30.5.Alpha + New process and documentation

by Mickael Istria

Hi all, Following our intent to move to released stuff, as described in https://issues.jboss.org/browse/JBIDE-13232?focusedCommentId=12757287&pag... and https://issues.jboss.org/browse/JBIDE-13408 , we'll make releases for target-platforms that are used in order to build milestones and releases. We created a new documentation on how to use target-platforms, which will be effective for 4.1.0.Alpha2 and further. You can already have a look at it here: https://github.com/jbosstools/jbosstools-target-platforms/wiki As a first shot of this release process, I'll release the 4.30.5.Alpha now, which was used in order to build JBT 4.1.0.Alpha1. 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>

12 years, 10 months

3
3
0 / 0

Хорошего дня

by Tatiana Gurianova

Приветствуем. Публикуете ли Вы сейчас модульную рекламу на Вашем интернет-ресурсе mailinglistarchive.com? С кем нужно обсудить этот вопрос? Мое почтение, Куликова Оксана Менеджер отдела продаж

12 years, 10 months

1
0
0 / 0

Juno SR2 target platform changing to include m2e 1.3 and m2e-wtp 0.17

by Nick Boldt

New target platform coming tonight. Ref: https://issues.jboss.org/browse/JBIDE-13603 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 10 months

1
1
0 / 0

Migrating API

by Rob Stryker

Hey all: I'd like to take this moment to remind everyone that changing interfaces is not allowed if the interface is public and non-internal. Interfaces cannot change at all and require very careful migration. Other tasks which are not allowed include changing the return type of an API class in ANY fashion. I've also been guilty of this recently, and caused a breakage in the soa product, but recent patch submissions have done the same. These rules are a lot more critical in LOW level modules, such as base/*, server/*, etc, and less so for projects like Central, which are at the top of the stack and have very few consumers. But, the rules still must be enforced regardless and we should always try to keep api stable. Migrating public interfaces is a bit of a harder task, and anyone attempting to do it should probably ask for advice on how to maintain api compatability. For stable components like base/common, it must be done in the safest way possible. This usually involves creating a second interface which extends the first, and creating new methods to use the more specific interface. In the future, when designing an API, if you think you might ever need any return value, even if you don't need one now, it is a good idea to return Object. While I don't think this is a beautiful solution, the fact is any subclass can return a more specific value. If you simply declare it as a 'void' return value, this can never be changed at all in any way. Any questions on api migration, do not delay to ask the list :) - Rob Stryker

12 years, 10 months

3
5
0 / 0

JBoss Tools Core 4.1.0.Alpha1c bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Alpha1c.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Alpha1c.web... Builds: http://download.jboss.org/jbosstools/builds/development/4.1.0.Alpha1c.core/ http://download.jboss.org/jbosstools/builds/development/4.1.0.Alpha1c.web... JBoss Central: To test this version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Alpha1c.core/jbosstools-directory.xml New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... Changes prompting this respin-c are: https://issues.jboss.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQu... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 10 months

1
0
0 / 0

Cannot resolve dependencies using aggregate update site

by Andrej Podhradsky

Hi folks, I'm not able to resolve BPEL dependencies when I define the following aggregated update site http://download.jboss.org/jbosstools/updates/integration/juno/integration... but when I define the particular BPEL site http://download.jboss.org/jbosstools/updates/integration/juno/integration... then everything is fine. Could you explain me where's the problem? Is the tycho problem or is something wrong with that update site? Note that I'm able to install BPEL from eclipse using the mentioned aggregated site. Best Regards -- Andrej Podhradsky Quality Assurance Associate JBoss SOA Platform IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno

12 years, 10 months

4
9
0 / 0

JBoss Tools Core 4.0.1.CR1 bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-4.0.1.CR1.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.0.1.CR1.webtools/ Builds: http://download.jboss.org/jbosstools/builds/development/4.0.1.CR1.core/20... http://download.jboss.org/jbosstools/builds/development/4.0.1.CR1.webtool... JBoss Central: To test this version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/JBossTools-4.0.1.CR1.core/jbosstools-directory.xml New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 10 months

1
0
0 / 0

Missing 4.0.0.Final tag in git

by Pavol Srna

Hi Nick, I don't see 4.0.0.Final tag in JBT git repos. Why is that? I'm asking because there is already 4.0.1 version in 4.0.x branch in jbosstools-build repo. Thanks for clarifying. -Pavol -- Pavol Srna QA Engineer, JBDS Phone: +420 532 294 352 irc: psrna Red Hat Czech Purkynova 99, 612 00 Brno, Czech Republic

12 years, 10 months

2
1
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 March 2013