From manderse at redhat.com Tue Apr 1 02:57:20 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 01 Apr 2014 08:57:20 +0200 Subject: [jbosstools-dev] Windup Eclipse Plugin v3.0.0 - Export Windup reports from Eclipse In-Reply-To: References: <2ec8db18.00008214.0000006a@RHCR9L4HN9> <6B8A8744-F1C3-428F-82BB-D72C36C86B78@redhat.com> Message-ID: Hey Ian, This mail got lost in my inbox ;/ > I could have sworn I saw HD versions of all three of the demo videos > when > I first uploaded them. Now looking at them again they are all small > and > grainy. I will have to take a look tonight to see what is going on > with > that. Let me know if you figured those out ;) > Yes, the wizard takes the already generated report out of the > .metadata > folder, zips/tars it up and exports it to the location of your choice. > Also if the report does not already exists then it generates one, and > there is the option to always generate new report before export as > well. cool. > As far as adding to the global menu. I did not know where else to put > the > new actions. I do have the export wizard in the export wizards dialog, > but > the other two options to view in the windup report view and to > generate > the windup report need a place to live. Before I first added the menu > I > was chatting with my friend who still commits to WTP about where he > would > put them, because I was worried about clutter, but he said he would > create > a new sub menu as I did. If you have a better idea for where the > "Open in > Windup Report View" and "Generate Windup Report" actions could live I > am > all ears. The only reason I also added the "Export Windup Report" > action > there as well was because I already had the sub menu and it seemed > like a > logical place a user may look for the export function as well as > checking > the export dialog. But if a new home is found for the other two > actions I > have no problem just having the export wizard live in the export > dialog. The context menu is just waaaaay too crowded for having 'once in a while' features put on all context menus. I would simply not put them in the context menu by default - you could have a command definition users can enable if they want to but otherwise just have a command that would be accessible via Ctrl+3 or the wizards. Or at least only show this if there is a windup report available to the project (assuming that can be detected in sub miliseconds so the menu does not get slow to open) > As far as adding all of this to the jboss-tools project. The biggest > problem is I still not have a nightly build, and I do not have a > nightly > build for the eclipse plugin because I have not been able to > coordinate > with Brad to get a nightly build for Windup. The biggest issue with > getting a nightly for windup would be to actually do a windup release > and > start doing windup development in a snapshot version rather than 0.7.0 > where it has been being done for the past year. I did start that > conversation with Brad a few months back but it stalled out due to > life > events. If you all are ready to make this happen on your end then I > can > start trying to work with Brad again to get Windup versioning > stabilized, > and the nightly builds set up. as far as I understand Lincoln is getting involved in the migration project so it would make sense to try coordinate the various releases with him and Brad. i've cc'ed him here. > Blue Skies, > ~Ian > > -----Original Message----- > From: Max Rydahl Andersen [mailto:manderse at redhat.com] > Sent: Monday, February 10, 2014 9:42 AM > To: Ian Tewksbury > Cc: jboss-migration at redhat.com; windup-dev at lists.jboss.org; > jbosstools-dev at lists.jboss.org; Evong Nham; Brad Davis > Subject: Re: [jbosstools-dev] Windup Eclipse Plugin v3.0.0 - Export > Windup > reports from Eclipse > > >> I have just released version 3.0.0 of the Windup Eclipse plugin. In >> this new release you can now export Windup reports that are generated >> in Eclipse. This allows a developer to easily generate a Windup >> report >> in Eclipse and then export it for sharing with whoever requested a >> Windup report. > > Cool. (I assume its "just" saving the already generated html to a > separate location?) > > Wondering if its time to include this into jboss tools releases ? > >> * Demo Video: http://www.youtube.com/watch?v=BbBiQaQj2zk > > seem to only be available in 360 resolution - got something bigger so > can > see what happens ? > > btw. I noticed Windup is added to the ever growing root context menu. > shouldn't this not just be via > the wizard menu or configured first via the Configure submenu instead > of > polluting this context menu ? > >> * Project Page: >> https://github.com/windup/windup-eclipse-plugin >> >> * Wiki: https://github.com/windup/windup-eclipse-plugin/wiki >> >> * Windup Project Page: https://github.com/windup/windup > > /max /max http://about.me/maxandersen From mistria at redhat.com Tue Apr 1 06:59:54 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 01 Apr 2014 12:59:54 +0200 Subject: [jbosstools-dev] m2e 1.4.1 (Java 8 support) is available In-Reply-To: References: Message-ID: <533A9C2A.9090801@redhat.com> On 04/01/2014 12:15 AM, Fred Bricon wrote: > Hi, > > FYI, following the recent availability of Java 8 support for Kepler > SR2, we just released m2e 1.4.1 (a.k.a 1.4.1.20140328-1905), available > from[1]. > This service release simply contains the backport for Java 8 support > [2] introduced in m2e 1.5/Luna [3]. > > [1] http://download.eclipse.org/technology/m2e/releases/ > [2] https://bugs.eclipse.org/431546 > [3] https://bugs.eclipse.org/420848 Is this something we'll want in a future release of our Kepler stream of JBoss Tools/Developer Studio ? If so, https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#create-jira-outlining-the-request Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140401/4d955e0c/attachment.html From fbricon at redhat.com Tue Apr 1 07:19:15 2014 From: fbricon at redhat.com (Fred Bricon) Date: Tue, 01 Apr 2014 13:19:15 +0200 Subject: [jbosstools-dev] m2e 1.4.1 (Java 8 support) is available In-Reply-To: <533A9C2A.9090801@redhat.com> References: <533A9C2A.9090801@redhat.com> Message-ID: <533AA0B3.2060804@redhat.com> If we plan on doing another release containing everything for Java 8 support then yes. Else no. Le mardi 1 avril 2014 12:59:54, Mickael Istria a ?crit : > On 04/01/2014 12:15 AM, Fred Bricon wrote: >> Hi, >> >> FYI, following the recent availability of Java 8 support for Kepler >> SR2, we just released m2e 1.4.1 (a.k.a 1.4.1.20140328-1905), >> available from[1]. >> This service release simply contains the backport for Java 8 support >> [2] introduced in m2e 1.5/Luna [3]. >> >> [1] http://download.eclipse.org/technology/m2e/releases/ >> [2] https://bugs.eclipse.org/431546 >> [3] https://bugs.eclipse.org/420848 > Is this something we'll want in a future release of our Kepler stream > of JBoss Tools/Developer Studio ? If so, > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#create-jira-outlining-the-request > > Cheers, > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From nboldt at redhat.com Tue Apr 1 22:32:33 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 01 Apr 2014 22:32:33 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta1a' bits available for QE testing (for real this time!) Message-ID: <533B76C1.8010000@redhat.com> As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Since the previous Beta1a content was identical to the Beta1 content, I deleted it and have since REPLACED the old Beta1 folders w/ new content. You'll note the /build/ folders have larger build numbers, too. Update Sites: * http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Beta1a.core/ * http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Beta1a.coretests/ * http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Beta1a.hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Beta1a.webtools/ Builds: * http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1a.core/2014-04-01_19-38-57-B95 * http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1a.coretests/2014-04-01_19-38-57-B82 * http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1a.hibernatetools/2014-04-01_20-15-46-B37 * http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1a.webtools/2014-04-01_20-15-46-B86 JBoss Central: * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta2-SNAPSHOT/ (upcoming milestone) To test the upcoming 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.2.0.Beta1a/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta1a/ Target Platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta1 (upcoming milestone) Until the above target platform site is released, you will need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) New + Noteworthy (subject to change): * http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstools-documentation/master/whatsnew/index.html * http://docs.jboss.org/tools/whatsnew/ Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Changes prompting this respin-a are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-a%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%228.0.0.Beta1%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.2.0.Beta1%22%29%29%29 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From fbricon at gmail.com Thu Apr 3 06:41:41 2014 From: fbricon at gmail.com (Fred Bricon) Date: Thu, 3 Apr 2014 12:41:41 +0200 Subject: [jbosstools-dev] Memory leaks in WTP with pending patches Message-ID: Hi guys, Snjeza contributed a few patches to fix some memory leaks in WTP quite some time ago. These 2 are still pending : * https://bugs.eclipse.org/399099 Memory leak in EAR5ModelProvider * https://bugs.eclipse.org/398568 Memory leak in org.eclipse.jem.workbench.utility.JavaModelListener Any chance these patches could be applied for Luna M7? Another memory leak candidate that might be worth looking at (though no patch was provided) : * https://bugs.eclipse.org/377998 Thanks, Fred -- "Have you tried turning it off and on again" - The IT Crowd -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140403/f3c93167/attachment.html From nboldt at redhat.com Fri Apr 4 11:13:37 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 04 Apr 2014 11:13:37 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta2-SNAPSHOT target platform: remove GPE/GWT, fix Atlassian Message-ID: <533ECC21.80605@redhat.com> Here is a proposal for a change to the JBoss Tools 4.40.0.Beta2-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/50 https://github.com/jbosstools/jbosstools-target-platforms/pull/49 https://github.com/jbosstools/jbosstools-target-platforms/pull/48 It consists of the following changes: * JBIDE-16960 Remove unneeded GPE/GWT features/plugins from TP * JBIDE-16910 Atlassian Connector cannot be installed (missing deps) -- The above PRs have already been applied, so you can use the following to try to build the TP locally to test it out: Build target-platform: $ cd jbosstools-target-platforms $ git fetch origin 4.40.x $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Beta2-SNAPSHOT -Pmultiple.target -- If you want to perform a scripted install of the entire target platform into your local Eclipse or JBDS instance, you can now do so with this script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh Usage is documented in the above script, and in this README: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files --- More info: The reason for the removal is that o.j.t.gwt.feature and o.j.t.maven.gwt.feature have been removed from JBoss Tools 4.2.0.Beta1/Beta2. You will notice that with the removal of GPE/GWT from the target platform, its size on disk is now 200M smaller. Big props to Rob Stryker and Jucia Jelinkova for bringing forth these problems. Why remove gwt and maven.gwt, plus the com.google stuff on which they depend? For JBT 4.1 / JBDS 7.1, we deprecated org.jboss.tools.gwt.feature - it's still in 4.1 / 7.1, but it's a hidden feature. For JBT 4.2 / JBDS 8.0, we have removed org.jboss.tools.maven.gwt.feature because much of the com.google stuff on which it depends cannot be installed on Luna. So we either end up with a partially-working install, or we remove it entirely and wait to see if Google actually produces a new GPE/GWT for Luna, including support for Maven. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Sun Apr 6 03:47:17 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Sun, 06 Apr 2014 09:47:17 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta2-SNAPSHOT target platform: remove GPE/GWT, fix Atlassian In-Reply-To: <533ECC21.80605@redhat.com> References: <533ECC21.80605@redhat.com> Message-ID: <448C304D-FFBE-4214-9739-05F441F1C4FA@redhat.com> On 4 Apr 2014, at 17:13, Nick Boldt wrote: > Here is a proposal for a change to the JBoss Tools > 4.40.0.Beta2-SNAPSHOT > target platform: > > https://github.com/jbosstools/jbosstools-target-platforms/pull/50 > https://github.com/jbosstools/jbosstools-target-platforms/pull/49 > https://github.com/jbosstools/jbosstools-target-platforms/pull/48 > > It consists of the following changes: > > * JBIDE-16960 Remove unneeded GPE/GWT features/plugins from TP > * JBIDE-16910 Atlassian Connector cannot be installed (missing deps) That last one is a good example of why we need to get these mails out. The jira does not list it explicitly but looking at https://github.com/jbosstools/jbosstools-target-platforms/pull/48/files We now got to include com.thoughtworks.xstream and org.joda.time that were missing AND need to include org.eclipse.mylyn.commons.soap_feature.feature.group since it will not be in Luna according to https://bugs.eclipse.org/bugs/show_bug.cgi?id=430816 That raises two questions to me: A) why are xstram and joda.time now required ? were they accidentally removed in the "great TP reduction refactor" ? If yes - great, this is a fix for that. B) What will atlassian jira plugin guys do with the missing spa-p dependency ? Will they mirror it ? use a different version ? change their packaging ? For now we can "survive" but atlassian have changed packaging on us in the last minute in past. Nick - have you opened issues against atlassian jira and if not could you ? btw. is the atlassian issue fixed in Beta1 or just Beta2 ? according to JBDS-3000 at least snjezana does not see the missing xstream. /max > -- > > The above PRs have already been applied, so you can use the following > to > try to build the TP locally to test it out: > > Build target-platform: > > $ cd jbosstools-target-platforms > $ git fetch origin 4.40.x > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple > $ mvn clean install -P \!multiple2repo > > Try with just built target-platform: > > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.Beta2-SNAPSHOT > -Pmultiple.target > > -- > > If you want to perform a scripted install of the entire target > platform > into your local Eclipse or JBDS instance, you can now do so with this > script: > > https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh > > Usage is documented in the above script, and in this README: > > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files > > --- > > More info: > > The reason for the removal is that o.j.t.gwt.feature and > o.j.t.maven.gwt.feature have been removed from JBoss Tools > 4.2.0.Beta1/Beta2. > > You will notice that with the removal of GPE/GWT from the target > platform, its size on disk is now 200M smaller. > > Big props to Rob Stryker and Jucia Jelinkova for bringing forth these > problems. > > Why remove gwt and maven.gwt, plus the com.google stuff on which they > depend? > > For JBT 4.1 / JBDS 7.1, we deprecated org.jboss.tools.gwt.feature - > it's > still in 4.1 / 7.1, but it's a hidden feature. > > For JBT 4.2 / JBDS 8.0, we have removed > org.jboss.tools.maven.gwt.feature because much of the com.google stuff > on which it depends cannot be installed on Luna. So we either end up > with a partially-working install, or we remove it entirely and wait to > see if Google actually produces a new GPE/GWT for Luna, including > support for Maven. > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From angelo.zerr at gmail.com Sun Apr 6 19:19:11 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Mon, 7 Apr 2014 01:19:11 +0200 Subject: [jbosstools-dev] Release of AngularJS Eclipse 0.1.0 Message-ID: Hi all, For your information, Pascal (many thank's Pascal) has created the release 0.1.0 of AngularJS Eclipse. Snaphost (next release) is 0.1.1. Please read https://github.com/angelozerr/tern.java/wiki/Installation-Update-Site for more informations about update site. Marketplace was created too at https://marketplace.eclipse.org/content/angularjs-eclipse/ Regards Angelo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140407/34c21b50/attachment.html From mistria at redhat.com Mon Apr 7 01:57:54 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 07 Apr 2014 07:57:54 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta2-SNAPSHOT target platform: remove GPE/GWT, fix Atlassian In-Reply-To: <448C304D-FFBE-4214-9739-05F441F1C4FA@redhat.com> References: <533ECC21.80605@redhat.com> <448C304D-FFBE-4214-9739-05F441F1C4FA@redhat.com> Message-ID: <53423E62.1030604@redhat.com> On 04/06/2014 09:47 AM, Max Rydahl Andersen wrote: > A) why are xstram and joda.time now required ? were they accidentally > removed in the "great TP reduction refactor" ? If yes - great, this is a > fix for that. Most likely yes. See bug comments for more details. > btw. is the atlassian issue fixed in Beta1 or just Beta2 ? according to > JBDS-3000 at least snjezana does not see the missing xstream. JBIDE-16910 isn't about installation time, otherwise install-grinder would have caught it. It's only an issue when trying to install everything from target-platform directly in your IDE, which is not a user scenario we test. -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140407/62c489a1/attachment.html From mistria at redhat.com Mon Apr 7 02:16:47 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 07 Apr 2014 08:16:47 +0200 Subject: [jbosstools-dev] EclipseCon France call for paper: 3 weeks left In-Reply-To: <5333029B.4090804@redhat.com> References: <5333029B.4090804@redhat.com> Message-ID: <534242CF.4060109@redhat.com> Just a reminder that Early-Bird talk selection (5 talks) is today, and that final deadline for submission on next week. Cheers, On 03/26/2014 05:38 PM, Mickael Istria wrote: > Beware that Call For Paper for EclipseCon France -in Toulouse, > (17)-18-19 June- ends in 3 weeks. > https://www.eclipsecon.org/france2014/cfp > So anyone interested should start getting approval, budget and talks > ready. > > There is much space for the topics covered by JBoss Tools, > Cordova/Aerogear, RedHat Developer Kit, OpenShift, Vert.x and so on. > I think it's also a place where it might be possible to demonstrate > how to use Java 8 in a JEE application with Eclipse, or having fun > with a Raspberry Pi as a target server for JEE development for example... > > There is no risk in submitting something out of the original scope, so > feel free to submit anything you think can make sense for the audience! -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140407/ccc4b7c2/attachment.html From manderse at redhat.com Mon Apr 7 02:45:38 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 07 Apr 2014 08:45:38 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta2-SNAPSHOT target platform: remove GPE/GWT, fix Atlassian In-Reply-To: <53423E62.1030604@redhat.com> References: <533ECC21.80605@redhat.com> <448C304D-FFBE-4214-9739-05F441F1C4FA@redhat.com> <53423E62.1030604@redhat.com> Message-ID: <98ACF605-9D73-431A-B1A7-ADE54678C41D@redhat.com> On 7 Apr 2014, at 7:57, Mickael Istria wrote: > On 04/06/2014 09:47 AM, Max Rydahl Andersen wrote: >> A) why are xstram and joda.time now required ? were they accidentally >> removed in the "great TP reduction refactor" ? If yes - great, this >> is a >> fix for that. > Most likely yes. See bug comments for more details. >> btw. is the atlassian issue fixed in Beta1 or just Beta2 ? according >> to >> JBDS-3000 at least snjezana does not see the missing xstream. > JBIDE-16910 isn't about installation time, otherwise install-grinder > would have caught it. It's only an issue when trying to install > everything from target-platform directly in your IDE, which is not a > user scenario we test. That does not seem to make sense. why would we not ensure everything in the TP is installable ? That is what the first users of TP (developers) need to do. /max http://about.me/maxandersen From manderse at redhat.com Mon Apr 7 02:48:36 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 07 Apr 2014 08:48:36 +0200 Subject: [jbosstools-dev] Release of AngularJS Eclipse 0.1.0 In-Reply-To: References: Message-ID: <48318C30-E554-4871-8CC1-2F8EA6FCFF63@redhat.com> On 7 Apr 2014, at 1:19, Angelo zerr wrote: > Hi all, > > For your information, Pascal (many thank's Pascal) has created the release > 0.1.0 of AngularJS Eclipse. Snaphost (next release) is 0.1.1. Please read > https://github.com/angelozerr/tern.java/wiki/Installation-Update-Site for > more informations about update site. > > Marketplace was created too at > https://marketplace.eclipse.org/content/angularjs-eclipse/ Great! /max http://about.me/maxandersen From mistria at redhat.com Mon Apr 7 02:49:09 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 07 Apr 2014 08:49:09 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta2-SNAPSHOT target platform: remove GPE/GWT, fix Atlassian In-Reply-To: <98ACF605-9D73-431A-B1A7-ADE54678C41D@redhat.com> References: <533ECC21.80605@redhat.com> <448C304D-FFBE-4214-9739-05F441F1C4FA@redhat.com> <53423E62.1030604@redhat.com> <98ACF605-9D73-431A-B1A7-ADE54678C41D@redhat.com> Message-ID: <53424A65.8010604@redhat.com> On 04/07/2014 08:45 AM, Max Rydahl Andersen wrote: > That does not seem to make sense. > why would we not ensure everything in the TP is installable ? That's the purpose of the TP validation, that runs everytime we build a TP. However, it appears there is a bug in the validation. https://issues.jboss.org/browse/JBIDE-17018 > That is what the first users of TP (developers) need to do. Actually, using it "the PDE way" seems to work. It's only when trying to install things in the IDE that installation fail. -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140407/5f7894a9/attachment.html From rstryker at redhat.com Mon Apr 7 03:32:17 2014 From: rstryker at redhat.com (Rob Stryker) Date: Mon, 07 Apr 2014 15:32:17 +0800 Subject: [jbosstools-dev] XML Catalog, assistance needed Message-ID: <53425481.5000707@redhat.com> Hi: I'm looking at separating out the xml schema catalog entries into their own plugin, and a request has been made to add even more schemas. But I'm having a problem discovering how to do it uniformly. There are several syntaxes used to add entries, and I really don't know which syntax to use and when: We use the following syntaxes at varying times: This first one (FORMAT 1) is most often used by our legacy dtd's, and I honestly have no idea how it works at all: I've seen this next entry (FORMAT 2) added as well. The thing to note here is that the name attribute, which I believe represents namespace, is set to http://www.jboss.com/xml/ns/javaee, but an open jira indicates this type of catalog entry will form invalid xml files and we should avoid it. The next syntax (FORMAT 3) is similar, but seems to have a namespace that points to a specific xsd file. The fourth (FORMAT 4) seems most often used by our newest schema, and seems the most successful one. The problem for me is that when I look at many other xsd files that could be added, they don't show namespaces in a urn:jboss format. Looking at the xsd files directly, they also don't have a string like "http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" anywhere in the xsd file, so I can't use formats 4 or 3. I have no idea how format 1 works, and format 2 has been indicated to be non-functional. So if I want to add an xsd file that has header like the one below, I have no idea how to add it: Ideally, I would make a small script in the plugin to regenerate the catalog entries based on what files are in the folder. This way it'd be deterministic, and we can add whole collections of schemas after each new major release of jee or wildfly. But I really can't figure out which catalog entry forms to use against what types of xsd files or how to properly map it at all. Any help here would be very much appreciated. From manderse at redhat.com Mon Apr 7 03:51:50 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 07 Apr 2014 09:51:50 +0200 Subject: [jbosstools-dev] XML Catalog, assistance needed In-Reply-To: <53425481.5000707@redhat.com> References: <53425481.5000707@redhat.com> Message-ID: <6716BE83-D966-4DE8-8AAD-F0401E1F85E0@redhat.com> Context: https://issues.jboss.org/browse/JBIDE-16358 was the original issue, Rob opened a topic branch w a new isolated plugin https://github.com/robstryker/jbosstools-server/tree/JBIDE-16358/as/plugins/org.jboss.tools.as.catalog > Hi: > > I'm looking at separating out the xml schema catalog entries into > their > own plugin, and a request has been made to add even more schemas. But > I'm having a problem discovering how to do it uniformly. There are > several syntaxes used to add entries, and I really don't know which > syntax to use and when: > > We use the following syntaxes at varying times: > > This first one (FORMAT 1) is most often used by our legacy dtd's, and > I > honestly have no idea how it works at all: > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_4_0.dtd" > webURL="http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd"/> > > I've seen this next entry (FORMAT 2) added as well. The thing to note > here is that the name attribute, which I believe represents namespace, > is set to http://www.jboss.com/xml/ns/javaee, but an open jira > indicates > this type of catalog entry will form invalid xml files and we should > avoid it. > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jbossws-web-services_1_0.xsd"/> > > > The next syntax (FORMAT 3) is similar, but seems to have a namespace > that points to a specific xsd file. > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_5_0.xsd"/> > > > The fourth (FORMAT 4) seems most often used by our newest schema, and > seems the most successful one. > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_1_0.xsd"/> > > > The problem for me is that when I look at many other xsd files that > could be added, they don't show namespaces in a urn:jboss format. > Looking at the xsd files directly, they also don't have a string like > "http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" anywhere in the xsd > file, so I can't use formats 4 or 3. I have no idea how format 1 > works, > and format 2 has been indicated to be non-functional. > > So if I want to add an xsd file that has header like the one below, I > have no idea how to add it: > > > targetNamespace="http://java.sun.com/xml/ns/javaee" > xmlns:javaee="http://java.sun.com/xml/ns/javaee" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > elementFormDefault="qualified" > attributeFormDefault="unqualified" > version="2.1"> > > > > Ideally, I would make a small script in the plugin to regenerate the > catalog entries based on what files are in the folder. This way it'd > be > deterministic, and we can add whole collections of schemas after each > new major release of jee or wildfly. But I really can't figure out > which > catalog entry forms to use against what types of xsd files or how to > properly map it at all. > > Any help here would be very much appreciated. > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Mon Apr 7 04:54:59 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 07 Apr 2014 10:54:59 +0200 Subject: [jbosstools-dev] XML Catalog, assistance needed In-Reply-To: <53425481.5000707@redhat.com> References: <53425481.5000707@redhat.com> Message-ID: hey, I started by reading the docs for catalogcontributions. http://www.eclipse.org/webtools/wst/components/xml/M5/new_and_noteworthy/catalogContributions.html This doc describes that 'public' is what is used to "associates a URI reference with the public identitier portion of an external identifier" and uri "uri element associates a URI reference with the a URI reference that is not part of an external identifier." Thus these are two different things. You need a at least a public entry to make it work for when users don't list identifiers and uri is for when direct urls are used. Thus if you don't have public entries then it explains why it does not work. Other background info: http://www.eclipse.org/webtools/wst/components/xml/M5/new_and_noteworthy/XMLCatalog-m5.html http://wiki.eclipse.org/Using_the_XML_Catalog > I'm looking at separating out the xml schema catalog entries into > their > own plugin, and a request has been made to add even more schemas. btw. if you are going to create new plugin please name the dir "schemas" not just dtd ;) > But > I'm having a problem discovering how to do it uniformly. There are > several syntaxes used to add entries, and I really don't know which > syntax to use and when: See above - public != uri. > We use the following syntaxes at varying times: > > This first one (FORMAT 1) is most often used by our legacy dtd's, and > I > honestly have no idea how it works at all: > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_4_0.dtd" > webURL="http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd"/> This is the entry that defines if you have a public id "-//JBoss//DTD JBOSS 4.0//EN" eclipse should look at this uri inside your plugin to get the schema. > I've seen this next entry (FORMAT 2) added as well. The thing to note > here is that the name attribute, which I believe represents namespace, > is set to http://www.jboss.com/xml/ns/javaee, but an open jira > indicates > this type of catalog entry will form invalid xml files and we should > avoid it. > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jbossws-web-services_1_0.xsd"/> Which jira ? What actually happens ? > The next syntax (FORMAT 3) is similar, but seems to have a namespace > that points to a specific xsd file. > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_5_0.xsd"/> I don't think there are any difference between FORMAT 2 and FORMAT 3 - they are just mappings of two uri's. > The fourth (FORMAT 4) seems most often used by our newest schema, and > seems the most successful one. > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_1_0.xsd"/> Define succesful ? This is simply mapping that when you use urn:jboss:1.0 as a namespace uri it will use this specific resource to locate it. Thus in short - you got *2* different entries, public and uri. They do different things (hence different names). and inside uri you are simply mapping a "virtual name" to a specific different resource that the tool can use. > The problem for me is that when I look at many other xsd files that > could be added, they don't show namespaces in a urn:jboss format. No, that is extra knowledge but they follow the same pattern so could probably be automated. Just need to verify against actual documentation on how to use these JBoss dtd/xmls. > Looking at the xsd files directly, they also don't have a string like > "http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" anywhere in the xsd > file, so I can't use formats 4 or 3. I have no idea how format 1 > works, > and format 2 has been indicated to be non-functional. > So if I want to add an xsd file that has header like the one below, I > have no idea how to add it: > > > targetNamespace="http://java.sun.com/xml/ns/javaee" > xmlns:javaee="http://java.sun.com/xml/ns/javaee" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > elementFormDefault="qualified" > attributeFormDefault="unqualified" > version="2.1"> I don't actually think xmlcatalog will even affect this creation - can you give me an example on how ? /max http://about.me/maxandersen From paul.verest at live.com Mon Apr 7 08:38:27 2014 From: paul.verest at live.com (Paul Verest) Date: Mon, 7 Apr 2014 20:38:27 +0800 Subject: [jbosstools-dev] Release of AngularJS Eclipse 0.1.0 In-Reply-To: <48318C30-E554-4871-8CC1-2F8EA6FCFF63@redhat.com> References: <48318C30-E554-4871-8CC1-2F8EA6FCFF63@redhat.com> Message-ID: Hello Angelo and Pascal Congratulation on 0.1 release Update site is very slow in China (I am at home, today is holiday) Is it on CDN or some cloud provider? Cheers, Paul On 07.04.2014 14:48, Max Rydahl Andersen wrote: > On 7 Apr 2014, at 1:19, Angelo zerr wrote: > >> Hi all, >> >> For your information, Pascal (many thank's Pascal) has created the release >> 0.1.0 of AngularJS Eclipse. Snaphost (next release) is 0.1.1. Please read >> https://github.com/angelozerr/tern.java/wiki/Installation-Update-Site for >> more informations about update site. >> >> Marketplace was created too at >> https://marketplace.eclipse.org/content/angularjs-eclipse/ > Great! > > /max > http://about.me/maxandersen > > From rcernich at redhat.com Mon Apr 7 12:18:02 2014 From: rcernich at redhat.com (Rob Cernich) Date: Mon, 7 Apr 2014 12:18:02 -0400 (EDT) Subject: [jbosstools-dev] XML Catalog, assistance needed In-Reply-To: References: <53425481.5000707@redhat.com> Message-ID: <991594718.497676.1396887482251.JavaMail.zimbra@redhat.com> Not sure if this helps or not, but here's what we're doing for SwitchYard. 1. We're using catalog.xml files for all SwitchYard related schema. 2. The target URLs are relative, which makes it easy to specify the target schema (i.e. you don't have to use something like: platform:/plugin/path/to/schema.xsd). 3. Catalogs are chained, which makes it easy to group the types of schema, e.g. third-party, 1.0, 1.1, 2.0, etc. 4. You don't need to figure out how the XML tools extension points work. 5. The catalog files are portable, e.g. I can manually add the base catalog from my tools project to my development workspace get schema resolution working (obviously, I need to make sure my tools project is up to date, but it works most of the time). Feel free to ping me on IRC. Here's the project link (note, the schema folder is populated via maven dependency unpack): https://github.com/jboss-switchyard/tools/tree/master/eclipse/plugins/org.switchyard.tools.xsd Here's the resulting plugin jar (might be easier to look at): http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/switchyard/1.1.5.Final/plugins/org.switchyard.tools.xsd_1.1.5.v20140403-2328-H5-Final.jar ----- Original Message ----- > hey, > > I started by reading the docs for catalogcontributions. > http://www.eclipse.org/webtools/wst/components/xml/M5/new_and_noteworthy/catalogContributions.html > > This doc describes that 'public' is what is used to "associates a URI > reference with the public identitier portion of an external identifier" > and uri "uri element associates a URI reference with the a URI reference > that is not part of an external identifier." > > Thus these are two different things. > > You need a at least a public entry to make it work for when users don't > list identifiers and uri is for when direct urls are used. > > Thus if you don't have public entries then it explains why it does not > work. > > Other background info: > http://www.eclipse.org/webtools/wst/components/xml/M5/new_and_noteworthy/XMLCatalog-m5.html > http://wiki.eclipse.org/Using_the_XML_Catalog > > > > I'm looking at separating out the xml schema catalog entries into > > their > > own plugin, and a request has been made to add even more schemas. > > btw. if you are going to create new plugin please name the dir "schemas" > not just dtd ;) > > > But > > I'm having a problem discovering how to do it uniformly. There are > > several syntaxes used to add entries, and I really don't know which > > syntax to use and when: > > See above - public != uri. > > > We use the following syntaxes at varying times: > > > > This first one (FORMAT 1) is most often used by our legacy dtd's, and > > I > > honestly have no idea how it works at all: > > > > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_4_0.dtd" > > webURL="http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd"/> > > This is the entry that defines if you have a public id "-//JBoss//DTD > JBOSS 4.0//EN" > eclipse should look at this uri inside your plugin to get the schema. > > > I've seen this next entry (FORMAT 2) added as well. The thing to note > > here is that the name attribute, which I believe represents namespace, > > is set to http://www.jboss.com/xml/ns/javaee, but an open jira > > indicates > > this type of catalog entry will form invalid xml files and we should > > avoid it. > > > > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jbossws-web-services_1_0.xsd"/> > > Which jira ? > What actually happens ? > > > The next syntax (FORMAT 3) is similar, but seems to have a namespace > > that points to a specific xsd file. > > > > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_5_0.xsd"/> > > I don't think there are any difference between FORMAT 2 and FORMAT 3 - > they are just mappings of two uri's. > > > The fourth (FORMAT 4) seems most often used by our newest schema, and > > seems the most successful one. > > > > > uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_1_0.xsd"/> > > Define succesful ? > > This is simply mapping that when you use urn:jboss:1.0 as a namespace > uri it will use this specific resource to locate it. > > Thus in short - you got *2* different entries, public and uri. They do > different things (hence different names). > and inside uri you are simply mapping a "virtual name" to a specific > different resource that the tool can use. > > > The problem for me is that when I look at many other xsd files that > > could be added, they don't show namespaces in a urn:jboss format. > > No, that is extra knowledge but they follow the same pattern so could > probably be automated. > Just need to verify against actual documentation on how to use these > JBoss dtd/xmls. > > > Looking at the xsd files directly, they also don't have a string like > > "http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" anywhere in the xsd > > file, so I can't use formats 4 or 3. I have no idea how format 1 > > works, > > and format 2 has been indicated to be non-functional. > > > So if I want to add an xsd file that has header like the one below, I > > have no idea how to add it: > > > > > > > targetNamespace="http://java.sun.com/xml/ns/javaee" > > xmlns:javaee="http://java.sun.com/xml/ns/javaee" > > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > > elementFormDefault="qualified" > > attributeFormDefault="unqualified" > > version="2.1"> > > I don't actually think xmlcatalog will even affect this creation - can > you give me an example on how ? > > /max > http://about.me/maxandersen > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > From dgolovin at exadel.com Mon Apr 7 15:28:31 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 07 Apr 2014 12:28:31 -0700 Subject: [jbosstools-dev] browsersim and cordovasim moved out from jbosstools-vpe Message-ID: <5342FC5F.4020502@exadel.com> Hello everyone, last week some changes were done in jbosstools on github.com related to jbosstools-vpe and jbosstools-aerogear repositories: 1. browsersim from jbosstools-vpe was moved to https://github.com/jbosstools/jbosstools-browsersim repository 2. cordovasim from jbosstools-vpe was moved to https://github.com/jbosstools/jbosstools-aerogear repository as cordovasim sub-module So if you depends on breowsersim/cordovasim please clone new jbosstools-browsersim repository and do not forget to get latest changes from jbosstools-vpe and jbosstools-aerogear repositories. Ids for eclipse features and plug-ins were NOT changed and all related jobs on jenkins are up and running. All changes were done in master branches and targeted 4.2.0.Beta2 release. Let me know if you have problems with local builds related to these changes. Thanks Denis From manderse at redhat.com Mon Apr 7 16:48:51 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 07 Apr 2014 22:48:51 +0200 Subject: [jbosstools-dev] XML Catalog, assistance needed In-Reply-To: <991594718.497676.1396887482251.JavaMail.zimbra@redhat.com> References: <53425481.5000707@redhat.com> <991594718.497676.1396887482251.JavaMail.zimbra@redhat.com> Message-ID: <78A96CE6-E4F2-4957-9EF5-0BF8AF54FEAB@redhat.com> On 7 Apr 2014, at 18:18, Rob Cernich wrote: > Not sure if this helps or not, but here's what we're doing for > SwitchYard. > > 1. We're using catalog.xml files for all SwitchYard related schema. > 2. The target URLs are relative, which makes it easy to specify the > target schema (i.e. you don't have to use something like: > platform:/plugin/path/to/schema.xsd). > 3. Catalogs are chained, which makes it easy to group the types of > schema, e.g. third-party, 1.0, 1.1, 2.0, etc. > 4. You don't need to figure out how the XML tools extension points > work. > 5. The catalog files are portable, e.g. I can manually add the base > catalog from my tools project to my development workspace get schema > resolution working (obviously, I need to make sure my tools project is > up to date, but it works most of the time). Excellent - I was wondering about using the catalog format but couldn't find an example. Yours definitely helps and much better agreed. I talked with Rob S. on chat today and the biggest problem we got is a bunch of the schemas we got does not really have a clear definition/documentation on were they came from...so that needs to be cleaned up/figured out first. And yes - the catalog approach is definitely a simpler setup. Thanks! > > Feel free to ping me on IRC. > > Here's the project link (note, the schema folder is populated via > maven dependency unpack): > https://github.com/jboss-switchyard/tools/tree/master/eclipse/plugins/org.switchyard.tools.xsd > > Here's the resulting plugin jar (might be easier to look at): > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/switchyard/1.1.5.Final/plugins/org.switchyard.tools.xsd_1.1.5.v20140403-2328-H5-Final.jar > > ----- Original Message ----- >> hey, >> >> I started by reading the docs for catalogcontributions. >> http://www.eclipse.org/webtools/wst/components/xml/M5/new_and_noteworthy/catalogContributions.html >> >> This doc describes that 'public' is what is used to "associates a URI >> reference with the public identitier portion of an external >> identifier" >> and uri "uri element associates a URI reference with the a URI >> reference >> that is not part of an external identifier." >> >> Thus these are two different things. >> >> You need a at least a public entry to make it work for when users >> don't >> list identifiers and uri is for when direct urls are used. >> >> Thus if you don't have public entries then it explains why it does >> not >> work. >> >> Other background info: >> http://www.eclipse.org/webtools/wst/components/xml/M5/new_and_noteworthy/XMLCatalog-m5.html >> http://wiki.eclipse.org/Using_the_XML_Catalog >> >> >>> I'm looking at separating out the xml schema catalog entries into >>> their >>> own plugin, and a request has been made to add even more schemas. >> >> btw. if you are going to create new plugin please name the dir >> "schemas" >> not just dtd ;) >> >>> But >>> I'm having a problem discovering how to do it uniformly. There are >>> several syntaxes used to add entries, and I really don't know which >>> syntax to use and when: >> >> See above - public != uri. >> >>> We use the following syntaxes at varying times: >>> >>> This first one (FORMAT 1) is most often used by our legacy dtd's, >>> and >>> I >>> honestly have no idea how it works at all: >>> >>> >> uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_4_0.dtd" >>> webURL="http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd"/> >> >> This is the entry that defines if you have a public id "-//JBoss//DTD >> JBOSS 4.0//EN" >> eclipse should look at this uri inside your plugin to get the schema. >> >>> I've seen this next entry (FORMAT 2) added as well. The thing to >>> note >>> here is that the name attribute, which I believe represents >>> namespace, >>> is set to http://www.jboss.com/xml/ns/javaee, but an open jira >>> indicates >>> this type of catalog entry will form invalid xml files and we should >>> avoid it. >>> >>> >> uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jbossws-web-services_1_0.xsd"/> >> >> Which jira ? >> What actually happens ? >> >>> The next syntax (FORMAT 3) is similar, but seems to have a namespace >>> that points to a specific xsd file. >>> >>> >> uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_5_0.xsd"/> >> >> I don't think there are any difference between FORMAT 2 and FORMAT 3 >> - >> they are just mappings of two uri's. >> >>> The fourth (FORMAT 4) seems most often used by our newest schema, >>> and >>> seems the most successful one. >>> >>> >> uri="platform:/plugin/org.jboss.tools.as.catalog/dtd/jboss_1_0.xsd"/> >> >> Define succesful ? >> >> This is simply mapping that when you use urn:jboss:1.0 as a namespace >> uri it will use this specific resource to locate it. >> >> Thus in short - you got *2* different entries, public and uri. They >> do >> different things (hence different names). >> and inside uri you are simply mapping a "virtual name" to a specific >> different resource that the tool can use. >> >>> The problem for me is that when I look at many other xsd files that >>> could be added, they don't show namespaces in a urn:jboss format. >> >> No, that is extra knowledge but they follow the same pattern so could >> probably be automated. >> Just need to verify against actual documentation on how to use these >> JBoss dtd/xmls. >> >>> Looking at the xsd files directly, they also don't have a string >>> like >>> "http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" anywhere in the xsd >>> file, so I can't use formats 4 or 3. I have no idea how format 1 >>> works, >>> and format 2 has been indicated to be non-functional. >> >>> So if I want to add an xsd file that has header like the one below, >>> I >>> have no idea how to add it: >>> >>> >>> >> targetNamespace="http://java.sun.com/xml/ns/javaee" >>> xmlns:javaee="http://java.sun.com/xml/ns/javaee" >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" >>> elementFormDefault="qualified" >>> attributeFormDefault="unqualified" >>> version="2.1"> >> >> I don't actually think xmlcatalog will even affect this creation - >> can >> you give me an example on how ? >> >> /max >> http://about.me/maxandersen >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> /max http://about.me/maxandersen From manderse at redhat.com Mon Apr 7 16:50:36 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 07 Apr 2014 22:50:36 +0200 Subject: [jbosstools-dev] browsersim and cordovasim moved out from jbosstools-vpe In-Reply-To: <5342FC5F.4020502@exadel.com> References: <5342FC5F.4020502@exadel.com> Message-ID: Context: https://issues.jboss.org/browse/JBIDE-16658 Thanks for the reorg Denis! The reason for the move btw. is so browsersim and cordovasim does not require the full VPE to work/be installed. /max > Hello everyone, > > last week some changes were done in jbosstools on github.com related > to > jbosstools-vpe and jbosstools-aerogear repositories: > 1. browsersim from jbosstools-vpe was moved to > https://github.com/jbosstools/jbosstools-browsersim repository > 2. cordovasim from jbosstools-vpe was moved to > https://github.com/jbosstools/jbosstools-aerogear repository as > cordovasim sub-module > > So if you depends on breowsersim/cordovasim please clone new > jbosstools-browsersim repository and do not forget to get latest > changes > from jbosstools-vpe and jbosstools-aerogear repositories. > > Ids for eclipse features and plug-ins were NOT changed and all related > jobs on jenkins are up and running. All changes were done in master > branches and targeted 4.2.0.Beta2 release. > > Let me know if you have problems with local builds related to these > changes. > > Thanks > Denis > > > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From nboldt at redhat.com Mon Apr 7 20:37:27 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 07 Apr 2014 20:37:27 -0400 Subject: [jbosstools-dev] JBT 4.2.0.Beta1 respin-b status :: DELAYED Message-ID: <534344C7.2000204@redhat.com> Due to test failures and 1 compilation failure [1] in as.core, tonight's respin will be DELAYED. [1] https://issues.jboss.org/browse/JBIDE-17034 Test failures include the usual "slave was too slow so test timed out" problems. Affected projects: * Central (red - test timeout on "virt" slave) * JavaEE (yellow - 2 test failures) * VPE (yellow - 1 test failure) I haven't opened JIRAs for these as I figure the project leads can decide if these warrant JIRAs or are transient problems due to bad slaves. SWT errors, disposed widgets, and test timeouts may be transient problems. However, the JavaEE test failing with "org.jboss.seam.core.jbpm not found" error sounds serious. If you're still reading this, there are more details re: test failures below. == Central == https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-central_4.2.luna/26/console 19:05:07 [INFO] org.jboss.tools.project.examples.test ............. FAILURE [40:31.078s] 19:05:07 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on project org.jboss.tools.project.examples.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 2400 seconds -> [Help 1] == JavaEE == https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-javaee_4.2.luna/22/testReport/ 1. org.jboss.tools.seam.ui.test.wizard.OpenSeamComponentDialogTest.testFindShortHand (from org.jboss.tools.seam.ui.test.SeamUiAllTests) junit.framework.AssertionFailedError: Component org.jboss.seam.core.jbpm not found 2. org.jboss.tools.seam.ui.test.hyperlink.SeamViewHyperlinkPartitionerTest.testSeamViewPartitioner (from org.jboss.tools.seam.ui.test.SeamUiAllTests) Failed to execute runnable (java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)) == VPE == https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-vpe_4.2.luna/16/testReport/org.jboss.tools.vpe.browsersim.browser.test/WebKitTests/testWebKitSetDefaultUserAgent/ 1. org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent (from org.jboss.tools.vpe.browsersim.browser.test.BrowserAllTests) org.eclipse.swt.SWTError: No more handles -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Tue Apr 8 06:21:53 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 08 Apr 2014 12:21:53 +0200 Subject: [jbosstools-dev] JBT 4.2.0.Beta1 respin-b status :: DELAYED In-Reply-To: <534344C7.2000204@redhat.com> References: <534344C7.2000204@redhat.com> Message-ID: Gah! :/ didn't you have a script to easily create jiras based on jenkins failures ? use those. best way to get attention and we need that for beta1. I'll start pinging those I can get to. /max > Due to test failures and 1 compilation failure [1] in as.core, > tonight's > respin will be DELAYED. > > [1] https://issues.jboss.org/browse/JBIDE-17034 > > Test failures include the usual "slave was too slow so test timed out" > problems. > > Affected projects: > > * Central (red - test timeout on "virt" slave) > > * JavaEE (yellow - 2 test failures) > > * VPE (yellow - 1 test failure) > > I haven't opened JIRAs for these as I figure the project leads can > decide if these warrant JIRAs or are transient problems due to bad > slaves. SWT errors, disposed widgets, and test timeouts may be > transient > problems. However, the JavaEE test failing with > "org.jboss.seam.core.jbpm not found" error sounds serious. > > If you're still reading this, there are more details re: test failures > below. > > == Central == > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-central_4.2.luna/26/console > > 19:05:07 [INFO] org.jboss.tools.project.examples.test ............. > FAILURE [40:31.078s] > > 19:05:07 [ERROR] Failed to execute goal > org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on > project org.jboss.tools.project.examples.test: Error while executing > platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: > Error while executing external command, process killed. Process > timeout > out after 2400 seconds -> [Help 1] > > == JavaEE == > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-javaee_4.2.luna/22/testReport/ > > 1. > > org.jboss.tools.seam.ui.test.wizard.OpenSeamComponentDialogTest.testFindShortHand > (from org.jboss.tools.seam.ui.test.SeamUiAllTests) > > junit.framework.AssertionFailedError: Component > org.jboss.seam.core.jbpm > not found > > 2. > > org.jboss.tools.seam.ui.test.hyperlink.SeamViewHyperlinkPartitionerTest.testSeamViewPartitioner > (from org.jboss.tools.seam.ui.test.SeamUiAllTests) > > Failed to execute runnable (java.lang.IllegalStateException: Need an > underlying widget to be able to set the input.(Has the widget been > disposed?)) > > == VPE == > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-vpe_4.2.luna/16/testReport/org.jboss.tools.vpe.browsersim.browser.test/WebKitTests/testWebKitSetDefaultUserAgent/ > > 1. > > org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent > (from org.jboss.tools.vpe.browsersim.browser.test.BrowserAllTests) > > org.eclipse.swt.SWTError: No more handles > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From mistria at redhat.com Tue Apr 8 09:06:12 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 08 Apr 2014 15:06:12 +0200 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit Message-ID: <5343F444.1060103@redhat.com> Hi all, Here is a proposal for a new 4.40.0.Beta2-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/53 It consists in the following changes: * JBIDE-17019 Add m2eclipse-egit to target-platform (fix JBIDE-16574) Please review this PR and yell if there is anything shocking. You can use the following stuff to try to build build the TP locally and try out against your component: Build target-platform: $ cd jbosstools-target-platforms $ git fetch mistria JBIDE-17019 $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Beta2-SNAPSHOT -Pmultiple.target Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140408/41d01ed7/attachment.html From manderse at redhat.com Tue Apr 8 09:17:19 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 08 Apr 2014 15:17:19 +0200 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit In-Reply-To: <5343F444.1060103@redhat.com> References: <5343F444.1060103@redhat.com> Message-ID: <866DD80C-0C5F-4E83-8681-42E2F8697D9E@redhat.com> Thanks for that - this one you wanted fixed by tomorrow or how ? your mail doesn't mention it. /max > Hi all, > > Here is a proposal for a new 4.40.0.Beta2-SNAPSHOT target platform: > https://github.com/jbosstools/jbosstools-target-platforms/pull/53 > > It consists in the following changes: > * JBIDE-17019 Add m2eclipse-egit to target-platform (fix JBIDE-16574) > > Please review this PR and yell if there is anything shocking. You can > use the following stuff to try to build build the TP locally and try > out > against your component: > > Build target-platform: > > $ cd jbosstools-target-platforms > $ git fetch mistria JBIDE-17019 > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple > $ mvn clean install -P \!multiple2repo > > Try with just built target-platform: > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.Beta2-SNAPSHOT > -Pmultiple.target > > Cheers, > > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From mistria at redhat.com Tue Apr 8 09:22:31 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 08 Apr 2014 15:22:31 +0200 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit In-Reply-To: <866DD80C-0C5F-4E83-8681-42E2F8697D9E@redhat.com> References: <5343F444.1060103@redhat.com> <866DD80C-0C5F-4E83-8681-42E2F8697D9E@redhat.com> Message-ID: <5343F817.8090004@redhat.com> On 04/08/2014 03:17 PM, Max Rydahl Andersen wrote: > Thanks for that - this one you wanted fixed by tomorrow or how ? your > mail doesn't mention it. There is no emergency for that it's not a blocker. So let's just give it a week of feedback unless it appears more important to someone else. -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140408/792d2581/attachment.html From fbricon at redhat.com Tue Apr 8 09:34:27 2014 From: fbricon at redhat.com (Fred Bricon) Date: Tue, 08 Apr 2014 15:34:27 +0200 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit In-Reply-To: <5343F817.8090004@redhat.com> References: <5343F444.1060103@redhat.com> <866DD80C-0C5F-4E83-8681-42E2F8697D9E@redhat.com> <5343F817.8090004@redhat.com> Message-ID: <5343FAE3.6040307@redhat.com> A week? Come on, the change is trivial and I'm waiting for it to apply the fix for https://issues.jboss.org/browse/JBIDE-16574 Le mardi 8 avril 2014 15:22:31, Mickael Istria a ?crit : > On 04/08/2014 03:17 PM, Max Rydahl Andersen wrote: >> Thanks for that - this one you wanted fixed by tomorrow or how ? your >> mail doesn't mention it. > There is no emergency for that it's not a blocker. > So let's just give it a week of feedback unless it appears more > important to someone else. > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From manderse at redhat.com Tue Apr 8 09:51:29 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 08 Apr 2014 15:51:29 +0200 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit In-Reply-To: <5343FAE3.6040307@redhat.com> References: <5343F444.1060103@redhat.com> <866DD80C-0C5F-4E83-8681-42E2F8697D9E@redhat.com> <5343F817.8090004@redhat.com> <5343FAE3.6040307@redhat.com> Message-ID: On 8 Apr 2014, at 15:34, Fred Bricon wrote: > A week? Come on, the change is trivial and I'm waiting for it to apply > the fix for https://issues.jboss.org/browse/JBIDE-16574 Yes, we should be fine to do this faster. Part of the TP updates is to make it clear who actually needs and when :) As written on jira i'm fine doing this asap - just want to give dgolovin chance to run the full build on his setup that is 7 minutes instead of 24hr+ on jenkins. /max > > Le mardi 8 avril 2014 15:22:31, Mickael Istria a ?crit : >> On 04/08/2014 03:17 PM, Max Rydahl Andersen wrote: >>> Thanks for that - this one you wanted fixed by tomorrow or how ? >>> your >>> mail doesn't mention it. >> There is no emergency for that it's not a blocker. >> So let's just give it a week of feedback unless it appears more >> important to someone else. >> -- >> Mickael Istria >> Eclipse developer at JBoss, by Red Hat >> My blog - My Tweets >> >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Tue Apr 8 09:56:55 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 08 Apr 2014 15:56:55 +0200 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit In-Reply-To: <5343F444.1060103@redhat.com> References: <5343F444.1060103@redhat.com> Message-ID: <053061C7-DBB8-44B6-97EF-8F364EA1EC57@redhat.com> On 8 Apr 2014, at 15:06, Mickael Istria wrote: > git fetch mistria JBIDE-17019 > just spend some time cursing about network being weird when realising your github username is not mistrial ;) https://github.com/mickaelistria /max http://about.me/maxandersen From mmalina at redhat.com Tue Apr 8 10:31:00 2014 From: mmalina at redhat.com (Martin Malina) Date: Tue, 8 Apr 2014 16:31:00 +0200 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit In-Reply-To: <053061C7-DBB8-44B6-97EF-8F364EA1EC57@redhat.com> References: <5343F444.1060103@redhat.com> <053061C7-DBB8-44B6-97EF-8F364EA1EC57@redhat.com> Message-ID: Integration tests build fine with this. On 8. 4. 2014, at 15:56, Max Rydahl Andersen wrote: > On 8 Apr 2014, at 15:06, Mickael Istria wrote: > >> git fetch mistria JBIDE-17019 >> > > just spend some time cursing about network being weird when realising > your github username is not mistrial ;) I hit the same problem :) -Martin > > https://github.com/mickaelistria > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140408/370ece35/attachment.html From dgolovin at exadel.com Tue Apr 8 11:48:22 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Tue, 08 Apr 2014 08:48:22 -0700 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit In-Reply-To: References: <5343F444.1060103@redhat.com> <866DD80C-0C5F-4E83-8681-42E2F8697D9E@redhat.com> <5343F817.8090004@redhat.com> <5343FAE3.6040307@redhat.com> Message-ID: <53441A46.8050007@exadel.com> I'll give it a try in next couple hours. Denis On 04/08/2014 06:51 AM, Max Rydahl Andersen wrote: > On 8 Apr 2014, at 15:34, Fred Bricon wrote: > >> A week? Come on, the change is trivial and I'm waiting for it to apply >> the fix for https://issues.jboss.org/browse/JBIDE-16574 > Yes, we should be fine to do this faster. Part of the TP updates is to > make it clear who actually needs and when :) > > As written on jira i'm fine doing this asap - just want to give dgolovin > chance to run the full build on his setup that is 7 minutes instead > of 24hr+ on jenkins. > > /max > >> Le mardi 8 avril 2014 15:22:31, Mickael Istria a ?crit : >>> On 04/08/2014 03:17 PM, Max Rydahl Andersen wrote: >>>> Thanks for that - this one you wanted fixed by tomorrow or how ? >>>> your >>>> mail doesn't mention it. >>> There is no emergency for that it's not a blocker. >>> So let's just give it a week of feedback unless it appears more >>> important to someone else. >>> -- >>> Mickael Istria >>> Eclipse developer at JBoss, by Red Hat >>> My blog - My Tweets >>> >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From dgolovin at exadel.com Tue Apr 8 15:48:05 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Tue, 08 Apr 2014 12:48:05 -0700 Subject: [jbosstools-dev] Upcoming change to target-platform: m2eclipse-egit In-Reply-To: <5343F444.1060103@redhat.com> References: <5343F444.1060103@redhat.com> Message-ID: <53445275.6000303@exadel.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140408/d1608145/attachment.html From nboldt at redhat.com Tue Apr 8 23:53:16 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 08 Apr 2014 23:53:16 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta1b bits available for QE testing Message-ID: <5344C42C.9040103@redhat.com> 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/staging/JBossTools-4.2.0.Beta1b.core/ * http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Beta1b.coretests/ * http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Beta1b.hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Beta1b.webtools/ Builds: * http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1b.core/2014-04-08_19-15-41-B105 * http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1b.coretests/2014-04-08_19-15-41-B91 * http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1b.hibernatetools/2014-04-08_19-49-44-B47 * http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1b.webtools/2014-04-08_19-49-45-B97 JBoss Central: * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta2-SNAPSHOT/ (upcoming milestone) To test the upcoming 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.2.0.Beta1b/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta1b/ Target Platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta1 (upcoming milestone) Until the above target platform site is released, you will need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) New + Noteworthy (subject to change): * http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstools-documentation/master/whatsnew/index.html * http://docs.jboss.org/tools/whatsnew/ Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Changes prompting this respin-b are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-b%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%228.0.0.Beta1%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.2.0.Beta1%22%29%29%29 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From p.g.richardson at phantomjinx.co.uk Fri Apr 11 10:55:10 2014 From: p.g.richardson at phantomjinx.co.uk (phantomjinx) Date: Fri, 11 Apr 2014 15:55:10 +0100 Subject: [jbosstools-dev] Replacement of deprecated teiid runtime client plugins Message-ID: <5348024E.30207@phantomjinx.co.uk> Afternoon all, As some of you may know, for Teiid Designer, I have been working over the last few months on a single teiid-runtime-client plugin that replaces the current 3 (and was soon to be more!) versioned teiid client plugins. The aims of the single plugin were: * Forking the teiid codebase and importing as a git submodule was proving unsustainable and fast becoming unmanagable hence a single plugin contained in (and maintained by Designer devs) was preferred; * The plugin should allow Designer to perform local sql parsing, resolving and validation of vdb models, as well as connecting/deploying/undeploying to all teiid instances at version 7.7+; * A single plugin where 90% of the teiid client codebase is the same should be able to handle, with the help of annotations and version checks, the 10% of differences between teiid versions; * Only where absolutely necessary should actual different classes be created that are teiid version-specific, eg. Teiid7Parser, Teiid8Parser; Thus, the single plugin is backward compatible (but then most of teiid is already backward compatible!) but it should also be forward limiting in that validating teiid v8 sql syntax against a teiid v7 version should correctly fail. Currently, the plugin supports up to teiid v8.7.0.CR2 and will support 8.7.0.Final upon its release. At this point, the plugin is being soak tested and I have now included it in nightly builds to allow people to play with it / find bugs and otherwise spot whatevers bits I have missed. Hope that is clear but any questions do not hesitate to ask. Regards PGR -- Paul Richardson * p.g.richardson at phantomjinx.co.uk * p.g.richardson at redhat.com * pgrichardson at linux.com "I know exactly who reads the papers ... * The Daily Mirror is read by people who think they run the country. * The Guardian is read by people who think they ought to run the country. * The Times is read by people who do actually run the country. * The Daily Mail is read by the wives of the people who run the country. * The Financial Times is read by the people who own the country. * The Morning Star is read by the people who think the country ought to be run by another country. * The Daily Telegraph is read by the people who think it is." Jim Hacker, Yes Minister From rcernich at redhat.com Fri Apr 11 12:31:11 2014 From: rcernich at redhat.com (Rob Cernich) Date: Fri, 11 Apr 2014 12:31:11 -0400 (EDT) Subject: [jbosstools-dev] Replacement of deprecated teiid runtime client plugins In-Reply-To: <5348024E.30207@phantomjinx.co.uk> References: <5348024E.30207@phantomjinx.co.uk> Message-ID: <1410172734.3431047.1397233871563.JavaMail.zimbra@redhat.com> Great work Paul! ----- Original Message ----- > Afternoon all, > > As some of you may know, for Teiid Designer, I have been working over the > last few months on a > single teiid-runtime-client plugin that replaces the current 3 (and was soon > to be more!) > versioned teiid client plugins. The aims of the single plugin were: > > * Forking the teiid codebase and importing as a git submodule was proving > unsustainable and fast > becoming unmanagable hence a single plugin contained in (and maintained by > Designer devs) was > preferred; > > * The plugin should allow Designer to perform local sql parsing, resolving > and validation of vdb > models, as well as connecting/deploying/undeploying to all teiid instances at > version 7.7+; > > * A single plugin where 90% of the teiid client codebase is the same should > be able to handle, > with the help of annotations and version checks, the 10% of differences > between teiid versions; > > * Only where absolutely necessary should actual different classes be created > that are teiid > version-specific, eg. Teiid7Parser, Teiid8Parser; > > Thus, the single plugin is backward compatible (but then most of teiid is > already backward > compatible!) but it should also be forward limiting in that validating teiid > v8 sql syntax against > a teiid v7 version should correctly fail. > > Currently, the plugin supports up to teiid v8.7.0.CR2 and will support > 8.7.0.Final upon its > release. At this point, the plugin is being soak tested and I have now > included it in nightly > builds to allow people to play with it / find bugs and otherwise spot > whatevers bits I have missed. > > Hope that is clear but any questions do not hesitate to ask. > > Regards > > PGR > > -- > Paul Richardson > > * p.g.richardson at phantomjinx.co.uk > * p.g.richardson at redhat.com > * pgrichardson at linux.com > > "I know exactly who reads the papers ... > > * The Daily Mirror is read by people who think they run the country. > * The Guardian is read by people who think they ought to run the country. > * The Times is read by people who do actually run the country. > * The Daily Mail is read by the wives of the people who run the country. > * The Financial Times is read by the people who own the country. > * The Morning Star is read by the people who think the country ought to be > run by another country. > * The Daily Telegraph is read by the people who think it is." > > Jim Hacker, Yes Minister > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > From manderse at redhat.com Fri Apr 11 13:28:36 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Apr 2014 19:28:36 +0200 Subject: [jbosstools-dev] Replacement of deprecated teiid runtime client plugins In-Reply-To: <5348024E.30207@phantomjinx.co.uk> References: <5348024E.30207@phantomjinx.co.uk> Message-ID: <41A74629-90E5-4BA3-AA8C-11FA8394E810@redhat.com> This sounds amazing! Got links to the code ? about going from 3 to 1 plugins we need to check p2 metadata is right to avoid issues. Awesome! this week turned out alright :) /max > Afternoon all, > > As some of you may know, for Teiid Designer, I have been working over > the last few months on a > single teiid-runtime-client plugin that replaces the current 3 (and > was soon to be more!) > versioned teiid client plugins. The aims of the single plugin were: > > * Forking the teiid codebase and importing as a git submodule was > proving unsustainable and fast > becoming unmanagable hence a single plugin contained in (and > maintained by Designer devs) was > preferred; > > * The plugin should allow Designer to perform local sql parsing, > resolving and validation of vdb > models, as well as connecting/deploying/undeploying to all teiid > instances at version 7.7+; > > * A single plugin where 90% of the teiid client codebase is the same > should be able to handle, > with the help of annotations and version checks, the 10% of > differences between teiid versions; > > * Only where absolutely necessary should actual different classes be > created that are teiid > version-specific, eg. Teiid7Parser, Teiid8Parser; > > Thus, the single plugin is backward compatible (but then most of teiid > is already backward > compatible!) but it should also be forward limiting in that validating > teiid v8 sql syntax against > a teiid v7 version should correctly fail. > > Currently, the plugin supports up to teiid v8.7.0.CR2 and will support > 8.7.0.Final upon its > release. At this point, the plugin is being soak tested and I have now > included it in nightly > builds to allow people to play with it / find bugs and otherwise spot > whatevers bits I have missed. > > Hope that is clear but any questions do not hesitate to ask. > > Regards > > PGR > > -- > Paul Richardson > > * p.g.richardson at phantomjinx.co.uk > * p.g.richardson at redhat.com > * pgrichardson at linux.com > > "I know exactly who reads the papers ... > > * The Daily Mirror is read by people who think they run the country. > * The Guardian is read by people who think they ought to run the > country. > * The Times is read by people who do actually run the country. > * The Daily Mail is read by the wives of the people who run the > country. > * The Financial Times is read by the people who own the country. > * The Morning Star is read by the people who think the country ought > to be run by another country. > * The Daily Telegraph is read by the people who think it is." > > Jim Hacker, Yes Minister > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From p.g.richardson at phantomjinx.co.uk Fri Apr 11 14:46:30 2014 From: p.g.richardson at phantomjinx.co.uk (phantomjinx) Date: Fri, 11 Apr 2014 19:46:30 +0100 Subject: [jbosstools-dev] Replacement of deprecated teiid runtime client plugins In-Reply-To: <41A74629-90E5-4BA3-AA8C-11FA8394E810@redhat.com> References: <5348024E.30207@phantomjinx.co.uk> <41A74629-90E5-4BA3-AA8C-11FA8394E810@redhat.com> Message-ID: <53483886.3090006@phantomjinx.co.uk> Thanks! ... stuff that might be of interest * The single runtime client plugin: ** https://github.com/Teiid-Designer/teiid-designer/tree/master/plugins/teiid/org.teiid.runtime.client * @Since annotation for methods that only apply to later teiid versions (@Removed and @Updated also available) ** https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org.teiid.designer.spi/src/org/teiid/designer/annotation/Since.java * AnnotationUtils class for checking applicability of code, ie. classes, methods and enums ** https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org.teiid.designer.spi/src/org/teiid/designer/annotation/AnnotationUtils.java * Example of an interface with a @Since annotation (see deploy method) ** https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/teiid/org.teiid.runtime.client/admin/org/teiid/adminapi/Admin.java * Example of checking the teiid version and thereby giving a different result (eg. setShortNameOnly method) ** https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/teiid/org.teiid.runtime.client/engine/org/teiid/query/sql/visitor/SQLStringVisitor.java * Example of using @Since annotation in enumerator and only returning those enum values conforming to a specific teiid version ** Note. This is an enum used extensively in Teiid and reflection is quite slow hence caching the results of the getValues method is preferred ** https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/teiid/org.teiid.runtime.client/common-core/org/teiid/core/types/DataTypeManagerService.java >> about going from 3 to 1 plugins we need to heck p2 metadata is right to avoid issues. Can you elaborate on this as not totally sure what your thinking is (it is Friday after all!) Cheers PGR On 04/11/2014 06:28 PM, Max Rydahl Andersen wrote: > This sounds amazing! Got links to the code ? > > about going from 3 to 1 plugins we need to heck p2 metadata is right to avoid issues. > > Awesome! this week turned out alright :) > > /max > >> Afternoon all, >> >> As some of you may know, for Teiid Designer, I have been working over the last few months on a >> single teiid-runtime-client plugin that replaces the current 3 (and was soon to be more!) >> versioned teiid client plugins. The aims of the single plugin were: >> >> * Forking the teiid codebase and importing as a git submodule was proving unsustainable and fast >> becoming unmanagable hence a single plugin contained in (and maintained by Designer devs) was >> preferred; >> >> * The plugin should allow Designer to perform local sql parsing, resolving and validation of vdb >> models, as well as connecting/deploying/undeploying to all teiid instances at version 7.7+; >> >> * A single plugin where 90% of the teiid client codebase is the same should be able to handle, >> with the help of annotations and version checks, the 10% of differences between teiid versions; >> >> * Only where absolutely necessary should actual different classes be created that are teiid >> version-specific, eg. Teiid7Parser, Teiid8Parser; >> >> Thus, the single plugin is backward compatible (but then most of teiid is already backward >> compatible!) but it should also be forward limiting in that validating teiid v8 sql syntax against >> a teiid v7 version should correctly fail. >> >> Currently, the plugin supports up to teiid v8.7.0.CR2 and will support 8.7.0.Final upon its >> release. At this point, the plugin is being soak tested and I have now included it in nightly >> builds to allow people to play with it / find bugs and otherwise spot whatevers bits I have missed. >> >> Hope that is clear but any questions do not hesitate to ask. >> >> Regards >> >> PGR >> >> -- >> Paul Richardson >> >> * p.g.richardson at phantomjinx.co.uk >> * p.g.richardson at redhat.com >> * pgrichardson at linux.com >> >> "I know exactly who reads the papers ... >> >> * The Daily Mirror is read by people who think they run the country. >> * The Guardian is read by people who think they ought to run the country. >> * The Times is read by people who do actually run the country. >> * The Daily Mail is read by the wives of the people who run the country. >> * The Financial Times is read by the people who own the country. >> * The Morning Star is read by the people who think the country ought to be run by another country. >> * The Daily Telegraph is read by the people who think it is." >> >> Jim Hacker, Yes Minister >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen -- Paul Richardson * p.g.richardson at phantomjinx.co.uk * p.g.richardson at redhat.com * pgrichardson at linux.com "I know exactly who reads the papers ... * The Daily Mirror is read by people who think they run the country. * The Guardian is read by people who think they ought to run the country. * The Times is read by people who do actually run the country. * The Daily Mail is read by the wives of the people who run the country. * The Financial Times is read by the people who own the country. * The Morning Star is read by the people who think the country ought to be run by another country. * The Daily Telegraph is read by the people who think it is." Jim Hacker, Yes Minister From rcernich at redhat.com Fri Apr 11 14:58:05 2014 From: rcernich at redhat.com (Rob Cernich) Date: Fri, 11 Apr 2014 14:58:05 -0400 (EDT) Subject: [jbosstools-dev] Replacement of deprecated teiid runtime client plugins In-Reply-To: <53483886.3090006@phantomjinx.co.uk> References: <5348024E.30207@phantomjinx.co.uk> <41A74629-90E5-4BA3-AA8C-11FA8394E810@redhat.com> <53483886.3090006@phantomjinx.co.uk> Message-ID: <1353898419.3504719.1397242685030.JavaMail.zimbra@redhat.com> > >> about going from 3 to 1 plugins we need to heck p2 metadata is right to > >> avoid issues. > > Can you elaborate on this as not totally sure what your thinking is (it is > Friday after all!) > I suspect Max is talking about ensuring the feature information is correct so that the other two plugins get uninstalled during an update (i.e. same feature, one included plugin vs. three). Or that p2 info is added so that updates are successful, e.g. this feature also provides "blah." Simply put, you should be able to update an existing install that has the three plugins, with the new version that has one plugin, without error. From manderse at redhat.com Fri Apr 11 15:49:51 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Apr 2014 21:49:51 +0200 Subject: [jbosstools-dev] Replacement of deprecated teiid runtime client plugins In-Reply-To: <1353898419.3504719.1397242685030.JavaMail.zimbra@redhat.com> References: <5348024E.30207@phantomjinx.co.uk> <41A74629-90E5-4BA3-AA8C-11FA8394E810@redhat.com> <53483886.3090006@phantomjinx.co.uk> <1353898419.3504719.1397242685030.JavaMail.zimbra@redhat.com> Message-ID: On 11 Apr 2014, at 20:58, Rob Cernich wrote: >>>> about going from 3 to 1 plugins we need to heck p2 metadata is >>>> right to >>>> avoid issues. >> >> Can you elaborate on this as not totally sure what your thinking is >> (it is >> Friday after all!) >> > > I suspect Max is talking about ensuring the feature information is > correct so that the other two plugins get uninstalled during an update > (i.e. same feature, one included plugin vs. three). Or that p2 info > is added so that updates are successful, e.g. this feature also > provides "blah." Simply put, you should be able to update an existing > install that has the three plugins, with the new version that has one > plugin, without error. Yes. It should "just" work but depending on what you put in feature/plugins it might not be. i.e. if your plugin is somehow referenced by optional dependencies the plugin can actually still be active on restart after first install. Just needs testing/verificaiton. /max http://about.me/maxandersen From nboldt at redhat.com Fri Apr 11 16:37:38 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 11 Apr 2014 16:37:38 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Please triage unresolved issues for Beta1 Message-ID: <53485292.5090705@redhat.com> There are currently 16 unresolved issues [1] with a fixVersion of 4.2.0.Beta1 or 8.0.0.Beta1. [1] https://issues.jboss.org/issues/?jql=%28project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212323828%22%29%20OR%20%28project%20%3D%20JBDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212323832%22%29 * If they're not done, please bump these to Beta2. * If they're done and need to be verified by QE, please Resolve them. * If they're done and nothing more needs to be done to verify them, please Close them. Thanks! -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Apr 11 19:20:44 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 11 Apr 2014 19:20:44 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] Message-ID: <534878CC.2040803@redhat.com> Project leads, please tag your projects! co jbosstools-4.2.0.Beta1x git tag jbosstools-4.2.0.Beta1 git push origin jbosstools-4.2.0.Beta1 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Apr 11 19:36:17 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 11 Apr 2014 19:36:17 -0400 Subject: [jbosstools-dev] JBoss Tools jbosstools-4.2.0.Beta1 is now available. Message-ID: <53487C71.3000309@redhat.com> This is a development release aimed at Eclipse 4.4.M6 (Luna M6) users. Eclipse Marketplace: Soon, there will be an Eclipse Marketplace entry here: https://marketplace.eclipse.org/content/jboss-tools-luna Update Site: http://download.jboss.org/jbosstools/updates/development/luna/ Update Site Zips: For now, the zips can be found here: * http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/ * http://download.jboss.org/jbosstools/builds/development/sf.net/4.2.0.Beta1/ Next week they'll be here: * http://tools.jboss.org/downloads/overview.html * http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html Installation instructions: * http://tools.jboss.org/downloads/installation.html JBoss Central: This release includes changes to JBoss Central. To see these updates, launch Eclipse with this extra -vmarg in your eclipse.ini: * -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/luna/jbosstools-directory.xml New + Noteworthy: Subject to change, the latest N&N is here: * http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstools-documentation/master/whatsnew/index.html * http://docs.jboss.org/tools/whatsnew/ Schedule / Upcoming Releases: * https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From adietish at redhat.com Mon Apr 14 03:03:42 2014 From: adietish at redhat.com (=?ISO-8859-1?Q?Andr=E9_Dietisheim?=) Date: Mon, 14 Apr 2014 09:03:42 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] In-Reply-To: <534878CC.2040803@redhat.com> References: <534878CC.2040803@redhat.com> Message-ID: <534B884E.1000603@redhat.com> On 04/12/2014 01:20 AM, Nick Boldt wrote: > git push origin jbosstools-4.2.0.Beta1 done for openshift. From bfitzpat at redhat.com Mon Apr 14 08:38:11 2014 From: bfitzpat at redhat.com (Brian Fitzpatrick) Date: Mon, 14 Apr 2014 08:38:11 -0400 (EDT) Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] In-Reply-To: <534B884E.1000603@redhat.com> References: <534878CC.2040803@redhat.com> <534B884E.1000603@redhat.com> Message-ID: <615015735.4321538.1397479091927.JavaMail.zimbra@redhat.com> Done for webservices _______________________________ Brian Fitzpatrick (aka "Fitz") Senior Software Engineer, SOA-P JBoss by Red Hat ----- Original Message ----- From: "Andr? Dietisheim" To: "Nick Boldt" , jbosstools-dev at lists.jboss.org Sent: Monday, April 14, 2014 1:03:42 AM Subject: Re: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] On 04/12/2014 01:20 AM, Nick Boldt wrote: > git push origin jbosstools-4.2.0.Beta1 done for openshift. _______________________________________________ jbosstools-dev mailing list jbosstools-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev From xcoulon at redhat.com Mon Apr 14 09:07:41 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Mon, 14 Apr 2014 15:07:41 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] In-Reply-To: <615015735.4321538.1397479091927.JavaMail.zimbra@redhat.com> References: <534878CC.2040803@redhat.com> <534B884E.1000603@redhat.com> <615015735.4321538.1397479091927.JavaMail.zimbra@redhat.com> Message-ID: <0A218B6C-1BEF-485E-BFB8-B741158F4CD2@redhat.com> Done for LiveReload. Best regards, /Xavier On 14 Apr 2014, at 14:38, Brian Fitzpatrick wrote: > Done for webservices > > _______________________________ > Brian Fitzpatrick (aka "Fitz") > Senior Software Engineer, SOA-P > JBoss by Red Hat > > ----- Original Message ----- > From: "Andr? Dietisheim" > To: "Nick Boldt" , jbosstools-dev at lists.jboss.org > Sent: Monday, April 14, 2014 1:03:42 AM > Subject: Re: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] > > On 04/12/2014 01:20 AM, Nick Boldt wrote: >> git push origin jbosstools-4.2.0.Beta1 > done for openshift. > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140414/864392f1/attachment.html From fbricon at redhat.com Mon Apr 14 09:14:50 2014 From: fbricon at redhat.com (Fred Bricon) Date: Mon, 14 Apr 2014 15:14:50 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] In-Reply-To: <0A218B6C-1BEF-485E-BFB8-B741158F4CD2@redhat.com> References: <534878CC.2040803@redhat.com> <534B884E.1000603@redhat.com> <615015735.4321538.1397479091927.JavaMail.zimbra@redhat.com> <0A218B6C-1BEF-485E-BFB8-B741158F4CD2@redhat.com> Message-ID: <534BDF4A.8060005@redhat.com> Central done Le 14/04/2014 15:07, Xavier Coulon a ?crit : > Done for LiveReload. > > Best regards, > /Xavier > > > > On 14 Apr 2014, at 14:38, Brian Fitzpatrick > wrote: > >> Done for webservices >> >> _______________________________ >> Brian Fitzpatrick (aka "Fitz") >> Senior Software Engineer, SOA-P >> JBoss by Red Hat >> >> ----- Original Message ----- >> From: "Andr? Dietisheim" > > >> To: "Nick Boldt" >, >> jbosstools-dev at lists.jboss.org >> Sent: Monday, April 14, 2014 1:03:42 AM >> Subject: Re: [jbosstools-dev] ACTION REQUIRED: Project leads, please >> tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag >> jbosstools-4.2.0.Beta1 ] >> >> On 04/12/2014 01:20 AM, Nick Boldt wrote: >>> git push origin jbosstools-4.2.0.Beta1 >> done for openshift. >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140414/cebbc3e6/attachment.html From snjeza.peco at gmail.com Mon Apr 14 09:28:19 2014 From: snjeza.peco at gmail.com (Snjezana Peco) Date: Mon, 14 Apr 2014 15:28:19 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] In-Reply-To: <534878CC.2040803@redhat.com> References: <534878CC.2040803@redhat.com> Message-ID: <534BE273.7080708@gmail.com> Done for arquillian, birt and portlet. Snjeza On 4/12/2014 1:20 AM, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.2.0.Beta1x > git tag jbosstools-4.2.0.Beta1 > git push origin jbosstools-4.2.0.Beta1 > From mistria at redhat.com Mon Apr 14 13:02:42 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 14 Apr 2014 19:02:42 +0200 Subject: [jbosstools-dev] JBoss Tools 4.2.0.Beta1 is now available. Message-ID: <534C14B2.8020806@redhat.com> This is a development release aimed at Eclipse 4.4.M6 (Luna M6) users. Eclipse Marketplace: https://marketplace.eclipse.org/content/jboss-tools-luna Update Site: http://download.jboss.org/jbosstools/updates/development/luna/ Update Site Zips: * http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/ * http://download.jboss.org/jbosstools/builds/development/sf.net/4.2.0.Beta1/ Installation instructions: * http://tools.jboss.org/downloads/installation.html JBoss Central: This release includes changes to JBoss Central. To see these updates, launch Eclipse with this extra -vmarg in your eclipse.ini: * -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/luna/jbosstools-directory.xml New + Noteworthy: Subject to change, the latest N&N is here: * http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstools-documentation/master/whatsnew/index.html * http://docs.jboss.org/tools/whatsnew/ Schedule / Upcoming Releases: * https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140414/c4347dff/attachment.html From koen.aers at jboss.com Tue Apr 15 02:59:50 2014 From: koen.aers at jboss.com (Koen Aers) Date: Tue, 15 Apr 2014 08:59:50 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta1x -> tag jbosstools-4.2.0.Beta1 ] In-Reply-To: <534878CC.2040803@redhat.com> References: <534878CC.2040803@redhat.com> Message-ID: <7DA694A5-51C6-4760-9BD8-2F1C1D0CB18C@jboss.com> Done for Forge and Hibernate Op 12-apr.-2014, om 01:20 heeft Nick Boldt het volgende geschreven: > Project leads, please tag your projects! > > co jbosstools-4.2.0.Beta1x > git tag jbosstools-4.2.0.Beta1 > git push origin jbosstools-4.2.0.Beta1 > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From manderse at redhat.com Fri Apr 18 19:06:24 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Sat, 19 Apr 2014 01:06:24 +0200 Subject: [jbosstools-dev] ATTENTION: jbosstools-website git history rewritten. Please re-clone Message-ID: Hey, A couple of errors got into the authors in jbosstools-website so to avoid too much problems I went ahead and did a filter-branch to fix these author mails before the repo gets used too much ;) I've merged all non-trivial PR's before this so that work is in master - but please make sure to either reclone the repository or do a git pull --force to get the latest/greatest. Sorry for the inconvenience - won't happen again ;) /max http://about.me/maxandersen From manderse at redhat.com Tue Apr 22 10:43:56 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 22 Apr 2014 16:43:56 +0200 Subject: [jbosstools-dev] simplified jira creation screen enabled on JBIDE Message-ID: <39DE130D-2BAE-4990-BC92-4643D3A522CF@redhat.com> Hey, JBIDE now is using simplified jira creation screen. This gives a much simpler experience for opening bugs but still allow committers/contributors to go to advanced tab to fill in more details. Note, that if you really just want all fields on one long screen even though you just need a small subset - you can click the "Configure Fields" in upper right corner to customise it how you like it to be. But for now for the non-advanced user the JBIDE creation screen is simpler. I'm trying to get this on JBDS too but there seems to be some challenges... Let me know if you love or hate this simplification. /max http://about.me/maxandersen From angelo.zerr at gmail.com Wed Apr 23 08:08:55 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Wed, 23 Apr 2014 14:08:55 +0200 Subject: [jbosstools-dev] tern.java forum Message-ID: Hi All, At first I would like to say you "Many thank's!" to interest you to tern.java (and tern.js) and for your contributions. It's a fantastic adventure fore me and I have a great luck to work with guys like you. I contact you because you are integrating tern.java (and AngularJS Eclipse) : * in JBoss Tools * in Liferay IDE * in Nodeclipse. I hope that our collaboration will show that tern.js is the killer javascript inference engine. I contact you, because I think it's important that we share our idea about tern.java (and tern.js) in a commons forum. So my idea is to create a Google Groups "tern.java" for that. I would like to explain more my roadmap (like Tern Tooling https://github.com/angelozerr/tern.java/wiki/Tern-Toolings to provide Eclipse wizards to create JSON type definitions, server plugin and CodeMirror/Ace/Orion editor plugged with tern). What do you think about this idea of Google Groups "tern.java"? Regards Angelo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140423/e70746c7/attachment.html From manderse at redhat.com Wed Apr 23 08:20:23 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 23 Apr 2014 14:20:23 +0200 Subject: [jbosstools-dev] tern.java forum In-Reply-To: References: Message-ID: On 23 Apr 2014, at 14:08, Angelo zerr wrote: > Hi All, > > At first I would like to say you "Many thank's!" to interest you to > tern.java (and tern.js) and for your contributions. It's a fantastic > adventure fore me and I have a great luck to work with guys like you. > > I contact you because you are integrating tern.java (and AngularJS > Eclipse) > : > > * in JBoss Tools > * in Liferay IDE > * in Nodeclipse. > > I hope that our collaboration will show that tern.js is the killer > javascript inference engine. > > I contact you, because I think it's important that we share our idea > about > tern.java (and tern.js) in a commons forum. So my idea is to create a > Google Groups "tern.java" for that. > > I would like to explain more my roadmap (like Tern Tooling > https://github.com/angelozerr/tern.java/wiki/Tern-Toolings to provide > Eclipse wizards to create JSON type definitions, server plugin and > CodeMirror/Ace/Orion editor plugged with tern). I don't see this as something that make sense in tern.java core - but if its just additions that can be installed separately fine by me. > What do you think about this idea of Google Groups "tern.java"? sounds like a good idea - send link when you got it ? :) > > Regards Angelo > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From angelo.zerr at gmail.com Wed Apr 23 08:26:11 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Wed, 23 Apr 2014 14:26:11 +0200 Subject: [jbosstools-dev] tern.java forum In-Reply-To: References: Message-ID: Hi Max, I would like to explain more my roadmap (like Tern Tooling >> https://github.com/angelozerr/tern.java/wiki/Tern-Toolings to provide >> Eclipse wizards to create JSON type definitions, server plugin and >> CodeMirror/Ace/Orion editor plugged with tern). >> > > I don't see this as something that make sense in tern.java core - but if > its just additions that > can be installed separately fine by me. We have discussed about that. It's exactly that I have done. There are 2 plugins : * tern.eclipse.ide.tools.core * tern.eclipse.ide.tools.ui and when you install tern.java you can select or not "Tern Tooling" in the update site. > > > What do you think about this idea of Google Groups "tern.java"? >> > > sounds like a good idea - send link when you got it ? :) > Cool! I will do it. > >> Regards Angelo >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > > > /max > http://about.me/maxandersen > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140423/29e39da6/attachment.html From paul.verest at live.com Wed Apr 23 09:34:06 2014 From: paul.verest at live.com (Paul Verest) Date: Wed, 23 Apr 2014 13:34:06 +0000 Subject: [jbosstools-dev] tern.java forum In-Reply-To: References: Message-ID: Hello Everybody There is really nice team gathering about tern.java Let's continue to use GitHub issues for discussion - it is more organized with distinct issues - it is real time - issues and code can be easily referenced, images just drag-and-dropped - it uses markdown that can be easily copied to wiki or README - it spams less (I have separate emailbox for GitHub notifications enide.github at gmail.com but mostly check on https://github.com/notifications ) - Google groups are recently blocked in China (before they were terribly slow, there is no Google servers in China) - (for organization owners) recently GitHub even gives view stats like Google Analytics for pages tern.java Google group / forum may happily continue to exist as place for users to ask questions - how to use - have long and non-constructive discussions (while issues on GitHub should be closeable, i.e. there is to be some result by each issue) Date: Wed, 23 Apr 2014 14:08:55 +0200 Subject: tern.java forum From: angelo.zerr at gmail.com To: jbosstools-dev at lists.jboss.org; pascal.leclercq at gmail.com; gregory.amerson at liferay.com; paul.verest at live.com; marijnh at gmail.com Hi All, At first I would like to say you "Many thank's!" to interest you to tern.java (and tern.js) and for your contributions. It's a fantastic adventure fore me and I have a great luck to work with guys like you. I contact you because you are integrating tern.java (and AngularJS Eclipse) : * in JBoss Tools * in Liferay IDE * in Nodeclipse. I hope that our collaboration will show that tern.js is the killer javascript inference engine. I contact you, because I think it's important that we share our idea about tern.java (and tern.js) in a commons forum. So my idea is to create a Google Groups "tern.java" for that. I would like to explain more my roadmap (like Tern Tooling https://github.com/angelozerr/tern.java/wiki/Tern-Toolings to provide Eclipse wizards to create JSON type definitions, server plugin and CodeMirror/Ace/Orion editor plugged with tern). What do you think about this idea of Google Groups "tern.java"? Regards Angelo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140423/2821b49a/attachment.html From angelo.zerr at gmail.com Thu Apr 24 04:35:02 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Thu, 24 Apr 2014 10:35:02 +0200 Subject: [jbosstools-dev] tern.java forum In-Reply-To: References: Message-ID: Hi Paul, I didn't know that Google Group was a problem in China. Ok I will continue to create issues on GitHub to explain my ideas. Regards Angelo 2014-04-23 15:34 GMT+02:00 Paul Verest : > Hello Everybody > > There is really nice team gathering about tern.java > > > Let's continue to use GitHub issues for discussion > - it is more organized with distinct issues > - it is real time > - issues and code can be easily referenced, images just drag-and-dropped > - it uses markdown that can be easily copied to wiki or README > - it spams less (I have separate emailbox for GitHub notifications > enide.github at gmail.com but mostly check on > https://github.com/notifications ) > - Google groups are recently blocked in China (before they were terribly > slow, there is no Google servers in China) > - (for organization owners) recently GitHub even gives view stats like > Google Analytics for pages > > tern.java Google group / forum may happily continue to exist as place for > users to ask questions > - how to use > - have long and non-constructive discussions (while issues on GitHub > should be closeable, i.e. there is to be some result by each issue) > > > ------------------------------ > Date: Wed, 23 Apr 2014 14:08:55 +0200 > Subject: tern.java forum > From: angelo.zerr at gmail.com > To: jbosstools-dev at lists.jboss.org; pascal.leclercq at gmail.com; > gregory.amerson at liferay.com; paul.verest at live.com; marijnh at gmail.com > > > Hi All, > > At first I would like to say you "Many thank's!" to interest you to > tern.java (and tern.js) and for your contributions. It's a fantastic > adventure fore me and I have a great luck to work with guys like you. > > I contact you because you are integrating tern.java (and AngularJS > Eclipse) : > > * in JBoss Tools > * in Liferay IDE > * in Nodeclipse. > > I hope that our collaboration will show that tern.js is the killer > javascript inference engine. > > I contact you, because I think it's important that we share our idea about > tern.java (and tern.js) in a commons forum. So my idea is to create a > Google Groups "tern.java" for that. > > I would like to explain more my roadmap (like Tern Tooling > https://github.com/angelozerr/tern.java/wiki/Tern-Toolings to provide > Eclipse wizards to create JSON type definitions, server plugin and > CodeMirror/Ace/Orion editor plugged with tern). > > What do you think about this idea of Google Groups "tern.java"? > > Regards Angelo > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140424/485bca5a/attachment-0001.html From manderse at redhat.com Thu Apr 24 18:19:44 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 25 Apr 2014 00:19:44 +0200 Subject: [jbosstools-dev] external contributor interested in making browsersim work with webdriver/arquillian Message-ID: <7D69BD85-6557-4BB6-8719-87EC6DFEA367@redhat.com> Hey Konstantin/Ilya, Could you look at this question from Alex S. https://community.jboss.org/thread/240227 ? /max http://about.me/maxandersen From manderse at redhat.com Sun Apr 27 03:16:14 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Sun, 27 Apr 2014 09:16:14 +0200 Subject: [jbosstools-dev] Testing the patches from https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 In-Reply-To: <53581FEE.5010801@redhat.com> References: <53581FEE.5010801@redhat.com> Message-ID: <8E883267-71EF-4C2D-B328-A3C39340152D@redhat.com> Snjezana - thanks for the writeup but it would be way better to attach these files in a jira and then send link to the mailing list since mailman will not (always) allow the binaries to go through for space and security concerns. /max > Hi, > > Requirements: Fedora 20 64-bit or some other distribution that > includes GTK3 >= 3.10 > > 1) download Eclipse I-build - > http://download.eclipse.org/eclipse/downloads/drops4/I20140422-0800/ > 2) install it > 3) copy the attached eclipse_1603.so to > ${ECLIPSE_HOME}/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140414-2101/ > GTK >= 3.10 is enabled by this library. > 4) copy the attached > org.eclipse.swt.gtk.linux.x86_64_3.103.0.v20140415-1109.jar to > ${ECLIPSE_HOME}/plugins > This plugin contains the patches from > https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > 5) call "export SWT_GTK3=1" (optional) > 6) start Eclipse > > If Eclipse doesn't start, copy the attached *4424.so libraries to > ~/.swt/lib/linux/x86_64/ > > You will encounter the issue described in > https://bugs.eclipse.org/bugs/show_bug.cgi?id=427511 (the issue hasn't > been fixed yet). If you can't reproduce it, you don't use GTK >= 3.10. > However, you won't face any issues described in > https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127. If you skip step > 4, all views/editors/tabs will be empty. > > Snjeza > > [eclipse_1603.so] > > [libswt-atk-gtk-4424.so] > > [libswt-cairo-gtk-4424.so] > > [libswt-gtk-4424.so] > > [libswt-pi3-gtk-4424.so] > > [libswt-pi-gtk-4424.so] > > [org.eclipse.swt.gtk.linux.x86_64_3.103.0.v20140415-1109.jar] /max http://about.me/maxandersen From mmurray at redhat.com Mon Apr 28 01:29:30 2014 From: mmurray at redhat.com (Michelle Murray) Date: Mon, 28 Apr 2014 01:29:30 -0400 (EDT) Subject: [jbosstools-dev] simplified jira creation screen enabled on JBIDE In-Reply-To: <39DE130D-2BAE-4990-BC92-4643D3A522CF@redhat.com> References: <39DE130D-2BAE-4990-BC92-4643D3A522CF@redhat.com> Message-ID: <516221472.10820917.1398662970384.JavaMail.zimbra@redhat.com> +1 to the simplified version it makes clear which fields the reporter must complete versus which should be left to the assignee ----- Original Message ----- > From: "Max Rydahl Andersen" > To: "jbosstools-dev jbosstools-dev" > Sent: Wednesday, 23 April, 2014 12:43:56 AM > Subject: [jbosstools-dev] simplified jira creation screen enabled on JBIDE > Hey, > JBIDE now is using simplified jira creation screen. > This gives a much simpler experience for opening bugs but still allow > committers/contributors to go to advanced tab to fill in more details. > Note, that if you really just want all fields on one long screen even > though you just need a small subset - you can click the "Configure > Fields" in upper right corner to customise it how you like it to be. > But for now for the non-advanced user the JBIDE creation screen is > simpler. > I'm trying to get this on JBDS too but there seems to be some > challenges... > Let me know if you love or hate this simplification. > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140428/719c2bf2/attachment.html From snjezana.peco at redhat.com Mon Apr 28 11:00:53 2014 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Mon, 28 Apr 2014 17:00:53 +0200 Subject: [jbosstools-dev] Testing the patches from https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 In-Reply-To: <8E883267-71EF-4C2D-B328-A3C39340152D@redhat.com> References: <53581FEE.5010801@redhat.com> <8E883267-71EF-4C2D-B328-A3C39340152D@redhat.com> Message-ID: <535E6D25.1050200@redhat.com> The patches from https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 have been merged into master. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127#c59 They will be included into the next build. I will also try to fix https://bugs.eclipse.org/bugs/show_bug.cgi?id=427480 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=427511. I have already fixed them in my tree, but there is yet another minor issue related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=427480. Namely, tree items sometimes are bolded. Snjeza On 4/27/2014 9:16 AM, Max Rydahl Andersen wrote: > Snjezana - thanks for the writeup but it would be way better to attach > these files in a jira and then send link to the mailing list since > mailman will not (always) allow the binaries to go through for space > and security concerns. > > /max > >> Hi, >> >> Requirements: Fedora 20 64-bit or some other distribution that >> includes GTK3 >= 3.10 >> >> 1) download Eclipse I-build - >> http://download.eclipse.org/eclipse/downloads/drops4/I20140422-0800/ >> 2) install it >> 3) copy the attached eclipse_1603.so to >> ${ECLIPSE_HOME}/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140414-2101/ >> GTK >= 3.10 is enabled by this library. >> 4) copy the attached >> org.eclipse.swt.gtk.linux.x86_64_3.103.0.v20140415-1109.jar to >> ${ECLIPSE_HOME}/plugins >> This plugin contains the patches from >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 >> 5) call "export SWT_GTK3=1" (optional) >> 6) start Eclipse >> >> If Eclipse doesn't start, copy the attached *4424.so libraries to >> ~/.swt/lib/linux/x86_64/ >> >> You will encounter the issue described in >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=427511 (the issue >> hasn't been fixed yet). If you can't reproduce it, you don't use GTK >> >= 3.10. >> However, you won't face any issues described in >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127. If you skip >> step 4, all views/editors/tabs will be empty. >> >> Snjeza >> >> [eclipse_1603.so] >> >> [libswt-atk-gtk-4424.so] >> >> [libswt-cairo-gtk-4424.so] >> >> [libswt-gtk-4424.so] >> >> [libswt-pi3-gtk-4424.so] >> >> [libswt-pi-gtk-4424.so] >> >> [org.eclipse.swt.gtk.linux.x86_64_3.103.0.v20140415-1109.jar] > > > /max > http://about.me/maxandersen From sbharadw at redhat.com Tue Apr 29 04:49:43 2014 From: sbharadw at redhat.com (Supriya Bharadwaj) Date: Tue, 29 Apr 2014 04:49:43 -0400 (EDT) Subject: [jbosstools-dev] Subscription to the list In-Reply-To: <613884035.6379937.1398761345930.JavaMail.zimbra@redhat.com> Message-ID: <919471173.6380094.1398761383953.JavaMail.zimbra@redhat.com> Hi, Can you please add me to the jbosstools-dev at lists or let me know the steps that I need to take to subscribe to the list? Thanks, Supriya Bharadwaj Red Hat Pune Phone: +91 20 3046 6774 Cell: +91 99 6047 7444 email: sbharadw at redhat.com irc: Supriya_ From angelo.zerr at gmail.com Tue Apr 29 05:22:01 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Tue, 29 Apr 2014 11:22:01 +0200 Subject: [jbosstools-dev] Replace json-simple by minimal-json in tern.java? Message-ID: Hi all, For your information, I would like to try to migrate from json-simple to minimal-json in tern.java (see https://github.com/angelozerr/tern.java/issues/59) Before doing that, I would like to know if it's a problem for you to change (again) your build if I can do the same feature with minimal-json. The reason for this migration is about : * even if json-simple works great, it seems not activated. * minimal-json belongs to Eclipse (Eclipse RAP) * minimal-json seems more optmized than json-simple (see benchmark at http://eclipsesource.com/blogs/2013/11/27/minimal-json-0-9-1-available-on-maven-central/ ) Are you OK with this migration (if I can do it)? Regards Angelo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140429/f6675b7c/attachment.html From manderse at redhat.com Tue Apr 29 08:54:12 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 29 Apr 2014 14:54:12 +0200 Subject: [jbosstools-dev] Replace json-simple by minimal-json in tern.java? In-Reply-To: References: Message-ID: <8BBDD73F-B1F2-416B-9804-8B9FF6767789@redhat.com> On 29 Apr 2014, at 11:22, Angelo zerr wrote: > Hi all, > > For your information, I would like to try to migrate from json-simple > to > minimal-json in tern.java (see > https://github.com/angelozerr/tern.java/issues/59) > > Before doing that, I would like to know if it's a problem for you to > change > (again) your build if I can do the same feature with minimal-json. The > reason for this migration is about : > > * even if json-simple works great, it seems not activated. > * minimal-json belongs to Eclipse (Eclipse RAP) does this mean it is available already as osgi bundle in a p2 repo ? Then that seems like a win ;) > * minimal-json seems more optmized than json-simple (see benchmark at > http://eclipsesource.com/blogs/2013/11/27/minimal-json-0-9-1-available-on-maven-central/ > ) > > Are you OK with this migration (if I can do it)? > > Regards Angelo > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From cdaley at redhat.com Tue Apr 29 09:24:28 2014 From: cdaley at redhat.com (Corey Daley) Date: Tue, 29 Apr 2014 09:24:28 -0400 (EDT) Subject: [jbosstools-dev] Subscription to the list In-Reply-To: <919471173.6380094.1398761383953.JavaMail.zimbra@redhat.com> References: <919471173.6380094.1398761383953.JavaMail.zimbra@redhat.com> Message-ID: <350807803.8764614.1398777868923.JavaMail.zimbra@redhat.com> You should be able to visit this link (https://lists.jboss.org/mailman/listinfo/jbosstools-dev) and enter your name and email address to join the mailing list. Corey Daley Senior Product Marketing Manager OpenShift | PaaS by Red Hat, Inc. www.openshift.com @openshift, @openshift_ops ----- Original Message ----- From: "Supriya Bharadwaj" To: jbosstools-dev at lists.jboss.org Sent: Tuesday, April 29, 2014 4:49:43 AM Subject: [jbosstools-dev] Subscription to the list Hi, Can you please add me to the jbosstools-dev at lists or let me know the steps that I need to take to subscribe to the list? Thanks, Supriya Bharadwaj Red Hat Pune Phone: +91 20 3046 6774 Cell: +91 99 6047 7444 email: sbharadw at redhat.com irc: Supriya_ _______________________________________________ jbosstools-dev mailing list jbosstools-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev From angelo.zerr at gmail.com Tue Apr 29 09:34:55 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Tue, 29 Apr 2014 15:34:55 +0200 Subject: [jbosstools-dev] Replace json-simple by minimal-json in tern.java? In-Reply-To: <8BBDD73F-B1F2-416B-9804-8B9FF6767789@redhat.com> References: <8BBDD73F-B1F2-416B-9804-8B9FF6767789@redhat.com> Message-ID: Hi Max, > does this mean it is available already as osgi bundle in a p2 repo ? > It is available on maven central repo http://search.maven.org/#artifactdetails|com.eclipsesource.minimal-json|minimal-json|0.9.1|bundle I don't know if there is a p2 repo? > > Then that seems like a win ;) > Ok I will try it the migration. Thank's for your reply! > > * minimal-json seems more optmized than json-simple (see benchmark at >> http://eclipsesource.com/blogs/2013/11/27/minimal-json- >> 0-9-1-available-on-maven-central/ >> ) >> >> Are you OK with this migration (if I can do it)? >> >> Regards Angelo >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > > > /max > http://about.me/maxandersen > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140429/da4e558e/attachment-0001.html From manderse at redhat.com Tue Apr 29 14:09:53 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 29 Apr 2014 20:09:53 +0200 Subject: [jbosstools-dev] Replace json-simple by minimal-json in tern.java? In-Reply-To: References: <8BBDD73F-B1F2-416B-9804-8B9FF6767789@redhat.com> Message-ID: On 29 Apr 2014, at 15:34, Angelo zerr wrote: > Hi Max, > > >> does this mean it is available already as osgi bundle in a p2 repo ? >> > > It is available on maven central repo > http://search.maven.org/#artifactdetails|com.eclipsesource.minimal-json|minimal-json|0.9.1|bundle > I don't know if there is a p2 repo? so then it doesn't seem like a big win ;) > >> >> Then that seems like a win ;) >> > > Ok I will try it the migration. > > Thank's for your reply! > >> >> * minimal-json seems more optmized than json-simple (see benchmark at >>> http://eclipsesource.com/blogs/2013/11/27/minimal-json- >>> 0-9-1-available-on-maven-central/ >>> ) >>> >>> Are you OK with this migration (if I can do it)? >>> >>> Regards Angelo >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >> >> >> /max >> http://about.me/maxandersen >> /max http://about.me/maxandersen From angelo.zerr at gmail.com Tue Apr 29 17:07:54 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Tue, 29 Apr 2014 23:07:54 +0200 Subject: [jbosstools-dev] Replace json-simple by minimal-json in tern.java? In-Reply-To: References: <8BBDD73F-B1F2-416B-9804-8B9FF6767789@redhat.com> Message-ID: Hi max, Migration to minimal-json was done. Don't hesitate to create issues if you find bugs (Junit works well). For P2, I have posted my question at https://github.com/ralfstx/minimal-json/issues/28 Regards Angelo 2014-04-29 20:09 GMT+02:00 Max Rydahl Andersen : > On 29 Apr 2014, at 15:34, Angelo zerr wrote: > > Hi Max, >> >> >> does this mean it is available already as osgi bundle in a p2 repo ? >>> >>> >> It is available on maven central repo >> http://search.maven.org/#artifactdetails|com.eclipsesource.minimal-json| >> minimal-json|0.9.1|bundle >> I don't know if there is a p2 repo? >> > > so then it doesn't seem like a big win ;) > > > >> >>> Then that seems like a win ;) >>> >>> >> Ok I will try it the migration. >> >> Thank's for your reply! >> >> >>> * minimal-json seems more optmized than json-simple (see benchmark at >>> >>>> http://eclipsesource.com/blogs/2013/11/27/minimal-json- >>>> 0-9-1-available-on-maven-central/ >>>> ) >>>> >>>> Are you OK with this migration (if I can do it)? >>>> >>>> Regards Angelo >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >>>> >>> >>> /max >>> http://about.me/maxandersen >>> >>> > > /max > http://about.me/maxandersen > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140429/fdd6045f/attachment.html From nboldt at redhat.com Wed Apr 30 00:02:08 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 30 Apr 2014 14:02:08 +1000 Subject: [jbosstools-dev] Replace json-simple by minimal-json in tern.java? In-Reply-To: References: <8BBDD73F-B1F2-416B-9804-8B9FF6767789@redhat.com> Message-ID: <536075C0.5020501@redhat.com> PR to turn the maven jar into an osgi bundle, and stick both that jar and its source bundle onto an update site, with generated index.html page: https://github.com/ralfstx/minimal-json/pull/29 On 04/30/2014 07:07 AM, Angelo zerr wrote: > Hi max, > > Migration to minimal-json was done. Don't hesitate to create issues if > you find bugs (Junit works well). > > For P2, I have posted my question at > https://github.com/ralfstx/minimal-json/issues/28 > > Regards Angelo > > > 2014-04-29 20:09 GMT+02:00 Max Rydahl Andersen >: > > On 29 Apr 2014, at 15:34, Angelo zerr wrote: > > Hi Max, > > > does this mean it is available already as osgi bundle in a > p2 repo ? > > > It is available on maven central repo > http://search.maven.org/#__artifactdetails|com.__eclipsesource.minimal-json|__minimal-json|0.9.1|bundle > > I don't know if there is a p2 repo? > > > so then it doesn't seem like a big win ;) > > > > > Then that seems like a win ;) > > > Ok I will try it the migration. > > Thank's for your reply! > > > * minimal-json seems more optmized than json-simple (see > benchmark at > > http://eclipsesource.com/__blogs/2013/11/27/minimal-json- > 0-9-1-available-on-maven-__central/ > ) > > Are you OK with this migration (if I can do it)? > > Regards Angelo > _________________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > > https://lists.jboss.org/__mailman/listinfo/jbosstools-__dev > > > > > /max > http://about.me/maxandersen > > > > /max > http://about.me/maxandersen > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Wed Apr 30 11:24:37 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 30 Apr 2014 17:24:37 +0200 Subject: [jbosstools-dev] making dark theme in luna useful Message-ID: <8C4A4856-3416-431E-AEE9-952E237CCE78@redhat.com> Hi, Luna introduces a Dark Theme (all the cool kids uses it) But for it to be really good the editors need to declare colour scheme for the dark theme. Anyone up for helping eclipse make this happen including making sure our editors behaves well ? https://bugs.eclipse.org/bugs/show_bug.cgi?id=433475 is the uber bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=433718 is the one for WTP XML editors... ...and then there is ours..we just need to check if we actually have issues or will listen to all these default ones. Anyone up for some graphical colouring ? :) /max http://about.me/maxandersen p.s. i'm not a cool kid.