October 2015 - jbosstools-dev - Jboss List Archives

Mechanism for deciding which archetype will be used for target runtime.

by Radim Hopp

Hi, I guess, that the main mechanism for deciding which archetype will be used for which server runtime is stacks.yaml, but what about runtimes, which are not in stacks.yaml yet? For example now, when I try to create EAR project with target runtime EAP7 (EAP7 is not yet in stacks.yaml), it creates org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final (archetype for JBossAS 7) and this doesn't seem right. Another example: EAR project with target runtime WFLY9 -> rg.wildfly.archetype:wildfly-javaee7-webapp-ear-archetype:8.2.0.Final. This looks pretty ok, as this is WFLY8.2 archetype and WFLY9 archetypes are not released yet. Radim

11 years

3
3
0 / 0

Green light for using Java 8 as minimal Execution Environment Master

by Denis Golovin

After Max shared his interpretation of Eclipse adoption and impact of requiring Java 8 for our Mars release we agreed there is no way back and master branch can now use new Java 8 features (see this link http://www.oracle.com/technetwork/java/javase/8-whats-new-2157071.html for details). Openshift is already using it and Eclipse Neon release is going to require Java 8 as well. Just do not forget to change minimal EE to JavaSE-1.8 for bundles that use Java 8 specific features. Jenkins projects are already using Java 8 to build JBossTools and JBDS projects, so there should be no problems with nightly builds in case you decided to go for it. Denis -- CONFIDENTIALITY NOTICE: This email and files attached to it are confidential. If you are not the intended recipient you are hereby notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.

11 years

2
1
0 / 0

Unable to deliver your item, #00000228696

by FedEx International Ground

Dear Customer, Your parcel has arrived at October 05. Courier was unable to deliver the parcel to you. Please, open email attachment to print shipment label. Yours trully, Freddie Barrett, Sr. Operation Manager.

11 years

1
0
0 / 0

New devdoc component added to JBIDE JIRA

by Nick Boldt

FYI, I've added a new component to JBIDE JIRA: devdoc. This is because having everything in "build" isn't always accurate. Hopefully this will also encourage me, Mickael, Paul, Max, Alexey, Denis, etc. to write & update more developer documentation so our process documents stay current, even as they're evolving & improving. https://issues.jboss.org/browse/JBIDE/component/12322530/?selectedTab=com... I haven't created a matching component in JBDS yet, since most devdoc is in https://github.com/jbosstools/jbosstools-devdoc - we only use https://github.com/jbdevstudio/jbdevstudio-devdoc for the release guide, which other than some internal server details could potentially be moved to the JBT side of the house. Comments, feedback, brickbats & new issues under this component welcome. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years

3
6
0 / 0

Please clean up your .Final / .GA issues!

by Nick Boldt

There are 4 remaining issues for JBIDE 4.3.0.Final: https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolu... * openshift doc, * website (docker & features page), * devdoc There are 14 remaining issues for JBDS 9.0.0.GA: * 8 of these are Epics, * 5 are screencasts, * 1 is for doc (Central Zip) https://issues.jboss.org/issues/?jql=project%20%3D%20JBDS%20AND%20resolut... A note about Epics: if you Epic continues after 9.0.0.GA, please set its fixversion to 9.1 or 10 as appropriate. If it's done, please resolve it. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years

1
0
0 / 0

Re: [jbosstools-dev] Selling models, See details / Account Manager/grgg2b/与您共享了相册。

by RE:Selling models, See details / Account Manager/grgg2b/

Dear Sir/Madam I know you from your great website, and glad to introduce our Child gps tracker bracelet Anti lost smart watch with SOS function, GPS+LBS, ISO /Android APP tracking, two-way communication for child/kids/baby (JM90) Child gps tracker bracelet descriptions: 1. GPS+ Base Station Dual Mode Positioning 2. SOS 3. Electric Fence 4. Anti-dropoff Alarm 5. Low Battery Alarm 6. History-trace checking 7. Two-way Communication 8. Support IE&app Real-time tracking 9. App Support IOS&Android 10. Interval of sending GPS data,There are three modes available 11. Monitoring Call 12. Watch Message Hope to hear from you soon. Best Regards China,guangdong Jim https://picasaweb.google.com/lh/sredir?uname=103953622645706953788&target...

11 years

1
0
0 / 0

The list of uninstallable connectors at the top of Central catalog sucks

by Mickael Istria

Hi all, While I'm testing staged JBT 4.3.0.CR2a, I noticed that a user facing Central will see a catalog with a list of items that they cannot select, with no widget, nothing. Click "Select All" doesn't produce an obvious feedback so user isn't aware of the impact of "Select All". It takes at least a few seconds to me, who developed most of the support for those uninstallable entries in Central catalog, to think about scrolling down to see usable content. I believe it's going to be much worse for new users, or for those who don't look at software page often. Those entries hide some parts of JBoss Tools with real added-value (Hybrid Tools, OpenShift v3...). Those useless uninstallable connectors are hiding the useful content, and unless one already knows or is curious enough to find installable connectors, it just make this install page seem useless. IMO, it's worse to have this poor UX in our product than to have some occasional questions on the user forums. My immediate recommendation would be: * Either to drop all those JBT-IS "not yet available" connector and face user questions on forums, or * instead of a dozen of "not yet available" entries hiding the installable one, we should have a single "JBoss Tools integration Stack" entry telling that the content are not available yet. On a longer-term approach, there are now way too many things in Central, either we should make it simpler, or fully revise it to have a more structured browser, which will ultimately look either like MarketPlace Client or the regular p2 install wizard with a tree (and some additional columns and some icons since it's the only real difference between central catalogs and a p2 site) 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

5
13
0 / 0

Changes between JBDS 9.0.0.CR2 B116 and B124 (respin-b)

by Martin Malina

Hi Mickael, I am trying to compare the two builds of JBDS to see what changed. And I have two questions. 1. In many third party plugins, there is a change where in one build there are ECLIPSE_.SF and ECLIPSE_.RSA files, but in the newer build I can see ECLIPSEF.SF and ECLIPSEF.RSA . You can see that "_" in the file name was changed to "F". I guess this shouldn't be anything to worry about, but do you have any idea what it is about? 2. I tried to install everything from Central in JBDS 9.0.0.CR2 B116 and got this error: Cannot complete the install because of a conflicting dependency. Software being installed: JBoss OpenShift 3 Tools 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.feature.feature.group 3.0.0.CR1-v20150911-0237-B995) Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.package 9.0.0.GA-v20150925-1252-B116) Only one of the following can be installed at once: OpenShift Common UI 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.common.ui 3.0.0.CR1-v20150911-0237-B995) OpenShift Common UI 3.0.0.Final-v20150924-2333-B49 (org.jboss.tools.openshift.common.ui 3.0.0.Final-v20150924-2333-B49) Cannot satisfy dependency: From: JBoss Developer Studio (Core Features) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.feature.feature.group 9.0.0.GA-v20150925-1252-B116) To: org.jboss.tools.openshift.express.feature.feature.group [3.0.0.Final-v20150924-2333-B49] Cannot satisfy dependency: From: JBoss Developer Studio (Branded Product) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.package 9.0.0.GA-v20150925-1252-B116) To: com.jboss.devstudio.core.feature.feature.group [9.0.0.GA-v20150925-1252-B116] Cannot satisfy dependency: From: JBoss OpenShift 2 Tools 3.0.0.Final-v20150924-2333-B49 (org.jboss.tools.openshift.express.feature.feature.group 3.0.0.Final-v20150924-2333-B49) To: org.jboss.tools.openshift.common.ui [3.0.0.Final-v20150924-2333-B49] Cannot satisfy dependency: From: JBoss OpenShift 3 Tools 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.feature.feature.group 3.0.0.CR1-v20150911-0237-B995) To: org.jboss.tools.openshift.common.ui [3.0.0.CR1-v20150911-0237-B995] So it seems that central offers me OpenShift 3 tools version CR1 and not Final, perhaps it's a bad configuration in the property file online? Maybe that's because the file was updated to work with the respins, but it should still work with the older builds as well, no? Thanks, Martin -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265

11 years

3
3
0 / 0

JBoss Tools Core 4.3.0.CR2b bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/mars/staging/updates/ New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... -- Additional update sites: * http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.CR2b/ * http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0... Target platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... Discovery sites: * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr... * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... Build folders (for build logs & update site zips): * http://download.jboss.org/jbosstools/mars/staging/builds/ -- Changes prompting this respin-b are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-b%22%29%2... To compare the upcoming version of Central (4.3.0.CR2b) against an older version, add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.CR2b/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR2b/ -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR2b/jbosstools-earlyaccess.properties -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years

1
0
0 / 0

Problems with item delivery, n.000588719

by FedEx 2Day A.M.

Dear Customer, Courier was unable to deliver the parcel to you. Please, download Delivery Label attached to this email. Yours sincerely, Pedro Stanley, Sr. Support Manager.

11 years

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 October 2015