July 2013 - jbosstools-dev - Jboss List Archives

by Paul Richardson

The second milestone release ( Alpha2 ) for Teiid Designer 8.2 is available. New in Alpha2: * Provides Teiid client drivers for each installed teiid client version, without requiring connection to a server * Improvements to the model refactoring framework (rename, delete, cut/copy) to integrate better with Eclipse * Teiid servers can be added that exist on the same host * Major refactoring of DDL importer, now supporting database extension properties * Auto generate REST WARs at deployment time to expose your VDBs as REST services and allow for REST based ad hoc queries. * Significant number of issues fixed (see the JIRA summary for details [1]) Find downloads at: http://www.jboss.org/teiiddesigner/downloads Update Site URL: http://download.jboss.org/jbosstools/updates/development/kepler/soa-tooli... [1] https://issues.jboss.org/browse/TEIIDDES/fixforversion/12321512 Teiid Designer Project Team -- Paul Richardson * p.g.richardson(a)redhat.com * pgrichardson(a)linux.com * mob: +44 (0)9780 869490

10 years, 2 months

4
5
0 / 0

Tests error during local build

by Konstantin Marmalyukov

I'm trying to build org.jboss.tools.vpe.browsersim.eclipse.test locally to reproduce its failure on Hudson. But I got an error* */[ERROR] Cannot resolve project dependencies:// //[ERROR] Software being installed: org.jboss.tools.vpe.browsersim.eclipse.test////3.5.0.qualifier// //[ERROR] Missing requirement: org.jboss.tools.vpe.browsersim.eclipse.test 3.5.0.qualifier requires 'bundle org.jboss.tools.tests 3.5.0' but it could not be found/ During local built all dependencies must be resolved by tycho and downloaded from our servers, am I right? How this problem can be fixed?

10 years, 3 months

7
14
0 / 0

Locus Repository Usage

by Rob Cernich

Hey all, Recently, the JBTIS builds were broken and after a little analysis it appears the culprit is Locus. After looking at how JBTIS is using Locus, I'm wondering if the target files for JBTIS are incorrect. Currently, the target files declare specific artifact versions, but specify the root locus repository URL. Besides the fact that the JBTIS TP is pointing to the "integration" repository for Locus, I'm wondering if it would be better if we pointed at a specific version of Locus and simply specified the artifacts without version. This would require less maintenance of the TP and should make the build more stable. That said, the solution would only work if it is acceptable to version the dependencies based on a specific version of Locus. Is this acceptable? Reference: https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... Specific plugin versions would go to 0.0.0, while the repository URL would go to .../stable/locus/<some-version>. Thanks in advance, Rob

10 years, 3 months

5
11
0 / 0

JBoss Tools 4.1.x, 4.2.0, and beyond!

by Nick Boldt

A while ago I sent an email saying that your projects' master branch should be used for new development work aimed at Eclipse 4.4 (Luna, June 2014). However, it appears that we may be doing a second release on Kepler this year. Therefore, please set up your branches as follows: * master branch: new features & bugfixes, to be included in JBoss Tools 4.2, aimed at Eclipse 4.3.1 (Kepler SR1). Be sure to upversion your features/plugins appropriately (eg., 4.1.100 or 4.2.0 as required) * jbosstools-4.1.x branch aimed at MAINTENANCE ONLY BUGFIXES for JBT 4.1.1 (again, on Kepler). Be sure to upversion your features/plugins appropriately (eg., 4.1.1) If you are keen to try Luna [1] once its first M1 milestone releases on August 23, please create a temporary branch, perhaps called "jbosstools-luna", in which you can experiment with Eclipse 4.4 compliance/compatibilty. This release will likely be called JBoss Tools 4.3. Questions or concerns, please talk to Denis, Fred, Max or Mickael. As a reminder, I'll be on PTO from Wed, Jul 31 - Sun, Aug 11, with limited internet access. [1] http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 4 months

2
1
0 / 0

Disabling a compulsory field in JIRA

by Michelle Murray

So I've got a bit of an issue with JIRA at the moment and I hope someone can solve it for me. I'm asking the JBDS team because we all use JIRA a lot and someone else might have come across the issue. Steps to reproduce: 1. Find a bug in JBDS 2. Go to JIRA to report bug 3. Click 'create issue' icon 4. Fill in the usual fields (bug, summary, component, affects version, description) 5. Click 'create' to create the JIRA >> Creation fails It seems that in the create new issue window, there is another compulsory field, 'Support Case Reference' (screen capture attached). And if I don't enter a URL I can't submit the bug. Now this seems to just be my issue as Rob had a look and the field doesn't appear for him. I've obviously done something, but what and how do I fix it? Any ideas anyone? Answers on a postcard to Brisbane :) Thanks, Michelle

10 years, 4 months

3
2
0 / 0

Locus 1.0.0.Final is released

by Mickael Istria

