From May-presales9 at vip.126.com Sun Dec 1 13:31:43 2013 From: May-presales9 at vip.126.com (May@oversea-print.com) Date: Mon, 2 Dec 2013 02:31:43 +0800 Subject: [jbosstools-dev] International prints product Message-ID: <529B808C.637D7B.27865@m19-178.vip.126.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/17ae0eb3/attachment.html From xcoulon at redhat.com Mon Dec 2 03:29:29 2013 From: xcoulon at redhat.com (Xavier Coulon) Date: Mon, 2 Dec 2013 09:29:29 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.CR1 ] In-Reply-To: <5298E669.7080900@redhat.com> References: <5298E669.7080900@redhat.com> Message-ID: <73EEFEA1-B035-4F0B-93AF-88D3578175E6@redhat.com> Hello Nick, It's done for LiveReload and Webservices. Best regards, /Xavier On Nov 29, 2013, at 8:09 PM, Nick Boldt wrote: > git tag jbosstools-4.1.1.CR1 > git push origin jbosstools-4.1.1.CR1 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/cf6102d7/attachment.html From Tina-marketing5 at vip.126.com Mon Dec 2 04:20:32 2013 From: Tina-marketing5 at vip.126.com (Tina@oversea-print.com) Date: Mon, 2 Dec 2013 17:20:32 +0800 Subject: [jbosstools-dev] Customized paper bag /oversea provider Message-ID: <529C50E8.695228.27865@m19-178.vip.126.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/cf1a494e/attachment.html From d at dfhbsef.mygbiz.com Mon Dec 2 09:56:43 2013 From: d at dfhbsef.mygbiz.com (Bluetooth speaker Supply) Date: Mon, 02 Dec 2013 14:56:43 +0000 Subject: [jbosstools-dev] =?gb2312?b?Qmx1ZXRvb3RoIHNwZWFrZXIgU3VwcGx50+s=?= =?gb2312?b?xPq5ss/twcvP4LLhoaM=?= Message-ID: <047d7b6043ce58380a04ec8e63fc@google.com> 1869868077550249394707769930233589335961412675100018784969019495219310241186158170883119327167689266 Dear Sir or Madam, Wealth Land Electronics Co.,Ltd here. We specialize in electronic devices field with full experience and we have 100 % confidence in our technology and quality. Now our hot seller is bluetooth speaker . Bluetooth speaker is very morden product which can work with all bluetooth electronic device . Various shapes are available , It can offer you magical sound when you listen music . Make your life more enjoyable . If any interest, feel free to contact me. Best regards, Mr. Buick Sales Manager ELECTRONIC LIMITED sBwdtLfztiOXYWbMFMrEDTXZRqFyiQSnPUisNaOAbywYGXJNnOZTliFbzrnzQfAoxVQtvcwBJzforqvSZgKXWnqtlKZRCjmGjnByhuUUvDQsMrPhHhsmFoLuFLHTkzGIRpkNPvCVdTytusxipwNonDtwRqTxvdSmdThsaaNNpxKmFlJbnbYSliEozFBMdeABLiPtJpvPXMsnomrcVcHhTjnphGjRBxlGwnBLuuhTuRdsZrchGvsmEBYuSYUgjyUVeojNcvPidSyHHGLwpwanmDJMEdslVDFaCHVfANBnOkjL https://picasaweb.google.com/lh/sredir?uname=106629282028130373780&target=ALBUM&id=5927972901320504225&authkey=Gv1sRgCLTQk6DS8bSj-wE&invite=CPWJ3OEI&feat=email -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/9de78510/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: picasaweblogo-zh_CN.gif Type: image/gif Size: 1646 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/9de78510/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: email.jpg Type: image/jpeg Size: 4838 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/9de78510/attachment.jpg From mistria at redhat.com Mon Dec 2 10:38:22 2013 From: mistria at redhat.com (Mickael Istria) Date: Mon, 02 Dec 2013 16:38:22 +0100 Subject: [jbosstools-dev] Upcoming releases of target platforms Message-ID: <529CA96E.8030608@redhat.com> Hi all, In order to finalize the 4.1.1.Final stream, we plan to release the following target-platforms very soon: * TP 4.30.6.Final * TP 4.31.1.Final * Central TP 4.31.0.Final Those target-platforms will have the exact same content as their related CR1 versions, they're just rebuilt to have a .Final suffix. So there should be neither good or bad surprise. If you feel like there's something that needs to be changed, please tell it right now. -- 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/20131202/9e778945/attachment-0001.html From nboldt at redhat.com Mon Dec 2 12:13:00 2013 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 02 Dec 2013 12:13:00 -0500 Subject: [jbosstools-dev] Upcoming releases of target platforms In-Reply-To: <529CA96E.8030608@redhat.com> References: <529CA96E.8030608@redhat.com> Message-ID: <529CBF9C.9000309@redhat.com> CR1 == Final except for the Central TP: * 4.31.0.CR1 contains Subclipse 1.8 / SVNKit 1.7 * 4.31.0.Final contains Subclipse 1.10 / SVNKit 1.8 Ref: JBDS-2709 / JBDS-2710 Cheers, On 12/02/2013 10:38 AM, Mickael Istria wrote: > Hi all, > > In order to finalize the 4.1.1.Final stream, we plan to release the > following target-platforms very soon: > * TP 4.30.6.Final > * TP 4.31.1.Final > * Central TP 4.31.0.Final > Those target-platforms will have the exact same content as their related > CR1 versions, they're just rebuilt to have a .Final suffix. So there > should be neither good or bad surprise. > > If you feel like there's something that needs to be changed, please tell > it right now. > -- > 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 > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From fbricon at redhat.com Mon Dec 2 13:28:33 2013 From: fbricon at redhat.com (Fred Bricon) Date: Mon, 02 Dec 2013 19:28:33 +0100 Subject: [jbosstools-dev] [jdf-dev] JBoss Central HTML5 archetype is borked In-Reply-To: <5298F5A5.6010003@redhat.com> References: <5298CE37.8090407@redhat.com> <5298F5A5.6010003@redhat.com> Message-ID: <529CD151.6050102@redhat.com> Thanks Rafael, that fixed the main issue. However, the essential dependencies are incorrect, here's a PR fixing them : https://github.com/jboss-jdf/jdf-stack/pull/28 Now this lead me to find a severe issue in JBoss Central (https://issues.jboss.org/browse/JBIDE-16170), where we display a warning about these missing dependencies only if the user selects an enterprise runtime which is really really bad. We have 2 solutions : - respin JBT/JBDS for GA with a fix - make stacks.yaml point at the old html5 archetype, with a target:community label, effectively using a different archetype if a non-enterprise runtime is selected. WDYT? Fred Le 29/11/2013 21:14, Rafael Benevides a ?crit : > I hope this commit fixes the issues: > https://github.com/jboss-jdf/jdf-stack/commit/49134b900 > > Please, let me know of any additional issues. > > Thanks for the report. > > Em 29/11/13 15:26, Fred Bricon escreveu: >> 2 issues were introduced in JBoss Central with the latest stacks.yaml >> update : >> >> - 2 archetype versions use the same html5-mobile tag : 2.4.0.Final and >> 2.4.0-build-1. But JBT, using >> org.apache.maven.artifact.versioning.ComparableVersion, finds >> 2.4.0-build-1 is higher than 2.4.0.Final and uses it as the most recent >> version. Since 2.4.0-build-1 dependencies haven't been released as part >> of WFK 2.4, the generated project fails to build because of missing >> deps. lastWFKArchetypeRelease should be updated to 2.4.0.Final in >> https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml >> >> - There's a blank html5 archetype, pointing at the non-blank one, which >> makes JBoss Central wizards to enable a useless 'use blank' checkbox. >> Why keep it referenced? >> >> Fred >> >> _______________________________________________ >> jdf-dev mailing list >> jdf-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jdf-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/4b160161/attachment.html From kmarmaliykov at exadel.com Mon Dec 2 14:13:11 2013 From: kmarmaliykov at exadel.com (Konstantin Marmalyukov) Date: Mon, 02 Dec 2013 22:13:11 +0300 Subject: [jbosstools-dev] Status for VPE/BrowserSim team Message-ID: <529CDBC7.2060105@exadel.com> Last two weeks: Ilya Buziuk * chromedevtools for Eclipse investigation - https://code.google.com/p/chromedevtools/wiki/EclipseDebugger * JBIDE-16060 CordovaSim: InAppBrowser plugin doesn't work on Fedora * JBIDE-16119 CordovaSim "windows" will not open * JBIDE-16090 firebug lite + livereload goes blank * JBIDE-15991 BrowserSim New and Noteworthy for 4.1.1.CR1 * Testing new 7.1.0.CR1 build on windows, linux, mac Konstantin Marmalyukov * fixing minor bugs * update of javafx libs detector and separator of javafx and webkit browser(have compilable version now) * created standalone app for win64 * Luna M3 + new TP(got failed tests and build problems) * JBIDE-16019 Reorganize JST component This week: * Bug fixing * Research: javafx and xulrunner compatibility * Need to add javafx Webkit as an alternative BrowserSim's engine * JBIDE-16134 CordovaSim should start the livereload server * failed tests on Luna -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/270fb6dd/attachment.html From benevides at redhat.com Mon Dec 2 15:07:09 2013 From: benevides at redhat.com (Rafael Benevides) Date: Mon, 02 Dec 2013 18:07:09 -0200 Subject: [jbosstools-dev] [jdf-dev] JBoss Central HTML5 archetype is borked In-Reply-To: <529CD151.6050102@redhat.com> References: <5298CE37.8090407@redhat.com> <5298F5A5.6010003@redhat.com> <529CD151.6050102@redhat.com> Message-ID: <529CE86D.2080209@redhat.com> Hi Fred! I merged your PR. I think that the second proposed solution is better because it doesn't evolve any respin with a fix and the result as I understood is the same. Do you agree ? Em 02/12/13 16:28, Fred Bricon escreveu: > Thanks Rafael, that fixed the main issue. However, the essential > dependencies are incorrect, here's a PR fixing them : > https://github.com/jboss-jdf/jdf-stack/pull/28 > > Now this lead me to find a severe issue in JBoss Central > (https://issues.jboss.org/browse/JBIDE-16170), where we display a > warning about these missing dependencies only if the user selects an > enterprise runtime which is really really bad. > > We have 2 solutions : > - respin JBT/JBDS for GA with a fix > - make stacks.yaml point at the old html5 archetype, with a > target:community label, effectively using a different archetype if a > non-enterprise runtime is selected. > > WDYT? > > Fred > > > > Le 29/11/2013 21:14, Rafael Benevides a ?crit : >> I hope this commit fixes the issues: >> https://github.com/jboss-jdf/jdf-stack/commit/49134b900 >> >> Please, let me know of any additional issues. >> >> Thanks for the report. >> >> Em 29/11/13 15:26, Fred Bricon escreveu: >>> 2 issues were introduced in JBoss Central with the latest stacks.yaml >>> update : >>> >>> - 2 archetype versions use the same html5-mobile tag : 2.4.0.Final and >>> 2.4.0-build-1. But JBT, using >>> org.apache.maven.artifact.versioning.ComparableVersion, finds >>> 2.4.0-build-1 is higher than 2.4.0.Final and uses it as the most recent >>> version. Since 2.4.0-build-1 dependencies haven't been released as part >>> of WFK 2.4, the generated project fails to build because of missing >>> deps. lastWFKArchetypeRelease should be updated to 2.4.0.Final in >>> https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml >>> >>> - There's a blank html5 archetype, pointing at the non-blank one, which >>> makes JBoss Central wizards to enable a useless 'use blank' checkbox. >>> Why keep it referenced? >>> >>> Fred >>> >>> _______________________________________________ >>> jdf-dev mailing list >>> jdf-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jdf-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/0273b69d/attachment.html From akazakov at exadel.com Mon Dec 2 16:50:08 2013 From: akazakov at exadel.com (Alexey Kazakov) Date: Mon, 02 Dec 2013 13:50:08 -0800 Subject: [jbosstools-dev] Test failing with Luna? Try the org.eclipse.osgi.compatibility.state fragment! In-Reply-To: <5298D889.8010606@redhat.com> References: <5298D889.8010606@redhat.com> Message-ID: <529D0090.100@exadel.com> I got the following error when added org.eclipse.osgi.compatibility.state as a dependency: [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.common.all.test.feature.source.feature.group 3.6.0.qualifier [ERROR] Missing requirement: org.jboss.tools.common.model.ui.test 3.6.0.qualifier requires 'bundle org.eclipse.osgi.compatibility.state.source 0.0.0' but it could not be found [ERROR] Cannot satisfy dependency: org.jboss.tools.common.all.test.feature.feature.group 3.6.0.qualifier depends on: org.jboss.tools.common.model.ui.test 0.0.0 [ERROR] Cannot satisfy dependency: org.jboss.tools.common.all.test.feature.source.feature.group 3.6.0.qualifier depends on: org.jboss.tools.common.all.test.feature.feature.group [3.6.0,3.6.1) [ERROR] [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.common.model.ui.test 3.6.0.qualifier to bundle org.eclipse.osgi.compatibility.state.source 0.0.0.; No solution found because the problem is unsatisfiable.] -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.common.model.ui.test 3.6.0.qualifier to bundle org.eclipse.osgi.compatibility.state.source 0.0.0.; No solution found because the problem is unsatisfiable.] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.common.model.ui.test 3.6.0.qualifier to bundle org.eclipse.osgi.compatibility.state.source 0.0.0.; No solution found because the problem is unsatisfiable.] at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98) at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88) at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63) at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134) at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 11 more On 11/29/2013 10:10 AM, Mickael Istria wrote: > Hi all, > > As part of Luna came a change that we've not correctly estimated: > http://wiki.eclipse.org/Equinox/Luna_Framework#Removal_of_the_PlatformAdmin_Service_Implementation > . This cause some parts of Eclipse to be failing with surefire as they > depend on a class which is not available in default Equinox bundles > any more. The TEMPORARY workaround is to add a dependency to your > tycho-surefire-plugin to fragment org.eclipse.osgi.compatibility.state. > So in case of failing test, try to add the fragment locally, and if it > works better, open a bug to keep track of that change (make me a dep > of JBIDE-16161). This should be fine for JBT 4.2.0.Alpha1 build and > tests against Luna M3. > > Then by Luna M4, this should happen: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 , and hopefully, > it will remove most of our dependencies on this somehow deprecated > PlatfromAdmin service. We'll be able to get rid of the additional > dependency on surefire, and everything will be fine. > > In case you have a message in your tycho-surefire-plugin saying "Could > not acquire PlatformAdmin", you can safely ignore it > https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 . It's just a > warning. What's important is whether your tests do work or not, and if > not, whether adding the fragment helps. > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/ae8584d8/attachment-0001.html From fbricon at redhat.com Mon Dec 2 16:59:28 2013 From: fbricon at redhat.com (Fred Bricon) Date: Mon, 02 Dec 2013 22:59:28 +0100 Subject: [jbosstools-dev] [jdf-dev] JBoss Central HTML5 archetype is borked In-Reply-To: <529CE86D.2080209@redhat.com> References: <5298CE37.8090407@redhat.com> <5298F5A5.6010003@redhat.com> <529CD151.6050102@redhat.com> <529CE86D.2080209@redhat.com> Message-ID: <529D02C0.1070006@redhat.com> Le lundi 2 d?cembre 2013 21:07:09, Rafael Benevides a ?crit : > Hi Fred! > > I merged your PR. > Thanks > I think that the second proposed solution is better because it doesn't > evolve any respin with a fix and the result as I understood is the > same. Do you agree ? +1. Can you do a PR I can try tomorrow morning? > > Em 02/12/13 16:28, Fred Bricon escreveu: >> Thanks Rafael, that fixed the main issue. However, the essential >> dependencies are incorrect, here's a PR fixing them : >> https://github.com/jboss-jdf/jdf-stack/pull/28 >> >> Now this lead me to find a severe issue in JBoss Central >> (https://issues.jboss.org/browse/JBIDE-16170), where we display a >> warning about these missing dependencies only if the user selects an >> enterprise runtime which is really really bad. >> >> We have 2 solutions : >> - respin JBT/JBDS for GA with a fix >> - make stacks.yaml point at the old html5 archetype, with a >> target:community label, effectively using a different archetype if a >> non-enterprise runtime is selected. >> >> WDYT? >> >> Fred >> >> >> >> Le 29/11/2013 21:14, Rafael Benevides a ?crit : >>> I hope this commit fixes the issues: >>> https://github.com/jboss-jdf/jdf-stack/commit/49134b900 >>> >>> Please, let me know of any additional issues. >>> >>> Thanks for the report. >>> >>> Em 29/11/13 15:26, Fred Bricon escreveu: >>>> 2 issues were introduced in JBoss Central with the latest stacks.yaml >>>> update : >>>> >>>> - 2 archetype versions use the same html5-mobile tag : 2.4.0.Final and >>>> 2.4.0-build-1. But JBT, using >>>> org.apache.maven.artifact.versioning.ComparableVersion, finds >>>> 2.4.0-build-1 is higher than 2.4.0.Final and uses it as the most >>>> recent >>>> version. Since 2.4.0-build-1 dependencies haven't been released as >>>> part >>>> of WFK 2.4, the generated project fails to build because of missing >>>> deps. lastWFKArchetypeRelease should be updated to 2.4.0.Final in >>>> https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml >>>> >>>> - There's a blank html5 archetype, pointing at the non-blank one, >>>> which >>>> makes JBoss Central wizards to enable a useless 'use blank' checkbox. >>>> Why keep it referenced? >>>> >>>> Fred >>>> >>>> _______________________________________________ >>>> jdf-dev mailing list >>>> jdf-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>> >> > From manderse at redhat.com Mon Dec 2 18:07:55 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 3 Dec 2013 00:07:55 +0100 Subject: [jbosstools-dev] [jdf-dev] JBoss Central HTML5 archetype is borked In-Reply-To: <529D02C0.1070006@redhat.com> References: <5298CE37.8090407@redhat.com> <5298F5A5.6010003@redhat.com> <529CD151.6050102@redhat.com> <529CE86D.2080209@redhat.com> <529D02C0.1070006@redhat.com> Message-ID: <20131202230755.GA9510@slowbeard.local> Another issue I see here is why we are *removing* examples from stacks ? it should just be adding, not removing examples since that would invalidate JBDS 7.0 afaics. /max On Mon, Dec 02, 2013 at 10:59:28PM +0100, Fred Bricon wrote: >Le lundi 2 d?cembre 2013 21:07:09, Rafael Benevides a ?crit : >> Hi Fred! >> >> I merged your PR. >> >Thanks > >> I think that the second proposed solution is better because it doesn't >> evolve any respin with a fix and the result as I understood is the >> same. Do you agree ? >+1. Can you do a PR I can try tomorrow morning? > >> >> Em 02/12/13 16:28, Fred Bricon escreveu: >>> Thanks Rafael, that fixed the main issue. However, the essential >>> dependencies are incorrect, here's a PR fixing them : >>> https://github.com/jboss-jdf/jdf-stack/pull/28 >>> >>> Now this lead me to find a severe issue in JBoss Central >>> (https://issues.jboss.org/browse/JBIDE-16170), where we display a >>> warning about these missing dependencies only if the user selects an >>> enterprise runtime which is really really bad. >>> >>> We have 2 solutions : >>> - respin JBT/JBDS for GA with a fix >>> - make stacks.yaml point at the old html5 archetype, with a >>> target:community label, effectively using a different archetype if a >>> non-enterprise runtime is selected. >>> >>> WDYT? >>> >>> Fred >>> >>> >>> >>> Le 29/11/2013 21:14, Rafael Benevides a ?crit : >>>> I hope this commit fixes the issues: >>>> https://github.com/jboss-jdf/jdf-stack/commit/49134b900 >>>> >>>> Please, let me know of any additional issues. >>>> >>>> Thanks for the report. >>>> >>>> Em 29/11/13 15:26, Fred Bricon escreveu: >>>>> 2 issues were introduced in JBoss Central with the latest stacks.yaml >>>>> update : >>>>> >>>>> - 2 archetype versions use the same html5-mobile tag : 2.4.0.Final and >>>>> 2.4.0-build-1. But JBT, using >>>>> org.apache.maven.artifact.versioning.ComparableVersion, finds >>>>> 2.4.0-build-1 is higher than 2.4.0.Final and uses it as the most >>>>> recent >>>>> version. Since 2.4.0-build-1 dependencies haven't been released as >>>>> part >>>>> of WFK 2.4, the generated project fails to build because of missing >>>>> deps. lastWFKArchetypeRelease should be updated to 2.4.0.Final in >>>>> https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml >>>>> >>>>> - There's a blank html5 archetype, pointing at the non-blank one, >>>>> which >>>>> makes JBoss Central wizards to enable a useless 'use blank' checkbox. >>>>> Why keep it referenced? >>>>> >>>>> Fred >>>>> >>>>> _______________________________________________ >>>>> jdf-dev mailing list >>>>> jdf-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>>> >>> >> > > >_______________________________________________ >jdf-dev mailing list >jdf-dev at lists.jboss.org >https://lists.jboss.org/mailman/listinfo/jdf-dev From dgolovin at exadel.com Mon Dec 2 18:28:06 2013 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 02 Dec 2013 15:28:06 -0800 Subject: [jbosstools-dev] Test failing with Luna? Try the org.eclipse.osgi.compatibility.state fragment! In-Reply-To: <5298D889.8010606@redhat.com> References: <5298D889.8010606@redhat.com> Message-ID: <529D1786.3080109@exadel.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/9a4f2959/attachment.html From dgolovin at exadel.com Mon Dec 2 18:49:03 2013 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 02 Dec 2013 15:49:03 -0800 Subject: [jbosstools-dev] Test failing with Luna? Try the org.eclipse.osgi.compatibility.state fragment! In-Reply-To: <529D0090.100@exadel.com> References: <5298D889.8010606@redhat.com> <529D0090.100@exadel.com> Message-ID: <529D1C6F.1000707@exadel.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/4e31d14e/attachment.html From akazakov at exadel.com Mon Dec 2 19:04:57 2013 From: akazakov at exadel.com (Alexey Kazakov) Date: Mon, 02 Dec 2013 16:04:57 -0800 Subject: [jbosstools-dev] Test failing with Luna? Try the org.eclipse.osgi.compatibility.state fragment! In-Reply-To: <529D1C6F.1000707@exadel.com> References: <5298D889.8010606@redhat.com> <529D0090.100@exadel.com> <529D1C6F.1000707@exadel.com> Message-ID: <529D2029.5050509@exadel.com> It helped! Thanks. On 12/02/2013 03:49 PM, Denis Golovin wrote: > I sent PR with changes that works for me > https://github.com/jbosstools/jbosstools-build/pull/130 > > Denis > > > On 12/02/2013 01:50 PM, Alexey Kazakov wrote: >> I got the following error when added >> org.eclipse.osgi.compatibility.state as a dependency: >> >> [ERROR] Cannot resolve project dependencies: >> [ERROR] Software being installed: >> org.jboss.tools.common.all.test.feature.source.feature.group >> 3.6.0.qualifier >> [ERROR] Missing requirement: org.jboss.tools.common.model.ui.test >> 3.6.0.qualifier requires 'bundle >> org.eclipse.osgi.compatibility.state.source 0.0.0' but it could not >> be found >> [ERROR] Cannot satisfy dependency: >> org.jboss.tools.common.all.test.feature.feature.group 3.6.0.qualifier >> depends on: org.jboss.tools.common.model.ui.test 0.0.0 >> [ERROR] Cannot satisfy dependency: >> org.jboss.tools.common.all.test.feature.source.feature.group >> 3.6.0.qualifier depends on: >> org.jboss.tools.common.all.test.feature.feature.group [3.6.0,3.6.1) >> [ERROR] >> [ERROR] Internal error: java.lang.RuntimeException: No solution found >> because the problem is unsatisfiable.: [Unable to satisfy dependency >> from org.jboss.tools.common.model.ui.test 3.6.0.qualifier to bundle >> org.eclipse.osgi.compatibility.state.source 0.0.0.; No solution found >> because the problem is unsatisfiable.] -> [Help 1] >> org.apache.maven.InternalErrorException: Internal error: >> java.lang.RuntimeException: No solution found because the problem is >> unsatisfiable.: [Unable to satisfy dependency from >> org.jboss.tools.common.model.ui.test 3.6.0.qualifier to bundle >> org.eclipse.osgi.compatibility.state.source 0.0.0.; No solution found >> because the problem is unsatisfiable.] >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:606) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >> Caused by: java.lang.RuntimeException: No solution found because the >> problem is unsatisfiable.: [Unable to satisfy dependency from >> org.jboss.tools.common.model.ui.test 3.6.0.qualifier to bundle >> org.eclipse.osgi.compatibility.state.source 0.0.0.; No solution found >> because the problem is unsatisfiable.] >> at >> org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98) >> at >> org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88) >> at >> org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63) >> at >> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134) >> at >> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87) >> at >> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369) >> at >> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345) >> at >> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109) >> at >> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> ... 11 more >> >> >> On 11/29/2013 10:10 AM, Mickael Istria wrote: >>> Hi all, >>> >>> As part of Luna came a change that we've not correctly estimated: >>> http://wiki.eclipse.org/Equinox/Luna_Framework#Removal_of_the_PlatformAdmin_Service_Implementation >>> . This cause some parts of Eclipse to be failing with surefire as >>> they depend on a class which is not available in default Equinox >>> bundles any more. The TEMPORARY workaround is to add a dependency to >>> your tycho-surefire-plugin to fragment >>> org.eclipse.osgi.compatibility.state. >>> So in case of failing test, try to add the fragment locally, and if >>> it works better, open a bug to keep track of that change (make me a >>> dep of JBIDE-16161). This should be fine for JBT 4.2.0.Alpha1 build >>> and tests against Luna M3. >>> >>> Then by Luna M4, this should happen: >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 , and >>> hopefully, it will remove most of our dependencies on this somehow >>> deprecated PlatfromAdmin service. We'll be able to get rid of the >>> additional dependency on surefire, and everything will be fine. >>> >>> In case you have a message in your tycho-surefire-plugin saying >>> "Could not acquire PlatformAdmin", you can safely ignore it >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 . It's just a >>> warning. What's important is whether your tests do work or not, and >>> if not, whether adding the fragment helps. >>> -- >>> 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 >> >> >> >> _______________________________________________ >> 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/20131202/ecf0a245/attachment-0001.html From dgolovin at exadel.com Mon Dec 2 19:13:53 2013 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 02 Dec 2013 16:13:53 -0800 Subject: [jbosstools-dev] Test failing with Luna? Try the org.eclipse.osgi.compatibility.state fragment! In-Reply-To: <5298D889.8010606@redhat.com> References: <5298D889.8010606@redhat.com> Message-ID: <529D2241.9060903@exadel.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131202/a5bea84b/attachment.html From mistria at redhat.com Tue Dec 3 03:43:19 2013 From: mistria at redhat.com (Mickael Istria) Date: Tue, 03 Dec 2013 09:43:19 +0100 Subject: [jbosstools-dev] Target Platform 4.30.6.Final and 4.31.1.Final release Message-ID: <529D99A7.1080900@redhat.com> |JBoss Tools Target Platform 4.30.6.Final and 4.31.1.Final have been released. Changes ======= * None, compared to their CR1 version. Only qualifier changes to Final Usage ===== Those platform are what JBoss Tools 4.1.1.Final will use. All jobs in jenkins for *branch* have been updated to use Minimal TP version 4.30.6.Final. Parent pom 4.1.1.Final-SNAPSHOT for branch jbosstools-4.1.1.x has been updated to use Minimal TP 4.30.6.Final. Parent pom 4.1.2.Alpha1-SNAPSHOT for branch jbosstools-4.1.x|||has been updated to use Minimal TP 4.30.6.Final.| |||All jobs in jenkins for *branch* have been updated to use Maximal/Recommanded TP version 4.31.1.Final. Parent pom 4.1.1.Final-SNAPSHOT for branch jbosstools-4.1.1.x has been updated to use||||||Maximal/Recommanded TP version 4.31.1.Final.|| Parent pom 4.1.2.Alpha1-SNAPSHOT for branch jbosstools-4.1.x|||has been updated to use||||||||Maximal/Recommanded TP version 4.31.1.Final.|||| Download ======== Zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.30.6.Final/jbosstoolstarget-4.30.6.Final.zip p2 site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.30.6.Final/REPO/ and| ||Zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.31.1.Final/jbosstoolstarget-4.31.1.Final.zip p2 site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.31.1.Final/REPO/| Testing/Development =================== You can try it out and use it directly like this: $ mvn clean verify -Dtpc.version=4.31.1.Final For advanced usage and help (using in IDE, building a mirror locally, using a zip...), plese read https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md What's next? ============ Branch 4.30.x for target platform has been prepared for potential upgrades, and it's version is now 4.30.7.Alpha1-SNAPSHOT.| ||Branch 4.31.x for target platform has been prepared for potential upgrades, and it's version is now 4.31.2.Alpha1-SNAPSHOT.| | -- 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/20131203/9dea6b7f/attachment.html From benevides at redhat.com Tue Dec 3 07:05:20 2013 From: benevides at redhat.com (Rafael Benevides) Date: Tue, 03 Dec 2013 10:05:20 -0200 Subject: [jbosstools-dev] [jdf-dev] JBoss Central HTML5 archetype is borked In-Reply-To: <20131202230755.GA9510@slowbeard.local> References: <5298CE37.8090407@redhat.com> <5298F5A5.6010003@redhat.com> <529CD151.6050102@redhat.com> <529CE86D.2080209@redhat.com> <529D02C0.1070006@redhat.com> <20131202230755.GA9510@slowbeard.local> Message-ID: <529DC900.3070008@redhat.com> Max, What do you mean by examples ? If you were talking about the Archetypes, I tried to keep them but it seems that Fred had an issue with duplicated archetypes version. Or am I missing something? Em 02/12/13 21:07, Max Rydahl Andersen escreveu: > Another issue I see here is why we are *removing* examples from stacks ? > > it should just be adding, not removing examples since that would > invalidate JBDS 7.0 afaics. > > /max > > On Mon, Dec 02, 2013 at 10:59:28PM +0100, Fred Bricon wrote: >> Le lundi 2 d?cembre 2013 21:07:09, Rafael Benevides a ?crit : >>> Hi Fred! >>> >>> I merged your PR. >>> >> Thanks >> >>> I think that the second proposed solution is better because it doesn't >>> evolve any respin with a fix and the result as I understood is the >>> same. Do you agree ? >> +1. Can you do a PR I can try tomorrow morning? >> >>> >>> Em 02/12/13 16:28, Fred Bricon escreveu: >>>> Thanks Rafael, that fixed the main issue. However, the essential >>>> dependencies are incorrect, here's a PR fixing them : >>>> https://github.com/jboss-jdf/jdf-stack/pull/28 >>>> >>>> Now this lead me to find a severe issue in JBoss Central >>>> (https://issues.jboss.org/browse/JBIDE-16170), where we display a >>>> warning about these missing dependencies only if the user selects an >>>> enterprise runtime which is really really bad. >>>> >>>> We have 2 solutions : >>>> - respin JBT/JBDS for GA with a fix >>>> - make stacks.yaml point at the old html5 archetype, with a >>>> target:community label, effectively using a different archetype if a >>>> non-enterprise runtime is selected. >>>> >>>> WDYT? >>>> >>>> Fred >>>> >>>> >>>> >>>> Le 29/11/2013 21:14, Rafael Benevides a ?crit : >>>>> I hope this commit fixes the issues: >>>>> https://github.com/jboss-jdf/jdf-stack/commit/49134b900 >>>>> >>>>> Please, let me know of any additional issues. >>>>> >>>>> Thanks for the report. >>>>> >>>>> Em 29/11/13 15:26, Fred Bricon escreveu: >>>>>> 2 issues were introduced in JBoss Central with the latest >>>>>> stacks.yaml >>>>>> update : >>>>>> >>>>>> - 2 archetype versions use the same html5-mobile tag : >>>>>> 2.4.0.Final and >>>>>> 2.4.0-build-1. But JBT, using >>>>>> org.apache.maven.artifact.versioning.ComparableVersion, finds >>>>>> 2.4.0-build-1 is higher than 2.4.0.Final and uses it as the most >>>>>> recent >>>>>> version. Since 2.4.0-build-1 dependencies haven't been released as >>>>>> part >>>>>> of WFK 2.4, the generated project fails to build because of missing >>>>>> deps. lastWFKArchetypeRelease should be updated to 2.4.0.Final in >>>>>> https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml >>>>>> >>>>>> - There's a blank html5 archetype, pointing at the non-blank one, >>>>>> which >>>>>> makes JBoss Central wizards to enable a useless 'use blank' >>>>>> checkbox. >>>>>> Why keep it referenced? >>>>>> >>>>>> Fred >>>>>> >>>>>> _______________________________________________ >>>>>> jdf-dev mailing list >>>>>> jdf-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>>>> >>>> >>> >> >> >> _______________________________________________ >> jdf-dev mailing list >> jdf-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jdf-dev From benevides at redhat.com Tue Dec 3 09:07:25 2013 From: benevides at redhat.com (Rafael Benevides) Date: Tue, 03 Dec 2013 12:07:25 -0200 Subject: [jbosstools-dev] [jdf-dev] JBoss Central HTML5 archetype is borked In-Reply-To: <529D02C0.1070006@redhat.com> References: <5298CE37.8090407@redhat.com> <5298F5A5.6010003@redhat.com> <529CD151.6050102@redhat.com> <529CE86D.2080209@redhat.com> <529D02C0.1070006@redhat.com> Message-ID: <529DE59D.4060206@redhat.com> Fred, Can you try this PR https://github.com/jboss-jdf/jdf-stack/pull/29 ? Thanks Em 02/12/13 19:59, Fred Bricon escreveu: > Le lundi 2 d?cembre 2013 21:07:09, Rafael Benevides a ?crit : >> Hi Fred! >> >> I merged your PR. >> > Thanks > >> I think that the second proposed solution is better because it doesn't >> evolve any respin with a fix and the result as I understood is the >> same. Do you agree ? > +1. Can you do a PR I can try tomorrow morning? > >> >> Em 02/12/13 16:28, Fred Bricon escreveu: >>> Thanks Rafael, that fixed the main issue. However, the essential >>> dependencies are incorrect, here's a PR fixing them : >>> https://github.com/jboss-jdf/jdf-stack/pull/28 >>> >>> Now this lead me to find a severe issue in JBoss Central >>> (https://issues.jboss.org/browse/JBIDE-16170), where we display a >>> warning about these missing dependencies only if the user selects an >>> enterprise runtime which is really really bad. >>> >>> We have 2 solutions : >>> - respin JBT/JBDS for GA with a fix >>> - make stacks.yaml point at the old html5 archetype, with a >>> target:community label, effectively using a different archetype if a >>> non-enterprise runtime is selected. >>> >>> WDYT? >>> >>> Fred >>> >>> >>> >>> Le 29/11/2013 21:14, Rafael Benevides a ?crit : >>>> I hope this commit fixes the issues: >>>> https://github.com/jboss-jdf/jdf-stack/commit/49134b900 >>>> >>>> Please, let me know of any additional issues. >>>> >>>> Thanks for the report. >>>> >>>> Em 29/11/13 15:26, Fred Bricon escreveu: >>>>> 2 issues were introduced in JBoss Central with the latest stacks.yaml >>>>> update : >>>>> >>>>> - 2 archetype versions use the same html5-mobile tag : 2.4.0.Final >>>>> and >>>>> 2.4.0-build-1. But JBT, using >>>>> org.apache.maven.artifact.versioning.ComparableVersion, finds >>>>> 2.4.0-build-1 is higher than 2.4.0.Final and uses it as the most >>>>> recent >>>>> version. Since 2.4.0-build-1 dependencies haven't been released as >>>>> part >>>>> of WFK 2.4, the generated project fails to build because of missing >>>>> deps. lastWFKArchetypeRelease should be updated to 2.4.0.Final in >>>>> https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml >>>>> >>>>> - There's a blank html5 archetype, pointing at the non-blank one, >>>>> which >>>>> makes JBoss Central wizards to enable a useless 'use blank' checkbox. >>>>> Why keep it referenced? >>>>> >>>>> Fred >>>>> >>>>> _______________________________________________ >>>>> jdf-dev mailing list >>>>> jdf-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jdf-dev >>>> >>> >> > > From manderse at redhat.com Tue Dec 3 10:03:19 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 3 Dec 2013 16:03:19 +0100 Subject: [jbosstools-dev] [jdf-dev] JBoss Central HTML5 archetype is borked In-Reply-To: <529DC900.3070008@redhat.com> References: <5298CE37.8090407@redhat.com> <5298F5A5.6010003@redhat.com> <529CD151.6050102@redhat.com> <529CE86D.2080209@redhat.com> <529D02C0.1070006@redhat.com> <20131202230755.GA9510@slowbeard.local> <529DC900.3070008@redhat.com> Message-ID: <20131203150319.GR9510@slowbeard.local> On Tue, Dec 03, 2013 at 10:05:20AM -0200, Rafael Benevides wrote: >Max, > >What do you mean by examples ? sorry, I meant archetypes (examples is just what we use it for on jbds side) >If you were talking about the Archetypes, I tried to keep them but it >seems that Fred had an issue with duplicated archetypes version. Or am >I missing something? I think it is because the id of the html5 archetype was used for both new and old. With the changes done it seems it would be better those had two different id's so it could be separate. /max > >Em 02/12/13 21:07, Max Rydahl Andersen escreveu: >>Another issue I see here is why we are *removing* examples from stacks ? >> >>it should just be adding, not removing examples since that would >>invalidate JBDS 7.0 afaics. >> >>/max >> >>On Mon, Dec 02, 2013 at 10:59:28PM +0100, Fred Bricon wrote: >>>Le lundi 2 d?cembre 2013 21:07:09, Rafael Benevides a ?crit : >>>>Hi Fred! >>>> >>>>I merged your PR. >>>> >>>Thanks >>> >>>>I think that the second proposed solution is better because it doesn't >>>>evolve any respin with a fix and the result as I understood is the >>>>same. Do you agree ? >>>+1. Can you do a PR I can try tomorrow morning? >>> >>>> >>>>Em 02/12/13 16:28, Fred Bricon escreveu: >>>>>Thanks Rafael, that fixed the main issue. However, the essential >>>>>dependencies are incorrect, here's a PR fixing them : >>>>>https://github.com/jboss-jdf/jdf-stack/pull/28 >>>>> >>>>>Now this lead me to find a severe issue in JBoss Central >>>>>(https://issues.jboss.org/browse/JBIDE-16170), where we display a >>>>>warning about these missing dependencies only if the user selects an >>>>>enterprise runtime which is really really bad. >>>>> >>>>>We have 2 solutions : >>>>>- respin JBT/JBDS for GA with a fix >>>>>- make stacks.yaml point at the old html5 archetype, with a >>>>>target:community label, effectively using a different archetype if a >>>>>non-enterprise runtime is selected. >>>>> >>>>>WDYT? >>>>> >>>>>Fred >>>>> >>>>> >>>>> >>>>>Le 29/11/2013 21:14, Rafael Benevides a ?crit : >>>>>>I hope this commit fixes the issues: >>>>>>https://github.com/jboss-jdf/jdf-stack/commit/49134b900 >>>>>> >>>>>>Please, let me know of any additional issues. >>>>>> >>>>>>Thanks for the report. >>>>>> >>>>>>Em 29/11/13 15:26, Fred Bricon escreveu: >>>>>>>2 issues were introduced in JBoss Central with the latest >>>>>>>stacks.yaml >>>>>>>update : >>>>>>> >>>>>>>- 2 archetype versions use the same html5-mobile tag : >>>>>>>2.4.0.Final and >>>>>>>2.4.0-build-1. But JBT, using >>>>>>>org.apache.maven.artifact.versioning.ComparableVersion, finds >>>>>>>2.4.0-build-1 is higher than 2.4.0.Final and uses it as the most >>>>>>>recent >>>>>>>version. Since 2.4.0-build-1 dependencies haven't been released as >>>>>>>part >>>>>>>of WFK 2.4, the generated project fails to build because of missing >>>>>>>deps. lastWFKArchetypeRelease should be updated to 2.4.0.Final in >>>>>>>https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml >>>>>>> >>>>>>>- There's a blank html5 archetype, pointing at the non-blank one, >>>>>>>which >>>>>>>makes JBoss Central wizards to enable a useless 'use >>>>>>>blank' checkbox. >>>>>>>Why keep it referenced? >>>>>>> >>>>>>>Fred >>>>>>> >>>>>>>_______________________________________________ >>>>>>>jdf-dev mailing list >>>>>>>jdf-dev at lists.jboss.org >>>>>>>https://lists.jboss.org/mailman/listinfo/jdf-dev >>>>>> >>>>> >>>> >>> >>> >>>_______________________________________________ >>>jdf-dev mailing list >>>jdf-dev at lists.jboss.org >>>https://lists.jboss.org/mailman/listinfo/jdf-dev > From nboldt at redhat.com Tue Dec 3 12:23:40 2013 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 03 Dec 2013 12:23:40 -0500 Subject: [jbosstools-dev] New JIRA versions added: JBIDE 4.2.0.* and JBDS 8.0.0.* Message-ID: <529E139C.8000307@redhat.com> FYI, there are now several milestones in JIRA for JBIDE & JBDS. Dates have not yet been assigned as the schedule is still TBD. 4.2.0.Alpha1 / 8.0.0.Alpha1 4.2.0.Alpha2 / 8.0.0.Alpha2 4.2.0.Beta1 / 8.0.0.Beta1 4.2.0.CR1 / 8.0.0.CR1 4.2.0.Final / 8.0.0.GA -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Tue Dec 3 13:00:20 2013 From: mistria at redhat.com (Mickael Istria) Date: Tue, 03 Dec 2013 19:00:20 +0100 Subject: [jbosstools-dev] Test failing with Luna? Try the org.eclipse.osgi.compatibility.state fragment! In-Reply-To: <5298D889.8010606@redhat.com> References: <5298D889.8010606@redhat.com> Message-ID: <529E1C34.6090808@redhat.com> On popular request, I've changed the parent pom to add the org.eclipse.e4.rcp feature as suggested by Snjezana. This should make some tests now more or less magically work better. This is a temporary fix, so that as soon as we have a TP containing fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 , we'll remove this dependency in surefire to get back to a smaller set of dependencies during tests. More of the story at https://issues.jboss.org/browse/JBIDE-16161 -- 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/20131203/bbab0cdc/attachment.html From nboldt at redhat.com Tue Dec 3 13:37:35 2013 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 03 Dec 2013 13:37:35 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Upcoming code freeze for JBDS 8 Alpha1 :: now on Thursday, Dec 05 In-Reply-To: <529E24A4.5080400@redhat.com> References: <529E24A4.5080400@redhat.com> Message-ID: <529E24EF.10008@redhat.com> Reminder, we have code freeze for JBT 4.2 / JBDS 8 Alpha1 this Thursday, Dec 05. (It was postponed from last week due to holiday conflicts & PTO.) If you will be *unable to code freeze on time*, please respond here ASAP. Otherwise, I will send the usual Task JIRA emails out tomorrow night so everyone can freeze and branch on Thursday in your time zone. --- FYI, there are compilation failures for these projects: * Forge - job set to use Luna TP and Maven 3.1.0. Should it be 3.1.1? * Hibernate - job set to use Kepler TP. Should it be Luna? --- Also seeing build failures (tests or timeouts) for these projects, but am respinning today to see if they were transient Jenkins problems not due to github sources: * Base * Central * JavaEE * JST * Server * Webservices Thanks, Nick On 11/28/2013 06:40 AM, Max Rydahl Andersen wrote: > On Wed, Nov 27, 2013 at 01:14:56PM -0500, Nick Boldt wrote: >> Thursday the 5th works too - gives people a bit more time to churn out >> some alpha content and for Hibernate to solve is compilation issues. >> >> Whether it's Monday Dec 2 or Thursday Dec 5, either way the release >> would be like this: >> >> Mon Dec 02 (or 05) :: JBDS 8 Alpha1 Code Freeze/Branch >> Mon Dec 09 :: JBDS 8 Alpha1 QE start (earlier if possible) >> Fri Dec 13 :: JBDS 8 Alpha1 release to EA/dev milestone >> >> How about we aim for Monday and see who needs more time? > > Since noone of these are around before Monday its not really apropriate. > > If you want it earlier than Thursday as usual I would say Wednesday. > > Giving everyone a chance to react to any failures found and the > tagging/branching needed. > > /max >> >> Nick >> >> On 11/27/2013 07:11 AM, Max Rydahl Andersen wrote: >>> On Tue, Nov 26, 2013 at 02:56:19PM -0500, Nick Boldt wrote: >>>> Yes, that could work. >>>> >>>> When does the whole Brno team disappear for the holiday shutdown / >>>> PTO? That is, when is the last *effective* date when we have a QE team >>>> to review & approve the Alpha build? >>> >>> Recall that for the alpha builds we only wanted very basic testing and >>> it wouldn't really prevent us from doing the alpha1 build - at most just >>> provide input on wether >>> we would publish jboss tools alpha1 to marketplace or not. >>> >>> I'm suggesting we move the codefreeze to Thursday next week, but lets >>> finalize the >>> date on the pm call today. >>> >>> /max >>> >>> >>>> >>>> Nick >>>> >>>> >>>> On 11/26/2013 02:50 PM, Alexey Kazakov wrote: >>>>> Thursday, Nov 28 is not good time for code freeze because of >>>>> Thanksgiving in USA. >>>>> Can we move it to Monday, December 2? >>>>> >>>>> Slava is on PTO this week. >>>>> I took a day off on Wednesday (+ Thursday and Friday) >>>>> Denis, Daniel - Thursday, Friday >>>>> >>>>> So it's pretty hard to freeze base, jst, javaee this week for us. >>>>> >>>>> On 11/20/2013 08:51 AM, Nick Boldt wrote: >>>>>> I know we're barely half way through the testing cycle for JBDS >>>>>> 7.1.0.CR1, but in order to be able to get a first Alpha for JBDS 8 >>>>>> out >>>>>> by year's end, we need to start looking at building JBDS 8 on Luna >>>>>> ASAP. >>>>>> >>>>>> To that end, Mickael will be producing a new Luna M3 target platform >>>>>> this week - watch for that email w/ instructions. >>>>>> >>>>>> The goal is to test building your projects w/ Luna, so that if you're >>>>>> a project who tends to be broken every year by upstream API >>>>>> changes in >>>>>> platform or WTP (eg., hibernate tools), you can find those problems >>>>>> and fix them ASAP. Or if necessary, report problems upstream. >>>>>> >>>>>> Attached is a screenshot of the proposed schedule for the first 3 >>>>>> milestones of JBDS 8. I'm hoping to have code freeze for JBDS 8 >>>>>> Alpha1 >>>>>> next Thursday, Nov 28, so that we can get Alpha1 out in early >>>>>> December. >>>>>> >>>>>> Cheers, >>>>>> >>>>> >>>> >>>> -- >>>> Nick Boldt :: JBoss by Red Hat >>>> Productization Lead :: JBoss Tools & Dev Studio >>>> http://nick.divbyzero.com >>>> >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Tue Dec 3 13:35:35 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 3 Dec 2013 19:35:35 +0100 Subject: [jbosstools-dev] Test failing with Luna? Try the org.eclipse.osgi.compatibility.state fragment! In-Reply-To: <529E1C34.6090808@redhat.com> References: <5298D889.8010606@redhat.com> <529E1C34.6090808@redhat.com> Message-ID: <20131203183535.GU9510@slowbeard.local> we really need to limit these "add a big feature with 90+ plugins" just to fix what looks like a luna change we need to fix sooner rather than later. i.e. why was it not sufficient to apply Denis one plugin add instead of the full rcp feature ? /max On Tue, Dec 03, 2013 at 07:00:20PM +0100, Mickael Istria wrote: >On popular request, I've changed the parent pom to add the >org.eclipse.e4.rcp feature as suggested by Snjezana. This should make >some tests now more or less magically work better. >This is a temporary fix, so that as soon as we have a TP containing >fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 , we'll >remove this dependency in surefire to get back to a smaller set of >dependencies during tests. > >More of the story at https://issues.jboss.org/browse/JBIDE-16161 >-- >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 mistria at redhat.com Tue Dec 3 13:51:45 2013 From: mistria at redhat.com (Mickael Istria) Date: Tue, 03 Dec 2013 19:51:45 +0100 Subject: [jbosstools-dev] Test failing with Luna? Try the org.eclipse.osgi.compatibility.state fragment! In-Reply-To: <20131203183535.GU9510@slowbeard.local> References: <5298D889.8010606@redhat.com> <529E1C34.6090808@redhat.com> <20131203183535.GU9510@slowbeard.local> Message-ID: <529E2841.7090203@redhat.com> On 12/03/2013 07:35 PM, Max Rydahl Andersen wrote: > we really need to limit these "add a big feature with 90+ plugins" > just to fix what looks like a luna change we need to fix sooner rather > than later. > i.e. why was it not sufficient to apply Denis one plugin add instead > of the full rcp feature ? Denis' patch didn't fix everything according to Snjezana (cf comments on JBIDE-16161). Running tests is a blocker, so I simply went for this "fits all" solution in a first time to make everyone a bit happier and more able to progress. This solution is temporary and dependencies will be refined later, when Eclipse code will be cleaned from dependency to these deprecated stuff. So if someone comes with a patch that works as well as the one that was merged with less dependencies, it will get merged. But from my POV, this is a temporary detail. -- 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/20131203/fffea731/attachment.html From helen3094 at sina.cn Tue Dec 3 23:38:38 2013 From: helen3094 at sina.cn (helen3094 at sina.cn) Date: Wed, 4 Dec 2013 12:38:38 +0800 Subject: [jbosstools-dev] Sport interval timer supplier from China Message-ID: An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131204/e151189e/attachment.html From mmurray at redhat.com Wed Dec 4 05:38:32 2013 From: mmurray at redhat.com (Michelle Murray) Date: Wed, 4 Dec 2013 05:38:32 -0500 (EST) Subject: [jbosstools-dev] Action Required: Apply docs PRs for upcoming release In-Reply-To: <1893279777.5455369.1386153431739.JavaMail.root@redhat.com> References: <1893279777.5455369.1386153431739.JavaMail.root@redhat.com> Message-ID: <1308326015.5457317.1386153512721.JavaMail.root@redhat.com> Hello Devs, The PRs below are to update the book version numbers for the upcoming JBDS/JBT release. https://github.com/jbosstools/jbosstools-birt/pull/16 https://github.com/jbosstools/jbosstools-bpel/pull/20 https://github.com/jbosstools/jbosstools-central/pull/192 [done - thanks Fred] https://github.com/jbosstools/jbosstools-esb/pull/46 https://github.com/jbosstools/jbosstools-hibernate/pull/34 https://github.com/jbosstools/jbosstools-javaee/pull/178 https://github.com/jbosstools/jbosstools-portlet/pull/23 https://github.com/jbosstools/jbosstools-server/pull/182 https://github.com/jbosstools/jbosstools-webservices/pull/102 Please apply to 4.1.x branch only. And please apply ASAP. Thanks, Michelle -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131204/7f5e369d/attachment-0001.html From nboldt at redhat.com Thu Dec 5 00:04:13 2013 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 05 Dec 2013 00:04:13 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: JBT 4.2.0.Alpha1 / JBDS 8.0.0.Alpha1 Code Freeze & Branch is today (2013-12-05) Message-ID: <52A0094D.9050109@redhat.com> Thursday, December 05, 2013 is the code freeze & branch day for JBT 4.2.0.Alpha1 & JBDS 8.0.0.Alpha1, per the posted schedule [1]. This code freeze and branch day only involves projects included in JBoss Tools Core / JBoss Developer Studio, NOT the Integration Stack (i.e. bpel, esb, jbpm3, etc.) This build will be our first Alpha, built against Eclipse Luna M3 (4.4.0.M3). There are no respins planned, but are possible if needed. JIRAs for each component have been created to make it easy to perform the steps required to prepare for code freeze and create a new branch. See JIRAs below. [1] https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel JIRAs: JBDS : https://issues.jboss.org/browse/JBDS-2855 JBoss Tools : https://issues.jboss.org/browse/JBIDE-16226 Aerogear : https://issues.jboss.org/browse/JBIDE-16227 JST : https://issues.jboss.org/browse/JBIDE-16228 VPE : https://issues.jboss.org/browse/JBIDE-16229 JBT Update Sites : https://issues.jboss.org/browse/JBIDE-16230 Server : https://issues.jboss.org/browse/JBIDE-16231 Hibernate : https://issues.jboss.org/browse/JBIDE-16232 Base : https://issues.jboss.org/browse/JBIDE-16233 OpenShift : https://issues.jboss.org/browse/JBIDE-16234 JavaEE : https://issues.jboss.org/browse/JBIDE-16235 Birt : https://issues.jboss.org/browse/JBIDE-16236 GWT : https://issues.jboss.org/browse/JBIDE-16237 Forge : https://issues.jboss.org/browse/JBIDE-16238 Webservices : https://issues.jboss.org/browse/JBIDE-16239 Arquillian : https://issues.jboss.org/browse/JBIDE-16240 Central : https://issues.jboss.org/browse/JBIDE-16241 Portlet : https://issues.jboss.org/browse/JBIDE-16242 Freemarker : https://issues.jboss.org/browse/JBIDE-16243 Central Discovery : https://issues.jboss.org/browse/JBIDE-16244 Query: https://issues.jboss.org/issues/?jql=%28project%20in%20%28JBDS%29%20AND%20fixVersion%20%3D%20%228.0.0.Alpha1%22%20OR%20project%20in%20%28JBIDE%29%20AND%20fixVersion%20%3D%20%224.2.0.Alpha1%22%29%20AND%20labels%20%3D%20task -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Thu Dec 5 04:03:38 2013 From: mistria at redhat.com (Mickael Istria) Date: Thu, 05 Dec 2013 10:03:38 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: JBT 4.2.0.Alpha1 / JBDS 8.0.0.Alpha1 Code Freeze & Branch is today (2013-12-05) In-Reply-To: <52A0094D.9050109@redhat.com> References: <52A0094D.9050109@redhat.com> Message-ID: <52A0416A.10805@redhat.com> Here are some errors that IMO, requires to postpone the codefreeze: * jsf tests has a compilation errors * jbosstools-forge has compilation errors * jbosstools-vpe has compilation errors (related to the one in jsf) And some things that needs to be investigated: * jbosstools-base has test failures and timeout * jbosstools-central has test failures and timeout * jbosstools-hibernate has test timeout As a reminder, all this can be observed by looking at the jenkins status and reading the notifications sent by jenkins. Also, all those jobs are now built using the 4.40.0.Alpha1-SNAPSHOT which is based on Luna M3. So if you're done with JBT 4.1.1, you should make sure you're using this new target-platform while developing. -- 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/20131205/10ae0f56/attachment.html From mmalina at redhat.com Thu Dec 5 09:49:37 2013 From: mmalina at redhat.com (Martin Malina) Date: Thu, 5 Dec 2013 15:49:37 +0100 Subject: [jbosstools-dev] Offline groovy script not working? Message-ID: Hi Fred, I?m not sure you?re the right person for this. I wanted to do some doc reviewing today, so I wanted to try the groovy offline script (Preferences -> JBoss Tools -> Project Examples -> Offline Support). When I ran the script I saw a couple of errors along the way, see at the end of email. I was told that it could have to do with WFK 2.4 not being available in the online repo yet. But ultimately the script failed this exception: java.io.FileNotFoundException: /Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-javaee6-webapp-blank-archetype/my-jboss-javaee6-webapp-blank-archetype I know there have been some problems with the blank archetype, but I wanted to check if this is something known that is going to be fixed or not. If not, I will create a JIRA. The whole log of me running the script is here: https://dl.dropboxusercontent.com/u/20099120/groovy.log I was using JBDS 7.1.0.CR1b B560 (aka CR1) and had jboss nexus and http://maven.repository.redhat.com/techpreview/all/ in my settings.xml. After the script finished, the offline dir was 536M big. Thanks, Martin Building org.jboss.as.quickstarts:jboss-as-kitchensink-rf:7.1.2-SNAPSHOT default,arq-jbossas-managed,openshift,debug [ERROR] Failed to execute goal on project jboss-as-kitchensink-rf: Could not resolve dependencies for project org.jboss.as.quickstarts:jboss-as-kitchensink-rf:war:7.1.2-SNAPSHOT: Could not find artifact com.sun.faces:jsf-impl:jar:2.1.5-jbossorg-1 in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException Result: 1 Building org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final default,openshift,minify,arq-jbossas-managed,aerogearci-jbossas-managed-7,graph [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final (/Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-kitchensink-backbone.zip/pom.xml) has 1 error [ERROR] 'dependencies.dependency.version' for org.jboss.as:jboss-as-arquillian-container-managed:jar must be a valid version but is '${version.jboss.as}'. @ line 396, column 30 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException Result: 1 -- 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/20131205/3e0a2837/attachment.html From fbricon at redhat.com Thu Dec 5 10:29:30 2013 From: fbricon at redhat.com (Fred Bricon) Date: Thu, 05 Dec 2013 16:29:30 +0100 Subject: [jbosstools-dev] Offline groovy script not working? In-Reply-To: References: Message-ID: <52A09BDA.5020902@redhat.com> missing com.sun.faces:jsf-impl:jar:2.1.5-jbossorg-1 rings a bell, but I can't remember what repo is missing. Need to investigate. Please open a JIRA Le jeudi 5 d?cembre 2013 15:49:37, Martin Malina a ?crit : > Hi Fred, > > I?m not sure you?re the right person for this. > I wanted to do some doc reviewing today, so I wanted to try the groovy > offline script (Preferences -> JBoss Tools -> Project Examples -> > Offline Support). > When I ran the script I saw a couple of errors along the way, see at > the end of email. I was told that it could have to do with WFK 2.4 not > being available in the online repo yet. > But ultimately the script failed this exception: > java.io.FileNotFoundException: > /Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-javaee6-webapp-blank-archetype/my-jboss-javaee6-webapp-blank-archetype > > I know there have been some problems with the blank archetype, but I > wanted to check if this is something known that is going to be fixed > or not. If not, I will create a JIRA. The whole log of me running the > script is here: https://dl.dropboxusercontent.com/u/20099120/groovy.log > I was using JBDS 7.1.0.CR1b B560 (aka CR1) and had jboss nexus and > http://maven.repository.redhat.com/techpreview/all/ in my > settings.xml. After the script finished, the offline dir was 536M big. > > Thanks, > Martin > > Building > org.jboss.as.quickstarts:jboss-as-kitchensink-rf:7.1.2-SNAPSHOT > default,arq-jbossas-managed,openshift,debug > [ERROR] Failed to execute goal on project jboss-as-kitchensink-rf: > Could not resolve dependencies for > project org.jboss.as.quickstarts:jboss-as-kitchensink-rf:war:7.1.2-SNAPSHOT: > Could not find artifact com.sun.faces:jsf-impl:jar:2.1.5-jbossorg-1 in > redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) > -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with > the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > Result: 1 > > > Building > org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final > default,openshift,minify,arq-jbossas-managed,aerogearci-jbossas-managed-7,graph > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project > org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final (/Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-kitchensink-backbone.zip/pom.xml) > has 1 error > [ERROR] 'dependencies.dependency.version' for > org.jboss.as:jboss-as-arquillian-container-managed:jar must be a valid > version but is '${version.jboss.as}'. @ line 396, column 30 > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with > the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > Result: 1 > > > -- > Martin Malina > JBoss QA Engineer > Red Hat Czech s.r.o. > Purkynova 99 > 612 45 Brno, Czech Republic > > Tel.: +420 532 294 265 > > > > From mmalina at redhat.com Thu Dec 5 11:20:19 2013 From: mmalina at redhat.com (Martin Malina) Date: Thu, 5 Dec 2013 17:20:19 +0100 Subject: [jbosstools-dev] Offline groovy script not working? In-Reply-To: <52A09BDA.5020902@redhat.com> References: <52A09BDA.5020902@redhat.com> Message-ID: <409E9A46-D581-46B5-ABF1-7419AB27ADF2@redhat.com> Thanks, Fred. JIRA here: https://issues.jboss.org/browse/JBIDE-16249 -Martin On 5. 12. 2013, at 16:29, Fred Bricon wrote: > missing com.sun.faces:jsf-impl:jar:2.1.5-jbossorg-1 rings a bell, but I can't remember what repo is missing. > Need to investigate. Please open a JIRA > > > Le jeudi 5 d?cembre 2013 15:49:37, Martin Malina a ?crit : >> Hi Fred, >> >> I?m not sure you?re the right person for this. >> I wanted to do some doc reviewing today, so I wanted to try the groovy >> offline script (Preferences -> JBoss Tools -> Project Examples -> >> Offline Support). >> When I ran the script I saw a couple of errors along the way, see at >> the end of email. I was told that it could have to do with WFK 2.4 not >> being available in the online repo yet. >> But ultimately the script failed this exception: >> java.io.FileNotFoundException: >> /Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-javaee6-webapp-blank-archetype/my-jboss-javaee6-webapp-blank-archetype >> >> I know there have been some problems with the blank archetype, but I >> wanted to check if this is something known that is going to be fixed >> or not. If not, I will create a JIRA. The whole log of me running the >> script is here: https://dl.dropboxusercontent.com/u/20099120/groovy.log >> I was using JBDS 7.1.0.CR1b B560 (aka CR1) and had jboss nexus and >> http://maven.repository.redhat.com/techpreview/all/ in my >> settings.xml. After the script finished, the offline dir was 536M big. >> >> Thanks, >> Martin >> >> Building >> org.jboss.as.quickstarts:jboss-as-kitchensink-rf:7.1.2-SNAPSHOT >> default,arq-jbossas-managed,openshift,debug >> [ERROR] Failed to execute goal on project jboss-as-kitchensink-rf: >> Could not resolve dependencies for >> project org.jboss.as.quickstarts:jboss-as-kitchensink-rf:war:7.1.2-SNAPSHOT: >> Could not find artifact com.sun.faces:jsf-impl:jar:2.1.5-jbossorg-1 in >> redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) >> -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with >> the -e switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException >> Result: 1 >> >> >> Building >> org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final >> default,openshift,minify,arq-jbossas-managed,aerogearci-jbossas-managed-7,graph >> [ERROR] The build could not read 1 project -> [Help 1] >> [ERROR] >> [ERROR] The project >> org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final (/Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-kitchensink-backbone.zip/pom.xml) >> has 1 error >> [ERROR] 'dependencies.dependency.version' for >> org.jboss.as:jboss-as-arquillian-container-managed:jar must be a valid >> version but is '${version.jboss.as}'. @ line 396, column 30 >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with >> the -e switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException >> Result: 1 >> >> >> -- >> Martin Malina >> JBoss QA Engineer >> Red Hat Czech s.r.o. >> Purkynova 99 >> 612 45 Brno, Czech Republic >> >> Tel.: +420 532 294 265 >> >> >> >> > > -- 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/20131205/929015b5/attachment-0001.html From akazakov at exadel.com Thu Dec 5 12:27:56 2013 From: akazakov at exadel.com (Alexey Kazakov) Date: Thu, 05 Dec 2013 09:27:56 -0800 Subject: [jbosstools-dev] ACTION REQUIRED: JBT 4.2.0.Alpha1 / JBDS 8.0.0.Alpha1 Code Freeze & Branch is today (2013-12-05) In-Reply-To: <52A0416A.10805@redhat.com> References: <52A0094D.9050109@redhat.com> <52A0416A.10805@redhat.com> Message-ID: <52A0B79C.8020208@exadel.com> On 12/05/2013 01:03 AM, Mickael Istria wrote: > Here are some errors that IMO, requires to postpone the codefreeze: > * jsf tests has a compilation errors > * jbosstools-vpe has compilation errors (related to the one in jsf) JST must be rebuilt to eliminate these problems. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131205/1ee95157/attachment.html From mistria at redhat.com Fri Dec 6 04:49:32 2013 From: mistria at redhat.com (Mickael Istria) Date: Fri, 06 Dec 2013 10:49:32 +0100 Subject: [jbosstools-dev] Update your README.md Message-ID: <52A19DAC.9040301@redhat.com> Hi all, I've noticed that README.md files are not up-to-date and still point to old and unmaintained content. It would be nice if you could update them to direct to https://github.com/jbosstools/jbosstools-devdoc which is the place where we now maintain documentation for contributors/developers: https://issues.jboss.org/browse/JBIDE-16262 Thanks in advance, -- 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/20131206/2ae3e112/attachment.html From manderse at redhat.com Fri Dec 6 05:53:31 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 6 Dec 2013 11:53:31 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: JBT 4.2.0.Alpha1 / JBDS 8.0.0.Alpha1 Code Freeze & Branch is today (2013-12-05) In-Reply-To: <52A0416A.10805@redhat.com> References: <52A0094D.9050109@redhat.com> <52A0416A.10805@redhat.com> Message-ID: <20131206105331.GG26908@slowbeard.local> Guys - please remember Alpha1 is *not* meant to be without test errors. That is *normal* when we upgrade Eclipse release train. What alpha1 is for is to fix compilation errors and get issues found related to the upgrade - and any issue that can't be easily fixed gets a jira marked as critical for Alpha2 to look into. /max On Thu, Dec 05, 2013 at 10:03:38AM +0100, Mickael Istria wrote: >Here are some errors that IMO, requires to postpone the codefreeze: >* jsf tests has a compilation errors >* jbosstools-forge has compilation errors >* jbosstools-vpe has compilation errors (related to the one in jsf) > >And some things that needs to be investigated: >* jbosstools-base has test failures and timeout >* jbosstools-central has test failures and timeout >* jbosstools-hibernate has test timeout > >As a reminder, all this can be observed by looking at the jenkins >status and reading the notifications sent by jenkins. >Also, all those jobs are now built using the 4.40.0.Alpha1-SNAPSHOT >which is based on Luna M3. So if you're done with JBT 4.1.1, you >should make sure you're using this new target-platform while >developing. >-- >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 mistria at redhat.com Fri Dec 6 07:02:58 2013 From: mistria at redhat.com (Mickael Istria) Date: Fri, 06 Dec 2013 13:02:58 +0100 Subject: [jbosstools-dev] JBoss Tools target platform 4.40.0.Alpha1 Message-ID: <52A1BCF2.6010209@redhat.com> |JBoss Tools Target Platform 4.40.0.Alpha1 has been released. Changes ======= * m2e-apt 1.1.0 - JBIDE-16151 Usage ===== TP 4.40.0.Alpha1 is what JBoss Tools 4.2.0.Alpha1 will use. All jobs in jenkins for branch jbosstools-4.2.x have been updated to use TP 4.40.0.Alpha1. Parent pom 4.2.0.Alpha1 for branch jbosstools-4.2.x has been updated to use TP|||4.40.0.Alpha1|. All jobs in jenkins for *master* have been updated to use TP|||4.40.0.Alpha1|. Parent pom 4.2.0.Alpha2-SNAPSHOT for *master* has been updated to use TP|||4.40.0.Alpha1|. Download ======== Zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/|||4.40.0.Alpha1|/jbosstoolstarget-|||4.40.0.Alpha1|.zip p2 site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/|||4.40.0.Alpha1|/REPO/ Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/|||4.40.0.Alpha1| Testing/Development =================== You can try it out and use it directly like this: $ mvn clean verify -Dtpc.version=|||4.40.0.Alpha1| For advanced usage and help (using in IDE, building a mirror locally, using a zip...), plese read https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md What's next? ============ Branch 4.40.x for target platform has been prepared for potential upgrades, and it's version is now 4.40.0.Alpha2-SNAPSHOT.| -- 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/20131206/cd99c7c6/attachment.html From f at rehberf.mygbiz.com Sun Dec 8 11:51:55 2013 From: f at rehberf.mygbiz.com (Bluetooth Pedometer Supply) Date: Sun, 08 Dec 2013 16:51:55 +0000 Subject: [jbosstools-dev] =?gb2312?b?Qmx1ZXRvb3RoIFBlZG9tZXRlciBTdXBwbHk=?= =?gb2312?b?0+vE+rmyz+3By8/gsuGhow==?= Message-ID: <047d7b15b01d6bc21204ed08b2c8@google.com> Dear Sir or Madam, We specialize in electronic devices field with full experience and we have 100 % confidence in our technology and quality. Now our hot seller is pedometer. The new pedometer is more intelligent with more beautiful interface and easier operation. Pedometer is a little guy with the blueooth function can fit for ipone and ipad.Once connected with the phone by bluetooth,it can help you record the amount of exercise, calorie consumpion and master the time when you are exercising.Let you have a regular exercise and healthy body.Besides,it also supports off-line record function and reread the historical data records. If you are interested in,Pls contact me. Best regards, Kayla ELECTRONICS LIMITED Factory add:East of industry Rd, Longhua town, Bao"an district, Shenzhen, P.R.China https://picasaweb.google.com/lh/sredir?uname=103836980161342841172&target=ALBUM&id=5934322574886386289&authkey=Gv1sRgCMz1_5GWi5W1tQE&invite=CPuazvUP&feat=email -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131208/4630d573/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: picasaweblogo-zh_CN.gif Type: image/gif Size: 1646 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131208/4630d573/attachment-0001.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: email.jpg Type: image/jpeg Size: 6390 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131208/4630d573/attachment-0001.jpg From nboldt at redhat.com Sun Dec 8 23:38:47 2013 From: nboldt at redhat.com (Nick Boldt) Date: Sun, 08 Dec 2013 23:38:47 -0500 Subject: [jbosstools-dev] JBoss Tools Core 4.1.1.CR2 (Final?) bits available for QE testing Message-ID: <52A54957.2080902@redhat.com> As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. If QE passes these and no respin is required, they will be renamed Final. JBoss Tools Target Platforms: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kepler/ (JBoss Tools - current release) http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.31.1.Final (JBoss Tools - upcoming milestone) (This is loaded automatically into Eclipse when installing JBoss Tools. Provided here simply for reference.) Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.CR2.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.CR2.coretests/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.CR2.webtools/ Builds: http://download.jboss.org/jbosstools/builds/development/4.1.1.CR2.core/2013-12-08_01-06-33-B605 http://download.jboss.org/jbosstools/builds/development/4.1.1.CR2.coretests/2013-12-08_02-02-46-B401 http://download.jboss.org/jbosstools/builds/development/4.1.1.CR2.webtools/2013-12-08_01-06-33-B493 JBoss Central: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kepler/ (JBoss Central - current release) http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.31.0.Final/ (JBoss Central - 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.1.1.CR2/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.1.1.CR2/ -- 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 and http://docs.jboss.org/tools/whatsnew/ -- Schedule* / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel * - Note that CR2 is not a formal release in JIRA, but rather a build-toward-Final. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Sun Dec 8 23:55:37 2013 From: nboldt at redhat.com (Nick Boldt) Date: Sun, 08 Dec 2013 23:55:37 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: JBT 4.1.1 / JBDS 7.1.0 jobs are DISABLED :: JBT 4.2 / JBDS 8.0 jobs are ENABLED Message-ID: <52A54D49.5040308@redhat.com> If you plan to commit anything to the jbosstools-4.1.1.x branch, please be sure to let me know so that I can run your _41 or _71 job to pick up the commit. Otherwise, these jobs will remain disabled until they are needed again for JBT 4.1.2 / JBDS 7.1.1 builds, starting in Feb 2014. -- Meanwhile, the _42 and _80 jobs are enabled so that we can spin up the first JBT 4.2.0.Alpha1 / JBDS 8.0.0.Alpha1 builds this week. Any questions, please don't hesitate to ask. Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Mon Dec 9 07:31:12 2013 From: mistria at redhat.com (Mickael Istria) Date: Mon, 09 Dec 2013 13:31:12 +0100 Subject: [jbosstools-dev] JBoss Tools is branched for 4.2.0.Alpha1 Message-ID: <52A5B810.4020601@redhat.com> JBoss Tools is branched for 4.2.0.Alpha1 Branches: * https://github.com/jbosstools/jbosstools-base/tree/jbosstools-4.2.0.Alpha1x * https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.2.0.Alpha1x * ... Jobs: * http://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.2.luna/ Note that we are *code frozen* for 4.2.0.Alpha1, which means only urgent fixes should be done in the branch, associated w/ a JIRA. Trunk remains open for new development work. Where applicable, please remember to commit changes in BOTH trunk and the new branch. -- 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/20131209/31410f59/attachment.html From nboldt at redhat.com Mon Dec 9 15:57:44 2013 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 09 Dec 2013 15:57:44 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Test Failures in JBoss Tools 4.2.0.Alpha1 Message-ID: <52A62EC8.30009@redhat.com> If your project is listed below, please have a look at your latest build(s) and if you can reproduce the problems listed, please fix them in your master branch. There's no need to backport these to the Alpha1x branch unless they expose a real underlying blocker issue for which your project is entirely broken. These may be fixable by adding more time to the tests' pom.xml files (if it's a simple timeout due to network connectivity or some other process that takes longer on Jenkins than when you build locally) or else you might need to check for blocking UI or threads (in which case, no additional time will help as it's a flaw in the test). Note that for jobs that fail due to overall job timeout (server, javaee), I've doubled the timeout to 6hrs (360 mins). But really, should your component take more than 3hrs to build & run tests? Maybe some of those long-running tests should be moved to the integration tests project? [1] https://github.com/jbosstools/jbosstools-integration-tests/tree/master/tests ---- *webservices:* org.jboss.tools.ws.creation.core.test: Process timeout out after 3600 seconds *vpe:* Unstable (yellow) due to 1 test failure in org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent *server:* Build timed out (after 180 minutes) while testing. Some tests did not run. *jst:* org.jboss.tools.jst.web.kb.test: Process timeout out after 2400 seconds org.jboss.tools.jst.web.test: Process timeout out after 2400 seconds org.jboss.tools.jst.web.ui.test: Process timeout out after 2400 seconds *javaee:* Build timed out (after 180 minutes) while testing. Some tests did not run. *hibernate:* org.jboss.tools.hibernate.jpt.core.test: Process timeout out after 2400 seconds *central (maven):* org.jboss.tools.maven.sourcelookup.test: Process timeout out after 2400 seconds *base:* org.jboss.tools.common.model.test: Process timeout out after 2400 seconds *aerogear:* job misconfig (wrong path to all-tests/pom.xml), should be fixed now. respinning. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Tue Dec 10 03:34:25 2013 From: mistria at redhat.com (Mickael Istria) Date: Tue, 10 Dec 2013 09:34:25 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Test Failures in JBoss Tools 4.2.0.Alpha1 In-Reply-To: <52A62EC8.30009@redhat.com> References: <52A62EC8.30009@redhat.com> Message-ID: <52A6D211.4080806@redhat.com> On 12/09/2013 09:57 PM, Nick Boldt wrote: > These may be fixable by adding more time to the tests' pom.xml files (if > it's a simple timeout due to network connectivity or some other process > that takes longer on Jenkins than when you build locally) or else you > might need to check for blocking UI or threads (in which case, no > additional time will help as it's a flaw in the test). > > Note that for jobs that fail due to overall job timeout (server, > javaee), I've doubled the timeout to 6hrs (360 mins). > > But really, should your component take more than 3hrs to build & run > tests? Maybe some of those long-running tests should be moved to the > integration tests project? Most of these timeouts seem related to environmental issues on Jenkins (that I've reported to the team in charge of Jenkins). What's important if your component is listed is to make sure it works locally. If it does work locally but not on Jenkins, then it's our (Nick & I) problem. If it doesn't even work locally, it's yours ;) -- 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/20131210/f9a9b89e/attachment.html From nboldt at redhat.com Tue Dec 10 10:40:33 2013 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 10 Dec 2013 10:40:33 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Test Failures in JBoss Tools 4.2.0.Alpha1 In-Reply-To: <52A62EC8.30009@redhat.com> References: <52A62EC8.30009@redhat.com> Message-ID: <52A735F1.1010708@redhat.com> With double the time to run (6hrs instead of 3), these jobs are now showing test failures instead of build timeout: *server:* org.jboss.ide.eclipse.archives.test: Process timeout out after 2400 seconds org.jboss.ide.eclipse.archives.ui.test: Process timeout out after 2400 seconds https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-server_42/5/console *javaee:* org.jboss.tools.cdi.core.test: Process timeout out after 2400 seconds org.jboss.tools.jsf.test: Process timeout out after 3600 seconds org.jboss.tools.jsf.ui.test: Process timeout out after 3600 seconds org.jboss.tools.seam.core.test: Process timeout out after 1800 seconds org.jboss.tools.seam.ui.test: Process timeout out after 1800 seconds https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-javaee_42/6/console On 12/09/2013 03:57 PM, Nick Boldt wrote: > If your project is listed below, please have a look at your latest > build(s) and if you can reproduce the problems listed, please fix them > in your master branch. There's no need to backport these to the Alpha1x > branch unless they expose a real underlying blocker issue for which your > project is entirely broken. > > These may be fixable by adding more time to the tests' pom.xml files (if > it's a simple timeout due to network connectivity or some other process > that takes longer on Jenkins than when you build locally) or else you > might need to check for blocking UI or threads (in which case, no > additional time will help as it's a flaw in the test). > > Note that for jobs that fail due to overall job timeout (server, > javaee), I've doubled the timeout to 6hrs (360 mins). > > But really, should your component take more than 3hrs to build & run > tests? Maybe some of those long-running tests should be moved to the > integration tests project? > > [1] > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/tests > > > ---- > > *webservices:* > > org.jboss.tools.ws.creation.core.test: Process timeout out after 3600 > seconds > > *vpe:* > > Unstable (yellow) due to 1 test failure in > org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent > > > *server:* > > Build timed out (after 180 minutes) while testing. Some tests did not run. > > *jst:* > > org.jboss.tools.jst.web.kb.test: Process timeout out after 2400 seconds > org.jboss.tools.jst.web.test: Process timeout out after 2400 seconds > org.jboss.tools.jst.web.ui.test: Process timeout out after 2400 seconds > > *javaee:* > > Build timed out (after 180 minutes) while testing. Some tests did not run. > > *hibernate:* > > org.jboss.tools.hibernate.jpt.core.test: Process timeout out after 2400 > seconds > > *central (maven):* > > org.jboss.tools.maven.sourcelookup.test: Process timeout out after 2400 > seconds > > *base:* > > org.jboss.tools.common.model.test: Process timeout out after 2400 seconds > > *aerogear:* > > job misconfig (wrong path to all-tests/pom.xml), should be fixed now. > respinning. > > > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Tue Dec 10 13:18:11 2013 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 10 Dec 2013 13:18:11 -0500 Subject: [jbosstools-dev] Should we build JBT 4.2 with JDK 7? Message-ID: <52A75AE3.5030903@redhat.com> Three of the projects in JBoss Tools use JDK 7 for testing: Server, Webservices, and now Forge 2. This is accomplished in Jenkins like this: -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m -Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}" -Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}" -Djbosstools.test.jre.7="${NATIVE_TOOLS}${SEP}${JAVA17}" But all the projects still use JDK 6 to compile. java16_default Is that OK? Or is it time to consider moving to JDK 7 for building as well as running tests? If this warrants a JIRA, please open one and link to it from here. If not, discuss why it makes sense to stay with JDK 6 for compilation. If your project needs JDK 7 to run tests, and is not listed above, please open a JIRA or fix your _42 and _master jobs directly. If you can't fix your job (not sure how or don't have permission), email me or JIRA me and I'll fix your jobs for you. Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From bfitzpat at redhat.com Tue Dec 10 13:23:31 2013 From: bfitzpat at redhat.com (Brian Fitzpatrick) Date: Tue, 10 Dec 2013 13:23:31 -0500 (EST) Subject: [jbosstools-dev] Should we build JBT 4.2 with JDK 7? In-Reply-To: <52A75AE3.5030903@redhat.com> References: <52A75AE3.5030903@redhat.com> Message-ID: <1414879512.39483468.1386699811360.JavaMail.root@redhat.com> I we need to shift WS to build in JDK 7, that's fine. I'm honestly not sure of the need for JDK 5/6 support except for possibly runtime support back to JBoss AS 4.2. Open to suggestions. :) I'm working on the WS test failures now - been chatting with Alessio today and hopefully we can figure out what's going on and get it fixed finally. --Fitz _______________________________ Brian Fitzpatrick (aka "Fitz") Senior Software Engineer, SOA-P JBoss by Red Hat ----- Original Message ----- From: "Nick Boldt" To: jbosstools-dev at lists.jboss.org Sent: Tuesday, December 10, 2013 11:18:11 AM Subject: [jbosstools-dev] Should we build JBT 4.2 with JDK 7? Three of the projects in JBoss Tools use JDK 7 for testing: Server, Webservices, and now Forge 2. This is accomplished in Jenkins like this: -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m -Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}" -Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}" -Djbosstools.test.jre.7="${NATIVE_TOOLS}${SEP}${JAVA17}" But all the projects still use JDK 6 to compile. java16_default Is that OK? Or is it time to consider moving to JDK 7 for building as well as running tests? If this warrants a JIRA, please open one and link to it from here. If not, discuss why it makes sense to stay with JDK 6 for compilation. If your project needs JDK 7 to run tests, and is not listed above, please open a JIRA or fix your _42 and _master jobs directly. If you can't fix your job (not sure how or don't have permission), email me or JIRA me and I'll fix your jobs for you. Cheers, -- 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 mistria at redhat.com Wed Dec 11 04:08:49 2013 From: mistria at redhat.com (Mickael Istria) Date: Wed, 11 Dec 2013 10:08:49 +0100 Subject: [jbosstools-dev] Should we build JBT 4.2 with JDK 7? In-Reply-To: <52A75AE3.5030903@redhat.com> References: <52A75AE3.5030903@redhat.com> Message-ID: <52A82BA1.1000102@redhat.com> It would somehow make sense to follow the move of Eclipse packages: https://bugs.eclipse.org/bugs/show_bug.cgi?id=423734 . They're still using Java 6, but they discuss/plan to set Java 7 as minimal version for Luna. -- 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/20131211/c53cecfe/attachment.html From mistria at redhat.com Wed Dec 11 09:02:16 2013 From: mistria at redhat.com (Mickael Istria) Date: Wed, 11 Dec 2013 15:02:16 +0100 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Alpha1 bits available for QE testing Message-ID: <52A87068.1010408@redhat.com> JBoss Tools Core 4.2.0.Alpha1 bits available for QE testing As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Update Sites: * http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.core/ * http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.coretests/ * http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.webtools/ Builds: * http://download.jboss.org/jbosstools/builds/development/4.2.0.Alpha1.core/2013-12-11_01-09-15-B32 * http://download.jboss.org/jbosstools/builds/development/4.2.0.Alpha1.coretests/2013-12-11_01-35-01-B17 * http://download.jboss.org/jbosstools/builds/development/4.2.0.Alpha1.webtools/2013-12-11_01-09-15-B31 JBoss Central: * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kepler/ (JBoss Central - current release) * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Alpha1-SNAPSHOT/ (JBoss Central - 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.Alpha1/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Alpha1/ JBoss Tools Target Platforms (This is loaded automatically into Eclipse when installing JBoss Tools. Provided here simply for reference): * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kepler/ (JBoss Tools - current release) * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Alpha1 (JBoss Tools - upcoming milestone) New + Noteworthy: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstools-documentation/master/whatsnew/index.html (subject to change) and 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/20131211/7fb81229/attachment.html From nboldt at redhat.com Wed Dec 11 14:18:17 2013 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 11 Dec 2013 14:18:17 -0500 Subject: [jbosstools-dev] FYI :: Support Matrix Wiki updated :: JBT 4.2 / JBDS 8 / Eclipse 4.4 / Luna + target platform links Message-ID: <52A8BA79.8040502@redhat.com> This document now contains details about JBT 4.2 / JBDS 8 / Eclipse 4.4 / Luna. https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTechnologiesInJBossToolsJBDS I've also added a new section about target platforms and Central content. https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTechnologiesInJBossToolsJBDS#targetplatforms Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Thu Dec 12 16:41:05 2013 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 12 Dec 2013 16:41:05 -0500 Subject: [jbosstools-dev] JBoss Tools 4.1.1.Final is available Message-ID: <52AA2D71.1010908@redhat.com> JBoss Tools 4.1.1.Final is now available. This is a stable release aimed at Eclipse 4.3 (Kepler R or SR1) users. Eclipse Marketplace (updated from 4.1.0.1 to 4.1.1): https://marketplace.eclipse.org/content/jboss-tools-kepler Update Site (updated from 4.1.0.1 to 4.1.1): http://download.jboss.org/jbosstools/updates/stable/kepler/ Installation + Download Pages: http://www.jboss.org/tools/download http://www.jboss.org/tools/download/stable/4_1 http://www.jboss.org/tools/download/installation/update_4_1 JBoss Central: This release also includes changes, updates, and new content added to JBoss Central. For a list of changes, see https://issues.jboss.org/browse/JBDS-2710 -- 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 and 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 nboldt at redhat.com Thu Dec 12 17:00:45 2013 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 12 Dec 2013 17:00:45 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] Message-ID: <52AA320D.7090106@redhat.com> Project leads, please tag your projects! co jbosstools-4.1.1.x git tag jbosstools-4.1.1.Final git push origin jbosstools-4.1.1.Final (This single email replaces 17 Task JIRAs. If you prefer this approach, let me know. If you prefer JIRAs, let me know that too.) -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Thu Dec 12 17:23:25 2013 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 12 Dec 2013 17:23:25 -0500 Subject: [jbosstools-dev] JBDS 7.1.0.GA on Early Access Message-ID: <52AA375D.1090306@redhat.com> JBDS 7.1.0.GA Early Access installers are now available! https://devstudio.jboss.com/earlyaccess/ Note that bits may take a while to replicate from our staging server to publication. Please allow at least an hour before attempting to download them - if the page above still shows the previous CR1 milestone instead of 7.1.0.GA, try again later. -- JBoss Central This release also includes changes, updates, and new content added to JBoss Central. For a list of changes, see https://issues.jboss.org/browse/JBDS-2710 -- Eclipse Marketplace https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kepler -- Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion2s-panel -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From akazakov at exadel.com Thu Dec 12 19:09:28 2013 From: akazakov at exadel.com (Alexey Kazakov) Date: Thu, 12 Dec 2013 16:09:28 -0800 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AA320D.7090106@redhat.com> References: <52AA320D.7090106@redhat.com> Message-ID: <52AA5038.1060006@exadel.com> Done for base, jst and javaee On 12/12/2013 02:00 PM, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.1.1.x > git tag jbosstools-4.1.1.Final > git push origin jbosstools-4.1.1.Final > > > (This single email replaces 17 Task JIRAs. If you prefer this approach, > let me know. If you prefer JIRAs, let me know that too.) > From xcoulon at redhat.com Fri Dec 13 03:30:14 2013 From: xcoulon at redhat.com (Xavier Coulon) Date: Fri, 13 Dec 2013 09:30:14 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AA5038.1060006@exadel.com> References: <52AA320D.7090106@redhat.com> <52AA5038.1060006@exadel.com> Message-ID: <3CC079F2-6380-4B69-BF85-110AC7DDA86B@redhat.com> Done for LiveReload and WebServices. Best regards, /Xavier On Dec 13, 2013, at 1:09 AM, Alexey Kazakov wrote: > Done for base, jst and javaee > > On 12/12/2013 02:00 PM, Nick Boldt wrote: >> Project leads, please tag your projects! >> >> co jbosstools-4.1.1.x >> git tag jbosstools-4.1.1.Final >> git push origin jbosstools-4.1.1.Final >> >> >> (This single email replaces 17 Task JIRAs. If you prefer this approach, >> let me know. If you prefer JIRAs, let me know that too.) >> > > _______________________________________________ > 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/20131213/322203fc/attachment-0001.html From fbricon at redhat.com Fri Dec 13 06:59:29 2013 From: fbricon at redhat.com (Fred Bricon) Date: Fri, 13 Dec 2013 12:59:29 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <3CC079F2-6380-4B69-BF85-110AC7DDA86B@redhat.com> References: <52AA320D.7090106@redhat.com> <52AA5038.1060006@exadel.com> <3CC079F2-6380-4B69-BF85-110AC7DDA86B@redhat.com> Message-ID: <52AAF6A1.9080900@redhat.com> Central done Le 13/12/2013 09:30, Xavier Coulon a ?crit : > Done for LiveReload and WebServices. > > Best regards, > /Xavier > > > > On Dec 13, 2013, at 1:09 AM, Alexey Kazakov wrote: > >> Done for base, jst and javaee >> >> On 12/12/2013 02:00 PM, Nick Boldt wrote: >>> Project leads, please tag your projects! >>> >>> co jbosstools-4.1.1.x >>> git tag jbosstools-4.1.1.Final >>> git push origin jbosstools-4.1.1.Final >>> >>> >>> (This single email replaces 17 Task JIRAs. If you prefer this approach, >>> let me know. If you prefer JIRAs, let me know that too.) >>> >> >> _______________________________________________ >> 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 --- Ce courrier ?lectronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. http://www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131213/ac4863fb/attachment.html From snjezana.peco at redhat.com Fri Dec 13 07:37:02 2013 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Fri, 13 Dec 2013 13:37:02 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AA320D.7090106@redhat.com> References: <52AA320D.7090106@redhat.com> Message-ID: <52AAFF6E.9030007@redhat.com> I have done it for arquillian,birt and portlet. Snjeza On 12/12/2013 11:00 PM, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.1.1.x > git tag jbosstools-4.1.1.Final > git push origin jbosstools-4.1.1.Final > > > (This single email replaces 17 Task JIRAs. If you prefer this approach, > let me know. If you prefer JIRAs, let me know that too.) > From kmarmaliykov at exadel.com Fri Dec 13 08:11:11 2013 From: kmarmaliykov at exadel.com (Konstantin Marmalyukov) Date: Fri, 13 Dec 2013 16:11:11 +0300 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AA320D.7090106@redhat.com> References: <52AA320D.7090106@redhat.com> Message-ID: <52AB076F.4060507@exadel.com> Done for VPE. As for me, email is better notification way. On 12/13/2013 1:00 AM, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.1.1.x > git tag jbosstools-4.1.1.Final > git push origin jbosstools-4.1.1.Final > > > (This single email replaces 17 Task JIRAs. If you prefer this approach, > let me know. If you prefer JIRAs, let me know that too.) > From adietish at redhat.com Fri Dec 13 08:25:23 2013 From: adietish at redhat.com (=?ISO-8859-1?Q?Andr=E9_Dietisheim?=) Date: Fri, 13 Dec 2013 14:25:23 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AA320D.7090106@redhat.com> References: <52AA320D.7090106@redhat.com> Message-ID: <52AB0AC3.6090003@redhat.com> Done for openshift. btw. I personally prefer the jira approach, keeps jira as the single task-listing authority, no mail-spams "Yes, done here". On 12/12/2013 11:00 PM, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.1.1.x > git tag jbosstools-4.1.1.Final > git push origin jbosstools-4.1.1.Final > > > (This single email replaces 17 Task JIRAs. If you prefer this approach, > let me know. If you prefer JIRAs, let me know that too.) > From nboldt at redhat.com Fri Dec 13 10:41:30 2013 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 13 Dec 2013 10:41:30 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AB0AC3.6090003@redhat.com> References: <52AA320D.7090106@redhat.com> <52AB0AC3.6090003@redhat.com> Message-ID: <52AB2AAA.7020004@redhat.com> Thanks to everyone who's tagged! To reply to Andre's comment about jiras vs. emails (so far the only feedback): Task JIRAs still generate email... in fact, they generate way more (for me, anyway) because as the opener of all the JIRAs, I get one for each status change of: "assigned to ___" "started working", "resolved", and "closed". So that's generally 1 or 2 JIRA emails for each of the 17 projects. OTOH, when people reply to the mailing list on this thread, then EVERYONE sees the confirmation/acknowledgement - but for people who can tag multiple projects, it reduces their overhead from 3 x 2 JIRAs down to 1 single email. Replying to me directly would produce the same confirmation response but w/o the list-spam & dozens of people hitting their delete keys. :) What about having *1 JIRA for all project tagging*, and everyone can just comment there when done, without having to take ownership of the JIRA? That would provide tracking/confirmation/auditing/accountability, and also reduce the amount of mail generated. As a project lead, you'd still get everyone's "___ is tagged" emails as generated by JIRA, but then the whole world wouldn't also see their spammy goodness in jbosstools-dev at . WDYT? N On 12/13/2013 08:25 AM, Andr? Dietisheim wrote: > Done for openshift. > > btw. I personally prefer the jira approach, keeps jira as the single > task-listing authority, no mail-spams "Yes, done here". > > On 12/12/2013 11:00 PM, Nick Boldt wrote: >> Project leads, please tag your projects! >> >> co jbosstools-4.1.1.x >> git tag jbosstools-4.1.1.Final >> git push origin jbosstools-4.1.1.Final >> >> >> (This single email replaces 17 Task JIRAs. If you prefer this approach, >> let me know. If you prefer JIRAs, let me know that too.) >> > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Fri Dec 13 10:57:15 2013 From: mistria at redhat.com (Mickael Istria) Date: Fri, 13 Dec 2013 16:57:15 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AB2AAA.7020004@redhat.com> References: <52AA320D.7090106@redhat.com> <52AB0AC3.6090003@redhat.com> <52AB2AAA.7020004@redhat.com> Message-ID: <52AB2E5B.8050903@redhat.com> On 12/13/2013 04:41 PM, Nick Boldt wrote: > What about having *1 JIRA for all project tagging*, and everyone can > just comment there when done, without having to take ownership of the > JIRA? That would provide tracking/confirmation/auditing/accountability, > and also reduce the amount of mail generated. Yes, that would be the best thing IMO. The Jira would list all projects, and everytime a repository is tagged, developer come to Jira and says it's done. We close the Jira when all projects are done. -- 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/20131213/0a43d0e9/attachment.html From adietish at redhat.com Fri Dec 13 11:57:54 2013 From: adietish at redhat.com (=?UTF-8?B?QW5kcsOpIERpZXRpc2hlaW0=?=) Date: Fri, 13 Dec 2013 17:57:54 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AB2AAA.7020004@redhat.com> References: <52AA320D.7090106@redhat.com> <52AB0AC3.6090003@redhat.com> <52AB2AAA.7020004@redhat.com> Message-ID: <52AB3C92.4040803@redhat.com> a single global jira works for me too, as would any solution, no big deal. It's more that I love to have my item in my task-list (jira assigned to me). On 12/13/2013 04:41 PM, Nick Boldt wrote: > Thanks to everyone who's tagged! > > To reply to Andre's comment about jiras vs. emails (so far the only > feedback): > > Task JIRAs still generate email... in fact, they generate way more > (for me, anyway) because as the opener of all the JIRAs, I get one for > each status change of: "assigned to ___" "started working", > "resolved", and "closed". So that's generally 1 or 2 JIRA emails for > each of the 17 projects. > > OTOH, when people reply to the mailing list on this thread, then > EVERYONE sees the confirmation/acknowledgement - but for people who > can tag multiple projects, it reduces their overhead from 3 x 2 JIRAs > down to 1 single email. > > Replying to me directly would produce the same confirmation response > but w/o the list-spam & dozens of people hitting their delete keys. :) > > What about having *1 JIRA for all project tagging*, and everyone can > just comment there when done, without having to take ownership of the > JIRA? That would provide > tracking/confirmation/auditing/accountability, and also reduce the > amount of mail generated. > > As a project lead, you'd still get everyone's "___ is tagged" emails > as generated by JIRA, but then the whole world wouldn't also see their > spammy goodness in jbosstools-dev at . > > WDYT? > > N > > On 12/13/2013 08:25 AM, Andr? Dietisheim wrote: >> Done for openshift. >> >> btw. I personally prefer the jira approach, keeps jira as the single >> task-listing authority, no mail-spams "Yes, done here". >> >> On 12/12/2013 11:00 PM, Nick Boldt wrote: >>> Project leads, please tag your projects! >>> >>> co jbosstools-4.1.1.x >>> git tag jbosstools-4.1.1.Final >>> git push origin jbosstools-4.1.1.Final >>> >>> >>> (This single email replaces 17 Task JIRAs. If you prefer this approach, >>> let me know. If you prefer JIRAs, let me know that too.) >>> >> > From rstryker at redhat.com Mon Dec 16 02:03:40 2013 From: rstryker at redhat.com (Rob Stryker) Date: Mon, 16 Dec 2013 15:03:40 +0800 Subject: [jbosstools-dev] Question on BPEL publisher Message-ID: <52AEA5CC.7010109@redhat.com> Looking over the code of BPEL's publisher, it is very different from most publishers we have. First, it does not respond to incremental publish requests. Second, it only works in local mode, not remote mode. And third, it seems to publish multiple jars, rather than simply overwriting the previous one. Fourth, the publisher itself seems to keep a little model of how many jars were deployed with what versions, something that's pretty non-standard. I'm currently trying to unify some of the publisher's actions and to ensure that they work for all use cases. With this in mind, we must remember we may be switching to a management deployment in the near future. And, of course, if possible, I'd like to ensure all modules can be published in some way regardless of configuration. So I'd like to gather some requirements from you all on how exactly you'd like a server set up to deploy to RSE mode, or to deploy using management api only, to actually function with regards to a bpel module. Thanks. - Rob Stryker From manderse at redhat.com Mon Dec 16 07:18:11 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 16 Dec 2013 13:18:11 +0100 Subject: [jbosstools-dev] jbosstools-issues backlog Message-ID: Hey, Last week update of mail alias from jira-events at lists.jboss.org to issues at jboss.org caused a rather big backlog of emails to get put on hold for jbosstools-issues. Thus if you feel you have missed some jira notifications from jbosstools-issues that should explain it ;) I am unfortunately only a moderator of the list so I can?t do admin tasks on it - I?ve opened a ticket against help at jboss.org to get those resolved. I?ll let you know when there are movement on getting the mailing list issue fix. Thanks, Max From manderse at redhat.com Mon Dec 16 16:40:35 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 16 Dec 2013 22:40:35 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ] In-Reply-To: <52AA320D.7090106@redhat.com> References: <52AA320D.7090106@redhat.com> Message-ID: <35D89FD5-8B7D-47A7-80FF-DFB50D5D1C05@redhat.com> One key point missing here - please be sure jbosstools-4.1.x have all the commits that 4.1.1.Final has. A few days ago that was not the case for all repositories! /max On 12 Dec 2013, at 23:00, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.1.1.x > git tag jbosstools-4.1.1.Final > git push origin jbosstools-4.1.1.Final > > > (This single email replaces 17 Task JIRAs. If you prefer this approach, > let me know. If you prefer JIRAs, let me know that too.) > > -- > 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 mistria at redhat.com Tue Dec 17 09:22:51 2013 From: mistria at redhat.com (Mickael Istria) Date: Tue, 17 Dec 2013 15:22:51 +0100 Subject: [jbosstools-dev] XulRunner & SWT over GTK3 Message-ID: <52B05E3B.6010701@redhat.com> Hi all, Many of us have identified a major bug leading to Eclipse crash when using JBT 4.2.0.Alpha1 and Eclipse Luna. https://issues.jboss.org/browse/JBIDE-16280 , https://issues.jboss.org/browse/JBIDE-16308 , https://issues.jboss.org/browse/JBIDE-16290 . Xulrunner binaries we have don't work on GTK3 (which is next Eclipse default implementation for SWT on Linux). Apparently there is no xulrunner available which works with GTK3, and anyway, the dependency on discontinued JavaXPCom seems to show that it's impossible to find a set of compatible SWT/GTK3/XulRunner/JavaXPCom libraries that can work together. This makes that currently, we don't have any way to get XulRunner and VPE working on Linux. They currently crash the workbench, but even if we workaround that (by checking the gtk version used and avoid invoking xulrunner when using GTK3) we can't have this feature working. What do we do from here? It seems like the recommended way (from old messages on JavaXPCom list) is to use WebKitGTK+ on Linux instead of xulrunner. For more uniformity, it would require to get rid of xulrunner for other OS and rely fully on Webkit and a Java binding such as webkit driver. Is this a right path to follow? If yes, this should be started very soon, except if we prefer dropping the whole VPE in favour of something else. 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/20131217/2bbc6a95/attachment.html From mistria at redhat.com Tue Dec 17 13:35:10 2013 From: mistria at redhat.com (Mickael Istria) Date: Tue, 17 Dec 2013 19:35:10 +0100 Subject: [jbosstools-dev] New approach to inter-JBT dependencies Message-ID: <52B0995E.3070401@redhat.com> Hi all, Small steps after small steps, we're coming to a simpler and more explicit approach to inter-JBT dependency management. We used to have a composite site linking to all components and consume this in any component to resolve dependencies. This had major pitfalls: * It allows cyclic dependencies between components * Some deleted bundles can remain because they're in the composite * It is not very explicit in term of what depends on what So we'll soon get rid of it, and replace this composite by direct reference to necessary other component sites in root pom (for each component) and by removing the composite site and related profiles. Here is how things will change: https://github.com/mickaelistria/jbosstools-javaee/commit/26c37d2f2f7f2631039f5027dd4e2e79bbdb3d7e Default value for jbosstools-site-stream variable will be controlled by parent pom. This change shouldn't require you anything. At the contrary, this change will be the opportunity for you and us to drop some counter-intuitive things and save some space in our memories to put nice souvenirs there instead. If you have any comment or question, feel free to ask them in https://issues.jboss.org/browse/JBIDE-16309 . So get ready for a bunch of incoming PR for your component to add these repositories! 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/20131217/ce9192db/attachment.html From j at wefwef.export-supply.com Tue Dec 17 21:43:23 2013 From: j at wefwef.export-supply.com (video card) Date: Wed, 18 Dec 2013 02:43:23 +0000 Subject: [jbosstools-dev] =?gb2312?b?dmlkZW8gY2FyZNPrxPq5ss/twcvP4LLhoaM=?= Message-ID: <047d7b15fc8134c79704edc602e0@google.com> Dear Sir or Madam, Electronics Co.,Ltd here. We specialize in electronic devices field with full experience and we have 100 % confidence in our technology and quality. Now our hot seller is video card ? Video card is a digital product just like a Mp4 with a printing paper to cover it . You can design the artwork of the paper , and put the video you prefer into it . Usually we used the video card for business promotion or as the gift to your customers or friends . If any interest, feel free to contact me. Best regards, Cherry Sales Specialist ELECTRONIC LIMITED https://picasaweb.google.com/lh/sredir?uname=104427823977869399650&target=ALBUM&id=5941680223443839745&authkey=Gv1sRgCJzutaKbpMHEhQE&invite=COvvs9YG&feat=email -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131218/5362d957/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: picasaweblogo-zh_CN.gif Type: image/gif Size: 1646 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131218/5362d957/attachment-0001.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: email.jpg Type: image/jpeg Size: 5640 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131218/5362d957/attachment-0001.jpg From mistria at redhat.com Wed Dec 18 04:39:41 2013 From: mistria at redhat.com (Mickael Istria) Date: Wed, 18 Dec 2013 10:39:41 +0100 Subject: [jbosstools-dev] AngularJS Eclipse Message-ID: <52B16D5D.1080703@redhat.com> Hi all, I've noticed this project https://github.com/angelozerr/angularjs-eclipse/wiki/HTML-Features . Does anyone know about it. Is it better than what we have in JBT? 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/20131218/cc67ef81/attachment.html From manderse at redhat.com Wed Dec 18 06:30:04 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 18 Dec 2013 12:30:04 +0100 Subject: [jbosstools-dev] AngularJS Eclipse In-Reply-To: <52B16D5D.1080703@redhat.com> References: <52B16D5D.1080703@redhat.com> Message-ID: <89900AAA-6088-4B06-B111-487F4FC1C065@redhat.com> On 18 Dec 2013, at 10:39, Mickael Istria wrote: > Hi all, > > I've noticed this project https://github.com/angelozerr/angularjs-eclipse/wiki/HTML-Features . > Does anyone know about it. Is it better than what we have in JBT? It wasn?t until recently. Now it provides code completions we don?t. I?ve tried reach out to the guy on twitter 3-4 times - he have not responded. Maybe he will react to someone pinging him from France (he is french afaik ;) /max -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131218/6b80b908/attachment.html From mistria at redhat.com Wed Dec 18 06:39:25 2013 From: mistria at redhat.com (Mickael Istria) Date: Wed, 18 Dec 2013 12:39:25 +0100 Subject: [jbosstools-dev] AngularJS Eclipse In-Reply-To: <89900AAA-6088-4B06-B111-487F4FC1C065@redhat.com> References: <52B16D5D.1080703@redhat.com> <89900AAA-6088-4B06-B111-487F4FC1C065@redhat.com> Message-ID: <52B1896D.2090004@redhat.com> On 12/18/2013 12:30 PM, Max Rydahl Andersen wrote: > Maybe he will react to someone pinging him from France (he is french > afaik ;) We've helped one another in the past on Developpez forum. I'll see whether this helps to get his feedback. It seems to me that he's doing an alternate HTML editor dedicated to Angular. IMO, this is not ideal from a usability POV. -- 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/20131218/ba99ff5c/attachment.html From manderse at redhat.com Wed Dec 18 08:45:57 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 18 Dec 2013 14:45:57 +0100 Subject: [jbosstools-dev] XulRunner & SWT over GTK3 In-Reply-To: <52B05E3B.6010701@redhat.com> References: <52B05E3B.6010701@redhat.com> Message-ID: <63EC2F1F-745B-401F-BA41-686A5948BAD7@redhat.com> On 17 Dec 2013, at 15:22, Mickael Istria wrote: > Hi all, > > Many of us have identified a major bug leading to Eclipse crash when using JBT 4.2.0.Alpha1 and Eclipse Luna. https://issues.jboss.org/browse/JBIDE-16280 , https://issues.jboss.org/browse/JBIDE-16308 , https://issues.jboss.org/browse/JBIDE-16290 . > Xulrunner binaries we have don't work on GTK3 (which is next Eclipse default implementation for SWT on Linux). Apparently there is no xulrunner available which works with GTK3, and anyway, the dependency on discontinued JavaXPCom seems to show that it's impossible to find a set of compatible SWT/GTK3/XulRunner/JavaXPCom libraries that can work together. > This makes that currently, we don't have any way to get XulRunner and VPE working on Linux. They currently crash the workbench, but even if we workaround that (by checking the gtk version used and avoid invoking xulrunner when using GTK3) we can't have this feature working. > > What do we do from here? Curses native code and how it always ends up hurting us ? :) > It seems like the recommended way (from old messages on JavaXPCom list) is to use WebKitGTK+ on Linux instead of xulrunner. For more uniformity, it would require to get rid of xulrunner for other OS and rely fully on Webkit and a Java binding such as webkit driver. Konstantin, Ilya and Denis is and have been working on using JavaFX Webview (based on webkit) as a replacement for xulrunner. Been discussed in various Jiras, confcalls and face-2-face meetings. We should know something soon on feasibility of it. > Is this a right path to follow? If yes, this should be started very soon, except if we prefer dropping the whole VPE in favour of something else. I don?t understand what the difference is between this path and ?dropping the whole of VPE in favour of something else? ? /max -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131218/0dd81d63/attachment.html From manderse at redhat.com Wed Dec 18 08:47:02 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 18 Dec 2013 14:47:02 +0100 Subject: [jbosstools-dev] AngularJS Eclipse In-Reply-To: <52B1896D.2090004@redhat.com> References: <52B16D5D.1080703@redhat.com> <89900AAA-6088-4B06-B111-487F4FC1C065@redhat.com> <52B1896D.2090004@redhat.com> Message-ID: <4CBC3C0F-3906-4274-80B3-ED9F13362189@redhat.com> On 18 Dec 2013, at 12:39, Mickael Istria wrote: > On 12/18/2013 12:30 PM, Max Rydahl Andersen wrote: >> Maybe he will react to someone pinging him from France (he is french afaik ;) > We've helped one another in the past on Developpez forum. I'll see whether this helps to get his feedback. > It seems to me that he's doing an alternate HTML editor dedicated to Angular. IMO, this is not ideal from a usability POV. yup exactly. would be better if he could contribute to jbosstools editor or even JSDT editor. /max From mistria at redhat.com Wed Dec 18 09:47:16 2013 From: mistria at redhat.com (Mickael Istria) Date: Wed, 18 Dec 2013 15:47:16 +0100 Subject: [jbosstools-dev] AngularJS Eclipse In-Reply-To: <52B16D5D.1080703@redhat.com> References: <52B16D5D.1080703@redhat.com> Message-ID: <52B1B574.1070209@redhat.com> More technical details: https://github.com/angelozerr/angularjs-eclipse/wiki/Technical-information He doesn't seem very motivated to contribute to JSDT yet... -- 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/20131218/0d440171/attachment.html From akazakov at exadel.com Wed Dec 18 13:51:39 2013 From: akazakov at exadel.com (Alexey Kazakov) Date: Wed, 18 Dec 2013 10:51:39 -0800 Subject: [jbosstools-dev] AngularJS Eclipse In-Reply-To: <89900AAA-6088-4B06-B111-487F4FC1C065@redhat.com> References: <52B16D5D.1080703@redhat.com> <89900AAA-6088-4B06-B111-487F4FC1C065@redhat.com> Message-ID: <52B1EEBB.20700@exadel.com> On 12/18/2013 03:30 AM, Max Rydahl Andersen wrote: > > On 18 Dec 2013, at 10:39, Mickael Istria > wrote: > >> Hi all, >> >> I've noticed this project >> https://github.com/angelozerr/angularjs-eclipse/wiki/HTML-Features . >> Does anyone know about it. Is it better than what we have in JBT? > > It wasn't until recently. Now it provides code completions we don't. What code completion it provide we don't? It provides ng-* completion which we do too. And IMO ours is better since we provide context-dependent code completion. For example we suggest count/when/... attributes only for ng-pluralize directives ( or ) Or ng-maxlength only for input directives. Or we don't suggest ng-app if it's already defined in any parent tag. Etc. So we analyze the context when calculating what can be suggested in the particular place. angularjs-eclipse seems to suggest a fixed list (very limited) of most used ng-* directives for html tags. It does not provide code completion for {{}} expressions which we plan to do in JBT 4.2. The upstream project https://github.com/angelozerr/tern.java/wiki/Tern-Eclipse-IDE is supposed to provide some angular specific code completion in *.js files but I couldn't manage to make it work. The good thing in that tools we don't have in JBT is ng-* and {{}} highlighting. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131218/dba24e0e/attachment-0001.html From fbricon at gmail.com Wed Dec 18 16:35:53 2013 From: fbricon at gmail.com (Fred Bricon) Date: Wed, 18 Dec 2013 22:35:53 +0100 Subject: [jbosstools-dev] m2e-wtp 1.1.0 Luna M4 build available Message-ID: m2e-wtp 1.1.0 Luna M4 build (1.1.0.20131218-1954) is available from the p2 repository at [1]. It's also compatible with Eclipse Kepler. See [2] for a short but complete list of bug fixes and improvements for this milestone release. Please test this version and report any bugs you find to Bugzilla [3]. [1] http://download.eclipse.org/m2e-wtp/milestones/luna/1.1.0 [2] https://bugs.eclipse.org/bugs/buglist.cgi?resolution=FIXED&query_format=advanced&product=M2E-WTP&target_milestone=1.1.0%2FLuna%20M4&list_id=7783989 [3] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP Regards, Fred Bricon -- "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/20131218/e013a1ba/attachment.html From manderse at redhat.com Thu Dec 19 05:51:06 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 19 Dec 2013 11:51:06 +0100 Subject: [jbosstools-dev] Should we build JBT 4.2 with JDK 7? In-Reply-To: <1414879512.39483468.1386699811360.JavaMail.root@redhat.com> References: <52A75AE3.5030903@redhat.com> <1414879512.39483468.1386699811360.JavaMail.root@redhat.com> Message-ID: On 10 Dec 2013, at 19:23, Brian Fitzpatrick wrote: > I we need to shift WS to build in JDK 7, that's fine. I'm honestly not sure of the need for JDK 5/6 support except for possibly runtime support back to JBoss AS 4.2. Do we still run the generation via the server provided scripts and in an external process ? Then this would continue to work. If we run it in ?in-process? of eclipse, then yeah - that could be a problem but doesn?t the WS generation supporting targeting different versions of the spec ? /max > > Open to suggestions. :) > > I'm working on the WS test failures now - been chatting with Alessio today and hopefully we can figure out what's going on and get it fixed finally. > > --Fitz > > _______________________________ > Brian Fitzpatrick (aka "Fitz") > Senior Software Engineer, SOA-P > JBoss by Red Hat > > ----- Original Message ----- > From: "Nick Boldt" > To: jbosstools-dev at lists.jboss.org > Sent: Tuesday, December 10, 2013 11:18:11 AM > Subject: [jbosstools-dev] Should we build JBT 4.2 with JDK 7? > > Three of the projects in JBoss Tools use JDK 7 for testing: Server, > Webservices, and now Forge 2. > > This is accomplished in Jenkins like this: > > -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m > -Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}" > -Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}" > -Djbosstools.test.jre.7="${NATIVE_TOOLS}${SEP}${JAVA17}" > > But all the projects still use JDK 6 to compile. > > java16_default > > > Is that OK? Or is it time to consider moving to JDK 7 for building as > well as running tests? > > > If this warrants a JIRA, please open one and link to it from here. If > not, discuss why it makes sense to stay with JDK 6 for compilation. > > If your project needs JDK 7 to run tests, and is not listed above, > please open a JIRA or fix your _42 and _master jobs directly. If you > can't fix your job (not sure how or don't have permission), email me or > JIRA me and I'll fix your jobs for you. > > Cheers, > > -- > 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 > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From manderse at redhat.com Thu Dec 19 05:54:39 2013 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 19 Dec 2013 11:54:39 +0100 Subject: [jbosstools-dev] Should we build JBT 4.2 with JDK 7? In-Reply-To: <52A75AE3.5030903@redhat.com> References: <52A75AE3.5030903@redhat.com> Message-ID: <63813D42-D8CE-43A2-AA3D-C48B4BDFB81A@redhat.com> For now I say, keep the jdk build requirement as low as possible. Don?t just raise it to JDK 7 without the component actually needing/wanting it. That said - Java 7 is what we should be targeting for *running* JBT/JBDS since it is actually starting to be hard to get Java 6 on some machines ;) One downside of moving from Java 6 to 7 is though we loose the option of 32-bit JVM on OSX which in turn means we cannot support the visual part of VPE on OSX anymore. But since VPE uses xulrunner which looks like it can?t run on GTK3 anymore we need to find another solution for that anyway. /max On 10 Dec 2013, at 19:18, Nick Boldt wrote: > Three of the projects in JBoss Tools use JDK 7 for testing: Server, > Webservices, and now Forge 2. > > This is accomplished in Jenkins like this: > > -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m > -Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}" > -Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}" > -Djbosstools.test.jre.7="${NATIVE_TOOLS}${SEP}${JAVA17}" > > But all the projects still use JDK 6 to compile. > > java16_default > > > Is that OK? Or is it time to consider moving to JDK 7 for building as > well as running tests? > > > If this warrants a JIRA, please open one and link to it from here. If > not, discuss why it makes sense to stay with JDK 6 for compilation. > > If your project needs JDK 7 to run tests, and is not listed above, > please open a JIRA or fix your _42 and _master jobs directly. If you > can't fix your job (not sure how or don't have permission), email me or > JIRA me and I'll fix your jobs for you. > > Cheers, > > -- > 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 dietisheim at puzzle.ch Thu Dec 19 18:41:25 2013 From: dietisheim at puzzle.ch (=?ISO-8859-1?Q?Andr=E9_Dietisheim?=) Date: Fri, 20 Dec 2013 00:41:25 +0100 Subject: [jbosstools-dev] create github pull-requests in Eclipse Message-ID: <52B38425.5080306@puzzle.ch> Hi folks Thought that this would be interesting for most of us: A handy plugin (I once wanted to create but never found the time to do it) that allows you to create pull-requests within Eclipse: http://eclipseo.blogspot.fr/2013/06/eclipse-plugin-for-raising-pullrequest.html I did not test it yet... maybe you'll do before I can? Cheers Andr? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131220/c2fd4bc7/attachment.html From nboldt at redhat.com Thu Dec 19 23:45:09 2013 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 19 Dec 2013 23:45:09 -0500 Subject: [jbosstools-dev] JBoss Tools 4.2.0.Alpha1 is available Message-ID: <52B3CB55.70001@redhat.com> JBoss Tools 4.2.0.Alpha1 is now available. This is a development release aimed at Eclipse 4.4 (Luna M3) users. PLEASE NOTE! Linux users will experience a crash using the Visual Page Editor (VPE) unless they use one of these workarounds: https://www.jboss.org/tools/download/dev/4_2_x#noteGTK3 Update Site: http://download.jboss.org/jbosstools/updates/development/luna/ Download Pages: http://www.jboss.org/tools/download http://www.jboss.org/tools/download/dev/4_2_x 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 and 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 nboldt at redhat.com Thu Dec 19 23:48:04 2013 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 19 Dec 2013 23:48:04 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Alpha1x -> tag jbosstools-4.2.0.Alpha1 ] Message-ID: <52B3CC04.7030605@redhat.com> Project leads, please tag your projects! co jbosstools-4.2.0.Alpha1x git tag jbosstools-4.2.0.Alpha1 git push origin jbosstools-4.2.0.Alpha1 You do not need to reply to this email. Simply comment in this JIRA when tagging is complete: https://issues.jboss.org/browse/JBIDE-16317 Thanks, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From xcoulon at redhat.com Fri Dec 20 13:07:55 2013 From: xcoulon at redhat.com (Xavier Coulon) Date: Fri, 20 Dec 2013 19:07:55 +0100 Subject: [jbosstools-dev] Preview of upcoming website Message-ID: <086F3104-5691-46D3-8226-A490BC823A5F@redhat.com> Hello everyone ! We finally have a draft of the upcoming website to share with you. It's not complete, but it's hopefully in a good enough shape so you can take a look at it and see how it's organized: http://jbosstools.github.io/jbosstools-website/ The code source for the site is on the github repo (on the 'master' branch): https://github.com/jbosstools/jbosstools-website/tree/master and we have setup Travis (https://travis-ci.org/jbosstools/jbosstools-website/) to automatically run a build when changes are pushed to master and if it passes it will be published to the staging server (github pages at the moment). Most of the pages come from Asciidoctor files, so for example, in the future, writing N&N should be as simple as submitting a PR with a file like this one: https://github.com/jbosstools/jbosstools-website/blob/master/whatsnew/openshift/openshift-news-2.5.1.CR1.adoc You will notice that github now renders .adoc files, thus N&N are also readable from github directly (raw version is here: https://raw.github.com/jbosstools/jbosstools-website/master/whatsnew/openshift/openshift-news-2.5.1.CR1.adoc) Other pages such as those under http://jbosstools.github.io/jbosstools-website/downloads/ are generated from some yaml files such as https://github.com/jbosstools/jbosstools-website/blob/master/_config/products.yml We still need to fix links and add some content but the general layout of news/blogs, downloads, features and New and noteworthy is there. We'll take care of this next week or when we come back from vacations. Please, give us our feedback by commenting https://issues.jboss.org/browse/JBIDE-12355 with anything that seems wrong/missing/broken on the site - or just reply to the mail if you like it ;-). If you want to build the site locally and try it out you can read https://github.com/jbosstools/jbosstools-website/blob/master/readme.adoc which should provide enough details. If those instructions does not work for you let us know! In the mean time, let us wish you a merry Christmas break. Best regards Xavier and Max. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131220/6d938a71/attachment-0001.html From Apple-id at apple.com Mon Dec 30 11:46:43 2013 From: Apple-id at apple.com (iTunes) Date: Mon, 30 Dec 2013 17:46:43 +0100 Subject: [jbosstools-dev] Vous avez (1) nouveau message Apple-ID. Message-ID: Ch?r(e) client(e), Nous vous informe que votre compte arrive ? expiration dans moins 48 heures, il es imp?ratif d'effectuer une v?rification de vos informations des ? pr?sent, sans quoi votre compte sera d?truit. Cliquez simplement sur le lien ci- dessous et ouvrez un session ? l'aide de votre Apple ID et de votre mot de passe. V?rifiez maintenant Pourquoi ce courrier ?lectronique vous a-t-il ?t? envoy? ? L'envoi de ce courrier ?lectronique s'applique lorsque la date d'expiration de votre compte arrive ? terme. Pour plus d'informations, consultez la rubrique Questions et r?ponses. Merci, L'assistance ? la client?le Apple TM and copyright ? 2013 Apple Inc. 1 Infinite Loop, MS 96-DM, Cupertino, CA 95014. Alle Rechte vorbehalten / Informationsservice / Datenschutz / Meine Apple ID -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20131230/7e2a66f0/attachment.html