October 2013 - jbosstools-dev - Jboss List Archives

Installing JBT 4.1.1.x builds on JBDS 7.0.1

by Yahor Radtsevich

Hi all, I am wondering how JBDS users can install JBT 4.1.1.x builds. For instance, I want to install CordovaSim from JBT 4.1.1.Beta1 on my JBDS 7.0.1. The problem is that CordovaSim requires BrowserSim to be updated from 3.5.0.Final to 3.5.1.Beta1, which is not possible due to "a conflicting dependency" error (http://pastebin.com/sAbAFEMu ). Is there a workaround for this? -- Best Regards, Yahor Radtsevich

11 years, 1 month

3
4
0 / 0

Release Target Platforms 4.31.1.Alpha1

by Mickael Istria

|JBoss Tools Target Platform 4.31.1.Alpha1 has been released. Changes ======= * Use of Atlassian plugins 3.2.2 Usage ===== 4.31.1.Alpha1 is what JBoss Tools 4.1.1.Beta1 respins will use. All CI jobs in jenkins for *branch* have been updated to use TP 4.31.1.Alpha1. Parent pom 4.1.1.Beta1 for *branch* has been updated to use TP 4.31.1.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.1.Alpha1 For advanced usage and help (using in IDE, building a mirror locally, using a zip...), plese read https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... What's next? ============ Branch 4.31.x for target platform has been prepared for potential upgrades, and it's version is now 4.31.1.Alpha2-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>

11 years, 1 month

1
0
0 / 0

JBoss Tools Core 4.1.1.Beta1 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. Target Platforms: Add one of these URLs to your Eclipse before attempting to install JBoss Tools, in order to resolve all dependencies. Both should work equally well. http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Beta1.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Beta1.coret... http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Beta1.webto... Builds: http://download.jboss.org/jbosstools/builds/development/4.1.1.Beta1.core/... http://download.jboss.org/jbosstools/builds/development/4.1.1.Beta1.coret... http://download.jboss.org/jbosstools/builds/development/4.1.1.Beta1.webto... 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/discovery/development/4.1.1.Beta1/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.1.1.Beta1/ -- New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... and http://docs.jboss.org/tools/whatsnew/ -- Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

1
0
0 / 0

Changes coming to JBT, JBDS and Central Target Platforms

by Nick Boldt

Three changes have been pushed to the Target Platforms today, as they were approved by QE &/or PM for inclusion. 1. Atlassian 3.2.1 -> 3.2.2 Affected Target Platforms: JBT, JBDS, Central https://issues.jboss.org/browse/JBDS-2774 2. PMD 4.0.0 -> 4.0.1 Affected Target Platforms: Central https://issues.jboss.org/browse/JBIDE-15353 3. Mylyn Builds Connector: Hudson/Jenkins (org.eclipse.mylyn.hudson.feature) 1.1.1 Affected Target Platforms: Central https://issues.jboss.org/browse/JBDS-2752, JBDS-2724 --- For future changes & change summary, see: https://issues.jboss.org/browse/JBDS-2710 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

1
0
0 / 0

Locus 1.1.0 is released

by Mickael Istria

Hi all, To all Locus users: Locus 1.1.0 has been released, and its URL is https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... . Please use this URL instead of the previous ones. Source has been tagged "1.1.0" and is available at https://github.com/jbosstools/jbosstools-locus/tree/1.1.0 Master was updated to start a new stream 1.2.0-SNAPSHOT, snapshots will be available at https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... -- 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, 1 month

1
0
0 / 0

ASTools Refactor (as always), advice required from consumers!

by Rob Stryker

Hi All: OPENSHIFT, TEIID DESIGNER, CENTRAL, and others.... HEAR ME! I'm working on drawing out the beginning plans of a somewhat large refactor to astools, specifically to server behavior (module start / stop, deploy, server start / stop, management commands, etc). What I need from you all is a comprehensive list of how you're all interacting with astools as of now, and what things you'd LIKE to see in the future. This will be a major version bump when complete, and while I will do my best to not severely break api, I will. I know I will, because it's about time thats been done and the old cruft gets cleaned. Obviously existing servers will continue to function. That would be a critical breakage and even I won't do that, but, I would like to make all consumers of astools' migrations as easy as possible. Even though most of these changes will be to classes that should have been internal but never were, the changes will necessarily bleed into utility classes etc. I'll do my best to avoid that, but it's not always possible. The idea here is to split the server behavior into systems and subsystems, with different implementations that can be mixed and matched. How far this refactor goes depends on how you guys are using astools currently. Odds are most of the changes will be to internal stuff, but that's the problem, since astools never had properly hidden internal packages. So odds are you're all reaching in and using code all over the place. If you don't tell me what you're using now, odds are I'll break it with impunity. If you do tell me, I'll try my best to keep those classes and methods there, mark them as deprecated, provide helpful javadoc for transitioning, and, in the very end, once everyone converts, I'd clean up the cruft. But, if you dont tell me, I'll probably break you when I commit it, and it won't be my fault ;) (If we're being honest, I'll probably break you a little even if you do tell me, but that'll be my fault, not yours) The current ideas for systems is: publish, moduleController, serverState (previously pollers), startup, shutdown, etc. I'm also trying to work in the idea of extenders able to contribute their own systems or subsystems for various configurations or server types, but I'm not at that point yet. I am at the point, though, where my desired new interfaces conflict with the old poorly designed ones. Things to tell me that you depend on: 1) Internal Classes 2) CONSTANTS (IJBossToolingConstants.xyz, or others) 3) API classes 4) depending on server mode (local vs rse) 5) basically everything which could break Most string constants will not change, but their LOCATIONS might change, as many should be internal but aren't. Anyway, consider this the 'gathering requirements' phase. Let me know, or bear the consequences! - Rob Stryker I cause problems