Hi all, Locus 1.0.0.Final is released. As a reminder, Locus is the area where we repackage all non-OSGi/non-p2 dependencies that we want to use in the various Eclipse plugins and RCP applications we build. Its output is a p2 repository containing those artifacts and is meant to be consumed in target-platforms. The release is available at 2 stable locations with same content: * On JBoss Nexus, at https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... * On download.jboss.org at http://download.jboss.org/tools/updates/stable/locus/1.0.0.Final/ Here is the list of provided bundles: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... Git repository and tag: https://github.com/jbosstools/jbosstools-locus/tree/1.0.0.Final Issue tracker: https://issues.jboss.org/browse/JBIDE/component/12317444 CI Build which produced the release: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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>

10 years, 4 months

2
2
0 / 0

FedEx Shipment Notification

by trackingupdates＠fedex.com

body { font-family : "Courier New", Courier, monospace; font-size : 9pt; valign : top; text-align : left; line-height: 9pt:w }td { font-family : "Courier New", Courier, monospace; font-size : 9pt; valign : top; text-align : left; line-height: 9pt } ________________________________________________________________________________ This tracking update has been requested and attached to this email ________________________________________________________________________________ Reference information includes: Invoice number, Reference, Special handling/Services, Residential Delivery. Reference information is attached to this email. Tracking number: 472177693216 To track the latest status of your shipment, click on the tracking number above, or visit us at fedex.com. To learn more about FedEx Express, please visit our website at fedex.com. This tracking update has been sent to you by FedEx on the behalf of the Requestor noted above. FedEx does not validate the authenticity of the requestor and does not validate, guarantee or warrant the authenticity of the request, the requestor's message, or the accuracy of this tracking update. For tracking results and fedex.com's terms of use, go to fedex.com. Thank you for your business.

10 years, 4 months

1
0
0 / 0

Move to Tycho 0.18.1

by Mickael Istria

Hi all, Tycho 0.18.1 was released last week and contains a necessary fix to support Maven 3.1.0, without breaking compatibility with Maven 3.0.x. See https://issues.jboss.org/browse/JBIDE-15281 for details. In order to make it easier for everyone to build, we'd like to migrate to Tycho 0.18.1 and enable compatibility with Maven 3.1.0 by the end of the day. If you have any objection to that, please let us know. 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>

10 years, 4 months

1
0
0 / 0

JBoss Tools 4.1.0.Final is available

by Nick Boldt

JBoss Tools 4.1.0.Final is now available. This is a stable release aimed at Eclipse 4.3.0 (Kepler) users. Eclipse Marketplace: https://marketplace.eclipse.org/content/jboss-tools-kepler Update Sites: http://download.jboss.org/jbosstools/updates/stable/kepler/ Installation + Download Pages: http://www.jboss.org/tools/download http://www.jboss.org/tools/download/stable/4_1 http://www.jboss.org/tools/download/installation/update_4_1 Requirement Sites: (These are loaded automatically into Eclipse when installing JBoss Tools from the URLs above. Provided here simply for reference.) http://download.jboss.org/jbosstools/updates/kepler/ http://download.jboss.org/jbosstools/updates/kepler/extras/ -- 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... --------- Project leads, please tag your projects! co jbosstools-4.1.0.Finalx git tag jbosstools-4.1.0.Final git push origin jbosstools-4.1.0.Final -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

10 years, 4 months

4
5
0 / 0

Fwd: JBoss Tools maintenance branch - once tagged for 4.1.0.Final - is open for 4.1.x bug fixes / No new 4.x releases scheduled yet

by Michelle Murray

jbosstools-bpel does not yet have a jbosstools-4.1.x branch [1]. This is breaking the new jenkins build for the 4.1 docs [2]. Is a 4.1.x branch going to be created? Who is going to create it? Thanks, Michelle [1] https://github.com/jbosstools/jbosstools-bpel [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs_41/ ----- Forwarded Message ----- From: "Nick Boldt" <nboldt(a)redhat.com> To: jbosstools-dev(a)lists.jboss.org Sent: Wednesday, 24 July, 2013 2:21:15 AM Subject: [jbosstools-dev] JBoss Tools maintenance branch - once tagged for 4.1.0.Final - is open for 4.1.x bug fixes / No new 4.x releases scheduled yet BEFORE ANYTHING goes into the jbosstools-4.1.x branches, please be sure that you've tagged your branches with a jbosstools-4.1.0.Final tag. -- Then, and only then, the jbosstools-4.1.x branches of the various projects will be once again open for bug fixing. This process requires every issue assigned to 4.1.1.Final in JBIDE JIRA to have PR request attached, reviewed and approved by Max, Fred or Denis before pushing it to 4.1.x branch. * There should be no API changes, or new features/plugins in the maintenance branch. * Please be aware that most likely nothing will be approved until end of next week. -- Worthy of note too, *there is no scheduled 4.1.1 release* (Beta, CR, or Final) at this time. There is also *no scheduled 4.2.0* scheduled at this time. Both will *most likely* happen, but no dates have been set ... yet. We should have a better idea of the Aug/Sept/Oct release plans in the next few weeks - Max is back Monday Aug 29, so the conversations can begin in earnest then. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

10 years, 4 months

3
2
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev July 2013