From mistria at redhat.com Tue Jul 1 02:52:21 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 01 Jul 2014 08:52:21 +0200 Subject: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym In-Reply-To: References: Message-ID: <53B25AA5.5040202@redhat.com> On 06/30/2014 07:24 PM, Gorkem Ercan wrote: > Here is my proposal for the move. > 1. Do the rename and move this week. The move is only for the cordova > parts and CordovaSim is not affected by this directly. Once it is > completed, all the new development will commence from Eclipse repo. > 2. Setup builds on Eclipse build infrastructure. Hopefully I can > recruit Mickael and/or Nick to help with those. > 3. Make an initial release on Eclipse and modify JBoss TP to include > the release. > 4. Remove the existing cordova plugins and features from aerogear > update site. > 5. Modify CordovaSim to use the renamed plugins/packages/bundles. That seems like a good plan. If you want to make the transition easier, you could also create a target definition dedicated to Thym, which would have only dependencies on the necessary org.eclipse and Orbit parts. Do you already have the Bugzilla component created? Did you already request a Hudson instance? -- 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/20140701/ddb225c9/attachment.html From mistria at redhat.com Tue Jul 1 03:09:10 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 01 Jul 2014 09:09:10 +0200 Subject: [jbosstools-dev] Compilation failure in Seam In-Reply-To: <53B1EAB0.9020408@exadel.com> References: <53B1EAB0.9020408@exadel.com> Message-ID: <53B25E96.4080805@redhat.com> On 07/01/2014 12:54 AM, Daniel Azarov wrote: > Hi, > > We got compilation failure in Seam Tools again. > (Seehttps://issues.jboss.org/browse/JBIDE-17729) > > The cause is that org.jboss.tools.hibernate.spi.IConfiguration was changed. > > It is not good to change public API without full build tested. > > At least Seam Tools depends on hibernate. > Please when you change public API in Hibernate be sure Seam compiles too. Also, I suggest all bundles that depends on this IConfiguration change and that requires backward-incompatible changes to update the version range of their dependency on the hibernate bundle but setting current version as minVersion. -- 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/20140701/d4f0b206/attachment-0001.html From mistria at redhat.com Tue Jul 1 04:36:37 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 01 Jul 2014 10:36:37 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta4 Message-ID: <53B27315.8010602@redhat.com> Hi all, We plan to release the target-platform 4.40.0.Beta4 later today. So if you have any pending issue regarding target-platforms that you want to be fixed for next JBoss Tools/JBoss Developer Studio release, please raise your hand ASAP and this request will be made top-priority. 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/20140701/b3e6749d/attachment.html From mmurray at redhat.com Tue Jul 1 06:39:50 2014 From: mmurray at redhat.com (Michelle Murray) Date: Tue, 1 Jul 2014 06:39:50 -0400 (EDT) Subject: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym In-Reply-To: <53B25AA5.5040202@redhat.com> References: <53B25AA5.5040202@redhat.com> Message-ID: <1588934466.1456790.1404211190408.JavaMail.zimbra@redhat.com> Hello, OK, I've missed something and I'm very confused about what is happening here. Please can someone catch me up. So the Hybrid Mobile Tools plug-in [1] we currently have in JBDS/JBT is going to be removed and become a distinct Eclipse project? Is this what Gorkem means by AeroGear Cordova tools? And JBDS/JBT will only keep CordovaSim? Thanks, Michelle [1] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Developer_Studio/7.1/html-single/User_Guide/index.html#chap-Hybrid_Mobile_Tools_and_CordovaSim_Technology_Preview ----- Original Message ----- > From: "Mickael Istria" > To: jbosstools-dev at lists.jboss.org > Sent: Tuesday, 1 July, 2014 4:52:21 PM > Subject: Re: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym > On 06/30/2014 07:24 PM, Gorkem Ercan wrote: > > Here is my proposal for the move. > > > 1. Do the rename and move this week. The move is only for the cordova parts > > and CordovaSim is not affected by this directly. Once it is completed, all > > the new development will commence from Eclipse repo. > > > 2. Setup builds on Eclipse build infrastructure. Hopefully I can recruit > > Mickael and/or Nick to help with those. > > > 3. Make an initial release on Eclipse and modify JBoss TP to include the > > release. > > > 4. Remove the existing cordova plugins and features from aerogear update > > site. > > > 5. Modify CordovaSim to use the renamed plugins/packages/bundles. > > That seems like a good plan. > If you want to make the transition easier, you could also create a target > definition dedicated to Thym, which would have only dependencies on the > necessary org.eclipse and Orbit parts. > Do you already have the Bugzilla component created? Did you already request a > Hudson instance? > -- > 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/20140701/fe49fbfc/attachment.html From fbricon at redhat.com Tue Jul 1 08:41:35 2014 From: fbricon at redhat.com (Fred Bricon) Date: Tue, 01 Jul 2014 14:41:35 +0200 Subject: [jbosstools-dev] Please triage issues for JBT 4.2.0.Beta3/JBDS 8.0.0 Beta3 Code Freeze Message-ID: <53B2AC7F.1060703@redhat.com> Hi, in case you didn't know, code freeze for Beta3 is tomorrow EOB. We still have 184(!!!) open issues : https://issues.jboss.org/issues/?filter=12321673&jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(4.2.0.Beta3%2C%208.0.0.Beta3)%20%20AND%20component%20!%3D%20website%20ORDER%20BY%20assignee%20ASC Please triage the issues assigned to you and/or to the components you lead. Fred From manderse at redhat.com Tue Jul 1 08:50:47 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 01 Jul 2014 14:50:47 +0200 Subject: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym In-Reply-To: <1588934466.1456790.1404211190408.JavaMail.zimbra@redhat.com> References: <53B25AA5.5040202@redhat.com> <1588934466.1456790.1404211190408.JavaMail.zimbra@redhat.com> Message-ID: On 1 Jul 2014, at 12:39, Michelle Murray wrote: > Hello, > > OK, I've missed something and I'm very confused about what is > happening here. Please can someone catch me up. > > So the Hybrid Mobile Tools plug-in [1] we currently have in JBDS/JBT > is going to be removed and become a distinct Eclipse project? Is this > what Gorkem means by AeroGear Cordova tools? And JBDS/JBT will only > keep CordovaSim? at a source code level that is correct yes. We will still bundle/depend-on eclipse Thym (Tools for Hybrid Mobile) in our usage/installs. We probably will add some plugins to cover aeorogear specific functionality but nothing concrete on that yet. /max > > Thanks, > Michelle > > [1] > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Developer_Studio/7.1/html-single/User_Guide/index.html#chap-Hybrid_Mobile_Tools_and_CordovaSim_Technology_Preview > > ----- Original Message ----- > >> From: "Mickael Istria" >> To: jbosstools-dev at lists.jboss.org >> Sent: Tuesday, 1 July, 2014 4:52:21 PM >> Subject: Re: [jbosstools-dev] Moving Aerogear Cordova tools to >> Eclipse thym > >> On 06/30/2014 07:24 PM, Gorkem Ercan wrote: > >>> Here is my proposal for the move. >> >>> 1. Do the rename and move this week. The move is only for the >>> cordova parts >>> and CordovaSim is not affected by this directly. Once it is >>> completed, all >>> the new development will commence from Eclipse repo. >> >>> 2. Setup builds on Eclipse build infrastructure. Hopefully I can >>> recruit >>> Mickael and/or Nick to help with those. >> >>> 3. Make an initial release on Eclipse and modify JBoss TP to include >>> the >>> release. >> >>> 4. Remove the existing cordova plugins and features from aerogear >>> update >>> site. >> >>> 5. Modify CordovaSim to use the renamed plugins/packages/bundles. >> > >> That seems like a good plan. >> If you want to make the transition easier, you could also create a >> target >> definition dedicated to Thym, which would have only dependencies on >> the >> necessary org.eclipse and Orbit parts. >> Do you already have the Bugzilla component created? Did you already >> request a >> Hudson instance? > >> -- >> 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 /max http://about.me/maxandersen From manderse at redhat.com Tue Jul 1 08:53:29 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 01 Jul 2014 14:53:29 +0200 Subject: [jbosstools-dev] An excursion into integration testing plugins with Arquillian In-Reply-To: <53ADF566.7030300@phantomjinx.co.uk> References: <53A85C9C.3030801@phantomjinx.co.uk> <42E83CBB-5270-411A-B778-C41C56C46A6C@redhat.com> <53AD7E90.3020409@phantomjinx.co.uk> <7AD35903-55CB-46F6-9F48-9CC8D4A724AF@redhat.com> <53ADF566.7030300@phantomjinx.co.uk> Message-ID: <5E889845-98AE-4871-98C8-B0ED190CE3BA@redhat.com> On 28 Jun 2014, at 0:51, Paul G. Richardson wrote: > On 06/27/2014 04:08 PM, Max Rydahl Andersen wrote: >> >>>>> Might be of interest ... >>>>> >>>>> https://community.jboss.org/en/teiiddesigner/dev/blog/2014/06/23/unit-testing-an-eclipse-plugin-with-arquillian >>>>> >>>>> >>>> >>>> thats cool - even though I was hoping it was actually using >>>> arquillian to test eclipse (i.e. as an >>>> alternative to eclipse test runner). >>>> >>>> May I ask why the code we have in our server adapter testing base >>>> code was not sufficient for >>>> starting jboss servers and test against it ? >>>> >>>> /max >>>> http://about.me/maxandersen >>> >>> Cos... I didn't know it was there ;-) >> >> there is this mailing list called jbosstools-dev where you can ask >> how >> we test our existing jboss server tooling :) >> >>> I may have misunderstood mistria as well that the current JBT >>> testing >>> started servers with WTP? >> >> They are. We could probably remove that but for now not had that need >> since the plugins talking to the server >> have already had the dependency on the server adapter/wtp anyway. >> >>> I >>> didn't really want to introduce that element as well into the >>> integration-testing. I wanted to >>> confine it to: >>> - Start JBoss Server with Teiid installed >>> - Connect to Teiid using Teiid API from our Teiid client plugin >>> - Deploy Teiid's own testing VDBs using our Teiid client plugin >>> ... ... >> >> So that is reason enough for it. If you don't need/want to test your >> server adapter as part of this >> then yeah you don't have a need for it and its really cool to get >> arquillian to do it. >> >> What worries me and what I couldn't immediately grok was why >> ant/eclipserunner had to be involved in this ? >> >> This is because you need to actually invoke arquillian before the >> eclipse run ? >> >> if it is then yeah - this is why I tease arquillian team to get an >> eclipse friendly version of it >> so all these hoops doesn't need to be jumped through. >> >> I tried following a few of your links but they 404's (like >> https://github.com/Teiid-Designer/komodo/blob/master/tests/org.komodo.eclipse.teiid-8.7.client.test/src/arquillian.xml) >> >> would love to show Aslak the complexity required for this (which >> seems >> unnecessary) >> >> /max >> http://about.me/maxandersen > > > Ask for help when I can struggle on my own - are you mad!! ;-) > > One of those "I'll just try this quickly situations that turn into a > crusade' is the best explanation. > > Anyway... > > Answering points above in sequence: > > Ant is responsible for downloading the maven dependencies and copying > them to a libs folder as library dependencies for the test plugin. ..okey - any reasons why not just using the mvn copy goal for that which we use in other cases ? > Executing tests within Eclipse AND through maven is part-and-parcel of > our development process. Run the tests in Eclipse once (or during) > development and then run them through maven prior to push to github > and letting jenkins build. Sure - just read the blog as if you were running eclipse in yet another different way via ant ? > Otherwise, yes you are correct. Arquillian must be invoked prior to > running the unit test so that the JBoss container is there waiting. > Links fixed but the komodo repository is a live firing range at the > moment with lots of development going on so more than likely they > might break again in the future. I'll try and keep and eye-out. > > Maybe I have got so used to using Eclipse auto-builders (using ant) to > bring in extra libraries from some other source that I don't really > see it as complex. Then again seeing wood for the trees is not > necessarily my forte. My main concern is that this is bringing in dependencies outside or our target platform thus less easy to contain/check for overlaps. Also - using mvn copy goal seems to me to be the better way rather than using ant auto builders? /max http://about.me/maxandersen From fbricon at redhat.com Tue Jul 1 09:00:06 2014 From: fbricon at redhat.com (Fred Bricon) Date: Tue, 01 Jul 2014 15:00:06 +0200 Subject: [jbosstools-dev] Please triage issues for JBT 4.2.0.Beta3/JBDS 8.0.0 Beta3 Code Freeze In-Reply-To: <53B2AC7F.1060703@redhat.com> References: <53B2AC7F.1060703@redhat.com> Message-ID: <53B2B0D6.8040801@redhat.com> Sorry, the previous link used a filter parameter that made it private. Try : https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(4.2.0.Beta3%2C%208.0.0.Beta3)%20AND%20summary%20!~%20%22New%20and%20Noteworthy%22%20AND%20component%20!%3D%20website%20ORDER%20BY%20assignee%20ASC&startIndex=100 (now 181 issues) Le 01/07/2014 14:41, Fred Bricon a ?crit : > Hi, > > in case you didn't know, code freeze for Beta3 is tomorrow EOB. We still > have 184(!!!) open issues : > https://issues.jboss.org/issues/?filter=12321673&jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(4.2.0.Beta3%2C%208.0.0.Beta3)%20%20AND%20component%20!%3D%20website%20ORDER%20BY%20assignee%20ASC > > Please triage the issues assigned to you and/or to the components you lead. > > Fred > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From p.g.richardson at phantomjinx.co.uk Tue Jul 1 09:58:56 2014 From: p.g.richardson at phantomjinx.co.uk (phantomjinx) Date: Tue, 01 Jul 2014 14:58:56 +0100 Subject: [jbosstools-dev] An excursion into integration testing plugins with Arquillian In-Reply-To: <5E889845-98AE-4871-98C8-B0ED190CE3BA@redhat.com> References: <53A85C9C.3030801@phantomjinx.co.uk> <42E83CBB-5270-411A-B778-C41C56C46A6C@redhat.com> <53AD7E90.3020409@phantomjinx.co.uk> <7AD35903-55CB-46F6-9F48-9CC8D4A724AF@redhat.com> <53ADF566.7030300@phantomjinx.co.uk> <5E889845-98AE-4871-98C8-B0ED190CE3BA@redhat.com> Message-ID: <53B2BEA0.4010702@phantomjinx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/01/2014 01:53 PM, Max Rydahl Andersen wrote: > On 28 Jun 2014, at 0:51, Paul G. Richardson wrote: > >> On 06/27/2014 04:08 PM, Max Rydahl Andersen wrote: >>> >>>>>> Might be of interest ... >>>>>> >>>>>> https://community.jboss.org/en/teiiddesigner/dev/blog/2014/06/23/unit-testing-an-eclipse-plugin-with-arquillian >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>>> thats cool - even though I was hoping it was actually using >>>>> arquillian to test eclipse (i.e. as an alternative to eclipse test runner). >>>>> >>>>> May I ask why the code we have in our server adapter testing base code was not >>>>> sufficient for starting jboss servers and test against it ? >>>>> >>>>> /max http://about.me/maxandersen >>>> >>>> Cos... I didn't know it was there ;-) >>> >>> there is this mailing list called jbosstools-dev where you can ask how we test our existing >>> jboss server tooling :) >>> >>>> I may have misunderstood mistria as well that the current JBT testing started servers >>>> with WTP? >>> >>> They are. We could probably remove that but for now not had that need since the plugins >>> talking to the server have already had the dependency on the server adapter/wtp anyway. >>> >>>> I didn't really want to introduce that element as well into the integration-testing. I >>>> wanted to confine it to: - Start JBoss Server with Teiid installed - Connect to Teiid >>>> using Teiid API from our Teiid client plugin - Deploy Teiid's own testing VDBs using our >>>> Teiid client plugin ... ... >>> >>> So that is reason enough for it. If you don't need/want to test your server adapter as part >>> of this then yeah you don't have a need for it and its really cool to get arquillian to do >>> it. >>> >>> What worries me and what I couldn't immediately grok was why ant/eclipserunner had to be >>> involved in this ? >>> >>> This is because you need to actually invoke arquillian before the eclipse run ? >>> >>> if it is then yeah - this is why I tease arquillian team to get an eclipse friendly version >>> of it so all these hoops doesn't need to be jumped through. >>> >>> I tried following a few of your links but they 404's (like >>> https://github.com/Teiid-Designer/komodo/blob/master/tests/org.komodo.eclipse.teiid-8.7.client.test/src/arquillian.xml) >>> >>> >>> >>> would love to show Aslak the complexity required for this (which seems >>> unnecessary) >>> >>> /max http://about.me/maxandersen >> >> >> Ask for help when I can struggle on my own - are you mad!! ;-) >> >> One of those "I'll just try this quickly situations that turn into a crusade' is the best >> explanation. >> >> Anyway... >> >> Answering points above in sequence: >> >> Ant is responsible for downloading the maven dependencies and copying them to a libs folder >> as library dependencies for the test plugin. > > ..okey - any reasons why not just using the mvn copy goal for that which we use in other cases > ? > >> Executing tests within Eclipse AND through maven is part-and-parcel of our development >> process. Run the tests in Eclipse once (or during) development and then run them through >> maven prior to push to github and letting jenkins build. > > Sure - just read the blog as if you were running eclipse in yet another different way via ant > ? > >> Otherwise, yes you are correct. Arquillian must be invoked prior to running the unit test so >> that the JBoss container is there waiting. > >> Links fixed but the komodo repository is a live firing range at the moment with lots of >> development going on so more than likely they might break again in the future. I'll try and >> keep and eye-out. >> >> Maybe I have got so used to using Eclipse auto-builders (using ant) to bring in extra >> libraries from some other source that I don't really see it as complex. Then again seeing >> wood for the trees is not necessarily my forte. > > My main concern is that this is bringing in dependencies outside or our target platform thus > less easy to contain/check for overlaps. Also - using mvn copy goal seems to me to be the > better way rather than using ant auto builders? The ant auto builder [1] does hands-off maven by calling 'mvn process-sources'. This always executes the mvn copy-dependencies goal so bringing in the dependencies [2]. It has always been essential that any process happening while developing in Eclipse must also occur when building on the command line through maven. This is an example of that with the ant providing the plumbing between Eclipse and maven. The question of the dependencies not being in the target platform is worthy of further consideration as the mvn-downloaded libraries are sometimes duplicated in the TP (even if mvn-downloaded version is older than the one in the TP). At the moment, confining the mvn library to only that plugin by not exporting its packages has worked so far. Of course, using these libraries (as you know) is not without its classpath challenges but so far fragments have seemed to mitigate these issues. Of course, it would be lovely if maven-central could convert all libraries to plugins 'on-the-fly' then they could just be dropped into the TP. However, due to the very classpath issues I have encountered I know that is nigh on impossible. [1] https://github.com/Teiid-Designer/komodo/blob/master/integration-tests/org.komodo.eclipse.teiid-8.7.client.test/build.xml [2] https://github.com/Teiid-Designer/komodo/blob/master/integration-tests/org.komodo.eclipse.teiid-8.7.client.test/pom.xml PGR - -- Paul Richardson * p.g.richardson at phantomjinx.co.uk * p.g.richardson at redhat.com * pgrichardson at linux.com "I know exactly who reads the papers ... * The Daily Mirror is read by people who think they run the country. * The Guardian is read by people who think they ought to run the country. * The Times is read by people who do actually run the country. * The Daily Mail is read by the wives of the people who run the country. * The Financial Times is read by the people who own the country. * The Morning Star is read by the people who think the country ought to be run by another country. * The Daily Telegraph is read by the people who think it is." Jim Hacker, Yes Minister -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOyvpUACgkQcthLMIwdEb3cQACgtQXYLh+AHX+tzLRFGw0ODM/0 JssAoImeXA4naGMajb/7ZKEBYzdNNF9a =F/5A -----END PGP SIGNATURE----- From dgolovin at exadel.com Tue Jul 1 14:16:01 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Tue, 01 Jul 2014 11:16:01 -0700 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta4 In-Reply-To: <53B2F58A.5040705@redhat.com> References: <53B27315.8010602@redhat.com> <53B2F3C8.2080803@exadel.com> <53B2F58A.5040705@redhat.com> Message-ID: <53B2FAE1.8020605@exadel.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140701/d9009f56/attachment.html From mistria at redhat.com Tue Jul 1 14:23:56 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 01 Jul 2014 20:23:56 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta4 In-Reply-To: <53B2FAE1.8020605@exadel.com> References: <53B27315.8010602@redhat.com> <53B2F3C8.2080803@exadel.com> <53B2F58A.5040705@redhat.com> <53B2FAE1.8020605@exadel.com> Message-ID: <53B2FCBC.7030102@redhat.com> On 07/01/2014 08:16 PM, Denis Golovin wrote: > We should delay TP release, not sure if code freeze should be affected. IMO, there is no point in freezing code if TP is not frozen. TP is upstream of JBT/JBDS, it's the first thing we should freeze. -- 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/20140701/29b85f1f/attachment.html From dgolovin at exadel.com Tue Jul 1 20:39:44 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Tue, 01 Jul 2014 17:39:44 -0700 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta4 In-Reply-To: <53B2FCBC.7030102@redhat.com> References: <53B27315.8010602@redhat.com> <53B2F3C8.2080803@exadel.com> <53B2F58A.5040705@redhat.com> <53B2FAE1.8020605@exadel.com> <53B2FCBC.7030102@redhat.com> Message-ID: <53B354D0.4000900@exadel.com> On 07/01/2014 11:23 AM, Mickael Istria wrote: > IMO, there is no point in freezing code if TP is not frozen. TP is > upstream of JBT/JBDS, it's the first thing we should freeze. It is not perfect to have changes after code freeze, but it is not a blocker for it. That's why we have respins. Denis From mistria at redhat.com Wed Jul 2 03:13:51 2014 From: mistria at redhat.com (Mickael Istria) Date: Wed, 02 Jul 2014 09:13:51 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta4 In-Reply-To: <53B354D0.4000900@exadel.com> References: <53B27315.8010602@redhat.com> <53B2F3C8.2080803@exadel.com> <53B2F58A.5040705@redhat.com> <53B2FAE1.8020605@exadel.com> <53B2FCBC.7030102@redhat.com> <53B354D0.4000900@exadel.com> Message-ID: <53B3B12F.8030005@redhat.com> On 07/02/2014 02:39 AM, Denis Golovin wrote: > On 07/01/2014 11:23 AM, Mickael Istria wrote: >> IMO, there is no point in freezing code if TP is not frozen. TP is >> upstream of JBT/JBDS, it's the first thing we should freeze. > It is not perfect to have changes after code freeze, but it is not a > blocker for it. That's why we have respins. Respins are a bad practice we got too much used to. Anyway... Regarding TP release, then if you're sure there will be changes, It won't be released before it's complete for Beta3 in order to avoid extra useless effort. So first spins of JBT will be built against TP 4.40.0.Beta3-SNAPSHOT. We can just *hope* the TP changes that will happen after Code Freeze won't break all components... -- 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/20140702/ba6f918b/attachment.html From fbricon at redhat.com Wed Jul 2 03:52:35 2014 From: fbricon at redhat.com (Fred Bricon) Date: Wed, 02 Jul 2014 09:52:35 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta4 In-Reply-To: <53B3B12F.8030005@redhat.com> References: <53B27315.8010602@redhat.com> <53B2F3C8.2080803@exadel.com> <53B2F58A.5040705@redhat.com> <53B2FAE1.8020605@exadel.com> <53B2FCBC.7030102@redhat.com> <53B354D0.4000900@exadel.com> <53B3B12F.8030005@redhat.com> Message-ID: <53B3BA43.2000000@redhat.com> I have a TP update requests for m2e-wro4j : https://issues.jboss.org/browse/JBIDE-17742 Fred Le mercredi 2 juillet 2014 09:13:51, Mickael Istria a ?crit : > On 07/02/2014 02:39 AM, Denis Golovin wrote: >> On 07/01/2014 11:23 AM, Mickael Istria wrote: >>> IMO, there is no point in freezing code if TP is not frozen. TP is >>> upstream of JBT/JBDS, it's the first thing we should freeze. >> It is not perfect to have changes after code freeze, but it is not a >> blocker for it. That's why we have respins. > Respins are a bad practice we got too much used to. Anyway... > Regarding TP release, then if you're sure there will be changes, It > won't be released before it's complete for Beta3 in order to avoid > extra useless effort. So first spins of JBT will be built against TP > 4.40.0.Beta3-SNAPSHOT. > We can just *hope* the TP changes that will happen after Code Freeze > won't break all components... > > -- > 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 angelo.zerr at gmail.com Wed Jul 2 09:06:17 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Wed, 2 Jul 2014 15:06:17 +0200 Subject: [jbosstools-dev] Cordojva & Tern In-Reply-To: References: <3A261B5E-A373-46E8-A701-41209115791B@redhat.com> Message-ID: Hi Victor, When you will have time, could you answer me. I think it should be good 1) to have a separate github for cordovajs (ex : tern-cordovajs project name). 2) It should be cool to have several version of cordovajs (generated from documentation). Many thank's for your answer. Regard's Angelo 2014-06-16 9:18 GMT+02:00 Angelo zerr : > > > > 2014-06-15 9:51 GMT+02:00 Max Rydahl Andersen : > > sorry for late response but been on on 2 weeks vacation did bad things to >> my inbox ;) > > > No problem max, I know this problem:) > >> >> I was wondering - is there a way (at code level) to distinguish between >> json type definitions that are automatically enabled by some plugin >> because it has detected the use of i.e. cordova.js vs something the >> user explicitly enabled ? >> >> Would be nice to allow users to explicit say I want *this* even though >> a plugin haven't been able to detect the library matching it. If there >> is just one kind of On/Off then the plugin can't know if turning it off >> is against the users will or just because he stopped using the related >> javascript library. >> >> wdyt ? > > > I'm sorry but I don't understand very well what you mean. Tern plugin > doesn't use the native javascript library, > so he can work without the javascript library. JSON Type definition is a > JSON which describes the structure of your library > (document has getElementById method, etc). Some JS framework like jQuery > can be described just with this JSON. > > tern plugin uses JSON Type Definition and add some feature like managing a > new scope per file (usefull for node.js plugin),managing effect (create an > instance of FileSystem when require('fs') is called). > >> >> >>> 1) if you wish to change some information about description of cordova >>> metadata, etc don't hesitate to create PR. >>> >> >> I think it looks fine. > > > Cool. > >> >> >> 2) I think it should be better to create a github for the cordova tern >>> plugin >>> >> >> You mean a separate git repo ? > > > Exactly! > > >> Yes, makes sense to me too. Actually thought >> that was you and Victor wrote earlier would happen. >> >> Victor - anything besides finding time to do it preventing us from >> putting this in a separate github repo ? >> >> btw. I assume you during the build of tern will then fetch the content of >> the github repo > > > I do that at hand because : > > 1) I have just discovered that we can have submodule with Git. > 2) I have forked angular.js, so I don't know very well how I can manage > that with fetch. > > >> and bundle it >> or does it require network access at runtime to get it ? > > > No it doesn't work like this (perhaps in the future of tern.java, using > npm could be interested to update the tern plugin). > > >> >> >> 3) do you know if cordova provides some api to generate doc? YUI, >>> DojoToolkit do that, so after it's easy to create version of the tern >>> cordova tern plugin like I have done for dojo >>> https://github.com/angelozerr/tern.dojotoolkit (I generate several >>> version >>> of dojotoolkit by using sources of dojo, if you are interested, I could >>> help you to do that). >>> >> >> I do not know about this. Maybe Gorkem does ? >> > > It should be really cool to do that in order to provide several version of > cordova.js. I have an idea too, to provide a wizard kind to generate tern > plugin version from sources. > > Regards Angelo > >> >> /max >> http://about.me/maxandersen >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140702/89dcad82/attachment-0001.html From gorkem.ercan at gmail.com Wed Jul 2 10:21:14 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Wed, 2 Jul 2014 10:21:14 -0400 Subject: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym In-Reply-To: <53B25AA5.5040202@redhat.com> References: <53B25AA5.5040202@redhat.com> Message-ID: On Tue, Jul 1, 2014 at 2:52 AM, Mickael Istria wrote: > On 06/30/2014 07:24 PM, Gorkem Ercan wrote: > > Here is my proposal for the move. > 1. Do the rename and move this week. The move is only for the cordova > parts and CordovaSim is not affected by this directly. Once it is > completed, all the new development will commence from Eclipse repo. > 2. Setup builds on Eclipse build infrastructure. Hopefully I can recruit > Mickael and/or Nick to help with those. > 3. Make an initial release on Eclipse and modify JBoss TP to include the > release. > 4. Remove the existing cordova plugins and features from aerogear update > site. > 5. Modify CordovaSim to use the renamed plugins/packages/bundles. > > > That seems like a good plan. > If you want to make the transition easier, you could also create a target > definition dedicated to Thym, which would have only dependencies on the > necessary org.eclipse and Orbit parts. > Do you already have the Bugzilla component created? Did you already > request a Hudson instance? > TP would be fantastic. Bugzilla is already setup at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Thym I have not done the hudson request yet, do we need only one? Can you do the honors? > > > -- > 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/20140702/8c4044b5/attachment.html From mistria at redhat.com Wed Jul 2 10:35:32 2014 From: mistria at redhat.com (Mickael Istria) Date: Wed, 02 Jul 2014 16:35:32 +0200 Subject: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym In-Reply-To: References: <53B25AA5.5040202@redhat.com> Message-ID: <53B418B4.4060308@redhat.com> On 07/02/2014 04:21 PM, Gorkem Ercan wrote: > TP would be fantastic. Since it requires knowledge of the actual dependencies of Thym, it's something you'll need to do (I can't help much). Take the jbosstools-multiple.target as example, remove everything that is JBoss, replace download.jboss.org URLs by the download.eclipse.org onesm and trim out all IUs and sites you won't need. > Bugzilla is already setup at > https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Thym Ok, I opened a ticket: https://bugs.eclipse.org/bugs/show_bug.cgi?id=438737 I see no-one seems to be following the ||thym-inbox at eclipse.org bugzilla user. Don't forget to add it to your watch list if you want notifications. > I have not done the hudson request yet, do we need only one? Can you > do the honors? https://bugs.eclipse.org/bugs/show_bug.cgi?id=438739 Let's continue the discussion on the thym-dev at eclipse.org mailing-list ;) -- 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/20140702/58f0ab7b/attachment.html From nboldt at redhat.com Wed Jul 2 10:41:59 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 02 Jul 2014 10:41:59 -0400 Subject: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym In-Reply-To: <53B418B4.4060308@redhat.com> References: <53B25AA5.5040202@redhat.com> <53B418B4.4060308@redhat.com> Message-ID: <53B41A37.2050009@redhat.com> Or, grep your manifest.mf and feature.xml files for all the required upstream bundles/features, and give that list to me/Mickael and we can cobble you a TP from that ingredient list. :D On 07/02/2014 10:35 AM, Mickael Istria wrote: > On 07/02/2014 04:21 PM, Gorkem Ercan wrote: >> TP would be fantastic. > Since it requires knowledge of the actual dependencies of Thym, it's > something you'll need to do (I can't help much). > Take the jbosstools-multiple.target as example, remove everything that > is JBoss, replace download.jboss.org URLs by the download.eclipse.org > onesm and trim out all IUs and sites you won't need. > >> Bugzilla is already setup at >> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Thym > Ok, I opened a ticket: https://bugs.eclipse.org/bugs/show_bug.cgi?id=438737 > I see no-one seems to be following the ||thym-inbox at eclipse.org bugzilla > user. Don't forget to add it to your watch list if you want notifications. > >> I have not done the hudson request yet, do we need only one? Can you >> do the honors? > https://bugs.eclipse.org/bugs/show_bug.cgi?id=438739 > > Let's continue the discussion on the thym-dev at eclipse.org mailing-list ;) > -- > 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 gorkem.ercan at gmail.com Wed Jul 2 12:12:30 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Wed, 2 Jul 2014 12:12:30 -0400 Subject: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym In-Reply-To: <53B41A37.2050009@redhat.com> References: <53B25AA5.5040202@redhat.com> <53B418B4.4060308@redhat.com> <53B41A37.2050009@redhat.com> Message-ID: Here is the list of dependencies.. I have tried to remove the duplicates. We do not really have much restrictions on specific versions of the dependencies, latest/luna versions should be fine -- Gorkem On Wed, Jul 2, 2014 at 10:41 AM, Nick Boldt wrote: > Or, grep your manifest.mf and feature.xml files for all the required > upstream bundles/features, and give that list to me/Mickael and we can > cobble you a TP from that ingredient list. > > :D > > > On 07/02/2014 10:35 AM, Mickael Istria wrote: > >> On 07/02/2014 04:21 PM, Gorkem Ercan wrote: >> >>> TP would be fantastic. >>> >> Since it requires knowledge of the actual dependencies of Thym, it's >> something you'll need to do (I can't help much). >> Take the jbosstools-multiple.target as example, remove everything that >> is JBoss, replace download.jboss.org URLs by the download.eclipse.org >> onesm and trim out all IUs and sites you won't need. >> >> Bugzilla is already setup at >>> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Thym >>> >> Ok, I opened a ticket: https://bugs.eclipse.org/bugs/ >> show_bug.cgi?id=438737 >> I see no-one seems to be following the ||thym-inbox at eclipse.org bugzilla >> user. Don't forget to add it to your watch list if you want notifications. >> >> I have not done the hudson request yet, do we need only one? Can you >>> do the honors? >>> >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=438739 >> >> Let's continue the discussion on the thym-dev at eclipse.org mailing-list ;) >> -- >> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140702/260d9013/attachment.html -------------- next part -------------- org.eclipse.core.runtime, org.eclipse.core.resources;bundle-version="[3.8.1,4.0.0)", org.eclipse.debug.core;bundle-version="[3.7.0,4.0.0)", org.apache.commons.io;bundle-version="[2.0.0,2.1.0)", org.eclipse.osgi.util org.eclipse.ant.launching, org.eclipse.core.externaltools org.eclipse.ui, org.eclipse.debug.ui;bundle-version="[3.8.0,4.0.0)", org.eclipse.ui.workbench, org.eclipse.ui.ide org.eclipse.debug.core;bundle-version="[3.7.0,4.0.0)", org.eclipse.wst.xml.core;bundle-version="[1.1.0,1.2.0)", org.eclipse.wst.sse.core;bundle-version="[1.1.0,1.2.0)", org.eclipse.core.expressions;bundle-version="[3.4.0,3.5.0)";visibility:=reexport, com.google.gson;bundle-version="[2.1.0,3.0.0)", org.apache.commons.io;bundle-version="[2.0.0,2.1.0)", org.eclipse.jgit;bundle-version="[3.0.0,4.0.0)", org.eclipse.ecf;bundle-version="[3.2.0,4.0.0)", org.eclipse.ecf.filetransfer;bundle-version="[5.0.0,6.0.0)", org.eclipse.ecf.provider.filetransfer.httpclient4;bundle-version="[1.0.0,2.0.0)", org.eclipse.wst.jsdt.core;bundle-version="[1.1.0,2.0.0)", org.apache.httpcomponents.httpclient;bundle-version="[4.2.5,4.3.0)", org.apache.httpcomponents.httpcore;bundle-version="[4.2.5,4.3.0)", org.jboss.tools.jst.jsdt;resolution:=optional, org.eclipse.core.net;bundle-version="[1.2.0,2.0.0)" org.eclipse.ecf.core.identity;version="3.2.0" org.apache.commons.codec, org.apache.commons.io org.eclipse.jface, org.junit, org.eclipse.jface.text;bundle-version="[3.8.0,4.0.0)", org.eclipse.ui.forms;bundle-version="3.5.200", org.eclipse.core.databinding, org.eclipse.core.databinding.beans, org.eclipse.core.databinding.observable, org.eclipse.core.databinding.property, org.eclipse.jface.databinding, com.ibm.icu, org.eclipse.debug.ui;bundle-version="[3.8.0,4.0.0)";visibility:=reexport, org.eclipse.equinox.p2.ui.discovery;bundle-version="[1.0.0,2.0.0)", org.eclipse.ui.navigator;bundle-version="[3.5.0,3.6.0)", org.eclipse.ui.forms, org.eclipse.wst.sse.ui From mistria at redhat.com Wed Jul 2 12:43:01 2014 From: mistria at redhat.com (Mickael Istria) Date: Wed, 02 Jul 2014 18:43:01 +0200 Subject: [jbosstools-dev] Moving Aerogear Cordova tools to Eclipse thym In-Reply-To: References: <53B25AA5.5040202@redhat.com> <53B418B4.4060308@redhat.com> <53B41A37.2050009@redhat.com> Message-ID: <53B43695.1060209@redhat.com> On 07/02/2014 06:12 PM, Gorkem Ercan wrote: > Here is the list of dependencies.. I have tried to remove the > duplicates. We do not really have much restrictions on specific > versions of the dependencies, latest/luna versions should be fine Ok thanks. Can you please attach this to https://bugs.eclipse.org/bugs/show_bug.cgi?id=438737 and put your comment there? -- 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/20140702/303c2ddf/attachment-0001.html From nboldt at redhat.com Wed Jul 2 13:32:08 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 02 Jul 2014 13:32:08 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta3 / JBDS 8.0.0.Beta3 Message-ID: <53B44218.10807@redhat.com> The code freeze is on now, Wed, Jul 02, 2014, so please ensure you are branched in the next 48hrs. ** IF YOU ARE UNABLE TO CODE FREEZE &/or BRANCH ** Please reply to this thread explaining WHY and estimating WHEN you think you might be ready, so that other projects are aware (and so we know how many projects are affected.) Please also comment in your task JIRA(s) so the information is captured there too. -- Task JIRA created for this milestone include: JBDS : https://issues.jboss.org/browse/JBDS-3081 LiveReload : https://issues.jboss.org/browse/JBIDE-17751 Webservices : https://issues.jboss.org/browse/JBIDE-17752 JBoss Tools : https://issues.jboss.org/browse/JBIDE-17753 Aerogear : https://issues.jboss.org/browse/JBIDE-17754 JST : https://issues.jboss.org/browse/JBIDE-17755 VPE : https://issues.jboss.org/browse/JBIDE-17756 JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17757 Server : https://issues.jboss.org/browse/JBIDE-17758 Hibernate : https://issues.jboss.org/browse/JBIDE-17759 Base : https://issues.jboss.org/browse/JBIDE-17760 OpenShift : https://issues.jboss.org/browse/JBIDE-17761 Birt : https://issues.jboss.org/browse/JBIDE-17762 Forge : https://issues.jboss.org/browse/JBIDE-17763 BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 JavaEE : https://issues.jboss.org/browse/JBIDE-17765 Arquillian : https://issues.jboss.org/browse/JBIDE-17766 Central : https://issues.jboss.org/browse/JBIDE-17767 Portlet : https://issues.jboss.org/browse/JBIDE-17768 Freemarker : https://issues.jboss.org/browse/JBIDE-17769 Central Discovery : https://issues.jboss.org/browse/JBIDE-17770 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Jul 2 13:37:30 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 02 Jul 2014 13:37:30 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta3 / JBDS 8.0.0.Beta3 In-Reply-To: <53B44218.10807@redhat.com> References: <53B44218.10807@redhat.com> Message-ID: <53B4435A.3000401@redhat.com> BTW, the JIRAs all say to check target platform 4.40.0.Beta3-SNAPSHOT or 4.40.0.Beta3, which is wrong. Please test with the latest target platform, *4.40.0.Beta4-SNAPSHOT*. Note too that target platform 4.40.0.Beta4 (the released version, not the snapshot) will NOT be available until we settle all the incoming changes (Tern, m2e-*, egit). This will hopefully happen next week - stay tuned for news. Nick On 07/02/2014 01:32 PM, Nick Boldt wrote: > The code freeze is on now, Wed, Jul 02, 2014, so please ensure you are > branched in the next 48hrs. > > ** IF YOU ARE UNABLE TO CODE FREEZE &/or BRANCH ** > > Please reply to this thread explaining WHY and estimating WHEN you think > you might be ready, so that other projects are aware (and so we know how > many projects are affected.) > > Please also comment in your task JIRA(s) so the information is captured > there too. > > -- > > Task JIRA created for this milestone include: > > JBDS : https://issues.jboss.org/browse/JBDS-3081 > LiveReload : https://issues.jboss.org/browse/JBIDE-17751 > Webservices : https://issues.jboss.org/browse/JBIDE-17752 > JBoss Tools : https://issues.jboss.org/browse/JBIDE-17753 > Aerogear : https://issues.jboss.org/browse/JBIDE-17754 > JST : https://issues.jboss.org/browse/JBIDE-17755 > VPE : https://issues.jboss.org/browse/JBIDE-17756 > JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17757 > Server : https://issues.jboss.org/browse/JBIDE-17758 > Hibernate : https://issues.jboss.org/browse/JBIDE-17759 > Base : https://issues.jboss.org/browse/JBIDE-17760 > OpenShift : https://issues.jboss.org/browse/JBIDE-17761 > Birt : https://issues.jboss.org/browse/JBIDE-17762 > Forge : https://issues.jboss.org/browse/JBIDE-17763 > BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 > JavaEE : https://issues.jboss.org/browse/JBIDE-17765 > Arquillian : https://issues.jboss.org/browse/JBIDE-17766 > Central : https://issues.jboss.org/browse/JBIDE-17767 > Portlet : https://issues.jboss.org/browse/JBIDE-17768 > Freemarker : https://issues.jboss.org/browse/JBIDE-17769 > Central Discovery : https://issues.jboss.org/browse/JBIDE-17770 > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From rstryker at redhat.com Wed Jul 2 15:25:48 2014 From: rstryker at redhat.com (Rob Stryker) Date: Thu, 03 Jul 2014 03:25:48 +0800 Subject: [jbosstools-dev] Possibly critical issue with forge or m2e Message-ID: <53B45CBC.9030905@redhat.com> Hey all: A user found a strange bug while using astools and publishing a zipped project. The bug is basically that truezip ( a library we use) can't initialize because it can't find a class. It can't find the class because the thread's classloader is from plexus classrealms, and not the standard eclipse classloader that we'd expect. So basically, either forge or m2e is changing a worker's classloader, and not putting it back. This (if true) could be a critical issue, since that thread / worker will probably never have the proper classloader again for the workspace session. I encourage anyone with access to m2e or forge to look into this and verify their respective codebases are behaving properly with regards to classloaders. Feel free to look at the jira and ask any for more details or any questions you might have that might help in tracking this down. https://issues.jboss.org/browse/JBIDE-17700 From xcoulon at redhat.com Wed Jul 2 17:08:19 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Wed, 2 Jul 2014 23:08:19 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta3 / JBDS 8.0.0.Beta3 In-Reply-To: <53B4435A.3000401@redhat.com> References: <53B44218.10807@redhat.com> <53B4435A.3000401@redhat.com> Message-ID: It's done for the WebServices and LiveReload components. Best regards, /Xavier On 02 Jul 2014, at 19:37, Nick Boldt wrote: > BTW, the JIRAs all say to check target platform 4.40.0.Beta3-SNAPSHOT or > 4.40.0.Beta3, which is wrong. > > Please test with the latest target platform, *4.40.0.Beta4-SNAPSHOT*. > > Note too that target platform 4.40.0.Beta4 (the released version, not > the snapshot) will NOT be available until we settle all the incoming > changes (Tern, m2e-*, egit). This will hopefully happen next week - stay > tuned for news. > > Nick > > > On 07/02/2014 01:32 PM, Nick Boldt wrote: >> The code freeze is on now, Wed, Jul 02, 2014, so please ensure you are >> branched in the next 48hrs. >> >> ** IF YOU ARE UNABLE TO CODE FREEZE &/or BRANCH ** >> >> Please reply to this thread explaining WHY and estimating WHEN you think >> you might be ready, so that other projects are aware (and so we know how >> many projects are affected.) >> >> Please also comment in your task JIRA(s) so the information is captured >> there too. >> >> -- >> >> Task JIRA created for this milestone include: >> >> JBDS : https://issues.jboss.org/browse/JBDS-3081 >> LiveReload : https://issues.jboss.org/browse/JBIDE-17751 >> Webservices : https://issues.jboss.org/browse/JBIDE-17752 >> JBoss Tools : https://issues.jboss.org/browse/JBIDE-17753 >> Aerogear : https://issues.jboss.org/browse/JBIDE-17754 >> JST : https://issues.jboss.org/browse/JBIDE-17755 >> VPE : https://issues.jboss.org/browse/JBIDE-17756 >> JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17757 >> Server : https://issues.jboss.org/browse/JBIDE-17758 >> Hibernate : https://issues.jboss.org/browse/JBIDE-17759 >> Base : https://issues.jboss.org/browse/JBIDE-17760 >> OpenShift : https://issues.jboss.org/browse/JBIDE-17761 >> Birt : https://issues.jboss.org/browse/JBIDE-17762 >> Forge : https://issues.jboss.org/browse/JBIDE-17763 >> BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 >> JavaEE : https://issues.jboss.org/browse/JBIDE-17765 >> Arquillian : https://issues.jboss.org/browse/JBIDE-17766 >> Central : https://issues.jboss.org/browse/JBIDE-17767 >> Portlet : https://issues.jboss.org/browse/JBIDE-17768 >> Freemarker : https://issues.jboss.org/browse/JBIDE-17769 >> Central Discovery : https://issues.jboss.org/browse/JBIDE-17770 >> > > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140702/81f6fc79/attachment.html From nboldt at redhat.com Wed Jul 2 17:29:18 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 02 Jul 2014 17:29:18 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove egit/jgit, update m2e-wro4j Message-ID: <53B479AE.5030109@redhat.com> Here is a proposal for 4 changes to the JBoss Tools 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and Early Access): https://github.com/jbosstools/jbosstools-discovery/pull/184 https://github.com/jbosstools/jbosstools-target-platforms/pull/78 https://github.com/jbosstools/jbosstools-discovery/pull/183 https://github.com/jbosstools/jbosstools-discovery/pull/182 It consists of the following changes: * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP * JBIDE-17742 - Remove EGit from Central Discovery -- The above PRs have not been applied (to allow time to complain / reject / pull an even *newer* version of Tern), so you can fetch the PRs and build the TP locally to test it out: Build target-platform: $ cd jbosstools-target-platforms $ git fetch origin 4.40.x $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT -Pmultiple.target -- If you want to perform a scripted install of the entire target platform into your local Eclipse or JBDS instance, you can now do so with this script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh Usage is documented in the above script, and in this README: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Jul 2 18:01:29 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 02 Jul 2014 18:01:29 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: POSSIBLE BETA3 BLOCKER with forge or m2e (JBIDE-17700) In-Reply-To: <53B45CBC.9030905@redhat.com> References: <53B45CBC.9030905@redhat.com> Message-ID: <53B48139.7040208@redhat.com> Escalating to SHOUTY CAPS in subject (so mail filters won't) and adding PM folks to cc: so this gets to the agenda, in case it is in fact a Beta3 blocker. As Koen is on PTO the next couple days, adding Lincoln instead. Apologies if someone else ought to be cc:'d instead. N On 07/02/2014 03:25 PM, Rob Stryker wrote: > Hey all: > > A user found a strange bug while using astools and publishing a zipped > project. The bug is basically that truezip ( a library we use) can't > initialize because it can't find a class. It can't find the class > because the thread's classloader is from plexus classrealms, and not the > standard eclipse classloader that we'd expect. > > So basically, either forge or m2e is changing a worker's classloader, > and not putting it back. This (if true) could be a critical issue, since > that thread / worker will probably never have the proper classloader > again for the workspace session. > > I encourage anyone with access to m2e or forge to look into this and > verify their respective codebases are behaving properly with regards to > classloaders. Feel free to look at the jira and ask any for more details > or any questions you might have that might help in tracking this down. > > https://issues.jboss.org/browse/JBIDE-17700 > _______________________________________________ > 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 nboldt at redhat.com Wed Jul 2 18:13:44 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 02 Jul 2014 18:13:44 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove {egit/jgit}, update {m2e-wro4j, tern, angularJS}, add {vpe.cordovasim, maven.jbosspackaging, common.mylyn} In-Reply-To: <53B479AE.5030109@redhat.com> References: <53B479AE.5030109@redhat.com> Message-ID: <53B48418.4050800@redhat.com> Missed one... there are now 5 JIRAs. -- Here is a proposal for *5* changes to the JBoss Tools 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and Early Access): https://github.com/jbosstools/jbosstools-discovery/pull/185 https://github.com/jbosstools/jbosstools-discovery/pull/184 https://github.com/jbosstools/jbosstools-target-platforms/pull/78 https://github.com/jbosstools/jbosstools-discovery/pull/183 https://github.com/jbosstools/jbosstools-discovery/pull/182 It consists of the following changes: * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, org.jboss.tools.maven.jbosspackaging.feature, and org.jboss.tools.common.mylyn.feature to JBoss Central TP * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP * JBIDE-17742 - Remove EGit from Central Discovery -- The above PRs have not been applied (to allow time to complain / reject / pull an even *newer* version of Tern), so you can fetch the PRs and build the TP locally to test it out: Build target-platform: $ cd jbosstools-target-platforms $ git fetch origin 4.40.x $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT -Pmultiple.target -- If you want to perform a scripted install of the entire target platform into your local Eclipse or JBDS instance, you can now do so with this script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh Usage is documented in the above script, and in this README: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files -- 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 dgolovin at exadel.com Wed Jul 2 18:15:00 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Wed, 02 Jul 2014 15:15:00 -0700 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove egit/jgit, update m2e-wro4j In-Reply-To: <53B479AE.5030109@redhat.com> References: <53B479AE.5030109@redhat.com> Message-ID: <53B48464.3020807@exadel.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140702/ee0c7baf/attachment.html From nboldt at redhat.com Wed Jul 2 18:33:28 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 02 Jul 2014 18:33:28 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove {egit/jgit}, update {m2e-wro4j, tern, angularJS}, add {vpe.cordovasim, maven.jbosspackaging, common.mylyn} In-Reply-To: <53B48418.4050800@redhat.com> References: <53B479AE.5030109@redhat.com> <53B48418.4050800@redhat.com> Message-ID: <53B488B8.10307@redhat.com> Make that 6, with Denis' additional change. -- Here is a proposal for *6* changes to the JBoss Tools 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and Early Access): https://github.com/jbosstools/jbosstools-target-platforms/pull/79 https://github.com/jbosstools/jbosstools-discovery/pull/185 https://github.com/jbosstools/jbosstools-discovery/pull/184 https://github.com/jbosstools/jbosstools-target-platforms/pull/78 https://github.com/jbosstools/jbosstools-discovery/pull/183 https://github.com/jbosstools/jbosstools-discovery/pull/182 It consists of the following changes: * JBDS-3082 add org.eclipse.core.runtime.compatibility.auth 3.2.300.v20120523-2004 to JBT/JBDS TP * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, org.jboss.tools.maven.jbosspackaging.feature, and org.jboss.tools.common.mylyn.feature to JBoss Central TP * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP * JBIDE-17742 - Remove EGit from Central Discovery -- The above PRs have not been applied (to allow time to complain / reject / pull an even *newer* version of Tern), so you can fetch the PRs and build the TP locally to test it out: Build target-platform: $ cd jbosstools-target-platforms $ git fetch origin 4.40.x $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT -Pmultiple.target -- If you want to perform a scripted install of the entire target platform into your local Eclipse or JBDS instance, you can now do so with this script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh Usage is documented in the above script, and in this README: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files On 07/02/2014 06:15 PM, Denis Golovin wrote: > Nick can we also add include to this one below? > > JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth bundle > version 3.2.300.v20120523-2004 > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From lincolnbaxter at gmail.com Wed Jul 2 18:56:41 2014 From: lincolnbaxter at gmail.com (Lincoln Baxter, III) Date: Wed, 2 Jul 2014 18:56:41 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: POSSIBLE BETA3 BLOCKER with forge or m2e (JBIDE-17700) In-Reply-To: <53B48139.7040208@redhat.com> References: <53B45CBC.9030905@redhat.com> <53B48139.7040208@redhat.com> Message-ID: The only place where Forge directly interacts with plexus is here: https://github.com/forge/core/blob/master/maven/impl-projects/src/main/java/org/jboss/forge/addon/maven/projects/PlexusContainer.java#L26 As you can see, we make sure to always restore the TCCL after invoking it (using https://github.com/forge/furnace/blob/master/container-api/src/main/java/org/jboss/forge/furnace/util/ClassLoaders.java#L21), because Plexus is... well... nasty and does nasty things. There was one place where we did not do this, but don't think it's the source of the error described above... however, just for paranoia's sake, I've added this TCCL protection in the shutdown method as well: https://github.com/forge/core/commit/37970feeb ~Lincoln On Wed, Jul 2, 2014 at 6:01 PM, Nick Boldt wrote: > Escalating to SHOUTY CAPS in subject (so mail filters won't) and adding PM > folks to cc: so this gets to the agenda, in case it is in fact a Beta3 > blocker. > > As Koen is on PTO the next couple days, adding Lincoln instead. Apologies > if someone else ought to be cc:'d instead. > > N > > On 07/02/2014 03:25 PM, Rob Stryker wrote: > >> Hey all: >> >> A user found a strange bug while using astools and publishing a zipped >> project. The bug is basically that truezip ( a library we use) can't >> initialize because it can't find a class. It can't find the class >> because the thread's classloader is from plexus classrealms, and not the >> standard eclipse classloader that we'd expect. >> >> So basically, either forge or m2e is changing a worker's classloader, >> and not putting it back. This (if true) could be a critical issue, since >> that thread / worker will probably never have the proper classloader >> again for the workspace session. >> >> I encourage anyone with access to m2e or forge to look into this and >> verify their respective codebases are behaving properly with regards to >> classloaders. Feel free to look at the jira and ask any for more details >> or any questions you might have that might help in tracking this down. >> >> https://issues.jboss.org/browse/JBIDE-17700 >> _______________________________________________ >> 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 > -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140702/ff522121/attachment.html From manderse at redhat.com Thu Jul 3 06:54:05 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 03 Jul 2014 12:54:05 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove {egit/jgit}, update {m2e-wro4j, tern, angularJS}, add {vpe.cordovasim, maven.jbosspackaging, common.mylyn} In-Reply-To: <53B488B8.10307@redhat.com> References: <53B479AE.5030109@redhat.com> <53B48418.4050800@redhat.com> <53B488B8.10307@redhat.com> Message-ID: <9BEAC311-787F-4CC1-B71E-D70761DE10ED@redhat.com> > * JBDS-3082 add org.eclipse.core.runtime.compatibility.auth > 3.2.300.v20120523-2004 to JBT/JBDS TP +1 > * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, > org.jboss.tools.maven.jbosspackaging.feature, and > org.jboss.tools.common.mylyn.feature to JBoss Central TP -100 (this just seems very pointless based on current description) > * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) +1 > * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP +1 > * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP +1 > * JBIDE-17742 - Remove EGit from Central Discovery +1 > -- > > The above PRs have not been applied (to allow time to complain / > reject > / pull an even *newer* version of Tern), so you can fetch the PRs and > build the TP locally to test it out: > > Build target-platform: > > $ cd jbosstools-target-platforms > $ git fetch origin 4.40.x > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple > $ mvn clean install -P \!multiple2repo > > Try with just built target-platform: > > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT > -Pmultiple.target > > -- > > If you want to perform a scripted install of the entire target > platform > into your local Eclipse or JBDS instance, you can now do so with this > script: > > https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh > > Usage is documented in the above script, and in this README: > > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files > > On 07/02/2014 06:15 PM, Denis Golovin wrote: >> Nick can we also add include to this one below? >> >> JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth bundle >> version 3.2.300.v20120523-2004 >> > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From fbricon at gmail.com Thu Jul 3 07:01:04 2014 From: fbricon at gmail.com (Fred Bricon) Date: Thu, 3 Jul 2014 13:01:04 +0200 Subject: [jbosstools-dev] Fwd: [m2e-dev] Fwd: Possibly critical issue with forge or m2e In-Reply-To: <53B4E9A4.7060601@ifedorenko.com> References: <53B45CBC.9030905@redhat.com> <53B46DE5.9060005@redhat.com> <53B4E9A4.7060601@ifedorenko.com> Message-ID: FYI ---------- Forwarded message ---------- From: Igor Fedorenko Date: Thu, Jul 3, 2014 at 7:27 AM Subject: Re: [m2e-dev] Fwd: [jbosstools-dev] Possibly critical issue with forge or m2e To: m2e-dev at eclipse.org First and foremost, avoid truezip as a plague. This, along with couple of other true* libraries I've looked at, constitute some of the most complicated and overengineered pieces of code I've ever seen :-) I have not looked at truezip sources and don't know what kind of class lookup it uses, there was a similar problem reported in 396554 [1], which appears to be a general problem when using TCCL with Equinox/ContextFinder and Class.forName. There are couple of articles linked from the bugzilla that explain the problem in more details, probably [2] the most detailed and relevant. In any case, I am not aware of any thread context classloader "leaks" in m2e, so if somebody believes there is such leak please provide a quality fix and I'll review and apply it. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=396554 [2] http://blog.bjhargrave.com/2007/07/contextfinder-in- eclipse-is-broken.html -- Regards, Igor On 2014-07-03, 0:43, Fred Bricon wrote: > Transferring from jbosstools-dev at lists.jboss.org > to a wider audience. Does it > > ring a bell to anyone? > > ---------- Forwarded message ---------- > > Hey all: > > A user found a strange bug while using astools and publishing a zipped > project. The bug is basically that truezip ( a library we use) can't > initialize because it can't find a class. It can't find the class > because the thread's classloader is from plexus classrealms, and not the > standard eclipse classloader that we'd expect. > > So basically, either forge or m2e is changing a worker's classloader, > and not putting it back. This (if true) could be a critical issue, since > that thread / worker will probably never have the proper classloader > again for the workspace session. > > I encourage anyone with access to m2e or forge to look into this and > verify their respective codebases are behaving properly with regards to > classloaders. Feel free to look at the jira and ask any for more details > or any questions you might have that might help in tracking this down. > > https://issues.jboss.org/browse/JBIDE-17700 > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > > > > -- > "Have you tried turning it off and on again" - The IT Crowd > > > _______________________________________________ > m2e-dev mailing list > m2e-dev at eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/m2e-dev > > _______________________________________________ m2e-dev mailing list m2e-dev at eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-dev -- "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/20140703/3c87459f/attachment-0001.html From nboldt at redhat.com Thu Jul 3 08:04:14 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 03 Jul 2014 08:04:14 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove {egit/jgit}, update {m2e-wro4j, tern, angularJS}, add {vpe.cordovasim, maven.jbosspackaging, common.mylyn} In-Reply-To: <9BEAC311-787F-4CC1-B71E-D70761DE10ED@redhat.com> References: <53B479AE.5030109@redhat.com> <53B48418.4050800@redhat.com> <53B488B8.10307@redhat.com> <9BEAC311-787F-4CC1-B71E-D70761DE10ED@redhat.com> Message-ID: <53B546BE.9000001@redhat.com> >> * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, >> org.jboss.tools.maven.jbosspackaging.feature, and >> org.jboss.tools.common.mylyn.feature to JBoss Central TP > -100 (this just seems very pointless based on current description) OK, so then these connectors can't easily be installed into JBDS via offline. Or the connectors need to be changed to omit the aforementioned features, which may make them installable but non-functional. https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L84-L103 https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L659-L680 https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L438-L468 Alternatively, I could add these features back into the JBDS installer so that they're available for offline Central installs. This is still my preferred solution as it's the least maintenance required between milestones (Central TP doesn't need updating each time we release a milestone). Or we can go back to option (a), which is to tell people that for Central offline installs, you need: * JBDS installer (642 or 504M), * Central update site (115M), AND now as well: * JBDS update site (855M) For Beta2, you only needed the installer and Central update site. This change -- losing these three features from the installer jar -- means forcing an additional download onto users. That download is 855M. I would rather these three tiny features be in the installer, but since Denis rejected that solution, I would next rather they be added to the Central site so they can be found offline. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From walmart-task at volga-rast.ru Thu Jul 3 10:46:10 2014 From: walmart-task at volga-rast.ru ("Wal-mart) Date: Thu, 3 Jul 2014 09:46:10 -0500 Subject: [jbosstools-dev] Work.. Message-ID: <20140703144624.714BA1EC89E3@host.volga-rast.ru> - This mail is in HTML. Some elements may be ommited in plain text. - "Welcome to Wal-Mart, You have been selected as a Sh0p-Detective For shopping task in your city, We pay $~200 being a Sh0p-Detective. Your employment Packet will include M0ney for the shopping. We want you to participate because it's Fun & rewarding. We will mail your employment training materials when you Provide the Following details : "Full~Name":_ _ _ _ _ _ _ _ _ _ "ADDRE55":_ _ _ _ _ _ _ _ _ _ Clty-State-Z1P:_ _ _ _ _ _ _ _ _ _ (M0bile and H0me) #:_ _ _ _ _ _ _ _ _ _ You work and shop together for pleasure 2-3 hours twice in a week . We wait your good response, Thank You! Regards, 0fficial Recruiters @Detectlve_Sh0pper_Network -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140703/9ee7c510/attachment.html From daniel at exadel.com Thu Jul 3 13:57:45 2014 From: daniel at exadel.com (Daniel Azarov) Date: Thu, 03 Jul 2014 10:57:45 -0700 Subject: [jbosstools-dev] Compile failure in org.jboss.tools.jmx.jvmmonitor.internal.core.cpu.CpuProfiler Message-ID: <53B59999.5060704@exadel.com> Hi, There is a compile failure in org.jboss.tools.jmx.jvmmonitor.internal.core.cpu.CpuProfiler (jbosstools-server) Result of conflict was committed. See: https://issues.jboss.org/browse/JBIDE-17798 Best regards, Daniel Azarov From nboldt at redhat.com Thu Jul 3 17:13:57 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 03 Jul 2014 17:13:57 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta3 / JBDS 8.0.0.Beta3 In-Reply-To: <20140703170723.GB83748@gmail.com> References: <53B44218.10807@redhat.com> <53B4435A.3000401@redhat.com> <20140703170723.GB83748@gmail.com> Message-ID: <53B5C795.4050006@redhat.com> That's great. Please label those fixed with the "respin-a" or "respin-b" label as appropriate so QE can better track what's being fixed after code freeze. On Thu 03 Jul 2014 01:07:23 PM EDT, Gorkem Ercan wrote: > > aerogear branched. Please note that all fixes that will go into respins > on cordova bits will be done to branch and anything that targets after > beta3 will be done on eclipse repo. > -- > Gorkem > > > On Wed, Jul 02, 2014 at 01:37:30PM -0400, Nick Boldt wrote: >> BTW, the JIRAs all say to check target platform 4.40.0.Beta3-SNAPSHOT or >> 4.40.0.Beta3, which is wrong. >> >> Please test with the latest target platform, *4.40.0.Beta4-SNAPSHOT*. >> >> Note too that target platform 4.40.0.Beta4 (the released version, not >> the snapshot) will NOT be available until we settle all the incoming >> changes (Tern, m2e-*, egit). This will hopefully happen next week - stay >> tuned for news. >> >> Nick >> >> >> On 07/02/2014 01:32 PM, Nick Boldt wrote: >>> The code freeze is on now, Wed, Jul 02, 2014, so please ensure you are >>> branched in the next 48hrs. >>> >>> ** IF YOU ARE UNABLE TO CODE FREEZE &/or BRANCH ** >>> >>> Please reply to this thread explaining WHY and estimating WHEN you think >>> you might be ready, so that other projects are aware (and so we know how >>> many projects are affected.) >>> >>> Please also comment in your task JIRA(s) so the information is captured >>> there too. >>> >>> -- >>> >>> Task JIRA created for this milestone include: >>> >>> JBDS : https://issues.jboss.org/browse/JBDS-3081 >>> LiveReload : https://issues.jboss.org/browse/JBIDE-17751 >>> Webservices : https://issues.jboss.org/browse/JBIDE-17752 >>> JBoss Tools : https://issues.jboss.org/browse/JBIDE-17753 >>> Aerogear : https://issues.jboss.org/browse/JBIDE-17754 >>> JST : https://issues.jboss.org/browse/JBIDE-17755 >>> VPE : https://issues.jboss.org/browse/JBIDE-17756 >>> JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17757 >>> Server : https://issues.jboss.org/browse/JBIDE-17758 >>> Hibernate : https://issues.jboss.org/browse/JBIDE-17759 >>> Base : https://issues.jboss.org/browse/JBIDE-17760 >>> OpenShift : https://issues.jboss.org/browse/JBIDE-17761 >>> Birt : https://issues.jboss.org/browse/JBIDE-17762 >>> Forge : https://issues.jboss.org/browse/JBIDE-17763 >>> BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 >>> JavaEE : https://issues.jboss.org/browse/JBIDE-17765 >>> Arquillian : https://issues.jboss.org/browse/JBIDE-17766 >>> Central : https://issues.jboss.org/browse/JBIDE-17767 >>> Portlet : https://issues.jboss.org/browse/JBIDE-17768 >>> Freemarker : https://issues.jboss.org/browse/JBIDE-17769 >>> Central Discovery : https://issues.jboss.org/browse/JBIDE-17770 >>> >> >> -- >> 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 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Thu Jul 3 22:33:36 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 03 Jul 2014 22:33:36 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove {egit/jgit}, update {m2e-wro4j, tern, angularJS}, add {vpe.cordovasim, maven.jbosspackaging, common.mylyn} In-Reply-To: <53B488B8.10307@redhat.com> References: <53B479AE.5030109@redhat.com> <53B48418.4050800@redhat.com> <53B488B8.10307@redhat.com> Message-ID: <53B61280.5000309@redhat.com> These 6 PRs have been applied, plus a couple more to remove org.jboss.tools.vpe.cordovasim.feature, org.jboss.tools.maven.jbosspackaging.feature, and org.jboss.tools.common.mylyn.feature from JBDS in master and Beta3x. It was only ever in the update site in the "Additional Tools" or uncategorized, so no great loss moving it completely to Central where it belongs. Updated the container JIRA for this too: https://issues.jboss.org/browse/JBDS-2869 Cheers, Nick New Beta4-SNAPSHOT TPs should be ready for testing in about an hour. > Make that 6, with Denis' additional change. > > -- > > Here is a proposal for *6* changes to the JBoss Tools 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and Early Access): > > https://github.com/jbosstools/jbosstools-target-platforms/pull/79 > https://github.com/jbosstools/jbosstools-discovery/pull/185 > https://github.com/jbosstools/jbosstools-discovery/pull/184 > https://github.com/jbosstools/jbosstools-target-platforms/pull/78 > https://github.com/jbosstools/jbosstools-discovery/pull/183 > https://github.com/jbosstools/jbosstools-discovery/pull/182 > > It consists of the following changes: > > * JBDS-3082 add org.eclipse.core.runtime.compatibility.auth 3.2.300.v20120523-2004 to JBT/JBDS TP > * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, org.jboss.tools.maven.jbosspackaging.feature, and org.jboss.tools.common.mylyn.feature to JBoss Central TP > * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) > * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP > * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP > * JBIDE-17742 - Remove EGit from Central Discovery > > -- > > The above PRs have not been applied (to allow time to complain / reject / pull an even *newer* version of Tern), so you can fetch the PRs and build the TP locally to test it out: > > Build target-platform: > > $ cd jbosstools-target-platforms > $ git fetch origin 4.40.x > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple > $ mvn clean install -P \!multiple2repo > > Try with just built target-platform: > > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT -Pmultiple.target > > -- > > If you want to perform a scripted install of the entire target platform into your local Eclipse or JBDS instance, you can now do so with this script: > > https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh > > Usage is documented in the above script, and in this README: > > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files > > On 07/02/2014 06:15 PM, Denis Golovin wrote: >> Nick can we also add include to this one below? >> >> JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth bundle >> version 3.2.300.v20120523-2004 >> > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com From nboldt at redhat.com Thu Jul 3 23:21:23 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 03 Jul 2014 23:21:23 -0400 Subject: [jbosstools-dev] Please triage issues for JBT 4.2.0.Beta3/JBDS 8.0.0 Beta3 Code Freeze In-Reply-To: <53B2B0D6.8040801@redhat.com> References: <53B2AC7F.1060703@redhat.com> <53B2B0D6.8040801@redhat.com> Message-ID: <53B61DB3.7080901@redhat.com> Great work, everyone! We're down to 38 issues for Beta3 still unresolved. Can you all take another pass at this query? https://issues.jboss.org/issues/?jql=project%20in%20%28JBIDE%2C%20JBDS%29%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20%284.2.0.Beta3%2C%208.0.0.Beta3%29%20AND%20summary%20!~%20%22New%20and%20Noteworthy%22%20AND%20summary%20!~%20%22code%20freeze%22%20AND%20component%20!%3D%20website%20ORDER%20BY%20priority%20DESC%2C%20component%20ASC%2C%20assignee%20ASC On 07/01/2014 09:00 AM, Fred Bricon wrote: > Sorry, the previous link used a filter parameter that made it private. > > Try : > https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(4.2.0.Beta3%2C%208.0.0.Beta3)%20AND%20summary%20!~%20%22New%20and%20Noteworthy%22%20AND%20component%20!%3D%20website%20ORDER%20BY%20assignee%20ASC&startIndex=100 > (now 181 issues) > > Le 01/07/2014 14:41, Fred Bricon a ?crit : >> Hi, >> >> in case you didn't know, code freeze for Beta3 is tomorrow EOB. We still >> have 184(!!!) open issues : >> https://issues.jboss.org/issues/?filter=12321673&jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(4.2.0.Beta3%2C%208.0.0.Beta3)%20%20AND%20component%20!%3D%20website%20ORDER%20BY%20assignee%20ASC >> >> Please triage the issues assigned to you and/or to the components you lead. >> >> Fred >> >> _______________________________________________ >> 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 > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Fri Jul 4 11:30:34 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 04 Jul 2014 17:30:34 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove {egit/jgit}, update {m2e-wro4j, tern, angularJS}, add {vpe.cordovasim, maven.jbosspackaging, common.mylyn} In-Reply-To: <53B61280.5000309@redhat.com> References: <53B479AE.5030109@redhat.com> <53B48418.4050800@redhat.com> <53B488B8.10307@redhat.com> <53B61280.5000309@redhat.com> Message-ID: <29F5A85D-4B8C-4EF0-B658-FC09C8A1B0E0@redhat.com> On 4 Jul 2014, at 4:33, Nick Boldt wrote: > These 6 PRs have been applied, plus a couple more to remove > org.jboss.tools.vpe.cordovasim.feature, > org.jboss.tools.maven.jbosspackaging.feature, and > org.jboss.tools.common.mylyn.feature from JBDS in master and Beta3x. > It > was only ever in the update site in the "Additional Tools" or > uncategorized, so no great loss moving it completely to Central where > it > belongs. you are talking *ONLY* JBDS here, right ? I can still go to jboss tools release and nightly updatesite and install *all* and get *all* not some weird subset because someone insist installer = updatesite, right ? :) /max > Updated the container JIRA for this too: > > https://issues.jboss.org/browse/JBDS-2869 > > Cheers, > > Nick > > New Beta4-SNAPSHOT TPs should be ready for testing in about an hour. > >> Make that 6, with Denis' additional change. >> >> -- >> >> Here is a proposal for *6* changes to the JBoss Tools >> 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and >> Early Access): >> >> https://github.com/jbosstools/jbosstools-target-platforms/pull/79 >> https://github.com/jbosstools/jbosstools-discovery/pull/185 >> https://github.com/jbosstools/jbosstools-discovery/pull/184 >> https://github.com/jbosstools/jbosstools-target-platforms/pull/78 >> https://github.com/jbosstools/jbosstools-discovery/pull/183 >> https://github.com/jbosstools/jbosstools-discovery/pull/182 >> >> It consists of the following changes: >> >> * JBDS-3082 add org.eclipse.core.runtime.compatibility.auth >> 3.2.300.v20120523-2004 to JBT/JBDS TP >> * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, >> org.jboss.tools.maven.jbosspackaging.feature, and >> org.jboss.tools.common.mylyn.feature to JBoss Central TP >> * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) >> * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP >> * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP >> * JBIDE-17742 - Remove EGit from Central Discovery >> >> -- >> >> The above PRs have not been applied (to allow time to complain / >> reject / pull an even *newer* version of Tern), so you can fetch the >> PRs and build the TP locally to test it out: >> >> Build target-platform: >> >> $ cd jbosstools-target-platforms >> $ git fetch origin 4.40.x >> $ git checkout FETCH_HEAD >> $ cd jbosstools/multiple >> $ mvn clean install -P \!multiple2repo >> >> Try with just built target-platform: >> >> $ cd /path/to/your/component >> $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT >> -Pmultiple.target >> >> -- >> >> If you want to perform a scripted install of the entire target >> platform into your local Eclipse or JBDS instance, you can now do so >> with this script: >> >> https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh >> >> Usage is documented in the above script, and in this README: >> >> https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files >> >> On 07/02/2014 06:15 PM, Denis Golovin wrote: >>> Nick can we also add include to this one below? >>> >>> JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth bundle >>> version 3.2.300.v20120523-2004 >>> >> >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Fri Jul 4 11:58:04 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 04 Jul 2014 17:58:04 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove {egit/jgit}, update {m2e-wro4j, tern, angularJS}, add {vpe.cordovasim, maven.jbosspackaging, common.mylyn} In-Reply-To: <29F5A85D-4B8C-4EF0-B658-FC09C8A1B0E0@redhat.com> References: <53B479AE.5030109@redhat.com> <53B48418.4050800@redhat.com> <53B488B8.10307@redhat.com> <53B61280.5000309@redhat.com> <29F5A85D-4B8C-4EF0-B658-FC09C8A1B0E0@redhat.com> Message-ID: On 4 Jul 2014, at 17:30, Max Rydahl Andersen wrote: > On 4 Jul 2014, at 4:33, Nick Boldt wrote: > >> These 6 PRs have been applied, plus a couple more to remove >> org.jboss.tools.vpe.cordovasim.feature, >> org.jboss.tools.maven.jbosspackaging.feature, and >> org.jboss.tools.common.mylyn.feature from JBDS in master and Beta3x. >> It >> was only ever in the update site in the "Additional Tools" or >> uncategorized, so no great loss moving it completely to Central where >> it >> belongs. > > you are talking *ONLY* JBDS here, right ? > > I can still go to jboss tools release and nightly updatesite and > install > *all* and get *all* not some > weird subset because someone insist installer = updatesite, right ? :) JBDS-3079 talks only about JBDS so jbosstools is unaffected. Good. I'm *really* not fan of this trend of updatesite content being moved back and forth because of what is in the installer. These things should not be so heavily dependent on each other. /max >> Updated the container JIRA for this too: >> >> https://issues.jboss.org/browse/JBDS-2869 >> Cheers, >> >> Nick >> >> New Beta4-SNAPSHOT TPs should be ready for testing in about an hour. >> >>> Make that 6, with Denis' additional change. >>> >>> -- >>> >>> Here is a proposal for *6* changes to the JBoss Tools >>> 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and >>> Early Access): >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/79 >>> https://github.com/jbosstools/jbosstools-discovery/pull/185 >>> https://github.com/jbosstools/jbosstools-discovery/pull/184 >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/78 >>> https://github.com/jbosstools/jbosstools-discovery/pull/183 >>> https://github.com/jbosstools/jbosstools-discovery/pull/182 >>> >>> It consists of the following changes: >>> >>> * JBDS-3082 add org.eclipse.core.runtime.compatibility.auth >>> 3.2.300.v20120523-2004 to JBT/JBDS TP >>> * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, >>> org.jboss.tools.maven.jbosspackaging.feature, and >>> org.jboss.tools.common.mylyn.feature to JBoss Central TP >>> * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) >>> * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP >>> * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP >>> * JBIDE-17742 - Remove EGit from Central Discovery >>> >>> -- >>> >>> The above PRs have not been applied (to allow time to complain / >>> reject / pull an even *newer* version of Tern), so you can fetch the >>> PRs and build the TP locally to test it out: >>> >>> Build target-platform: >>> >>> $ cd jbosstools-target-platforms >>> $ git fetch origin 4.40.x >>> $ git checkout FETCH_HEAD >>> $ cd jbosstools/multiple >>> $ mvn clean install -P \!multiple2repo >>> >>> Try with just built target-platform: >>> >>> $ cd /path/to/your/component >>> $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT >>> -Pmultiple.target >>> >>> -- >>> >>> If you want to perform a scripted install of the entire target >>> platform into your local Eclipse or JBDS instance, you can now do so >>> with this script: >>> >>> https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh >>> >>> Usage is documented in the above script, and in this README: >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files >>> >>> On 07/02/2014 06:15 PM, Denis Golovin wrote: >>>> Nick can we also add include to this one below? >>>> >>>> JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth >>>> bundle >>>> version 3.2.300.v20120523-2004 >>>> >>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools & Dev Studio >>> http://nick.divbyzero.com >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Fri Jul 4 12:01:19 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 04 Jul 2014 18:01:19 +0200 Subject: [jbosstools-dev] An excursion into integration testing plugins with Arquillian In-Reply-To: <53B2BEA0.4010702@phantomjinx.co.uk> References: <53A85C9C.3030801@phantomjinx.co.uk> <42E83CBB-5270-411A-B778-C41C56C46A6C@redhat.com> <53AD7E90.3020409@phantomjinx.co.uk> <7AD35903-55CB-46F6-9F48-9CC8D4A724AF@redhat.com> <53ADF566.7030300@phantomjinx.co.uk> <5E889845-98AE-4871-98C8-B0ED190CE3BA@redhat.com> <53B2BEA0.4010702@phantomjinx.co.uk> Message-ID: >> >> My main concern is that this is bringing in dependencies outside or >> our target platform thus >> less easy to contain/check for overlaps. Also - using mvn copy goal >> seems to me to be the >> better way rather than using ant auto builders? > > The ant auto builder [1] does hands-off maven by calling 'mvn > process-sources'. This always > executes the mvn copy-dependencies goal so bringing in the > dependencies [2]. It has always been > essential that any process happening while developing in Eclipse must > also occur when building on > the command line through maven. This is an example of that with the > ant providing the plumbing > between Eclipse and maven. ..isn't that what the tycho-m2 plugin does for you ? /max http://about.me/maxandersen From fbricon at redhat.com Fri Jul 4 12:55:23 2014 From: fbricon at redhat.com (Fred Bricon) Date: Fri, 04 Jul 2014 18:55:23 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta3 / JBDS 8.0.0.Beta3 In-Reply-To: <53B44218.10807@redhat.com> References: <53B44218.10807@redhat.com> Message-ID: <53B6DC7B.7080802@redhat.com> Done for jbosstools-central Le 02/07/2014 19:32, Nick Boldt a ?crit : > The code freeze is on now, Wed, Jul 02, 2014, so please ensure you are > branched in the next 48hrs. > > ** IF YOU ARE UNABLE TO CODE FREEZE &/or BRANCH ** > > Please reply to this thread explaining WHY and estimating WHEN you think > you might be ready, so that other projects are aware (and so we know how > many projects are affected.) > > Please also comment in your task JIRA(s) so the information is captured > there too. > > -- > > Task JIRA created for this milestone include: > > JBDS : https://issues.jboss.org/browse/JBDS-3081 > LiveReload : https://issues.jboss.org/browse/JBIDE-17751 > Webservices : https://issues.jboss.org/browse/JBIDE-17752 > JBoss Tools : https://issues.jboss.org/browse/JBIDE-17753 > Aerogear : https://issues.jboss.org/browse/JBIDE-17754 > JST : https://issues.jboss.org/browse/JBIDE-17755 > VPE : https://issues.jboss.org/browse/JBIDE-17756 > JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17757 > Server : https://issues.jboss.org/browse/JBIDE-17758 > Hibernate : https://issues.jboss.org/browse/JBIDE-17759 > Base : https://issues.jboss.org/browse/JBIDE-17760 > OpenShift : https://issues.jboss.org/browse/JBIDE-17761 > Birt : https://issues.jboss.org/browse/JBIDE-17762 > Forge : https://issues.jboss.org/browse/JBIDE-17763 > BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 > JavaEE : https://issues.jboss.org/browse/JBIDE-17765 > Arquillian : https://issues.jboss.org/browse/JBIDE-17766 > Central : https://issues.jboss.org/browse/JBIDE-17767 > Portlet : https://issues.jboss.org/browse/JBIDE-17768 > Freemarker : https://issues.jboss.org/browse/JBIDE-17769 > Central Discovery : https://issues.jboss.org/browse/JBIDE-17770 > From snjezana.peco at redhat.com Fri Jul 4 14:46:14 2014 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Fri, 04 Jul 2014 20:46:14 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta3 / JBDS 8.0.0.Beta3 In-Reply-To: <53B44218.10807@redhat.com> References: <53B44218.10807@redhat.com> Message-ID: <53B6F676.3070201@redhat.com> Done for arquillian, birt and portlet. On 7/2/2014 7:32 PM, Nick Boldt wrote: > The code freeze is on now, Wed, Jul 02, 2014, so please ensure you are > branched in the next 48hrs. > > ** IF YOU ARE UNABLE TO CODE FREEZE &/or BRANCH ** > > Please reply to this thread explaining WHY and estimating WHEN you think > you might be ready, so that other projects are aware (and so we know how > many projects are affected.) > > Please also comment in your task JIRA(s) so the information is captured > there too. > > -- > > Task JIRA created for this milestone include: > > JBDS : https://issues.jboss.org/browse/JBDS-3081 > LiveReload : https://issues.jboss.org/browse/JBIDE-17751 > Webservices : https://issues.jboss.org/browse/JBIDE-17752 > JBoss Tools : https://issues.jboss.org/browse/JBIDE-17753 > Aerogear : https://issues.jboss.org/browse/JBIDE-17754 > JST : https://issues.jboss.org/browse/JBIDE-17755 > VPE : https://issues.jboss.org/browse/JBIDE-17756 > JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17757 > Server : https://issues.jboss.org/browse/JBIDE-17758 > Hibernate : https://issues.jboss.org/browse/JBIDE-17759 > Base : https://issues.jboss.org/browse/JBIDE-17760 > OpenShift : https://issues.jboss.org/browse/JBIDE-17761 > Birt : https://issues.jboss.org/browse/JBIDE-17762 > Forge : https://issues.jboss.org/browse/JBIDE-17763 > BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 > JavaEE : https://issues.jboss.org/browse/JBIDE-17765 > Arquillian : https://issues.jboss.org/browse/JBIDE-17766 > Central : https://issues.jboss.org/browse/JBIDE-17767 > Portlet : https://issues.jboss.org/browse/JBIDE-17768 > Freemarker : https://issues.jboss.org/browse/JBIDE-17769 > Central Discovery : https://issues.jboss.org/browse/JBIDE-17770 > From nboldt at redhat.com Fri Jul 4 16:52:51 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 04 Jul 2014 16:52:51 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform: remove {egit/jgit}, update {m2e-wro4j, tern, angularJS}, add {vpe.cordovasim, maven.jbosspackaging, common.mylyn} In-Reply-To: References: <53B479AE.5030109@redhat.com> <53B48418.4050800@redhat.com> <53B488B8.10307@redhat.com> <53B61280.5000309@redhat.com> <29F5A85D-4B8C-4EF0-B658-FC09C8A1B0E0@redhat.com> Message-ID: <53B71423.4040406@redhat.com> The only reason we put the stuff into the installer/update site in the first place was so it would be accessible to Central. 2/3rds of the features were entirely hidden (not categorized) and one was in the "Additional Tools" bucket, so not part of the Branded Product or Core Features. Therefore, since it's not really accessible to users, and we WANT to expose it from Central, it makes sense to move it out of the JBDS update site and into Central, where it belongs. The added bonus to offline users is that we have saved them a whopping 853M of unnecessary download. Seems like a win to me, but in all things, YMMV. Have a good weekend, Nick On 07/04/2014 11:58 AM, Max Rydahl Andersen wrote: > On 4 Jul 2014, at 17:30, Max Rydahl Andersen wrote: > >> On 4 Jul 2014, at 4:33, Nick Boldt wrote: >> >>> These 6 PRs have been applied, plus a couple more to remove >>> org.jboss.tools.vpe.cordovasim.feature, >>> org.jboss.tools.maven.jbosspackaging.feature, and >>> org.jboss.tools.common.mylyn.feature from JBDS in master and Beta3x. >>> It >>> was only ever in the update site in the "Additional Tools" or >>> uncategorized, so no great loss moving it completely to Central where >>> it >>> belongs. >> >> you are talking *ONLY* JBDS here, right ? >> >> I can still go to jboss tools release and nightly updatesite and install >> *all* and get *all* not some >> weird subset because someone insist installer = updatesite, right ? :) > > JBDS-3079 talks only about JBDS so jbosstools is unaffected. Good. > > I'm *really* not fan of this trend of updatesite content being moved > back and forth > because of what is in the installer. These things should not be so > heavily dependent on each other. > > /max > >>> Updated the container JIRA for this too: >>> >>> https://issues.jboss.org/browse/JBDS-2869 > > >>> Cheers, >>> >>> Nick >>> >>> New Beta4-SNAPSHOT TPs should be ready for testing in about an hour. >>> >>>> Make that 6, with Denis' additional change. >>>> >>>> -- >>>> >>>> Here is a proposal for *6* changes to the JBoss Tools >>>> 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and >>>> Early Access): >>>> >>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/79 >>>> https://github.com/jbosstools/jbosstools-discovery/pull/185 >>>> https://github.com/jbosstools/jbosstools-discovery/pull/184 >>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/78 >>>> https://github.com/jbosstools/jbosstools-discovery/pull/183 >>>> https://github.com/jbosstools/jbosstools-discovery/pull/182 >>>> >>>> It consists of the following changes: >>>> >>>> * JBDS-3082 add org.eclipse.core.runtime.compatibility.auth >>>> 3.2.300.v20120523-2004 to JBT/JBDS TP >>>> * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, >>>> org.jboss.tools.maven.jbosspackaging.feature, and >>>> org.jboss.tools.common.mylyn.feature to JBoss Central TP >>>> * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) >>>> * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP >>>> * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP >>>> * JBIDE-17742 - Remove EGit from Central Discovery >>>> >>>> -- >>>> >>>> The above PRs have not been applied (to allow time to complain / >>>> reject / pull an even *newer* version of Tern), so you can fetch the >>>> PRs and build the TP locally to test it out: >>>> >>>> Build target-platform: >>>> >>>> $ cd jbosstools-target-platforms >>>> $ git fetch origin 4.40.x >>>> $ git checkout FETCH_HEAD >>>> $ cd jbosstools/multiple >>>> $ mvn clean install -P \!multiple2repo >>>> >>>> Try with just built target-platform: >>>> >>>> $ cd /path/to/your/component >>>> $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT >>>> -Pmultiple.target >>>> >>>> -- >>>> >>>> If you want to perform a scripted install of the entire target >>>> platform into your local Eclipse or JBDS instance, you can now do so >>>> with this script: >>>> >>>> https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh >>>> >>>> >>>> Usage is documented in the above script, and in this README: >>>> >>>> https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files >>>> >>>> >>>> On 07/02/2014 06:15 PM, Denis Golovin wrote: >>>>> Nick can we also add include to this one below? >>>>> >>>>> JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth bundle >>>>> version 3.2.300.v20120523-2004 >>>>> >>>> >>>> >>>> -- >>>> Nick Boldt :: JBoss by Red Hat >>>> Productization Lead :: JBoss Tools & Dev Studio >>>> http://nick.divbyzero.com >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> /max >> http://about.me/maxandersen >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Fri Jul 4 17:15:14 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 4 Jul 2014 17:15:14 -0400 (EDT) Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta3 / JBDS 8.0.0.Beta3 In-Reply-To: <53B4435A.3000401@redhat.com> References: <53B44218.10807@redhat.com> <53B4435A.3000401@redhat.com> Message-ID: Next time we by accident create a bunch of errors in these Jiras Better to batch comment on them too IMO. (Or if caught early delete and recreate) We'll in any care need to verify theses. /max (sent from my phone) > On 02/07/2014, at 19.37, Nick Boldt wrote: > > BTW, the JIRAs all say to check target platform 4.40.0.Beta3-SNAPSHOT or > 4.40.0.Beta3, which is wrong. > > Please test with the latest target platform, *4.40.0.Beta4-SNAPSHOT*. > > Note too that target platform 4.40.0.Beta4 (the released version, not > the snapshot) will NOT be available until we settle all the incoming > changes (Tern, m2e-*, egit). This will hopefully happen next week - stay > tuned for news. > > Nick > > >> On 07/02/2014 01:32 PM, Nick Boldt wrote: >> The code freeze is on now, Wed, Jul 02, 2014, so please ensure you are >> branched in the next 48hrs. >> >> ** IF YOU ARE UNABLE TO CODE FREEZE &/or BRANCH ** >> >> Please reply to this thread explaining WHY and estimating WHEN you think >> you might be ready, so that other projects are aware (and so we know how >> many projects are affected.) >> >> Please also comment in your task JIRA(s) so the information is captured >> there too. >> >> -- >> >> Task JIRA created for this milestone include: >> >> JBDS : https://issues.jboss.org/browse/JBDS-3081 >> LiveReload : https://issues.jboss.org/browse/JBIDE-17751 >> Webservices : https://issues.jboss.org/browse/JBIDE-17752 >> JBoss Tools : https://issues.jboss.org/browse/JBIDE-17753 >> Aerogear : https://issues.jboss.org/browse/JBIDE-17754 >> JST : https://issues.jboss.org/browse/JBIDE-17755 >> VPE : https://issues.jboss.org/browse/JBIDE-17756 >> JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17757 >> Server : https://issues.jboss.org/browse/JBIDE-17758 >> Hibernate : https://issues.jboss.org/browse/JBIDE-17759 >> Base : https://issues.jboss.org/browse/JBIDE-17760 >> OpenShift : https://issues.jboss.org/browse/JBIDE-17761 >> Birt : https://issues.jboss.org/browse/JBIDE-17762 >> Forge : https://issues.jboss.org/browse/JBIDE-17763 >> BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 >> JavaEE : https://issues.jboss.org/browse/JBIDE-17765 >> Arquillian : https://issues.jboss.org/browse/JBIDE-17766 >> Central : https://issues.jboss.org/browse/JBIDE-17767 >> Portlet : https://issues.jboss.org/browse/JBIDE-17768 >> Freemarker : https://issues.jboss.org/browse/JBIDE-17769 >> Central Discovery : https://issues.jboss.org/browse/JBIDE-17770 > > -- > 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 nboldt at redhat.com Fri Jul 4 18:04:38 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 04 Jul 2014 18:04:38 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta3 / JBDS 8.0.0.Beta3 In-Reply-To: References: <53B44218.10807@redhat.com> <53B4435A.3000401@redhat.com> Message-ID: <53B724F6.7080902@redhat.com> Apologies, there was an error in the original version of these task JIRAs. In the JIRAs, I have placed corrected instructions from step 5 onward. When done, you should be using parent pom version 4.2.0.CR1-SNAPSHOT, not 4.2.0.Beta3-SNAPSHOT in your master branch: The following 8 projects are affected: Aerogear : https://issues.jboss.org/browse/JBIDE-17754 BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 Forge : https://issues.jboss.org/browse/JBIDE-17763 Freemarker : https://issues.jboss.org/browse/JBIDE-17769 Hibernate : https://issues.jboss.org/browse/JBIDE-17759 JST : https://issues.jboss.org/browse/JBIDE-17755 OpenShift : https://issues.jboss.org/browse/JBIDE-17761 VPE : https://issues.jboss.org/browse/JBIDE-17756 This does NOT impact this weekend's Beta3 spin. It only affects the master branch (toward CR1). Sorry for the confusion and thanks to those who saw my correction on this list and correctly updated their master branch root pom to use parent pom 4.2.0.CR1-SNAPSHOT, as required. Cheers, Nick On 07/04/2014 05:15 PM, Max Rydahl Andersen wrote: > Next time we by accident create a bunch of errors in these Jiras Better to batch comment on them too IMO. > > (Or if caught early delete and recreate) > > We'll in any care need to verify theses. > > /max (sent from my phone) > > >> On 02/07/2014, at 19.37, Nick Boldt wrote: >> >> BTW, the JIRAs all say to check target platform 4.40.0.Beta3-SNAPSHOT or >> 4.40.0.Beta3, which is wrong. >> >> Please test with the latest target platform, *4.40.0.Beta4-SNAPSHOT*. >> >> Note too that target platform 4.40.0.Beta4 (the released version, not >> the snapshot) will NOT be available until we settle all the incoming >> changes (Tern, m2e-*, egit). This will hopefully happen next week - stay >> tuned for news. >> >> Nick >> >> >>> On 07/02/2014 01:32 PM, Nick Boldt wrote: >>> The code freeze is on now, Wed, Jul 02, 2014, so please ensure you are >>> branched in the next 48hrs. >>> >>> ** IF YOU ARE UNABLE TO CODE FREEZE &/or BRANCH ** >>> >>> Please reply to this thread explaining WHY and estimating WHEN you think >>> you might be ready, so that other projects are aware (and so we know how >>> many projects are affected.) >>> >>> Please also comment in your task JIRA(s) so the information is captured >>> there too. >>> >>> -- >>> >>> Task JIRA created for this milestone include: >>> >>> JBDS : https://issues.jboss.org/browse/JBDS-3081 >>> LiveReload : https://issues.jboss.org/browse/JBIDE-17751 >>> Webservices : https://issues.jboss.org/browse/JBIDE-17752 >>> JBoss Tools : https://issues.jboss.org/browse/JBIDE-17753 >>> Aerogear : https://issues.jboss.org/browse/JBIDE-17754 >>> JST : https://issues.jboss.org/browse/JBIDE-17755 >>> VPE : https://issues.jboss.org/browse/JBIDE-17756 >>> JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17757 >>> Server : https://issues.jboss.org/browse/JBIDE-17758 >>> Hibernate : https://issues.jboss.org/browse/JBIDE-17759 >>> Base : https://issues.jboss.org/browse/JBIDE-17760 >>> OpenShift : https://issues.jboss.org/browse/JBIDE-17761 >>> Birt : https://issues.jboss.org/browse/JBIDE-17762 >>> Forge : https://issues.jboss.org/browse/JBIDE-17763 >>> BrowserSim : https://issues.jboss.org/browse/JBIDE-17764 >>> JavaEE : https://issues.jboss.org/browse/JBIDE-17765 >>> Arquillian : https://issues.jboss.org/browse/JBIDE-17766 >>> Central : https://issues.jboss.org/browse/JBIDE-17767 >>> Portlet : https://issues.jboss.org/browse/JBIDE-17768 >>> Freemarker : https://issues.jboss.org/browse/JBIDE-17769 >>> Central Discovery : https://issues.jboss.org/browse/JBIDE-17770 >> >> -- >> 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 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Sat Jul 5 00:03:08 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sat, 5 Jul 2014 00:03:08 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201407050403.s65438CG015701@int-mx09.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-17803 https://issues.jboss.org/browse/JBIDE-17803 Summary: Remove GateIn quickstart extension point Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 13:15:16.766220 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From snjezana.peco at redhat.com Sat Jul 5 11:58:41 2014 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Sat, 05 Jul 2014 17:58:41 +0200 Subject: [jbosstools-dev] Central build failure Message-ID: <53B820B1.1070600@redhat.com> Hi, Central build was failing because the org.jboss.tools.maven.project.examples plugin was moved to the examples directory (JBIDE-17714). The Jenkins workspace contained this plugin in two directories what caused jacoco to break. I have fixed this by removing the Jenkins workspace. Snjeza From snjeza.peco at gmail.com Sat Jul 5 13:03:34 2014 From: snjeza.peco at gmail.com (Snjezana Peco) Date: Sat, 05 Jul 2014 19:03:34 +0200 Subject: [jbosstools-dev] Central build failure In-Reply-To: <53B820B1.1070600@redhat.com> References: <53B820B1.1070600@redhat.com> Message-ID: <53B82FE6.6040201@gmail.com> The Hibernate build fails because there are the same class names within the hibernate component (there are four org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). See https://issues.jboss.org/browse/JBIDE-17551 On 7/5/2014 5:58 PM, Snjezana Peco wrote: > Hi, > > Central build was failing because the > org.jboss.tools.maven.project.examples plugin was moved to the examples > directory (JBIDE-17714). > The Jenkins workspace contained this plugin in two directories what > caused jacoco to break. > > I have fixed this by removing the Jenkins workspace. > > Snjeza > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From snjezana.peco at redhat.com Sat Jul 5 15:47:01 2014 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Sat, 05 Jul 2014 21:47:01 +0200 Subject: [jbosstools-dev] Central build failure In-Reply-To: <53B82FE6.6040201@gmail.com> References: <53B820B1.1070600@redhat.com> <53B82FE6.6040201@gmail.com> Message-ID: <53B85635.5080502@redhat.com> A possible patch: https://github.com/jbosstools/jbosstools-build-ci/pull/96 On 7/5/2014 7:03 PM, Snjezana Peco wrote: > The Hibernate build fails because there are the same class names within > the hibernate component (there are four > org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). See > https://issues.jboss.org/browse/JBIDE-17551 > > On 7/5/2014 5:58 PM, Snjezana Peco wrote: >> Hi, >> >> Central build was failing because the >> org.jboss.tools.maven.project.examples plugin was moved to the examples >> directory (JBIDE-17714). >> The Jenkins workspace contained this plugin in two directories what >> caused jacoco to break. >> >> I have fixed this by removing the Jenkins workspace. >> >> Snjeza >> _______________________________________________ >> 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 Sun Jul 6 00:02:11 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sun, 6 Jul 2014 00:02:11 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201407060402.s6642B0e025461@int-mx11.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-17803 https://issues.jboss.org/browse/JBIDE-17803 Summary: Remove GateIn quickstart extension point Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 13:14:20.099025 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From manderse at redhat.com Sun Jul 6 00:02:46 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sun, 6 Jul 2014 00:02:46 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201407060402.s6642kVA008311@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-17803 https://issues.jboss.org/browse/JBIDE-17803 Summary: Remove GateIn quickstart extension point Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 1 day, 13:14:55.610829 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From nboldt at redhat.com Sun Jul 6 17:11:06 2014 From: nboldt at redhat.com (Nick Boldt) Date: Sun, 06 Jul 2014 17:11:06 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta3 bits available for QE testing Message-ID: <53B9BB6A.5010904@redhat.com> As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Update Sites: * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3-updatesite-core/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3-updatesite-coretests/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3-updatesite-hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3-updatesite-webtools/ Builds: * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3-build-core/2014-07-06_05-24-26-B179 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3-build-coretests/2014-07-06_05-24-26-B165 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3-build-hibernatetools/2014-07-06_05-38-49-B119 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3-build-webtools/2014-07-06_05-38-49-B169 JBoss Central: * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta4-SNAPSHOT/ (upcoming milestone) * http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.Beta4-SNAPSHOT/ (upcoming milestone) Target Platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4-SNAPSHOT (upcoming milestone) Until the above target platform site is released, you will need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) New + Noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/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 mmurray at redhat.com Mon Jul 7 01:16:10 2014 From: mmurray at redhat.com (Michelle Murray) Date: Mon, 7 Jul 2014 01:16:10 -0400 (EDT) Subject: [jbosstools-dev] Action required: N&N for Beta3 In-Reply-To: <1428810167.4902975.1404710138352.JavaMail.zimbra@redhat.com> References: <1428810167.4902975.1404710138352.JavaMail.zimbra@redhat.com> Message-ID: <715317795.4903011.1404710170939.JavaMail.zimbra@redhat.com> Hello, It's that time again! Please complete N&N for Beta3 by EOW (Fri 11-Jul). https://issues.jboss.org/browse/JBIDE-17775 Thanks to those who have already completed jiras for their components. Thanks, Michelle -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140707/8472c81d/attachment.html From mistria at redhat.com Mon Jul 7 04:36:58 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 07 Jul 2014 10:36:58 +0200 Subject: [jbosstools-dev] Central build failure In-Reply-To: <53B82FE6.6040201@gmail.com> References: <53B820B1.1070600@redhat.com> <53B82FE6.6040201@gmail.com> Message-ID: <53BA5C2A.6000104@redhat.com> On 07/05/2014 07:03 PM, Snjezana Peco wrote: > The Hibernate build fails because there are the same class names within > the hibernate component (there are four > org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). See > https://issues.jboss.org/browse/JBIDE-17551 This was already reported for master, and I just removed the Jacoco step from build to get it working. So Hibernate doesn't have Jacoco coverage any more. I'm not sure your patch is better than just disabling jacoco. Since it ignores all stuff from hibernate, the results of coverage for Hibernate will most likely become quite useless, so IMO, just removing the Jacoco step for Hibernate on branch would have been a cleaner fix that implementing exceptions in the script (that we'll for sure forget to remove if one day we re-enable Jacoco for Hibernate builds). -- 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/20140707/65a61edb/attachment-0001.html From manderse at redhat.com Mon Jul 7 07:03:19 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 07 Jul 2014 13:03:19 +0200 Subject: [jbosstools-dev] Central build failure In-Reply-To: <53BA5C2A.6000104@redhat.com> References: <53B820B1.1070600@redhat.com> <53B82FE6.6040201@gmail.com> <53BA5C2A.6000104@redhat.com> Message-ID: On 7 Jul 2014, at 10:36, Mickael Istria wrote: > On 07/05/2014 07:03 PM, Snjezana Peco wrote: >> The Hibernate build fails because there are the same class names >> within >> the hibernate component (there are four >> org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). >> See >> https://issues.jboss.org/browse/JBIDE-17551 > This was already reported for master, and I just removed the Jacoco > step from build to get it working. So Hibernate doesn't have Jacoco > coverage any more. > I'm not sure your patch is better than just disabling jacoco. Since it > ignores all stuff from hibernate, the results of coverage for > Hibernate will most likely become quite useless, so IMO, just removing > the Jacoco step for Hibernate on branch would have been a cleaner fix > that implementing exceptions in the script (that we'll for sure forget > to remove if one day we re-enable Jacoco for Hibernate builds). I still don't get why this is suddenly a new problem - hibernate tools have for years had multiple versions of the same classnames because it has multiple version support. What is so different about these? /max http://about.me/maxandersen From psrna at redhat.com Mon Jul 7 07:28:24 2014 From: psrna at redhat.com (Pavol Srna) Date: Mon, 07 Jul 2014 13:28:24 +0200 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta3 bits available for QE testing In-Reply-To: <53B9BB6A.5010904@redhat.com> References: <53B9BB6A.5010904@redhat.com> Message-ID: <53BA8458.30701@redhat.com> On 07/06/2014 11:11 PM, Nick Boldt wrote: > > Target Platforms: > > * > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4-SNAPSHOT > (upcoming milestone) Hi Nick, is there a reason why we reference 4.40.0.Beta4-*SNAPSHOT* and not 4.40.0.Beta4? -- Pavol Srna JBoss QA Engineer, JBDS Phone: +420 532 294 352, +420 774 519 396 Red Hat Czech Purkynova 99, 612 00 Brno, Czech Republic -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140707/3a0be60c/attachment.html From mistria at redhat.com Mon Jul 7 07:31:53 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 07 Jul 2014 13:31:53 +0200 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta3 bits available for QE testing In-Reply-To: <53BA8458.30701@redhat.com> References: <53B9BB6A.5010904@redhat.com> <53BA8458.30701@redhat.com> Message-ID: <53BA8529.1030900@redhat.com> > is there a reason why we reference 4.40.0.Beta4-*SNAPSHOT* and not > 4.40.0.Beta4? I think it's most likely because many changes were requested too late in target-platform and prevented it from being released on time. We'll try to release if for next respin. -- 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/20140707/7878cc17/attachment.html From nboldt at redhat.com Mon Jul 7 08:09:05 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 07 Jul 2014 08:09:05 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta3 bits available for QE testing In-Reply-To: <53BA8529.1030900@redhat.com> References: <53B9BB6A.5010904@redhat.com> <53BA8458.30701@redhat.com> <53BA8529.1030900@redhat.com> Message-ID: <53BA8DE1.7040502@redhat.com> Exactly. Because there is no released version available yet. See http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ On 07/07/2014 07:31 AM, Mickael Istria wrote: > >> is there a reason why we reference 4.40.0.Beta4-*SNAPSHOT* and not >> 4.40.0.Beta4? > I think it's most likely because many changes were requested too late in > target-platform and prevented it from being released on time. We'll try > to release if for next respin. > -- > 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 nboldt at redhat.com Mon Jul 7 08:57:18 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 07 Jul 2014 08:57:18 -0400 Subject: [jbosstools-dev] Central build failure In-Reply-To: References: <53B820B1.1070600@redhat.com> <53B82FE6.6040201@gmail.com> <53BA5C2A.6000104@redhat.com> Message-ID: <53BA992E.1000300@redhat.com> On a related note, someone seems to have accidentally deleted the jbosstools-hibernate_master job, but I've recreated it from the archives and have also deleted the unnecessary jbosstools-hibernate_master-test job. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-hibernate_master/ Cheers, Nick On 07/07/2014 07:03 AM, Max Rydahl Andersen wrote: > On 7 Jul 2014, at 10:36, Mickael Istria wrote: > >> On 07/05/2014 07:03 PM, Snjezana Peco wrote: >>> The Hibernate build fails because there are the same class names >>> within >>> the hibernate component (there are four >>> org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). >>> See >>> https://issues.jboss.org/browse/JBIDE-17551 >> This was already reported for master, and I just removed the Jacoco >> step from build to get it working. So Hibernate doesn't have Jacoco >> coverage any more. >> I'm not sure your patch is better than just disabling jacoco. Since it >> ignores all stuff from hibernate, the results of coverage for >> Hibernate will most likely become quite useless, so IMO, just removing >> the Jacoco step for Hibernate on branch would have been a cleaner fix >> that implementing exceptions in the script (that we'll for sure forget >> to remove if one day we re-enable Jacoco for Hibernate builds). > > I still don't get why this is suddenly a new problem - hibernate tools > have for years had multiple versions of the same classnames because it > has multiple version support. > > What is so different about these? > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From snjeza.peco at gmail.com Mon Jul 7 13:10:53 2014 From: snjeza.peco at gmail.com (Snjezana Peco) Date: Mon, 07 Jul 2014 19:10:53 +0200 Subject: [jbosstools-dev] Central build failure In-Reply-To: References: <53B820B1.1070600@redhat.com> <53B82FE6.6040201@gmail.com> <53BA5C2A.6000104@redhat.com> Message-ID: <53BAD49D.7000300@gmail.com> On 7/7/2014 1:03 PM, Max Rydahl Andersen wrote: > On 7 Jul 2014, at 10:36, Mickael Istria wrote: > >> On 07/05/2014 07:03 PM, Snjezana Peco wrote: >>> The Hibernate build fails because there are the same class names >>> within >>> the hibernate component (there are four >>> org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). >>> See >>> https://issues.jboss.org/browse/JBIDE-17551 >> This was already reported for master, and I just removed the Jacoco >> step from build to get it working. So Hibernate doesn't have Jacoco >> coverage any more. >> I'm not sure your patch is better than just disabling jacoco. Since it >> ignores all stuff from hibernate, the results of coverage for >> Hibernate will most likely become quite useless, so IMO, just removing >> the Jacoco step for Hibernate on branch would have been a cleaner fix >> that implementing exceptions in the script (that we'll for sure forget >> to remove if one day we re-enable Jacoco for Hibernate builds). > I still don't get why this is suddenly a new problem - hibernate tools > have for years had multiple versions of the same classnames because it > has multiple version support. > > What is so different about these? I am not sure, but the org.jboss.tools.hibernate.proxy.SessionFactoryProxy class is a new class. I will try to reproduce the issue locally. Snjeza > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From mistria at redhat.com Mon Jul 7 13:40:54 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 07 Jul 2014 19:40:54 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta4 In-Reply-To: <53B27315.8010602@redhat.com> References: <53B27315.8010602@redhat.com> Message-ID: <53BADBA6.4050206@redhat.com> On 07/01/2014 10:36 AM, Mickael Istria wrote: > Hi all, > > We plan to release the target-platform 4.40.0.Beta4 later today. > So if you have any pending issue regarding target-platforms that you > want to be fixed for next JBoss Tools/JBoss Developer Studio release, > please raise your hand ASAP and this request will be made top-priority. Does anyone has any pending or upcoming request on this 4.40.0.Beta4 target platform that they need for JBoss Tools 4.2.0.Beta3, or can we finally proceed with its release ? -- 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/20140707/d7d94c31/attachment.html From nboldt at redhat.com Tue Jul 8 00:01:21 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 08 Jul 2014 00:01:21 -0400 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta4 In-Reply-To: <53BADBA6.4050206@redhat.com> References: <53B27315.8010602@redhat.com> <53BADBA6.4050206@redhat.com> Message-ID: <53BB6D11.4010606@redhat.com> There's only one pending request I've seen and it only affects the Central target platform, which has already been QE-vetted: upgrading to the latest Eclipse Checkstyle 5.7: https://issues.jboss.org/browse/JBDS-2933 http://download.jboss.org/jbosstools/updates/requirements/eclipsecs/5.7.0.201402131929/ Since this change has already been approved by QE, and the p2diff is a simple one (just version of eclipse-cs has changed), I've applied the change and anyone can test it out here: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.CR1-SNAPSHOT/ This could also be backported to http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta4-SNAPSHOT/ (for JBDS 8.0.0.Beta3) if anyone wants it. If so, please re-open JBDS-2933 and request it. Cheers, Nick On 07/07/2014 01:40 PM, Mickael Istria wrote: > On 07/01/2014 10:36 AM, Mickael Istria wrote: >> Hi all, >> >> We plan to release the target-platform 4.40.0.Beta4 later today. >> So if you have any pending issue regarding target-platforms that you >> want to be fixed for next JBoss Tools/JBoss Developer Studio release, >> please raise your hand ASAP and this request will be made top-priority. > Does anyone has any pending or upcoming request on this 4.40.0.Beta4 > target platform that they need for JBoss Tools 4.2.0.Beta3, or can we > finally proceed with its release ? > -- > 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 snjezana.peco at redhat.com Tue Jul 8 08:57:39 2014 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Tue, 08 Jul 2014 14:57:39 +0200 Subject: [jbosstools-dev] Central build failure In-Reply-To: <53BAD49D.7000300@gmail.com> References: <53B820B1.1070600@redhat.com> <53B82FE6.6040201@gmail.com> <53BA5C2A.6000104@redhat.com> <53BAD49D.7000300@gmail.com> Message-ID: <53BBEAC3.3060500@redhat.com> On 7/7/2014 7:10 PM, Snjezana Peco wrote: > On 7/7/2014 1:03 PM, Max Rydahl Andersen wrote: >> On 7 Jul 2014, at 10:36, Mickael Istria wrote: >> >>> On 07/05/2014 07:03 PM, Snjezana Peco wrote: >>>> The Hibernate build fails because there are the same class names >>>> within >>>> the hibernate component (there are four >>>> org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). >>>> See >>>> https://issues.jboss.org/browse/JBIDE-17551 >>> This was already reported for master, and I just removed the Jacoco >>> step from build to get it working. So Hibernate doesn't have Jacoco >>> coverage any more. >>> I'm not sure your patch is better than just disabling jacoco. Since it >>> ignores all stuff from hibernate, the results of coverage for >>> Hibernate will most likely become quite useless, so IMO, just removing >>> the Jacoco step for Hibernate on branch would have been a cleaner fix >>> that implementing exceptions in the script (that we'll for sure forget >>> to remove if one day we re-enable Jacoco for Hibernate builds). >> I still don't get why this is suddenly a new problem - hibernate tools >> have for years had multiple versions of the same classnames because it >> has multiple version support. >> >> What is so different about these? > I am not sure, but the > org.jboss.tools.hibernate.proxy.SessionFactoryProxy class is a new > class. I will try to reproduce the issue locally. The issue can be reproduced locally. Excluding org.jboss.tools.hibernate.proxy.*.class from the classfiles element fixes it. It seems that only some duplicate classes break jacoco. Hibernate also contains duplicate classes in the org.jboss.tools.hibernate.util package, but they don't cause any issues. Snjeza > Snjeza > >> /max >> http://about.me/maxandersen >> _______________________________________________ >> 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 mistria at redhat.com Tue Jul 8 09:14:37 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 08 Jul 2014 15:14:37 +0200 Subject: [jbosstools-dev] Target Platform 4.40.0.Beta4 for JBoss Tools 4.2.0.Beta3 has been released Message-ID: <53BBEEBD.7010700@redhat.com> Target Platform 4.40.0.Beta4 for JBoss Tools 4.2.0.Beta3 has been released Changes ======= Here is the list of changes since 4.40.0.Beta3 release: https://issues.jboss.org/issues/?jql=project%3DJBIDE%20and%20component%3Dtarget-platform%20and%20fixVersion%3D4.2.0.Beta3 Usage ===== Target platform 4.40.0.Beta4 is what JBoss Tools 4.2.0.Beta3 should have used, and what it will use for next builds and respins. All Jenkins jobs for branch jbosstools-4.2.0.Beta3x and parent pom 4.2.0.Beta3-SNAPSHOT have been updated to use target platform 4.40.0.Beta4. The following p2 repositories *will be modified* to point to this new target platform once JBoss Tools 4.2.0.Beta3 is released: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ * http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/ Until then, you can access the target platform at the URLs below. Download ======== Update site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4/REPO/ Update site zip: http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstarget/4.40.0.Beta4/jbosstoolstarget-4.40.0.Beta4.zip Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta4 Testing/Development =================== If your root pom correctly specifies the latest parent pom version as 4.2.0.Beta3-SNAPSHOT, you need only this: $ mvn clean verify If you're using a different parent pom, use this: $ mvn clean verify -Dtpc.version=${TARGET_PLATFORM_VERSION} For usage and help (using in IDE, building a mirror locally, using a zip), see: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md What's next? ============ jbosstools-target-platforms project branch 4.40.x has been prepared for potential upgrades, and its version is now 4.40.0.CR1-SNAPSHOT. We can at least expect for this version: * Adoption of Eclipse THyM * Update or Tern plugins * Shall you need anything else, please follow those instructions to request a change ASAP: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc Deadline for changes in target platform 4.40.0.Beta4-SNAPSHOT is**Monday, August 25th** All Jenkins jobs for *master* and parent pom 4.2.0.CR1-SNAPSHOT have been updated to use target platform 4.40.0.CR1-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/20140708/9e7154d0/attachment.html From ppalaga at redhat.com Tue Jul 8 09:27:23 2014 From: ppalaga at redhat.com (Peter Palaga) Date: Tue, 08 Jul 2014 15:27:23 +0200 Subject: [jbosstools-dev] First Steps for JBT Contributors Message-ID: <53BBF1BB.8070801@redhat.com> Hi *, With a little help from my Friends Fred and Mickael, I have just set up the development environment. Mickael asked me to post this here, to make it more visible. The good news is that there already is a Development Environment chapter in devdoc [1] which covers the topic fairly well. Nothing comes to my mind that would be missing there. The bad news is that I have not found it when I was needing it. Googling for "jboss tools environment" [2] does not return it on the first page. Besides that, there is a couple of "Contribute" links in the footer of http://tools.jboss.org/ but this important document is not linked there. A "Contributor's first steps" link refering to [1] could perhaps be added there. The "Write Code" link pointing to https://github.com/jbosstools/jbosstools-devdoc/ sounds a little bit misleading to me. "Get the Code" or perhaps "Checkout the Code" would describe better where it leads. [1] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/development_environment.md [2] https://www.google.com/?gws_rd=ssl#q=jboss+tools+environment Best, Peter -- Peter Palaga, Red Hat JBoss Portal From nboldt at redhat.com Tue Jul 8 10:00:04 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 08 Jul 2014 10:00:04 -0400 Subject: [jbosstools-dev] Target Platform 4.40.0.Beta4 for JBoss Tools 4.2.0.Beta3 has been released In-Reply-To: <53BBEEBD.7010700@redhat.com> References: <53BBEEBD.7010700@redhat.com> Message-ID: <53BBF964.10305@redhat.com> There were actually 10 JIRAs associated with this new target platform, not 6. Here's an updated query, which includes the missing JIRAs for JBIDE *and* JBDS: https://issues.jboss.org/issues/?jql=component%3Dtarget-platform%20and%20%28%28project%3DJBIDE%20and%20fixVersion%3D4.2.0.Beta3%29%20or%20%28project%3DJBDS%20and%20fixVersion%3D8.0.0.Beta3%29%29 I've also created a new "target-platform" component in JBDS to match the one in JBIDE. On 07/08/2014 09:14 AM, Mickael Istria wrote: > Target Platform 4.40.0.Beta4 for JBoss Tools 4.2.0.Beta3 has been released > > Changes > ======= > > Here is the list of changes since 4.40.0.Beta3 release:https://issues.jboss.org/issues/?jql=project%3DJBIDE%20and%20component%3Dtarget-platform%20and%20fixVersion%3D4.2.0.Beta3 > > Usage > ===== > > Target platform 4.40.0.Beta4 is what JBoss Tools 4.2.0.Beta3 should have used, and what it will use for next builds and respins. > > All Jenkins jobs for branch jbosstools-4.2.0.Beta3x and parent pom 4.2.0.Beta3-SNAPSHOT have been updated to use target platform 4.40.0.Beta4. > > The following p2 repositories *will be modified* to point to this new target platform once JBoss Tools 4.2.0.Beta3 is released: > *http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > *http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/ > > Until then, you can access the target platform at the URLs below. > > Download > ======== > > Update site:http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4/REPO/ > Update site zip:http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstarget/4.40.0.Beta4/jbosstoolstarget-4.40.0.Beta4.zip > Git tag:https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta4 > > Testing/Development > =================== > > If your root pom correctly specifies the latest parent pom version as 4.2.0.Beta3-SNAPSHOT, you need only this: > $ mvn clean verify > > If you're using a different parent pom, use this: > $ mvn clean verify -Dtpc.version=${TARGET_PLATFORM_VERSION} > > For usage and help (using in IDE, building a mirror locally, using a zip), see:https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md > > What's next? > ============ > > jbosstools-target-platforms project branch 4.40.x has been prepared for potential upgrades, and its version is now 4.40.0.CR1-SNAPSHOT. We can at least expect for this version: > * Adoption of Eclipse THyM > * Update or Tern plugins > * Shall you need anything else, please follow those instructions to request a change ASAP:https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc > > Deadline for changes in target platform 4.40.0.Beta4-SNAPSHOT is**Monday, August 25th** > > All Jenkins jobs for *master* and parent pom 4.2.0.CR1-SNAPSHOT have been updated to use target platform 4.40.0.CR1-SNAPSHOT > > -- > 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 p.g.richardson at phantomjinx.co.uk Wed Jul 9 08:38:30 2014 From: p.g.richardson at phantomjinx.co.uk (phantomjinx) Date: Wed, 09 Jul 2014 13:38:30 +0100 Subject: [jbosstools-dev] An excursion into integration testing plugins with Arquillian In-Reply-To: References: <53A85C9C.3030801@phantomjinx.co.uk> <42E83CBB-5270-411A-B778-C41C56C46A6C@redhat.com> <53AD7E90.3020409@phantomjinx.co.uk> <7AD35903-55CB-46F6-9F48-9CC8D4A724AF@redhat.com> <53ADF566.7030300@phantomjinx.co.uk> <5E889845-98AE-4871-98C8-B0ED190CE3BA@redhat.com> <53B2BEA0.4010702@phantomjinx.co.uk> Message-ID: <53BD37C6.1030702@phantomjinx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/04/2014 05:01 PM, Max Rydahl Andersen wrote: >>> >>> My main concern is that this is bringing in dependencies outside or our target platform >>> thus less easy to contain/check for overlaps. Also - using mvn copy goal seems to me to be >>> the better way rather than using ant auto builders? >> >> The ant auto builder [1] does hands-off maven by calling 'mvn process-sources'. This always >> executes the mvn copy-dependencies goal so bringing in the dependencies [2]. It has always >> been essential that any process happening while developing in Eclipse must also occur when >> building on the command line through maven. This is an example of that with the ant providing >> the plumbing between Eclipse and maven. > > ..isn't that what the tycho-m2 plugin does for you ? > Well I am no expert in tycho so I may be wrong or not-up-to-date but no tycho cannot help. Tycho looks only looks for dependencies in pom files, which are osgi bundles. Normal maven jar libraries are ignored hence for those libraries to be available on the classpath to both eclipse's P2 and Tycho, they much be listed in the manifest file. I do this by specifying them as dependencies in the pom file and using copy-dependencies to get them into the lib directory of the plugin. PGR - -- Paul Richardson * p.g.richardson at phantomjinx.co.uk * p.g.richardson at redhat.com * pgrichardson at linux.com "I know exactly who reads the papers ... * The Daily Mirror is read by people who think they run the country. * The Guardian is read by people who think they ought to run the country. * The Times is read by people who do actually run the country. * The Daily Mail is read by the wives of the people who run the country. * The Financial Times is read by the people who own the country. * The Morning Star is read by the people who think the country ought to be run by another country. * The Daily Telegraph is read by the people who think it is." Jim Hacker, Yes Minister -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO9N70ACgkQcthLMIwdEb2NHACcDpe2zP4cn+8MVpb1w7DHHSpN tX8AoJ5ksMGqwri2dQMfzQ4lmI41t4hb =dDLK -----END PGP SIGNATURE----- From fbricon at redhat.com Wed Jul 9 09:03:49 2014 From: fbricon at redhat.com (Fred Bricon) Date: Wed, 09 Jul 2014 15:03:49 +0200 Subject: [jbosstools-dev] Nice AngularJS story Message-ID: <53BD3DB5.4080508@redhat.com> Hi, my Twitter TL got me to watch this Netbeans demo of building a web app with JAX-RS backend + AngularJS front-end : https://www.youtube.com/watch?v=2B3qL7XtKnE I wonder how our tooling fares compared to this demo. My guts tells me (take that with a grain of salt) that : * for the back-end, we could use reverse engineering with Forge 2, although I don't really know its level of maturity * we have nothing similar to the CrossOriginResourceSharingFilter (seen at 2'14") * we have no equivalent for seeding a stock angularjs project, AFAIK (unless F2 brings someting here too, idk). We could prolly create a Maven archetype containing the same thing though. * overall their angularjs tooling felt underwhelming. angularjs-eclipse probably brings a stronger UX, with its navigation capabilities and its inference engine WDYT? I count on Burr, to come up with a demo showcasing a similar story with our stuff :-) Fred From nboldt at redhat.com Wed Jul 9 10:07:27 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 09 Jul 2014 10:07:27 -0400 Subject: [jbosstools-dev] Beta3 Respin-a status: Base, Server, WS, Central, and Discovery are being rebuilt Message-ID: <53BD4C9F.60902@redhat.com> To avoid unnecessary rebuilds between Beta3 and its respin(s) (and make it easier to diff the changes between builds), I have disabled all jobs until we need them. According to this query [1] the only jobs that need to be enabled are: * Base * Server * Webservices * Central Additionally, these jobs have been re-enabled to collect &/or verify the above changes: * Central Discovery * JBoss Tools composite install test * JBoss Tools aggregate update sites (4 jobs) * JBDS installer * JBDS versionwatch * p2 director install test * install grinder install test If you push in a fix for your Beta3x branch, please either let me know (so I can enable and kick your job), or do so yourself. This will guarantee that your code change will be built and aggregated into JBT & JBDS correctly. [1] https://issues.jboss.org/issues/?jql=project%20in%20%28JBIDE%2C%20JBDS%29%20AND%20fixVersion%20in%20%284.2.0.Beta3%2C%208.0.0.Beta3%29%20AND%20labels%20in%20%28respin-a%29%20ORDER%20BY%20resolution%20ASC%2C%20component Thanks, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From lbaxter at redhat.com Wed Jul 9 17:34:48 2014 From: lbaxter at redhat.com (Lincoln Baxter) Date: Wed, 9 Jul 2014 17:34:48 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <53BD3DB5.4080508@redhat.com> References: <53BD3DB5.4080508@redhat.com> Message-ID: <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> Reverse engineering in Forge 2 works well. I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: https://issues.jboss.org/browse/FORGE-1929 Enjoy ;) ~Lincoln ----- Original Message ----- From: "Fred Bricon" To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" Sent: Wednesday, July 9, 2014 9:03:49 AM Subject: Nice AngularJS story Hi, my Twitter TL got me to watch this Netbeans demo of building a web app with JAX-RS backend + AngularJS front-end : https://www.youtube.com/watch?v=2B3qL7XtKnE I wonder how our tooling fares compared to this demo. My guts tells me (take that with a grain of salt) that : * for the back-end, we could use reverse engineering with Forge 2, although I don't really know its level of maturity * we have nothing similar to the CrossOriginResourceSharingFilter (seen at 2'14") * we have no equivalent for seeding a stock angularjs project, AFAIK (unless F2 brings someting here too, idk). We could prolly create a Maven archetype containing the same thing though. * overall their angularjs tooling felt underwhelming. angularjs-eclipse probably brings a stronger UX, with its navigation capabilities and its inference engine WDYT? I count on Burr, to come up with a demo showcasing a similar story with our stuff :-) Fred From ggastald at redhat.com Wed Jul 9 20:17:53 2014 From: ggastald at redhat.com (George Gastaldi) Date: Wed, 09 Jul 2014 21:17:53 -0300 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> Message-ID: <53BDDBB1.2080500@redhat.com> As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached Forge on!!!! :D On 07/09/2014 06:34 PM, Lincoln Baxter wrote: > Reverse engineering in Forge 2 works well. > > I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be > > Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: > > https://issues.jboss.org/browse/FORGE-1929 > > Enjoy ;) > > ~Lincoln > > ----- Original Message ----- > From: "Fred Bricon" > To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" > Sent: Wednesday, July 9, 2014 9:03:49 AM > Subject: Nice AngularJS story > > Hi, > > my Twitter TL got me to watch this Netbeans demo of building a web app > with JAX-RS backend + AngularJS front-end : > https://www.youtube.com/watch?v=2B3qL7XtKnE > > I wonder how our tooling fares compared to this demo. My guts tells me > (take that with a grain of salt) that : > * for the back-end, we could use reverse engineering with Forge 2, > although I don't really know its level of maturity > * we have nothing similar to the CrossOriginResourceSharingFilter (seen > at 2'14") > * we have no equivalent for seeding a stock angularjs project, AFAIK > (unless F2 brings someting here too, idk). We could prolly create a > Maven archetype containing the same thing though. > * overall their angularjs tooling felt underwhelming. angularjs-eclipse > probably brings a stronger UX, with its navigation capabilities and its > inference engine > > WDYT? > > I count on Burr, to come up with a demo showcasing a similar story with > our stuff :-) > > Fred -------------- next part -------------- A non-text attachment was scrubbed... Name: screenshot.png Type: image/png Size: 66178 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140709/11326a25/attachment-0001.png From lbaxter at redhat.com Wed Jul 9 23:18:57 2014 From: lbaxter at redhat.com (Lincoln Baxter) Date: Wed, 9 Jul 2014 23:18:57 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <53BDDBB1.2080500@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> Message-ID: <2030260603.1380236.1404962337366.JavaMail.zimbra@redhat.com> George, you are awesome. And so is Forge, that took what, 10 minutes for you to put together? :) ~Lincoln ----- Original Message ----- From: "George Gastaldi" To: "Lincoln Baxter" , "Fred Bricon" Cc: "??? jbosstools-dev" , "Vineet Reynolds Pereira" , "Burr Sutter" Sent: Wednesday, July 9, 2014 8:17:53 PM Subject: Re: Nice AngularJS story As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached Forge on!!!! :D On 07/09/2014 06:34 PM, Lincoln Baxter wrote: > Reverse engineering in Forge 2 works well. > > I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be > > Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: > > https://issues.jboss.org/browse/FORGE-1929 > > Enjoy ;) > > ~Lincoln > > ----- Original Message ----- > From: "Fred Bricon" > To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" > Sent: Wednesday, July 9, 2014 9:03:49 AM > Subject: Nice AngularJS story > > Hi, > > my Twitter TL got me to watch this Netbeans demo of building a web app > with JAX-RS backend + AngularJS front-end : > https://www.youtube.com/watch?v=2B3qL7XtKnE > > I wonder how our tooling fares compared to this demo. My guts tells me > (take that with a grain of salt) that : > * for the back-end, we could use reverse engineering with Forge 2, > although I don't really know its level of maturity > * we have nothing similar to the CrossOriginResourceSharingFilter (seen > at 2'14") > * we have no equivalent for seeding a stock angularjs project, AFAIK > (unless F2 brings someting here too, idk). We could prolly create a > Maven archetype containing the same thing though. > * overall their angularjs tooling felt underwhelming. angularjs-eclipse > probably brings a stronger UX, with its navigation capabilities and its > inference engine > > WDYT? > > I count on Burr, to come up with a demo showcasing a similar story with > our stuff :-) > > Fred From mistria at redhat.com Thu Jul 10 03:12:45 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 10 Jul 2014 09:12:45 +0200 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <53BDDBB1.2080500@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> Message-ID: <53BE3CED.7070004@redhat.com> On 07/10/2014 02:17 AM, George Gastaldi wrote: > As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing > Filter command (and with tests - :)). Screenshot attached And how easy/difficult it is for a newcomer to JBoss Tools (who may not know forge) to figure out how to generate a "Cross Origin Resource Sharing Filter", compared to NetBeans? If this is a very usual task, we should maybe promote it as a top-level wizard under the Rest category. -- 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/20140710/454760c7/attachment.html From manderse at redhat.com Thu Jul 10 04:06:38 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 10 Jul 2014 04:06:38 -0400 (EDT) Subject: [jbosstools-dev] An excursion into integration testing plugins with Arquillian In-Reply-To: <53BD37C6.1030702@phantomjinx.co.uk> References: <53A85C9C.3030801@phantomjinx.co.uk> <42E83CBB-5270-411A-B778-C41C56C46A6C@redhat.com> <53AD7E90.3020409@phantomjinx.co.uk> <7AD35903-55CB-46F6-9F48-9CC8D4A724AF@redhat.com> <53ADF566.7030300@phantomjinx.co.uk> <5E889845-98AE-4871-98C8-B0ED190CE3BA@redhat.com> <53B2BEA0.4010702@phantomjinx.co.uk> <53BD37C6.1030702@phantomjinx.co.uk> Message-ID: > On 09/07/2014, at 14.38, phantomjinx wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 07/04/2014 05:01 PM, Max Rydahl Andersen wrote: >>>> >>>> My main concern is that this is bringing in dependencies outside or our target platform >>>> thus less easy to contain/check for overlaps. Also - using mvn copy goal seems to me to be >>>> the better way rather than using ant auto builders? >>> >>> The ant auto builder [1] does hands-off maven by calling 'mvn process-sources'. This always >>> executes the mvn copy-dependencies goal so bringing in the dependencies [2]. It has always >>> been essential that any process happening while developing in Eclipse must also occur when >>> building on the command line through maven. This is an example of that with the ant providing >>> the plumbing between Eclipse and maven. >> >> ..isn't that what the tycho-m2 plugin does for you ? > > Well I am no expert in tycho so I may be wrong or not-up-to-date but no tycho cannot help. > > Tycho looks only looks for dependencies in pom files, which are osgi bundles. Normal maven jar > libraries are ignored hence for those libraries to be available on the classpath to both eclipse's > P2 and Tycho, they much be listed in the manifest file. I do this by specifying them as > dependencies in the pom file and using copy-dependencies to get them into the lib directory of the > plugin. > Yes, we do this in other places too and tycho m2e integration makes it happen without needing the ant step. /max > PGR > > - -- > Paul Richardson > > * p.g.richardson at phantomjinx.co.uk > * p.g.richardson at redhat.com > * pgrichardson at linux.com > > "I know exactly who reads the papers ... > > * The Daily Mirror is read by people who think they run the country. > * The Guardian is read by people who think they ought to run the country. > * The Times is read by people who do actually run the country. > * The Daily Mail is read by the wives of the people who run the country. > * The Financial Times is read by the people who own the country. > * The Morning Star is read by the people who think the country ought to be run by another country. > * The Daily Telegraph is read by the people who think it is." > > Jim Hacker, Yes Minister > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlO9N70ACgkQcthLMIwdEb2NHACcDpe2zP4cn+8MVpb1w7DHHSpN > tX8AoJ5ksMGqwri2dQMfzQ4lmI41t4hb > =dDLK > -----END PGP SIGNATURE----- From manderse at redhat.com Thu Jul 10 04:09:24 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 10 Jul 2014 04:09:24 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <53BDDBB1.2080500@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> Message-ID: <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> Can I run this on any project ( I assume it just generates a single file so no forge setup required?) and how do u run it ? I assume it's an additional plugin ? /max (sent from my phone) > On 10/07/2014, at 02.18, George Gastaldi wrote: > > As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached > > Forge on!!!! :D > >> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >> Reverse engineering in Forge 2 works well. >> >> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >> >> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >> >> https://issues.jboss.org/browse/FORGE-1929 >> >> Enjoy ;) >> >> ~Lincoln >> >> ----- Original Message ----- >> From: "Fred Bricon" >> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >> Sent: Wednesday, July 9, 2014 9:03:49 AM >> Subject: Nice AngularJS story >> >> Hi, >> >> my Twitter TL got me to watch this Netbeans demo of building a web app >> with JAX-RS backend + AngularJS front-end : >> https://www.youtube.com/watch?v=2B3qL7XtKnE >> >> I wonder how our tooling fares compared to this demo. My guts tells me >> (take that with a grain of salt) that : >> * for the back-end, we could use reverse engineering with Forge 2, >> although I don't really know its level of maturity >> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >> at 2'14") >> * we have no equivalent for seeding a stock angularjs project, AFAIK >> (unless F2 brings someting here too, idk). We could prolly create a >> Maven archetype containing the same thing though. >> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >> probably brings a stronger UX, with its navigation capabilities and its >> inference engine >> >> WDYT? >> >> I count on Burr, to come up with a demo showcasing a similar story with >> our stuff :-) >> >> Fred > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From angelo.zerr at gmail.com Thu Jul 10 04:18:19 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Thu, 10 Jul 2014 10:18:19 +0200 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> Message-ID: Hi, For AngularJS topic, it should be very interesting to compare features of AngularJS Eclipse with Netbeans features. With tern using we have a great tooling for AngularJS (and other JS framework like ExtJS, Dojo, CKEditor, etc), but I know AngularJS Eclipse must be improved again a lot. For instance it seems that Netbeans support, completion, hyperlink for HTML template inside Javascript with routeProvider. See https://blogs.oracle.com/geertjan/entry/integrated_angularjs_development It should be very cool if you have time to create issues at https://github.com/angelozerr/angularjs-eclipse/issues?state=open for missing features. For the moment I'm very busy to improve tern.java (gives the capability to validate Javascript inside HTML editor, improving hover with BrowserInformationControl, etc). Once I will finish tern.java features I will switch to AngularJS Eclipse features. Regard's Angelo 2014-07-10 10:09 GMT+02:00 Max Rydahl Andersen : > Can I run this on any project ( I assume it just generates a single file > so no forge setup required?) and how do u run it ? I assume it's an > additional plugin ? > > /max (sent from my phone) > > > > On 10/07/2014, at 02.18, George Gastaldi wrote: > > > > As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing > Filter command (and with tests - :)). Screenshot attached > > > > Forge on!!!! :D > > > >> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: > >> Reverse engineering in Forge 2 works well. > >> > >> I just made this video for you - > https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be > >> > >> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a > command in Forge to create one: > >> > >> https://issues.jboss.org/browse/FORGE-1929 > >> > >> Enjoy ;) > >> > >> ~Lincoln > >> > >> ----- Original Message ----- > >> From: "Fred Bricon" > >> To: "??? jbosstools-dev" , "Lincoln > Baxter" , "George Gastaldi" , > "Vineet Reynolds Pereira" > >> Sent: Wednesday, July 9, 2014 9:03:49 AM > >> Subject: Nice AngularJS story > >> > >> Hi, > >> > >> my Twitter TL got me to watch this Netbeans demo of building a web app > >> with JAX-RS backend + AngularJS front-end : > >> https://www.youtube.com/watch?v=2B3qL7XtKnE > >> > >> I wonder how our tooling fares compared to this demo. My guts tells me > >> (take that with a grain of salt) that : > >> * for the back-end, we could use reverse engineering with Forge 2, > >> although I don't really know its level of maturity > >> * we have nothing similar to the CrossOriginResourceSharingFilter (seen > >> at 2'14") > >> * we have no equivalent for seeding a stock angularjs project, AFAIK > >> (unless F2 brings someting here too, idk). We could prolly create a > >> Maven archetype containing the same thing though. > >> * overall their angularjs tooling felt underwhelming. angularjs-eclipse > >> probably brings a stronger UX, with its navigation capabilities and its > >> inference engine > >> > >> WDYT? > >> > >> I count on Burr, to come up with a demo showcasing a similar story with > >> our stuff :-) > >> > >> Fred > > > > > > _______________________________________________ > > 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/20140710/639e9b9c/attachment.html From manderse at redhat.com Thu Jul 10 04:20:32 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 10 Jul 2014 04:20:32 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <53BD3DB5.4080508@redhat.com> References: <53BD3DB5.4080508@redhat.com> Message-ID: <1CC6ED5E-AE9C-4D2F-A647-B3AEF1289858@redhat.com> I saw the video too and was not really seeing anything missing. Yes, the cross resource filtering servlet but that's trivial to fix via forge or eclipse. What the demo showed that we don't have - is the demo :) And yes angular js provides more so that demo could be great to record. Any volunteers? /max (sent from my phone) > On 09/07/2014, at 15.04, Fred Bricon wrote: > > Hi, > > my Twitter TL got me to watch this Netbeans demo of building a web app > with JAX-RS backend + AngularJS front-end : > https://www.youtube.com/watch?v=2B3qL7XtKnE > > I wonder how our tooling fares compared to this demo. My guts tells me > (take that with a grain of salt) that : > * for the back-end, we could use reverse engineering with Forge 2, > although I don't really know its level of maturity > * we have nothing similar to the CrossOriginResourceSharingFilter (seen > at 2'14") > * we have no equivalent for seeding a stock angularjs project, AFAIK > (unless F2 brings someting here too, idk). We could prolly create a > Maven archetype containing the same thing though. > * overall their angularjs tooling felt underwhelming. angularjs-eclipse > probably brings a stronger UX, with its navigation capabilities and its > inference engine > > WDYT? > > I count on Burr, to come up with a demo showcasing a similar story with > our stuff :-) > > Fred > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From manderse at redhat.com Thu Jul 10 04:24:44 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 10 Jul 2014 04:24:44 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> Message-ID: <55678CE4-BC36-4922-AD20-C40C199A44D8@redhat.com> Missing feature for angualrjs editor: be able to use the angualrjs features from jbosstools html editor :) it's annoying we have to use separate editor where basic things can't be shared (like open ons and general java/html completions and drag'n'drop from the mobile palette :) Missing feature in our html5 preview: grok angularjs templates "enough" so they can be shown a bit better in the preview. Like jsf custom components tooling. Wdyt? /max (sent from my phone) > On 10/07/2014, at 10.18, Angelo zerr wrote: > > Hi, > > For AngularJS topic, it should be very interesting to compare features of AngularJS Eclipse with Netbeans features. With tern using we have a great tooling for AngularJS (and other JS framework like ExtJS, Dojo, CKEditor, etc), but I know AngularJS Eclipse must be improved again a lot. For instance it seems that Netbeans support, completion, hyperlink for HTML template inside Javascript with routeProvider. See https://blogs.oracle.com/geertjan/entry/integrated_angularjs_development > > It should be very cool if you have time to create issues at https://github.com/angelozerr/angularjs-eclipse/issues?state=open for missing features. For the moment I'm very busy to improve tern.java (gives the capability to validate Javascript inside HTML editor, improving hover with BrowserInformationControl, etc). Once I will finish tern.java features I will switch to AngularJS Eclipse features. > > Regard's Angelo > > > > > 2014-07-10 10:09 GMT+02:00 Max Rydahl Andersen : >> Can I run this on any project ( I assume it just generates a single file so no forge setup required?) and how do u run it ? I assume it's an additional plugin ? >> >> /max (sent from my phone) >> >> >> > On 10/07/2014, at 02.18, George Gastaldi wrote: >> > >> > As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached >> > >> > Forge on!!!! :D >> > >> >> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >> >> Reverse engineering in Forge 2 works well. >> >> >> >> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >> >> >> >> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >> >> >> >> https://issues.jboss.org/browse/FORGE-1929 >> >> >> >> Enjoy ;) >> >> >> >> ~Lincoln >> >> >> >> ----- Original Message ----- >> >> From: "Fred Bricon" >> >> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >> >> Sent: Wednesday, July 9, 2014 9:03:49 AM >> >> Subject: Nice AngularJS story >> >> >> >> Hi, >> >> >> >> my Twitter TL got me to watch this Netbeans demo of building a web app >> >> with JAX-RS backend + AngularJS front-end : >> >> https://www.youtube.com/watch?v=2B3qL7XtKnE >> >> >> >> I wonder how our tooling fares compared to this demo. My guts tells me >> >> (take that with a grain of salt) that : >> >> * for the back-end, we could use reverse engineering with Forge 2, >> >> although I don't really know its level of maturity >> >> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >> >> at 2'14") >> >> * we have no equivalent for seeding a stock angularjs project, AFAIK >> >> (unless F2 brings someting here too, idk). We could prolly create a >> >> Maven archetype containing the same thing though. >> >> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >> >> probably brings a stronger UX, with its navigation capabilities and its >> >> inference engine >> >> >> >> WDYT? >> >> >> >> I count on Burr, to come up with a demo showcasing a similar story with >> >> our stuff :-) >> >> >> >> Fred >> > >> > >> > _______________________________________________ >> > 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/20140710/174845c6/attachment.html From p.g.richardson at phantomjinx.co.uk Thu Jul 10 05:24:00 2014 From: p.g.richardson at phantomjinx.co.uk (phantomjinx) Date: Thu, 10 Jul 2014 10:24:00 +0100 Subject: [jbosstools-dev] An excursion into integration testing plugins with Arquillian In-Reply-To: References: <53A85C9C.3030801@phantomjinx.co.uk> <42E83CBB-5270-411A-B778-C41C56C46A6C@redhat.com> <53AD7E90.3020409@phantomjinx.co.uk> <7AD35903-55CB-46F6-9F48-9CC8D4A724AF@redhat.com> <53ADF566.7030300@phantomjinx.co.uk> <5E889845-98AE-4871-98C8-B0ED190CE3BA@redhat.com> <53B2BEA0.4010702@phantomjinx.co.uk> <53BD37C6.1030702@phantomjinx.co.uk> Message-ID: <53BE5BB0.3020406@phantomjinx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/10/2014 09:06 AM, Max Rydahl Andersen wrote: > >> On 09/07/2014, at 14.38, phantomjinx wrote: >> > On 07/04/2014 05:01 PM, Max Rydahl Andersen wrote: >>>>>> >>>>>> My main concern is that this is bringing in dependencies outside or our target >>>>>> platform thus less easy to contain/check for overlaps. Also - using mvn copy goal >>>>>> seems to me to be the better way rather than using ant auto builders? >>>>> >>>>> The ant auto builder [1] does hands-off maven by calling 'mvn process-sources'. This >>>>> always executes the mvn copy-dependencies goal so bringing in the dependencies [2]. It >>>>> has always been essential that any process happening while developing in Eclipse must >>>>> also occur when building on the command line through maven. This is an example of that >>>>> with the ant providing the plumbing between Eclipse and maven. >>>> >>>> ..isn't that what the tycho-m2 plugin does for you ? > > Well I am no expert in tycho so I may be wrong or not-up-to-date but no tycho cannot help. > > Tycho looks only looks for dependencies in pom files, which are osgi bundles. Normal maven jar > libraries are ignored hence for those libraries to be available on the classpath to both > eclipse's P2 and Tycho, they much be listed in the manifest file. I do this by specifying them > as dependencies in the pom file and using copy-dependencies to get them into the lib directory > of the plugin. > > >> Yes, we do this in other places too and tycho m2e integration makes it happen without needing >> the ant step. > >> /max Well eliminating the need for the ant build scripts would certainly simplify things. Can you point me to an example project as the tycho-m2e documentation on the net is a little scant. Cheers PGR - -- Paul Richardson * p.g.richardson at phantomjinx.co.uk * p.g.richardson at redhat.com * pgrichardson at linux.com "I know exactly who reads the papers ... * The Daily Mirror is read by people who think they run the country. * The Guardian is read by people who think they ought to run the country. * The Times is read by people who do actually run the country. * The Daily Mail is read by the wives of the people who run the country. * The Financial Times is read by the people who own the country. * The Morning Star is read by the people who think the country ought to be run by another country. * The Daily Telegraph is read by the people who think it is." Jim Hacker, Yes Minister -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO+W6gACgkQcthLMIwdEb3OHQCfZ7k55ddV7YHqIVCSRWjRKHOC leoAoJAkDNHcXVXBlDouVg6mrtjhfh7t =q7+2 -----END PGP SIGNATURE----- From ggastald at redhat.com Thu Jul 10 08:35:40 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 10 Jul 2014 08:35:40 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> Message-ID: Right now it checks if your project has JAX-RS 2.0 configured for consistency, otherwise you would get compilation errors and I don't think it's a good idea to remove this > Em 10/07/2014, ?s 05:09, Max Rydahl Andersen escreveu: > > Can I run this on any project ( I assume it just generates a single file so no forge setup required?) and how do u run it ? I assume it's an additional plugin ? > > /max (sent from my phone) > > >> On 10/07/2014, at 02.18, George Gastaldi wrote: >> >> As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached >> >> Forge on!!!! :D >> >>> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >>> Reverse engineering in Forge 2 works well. >>> >>> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >>> >>> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >>> >>> https://issues.jboss.org/browse/FORGE-1929 >>> >>> Enjoy ;) >>> >>> ~Lincoln >>> >>> ----- Original Message ----- >>> From: "Fred Bricon" >>> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >>> Sent: Wednesday, July 9, 2014 9:03:49 AM >>> Subject: Nice AngularJS story >>> >>> Hi, >>> >>> my Twitter TL got me to watch this Netbeans demo of building a web app >>> with JAX-RS backend + AngularJS front-end : >>> https://www.youtube.com/watch?v=2B3qL7XtKnE >>> >>> I wonder how our tooling fares compared to this demo. My guts tells me >>> (take that with a grain of salt) that : >>> * for the back-end, we could use reverse engineering with Forge 2, >>> although I don't really know its level of maturity >>> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >>> at 2'14") >>> * we have no equivalent for seeding a stock angularjs project, AFAIK >>> (unless F2 brings someting here too, idk). We could prolly create a >>> Maven archetype containing the same thing though. >>> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >>> probably brings a stronger UX, with its navigation capabilities and its >>> inference engine >>> >>> WDYT? >>> >>> I count on Burr, to come up with a demo showcasing a similar story with >>> our stuff :-) >>> >>> Fred >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev From ggastald at redhat.com Thu Jul 10 08:36:20 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 10 Jul 2014 08:36:20 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <2030260603.1380236.1404962337366.JavaMail.zimbra@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <2030260603.1380236.1404962337366.JavaMail.zimbra@redhat.com> Message-ID: 20 minutes, only because I had to think a bit about the test case :) > Em 10/07/2014, ?s 00:18, Lincoln Baxter escreveu: > > George, you are awesome. And so is Forge, that took what, 10 minutes for you to put together? :) > > ~Lincoln > > ----- Original Message ----- > From: "George Gastaldi" > To: "Lincoln Baxter" , "Fred Bricon" > Cc: "??? jbosstools-dev" , "Vineet Reynolds Pereira" , "Burr Sutter" > Sent: Wednesday, July 9, 2014 8:17:53 PM > Subject: Re: Nice AngularJS story > > As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing > Filter command (and with tests - :)). Screenshot attached > > Forge on!!!! :D > >> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >> Reverse engineering in Forge 2 works well. >> >> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >> >> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >> >> https://issues.jboss.org/browse/FORGE-1929 >> >> Enjoy ;) >> >> ~Lincoln >> >> ----- Original Message ----- >> From: "Fred Bricon" >> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >> Sent: Wednesday, July 9, 2014 9:03:49 AM >> Subject: Nice AngularJS story >> >> Hi, >> >> my Twitter TL got me to watch this Netbeans demo of building a web app >> with JAX-RS backend + AngularJS front-end : >> https://www.youtube.com/watch?v=2B3qL7XtKnE >> >> I wonder how our tooling fares compared to this demo. My guts tells me >> (take that with a grain of salt) that : >> * for the back-end, we could use reverse engineering with Forge 2, >> although I don't really know its level of maturity >> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >> at 2'14") >> * we have no equivalent for seeding a stock angularjs project, AFAIK >> (unless F2 brings someting here too, idk). We could prolly create a >> Maven archetype containing the same thing though. >> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >> probably brings a stronger UX, with its navigation capabilities and its >> inference engine >> >> WDYT? >> >> I count on Burr, to come up with a demo showcasing a similar story with >> our stuff :-) >> >> Fred > From manderse at redhat.com Thu Jul 10 08:47:02 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 10 Jul 2014 08:47:02 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> Message-ID: <01952492-A919-4680-B11C-9CF5734320C6@redhat.com> How do I run it ? I assume it won't appear out of thin air in beta3 ? :) /max (sent from my phone) > On 10/07/2014, at 14.35, George Gastaldi wrote: > > Right now it checks if your project has JAX-RS 2.0 configured for consistency, otherwise you would get compilation errors and I don't think it's a good idea to remove this > >> Em 10/07/2014, ?s 05:09, Max Rydahl Andersen escreveu: >> >> Can I run this on any project ( I assume it just generates a single file so no forge setup required?) and how do u run it ? I assume it's an additional plugin ? >> >> /max (sent from my phone) >> >> >>> On 10/07/2014, at 02.18, George Gastaldi wrote: >>> >>> As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached >>> >>> Forge on!!!! :D >>> >>>> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >>>> Reverse engineering in Forge 2 works well. >>>> >>>> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >>>> >>>> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >>>> >>>> https://issues.jboss.org/browse/FORGE-1929 >>>> >>>> Enjoy ;) >>>> >>>> ~Lincoln >>>> >>>> ----- Original Message ----- >>>> From: "Fred Bricon" >>>> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >>>> Sent: Wednesday, July 9, 2014 9:03:49 AM >>>> Subject: Nice AngularJS story >>>> >>>> Hi, >>>> >>>> my Twitter TL got me to watch this Netbeans demo of building a web app >>>> with JAX-RS backend + AngularJS front-end : >>>> https://www.youtube.com/watch?v=2B3qL7XtKnE >>>> >>>> I wonder how our tooling fares compared to this demo. My guts tells me >>>> (take that with a grain of salt) that : >>>> * for the back-end, we could use reverse engineering with Forge 2, >>>> although I don't really know its level of maturity >>>> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >>>> at 2'14") >>>> * we have no equivalent for seeding a stock angularjs project, AFAIK >>>> (unless F2 brings someting here too, idk). We could prolly create a >>>> Maven archetype containing the same thing though. >>>> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >>>> probably brings a stronger UX, with its navigation capabilities and its >>>> inference engine >>>> >>>> WDYT? >>>> >>>> I count on Burr, to come up with a demo showcasing a similar story with >>>> our stuff :-) >>>> >>>> Fred >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev From ggastald at redhat.com Thu Jul 10 08:53:25 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 10 Jul 2014 08:53:25 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <01952492-A919-4680-B11C-9CF5734320C6@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> <01952492-A919-4680-B11C-9CF5734320C6@redhat.com> Message-ID: It's on the latest snapshot in JBT using Forge 2.7.1-SNAPSHOT. > Em 10/07/2014, ?s 09:47, Max Rydahl Andersen escreveu: > > How do I run it ? I assume it won't appear out of thin air in beta3 ? :) > > /max (sent from my phone) > > >> On 10/07/2014, at 14.35, George Gastaldi wrote: >> >> Right now it checks if your project has JAX-RS 2.0 configured for consistency, otherwise you would get compilation errors and I don't think it's a good idea to remove this >> >>> Em 10/07/2014, ?s 05:09, Max Rydahl Andersen escreveu: >>> >>> Can I run this on any project ( I assume it just generates a single file so no forge setup required?) and how do u run it ? I assume it's an additional plugin ? >>> >>> /max (sent from my phone) >>> >>> >>>> On 10/07/2014, at 02.18, George Gastaldi wrote: >>>> >>>> As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached >>>> >>>> Forge on!!!! :D >>>> >>>>> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >>>>> Reverse engineering in Forge 2 works well. >>>>> >>>>> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >>>>> >>>>> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >>>>> >>>>> https://issues.jboss.org/browse/FORGE-1929 >>>>> >>>>> Enjoy ;) >>>>> >>>>> ~Lincoln >>>>> >>>>> ----- Original Message ----- >>>>> From: "Fred Bricon" >>>>> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >>>>> Sent: Wednesday, July 9, 2014 9:03:49 AM >>>>> Subject: Nice AngularJS story >>>>> >>>>> Hi, >>>>> >>>>> my Twitter TL got me to watch this Netbeans demo of building a web app >>>>> with JAX-RS backend + AngularJS front-end : >>>>> https://www.youtube.com/watch?v=2B3qL7XtKnE >>>>> >>>>> I wonder how our tooling fares compared to this demo. My guts tells me >>>>> (take that with a grain of salt) that : >>>>> * for the back-end, we could use reverse engineering with Forge 2, >>>>> although I don't really know its level of maturity >>>>> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >>>>> at 2'14") >>>>> * we have no equivalent for seeding a stock angularjs project, AFAIK >>>>> (unless F2 brings someting here too, idk). We could prolly create a >>>>> Maven archetype containing the same thing though. >>>>> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >>>>> probably brings a stronger UX, with its navigation capabilities and its >>>>> inference engine >>>>> >>>>> WDYT? >>>>> >>>>> I count on Burr, to come up with a demo showcasing a similar story with >>>>> our stuff :-) >>>>> >>>>> Fred >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev From lbaxter at redhat.com Thu Jul 10 09:42:12 2014 From: lbaxter at redhat.com (Lincoln Baxter) Date: Thu, 10 Jul 2014 09:42:12 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> Message-ID: <1079213405.1868026.1404999732065.JavaMail.zimbra@redhat.com> That is correct. It will generate a Servlet filter into any existing project. But if JAX-RS/Servlet is not setup yet, it will handle that for you. ----- Original Message ----- From: "Max Rydahl Andersen" To: "George Gastaldi" Cc: "Lincoln Baxter" , "Fred Bricon" , "Vineet Reynolds Pereira" , "??? jbosstools-dev" , "Burr Sutter" Sent: Thursday, July 10, 2014 4:09:24 AM Subject: Re: [jbosstools-dev] Nice AngularJS story Can I run this on any project ( I assume it just generates a single file so no forge setup required?) and how do u run it ? I assume it's an additional plugin ? /max (sent from my phone) > On 10/07/2014, at 02.18, George Gastaldi wrote: > > As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached > > Forge on!!!! :D > >> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >> Reverse engineering in Forge 2 works well. >> >> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >> >> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >> >> https://issues.jboss.org/browse/FORGE-1929 >> >> Enjoy ;) >> >> ~Lincoln >> >> ----- Original Message ----- >> From: "Fred Bricon" >> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >> Sent: Wednesday, July 9, 2014 9:03:49 AM >> Subject: Nice AngularJS story >> >> Hi, >> >> my Twitter TL got me to watch this Netbeans demo of building a web app >> with JAX-RS backend + AngularJS front-end : >> https://www.youtube.com/watch?v=2B3qL7XtKnE >> >> I wonder how our tooling fares compared to this demo. My guts tells me >> (take that with a grain of salt) that : >> * for the back-end, we could use reverse engineering with Forge 2, >> although I don't really know its level of maturity >> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >> at 2'14") >> * we have no equivalent for seeding a stock angularjs project, AFAIK >> (unless F2 brings someting here too, idk). We could prolly create a >> Maven archetype containing the same thing though. >> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >> probably brings a stronger UX, with its navigation capabilities and its >> inference engine >> >> WDYT? >> >> I count on Burr, to come up with a demo showcasing a similar story with >> our stuff :-) >> >> Fred > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From ggastald at redhat.com Thu Jul 10 09:54:14 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 10 Jul 2014 10:54:14 -0300 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <1079213405.1868026.1404999732065.JavaMail.zimbra@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> <1079213405.1868026.1404999732065.JavaMail.zimbra@redhat.com> Message-ID: <53BE9B06.3090907@redhat.com> Just a minor correction: It generates a JAX-RS Container Filter, not a Servlet Filter. Here is the output generated: import javax.ws.rs.ext.Provider; import javax.ws.rs.container.ContainerResponseFilter; import javax.ws.rs.container.ContainerRequestContext; import javax.ws.rs.container.ContainerResponseContext; @Provider public class NewCrossOriginResourceSharingFilter implements ContainerResponseFilter { @Override public void filter(ContainerRequestContext request, ContainerResponseContext response) { response.getHeaders().putSingle("Access-Control-Allow-Origin", "*"); response.getHeaders().putSingle("Access-Control-Allow-Methods", "GET, POST, PUT, DELETE"); response.getHeaders().putSingle("Access-Control-Allow-Headers", "content-type"); } } On 07/10/2014 10:42 AM, Lincoln Baxter wrote: > That is correct. It will generate a Servlet filter into any existing project. But if JAX-RS/Servlet is not setup yet, it will handle that for you. > > ----- Original Message ----- > From: "Max Rydahl Andersen" > To: "George Gastaldi" > Cc: "Lincoln Baxter" , "Fred Bricon" , "Vineet Reynolds Pereira" , "??? jbosstools-dev" , "Burr Sutter" > Sent: Thursday, July 10, 2014 4:09:24 AM > Subject: Re: [jbosstools-dev] Nice AngularJS story > > Can I run this on any project ( I assume it just generates a single file so no forge setup required?) and how do u run it ? I assume it's an additional plugin ? > > /max (sent from my phone) > > >> On 10/07/2014, at 02.18, George Gastaldi wrote: >> >> As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached >> >> Forge on!!!! :D >> >>> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >>> Reverse engineering in Forge 2 works well. >>> >>> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >>> >>> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >>> >>> https://issues.jboss.org/browse/FORGE-1929 >>> >>> Enjoy ;) >>> >>> ~Lincoln >>> >>> ----- Original Message ----- >>> From: "Fred Bricon" >>> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >>> Sent: Wednesday, July 9, 2014 9:03:49 AM >>> Subject: Nice AngularJS story >>> >>> Hi, >>> >>> my Twitter TL got me to watch this Netbeans demo of building a web app >>> with JAX-RS backend + AngularJS front-end : >>> https://www.youtube.com/watch?v=2B3qL7XtKnE >>> >>> I wonder how our tooling fares compared to this demo. My guts tells me >>> (take that with a grain of salt) that : >>> * for the back-end, we could use reverse engineering with Forge 2, >>> although I don't really know its level of maturity >>> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >>> at 2'14") >>> * we have no equivalent for seeding a stock angularjs project, AFAIK >>> (unless F2 brings someting here too, idk). We could prolly create a >>> Maven archetype containing the same thing though. >>> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >>> probably brings a stronger UX, with its navigation capabilities and its >>> inference engine >>> >>> WDYT? >>> >>> I count on Burr, to come up with a demo showcasing a similar story with >>> our stuff :-) >>> >>> Fred >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev From mistria at redhat.com Thu Jul 10 10:01:32 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 10 Jul 2014 16:01:32 +0200 Subject: [jbosstools-dev] Esprima Message-ID: <53BE9CBC.7080901@redhat.com> Hi, Here is a project that could be interesting: https://projects.eclipse.org/proposals/esprima 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/20140710/60850bd4/attachment.html From marijnh at gmail.com Thu Jul 10 10:15:32 2014 From: marijnh at gmail.com (Marijn Haverbeke) Date: Thu, 10 Jul 2014 16:15:32 +0200 Subject: [jbosstools-dev] Esprima In-Reply-To: <53BE9CBC.7080901@redhat.com> References: <53BE9CBC.7080901@redhat.com> Message-ID: We are aware of Esprima. In fact Acorn, the parser used by Tern, is compatible with Esprima. On Thu, Jul 10, 2014 at 4:01 PM, Mickael Istria wrote: > Hi, > > Here is a project that could be interesting: > https://projects.eclipse.org/proposals/esprima > > Cheers, > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > -- > You received this message because you are subscribed to the Google Groups > "tern-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to tern-dev+unsubscribe at googlegroups.com. > For more options, visit https://groups.google.com/d/optout. From angelo.zerr at gmail.com Thu Jul 10 10:34:30 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Thu, 10 Jul 2014 16:34:30 +0200 Subject: [jbosstools-dev] Esprima In-Reply-To: References: <53BE9CBC.7080901@redhat.com> Message-ID: Hi, I don't know very good esprima, but is esprima can be compared to tern (which is javascript inference engine) or just be compared to acorn? If esprima is like acorn, can we use esprima inside tern? Is it interesting (for performance for example)? > In fact Acorn, the parser used by Tern, is compatible with Esprima. It means that we could use esprima lint https://github.com/eslint/eslint ? Regard's Angelo 2014-07-10 16:15 GMT+02:00 Marijn Haverbeke : > We are aware of Esprima. In fact Acorn, the parser used by Tern, is > compatible with Esprima. > > On Thu, Jul 10, 2014 at 4:01 PM, Mickael Istria > wrote: > > Hi, > > > > Here is a project that could be interesting: > > https://projects.eclipse.org/proposals/esprima > > > > Cheers, > > -- > > Mickael Istria > > Eclipse developer at JBoss, by Red Hat > > My blog - My Tweets > > > > -- > > You received this message because you are subscribed to the Google Groups > > "tern-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to tern-dev+unsubscribe at googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "tern-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to tern-dev+unsubscribe at googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140710/ddd14edd/attachment-0001.html From marijnh at gmail.com Thu Jul 10 10:45:30 2014 From: marijnh at gmail.com (Marijn Haverbeke) Date: Thu, 10 Jul 2014 16:45:30 +0200 Subject: [jbosstools-dev] Esprima In-Reply-To: References: <53BE9CBC.7080901@redhat.com> Message-ID: Esprima is a parser. Context: http://marijnhaverbeke.nl/blog/acorn.html On Thu, Jul 10, 2014 at 4:34 PM, Angelo zerr wrote: > Hi, > > I don't know very good esprima, but is esprima can be compared to tern > (which is javascript inference engine) or just be compared to acorn? > If esprima is like acorn, can we use esprima inside tern? Is it interesting > (for performance for example)? > >> In fact Acorn, the parser used by Tern, is compatible with Esprima. > It means that we could use esprima lint https://github.com/eslint/eslint ? > > Regard's Angelo > > > 2014-07-10 16:15 GMT+02:00 Marijn Haverbeke : > >> We are aware of Esprima. In fact Acorn, the parser used by Tern, is >> compatible with Esprima. >> >> On Thu, Jul 10, 2014 at 4:01 PM, Mickael Istria >> wrote: >> > Hi, >> > >> > Here is a project that could be interesting: >> > https://projects.eclipse.org/proposals/esprima >> > >> > Cheers, >> > -- >> > Mickael Istria >> > Eclipse developer at JBoss, by Red Hat >> > My blog - My Tweets >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "tern-dev" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to tern-dev+unsubscribe at googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "tern-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to tern-dev+unsubscribe at googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > From mistria at redhat.com Thu Jul 10 10:54:51 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 10 Jul 2014 16:54:51 +0200 Subject: [jbosstools-dev] THyM in JBoss Tools, when? Message-ID: <53BEA93B.1010200@redhat.com> Hi all, hi Gorkem, Can we already get a snapshot of THyM and add it to JBoss Tools 4.40.0.CR1-SNAPSHOT target-platforms? My opinion is the sooner the better. When we have THyM in target-platform, you'll be able to start the process of trimming out the part of jbosstools-aerogear that are now at Eclipse.org. As soon as you are ready, please create the request as explained in https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#create-jira-outlining-the-request Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140710/73ec1346/attachment.html From gorkem.ercan at gmail.com Thu Jul 10 11:19:05 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Thu, 10 Jul 2014 11:19:05 -0400 Subject: [jbosstools-dev] THyM in JBoss Tools, when? In-Reply-To: <53BEA93B.1010200@redhat.com> References: <53BEA93B.1010200@redhat.com> Message-ID: We need to take care of a few things before we move on. 1. We have removed the extension point from THyM that puts hybrid mobile tools and Tern.java cordova modules together. So we need a new plugin that will provide this sort of extensions on JBT repo. 2. We need a p2.inf file so that Thym can update the JBT hybrid tools (see JBIDE-17840) 3. CordovaSim is the only customer for Thym that I am aware of. We need to be ready to quickly make the changes to namespaces, version numbers etc so that we do not break. Once I have 1 and 2 in place, we can proceed. I guess that will be early next week. A question though, Does TP restrict to a particular version of a feature? Will it receive the updates of SNAPSHOT Thym builds? -- Gorkem On Thu, Jul 10, 2014 at 10:54 AM, Mickael Istria wrote: > Hi all, hi Gorkem, > > Can we already get a snapshot of THyM and add it to JBoss Tools > 4.40.0.CR1-SNAPSHOT target-platforms? My opinion is the sooner the better. > When we have THyM in target-platform, you'll be able to start the process > of trimming out the part of jbosstools-aerogear that are now at Eclipse.org. > As soon as you are ready, please create the request as explained in > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#create-jira-outlining-the-request > > Cheers, > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140710/6f123bdf/attachment.html From nboldt at redhat.com Thu Jul 10 11:21:43 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 10 Jul 2014 11:21:43 -0400 Subject: [jbosstools-dev] THyM in JBoss Tools, when? In-Reply-To: References: <53BEA93B.1010200@redhat.com> Message-ID: <53BEAF87.2080103@redhat.com> TP is a snapshot in time. It can be updated to include NEWER upstream content, but that's an intentionally-manual process to avoid unplanned changes coming in from upstream. So... no, the TP does NOT receive *automatic* updates of upstream SNAPSHOT Thym builds. You must request updates to the TP via JIRA. On 07/10/2014 11:19 AM, Gorkem Ercan wrote: > We need to take care of a few things before we move on. > 1. We have removed the extension point from THyM that puts hybrid mobile > tools and Tern.java cordova modules together. So we need a new plugin > that will provide this sort of extensions on JBT repo. > 2. We need a p2.inf file so that Thym can update the JBT hybrid tools > (see JBIDE-17840) > 3. CordovaSim is the only customer for Thym that I am aware of. We need > to be ready to quickly make the changes to namespaces, version numbers > etc so that we do not break. > > Once I have 1 and 2 in place, we can proceed. I guess that will be early > next week. > > A question though, Does TP restrict to a particular version of a > feature? Will it receive the updates of SNAPSHOT Thym builds? > -- > Gorkem > > > On Thu, Jul 10, 2014 at 10:54 AM, Mickael Istria > wrote: > > Hi all, hi Gorkem, > > Can we already get a snapshot of THyM and add it to JBoss Tools > 4.40.0.CR1-SNAPSHOT target-platforms? My opinion is the sooner the > better. > When we have THyM in target-platform, you'll be able to start the > process of trimming out the part of jbosstools-aerogear that are now > at Eclipse.org. > As soon as you are ready, please create the request as explained in > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#create-jira-outlining-the-request > > Cheers, > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > > _______________________________________________ > 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 gorkem.ercan at gmail.com Thu Jul 10 11:23:30 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Thu, 10 Jul 2014 11:23:30 -0400 Subject: [jbosstools-dev] THyM in JBoss Tools, when? In-Reply-To: <53BEAF87.2080103@redhat.com> References: <53BEA93B.1010200@redhat.com> <53BEAF87.2080103@redhat.com> Message-ID: On Thu, Jul 10, 2014 at 11:21 AM, Nick Boldt wrote: > TP is a snapshot in time. It can be updated to include NEWER upstream > content, but that's an intentionally-manual process to avoid unplanned > changes coming in from upstream. > > So... no, the TP does NOT receive *automatic* updates of upstream SNAPSHOT > Thym builds. > > You must request updates to the TP via JIRA. Lucky me :) > > > On 07/10/2014 11:19 AM, Gorkem Ercan wrote: > >> We need to take care of a few things before we move on. >> 1. We have removed the extension point from THyM that puts hybrid mobile >> tools and Tern.java cordova modules together. So we need a new plugin >> that will provide this sort of extensions on JBT repo. >> 2. We need a p2.inf file so that Thym can update the JBT hybrid tools >> (see JBIDE-17840) >> 3. CordovaSim is the only customer for Thym that I am aware of. We need >> to be ready to quickly make the changes to namespaces, version numbers >> etc so that we do not break. >> >> Once I have 1 and 2 in place, we can proceed. I guess that will be early >> next week. >> >> A question though, Does TP restrict to a particular version of a >> feature? Will it receive the updates of SNAPSHOT Thym builds? >> -- >> Gorkem >> >> >> On Thu, Jul 10, 2014 at 10:54 AM, Mickael Istria > > wrote: >> >> Hi all, hi Gorkem, >> >> Can we already get a snapshot of THyM and add it to JBoss Tools >> 4.40.0.CR1-SNAPSHOT target-platforms? My opinion is the sooner the >> better. >> When we have THyM in target-platform, you'll be able to start the >> process of trimming out the part of jbosstools-aerogear that are now >> at Eclipse.org. >> As soon as you are ready, please create the request as explained in >> https://github.com/jbosstools/jbosstools-devdoc/blob/master/ >> building/target_platforms/target_platforms_updates.adoc# >> create-jira-outlining-the-request >> >> Cheers, >> -- >> Mickael Istria >> Eclipse developer at JBoss, by Red Hat >> My blog - My Tweets >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> >> >> >> _______________________________________________ >> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140710/4076b7d4/attachment.html From mistria at redhat.com Thu Jul 10 11:24:30 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 10 Jul 2014 17:24:30 +0200 Subject: [jbosstools-dev] THyM in JBoss Tools, when? In-Reply-To: References: <53BEA93B.1010200@redhat.com> Message-ID: <53BEB02E.5000800@redhat.com> On 07/10/2014 05:19 PM, Gorkem Ercan wrote: > A question though, Does TP restrict to a particular version of a > feature? Will it receive the updates of SNAPSHOT Thym builds? We don't allow unknown/wildcard versions of dependencies in target definition, mainly to have repeatable builds and less surprises. So you'll have to ask everytime you want a new snapshot. Updates (without new dependencies) in TP are generally taken with a high priority, and can be available within 1 or 2 hours after the change request. I hope this will be good enough for your migration. -- 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/20140710/c8f89997/attachment-0001.html From dgolovin at exadel.com Thu Jul 10 13:00:25 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Thu, 10 Jul 2014 10:00:25 -0700 Subject: [jbosstools-dev] Esprima In-Reply-To: References: <53BE9CBC.7080901@redhat.com> Message-ID: <53BEC6A9.50705@exadel.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140710/c39ff10d/attachment.html From angelo.zerr at gmail.com Thu Jul 10 14:59:30 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Thu, 10 Jul 2014 20:59:30 +0200 Subject: [jbosstools-dev] Esprima In-Reply-To: <53BEC6A9.50705@exadel.com> References: <53BE9CBC.7080901@redhat.com> <53BEC6A9.50705@exadel.com> Message-ID: 2014-07-10 19:00 GMT+02:00 Denis Golovin : > On 07/10/2014 07:34 AM, Angelo zerr wrote: > > Hi, > > I don't know very good esprima, but is esprima can be compared to tern > (which is javascript inference engine) or just be compared to acorn? > If esprima is like acorn, can we use esprima inside tern? Is it > interesting (for performance for example)? > > There is a Speed Comparison page http://esprima.org/test/compare.html > Thank's denis. With my Chrome, it seems acorn is the faster. I love so tern:) SourceEsprimaUglifyJS2TraceurAcornUnderscore 1.5.26.5 ?2.3%12.1 ?7.3%8.8 ?0.9%4.1 ?1.6%Backbone 1.1.08.1 ?2.6%18.8 ?3.5%9.8 ?1.3%4.7 ?6.2%jQuery 1.9.155.1 ?6.1%141.7 ?5.3%78.6 ?4.8%48.9 ?6.2%*Total*69.6 ms172.6 ms97.2 ms57.7 ms > > > Best > Denis > > > > In fact Acorn, the parser used by Tern, is compatible with Esprima. > It means that we could use esprima lint https://github.com/eslint/eslint > ? > > Regard's Angelo > > > 2014-07-10 16:15 GMT+02:00 Marijn Haverbeke : > >> We are aware of Esprima. In fact Acorn, the parser used by Tern, is >> compatible with Esprima. >> >> On Thu, Jul 10, 2014 at 4:01 PM, Mickael Istria >> wrote: >> > Hi, >> > >> > Here is a project that could be interesting: >> > https://projects.eclipse.org/proposals/esprima >> > >> > Cheers, >> > -- >> > Mickael Istria >> > Eclipse developer at JBoss, by Red Hat >> > My blog - My Tweets >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "tern-dev" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to tern-dev+unsubscribe at googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "tern-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to tern-dev+unsubscribe at googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > _______________________________________________ > jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140710/2a53d2d4/attachment.html From bsutter at redhat.com Thu Jul 10 16:49:13 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 10 Jul 2014 16:49:13 -0400 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <2030260603.1380236.1404962337366.JavaMail.zimbra@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <2030260603.1380236.1404962337366.JavaMail.zimbra@redhat.com> Message-ID: <0AE371FA-F018-4D9B-982F-D11B765AE3EC@redhat.com> Impressive response to Fred's request. And Fred, thank you very much for pushing this use case - it is critical! Now, if only that Angular app was mobile-friendly so we could drop it into a Hybrid Mobile/Cordova project easily - that would be the maximum win. :-) On Jul 9, 2014, at 11:18 PM, Lincoln Baxter wrote: > George, you are awesome. And so is Forge, that took what, 10 minutes for you to put together? :) > > ~Lincoln > > ----- Original Message ----- > From: "George Gastaldi" > To: "Lincoln Baxter" , "Fred Bricon" > Cc: "??? jbosstools-dev" , "Vineet Reynolds Pereira" , "Burr Sutter" > Sent: Wednesday, July 9, 2014 8:17:53 PM > Subject: Re: Nice AngularJS story > > As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing > Filter command (and with tests - :)). Screenshot attached > > Forge on!!!! :D > > On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >> Reverse engineering in Forge 2 works well. >> >> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >> >> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >> >> https://issues.jboss.org/browse/FORGE-1929 >> >> Enjoy ;) >> >> ~Lincoln >> >> ----- Original Message ----- >> From: "Fred Bricon" >> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >> Sent: Wednesday, July 9, 2014 9:03:49 AM >> Subject: Nice AngularJS story >> >> Hi, >> >> my Twitter TL got me to watch this Netbeans demo of building a web app >> with JAX-RS backend + AngularJS front-end : >> https://www.youtube.com/watch?v=2B3qL7XtKnE >> >> I wonder how our tooling fares compared to this demo. My guts tells me >> (take that with a grain of salt) that : >> * for the back-end, we could use reverse engineering with Forge 2, >> although I don't really know its level of maturity >> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >> at 2'14") >> * we have no equivalent for seeding a stock angularjs project, AFAIK >> (unless F2 brings someting here too, idk). We could prolly create a >> Maven archetype containing the same thing though. >> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >> probably brings a stronger UX, with its navigation capabilities and its >> inference engine >> >> WDYT? >> >> I count on Burr, to come up with a demo showcasing a similar story with >> our stuff :-) >> >> Fred > From bsutter at redhat.com Thu Jul 10 16:47:45 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 10 Jul 2014 16:47:45 -0400 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> Message-ID: <24365F17-BF7B-45E5-89DB-BD81BDC6467F@redhat.com> Outstanding demo! On Jul 9, 2014, at 5:34 PM, Lincoln Baxter wrote: > Reverse engineering in Forge 2 works well. > > I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be > > Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: > > https://issues.jboss.org/browse/FORGE-1929 > > Enjoy ;) > > ~Lincoln > > ----- Original Message ----- > From: "Fred Bricon" > To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" > Sent: Wednesday, July 9, 2014 9:03:49 AM > Subject: Nice AngularJS story > > Hi, > > my Twitter TL got me to watch this Netbeans demo of building a web app > with JAX-RS backend + AngularJS front-end : > https://www.youtube.com/watch?v=2B3qL7XtKnE > > I wonder how our tooling fares compared to this demo. My guts tells me > (take that with a grain of salt) that : > * for the back-end, we could use reverse engineering with Forge 2, > although I don't really know its level of maturity > * we have nothing similar to the CrossOriginResourceSharingFilter (seen > at 2'14") > * we have no equivalent for seeding a stock angularjs project, AFAIK > (unless F2 brings someting here too, idk). We could prolly create a > Maven archetype containing the same thing though. > * overall their angularjs tooling felt underwhelming. angularjs-eclipse > probably brings a stronger UX, with its navigation capabilities and its > inference engine > > WDYT? > > I count on Burr, to come up with a demo showcasing a similar story with > our stuff :-) > > Fred From manderse at redhat.com Fri Jul 11 05:53:20 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Jul 2014 11:53:20 +0200 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <24365F17-BF7B-45E5-89DB-BD81BDC6467F@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <24365F17-BF7B-45E5-89DB-BD81BDC6467F@redhat.com> Message-ID: <1D234A1B-0BAC-4826-A1D3-01BF9C20B277@redhat.com> On 10 Jul 2014, at 22:47, Burr Sutter wrote: > Outstanding demo! definitely - now just need to actually have jbosstools installed with its html preview and angularjs tooling so the full story can be covered. /max > > > On Jul 9, 2014, at 5:34 PM, Lincoln Baxter wrote: > >> Reverse engineering in Forge 2 works well. >> >> I just made this video for you - >> https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >> >> Regarding CrossOriginResourceSharingFilter, it's simple enough to add >> a command in Forge to create one: >> >> https://issues.jboss.org/browse/FORGE-1929 >> >> Enjoy ;) >> >> ~Lincoln >> >> ----- Original Message ----- >> From: "Fred Bricon" >> To: "??? jbosstools-dev" , "Lincoln >> Baxter" , "George Gastaldi" >> , "Vineet Reynolds Pereira" >> >> Sent: Wednesday, July 9, 2014 9:03:49 AM >> Subject: Nice AngularJS story >> >> Hi, >> >> my Twitter TL got me to watch this Netbeans demo of building a web >> app >> with JAX-RS backend + AngularJS front-end : >> https://www.youtube.com/watch?v=2B3qL7XtKnE >> >> I wonder how our tooling fares compared to this demo. My guts tells >> me >> (take that with a grain of salt) that : >> * for the back-end, we could use reverse engineering with Forge 2, >> although I don't really know its level of maturity >> * we have nothing similar to the CrossOriginResourceSharingFilter >> (seen >> at 2'14") >> * we have no equivalent for seeding a stock angularjs project, AFAIK >> (unless F2 brings someting here too, idk). We could prolly create a >> Maven archetype containing the same thing though. >> * overall their angularjs tooling felt underwhelming. >> angularjs-eclipse >> probably brings a stronger UX, with its navigation capabilities and >> its >> inference engine >> >> WDYT? >> >> I count on Burr, to come up with a demo showcasing a similar story >> with >> our stuff :-) >> >> Fred > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Fri Jul 11 06:07:58 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Jul 2014 12:07:58 +0200 Subject: [jbosstools-dev] Esprima In-Reply-To: References: <53BE9CBC.7080901@redhat.com> <53BEC6A9.50705@exadel.com> Message-ID: On 10 Jul 2014, at 20:59, Angelo zerr wrote: > 2014-07-10 19:00 GMT+02:00 Denis Golovin : > >> On 07/10/2014 07:34 AM, Angelo zerr wrote: >> >> Hi, >> >> I don't know very good esprima, but is esprima can be compared to >> tern >> (which is javascript inference engine) or just be compared to acorn? >> If esprima is like acorn, can we use esprima inside tern? Is it >> interesting (for performance for example)? >> >> There is a Speed Comparison page http://esprima.org/test/compare.html >> > > Thank's denis. With my Chrome, it seems acorn is the faster. I love so > tern:) the challenge with Tern vs Esprima is that one is now EPL and used in Orion and thus could be used as extension in/to Eclipse JSDT - the other is neither. Is there anything stopping us from using epsrima as alternative to tern as basis of eclipse javascript tooling ? With that we could to cross development on both the web and desktop based IDE's at eclipse? /max http://about.me/maxandersen From manderse at redhat.com Fri Jul 11 06:09:39 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Jul 2014 12:09:39 +0200 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <1079213405.1868026.1404999732065.JavaMail.zimbra@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> <1079213405.1868026.1404999732065.JavaMail.zimbra@redhat.com> Message-ID: <6BE15865-267E-4D33-BA10-0F14B8B554DB@redhat.com> On 10 Jul 2014, at 15:42, Lincoln Baxter wrote: > That is correct. It will generate a Servlet filter into any existing > project. But if JAX-RS/Servlet is not setup yet, it will handle that > for you. you guys keep ignoring my question: *How* do I run it ? :) (especially when i'm on beta3 of tools) /max > ----- Original Message ----- > From: "Max Rydahl Andersen" > To: "George Gastaldi" > Cc: "Lincoln Baxter" , "Fred Bricon" > , "Vineet Reynolds Pereira" , > "??? jbosstools-dev" , "Burr Sutter" > > Sent: Thursday, July 10, 2014 4:09:24 AM > Subject: Re: [jbosstools-dev] Nice AngularJS story > > Can I run this on any project ( I assume it just generates a single > file so no forge setup required?) and how do u run it ? I assume it's > an additional plugin ? > > /max (sent from my phone) > > >> On 10/07/2014, at 02.18, George Gastaldi wrote: >> >> As of right now, Forge 2 has a REST: New Cross Origin Resource >> Sharing Filter command (and with tests - :)). Screenshot attached >> >> Forge on!!!! :D >> >>> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >>> Reverse engineering in Forge 2 works well. >>> >>> I just made this video for you - >>> https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >>> >>> Regarding CrossOriginResourceSharingFilter, it's simple enough to >>> add a command in Forge to create one: >>> >>> https://issues.jboss.org/browse/FORGE-1929 >>> >>> Enjoy ;) >>> >>> ~Lincoln >>> >>> ----- Original Message ----- >>> From: "Fred Bricon" >>> To: "??? jbosstools-dev" , "Lincoln >>> Baxter" , "George Gastaldi" >>> , "Vineet Reynolds Pereira" >>> >>> Sent: Wednesday, July 9, 2014 9:03:49 AM >>> Subject: Nice AngularJS story >>> >>> Hi, >>> >>> my Twitter TL got me to watch this Netbeans demo of building a web >>> app >>> with JAX-RS backend + AngularJS front-end : >>> https://www.youtube.com/watch?v=2B3qL7XtKnE >>> >>> I wonder how our tooling fares compared to this demo. My guts tells >>> me >>> (take that with a grain of salt) that : >>> * for the back-end, we could use reverse engineering with Forge 2, >>> although I don't really know its level of maturity >>> * we have nothing similar to the CrossOriginResourceSharingFilter >>> (seen >>> at 2'14") >>> * we have no equivalent for seeding a stock angularjs project, AFAIK >>> (unless F2 brings someting here too, idk). We could prolly create a >>> Maven archetype containing the same thing though. >>> * overall their angularjs tooling felt underwhelming. >>> angularjs-eclipse >>> probably brings a stronger UX, with its navigation capabilities and >>> its >>> inference engine >>> >>> WDYT? >>> >>> I count on Burr, to come up with a demo showcasing a similar story >>> with >>> our stuff :-) >>> >>> Fred >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From mistria at redhat.com Fri Jul 11 06:12:32 2014 From: mistria at redhat.com (Mickael Istria) Date: Fri, 11 Jul 2014 12:12:32 +0200 Subject: [jbosstools-dev] My super cool Eclipse extensions Message-ID: <53BFB890.6010500@redhat.com> Hi all, I'd like to share with you a few Eclipse extensions I've developed and I've been happily using for some time already. Maybe you'll like them. They could be integrated in JBoss Tools if you think they make sense. I let you try and give feedback: https://github.com/mickaelistria/jbosstools-eclipse 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/20140711/29c59792/attachment.html From marijnh at gmail.com Fri Jul 11 06:16:41 2014 From: marijnh at gmail.com (Marijn Haverbeke) Date: Fri, 11 Jul 2014 12:16:41 +0200 Subject: [jbosstools-dev] Esprima In-Reply-To: References: <53BE9CBC.7080901@redhat.com> <53BEC6A9.50705@exadel.com> Message-ID: > the challenge with Tern vs Esprima is that one is now EPL and used in Orion > and thus could be used as extension in/to Eclipse JSDT - the other is > neither. Tern and Acorn are MIT licensed, which should be compatibly with just about anything, including EPL. See https://www.eclipse.org/legal/eplfaq.php: ---- The current list of licenses approved for use by third-party code redistributed by Eclipse projects is: Apache Software License 1.1 Apache Software License 2.0 W3C Software License Common Public License Version 1.0 IBM Public License 1.0 Mozilla Public License Version 1.1 Common Development and Distribution License (CDDL) Version 1.0 GNU Free Documentation License Version 1.3 BSD MIT ---- From manderse at redhat.com Fri Jul 11 06:44:52 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Jul 2014 12:44:52 +0200 Subject: [jbosstools-dev] My super cool Eclipse extensions In-Reply-To: <53BFB890.6010500@redhat.com> References: <53BFB890.6010500@redhat.com> Message-ID: <51EB5449-2292-4C4B-A67C-8F8924E9DDA4@redhat.com> On 11 Jul 2014, at 12:12, Mickael Istria wrote: > Hi all, > > I'd like to share with you a few Eclipse extensions I've developed and > I've been happily using for some time already. Maybe you'll like them. > They could be integrated in JBoss Tools if you think they make sense. these features were all part of this years release "if we can find time"-bucket so yes for sure its interesting. > I let you try and give feedback: > https://github.com/mickaelistria/jbosstools-eclipse Can you do a quick video of them or at least explain how to install these (or do I need to build them first?) and how to invoke these features? asking since I tried but they didn't "just work" /max http://about.me/maxandersen From manderse at redhat.com Fri Jul 11 06:57:51 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Jul 2014 12:57:51 +0200 Subject: [jbosstools-dev] Esprima In-Reply-To: References: <53BE9CBC.7080901@redhat.com> <53BEC6A9.50705@exadel.com> Message-ID: On 11 Jul 2014, at 12:16, Marijn Haverbeke wrote: >> the challenge with Tern vs Esprima is that one is now EPL and used in >> Orion >> and thus could be used as extension in/to Eclipse JSDT - the other is >> neither. > > Tern and Acorn are MIT licensed, which should be compatibly with just > about anything, including EPL. See > https://www.eclipse.org/legal/eplfaq.php: this does not matter for Eclipse projects - what matters first is that the IP log is clean. The if the license is *not* EPL it needs to get specific approval to be included. If we can get these IP cleared then yes, this could be used - but I wonder why IBM/orion group didn't just use tern. They told me "because its not IP cleared"... In any case - having two different javascript parser for the exact same thing in eclipse tooling could be annoying over time. Thus i'm considering what options do we have for this ? /max http://about.me/maxandersen From marijnh at gmail.com Fri Jul 11 07:00:45 2014 From: marijnh at gmail.com (Marijn Haverbeke) Date: Fri, 11 Jul 2014 13:00:45 +0200 Subject: [jbosstools-dev] Esprima In-Reply-To: References: <53BE9CBC.7080901@redhat.com> <53BEC6A9.50705@exadel.com> Message-ID: Tern and Acorn don't assign IP to a single entity, so yes, I guess that means 'not IP cleared' in IBM's view. From p.g.richardson at phantomjinx.co.uk Fri Jul 11 08:03:37 2014 From: p.g.richardson at phantomjinx.co.uk (phantomjinx) Date: Fri, 11 Jul 2014 13:03:37 +0100 Subject: [jbosstools-dev] My super cool Eclipse extensions In-Reply-To: <53BFB890.6010500@redhat.com> References: <53BFB890.6010500@redhat.com> Message-ID: <53BFD299.5040801@phantomjinx.co.uk> On 07/11/2014 11:12 AM, Mickael Istria wrote: > Hi all, > > I'd like to share with you a few Eclipse extensions I've developed and I've been happily using for > some time already. Maybe you'll like them. > They could be integrated in JBoss Tools if you think they make sense. > > I let you try and give feedback: https://github.com/mickaelistria/jbosstools-eclipse > > Cheers, > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > You showed me yours, now I'll show you mine ;-) https://github.com/phantomjinx/eclipse-plugin s Makes life just a little easier. PGR -- Paul Richardson * p.g.richardson at phantomjinx.co.uk * p.g.richardson at redhat.com * pgrichardson at linux.com "I know exactly who reads the papers ... * The Daily Mirror is read by people who think they run the country. * The Guardian is read by people who think they ought to run the country. * The Times is read by people who do actually run the country. * The Daily Mail is read by the wives of the people who run the country. * The Financial Times is read by the people who own the country. * The Morning Star is read by the people who think the country ought to be run by another country. * The Daily Telegraph is read by the people who think it is." Jim Hacker, Yes Minister From manderse at redhat.com Fri Jul 11 09:17:13 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Jul 2014 15:17:13 +0200 Subject: [jbosstools-dev] First Steps for JBT Contributors In-Reply-To: <53BBF1BB.8070801@redhat.com> References: <53BBF1BB.8070801@redhat.com> Message-ID: <96A05422-CE63-4E9A-A67C-9C55AC180521@redhat.com> On 8 Jul 2014, at 15:27, Peter Palaga wrote: > Hi *, > > With a little help from my Friends Fred and Mickael, I have just set > up > the development environment. Mickael asked me to post this here, to > make > it more visible. > > The good news is that there already is a Development Environment > chapter > in devdoc [1] which covers the topic fairly well. Nothing comes to my > mind that would be missing there. > > The bad news is that I have not found it when I was needing it. > Googling > for "jboss tools environment" [2] does not return it on the first > page. > Besides that, there is a couple of "Contribute" links in the footer of > http://tools.jboss.org/ but this important document is not linked > there. > A "Contributor's first steps" link refering to [1] could perhaps be > added there. > The "Write Code" link pointing to > https://github.com/jbosstools/jbosstools-devdoc/ sounds a little bit > misleading to me. "Get the Code" or perhaps "Checkout the Code" would > describe better where it leads. > > [1] > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/development_environment.md > [2] https://www.google.com/?gws_rd=ssl#q=jboss+tools+environment > thanks for the feedback - I do agree as we have grown to have many multiple repositories instead of "just one" our guides for how to checkout and build have gotten weak in comparison. What I would like to see is that jbosstools-devdoc gets a better index page, better content and that we start linking to that from the various relevant places (to get it show up in google searches). If you have ideas/suggestions to that and time before me, the simplest is to do a PR against devdoc and I will happily merge them in. /max http://about.me/maxandersen From ggastald at redhat.com Fri Jul 11 10:18:34 2014 From: ggastald at redhat.com (George Gastaldi) Date: Fri, 11 Jul 2014 10:18:34 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <6BE15865-267E-4D33-BA10-0F14B8B554DB@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> <1079213405.1868026.1404999732065.JavaMail.zimbra@redhat.com> <6BE15865-267E-4D33-BA10-0F14B8B554DB@redhat.com> Message-ID: <34E23BD1-31C8-44AE-8F39-DE2E96292F64@redhat.com> Hi Max, I replied it yesterday: It's on the latest snapshot in JBT using Forge 2.7.1-SNAPSHOT Since JBT Beta3 is frozen, we cannot add Forge 2.7.1.Final (not yet released). You run it as any other Forge command: Ctrl (or Cmd) +4 and choose "REST: New Cross Origin Resource Sharing Filter" and it should present the wizard to set it up. Hope that answers your question :) George > Em 11/07/2014, ?s 07:09, "Max Rydahl Andersen" escreveu: > >> On 10 Jul 2014, at 15:42, Lincoln Baxter wrote: >> >> That is correct. It will generate a Servlet filter into any existing project. But if JAX-RS/Servlet is not setup yet, it will handle that for you. > > you guys keep ignoring my question: *How* do I run it ? :) (especially when i'm on beta3 of tools) > > /max > >> ----- Original Message ----- >> From: "Max Rydahl Andersen" >> To: "George Gastaldi" >> Cc: "Lincoln Baxter" , "Fred Bricon" , "Vineet Reynolds Pereira" , "??? jbosstools-dev" , "Burr Sutter" >> Sent: Thursday, July 10, 2014 4:09:24 AM >> Subject: Re: [jbosstools-dev] Nice AngularJS story >> >> Can I run this on any project ( I assume it just generates a single file so no forge setup required?) and how do u run it ? I assume it's an additional plugin ? >> >> /max (sent from my phone) >> >> >>> On 10/07/2014, at 02.18, George Gastaldi wrote: >>> >>> As of right now, Forge 2 has a REST: New Cross Origin Resource Sharing Filter command (and with tests - :)). Screenshot attached >>> >>> Forge on!!!! :D >>> >>>> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >>>> Reverse engineering in Forge 2 works well. >>>> >>>> I just made this video for you - https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >>>> >>>> Regarding CrossOriginResourceSharingFilter, it's simple enough to add a command in Forge to create one: >>>> >>>> https://issues.jboss.org/browse/FORGE-1929 >>>> >>>> Enjoy ;) >>>> >>>> ~Lincoln >>>> >>>> ----- Original Message ----- >>>> From: "Fred Bricon" >>>> To: "??? jbosstools-dev" , "Lincoln Baxter" , "George Gastaldi" , "Vineet Reynolds Pereira" >>>> Sent: Wednesday, July 9, 2014 9:03:49 AM >>>> Subject: Nice AngularJS story >>>> >>>> Hi, >>>> >>>> my Twitter TL got me to watch this Netbeans demo of building a web app >>>> with JAX-RS backend + AngularJS front-end : >>>> https://www.youtube.com/watch?v=2B3qL7XtKnE >>>> >>>> I wonder how our tooling fares compared to this demo. My guts tells me >>>> (take that with a grain of salt) that : >>>> * for the back-end, we could use reverse engineering with Forge 2, >>>> although I don't really know its level of maturity >>>> * we have nothing similar to the CrossOriginResourceSharingFilter (seen >>>> at 2'14") >>>> * we have no equivalent for seeding a stock angularjs project, AFAIK >>>> (unless F2 brings someting here too, idk). We could prolly create a >>>> Maven archetype containing the same thing though. >>>> * overall their angularjs tooling felt underwhelming. angularjs-eclipse >>>> probably brings a stronger UX, with its navigation capabilities and its >>>> inference engine >>>> >>>> WDYT? >>>> >>>> I count on Burr, to come up with a demo showcasing a similar story with >>>> our stuff :-) >>>> >>>> Fred >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen From mistria at redhat.com Fri Jul 11 10:45:23 2014 From: mistria at redhat.com (Mickael Istria) Date: Fri, 11 Jul 2014 16:45:23 +0200 Subject: [jbosstools-dev] My super cool Eclipse extensions In-Reply-To: <51EB5449-2292-4C4B-A67C-8F8924E9DDA4@redhat.com> References: <53BFB890.6010500@redhat.com> <51EB5449-2292-4C4B-A67C-8F8924E9DDA4@redhat.com> Message-ID: <53BFF883.2050302@redhat.com> On 07/11/2014 12:44 PM, Max Rydahl Andersen wrote: >> I let you try and give feedback: >> https://github.com/mickaelistria/jbosstools-eclipse > > Can you do a quick video of them or at least explain how to install > these (or do I need to build them first?) and how to invoke these > features? Yes, you need to build the stuff. I'll try to make a site available later and to put at least some screenshots on the README.md to show usage. -- 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/20140711/c39423c5/attachment.html From manderse at redhat.com Fri Jul 11 10:52:14 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Jul 2014 16:52:14 +0200 Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: <34E23BD1-31C8-44AE-8F39-DE2E96292F64@redhat.com> References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> <1079213405.1868026.1404999732065.JavaMail.zimbra@redhat.com> <6BE15865-267E-4D33-BA10-0F14B8B554DB@redhat.com> <34E23BD1-31C8-44AE-8F39-DE2E96292F64@redhat.com> Message-ID: On 11 Jul 2014, at 16:18, George Gastaldi wrote: > Hi Max, I replied it yesterday: > > It's on the latest snapshot in JBT using Forge 2.7.1-SNAPSHOT yes, but I thought we had a way to update forge for testing purposes ;) > Since JBT Beta3 is frozen, we cannot add Forge 2.7.1.Final (not yet > released). You run it as any other Forge command: Ctrl (or Cmd) +4 and > choose "REST: New Cross Origin Resource Sharing Filter" and it should > present the wizard to set it up. okey cool. > Hope that answers your question :) yes, thanks! > George > >> Em 11/07/2014, ?s 07:09, "Max Rydahl Andersen" >> escreveu: >> >>> On 10 Jul 2014, at 15:42, Lincoln Baxter wrote: >>> >>> That is correct. It will generate a Servlet filter into any existing >>> project. But if JAX-RS/Servlet is not setup yet, it will handle that >>> for you. >> >> you guys keep ignoring my question: *How* do I run it ? :) >> (especially when i'm on beta3 of tools) >> >> /max >> >>> ----- Original Message ----- >>> From: "Max Rydahl Andersen" >>> To: "George Gastaldi" >>> Cc: "Lincoln Baxter" , "Fred Bricon" >>> , "Vineet Reynolds Pereira" >>> , "??? jbosstools-dev" >>> , "Burr Sutter" >>> Sent: Thursday, July 10, 2014 4:09:24 AM >>> Subject: Re: [jbosstools-dev] Nice AngularJS story >>> >>> Can I run this on any project ( I assume it just generates a single >>> file so no forge setup required?) and how do u run it ? I assume >>> it's an additional plugin ? >>> >>> /max (sent from my phone) >>> >>> >>>> On 10/07/2014, at 02.18, George Gastaldi >>>> wrote: >>>> >>>> As of right now, Forge 2 has a REST: New Cross Origin Resource >>>> Sharing Filter command (and with tests - :)). Screenshot attached >>>> >>>> Forge on!!!! :D >>>> >>>>> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >>>>> Reverse engineering in Forge 2 works well. >>>>> >>>>> I just made this video for you - >>>>> https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >>>>> >>>>> Regarding CrossOriginResourceSharingFilter, it's simple enough to >>>>> add a command in Forge to create one: >>>>> >>>>> https://issues.jboss.org/browse/FORGE-1929 >>>>> >>>>> Enjoy ;) >>>>> >>>>> ~Lincoln >>>>> >>>>> ----- Original Message ----- >>>>> From: "Fred Bricon" >>>>> To: "??? jbosstools-dev" , >>>>> "Lincoln Baxter" , "George Gastaldi" >>>>> , "Vineet Reynolds Pereira" >>>>> >>>>> Sent: Wednesday, July 9, 2014 9:03:49 AM >>>>> Subject: Nice AngularJS story >>>>> >>>>> Hi, >>>>> >>>>> my Twitter TL got me to watch this Netbeans demo of building a web >>>>> app >>>>> with JAX-RS backend + AngularJS front-end : >>>>> https://www.youtube.com/watch?v=2B3qL7XtKnE >>>>> >>>>> I wonder how our tooling fares compared to this demo. My guts >>>>> tells me >>>>> (take that with a grain of salt) that : >>>>> * for the back-end, we could use reverse engineering with Forge 2, >>>>> although I don't really know its level of maturity >>>>> * we have nothing similar to the CrossOriginResourceSharingFilter >>>>> (seen >>>>> at 2'14") >>>>> * we have no equivalent for seeding a stock angularjs project, >>>>> AFAIK >>>>> (unless F2 brings someting here too, idk). We could prolly create >>>>> a >>>>> Maven archetype containing the same thing though. >>>>> * overall their angularjs tooling felt underwhelming. >>>>> angularjs-eclipse >>>>> probably brings a stronger UX, with its navigation capabilities >>>>> and its >>>>> inference engine >>>>> >>>>> WDYT? >>>>> >>>>> I count on Burr, to come up with a demo showcasing a similar story >>>>> with >>>>> our stuff :-) >>>>> >>>>> Fred >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> /max >> http://about.me/maxandersen /max http://about.me/maxandersen From lbaxter at redhat.com Fri Jul 11 10:57:48 2014 From: lbaxter at redhat.com (Lincoln Baxter) Date: Fri, 11 Jul 2014 10:57:48 -0400 (EDT) Subject: [jbosstools-dev] Nice AngularJS story In-Reply-To: References: <53BD3DB5.4080508@redhat.com> <139797048.1285503.1404941688111.JavaMail.zimbra@redhat.com> <53BDDBB1.2080500@redhat.com> <544FF9CD-BEE7-46A5-9553-ADB67FE606E1@redhat.com> <1079213405.1868026.1404999732065.JavaMail.zimbra@redhat.com> <6BE15865-267E-4D33-BA10-0F14B8B554DB@redhat.com> <34E23BD1-31C8-44AE-8F39-DE2E96292F64@redhat.com> Message-ID: <1411104256.3930039.1405090668723.JavaMail.zimbra@redhat.com> If you feel like it. Just open Forge in JBDS, open the Forge Console and run this: addon-install-from-git --url https://github.com/forge/core.git --coordinate org.jboss.forge.addon:javaee ----- Original Message ----- From: "Max Rydahl Andersen" To: "George Gastaldi" Cc: "Lincoln Baxter" , "Fred Bricon" , "Vineet Reynolds Pereira" , "??? jbosstools-dev" , "Burr Sutter" Sent: Friday, July 11, 2014 10:52:14 AM Subject: Re: [jbosstools-dev] Nice AngularJS story On 11 Jul 2014, at 16:18, George Gastaldi wrote: > Hi Max, I replied it yesterday: > > It's on the latest snapshot in JBT using Forge 2.7.1-SNAPSHOT yes, but I thought we had a way to update forge for testing purposes ;) > Since JBT Beta3 is frozen, we cannot add Forge 2.7.1.Final (not yet > released). You run it as any other Forge command: Ctrl (or Cmd) +4 and > choose "REST: New Cross Origin Resource Sharing Filter" and it should > present the wizard to set it up. okey cool. > Hope that answers your question :) yes, thanks! > George > >> Em 11/07/2014, ?s 07:09, "Max Rydahl Andersen" >> escreveu: >> >>> On 10 Jul 2014, at 15:42, Lincoln Baxter wrote: >>> >>> That is correct. It will generate a Servlet filter into any existing >>> project. But if JAX-RS/Servlet is not setup yet, it will handle that >>> for you. >> >> you guys keep ignoring my question: *How* do I run it ? :) >> (especially when i'm on beta3 of tools) >> >> /max >> >>> ----- Original Message ----- >>> From: "Max Rydahl Andersen" >>> To: "George Gastaldi" >>> Cc: "Lincoln Baxter" , "Fred Bricon" >>> , "Vineet Reynolds Pereira" >>> , "??? jbosstools-dev" >>> , "Burr Sutter" >>> Sent: Thursday, July 10, 2014 4:09:24 AM >>> Subject: Re: [jbosstools-dev] Nice AngularJS story >>> >>> Can I run this on any project ( I assume it just generates a single >>> file so no forge setup required?) and how do u run it ? I assume >>> it's an additional plugin ? >>> >>> /max (sent from my phone) >>> >>> >>>> On 10/07/2014, at 02.18, George Gastaldi >>>> wrote: >>>> >>>> As of right now, Forge 2 has a REST: New Cross Origin Resource >>>> Sharing Filter command (and with tests - :)). Screenshot attached >>>> >>>> Forge on!!!! :D >>>> >>>>> On 07/09/2014 06:34 PM, Lincoln Baxter wrote: >>>>> Reverse engineering in Forge 2 works well. >>>>> >>>>> I just made this video for you - >>>>> https://www.youtube.com/watch?v=mg8Z7qHzpBA&feature=youtu.be >>>>> >>>>> Regarding CrossOriginResourceSharingFilter, it's simple enough to >>>>> add a command in Forge to create one: >>>>> >>>>> https://issues.jboss.org/browse/FORGE-1929 >>>>> >>>>> Enjoy ;) >>>>> >>>>> ~Lincoln >>>>> >>>>> ----- Original Message ----- >>>>> From: "Fred Bricon" >>>>> To: "??? jbosstools-dev" , >>>>> "Lincoln Baxter" , "George Gastaldi" >>>>> , "Vineet Reynolds Pereira" >>>>> >>>>> Sent: Wednesday, July 9, 2014 9:03:49 AM >>>>> Subject: Nice AngularJS story >>>>> >>>>> Hi, >>>>> >>>>> my Twitter TL got me to watch this Netbeans demo of building a web >>>>> app >>>>> with JAX-RS backend + AngularJS front-end : >>>>> https://www.youtube.com/watch?v=2B3qL7XtKnE >>>>> >>>>> I wonder how our tooling fares compared to this demo. My guts >>>>> tells me >>>>> (take that with a grain of salt) that : >>>>> * for the back-end, we could use reverse engineering with Forge 2, >>>>> although I don't really know its level of maturity >>>>> * we have nothing similar to the CrossOriginResourceSharingFilter >>>>> (seen >>>>> at 2'14") >>>>> * we have no equivalent for seeding a stock angularjs project, >>>>> AFAIK >>>>> (unless F2 brings someting here too, idk). We could prolly create >>>>> a >>>>> Maven archetype containing the same thing though. >>>>> * overall their angularjs tooling felt underwhelming. >>>>> angularjs-eclipse >>>>> probably brings a stronger UX, with its navigation capabilities >>>>> and its >>>>> inference engine >>>>> >>>>> WDYT? >>>>> >>>>> I count on Burr, to come up with a demo showcasing a similar story >>>>> with >>>>> our stuff :-) >>>>> >>>>> Fred >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> /max >> http://about.me/maxandersen /max http://about.me/maxandersen From mistria at redhat.com Fri Jul 11 11:30:38 2014 From: mistria at redhat.com (Mickael Istria) Date: Fri, 11 Jul 2014 17:30:38 +0200 Subject: [jbosstools-dev] My super cool Eclipse extensions In-Reply-To: <51EB5449-2292-4C4B-A67C-8F8924E9DDA4@redhat.com> References: <53BFB890.6010500@redhat.com> <51EB5449-2292-4C4B-A67C-8F8924E9DDA4@redhat.com> Message-ID: <53C0031E.9010100@redhat.com> I made a snapshot available at http://mickaelistria.github.io/jbosstools-eclipse/repository/target/repository/ and README.md links to it. -- 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/20140711/c495b3ce/attachment-0001.html From nboldt at redhat.com Fri Jul 11 15:35:22 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 11 Jul 2014 15:35:22 -0400 Subject: [jbosstools-dev] Beta3 Respin-a status #2: Base, Server, WS, Central, Openshift, VPE, JavaEE, JST, Forge, Hibernate, Discovery are being rebuilt this weekend Message-ID: <53C03C7A.3060602@redhat.com> To avoid unnecessary rebuilds between Beta3 and its respin(s) (and make it easier to diff the changes between builds), I have disabled all jobs until we need them. According to this query [1] the only jobs that need to be enabled are: * Base * Server * Webservices * Central * VPE * Openshift * JavaEE Additionally, these jobs have been re-enabled to collect &/or verify the above changes, or to automatically fire should any of the 9 unresolved JIRAs [1] be fixed before Sunday night: * JST * Forge * Hibernate * Central Discovery * JBoss Tools composite install test * JBoss Tools aggregate update sites (4 jobs) * JBDS installer * JBDS versionwatch * p2 director install test * install grinder install test The following jobs are *STILL DISABLED*. If you require a fresh build to be included in respin-a, please make sure you re-enable your job & kick it off yourself. * Aerogear * BIRT * Browsersim * Freemarker * Livereload * Portlet If you push in a fix for your Beta3x branch, please remember to enable and kick your job. This will guarantee that your code change will be built and aggregated into JBT & JBDS correctly. [1] https://issues.jboss.org/issues/?jql=project%20in%20%28JBIDE%2C%20JBDS%29%20AND%20fixVersion%20in%20%284.2.0.Beta3%2C%208.0.0.Beta3%29%20AND%20labels%20in%20%28respin-a%29%20ORDER%20BY%20resolution%20ASC%2C%20component -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Fri Jul 11 17:15:29 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 11 Jul 2014 17:15:29 -0400 (EDT) Subject: [jbosstools-dev] Perceived performance :/ Message-ID: <79EEF9B9-51AD-427A-9CC0-EF2AC1D1FC54@redhat.com> Seeing this is not great. https://twitter.com/dashorst/status/487607610695483392 I've asked for details to know what are the specifics. But it's worrisome. Please make sure when you test your stuff you do it together with the full toolset and not just your one plugin loaded. Let's make sure we test this as users and not just as individual plugin developers. That's the only way we can spot performance issues caused by the combination. /max (sent from my phone) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140711/1f8ef4b5/attachment.html From mmurray at redhat.com Tue Jul 15 02:49:31 2014 From: mmurray at redhat.com (Michelle Murray) Date: Tue, 15 Jul 2014 02:49:31 -0400 (EDT) Subject: [jbosstools-dev] Action required: N&N for Beta3 In-Reply-To: <715317795.4903011.1404710170939.JavaMail.zimbra@redhat.com> References: <1428810167.4902975.1404710138352.JavaMail.zimbra@redhat.com> <715317795.4903011.1404710170939.JavaMail.zimbra@redhat.com> Message-ID: <1536386389.10061719.1405406971017.JavaMail.zimbra@redhat.com> Hello, https://issues.jboss.org/browse/JBIDE-17775 Still waiting on PRs to be made or jiras to be closed for: * Hibernate Tools * Forge Tools * Server Tools Please complete asap. Thanks, Michelle ----- Original Message ----- From: "Michelle Murray" To: "jbosstools-dev jbosstools-dev" Sent: Monday, 7 July, 2014 3:16:10 PM Subject: [jbosstools-dev] Action required: N&N for Beta3 Hello, It's that time again! Please complete N&N for Beta3 by EOW (Fri 11-Jul). https://issues.jboss.org/browse/JBIDE-17775 Thanks to those who have already completed jiras for their components. Thanks, Michelle _______________________________________________ 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/20140715/228ebff9/attachment.html From nboldt at redhat.com Mon Jul 14 00:38:20 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 14 Jul 2014 00:38:20 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta3a bits available for QE testing Message-ID: <53C35EBC.3030508@redhat.com> As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Update Sites: * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3a-updatesite-core/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3a-updatesite-coretests/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3a-updatesite-hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3a-updatesite-webtools/ Builds: * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3a-build-core/2014-07-11_21-41-17-B184 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3a-build-coretests/2014-07-11_21-41-16-B170 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3a-build-hibernatetools/2014-07-11_21-58-09-B124 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3a-build-webtools/2014-07-11_21-58-09-B174 JBoss Central: * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta4-SNAPSHOT/ (upcoming milestone) * http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.Beta4-SNAPSHOT/ (upcoming milestone) Target Platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4 (upcoming milestone) Until the above target platform site is released, you will need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) New + Noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/whatsnew/ Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Changes prompting this respin-a are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-a%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%228.0.0.Beta3%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.2.0.Beta3%22%29%29%29 To compare the upcoming version of Central (4.2.0.Beta3a) against an older version, add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3a/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3a/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3a/ -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Tue Jul 15 05:00:51 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 15 Jul 2014 11:00:51 +0200 Subject: [jbosstools-dev] Perceived performance :/ In-Reply-To: <79EEF9B9-51AD-427A-9CC0-EF2AC1D1FC54@redhat.com> References: <79EEF9B9-51AD-427A-9CC0-EF2AC1D1FC54@redhat.com> Message-ID: <53C4EDC3.1010506@redhat.com> On 07/11/2014 11:15 PM, Max Rydahl Andersen wrote: > Seeing this is not great. > https://twitter.com/dashorst/status/487607610695483392 It's a Beta, we have CAT and an open Jira. This type of comments simply shows that this user sucks at understanding the lifecycle of a project and the meaning of Beta. It's too bad, because a more intelligent feedback message could help him and us a lot. > I've asked for details to know what are the specifics. > But it's worrisome. > Please make sure when you test your stuff you do it together with the > full toolset and not just your one plugin loaded. > Let's make sure we test this as users and not just as individual > plugin developers. > That's the only way we can spot performance issues caused by the > combination. About performance while editing, there is a major one in Luna with GTK3: https://bugs.eclipse.org/bugs/show_bug.cgi?id=434898 . If you have a big file, scrolling is a nightmare. What's strange is that I felt affected by this only after Luna got released. -- 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/20140715/cbcd8c8b/attachment.html From manderse at redhat.com Tue Jul 15 05:11:15 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 15 Jul 2014 11:11:15 +0200 Subject: [jbosstools-dev] My super cool Eclipse extensions In-Reply-To: <53C0031E.9010100@redhat.com> References: <53BFB890.6010500@redhat.com> <51EB5449-2292-4C4B-A67C-8F8924E9DDA4@redhat.com> <53C0031E.9010100@redhat.com> Message-ID: <9DCAF94E-C217-441E-AC4A-355CDBDF021D@redhat.com> On 11 Jul 2014, at 17:30, Mickael Istria wrote: > I made a snapshot available at > http://mickaelistria.github.io/jbosstools-eclipse/repository/target/repository/ > and README.md links to it. cool. Tried the open folder/project. First impressions good, here are my feedback on it: 1) the menu item says "Open folder/project" but during the import it seem to write in progress "Creating Folder" ...that is misleading..what folder are being created ? 2) It seem to just guess and then import - user has zero chance of actually confirming if the guess is right. 3) It seem to just look at the toplevel dir, I think it should look recursively like Import project(s) does and then show which projects and what guessed project types it will be imported as. 4) In general I think the UI would be better if similar to import so you dont have to just get the OS specific browser as the first thing (i.e. being able to easily type full path and/or get list of what projects will be imported would make it easier to comprehend what is going on IMO) 5) it would be really nice if this feature would be automatically called if I dragged a folder to eclipse window 6) javascript seem to get enabled on all projects I try import even thogh they aren't all javascript...(i.e. importing jbosstools-browsersim root folder) 7) import of a multimodule project like jbosstools-browsersim only result in one top root level project (if I used the maven import it would have imported the others) 8) it made the target folder in org.jboss.tools.vpe.browsersim.debugger the source folder for the java project - not sure why. it is a PDE project that can be deduced from meta-inf and build.properties... that said this is a really nice feature and would like to see how we could include it into jbosstools and definitely try get it into eclipse Mars. /max http://about.me/maxandersen From manderse at redhat.com Tue Jul 15 05:25:22 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 15 Jul 2014 11:25:22 +0200 Subject: [jbosstools-dev] Perceived performance :/ In-Reply-To: <53C4EDC3.1010506@redhat.com> References: <79EEF9B9-51AD-427A-9CC0-EF2AC1D1FC54@redhat.com> <53C4EDC3.1010506@redhat.com> Message-ID: On 15 Jul 2014, at 11:00, Mickael Istria wrote: > On 07/11/2014 11:15 PM, Max Rydahl Andersen wrote: >> Seeing this is not great. >> https://twitter.com/dashorst/status/487607610695483392 > It's a Beta, we have CAT and an open Jira. This type of comments > simply shows that this user sucks at understanding the lifecycle of a > project and the meaning of Beta. > It's too bad, because a more intelligent feedback message could help > him and us a lot. if he was the only one that reported it like this I would think the same. He is not - the most common tweet about jbosstools is either "its great" or "its slow", lately there have been more "its slow" thus why I'm worried. I myself can see the slowness when I run it and report what I find - but we can't just wait for users to get annoyed enough to then give feedback when its too late to fix. >> I've asked for details to know what are the specifics. >> But it's worrisome. >> Please make sure when you test your stuff you do it together with the >> full toolset and not just your one plugin loaded. >> Let's make sure we test this as users and not just as individual >> plugin developers. >> That's the only way we can spot performance issues caused by the >> combination. > About performance while editing, there is a major one in Luna with > GTK3: https://bugs.eclipse.org/bugs/show_bug.cgi?id=434898 . If you > have a big file, scrolling is a nightmare. > What's strange is that I felt affected by this only after Luna got > released. good thing we need GTK2 then :) joking aside - can we help akurtakov by providing a simple SWT app that shows the regression ? /max http://about.me/maxandersen From manderse at redhat.com Mon Jul 14 05:26:11 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 14 Jul 2014 11:26:11 +0200 Subject: [jbosstools-dev] Fwd: JBoss Tools Core 4.2.0.Beta3a bits available for QE testing References: <53C35EBD.8050009@redhat.com> Message-ID: > As always, these are not FINAL bits, but preliminary results for QE > testing. Not for redistribution to customers. > > Update Sites: > > * > http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3a-updatesite-core/ > * > http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3a-updatesite-coretests/ > * > http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3a-updatesite-hibernatetools/ > * > http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3a-updatesite-webtools/ > > Builds: > > * > http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3a-build-core/2014-07-11_21-41-17-B184 > * > http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3a-build-coretests/2014-07-11_21-41-16-B170 > * > http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3a-build-hibernatetools/2014-07-11_21-58-09-B124 > * > http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3a-build-webtools/2014-07-11_21-58-09-B174 > > JBoss Central: > > * > http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta4-SNAPSHOT/ > (upcoming milestone) > * > http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.Beta4-SNAPSHOT/ > (upcoming milestone) > > Target Platforms: > > * > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4 > (upcoming milestone) > > Until the above target platform site is released, you will need to add > it to Eclipse to resolve dependencies at install time. > Once released, dependencies will be found automatically from here: > > * > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > (latest release) > > New + Noteworthy (subject to change): > > * > https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew > * http://tools.jboss.org/documentation/whatsnew/ > > Schedule / Upcoming Releases: > > https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel > > -- > > Changes prompting this respin-a are: > > https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-a%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%228.0.0.Beta3%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.2.0.Beta3%22%29%29%29 > > To compare the upcoming version of Central (4.2.0.Beta3a) against an > older version, add lines similar to these your eclipse.ini file after > the -vmargs line for the appropriate version & URLs: > > -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3a/jbosstools-directory.xml > > -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3a/ > > -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3a/ > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > From nboldt at redhat.com Mon Jul 14 00:40:38 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 14 Jul 2014 00:40:38 -0400 Subject: [jbosstools-dev] Beta3 respin-a status #3: ACTION REQUIRED - Unresolved Issues in Openshift, Forge, Webservices, Server, Hibernate Message-ID: <53C35F46.9020903@redhat.com> There are 24 issues tagged for Beta3 respin-a. 16 of those are resolved. 8 remain unresolved. If these issues are complete and no FURTHER respin is required, please resolve them. If these issues are incomplete and a respin-b will be required, please update the label to "respin-b" instead of "respin-a". Affected projects include: * Openshift (App Wizard) * Forge * Webservices * Server (3 issues) * Hibernate (2 issues) Thanks, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Tue Jul 15 05:34:46 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 15 Jul 2014 11:34:46 +0200 Subject: [jbosstools-dev] My super cool Eclipse extensions In-Reply-To: <9DCAF94E-C217-441E-AC4A-355CDBDF021D@redhat.com> References: <53BFB890.6010500@redhat.com> <51EB5449-2292-4C4B-A67C-8F8924E9DDA4@redhat.com> <53C0031E.9010100@redhat.com> <9DCAF94E-C217-441E-AC4A-355CDBDF021D@redhat.com> Message-ID: <53C4F5B6.2040401@redhat.com> On 07/15/2014 11:11 AM, Max Rydahl Andersen wrote: > Tried the open folder/project. > First impressions good, here are my feedback on it: Thanks. For next set of comments, feel free to use the GitHub issues mechanism. I'll put feedback/explanation/excuses here, I'd appreciate if you (not only Max, anyone) could give some priority of what you think is the more important for better usage. > 1) the menu item says "Open folder/project" but during the import it > seem to write in progress "Creating Folder" ...that is > misleading..what folder are being created ? It delegates most stuff to Eclipse Resources API, I guess that's what says "creating folder". It's not actually creating a folder in filesystem, but in resource model. I agree it can be confusing. > 2) It seem to just guess and then import - user has zero chance of > actually confirming if the guess is right. Yes, I already thought about it, and I think it's probably the next change I'll make. > 3) It seem to just look at the toplevel dir, I think it should look > recursively like Import project(s) does and then show which projects > and what guessed project types it will be imported as. Making it working recursively will probably take ages and show a lot of choices to the user, who would get frightened by the amount of things to configure. But I agree it would be nice. I'll think about it. > 4) In general I think the UI would be better if similar to import so > you dont have to just get the OS specific browser as the first thing > (i.e. being able to easily type full path and/or get list of what > projects will be imported would make it easier to comprehend what is > going on IMO) On that I disagree. If we want the operation to feel simple, it has to be simple at first, showing a FileDialog after a menu is pretty usual and efficient for most software, I hardly believe mimicking that behaviour is 90% of the benefit of this change. Allowing to easily type full path is something I can do with my OS browser. > 5) it would be really nice if this feature would be automatically > called if I dragged a folder to eclipse window I agree, I'll try to implement that. > 6) javascript seem to get enabled on all projects I try import even > thogh they aren't all javascript...(i.e. importing > jbosstools-browsersim root folder) Ok, it's probably a bug in the JS detector. I'll have a look and try to fix this. Note that fixing 2) would be a good way to workaround this one. > 7) import of a multimodule project like jbosstools-browsersim only > result in one top root level project (if I used the maven import it > would have imported the others) Yes, and I think it's good like this. What I think would be a nice continuation of the process would be to show Maven modules differently in Project Explorer to allow open/import from there. Cf https://bugs.eclipse.org/bugs/show_bug.cgi?id=424317 . > 8) it made the target folder in > org.jboss.tools.vpe.browsersim.debugger the source folder for the java > project - not sure why. it is a PDE project that can be deduced from > meta-inf and build.properties... No doubt it's a bug. The current detectors/configurators are "cumulative", so it runs default Java configurator even on a Maven or PDE project. > that said this is a really nice feature and would like to see how we > could include it into jbosstools and definitely try get it into > eclipse Mars. Technically, it could be integrated easily in JBoss Tools: no additional deps or nothing else, already builds with JBT parent pom and TP. But as you noticed, it requires some fixes/improvements. About having it part of Mars, it's something that I think cannot really happen, because IBM people already decided what they will work on, and this is not part of their short-list. Cf Dani's answers to https://bugs.eclipse.org/bugs/show_bug.cgi?id=427768 . Sorted by priority of mine (top is higher): * 2 * 6 * 8 * 5 * 3 * 1 * 7, 4 -- 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/20140715/24bbf581/attachment.html From manderse at redhat.com Tue Jul 15 06:01:05 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 15 Jul 2014 12:01:05 +0200 Subject: [jbosstools-dev] Beta3 respin-a status #3: ACTION REQUIRED - Unresolved Issues in Openshift, Forge, Webservices, Server, Hibernate In-Reply-To: <53C35F46.9020903@redhat.com> References: <53C35F46.9020903@redhat.com> Message-ID: <14D9418B-51CB-4CC4-9B14-3F20708E8254@redhat.com> On 14 Jul 2014, at 6:40, Nick Boldt wrote: > There are 24 issues tagged for Beta3 respin-a. 16 of those are > resolved. > 8 remain unresolved. nick, where are you looking - I moved all respin-a to respin-b when I saw your beta3a announcement mail. I currently only see one issue with respin-a: JBIDE-17843 and that one is reopened. > If these issues are complete and no FURTHER respin is required, please > resolve them. > If these issues are incomplete and a respin-b will be required, please > update the label to "respin-b" instead of "respin-a". they are not resolved - further respin is required. /max http://about.me/maxandersen From manderse at redhat.com Tue Jul 15 06:36:54 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 15 Jul 2014 12:36:54 +0200 Subject: [jbosstools-dev] My super cool Eclipse extensions In-Reply-To: <53C4F5B6.2040401@redhat.com> References: <53BFB890.6010500@redhat.com> <51EB5449-2292-4C4B-A67C-8F8924E9DDA4@redhat.com> <53C0031E.9010100@redhat.com> <9DCAF94E-C217-441E-AC4A-355CDBDF021D@redhat.com> <53C4F5B6.2040401@redhat.com> Message-ID: >> 3) It seem to just look at the toplevel dir, I think it should look >> recursively like Import project(s) does and then show which projects >> and what guessed project types it will be imported as. > Making it working recursively will probably take ages and show a lot > of choices to the user, who would get frightened by the amount of > things to configure. > But I agree it would be nice. I'll think about it. our runtime detection recursively scan about 500 dirs no my disk without problems. importing multiple nested projects like all of jbosstools takes miliseconds with the "old" approach. I don't think it will be as slow as you think. >> 4) In general I think the UI would be better if similar to import so >> you dont have to just get the OS specific browser as the first thing >> (i.e. being able to easily type full path and/or get list of what >> projects will be imported would make it easier to comprehend what is >> going on IMO) > On that I disagree. If we want the operation to feel simple, it has to > be simple at first, showing a FileDialog after a menu is pretty usual > and efficient for most software I hardly believe mimicking that > behaviour is 90% of the benefit of this change. I dont understand that sentence. The current UI is slow and non-informative of what will happen. Sure, it works great if you actually get to select the rigth folder in first go and it guesses the import correctly...but thats pretty damn never ;) > Allowing to easily type full path is something I can do with my OS > browser. yes, but not with all file dialogs. OSX especially sucks. You need to know to press ctrl+shift+G and whatnot. >> 5) it would be really nice if this feature would be automatically >> called if I dragged a folder to eclipse window > I agree, I'll try to implement that. >> 7) import of a multimodule project like jbosstools-browsersim only >> result in one top root level project (if I used the maven import it >> would have imported the others) > Yes, and I think it's good like this. What I think would be a nice > continuation of the process would be to show Maven modules differently > in Project Explorer to allow open/import from there. Cf > https://bugs.eclipse.org/bugs/show_bug.cgi?id=424317 . You think it is good it does not actually import the nested projects ? ...so you don't want to show a more userfriendly UI for the first step, but you are okey requiring users to after import of a nested project structure having to manually import them just because it is a maven project ? >> 8) it made the target folder in >> org.jboss.tools.vpe.browsersim.debugger the source folder for the >> java project - not sure why. it is a PDE project that can be deduced >> from meta-inf and build.properties... > No doubt it's a bug. The current detectors/configurators are > "cumulative", so it runs default Java configurator even on a Maven or > PDE project. yeah I think that will not work in many cases. They need to be a tad smarter. >> that said this is a really nice feature and would like to see how we >> could include it into jbosstools and definitely try get it into >> eclipse Mars. > Technically, it could be integrated easily in JBoss Tools: no > additional deps or nothing else, already builds with JBT parent pom > and TP. main problem is that it has dependencies to alot of things so we can't install it piecemal (i.e. I Assume the maven recognizer requires m2e to be installed) > But as you noticed, it requires some fixes/improvements. > About having it part of Mars, it's something that I think cannot > really happen, because IBM people already decided what they will work > on, and this is not part of their short-list. Cf Dani's answers to > https://bugs.eclipse.org/bugs/show_bug.cgi?id=427768 . I do not grok what this issue of nested resources has to do with simpler imports ? and if we already provide the code why would they not be okey to look at the contribution ? > Sorted by priority of mine (top is higher): > * 2 > * 6 > * 8 > * 5 > * 3 > * 1 > * 7, 4 I think 7,4 are critical since most projects are not just single projects these days. i.e. I can't use this to import any of our basic quickstarts unless I do them one by one. /max http://about.me/maxandersen From nboldt at redhat.com Tue Jul 15 11:16:51 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 15 Jul 2014 11:16:51 -0400 Subject: [jbosstools-dev] Beta3 respin-a status #3: ACTION REQUIRED - Unresolved Issues in Openshift, Forge, Webservices, Server, Hibernate In-Reply-To: <14D9418B-51CB-4CC4-9B14-3F20708E8254@redhat.com> References: <53C35F46.9020903@redhat.com> <14D9418B-51CB-4CC4-9B14-3F20708E8254@redhat.com> Message-ID: <53C545E3.8030804@redhat.com> When I sent this email (Mon, 14 Jul 2014 00:40:38 -0400), there were 8. By the time it was actually delivered to the mailing list, you'd already moved them. I believe that's called a "slip twixt lip and cup" [1]. :) [1] http://idioms.thefreedictionary.com/There%27s+many+a+slip+twixt+cup+and+lip On 07/15/2014 06:01 AM, Max Rydahl Andersen wrote: > On 14 Jul 2014, at 6:40, Nick Boldt wrote: > >> There are 24 issues tagged for Beta3 respin-a. 16 of those are resolved. >> 8 remain unresolved. > > nick, where are you looking - I moved all respin-a to respin-b when I > saw your beta3a announcement mail. > > I currently only see one issue with respin-a: JBIDE-17843 and that one > is reopened. > >> If these issues are complete and no FURTHER respin is required, please >> resolve them. > >> If these issues are incomplete and a respin-b will be required, please >> update the label to "respin-b" instead of "respin-a". > > they are not resolved - further respin is required. > > > /max > http://about.me/maxandersen -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Tue Jul 15 11:35:56 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 15 Jul 2014 17:35:56 +0200 Subject: [jbosstools-dev] Beta3 respin-a status #3: ACTION REQUIRED - Unresolved Issues in Openshift, Forge, Webservices, Server, Hibernate In-Reply-To: <53C545E3.8030804@redhat.com> References: <53C35F46.9020903@redhat.com> <14D9418B-51CB-4CC4-9B14-3F20708E8254@redhat.com> <53C545E3.8030804@redhat.com> Message-ID: <31E30837-1D88-4C1C-B20B-A1EDFD0A96F0@redhat.com> On 15 Jul 2014, at 17:16, Nick Boldt wrote: > When I sent this email (Mon, 14 Jul 2014 00:40:38 -0400), there were > 8. By the time it was actually delivered to the mailing list, you'd > already moved them. > > I believe that's called a "slip twixt lip and cup" [1]. :) > > [1] > http://idioms.thefreedictionary.com/There%27s+many+a+slip+twixt+cup+and+lip Phew - you didn't notice the flux capaciator that I used to go back in time and mess with jira ;). /max > > On 07/15/2014 06:01 AM, Max Rydahl Andersen wrote: >> On 14 Jul 2014, at 6:40, Nick Boldt wrote: >> >>> There are 24 issues tagged for Beta3 respin-a. 16 of those are >>> resolved. >>> 8 remain unresolved. >> >> nick, where are you looking - I moved all respin-a to respin-b when I >> saw your beta3a announcement mail. >> >> I currently only see one issue with respin-a: JBIDE-17843 and that >> one >> is reopened. >> >>> If these issues are complete and no FURTHER respin is required, >>> please >>> resolve them. >> >>> If these issues are incomplete and a respin-b will be required, >>> please >>> update the label to "respin-b" instead of "respin-a". >> >> they are not resolved - further respin is required. >> >> >> /max >> http://about.me/maxandersen > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com /max http://about.me/maxandersen From nboldt at redhat.com Tue Jul 15 11:52:44 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 15 Jul 2014 11:52:44 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform for Jboss Central: update SpringIDE In-Reply-To: <53B479AE.5030109@redhat.com> References: <53B479AE.5030109@redhat.com> Message-ID: <53C54E4C.8030303@redhat.com> Here is a proposal for 1 change to the JBoss Tools 4.40.0.Beta4-SNAPSHOT target platform for JBoss Central): https://github.com/jbosstools/jbosstools-download.jboss.org/pull/383 https://github.com/jbosstools/jbosstools-discovery/pull/196 It consists of the following change: * JBDS-2956 - Update to Spring IDE 3.6 in Central -- The above PRs have not been applied (to allow time to complain / reject / pull an even *newer* version of Tern), so you can fetch the PRs and build the TP locally to test it out: Build target-platform: $ cd jbosstools-target-platforms $ git fetch origin 4.40.x $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT -Pmultiple.target -- If you want to perform a scripted install of the entire target platform into your local Eclipse or JBDS instance, you can now do so with this script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh Usage is documented in the above script, and in this README: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#updating-versions-of-ius-in-target-files -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nickboldt at gmail.com Tue Jul 15 14:22:40 2014 From: nickboldt at gmail.com (Nick Boldt) Date: Tue, 15 Jul 2014 14:22:40 -0400 Subject: [jbosstools-dev] Fwd: [tycho-user] please test staged tycho 0.21.0 In-Reply-To: References: Message-ID: <53C57170.8030406@gmail.com> FYI, Tycho 0.21 is nearly ready. Feel free to try it out using the snippet below in your root pom, then mvn clean install -DtychoVersion=0.21.0 You should see downloads coming from various places, including https://oss.sonatype.org/content/repositories/orgeclipsetycho-1018 -------- Original Message -------- Subject: [tycho-user] please test staged tycho 0.21.0 Date: Tue, 15 Jul 2014 07:27:46 +0000 From: Sievers, Jan Reply-To: Tycho user list To: Tycho user list (tycho-user at eclipse.org) Tycho milestone release 0.21.0 has been staged. For details of new features and bugfixes, see release notes [1]. Please help by testing the staged milestone build. To use it, change your tycho version to 0.21.0 and add snippet [2] to your pom. We plan to promote this release in one week unless major regressions are found. Regards, Tycho team [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.21 [2] tycho-staged https://oss.sonatype.org/content/repositories/orgeclipsetycho-1018/ _______________________________________________ tycho-user mailing list tycho-user at eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/tycho-user From gorkem.ercan at gmail.com Tue Jul 15 14:36:48 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Tue, 15 Jul 2014 14:36:48 -0400 Subject: [jbosstools-dev] Existing Hybrid Mobile bugs and jiras going forward Message-ID: Hi, The matter of existing open Jiras for the aerogear-hybrid will probably come up. As you know most of the features on that component has moved to Thym project at Eclipse foundation[1]. All the bugs related to those features will be handled in Eclipse bugzilla. Going forward, new bug reports that are related to cordova development (except CordovaSim) should be opened on the Eclipse bugzilla. For the existing Jiras, I do not want to do a mass move to Eclipse bugzilla but rather open them on Eclipse bugzilla and have a link to it on Jira as we actually start working on them. An example of this flow can be seen on JBIDE-16987. Does that make sense for everyone but especially QE? [1] http://tools.jboss.org/blog/2014-07-14-development-of-HMT-moved-to-eclipse.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140715/7a42a2b3/attachment.html From manderse at redhat.com Wed Jul 16 00:07:17 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 16 Jul 2014 06:07:17 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform for Jboss Central: update SpringIDE In-Reply-To: <53C54E4C.8030303@redhat.com> References: <53B479AE.5030109@redhat.com> <53C54E4C.8030303@redhat.com> Message-ID: <73ABBC68-C940-430D-8A73-BCE999917704@redhat.com> On 15 Jul 2014, at 17:52, Nick Boldt wrote: > Here is a proposal for 1 change to the JBoss Tools > 4.40.0.Beta4-SNAPSHOT target platform for JBoss Central): > https://github.com/jbosstools/jbosstools-download.jboss.org/pull/383 > https://github.com/jbosstools/jbosstools-discovery/pull/196 > It consists of the following change: > > * JBDS-2956 - Update to Spring IDE 3.6 in Central > > -- > > The above PRs have not been applied (to allow time to complain / > reject > / pull an even *newer* version of Tern), one of the above PR's are applied and why is this related to Tern ? The change looks fine for me, mainly relevant for QE to verify if SpringIDE 3.6 works/fixes the issues. > so you can fetch the PRs and > build the TP locally to test it out: > > Build target-platform: > > $ cd jbosstools-target-platforms > $ git fetch origin 4.40.x > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple > $ mvn clean install -P \!multiple2repo > > Try with just built target-platform: > > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT > -Pmultiple.target I don't really see how the above relates to testing of *JBoss Central* target platform ? The above wont work since there is *no* 4.40.Beta4-SNAPSHOT for the actual jbosstools-target-platform. Aren't you mixing up .target platforms here ? /max http://about.me/maxandersen From nboldt at redhat.com Wed Jul 16 09:08:38 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 16 Jul 2014 09:08:38 -0400 Subject: [jbosstools-dev] Proposed change to JBT 4.40.Beta4-SNAPSHOT target platform for Jboss Central: update SpringIDE In-Reply-To: <73ABBC68-C940-430D-8A73-BCE999917704@redhat.com> References: <53B479AE.5030109@redhat.com> <53C54E4C.8030303@redhat.com> <73ABBC68-C940-430D-8A73-BCE999917704@redhat.com> Message-ID: <53C67956.6080203@redhat.com> On 07/16/2014 12:07 AM, Max Rydahl Andersen wrote: > On 15 Jul 2014, at 17:52, Nick Boldt wrote: > >> Here is a proposal for 1 change to the JBoss Tools >> 4.40.0.Beta4-SNAPSHOT target platform for JBoss Central): > >> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/383 >> https://github.com/jbosstools/jbosstools-discovery/pull/196 > >> It consists of the following change: >> >> * JBDS-2956 - Update to Spring IDE 3.6 in Central >> >> -- >> >> The above PRs have not been applied (to allow time to complain / reject >> / pull an even *newer* version of Tern), > one of the above PR's are applied and why is this related to Tern ? Yes, the one that simply creates the new mirror was applied because there's nothing to approve there. I should have removed the bit about Tern -- was copying from previous notification email template. > The change looks fine for me, mainly relevant for QE to verify if > SpringIDE 3.6 works/fixes the issues. They've already done that. > I don't really see how the above relates to testing of *JBoss Central* > target platform ? > The above wont work since there is *no* 4.40.Beta4-SNAPSHOT for the > actual jbosstools-target-platform. Again, I used the default template & didn't insert jbosstools-discovery in place of jbosstools-target-platforms. But there IS a JBT 4.40.0.Beta4-SNAPSHOT target platform: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4-SNAPSHOT/ > Aren't you mixing up .target platforms here ? Yes, I did. Apologies. Anyway, as it's been a day and no one has said no to applying the above PR, I'll do so and rebuild the Central TP in both master and Beta3x branches so that Spring 3.6 will now be included. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From daniel at exadel.com Wed Jul 16 14:20:37 2014 From: daniel at exadel.com (Daniel Azarov) Date: Wed, 16 Jul 2014 11:20:37 -0700 Subject: [jbosstools-dev] Compilation failure in Seam In-Reply-To: <53B1EAB0.9020408@exadel.com> References: <53B1EAB0.9020408@exadel.com> Message-ID: <53C6C275.9030205@exadel.com> Hi, Again, we've got Seam Tools broken. See https://issues.jboss.org/browse/JBIDE-17901 This time interface interface org.jboss.tools.hibernate.spi.IConfiguration was moved to plugin org.jboss.tools.hibernate.spi See https://github.com/jbosstools/jbosstools-hibernate/commit/7b0ab2fb71534cf3e557801900b5ccc9820e246d BTW there is no JIRA issue for that. Seam Tools depends on hibernate. Please, when you change public API in Hibernate be sure Seam compiles too. Best regards, Daniel Azarov On 06/30/2014 03:54 PM, Daniel Azarov wrote: > Hi, > > We got compilation failure in Seam Tools again. > (Seehttps://issues.jboss.org/browse/JBIDE-17729) > > The cause is that org.jboss.tools.hibernate.spi.IConfiguration was changed. > > It is not good to change public API without full build tested. > > At least Seam Tools depends on hibernate. > Please when you change public API in Hibernate be sure Seam compiles too. > > Best regards, > Daniel Azarov > > _______________________________________________ > 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/20140716/0f20e1e6/attachment.html From lhein at redhat.com Fri Jul 18 06:07:22 2014 From: lhein at redhat.com (Lars Heinemann) Date: Fri, 18 Jul 2014 12:07:22 +0200 Subject: [jbosstools-dev] Is there a shared parent pom for JBoss Tools IS projects? Message-ID: <1405678042.2430.3.camel@localhost.localdomain> Hey, I am updating our the Fuse Tooling pom file and I was wondering if the Integration Stack projects somehow share a common parent pom. Any ideas? Lars From manderse at redhat.com Fri Jul 18 06:14:20 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 18 Jul 2014 12:14:20 +0200 Subject: [jbosstools-dev] Is there a shared parent pom for JBoss Tools IS projects? In-Reply-To: <1405678042.2430.3.camel@localhost.localdomain> References: <1405678042.2430.3.camel@localhost.localdomain> Message-ID: <1ECF86BF-7650-421B-BF81-11A54BF1D4EC@redhat.com> On 18 Jul 2014, at 12:07, Lars Heinemann wrote: > Hey, > > I am updating our the Fuse Tooling pom file and I was wondering if the > Integration Stack projects somehow share a common parent pom. I do not think there is. I always wanted one but with the integration platform plugins following individual separate release cycles and the funkyness of tycho/p2 its tricky to have a true parent pom. Or rather - it requires some work to get it. We could definitely look at extracting the generic eclipse/tycho building instructions from jboss tools parent pom so that is reusable - but keep the references to specific version and repositories out of it. Like a super-parent. But for now I do not believe integration-stack has one. /max http://about.me/maxandersen From p.g.richardson at phantomjinx.co.uk Fri Jul 18 06:35:21 2014 From: p.g.richardson at phantomjinx.co.uk (phantomjinx) Date: Fri, 18 Jul 2014 11:35:21 +0100 Subject: [jbosstools-dev] Is there a shared parent pom for JBoss Tools IS projects? In-Reply-To: <1405678042.2430.3.camel@localhost.localdomain> References: <1405678042.2430.3.camel@localhost.localdomain> Message-ID: <53C8F869.5040604@phantomjinx.co.uk> On 07/18/2014 11:07 AM, Lars Heinemann wrote: > Hey, > > I am updating our the Fuse Tooling pom file and I was wondering if the > Integration Stack projects somehow share a common parent pom. > > Any ideas? > > Lars > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev FWIW, Teiid Designer uses the jboss tools parent pom. Never been a problem for us and we update the version as and when we need to (or told to ;-) ). org.jboss.tools parent 4.2.0.Beta3-SNAPSHOT Cheers PGR -- Paul Richardson * p.g.richardson at phantomjinx.co.uk * p.g.richardson at redhat.com * pgrichardson at linux.com "I know exactly who reads the papers ... * The Daily Mirror is read by people who think they run the country. * The Guardian is read by people who think they ought to run the country. * The Times is read by people who do actually run the country. * The Daily Mail is read by the wives of the people who run the country. * The Financial Times is read by the people who own the country. * The Morning Star is read by the people who think the country ought to be run by another country. * The Daily Telegraph is read by the people who think it is." Jim Hacker, Yes Minister From manderse at redhat.com Fri Jul 18 07:25:19 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 18 Jul 2014 13:25:19 +0200 Subject: [jbosstools-dev] Is there a shared parent pom for JBoss Tools IS projects? In-Reply-To: <53C8F869.5040604@phantomjinx.co.uk> References: <1405678042.2430.3.camel@localhost.localdomain> <53C8F869.5040604@phantomjinx.co.uk> Message-ID: <0A9A54FA-E570-4A3F-8A6A-B603AE505D29@redhat.com> On 18 Jul 2014, at 12:35, phantomjinx wrote: > On 07/18/2014 11:07 AM, Lars Heinemann wrote: >> Hey, >> >> I am updating our the Fuse Tooling pom file and I was wondering if >> the >> Integration Stack projects somehow share a common parent pom. >> >> Any ideas? >> >> Lars >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > FWIW, > > Teiid Designer uses the jboss tools parent pom. Never been a problem > for us and we update the > version as and when we need to (or told to ;-) ). ah nice - didn't realize that. cool. you at least then get consistent site packaging ;) /max > > > org.jboss.tools > parent > 4.2.0.Beta3-SNAPSHOT > > > Cheers > > PGR > > -- > > Paul Richardson > > * p.g.richardson at phantomjinx.co.uk > * p.g.richardson at redhat.com > * pgrichardson at linux.com > > "I know exactly who reads the papers ... > > * The Daily Mirror is read by people who think they run the country. > * The Guardian is read by people who think they ought to run the > country. > * The Times is read by people who do actually run the country. > * The Daily Mail is read by the wives of the people who run the > country. > * The Financial Times is read by the people who own the country. > * The Morning Star is read by the people who think the country ought > to be run by another country. > * The Daily Telegraph is read by the people who think it is." > > Jim Hacker, Yes Minister > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Fri Jul 18 08:08:29 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 18 Jul 2014 14:08:29 +0200 Subject: [jbosstools-dev] An excursion into integration testing plugins with Arquillian In-Reply-To: <53BE5BB0.3020406@phantomjinx.co.uk> References: <53A85C9C.3030801@phantomjinx.co.uk> <42E83CBB-5270-411A-B778-C41C56C46A6C@redhat.com> <53AD7E90.3020409@phantomjinx.co.uk> <7AD35903-55CB-46F6-9F48-9CC8D4A724AF@redhat.com> <53ADF566.7030300@phantomjinx.co.uk> <5E889845-98AE-4871-98C8-B0ED190CE3BA@redhat.com> <53B2BEA0.4010702@phantomjinx.co.uk> <53BD37C6.1030702@phantomjinx.co.uk> <53BE5BB0.3020406@phantomjinx.co.uk> Message-ID: <83F1AE5C-8902-442E-85A0-9C2941A40782@redhat.com> On 10 Jul 2014, at 11:24, phantomjinx wrote: > On 07/10/2014 09:06 AM, Max Rydahl Andersen wrote: >> >>> On 09/07/2014, at 14.38, phantomjinx >>> wrote: >>> >> On 07/04/2014 05:01 PM, Max Rydahl Andersen wrote: >>>>>>> >>>>>>> My main concern is that this is bringing in dependencies outside >>>>>>> or our target >>>>>>> platform thus less easy to contain/check for overlaps. Also - >>>>>>> using mvn copy goal >>>>>>> seems to me to be the better way rather than using ant auto >>>>>>> builders? >>>>>> >>>>>> The ant auto builder [1] does hands-off maven by calling 'mvn >>>>>> process-sources'. This >>>>>> always executes the mvn copy-dependencies goal so bringing in the >>>>>> dependencies [2]. It >>>>>> has always been essential that any process happening while >>>>>> developing in Eclipse must >>>>>> also occur when building on the command line through maven. This >>>>>> is an example of that >>>>>> with the ant providing the plumbing between Eclipse and maven. >>>>> >>>>> ..isn't that what the tycho-m2 plugin does for you ? >> >> Well I am no expert in tycho so I may be wrong or not-up-to-date but >> no tycho cannot help. >> >> Tycho looks only looks for dependencies in pom files, which are osgi >> bundles. Normal maven jar >> libraries are ignored hence for those libraries to be available on >> the classpath to both >> eclipse's P2 and Tycho, they much be listed in the manifest file. I >> do this by specifying them >> as dependencies in the pom file and using copy-dependencies to get >> them into the lib directory >> of the plugin. >> >> >>> Yes, we do this in other places too and tycho m2e integration makes >>> it happen without needing >>> the ant step. >> >>> /max > > Well eliminating the need for the ant build scripts would certainly > simplify things. Can you point > me to an example project as the tycho-m2e documentation on the net is > a little scant. sorry for delay. one example is the openshift project. https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.2.0.Beta3x/plugins/org.jboss.tools.openshift.express.client/pom.xml#L32 shows how we define copy dependencies. When you import it as a maven project you'll get errors/warnings about "plugin not covered by lifecycle" for tycho related plugins. Run Quickfix and download the m2e-tycho plugin. restart eclipse. now when you maven update the copy goal should be taking into account. /max > > Cheers > > PGR > > - -- > Paul Richardson > > * p.g.richardson at phantomjinx.co.uk > * p.g.richardson at redhat.com > * pgrichardson at linux.com > > "I know exactly who reads the papers ... > > * The Daily Mirror is read by people who think they run the country. > * The Guardian is read by people who think they ought to run the > country. > * The Times is read by people who do actually run the country. > * The Daily Mail is read by the wives of the people who run the > country. > * The Financial Times is read by the people who own the country. > * The Morning Star is read by the people who think the country ought > to be run by another country. > * The Daily Telegraph is read by the people who think it is." > > Jim Hacker, Yes Minister /max http://about.me/maxandersen From pleacu at redhat.com Fri Jul 18 08:36:36 2014 From: pleacu at redhat.com (Paul Leacu) Date: Fri, 18 Jul 2014 08:36:36 -0400 (EDT) Subject: [jbosstools-dev] Is there a shared parent pom for JBoss Tools IS projects? In-Reply-To: <1ECF86BF-7650-421B-BF81-11A54BF1D4EC@redhat.com> References: <1405678042.2430.3.camel@localhost.localdomain> <1ECF86BF-7650-421B-BF81-11A54BF1D4EC@redhat.com> Message-ID: <253279248.8340858.1405686996498.JavaMail.zimbra@redhat.com> The IS target-platform pulls in the the JBoss parent pom to facilitate nexus deployment and we use the jboss tycho plugins but no general JBoss parent pom. --paull ----- Original Message ----- > From: "Max Rydahl Andersen" > To: "Lars Heinemann" > Cc: jbosstools-dev at lists.jboss.org > Sent: Friday, July 18, 2014 6:14:20 AM > Subject: Re: [jbosstools-dev] Is there a shared parent pom for JBoss Tools IS projects? > > On 18 Jul 2014, at 12:07, Lars Heinemann wrote: > > > Hey, > > > > I am updating our the Fuse Tooling pom file and I was wondering if the > > Integration Stack projects somehow share a common parent pom. > > I do not think there is. I always wanted one but with the integration > platform plugins following individual separate release cycles > and the funkyness of tycho/p2 its tricky to have a true parent pom. > > Or rather - it requires some work to get it. > > We could definitely look at extracting the generic eclipse/tycho > building instructions from jboss tools parent pom > so that is reusable - but keep the references to specific version and > repositories out of it. Like a super-parent. > > But for now I do not believe integration-stack has one. > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > From mistria at redhat.com Fri Jul 18 14:35:34 2014 From: mistria at redhat.com (Mickael Istria) Date: Fri, 18 Jul 2014 20:35:34 +0200 Subject: [jbosstools-dev] Respin in progress: No more push allowed on branch Message-ID: <53C968F6.2000202@redhat.com> Hi all, We are currently in the process of building JBoss Tools 4.2.0.Beta3 respin-b. So please DON'T push any new change for this respin. It's too late. If you have a change you need to push, please notify the mailing-list first. 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/20140718/5cbb0f3a/attachment.html From nboldt at redhat.com Fri Jul 18 14:38:22 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 18 Jul 2014 14:38:22 -0400 Subject: [jbosstools-dev] Respin in progress: No more push allowed on branch In-Reply-To: <53C968F6.2000202@redhat.com> References: <53C968F6.2000202@redhat.com> Message-ID: <53C9699E.9030703@redhat.com> Subsequent fixes for Beta3 should be held until you hear that Beta3b (Beta3 respin-b) is released, in a few hours or so. Once that's done, you can push in fixes for Beta3, but please tag them with the "respin-c" label as they'll be too late for repsin-b. On 07/18/2014 02:35 PM, Mickael Istria wrote: > Hi all, > > We are currently in the process of building JBoss Tools 4.2.0.Beta3 > respin-b. > So please DON'T push any new change for this respin. It's too late. If > you have a change you need to push, please notify the mailing-list first. > > Cheers > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Fri Jul 18 19:23:08 2014 From: mistria at redhat.com (Mickael Istria) Date: Sat, 19 Jul 2014 01:23:08 +0200 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta3b bits available for QE testing Message-ID: <53C9AC5C.4000908@redhat.com> As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3b-updatesite-core/ Target platforms: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4 Until the above target platform site is released, you will need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta4/ (upcoming milestone) * http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.Beta4/ (upcoming milestone) New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel Additional update sites: * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3b-updatesite-coretests/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3b-updatesite-hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3b-updatesite-webtools/ Build sites: * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3b-build-core/2014-07-18_16-49-06-B197/ * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3b-build-coretests/2014-07-18_16-50-49-B183/ * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3b-build-hibernatetools/2014-07-18_17-11-58-B135/ * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3b-build-webtools/2014-07-18_17-11-58-B185/ Changes prompting this respin-b are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-b%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%228.0.0.Beta3%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.2.0.Beta3%22%29%29%29 To compare the upcoming version of Central (${version}) against an older version, add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3b/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3b/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3b/ -- 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/20140719/a2c5830a/attachment-0001.html From manderse at redhat.com Sat Jul 19 00:00:44 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sat, 19 Jul 2014 00:00:44 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201407190400.s6J40in2018776@int-mx13.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-17926 https://issues.jboss.org/browse/JBIDE-17926 Summary: JBOSS EAP 6.2.0 Database connection manager not available Shutdown Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 15:01:20.046318 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From jpeterka at redhat.com Mon Jul 21 05:33:50 2014 From: jpeterka at redhat.com (Jiri Peterka) Date: Mon, 21 Jul 2014 11:33:50 +0200 Subject: [jbosstools-dev] o.j.t.tycho-plugins.repository-utils missing pom Message-ID: <53CCDE7E.20203@redhat.com> Hi, there is a broken artifact (no pom file at least, see https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/tycho-plugins/repository-utils/0.19.0-SNAPSHOT/repository-utils-0.19.0-20140714.150948-34.pom ) Could somebody take a look at it? Thanks -- Jirka From manderse at redhat.com Mon Jul 21 06:10:58 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 21 Jul 2014 12:10:58 +0200 Subject: [jbosstools-dev] o.j.t.tycho-plugins.repository-utils missing pom In-Reply-To: <53CCDE7E.20203@redhat.com> References: <53CCDE7E.20203@redhat.com> Message-ID: On 21 Jul 2014, at 11:33, Jiri Peterka wrote: > Hi, > > there is a broken artifact (no pom file at least, see > https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/tycho-plugins/repository-utils/0.19.0-SNAPSHOT/repository-utils-0.19.0-20140714.150948-34.pom > ) eh - what is the context here ? I would not expect any snapshots inside the release repository. ..also why haven't we released any of these plugins since 0.16 ? ...that seems unexpected too. /max http://about.me/maxandersen From jpeterka at redhat.com Mon Jul 21 06:24:10 2014 From: jpeterka at redhat.com (Jiri Peterka) Date: Mon, 21 Jul 2014 12:24:10 +0200 Subject: [jbosstools-dev] o.j.t.tycho-plugins.repository-utils missing pom In-Reply-To: References: <53CCDE7E.20203@redhat.com> Message-ID: <53CCEA4A.2090904@redhat.com> On 07/21/2014 12:10 PM, Max Rydahl Andersen wrote: > On 21 Jul 2014, at 11:33, Jiri Peterka wrote: > >> Hi, >> >> there is a broken artifact (no pom file at least, see >> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/tycho-plugins/repository-utils/0.19.0-SNAPSHOT/repository-utils-0.19.0-20140714.150948-34.pom >> >> ) > > eh - what is the context here ? > > I would not expect any snapshots inside the release repository. sorry, wrong link, I was using this one http://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/tycho-plugins/repository-utils/0.19.0-SNAPSHOT/ -- Jirka > > ..also why haven't we released any of these plugins since 0.16 ? > ...that seems unexpected too. > > /max > http://about.me/maxandersen From mmalina at redhat.com Mon Jul 21 07:01:05 2014 From: mmalina at redhat.com (Martin Malina) Date: Mon, 21 Jul 2014 13:01:05 +0200 Subject: [jbosstools-dev] o.j.t.tycho-plugins.repository-utils missing pom In-Reply-To: References: <53CCDE7E.20203@redhat.com> Message-ID: AFAICS, no build that depends on the jboss tools parent pom works. Ie. when you try to build jbosstools-server or jbosstools-integration-tests, you get this: nattura:jbosstools-server rasp$ mvn clean verify -DskipTests Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 [INFO] Scanning for projects... Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml Downloading: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml (606 B at 0.4 KB/sec) [WARNING] Could not transfer metadata org.jboss.tools:parent:4.2.0.CR1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/parent-4.2.0.CR1-20140708.134830-2.pom objc[85943]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/bin/java and /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined. Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/parent-4.2.0.CR1-20140708.134830-2.pom (28 KB at 23.2 KB/sec) Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml Downloading: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml (869 B at 1.6 KB/sec) Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/jbosstools-unified-4.40.0.CR1-20140713.052635-2-jbosstools-unified.target Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/jbosstools-unified-4.40.0.CR1-20140713.052635-2-jbosstools-unified.target (32 KB at 30.8 KB/sec) [WARNING] The POM for org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-20140714.150948-34 is missing, no dependency information available [ERROR] Internal error: java.lang.RuntimeException: org.apache.maven.MavenExecutionException: Could not setup plugin ClassRealm: Plugin org.jboss.tools.tycho-plugins:repository-utils:0.19.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT: Failure to find org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 in https://repository.sonatype.org/content/groups/sonatype-public-grid was cached in the local repository, resolution will not be reattempted until the update interval of sonatype-public-grid has elapsed or updates are forced -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: org.apache.maven.MavenExecutionException: Could not setup plugin ClassRealm 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:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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: org.apache.maven.MavenExecutionException: Could not setup plugin ClassRealm at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:166) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:124) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:87) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:70) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 11 more Caused by: org.apache.maven.MavenExecutionException: Could not setup plugin ClassRealm at org.eclipse.tycho.core.maven.utils.PluginRealmHelper.newMavenExecutionException(PluginRealmHelper.java:143) at org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:130) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:146) ... 16 more Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.jboss.tools.tycho-plugins:repository-utils:0.19.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.eclipse.tycho.core.maven.utils.MavenCompatiblityHelper.getPluginDescriptor(MavenCompatiblityHelper.java:68) at org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:95) ... 17 more Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:279) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115) ... 24 more Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 in https://repository.sonatype.org/content/groups/sonatype-public-grid was cached in the local repository, resolution will not be reattempted until the update interval of sonatype-public-grid has elapsed or updates are forced at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:281) ... 27 more Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 in https://repository.sonatype.org/content/groups/sonatype-public-grid was cached in the local repository, resolution will not be reattempted until the update interval of sonatype-public-grid has elapsed or updates are forced at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230) at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:204) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:427) ... 30 more [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/InternalErrorException -Martin On 21. 7. 2014, at 12:10, Max Rydahl Andersen wrote: > On 21 Jul 2014, at 11:33, Jiri Peterka wrote: > >> Hi, >> >> there is a broken artifact (no pom file at least, see >> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/tycho-plugins/repository-utils/0.19.0-SNAPSHOT/repository-utils-0.19.0-20140714.150948-34.pom >> ) > > eh - what is the context here ? > > I would not expect any snapshots inside the release repository. > > ..also why haven't we released any of these plugins since 0.16 ? ...that > seems unexpected too. > > /max > http://about.me/maxandersen > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From manderse at redhat.com Mon Jul 21 08:49:54 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 21 Jul 2014 14:49:54 +0200 Subject: [jbosstools-dev] o.j.t.tycho-plugins.repository-utils missing pom In-Reply-To: References: <53CCDE7E.20203@redhat.com> Message-ID: On 21 Jul 2014, at 13:01, Martin Malina wrote: > AFAICS, no build that depends on the jboss tools parent pom works. eh...thats definitely not supposed to happen. Looking into it. /max > > Ie. when you try to build jbosstools-server or > jbosstools-integration-tests, you get this: > > nattura:jbosstools-server rasp$ mvn clean verify -DskipTests > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option > PermSize=128m; support was removed in 8.0 > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option > MaxPermSize=256m; support was removed in 8.0 > [INFO] Scanning for projects... > Downloading: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml > Downloading: > https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml > Downloaded: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml > (606 B at 0.4 KB/sec) > [WARNING] Could not transfer metadata > org.jboss.tools:parent:4.2.0.CR1-SNAPSHOT/maven-metadata.xml from/to > jbosstools-base (${jbosstools-base-site}): No connector available to > access repository jbosstools-base (${jbosstools-base-site}) of type p2 > using the available factories WagonRepositoryConnectorFactory > Downloading: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/parent-4.2.0.CR1-20140708.134830-2.pom > objc[85943]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Downloaded: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/parent-4.2.0.CR1-20140708.134830-2.pom > (28 KB at 23.2 KB/sec) > Downloading: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml > Downloading: > https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml > Downloaded: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml > (869 B at 1.6 KB/sec) > Downloading: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/jbosstools-unified-4.40.0.CR1-20140713.052635-2-jbosstools-unified.target > Downloaded: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/jbosstools-unified-4.40.0.CR1-20140713.052635-2-jbosstools-unified.target > (32 KB at 30.8 KB/sec) > [WARNING] The POM for > org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-20140714.150948-34 > is missing, no dependency information available > [ERROR] Internal error: java.lang.RuntimeException: > org.apache.maven.MavenExecutionException: Could not setup plugin > ClassRealm: Plugin > org.jboss.tools.tycho-plugins:repository-utils:0.19.0-SNAPSHOT or one > of its dependencies could not be resolved: Failed to read artifact > descriptor for > org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT: > Failure to find > org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 > in https://repository.sonatype.org/content/groups/sonatype-public-grid > was cached in the local repository, resolution will not be reattempted > until the update interval of sonatype-public-grid has elapsed or > updates are forced -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.RuntimeException: org.apache.maven.MavenExecutionException: > Could not setup plugin ClassRealm > 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:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > 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: > org.apache.maven.MavenExecutionException: Could not setup plugin > ClassRealm > at > org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:166) > at > org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:124) > at > org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:87) > at > org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:70) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > ... 11 more > Caused by: org.apache.maven.MavenExecutionException: Could not setup > plugin ClassRealm > at > org.eclipse.tycho.core.maven.utils.PluginRealmHelper.newMavenExecutionException(PluginRealmHelper.java:143) > at > org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:130) > at > org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:146) > ... 16 more > Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin > org.jboss.tools.tycho-plugins:repository-utils:0.19.0-SNAPSHOT or one > of its dependencies could not be resolved: Failed to read artifact > descriptor for > org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT > at > org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) > at > org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at > org.eclipse.tycho.core.maven.utils.MavenCompatiblityHelper.getPluginDescriptor(MavenCompatiblityHelper.java:68) > at > org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:95) > ... 17 more > Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: > Failed to read artifact descriptor for > org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT > at > org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296) > at > org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186) > at > org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:279) > at > org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115) > ... 24 more > Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: > Failure to find > org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 > in https://repository.sonatype.org/content/groups/sonatype-public-grid > was cached in the local repository, resolution will not be reattempted > until the update interval of sonatype-public-grid has elapsed or > updates are forced > at > org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538) > at > org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216) > at > org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193) > at > org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:281) > ... 27 more > Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: > Failure to find > org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 > in https://repository.sonatype.org/content/groups/sonatype-public-grid > was cached in the local repository, resolution will not be reattempted > until the update interval of sonatype-public-grid has elapsed or > updates are forced > at > org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230) > at > org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:204) > at > org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:427) > ... 30 more > [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/InternalErrorException > > > -Martin > > On 21. 7. 2014, at 12:10, Max Rydahl Andersen > wrote: > >> On 21 Jul 2014, at 11:33, Jiri Peterka wrote: >> >>> Hi, >>> >>> there is a broken artifact (no pom file at least, see >>> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/tycho-plugins/repository-utils/0.19.0-SNAPSHOT/repository-utils-0.19.0-20140714.150948-34.pom >>> ) >> >> eh - what is the context here ? >> >> I would not expect any snapshots inside the release repository. >> >> ..also why haven't we released any of these plugins since 0.16 ? >> ...that >> seems unexpected too. >> >> /max >> http://about.me/maxandersen >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From nboldt at redhat.com Mon Jul 21 10:32:28 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 21 Jul 2014 10:32:28 -0400 Subject: [jbosstools-dev] o.j.t.tycho-plugins.repository-utils missing pom In-Reply-To: References: <53CCDE7E.20203@redhat.com> Message-ID: <53CD247C.2090509@redhat.com> See comments in these JIRA: https://issues.jboss.org/browse/JBIDE-17941 https://issues.jboss.org/browse/JBIDE-17942 On 07/21/2014 08:49 AM, Max Rydahl Andersen wrote: > On 21 Jul 2014, at 13:01, Martin Malina wrote: > >> AFAICS, no build that depends on the jboss tools parent pom works. > > eh...thats definitely not supposed to happen. > > Looking into it. > > /max > >> >> Ie. when you try to build jbosstools-server or >> jbosstools-integration-tests, you get this: >> >> nattura:jbosstools-server rasp$ mvn clean verify -DskipTests >> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option >> PermSize=128m; support was removed in 8.0 >> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option >> MaxPermSize=256m; support was removed in 8.0 >> [INFO] Scanning for projects... >> Downloading: >> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml >> Downloading: >> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml >> Downloaded: >> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/maven-metadata.xml >> (606 B at 0.4 KB/sec) >> [WARNING] Could not transfer metadata >> org.jboss.tools:parent:4.2.0.CR1-SNAPSHOT/maven-metadata.xml from/to >> jbosstools-base (${jbosstools-base-site}): No connector available to >> access repository jbosstools-base (${jbosstools-base-site}) of type p2 >> using the available factories WagonRepositoryConnectorFactory >> Downloading: >> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/parent-4.2.0.CR1-20140708.134830-2.pom >> objc[85943]: Class JavaLaunchHelper is implemented in both >> /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/bin/java >> and >> /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre/lib/libinstrument.dylib. >> One of the two will be used. Which one is undefined. >> Downloaded: >> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.CR1-SNAPSHOT/parent-4.2.0.CR1-20140708.134830-2.pom >> (28 KB at 23.2 KB/sec) >> Downloading: >> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml >> Downloading: >> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml >> Downloaded: >> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/maven-metadata.xml >> (869 B at 1.6 KB/sec) >> Downloading: >> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/jbosstools-unified-4.40.0.CR1-20140713.052635-2-jbosstools-unified.target >> Downloaded: >> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbosstools-unified/4.40.0.CR1-SNAPSHOT/jbosstools-unified-4.40.0.CR1-20140713.052635-2-jbosstools-unified.target >> (32 KB at 30.8 KB/sec) >> [WARNING] The POM for >> org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-20140714.150948-34 >> is missing, no dependency information available >> [ERROR] Internal error: java.lang.RuntimeException: >> org.apache.maven.MavenExecutionException: Could not setup plugin >> ClassRealm: Plugin >> org.jboss.tools.tycho-plugins:repository-utils:0.19.0-SNAPSHOT or one >> of its dependencies could not be resolved: Failed to read artifact >> descriptor for >> org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT: >> Failure to find >> org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 >> in https://repository.sonatype.org/content/groups/sonatype-public-grid >> was cached in the local repository, resolution will not be reattempted >> until the update interval of sonatype-public-grid has elapsed or >> updates are forced -> [Help 1] >> org.apache.maven.InternalErrorException: Internal error: >> java.lang.RuntimeException: org.apache.maven.MavenExecutionException: >> Could not setup plugin ClassRealm >> 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:62) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:483) >> 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: >> org.apache.maven.MavenExecutionException: Could not setup plugin >> ClassRealm >> at >> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:166) >> at >> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:124) >> at >> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:87) >> at >> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:70) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> ... 11 more >> Caused by: org.apache.maven.MavenExecutionException: Could not setup >> plugin ClassRealm >> at >> org.eclipse.tycho.core.maven.utils.PluginRealmHelper.newMavenExecutionException(PluginRealmHelper.java:143) >> at >> org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:130) >> at >> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:146) >> ... 16 more >> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin >> org.jboss.tools.tycho-plugins:repository-utils:0.19.0-SNAPSHOT or one >> of its dependencies could not be resolved: Failed to read artifact >> descriptor for >> org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT >> at >> org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) >> at >> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:483) >> at >> org.eclipse.tycho.core.maven.utils.MavenCompatiblityHelper.getPluginDescriptor(MavenCompatiblityHelper.java:68) >> at >> org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:95) >> ... 17 more >> Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: >> Failed to read artifact descriptor for >> org.jboss.tools.tycho-plugins:repository-utils:jar:0.19.0-SNAPSHOT >> at >> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296) >> at >> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186) >> at >> org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:279) >> at >> org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115) >> ... 24 more >> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: >> Failure to find >> org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 >> in https://repository.sonatype.org/content/groups/sonatype-public-grid >> was cached in the local repository, resolution will not be reattempted >> until the update interval of sonatype-public-grid has elapsed or >> updates are forced >> at >> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538) >> at >> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216) >> at >> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193) >> at >> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:281) >> ... 27 more >> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: >> Failure to find >> org.jboss.tools.tycho-plugins:repository-utils:pom:0.19.0-20140714.150948-34 >> in https://repository.sonatype.org/content/groups/sonatype-public-grid >> was cached in the local repository, resolution will not be reattempted >> until the update interval of sonatype-public-grid has elapsed or >> updates are forced >> at >> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230) >> at >> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:204) >> at >> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:427) >> ... 30 more >> [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/InternalErrorException >> >> >> -Martin >> >> On 21. 7. 2014, at 12:10, Max Rydahl Andersen >> wrote: >> >>> On 21 Jul 2014, at 11:33, Jiri Peterka wrote: >>> >>>> Hi, >>>> >>>> there is a broken artifact (no pom file at least, see >>>> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/tycho-plugins/repository-utils/0.19.0-SNAPSHOT/repository-utils-0.19.0-20140714.150948-34.pom >>>> ) >>> >>> eh - what is the context here ? >>> >>> I would not expect any snapshots inside the release repository. >>> >>> ..also why haven't we released any of these plugins since 0.16 ? >>> ...that >>> seems unexpected too. >>> >>> /max >>> http://about.me/maxandersen >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen > > _______________________________________________ > 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 nboldt at redhat.com Tue Jul 22 12:22:27 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 22 Jul 2014 12:22:27 -0400 Subject: [jbosstools-dev] Respin-c planned for tonight Message-ID: <53CE8FC3.5000407@redhat.com> FYI, the usual weekend respin has been replaced by a Tuesday night one. Details here: http://ether-man.rhcloud.com/p/beta3b-review If you are not on this list of 2 JIRAs [1], and need to be, please reply to this thread first explaining why your issue needs to be fixed for Beta3 respin-c. [1] https://issues.jboss.org/issues/?jql=project%20in%20%28JBIDE%2C%20JBDS%29%20AND%20fixVersion%20in%20%284.2.0.Beta3%2C%208.0.0.Beta3%29%20AND%20labels%20in%20%28respin-c%29%20ORDER%20BY%20resolution%20DESC%2C%20labels%20DESC%2C%20updated%20DESC%2C%20component Note too that ideally this will be the last respin for Beta3 -- I am fairly confident we won't need another one this weekend (respin-d). -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Tue Jul 22 15:10:57 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 22 Jul 2014 15:10:57 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta3b bits available for QE testing In-Reply-To: <53C9AC5C.4000908@redhat.com> References: <53C9AC5C.4000908@redhat.com> Message-ID: <53CEB741.5060704@redhat.com> Due to a number of issues, you will need to use a different URL for testing Central/Early Access content. https://issues.jboss.org/browse/JBIDE-17826 https://issues.jboss.org/browse/JBDS-3095 https://issues.jboss.org/browse/JBDS-3094 -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/ This problem will go away when Beta3c is done. On 07/18/2014 07:23 PM, Mickael Istria wrote: > As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. > > Update site:http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3b-updatesite-core/ > > Target platforms:http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4 > > Until the above target platform site is released, you will need to add it to Eclipse to resolve dependencies at install time. > Once released, dependencies will be found automatically from here: > *http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) > *http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta4/ (upcoming milestone) > *http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.Beta4/ (upcoming milestone) > > New + noteworthy (subject to change): > *https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew > *http://tools.jboss.org/documentation/whatsnew/ > > Schedule:https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel > > Additional update sites: > *http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3b-updatesite-coretests/ > *http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3b-updatesite-hibernatetools/ > *http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3b-updatesite-webtools/ > Build sites: > *http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3b-build-core/2014-07-18_16-49-06-B197/ > *http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3b-build-coretests/2014-07-18_16-50-49-B183/ > *http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3b-build-hibernatetools/2014-07-18_17-11-58-B135/ > *http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3b-build-webtools/2014-07-18_17-11-58-B185/ > > Changes prompting this respin-b are: > https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-b%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%228.0.0.Beta3%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.2.0.Beta3%22%29%29%29 > > To compare the upcoming version of Central (${version}) against an older version, add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs: > -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3b/jbosstools-directory.xml > -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3b/ > -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3b/ > > -- > 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 nboldt at redhat.com Wed Jul 23 02:01:24 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 23 Jul 2014 02:01:24 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta3c bits available for QE testing Message-ID: <53CF4FB4.3060607@redhat.com> As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3c-updatesite-core/ Target platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4 (upcoming milestone) Until the above target platform site is released, you will need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta4b-SNAPSHOT/ (upcoming milestone) * http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.Beta4b-SNAPSHOT/ (upcoming milestone) New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Additional update sites & builds: * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3c-updatesite-coretests/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3c-updatesite-hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3c-updatesite-webtools/ * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3c-build-core/2014-07-22_15-40-19-B198 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3c-build-coretests/2014-07-22_15-40-19-B184 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3c-build-hibernatetools/2014-07-22_16-09-46-B136 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta3c-build-webtools/2014-07-22_16-09-46-B186 -- Changes prompting this respin-c are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-c%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%228.0.0.Beta3%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.2.0.Beta3%22%29%29%29 To compare the upcoming version of Central (4.2.0.Beta3c) against an older version, add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3c/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3c/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/development/4.2.0.Beta3c/ -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Thu Jul 24 00:00:37 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Thu, 24 Jul 2014 00:00:37 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201407240400.s6O40bJb032718@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3108 https://issues.jboss.org/browse/JBDS-3108 Summary: Add ability to "always accept" the hostkey of the SSH connection for cloning git repos Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 9:48:09.275116 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From rstryker at redhat.com Thu Jul 24 10:04:02 2014 From: rstryker at redhat.com (Rob Stryker) Date: Thu, 24 Jul 2014 22:04:02 +0800 Subject: [jbosstools-dev] Stacks github repo renamed, packages renamed Message-ID: <53D11252.2030107@redhat.com> https://issues.jboss.org/browse/JBIDE-17965 The stacks urls for stacks.yaml etc have changed. The old URLs still work for now, but I suppose this isn't guaranteed forever. We currently use stacks-client 1.0.0. We currently pull the stacks.yaml url from inside our client. Our client includes the old URL. If we want to continue pulling from the client, then we need a new client. If we update to a new client, we need to deal with changed package names. This will most likely affect stacks, server, and central (I think?) So... 2 options here: 1) I stop pulling stacks.yaml url from the client jar and just hard-code our default url 2) I update to stacks client 1.1.0.CR1, and we deal with changed package names throughout the product. Advice needed. From manderse at redhat.com Thu Jul 24 16:17:11 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 24 Jul 2014 22:17:11 +0200 Subject: [jbosstools-dev] Stacks github repo renamed, packages renamed In-Reply-To: <53D11252.2030107@redhat.com> References: <53D11252.2030107@redhat.com> Message-ID: On 24 Jul 2014, at 16:04, Rob Stryker wrote: > https://issues.jboss.org/browse/JBIDE-17965 > > The stacks urls for stacks.yaml etc have changed. The old URLs still > work for now, but I suppose this isn't guaranteed forever. who says that wont be guaranteed ? > We currently use stacks-client 1.0.0. > > We currently pull the stacks.yaml url from inside our client. Our client > includes the old URL. If we want to continue pulling from the client, > then we need a new client. > > If we update to a new client, we need to deal with changed package > names. This will most likely affect stacks, server, and central (I think?) > > So... 2 options here: > 1) I stop pulling stacks.yaml url from the client jar and just > hard-code our default url thought we did that already ? > 2) I update to stacks client 1.1.0.CR1, and we deal with changed > package names throughout the product. seems wrong they change this api. /max http://about.me/maxandersen From nboldt at redhat.com Thu Jul 24 16:31:36 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 24 Jul 2014 16:31:36 -0400 Subject: [jbosstools-dev] JBT parent pom 4.2.0.CR1-SNAPSHOT updated to use Tycho 0.21 Message-ID: <53D16D28.4090306@redhat.com> Tycho 0.21.0 has been released. Since we already did a bunch of tests last week and found no issues building JBT with it, I've updated the JBT parent pom 4.2.0.CR1-SNAPSHOT to build by default with Tycho 0.21.0. If you encounter any problems, please don't hesitate to comment on this thread or open a JIRA explaining what broke. See also: https://wiki.eclipse.org/Tycho/Release_Notes/0.21 Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Jul 25 16:24:13 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 25 Jul 2014 16:24:13 -0400 Subject: [jbosstools-dev] ACTION REQUIRED :: Unresolved issues for Beta3 for Forge, Hibernate, Website, Usage Message-ID: <53D2BCED.1080501@redhat.com> There are 4 unresolved issues that target a Beta3 release. I don't consider these blocking, so I've left them unresolved w/ a Beta3 target, rather than moving them to CR1. Here's the query: https://issues.jboss.org/issues/?jql=%28project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212324896%22%29%20or%20%28project%20%3D%20JBDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212324895%22%29 Affected projects: * JBIDE-17791 :: Forge (N&N only) * JBIDE-17778 :: Hibernate (N&N only) * JBIDE-17856 :: Website * JBDS-3046 :: Usage tracking / website Two are assigned and can be done Monday or for CR1. The others are unassigned. If you own Forge or Hibernate, please take ownership of these JIRAs and get your N&N completed. Thanks, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Jul 25 17:42:33 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 25 Jul 2014 17:42:33 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta3x -> tag jbosstools-4.2.0.Beta3 ] Message-ID: <53D2CF49.4030904@redhat.com> Project leads, please tag your projects! co jbosstools-4.2.0.Beta3x git tag jbosstools-4.2.0.Beta3 git push origin jbosstools-4.2.0.Beta3 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Jul 25 17:49:29 2014 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 25 Jul 2014 17:49:29 -0400 Subject: [jbosstools-dev] JBoss Tools 4.2.0.Beta3 is now available Message-ID: <53D2D0E9.7000708@redhat.com> This is a development release aimed at Eclipse 4.4 Luna users. Eclipse Marketplace: https://marketplace.eclipse.org/content/jboss-tools-luna Update Site: http://download.jboss.org/jbosstools/updates/development/luna/ Update Site Zips: http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.2.0.x/ Installation instructions: http://tools.jboss.org/downloads/installation.html New + Noteworthy (subject to change): http://tools-stg.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta3.html 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 snjezana.peco at redhat.com Sun Jul 27 15:57:16 2014 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Sun, 27 Jul 2014 21:57:16 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta3x -> tag jbosstools-4.2.0.Beta3 ] In-Reply-To: <53D2CF49.4030904@redhat.com> References: <53D2CF49.4030904@redhat.com> Message-ID: <53D5599C.1030901@redhat.com> Done for arqullian, birt and portlet. Regards, Snjeza On 7/25/2014 11:42 PM, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.2.0.Beta3x > git tag jbosstools-4.2.0.Beta3 > git push origin jbosstools-4.2.0.Beta3 > > From adietish at redhat.com Mon Jul 28 04:31:33 2014 From: adietish at redhat.com (=?ISO-8859-1?Q?Andr=E9_Dietisheim?=) Date: Mon, 28 Jul 2014 10:31:33 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta3x -> tag jbosstools-4.2.0.Beta3 ] In-Reply-To: <53D2CF49.4030904@redhat.com> References: <53D2CF49.4030904@redhat.com> Message-ID: <53D60A65.3080303@redhat.com> On 07/25/2014 11:42 PM, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.2.0.Beta3x > git tag jbosstools-4.2.0.Beta3 > git push origin jbosstools-4.2.0.Beta3 > > done for OpenShift From xcoulon at redhat.com Mon Jul 28 04:40:26 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Mon, 28 Jul 2014 10:40:26 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta3x -> tag jbosstools-4.2.0.Beta3 ] In-Reply-To: <53D2CF49.4030904@redhat.com> References: <53D2CF49.4030904@redhat.com> Message-ID: <58AEB343-747B-40AF-BA4E-1BAE04C329CB@redhat.com> Done for Web Services and LiveReload. Best regards, /Xavier On 25 Jul 2014, at 23:42, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.2.0.Beta3x > git tag jbosstools-4.2.0.Beta3 > git push origin jbosstools-4.2.0.Beta3 > > > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140728/e22fc142/attachment.html From gorkem.ercan at gmail.com Mon Jul 28 04:43:12 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Mon, 28 Jul 2014 11:43:12 +0300 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta3x -> tag jbosstools-4.2.0.Beta3 ] In-Reply-To: <53D2CF49.4030904@redhat.com> References: <53D2CF49.4030904@redhat.com> Message-ID: <20140728084312.GA51494@gmail.com> Done for jbossstools-aerogear. On Fri, Jul 25, 2014 at 05:42:33PM -0400, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.2.0.Beta3x > git tag jbosstools-4.2.0.Beta3 > git push origin jbosstools-4.2.0.Beta3 > > > -- > 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 kmarmaliykov at exadel.com Mon Jul 28 11:43:28 2014 From: kmarmaliykov at exadel.com (Konstantin Marmalyukov) Date: Mon, 28 Jul 2014 18:43:28 +0300 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.0.Beta3x -> tag jbosstools-4.2.0.Beta3 ] In-Reply-To: <53D2CF49.4030904@redhat.com> References: <53D2CF49.4030904@redhat.com> Message-ID: <53D66FA0.30307@exadel.com> VPE and Browsersim - done. On 07/26/2014 12:42 AM, Nick Boldt wrote: > Project leads, please tag your projects! > > co jbosstools-4.2.0.Beta3x > git tag jbosstools-4.2.0.Beta3 > git push origin jbosstools-4.2.0.Beta3 > > From manderse at redhat.com Tue Jul 29 00:01:19 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Tue, 29 Jul 2014 00:01:19 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201407290401.s6T41JjT024041@int-mx09.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-17986 https://issues.jboss.org/browse/JBIDE-17986 Summary: Bundled version of m2e-mavenarchiver is broken Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 10:07:42.710996 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From xcoulon at redhat.com Tue Jul 29 09:53:08 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Tue, 29 Jul 2014 15:53:08 +0200 Subject: [jbosstools-dev] Suggestion needed to improve the JAX-RS change processing and validation Message-ID: <427E16D4-4807-440B-B489-934BC2366534@redhat.com> Hello, I recently opened https://issues.jboss.org/browse/JBIDE-17290 because I realised that since I added the "as-you-type" validation in the JAX-RS tooling, I have two concurrent updates in the JAX-RS model: a JavaElementChangedListener that updates the JAX-RS elements in the model after the user edited a compilation unit, but the 'as-you-type' validator needs to perform the same updates in order to be sure that the validation occurs after the last changes have been taken into account. Actually, the two processes occur in parallel and I have no idea how to make sure that the JavaElementListener-related task is executed and completes before the validation start. I should point that the JavaElementChangedListener is not related to the JAX-RS Builder which is called when a file is saved - that's another story, since there are also updates at this level. I don't want to get rid of the JavaElementChangedListener because the notification event provides me with the modified CompilationUnit AST, which is required for later processing (I don't want to parse the compilation unit unless it's absolutely necessary). Furthermore, it feels weird that the updates would only occur during the validation, so I'd rather avoid such updates in the validator. Do you have any suggestion on how I could simplify and improve this part of the tooling ? Since we're now preparing for CR1, an easy-and-acceptable-by-Max solution would be preferred ;-) How is the situation handled in the CDI tooling ? Thanks for reading this mail and thanks for your help ! Best regards, /Xavier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140729/1ce570b6/attachment.html From glory at exadel.com Tue Jul 29 15:15:51 2014 From: glory at exadel.com (Viacheslav Kabanovich) Date: Tue, 29 Jul 2014 12:15:51 -0700 Subject: [jbosstools-dev] Suggestion needed to improve the JAX-RS change processing and validation In-Reply-To: <427E16D4-4807-440B-B489-934BC2366534@redhat.com> References: <427E16D4-4807-440B-B489-934BC2366534@redhat.com> Message-ID: <53D7F2E7.1090001@exadel.com> Hello, Xavier In CDI, the model is updated only on build. We have cache of Java libraries, which listens to changes in Java classpath with IElementChangedListener and on a change we only mark that the cache is to be updated before the next build (Eclipse starts the build right after listeners are notified about the classpath change). In this way, we only rebuild libraries that are changed. For as-you-type validation, we create each time new CDI model which wraps the main model and for all resources but the one to be validated it just redirects requests to the main model. For the validated resource we call builder with current content. CDI model objects remain unchanged in the main model, but as-you-type validation gets up-to-date objects from the temporary model. All other features, e.g. content assist, search, etc. do not have access to the up-to-date model and get aware of changes only after save/rebuild. If I had to manage model that would change both in build and on unsaved resource modifications, I would have extended this approach with main and wrapper models. Each modification would update model objects for the resource in the wrapper model but would not touch the main model. Build would update model objects for the resource in the main model and cleared that resource from the wrapper model making it to redirect requests to the main model for that resource. The operations to be synchronized would be only those marking resource in wrapper model as either modified (with up-to-date objects associated) or saved (to be requested from the main model). Unfortunately, I see that this will not help you to avoid parsing the compilation unit in as-you-type validator, as it runs in a separate thread and can be called before Java element changed event. In CDI, we do not use CompilationUnit AST, only IType, so that we do not have to parse the source. Best regards, Slava Kabanovich On 07/29/2014 06:53 AM, Xavier Coulon wrote: > Hello, > > I recently opened https://issues.jboss.org/browse/JBIDE-17290 because > I realised that since I added the "as-you-type" validation in the > JAX-RS tooling, I have two concurrent updates in the JAX-RS model: a > JavaElementChangedListener that updates the JAX-RS elements in the > model after the user edited a compilation unit, but the 'as-you-type' > validator needs to perform the same updates in order to be sure that > the validation occurs after the last changes have been taken into > account. Actually, the two processes occur in parallel and I have no > idea how to make sure that the JavaElementListener-related task is > executed and completes before the validation start. I should point > that the JavaElementChangedListener is not related to the JAX-RS > Builder which is called when a file is saved - that's another story, > since there are also updates at this level. > > I don't want to get rid of the JavaElementChangedListener because the > notification event provides me with the modified CompilationUnit AST, > which is required for later processing (I don't want to parse the > compilation unit unless it's absolutely necessary). Furthermore, it > feels weird that the updates would only occur during the validation, > so I'd rather avoid such updates in the validator. > > Do you have any suggestion on how I could simplify and improve this > part of the tooling ? Since we're now preparing for CR1, an > easy-and-acceptable-by-Max solution would be preferred ;-) > > How is the situation handled in the CDI tooling ? > > Thanks for reading this mail and thanks for your help ! > Best regards, > /Xavier > > > > > > _______________________________________________ > 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/20140729/f2e8da73/attachment.html From manderse at redhat.com Wed Jul 30 00:00:38 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Wed, 30 Jul 2014 00:00:38 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 2 issues with no component Message-ID: <201407300400.s6U40cRo005787@int-mx13.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-17990 https://issues.jboss.org/browse/JBIDE-17990 Summary: Organize imports does not work for Maven dependencies Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 12:31:59.618771 ---------------------------- * No component for JBIDE-17986 https://issues.jboss.org/browse/JBIDE-17986 Summary: Bundled version of m2e-mavenarchiver is broken Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 13:45:33.622570 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From xcoulon at redhat.com Wed Jul 30 04:24:47 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Wed, 30 Jul 2014 10:24:47 +0200 Subject: [jbosstools-dev] Suggestion needed to improve the JAX-RS change processing and validation In-Reply-To: <53D7F2E7.1090001@exadel.com> References: <427E16D4-4807-440B-B489-934BC2366534@redhat.com> <53D7F2E7.1090001@exadel.com> Message-ID: <4CBA2068-440B-4751-80C8-2BA6223A6EDA@redhat.com> Hello Slava ! Thanks for your reply. My comments are in-line: On 29 Jul 2014, at 21:15, Viacheslav Kabanovich wrote: > In CDI, the model is updated only on build. We have cache of Java libraries, which listens to changes in Java classpath with IElementChangedListener and on a change we only mark that the cache is to be updated before the next build (Eclipse starts the build right after listeners are notified about the classpath change). In this way, we only rebuild libraries that are changed. > > For as-you-type validation, we create each time new CDI model which wraps the main model and for all resources but the one to be validated it just redirects requests to the main model. For the validated resource we call builder with current content. CDI model objects remain unchanged in the main model, but as-you-type validation gets up-to-date objects from the temporary model. That looks close to the concept of "Working Copies" that JDT uses, and this is something I was about to try, actually. Keeping the "Primary Copy" for a given resource unchanged, and creating a "Working Copy" during the as-you-type-validation. > > All other features, e.g. content assist, search, etc. do not have access to the up-to-date model and get aware of changes only after save/rebuild. That would not work for me. For example: @Path("/") public class CarResource { @PathParam("id") private Integer id; @GET @Path("{id}") public Object getCar() { return null; } } if the user changes @Path("{id}") to something like @Path("{carId}"), then the content assist on the value for @PathParam (on the 'id' field above) should propose "carId" instead of "id". So the model needs to be updated before the resource was changed. > > If I had to manage model that would change both in build and on unsaved resource modifications, I would have extended this approach with main and wrapper models. Each modification would update model objects for the resource in the wrapper model but would not touch the main model. Build would update model objects for the resource in the main model and cleared that resource from the wrapper model making it to redirect requests to the main model for that resource. The operations to be synchronized would be only those marking resource in wrapper model as either modified (with up-to-date objects associated) or saved (to be requested from the main model). > Yes, again, this reminds me the way JDT works with primary copies and working copies, AFAIU. I may consider this option and see how much it impacts the current code. > Unfortunately, I see that this will not help you to avoid parsing the compilation unit in as-you-type validator, as it runs in a separate thread and can be called before Java element changed event. In CDI, we do not use CompilationUnit AST, only IType, so that we do not have to parse the source. I know that the AST is slower to compute, but it includes binding resolution, which is really helpful in cases where the user would use constants instead of String values, for example. And it also helps resolving fully qualified name for Java elements. Best regards, /Xavier > > Best regards, > Slava Kabanovich > > On 07/29/2014 06:53 AM, Xavier Coulon wrote: >> Hello, >> >> I recently opened https://issues.jboss.org/browse/JBIDE-17290 because I realised that since I added the "as-you-type" validation in the JAX-RS tooling, I have two concurrent updates in the JAX-RS model: a JavaElementChangedListener that updates the JAX-RS elements in the model after the user edited a compilation unit, but the 'as-you-type' validator needs to perform the same updates in order to be sure that the validation occurs after the last changes have been taken into account. Actually, the two processes occur in parallel and I have no idea how to make sure that the JavaElementListener-related task is executed and completes before the validation start. I should point that the JavaElementChangedListener is not related to the JAX-RS Builder which is called when a file is saved - that's another story, since there are also updates at this level. >> >> I don't want to get rid of the JavaElementChangedListener because the notification event provides me with the modified CompilationUnit AST, which is required for later processing (I don't want to parse the compilation unit unless it's absolutely necessary). Furthermore, it feels weird that the updates would only occur during the validation, so I'd rather avoid such updates in the validator. >> >> Do you have any suggestion on how I could simplify and improve this part of the tooling ? Since we're now preparing for CR1, an easy-and-acceptable-by-Max solution would be preferred ;-) >> >> How is the situation handled in the CDI tooling ? >> >> Thanks for reading this mail and thanks for your help ! >> Best regards, >> /Xavier >> >> >> >> >> >> _______________________________________________ >> 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/20140730/5249484f/attachment-0001.html From mistria at redhat.com Wed Jul 30 12:07:00 2014 From: mistria at redhat.com (Mickael Istria) Date: Wed, 30 Jul 2014 18:07:00 +0200 Subject: [jbosstools-dev] Release JBoss Tools Tycho plugins 0.21.0 Message-ID: <53D91824.20201@redhat.com> Hi all, I've released version 0.21.0 of our Tycho plugins (for repository facade and target-platforms), which builds and works against Tycho 0.21.0. If you're using Tycho 0.21.0, please update to this version. If you're using an older Tycho version, then you'd rather stay with the 0.19.0-SNAPSHOT version of our plugins (which will remain a SNAPSHOT forever). 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/20140730/379328e3/attachment.html From mistria at redhat.com Wed Jul 30 13:38:23 2014 From: mistria at redhat.com (Mickael Istria) Date: Wed, 30 Jul 2014 19:38:23 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.0.CR1-SNAPSHOT target platform: THyM Message-ID: <53D92D8F.1020308@redhat.com> Here is a proposal for a change to the JBoss Tools 4.40.0.CR1-SNAPSHOT target platform: * https://github.com/jbosstools/jbosstools-target-platforms/pull/80 It consists in the following changes: * JBIDE-17909: Include a snapshot of THyM 0.1.0 p2diff reports are attached to the related JIRA(s). Please review the above PR(s), as it will be applied ASAP. You can use the following to build & test the target-platform locally against your component(s). 1. Build target-platform: $ cd jbosstools-target-platforms $ git fetch origin pull/80/head $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install 2. Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT -Pmultiple.target -- 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/20140730/07d794dd/attachment.html From manderse at redhat.com Wed Jul 30 18:16:29 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 31 Jul 2014 00:16:29 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.0.CR1-SNAPSHOT target platform: THyM In-Reply-To: <53D92D8F.1020308@redhat.com> References: <53D92D8F.1020308@redhat.com> Message-ID: <2B8F8205-22E1-4AF1-BBA7-6C62E99EE670@redhat.com> On 30 Jul 2014, at 19:38, Mickael Istria wrote: > Here is a proposal for a change to the JBoss Tools 4.40.0.CR1-SNAPSHOT > target platform: > * https://github.com/jbosstools/jbosstools-target-platforms/pull/80 > > It consists in the following changes: > * JBIDE-17909: Include a snapshot of THyM 0.1.0 > > p2diff reports are attached to the related JIRA(s). > > Please review the above PR(s), as it will be applied ASAP. > You can use the following to build & test the target-platform locally > against your component(s). > 1. Build target-platform: > $ cd jbosstools-target-platforms > $ git fetch origin pull/80/head > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple > $ mvn clean install > 2. Try with just built target-platform: > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT -Pmultiple.target > -- > 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 I haven't tested the build but just reviewed the list and looks good. Got question about updates but that is in the jira. /max http://about.me/maxandersen From manderse at redhat.com Wed Jul 30 18:19:01 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 31 Jul 2014 00:19:01 +0200 Subject: [jbosstools-dev] Release JBoss Tools Tycho plugins 0.21.0 In-Reply-To: <53D91824.20201@redhat.com> References: <53D91824.20201@redhat.com> Message-ID: <5D905477-A040-45D5-9543-65E3390B65E8@redhat.com> On 30 Jul 2014, at 18:07, Mickael Istria wrote: > Hi all, > > I've released version 0.21.0 of our Tycho plugins (for repository > facade and target-platforms), which builds and works against Tycho > 0.21.0. > If you're using Tycho 0.21.0, please update to this version. > If you're using an older Tycho version, then you'd rather stay with > the 0.19.0-SNAPSHOT version of our plugins (which will remain a > SNAPSHOT forever). how ? wont it get deleted after ~30-90 days when we stop building it ? /max http://about.me/maxandersen From nboldt at redhat.com Wed Jul 30 18:31:00 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 30 Jul 2014 18:31:00 -0400 Subject: [jbosstools-dev] Release JBoss Tools Tycho plugins 0.21.0 In-Reply-To: <5D905477-A040-45D5-9543-65E3390B65E8@redhat.com> References: <53D91824.20201@redhat.com> <5D905477-A040-45D5-9543-65E3390B65E8@redhat.com> Message-ID: <53D97224.706@redhat.com> Note that snapshots have a bad habit of being periodically purged from Nexus, and Tycho 0.21 is better than 0.19 or 0.20, so... at your earliest convenience it's recommended that you move up to using both Tycho 0.21.0 and our tycho-plugins 0.21.0 too. These will be set as the defaults in the parent pom, but if you're overriding that, or not using that, YMMV. On 07/30/2014 06:19 PM, Max Rydahl Andersen wrote: > On 30 Jul 2014, at 18:07, Mickael Istria wrote: > >> Hi all, >> >> I've released version 0.21.0 of our Tycho plugins (for repository >> facade and target-platforms), which builds and works against Tycho >> 0.21.0. >> If you're using Tycho 0.21.0, please update to this version. >> If you're using an older Tycho version, then you'd rather stay with >> the 0.19.0-SNAPSHOT version of our plugins (which will remain a >> SNAPSHOT forever). > > how ? wont it get deleted after ~30-90 days when we stop building it ? > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Thu Jul 31 03:14:32 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 31 Jul 2014 09:14:32 +0200 Subject: [jbosstools-dev] Release JBoss Tools Tycho plugins 0.21.0 In-Reply-To: <5D905477-A040-45D5-9543-65E3390B65E8@redhat.com> References: <53D91824.20201@redhat.com> <5D905477-A040-45D5-9543-65E3390B65E8@redhat.com> Message-ID: <53D9ECD8.2020908@redhat.com> On 07/31/2014 12:19 AM, Max Rydahl Andersen wrote: >> If you're using an older Tycho version, then you'd rather stay with >> the 0.19.0-SNAPSHOT version of our plugins (which will remain a >> SNAPSHOT forever). > > how ? wont it get deleted after ~30-90 days when we stop building it ? Yes, it will be deleted, and if necessary we'll deploy it again (as a 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/20140731/52dbad92/attachment.html From nboldt at redhat.com Thu Jul 31 12:44:26 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 31 Jul 2014 12:44:26 -0400 Subject: [jbosstools-dev] ACTION REQUIRED :: Copyright and provider name verification Message-ID: <53DA726A.3010906@redhat.com> There have been a number of new plugins and features added this year, and many more which have been updated since last year. As such, those files which have changed need to be updated to bear a copyright date ending in 2014. You can also update ALL your files to 2014 (if you'd like) but files which have NOT changed need not be updated. Note too that if a plugin is new/updated this year, its containing feature(s) must also be updated to this year's copyright date, even if nothing has changed in that feature other than its children. Here are 19 task JIRAs to track this activity: JBDS : https://issues.jboss.org/browse/JBDS-3114 JBoss Tools : https://issues.jboss.org/browse/JBIDE-18010 Aerogear : https://issues.jboss.org/browse/JBIDE-18011 JST : https://issues.jboss.org/browse/JBIDE-18012 VPE : https://issues.jboss.org/browse/JBIDE-18013 Server : https://issues.jboss.org/browse/JBIDE-18014 Hibernate : https://issues.jboss.org/browse/JBIDE-18015 Base : https://issues.jboss.org/browse/JBIDE-18016 OpenShift : https://issues.jboss.org/browse/JBIDE-18017 JavaEE : https://issues.jboss.org/browse/JBIDE-18018 Birt : https://issues.jboss.org/browse/JBIDE-18019 Forge : https://issues.jboss.org/browse/JBIDE-18020 BrowserSim : https://issues.jboss.org/browse/JBIDE-18021 Webservices : https://issues.jboss.org/browse/JBIDE-18022 Arquillian : https://issues.jboss.org/browse/JBIDE-18023 Central : https://issues.jboss.org/browse/JBIDE-18024 Portlet : https://issues.jboss.org/browse/JBIDE-18025 Freemarker : https://issues.jboss.org/browse/JBIDE-18026 LiveReload : https://issues.jboss.org/browse/JBIDE-18027 Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com