11 years, 1 month

3
4
0 / 0

ACTION REQUIRED: JBT 4.1.1.Alpha2 / JBDS 7.1.0.Alpha2 Code Freeze + Branch

by Nick Boldt

Today is the code freeze & branch day for JBT 4.1.1.Alpha2 & JBDS 7.1.0.Alpha2, per the posted schedule [1]. This code freeze and branch day only involves projects included in JBoss Tools Core / JBoss Developer Studio, NOT the Integration Stack (i.e. bpel, esb, jbpm3, etc.) This build will be our second Alpha. There will be no planned respins - QE should only be doing simple "does it install? does it blow up?" smoke tests. JIRAs for each component have been created to make it easy to perform the steps required to prepare for code freeze and create a new branch. See JIRAs below. *IF YOUR COMPONENT HAS NOT CHANGED* since 4.1.1.Alpha1 (code freeze was Sept 5 2013), please *REJECT the JIRA* - do not close it, as that suggests that a build of your component IS required. Rejecting the JIRA tells me that I don't have to worry about respinning identical bits and wasting my time building it. It will also save users' time (and bandwidth!) upgrading to identical bits. [1] https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... JIRAs: JBDS : https://issues.jboss.org/browse/JBDS-2773 JBoss Tools : https://issues.jboss.org/browse/JBIDE-15527 Aerogear : https://issues.jboss.org/browse/JBIDE-15528 JST : https://issues.jboss.org/browse/JBIDE-15529 VPE : https://issues.jboss.org/browse/JBIDE-15530 XULRunner : https://issues.jboss.org/browse/JBIDE-15531 JBT Update Sites : https://issues.jboss.org/browse/JBIDE-15532 Central Discovery : https://issues.jboss.org/browse/JBIDE-15533 Server : https://issues.jboss.org/browse/JBIDE-15534 Hibernate : https://issues.jboss.org/browse/JBIDE-15535 Base : https://issues.jboss.org/browse/JBIDE-15536 OpenShift : https://issues.jboss.org/browse/JBIDE-15537 JavaEE : https://issues.jboss.org/browse/JBIDE-15538 Birt : https://issues.jboss.org/browse/JBIDE-15539 GWT : https://issues.jboss.org/browse/JBIDE-15540 Forge : https://issues.jboss.org/browse/JBIDE-15541 Webservices : https://issues.jboss.org/browse/JBIDE-15542 Arquillian : https://issues.jboss.org/browse/JBIDE-15543 Central : https://issues.jboss.org/browse/JBIDE-15544 Portlet : https://issues.jboss.org/browse/JBIDE-15545 Freemarker : https://issues.jboss.org/browse/JBIDE-15546 LiveReload : https://issues.jboss.org/browse/JBIDE-15547 Query: https://issues.jboss.org/browse/JBIDE-15456?jql=%28%28project%20in%20%28J... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

2
3
0 / 0

Portable charger promotion gifts与您共享了相册。

by Portable charger promotion gifts

Hello, How are u This is from a factory/manufacturer in china, which mainly manufacture portable powerbank chargers They are very good item for promotion gifts. external battery portable charger for almost mobiles, ipad,as well as most electronic devices. We provide OEM/ODM service For free, if quantity can be up to 5k pcs. 2200mAh-3.7usd/pc QUALITY A CELL 100% full capacity for inside battery,not fake capacity. Best wishes Abby Address: shangpai village ,Shiyan town,shenzhen.China https://picasaweb.google.com/lh/sredir?uname=116660998215951951295&target...

11 years, 1 month

1
0
0 / 0

org.jboss.tools.tests missing ? use latest parent and mvn -U

by Max Rydahl Andersen

Hey, If you see build errors like this: :"Unable to satisfy dependency from <your test bundle> to bundle org.jboss.tools.tests 0.0.0." then please check you are using the latest parent in 4.1.x branch: 4.1.1.Beta1-SNAPSHOT and run with mvn -U to ensure you have the latest snapshot from yesterday. After this tools.tests should be available to you again. Background: tools.tests went missing because our parent pom was referring to integration-stack tests site instead of the core tests site and the old integration-stack by error had org.jboss.tools.tests included thus when we updated the borked integrationtests to be correct it had this cascading effect of breaking the dependency. Martin and Nick found this issue yesterday and we got it fixed in the parent pom. If you see similar errors on older branches and can't use 4.1.1.Beta1 then let us know and we need to probably update the parent pom for those too if there are other builds needed from that. related jiras/PRs: JBIDE-13790, https://github.com/jbosstools/jbosstools-build/commit/ffcaead94ab989b0693... /max

11 years, 1 month

1
0
0 / 0

Reminder: JBT 4.1.1.Beta1 / JBDS 7.1.0.Beta1 Feature Complete Code Freeze & Branch is tomorrow (2013-10-17)

by Nick Boldt

Reminder: JBT 4.1.1.Beta1 and JBDS 7.1.0.Beta1 will be having its "Feature Complete" Code Freeze & Branch tomorrow, on 2013-10-17. As we did for Alpha1 and Alpha2, I will be sending task JIRAs w/ details on how to prepare and branch tonight. Unlike Alpha1 and Alpha2, Beta1 will likely involve weekly respins (using respin-a, respin-b labels in JIRA), and will be a much longer testing cycle (Oct 21-Nov 07). --- If your project *will NOT be able* to freeze & branch on Thurs Oct 17, let me know immediately! Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev October 2013