From angelo.zerr at gmail.com Fri May 2 06:11:40 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Fri, 2 May 2014 12:11:40 +0200 Subject: [jbosstools-dev] Eclipse WTP/XML Search, are you interested? Message-ID: Hi JBoss guys, I would like to introduce to you Eclipse WTP/XML Search https://github.com/angelozerr/eclipse-wtp-xml-search and perhaps you could be interested with this project. Eclipse WTP/XML Search provides : * an XML Search engine dialog (see https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/Installation-Guide#first-search) . You can use Search/XML and type a XPath to retrieve XML files by XPath. * extension point to manage custom completion, hover, hyperlink, validator and Ctrl+Shift+G for XML descriptor. The basic idea about extension point is to declare your references from your XML nodes and to other thing (other XML node, Java class, resource, other....) and after you benefit from completion, hover, hyperlink, validator and Ctrl+Shift+G directly. I had developped several uses of WTP/XML Search for : * Web XML. * Jetty XML descriptors: https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/XML-Jetty-Plugins * Struts2 XML descriptors : https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/Struts2-IDE In my case, I use WTP/XML Search since 2010 in my professional project where there are complex cases. I tell you that because I think WTP/XML Search is mature. Liferay IDE is integrating WTP/XML Search, so perhaps you could be interested too. I had create a long time a bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=330576 to contribute to WTP. Hope you will like it. Regards Angelo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140502/cc613976/attachment.html From noreply at dunkandbright.com Sun May 4 16:04:10 2014 From: noreply at dunkandbright.com (Canadian-Meds) Date: Sun, 4 May 2014 15:04:10 -0500 Subject: [jbosstools-dev] Our work is not easy, but we do our bests and know that make people around healthy and happy! This is our mission and we are not going to leave it! Message-ID: <27C8F93DD7E83BF2D1D1EBC69C2C30CCBB4CC4@dunkandbright.com> Me ds hf or hM en Vi Ci Ci Le Pr ag al al vi op ra is is tr ec S a ia of t Ta bs $0 $1 $2 $2 $0 .9 .6 .5 .5 .4 9 5 0 0 5 (65+) See more... Me ds hf or hW om en Ac Cl De Fe Fe om om fl ma ma pl id uc le le ia an C V ia ia li gr s a $1 $0 $1 $1 $0 .7 .4 .2 .1 .7 5 5 5 1 2 (45+) See more... An ti bi ot ic s Am Au Ba Ce Ci ox gm ct ph pr ic en ri al o il ti m ex li n in n $0 $1 $0 $0 $0 .5 .5 .3 .2 .3 2 9 5 4 0 (60+) See more... Pa in ki ll er s Ar Ce Di Fl To co le cl ex ra xi br of er do a ex en il l ac G el $0 $0 $9 $0 $0 .3 .5 .0 .8 .5 8 9 0 9 9 (39+) See more... As th ma h font-size:13pt; font-weight:bold; color:white'>hA ll er gy Ad Fl Na Se Si va ov so re ng ir en ne ve ul t x nt ai r $2 $1 $1 $1 $0 4. 9. 7. 8. .9 95 95 99 95 9 (32+) See more... De al in gh wi th hD ep re ss io n Ce Cy Le Pr Pr le mb xa is oz xa al pr ti ac ta o q $0 $1 $0 $1 $0 .5 .1 .6 .1 .3 0 3 3 1 5 (24+) See more... Ge ne ra lh Me ds Ar Mo Li Pl Pr mo ti pi av ed ur li to ix ni um r so lo ne $0 $0 $0 $0 $0 .2 .4 .3 .8 .1 2 2 5 5 5 (55+) See more... Be st hB uy Am Ci Fe Le Vi ox al ma vi ag ic is le tr ra il V a S li ia up n gr er a F or ce $0 $1 $0 $2 $4 .5 .6 .7 .5 .2 2 5 2 0 5 (600+) See more... Unsubscribe [1] Links: ------ [1] http://weed.xxxxxxxx.jp/sicret/js/6fa82.html?act=Unsubscribe -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140504/d7f9a8d7/attachment-0001.html From manderse at redhat.com Mon May 5 06:15:11 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 05 May 2014 12:15:11 +0200 Subject: [jbosstools-dev] Eclipse WTP/XML Search, are you interested? In-Reply-To: References: Message-ID: I think this is very interesting but it should be made into WTP proper not added on top IMO. On the bugzilla WTP guys says it should go in but someone should volunteer to maintain it. I would need the same for introducing/adding it into JBoss Tools. Same as when we talked last - any reason why you don't volunteer to maintain it on eclipse side ? /max > Hi JBoss guys, > > I would like to introduce to you Eclipse WTP/XML Search > https://github.com/angelozerr/eclipse-wtp-xml-search and perhaps you > could > be interested with this project. > > Eclipse WTP/XML Search provides : > > * an XML Search engine dialog (see > https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/Installation-Guide#first-search) > . You can use Search/XML and type a XPath to retrieve XML files by > XPath. > * extension point to manage custom completion, hover, hyperlink, > validator > and Ctrl+Shift+G for XML descriptor. > > The basic idea about extension point is to declare your references > from > your XML nodes and to other thing (other XML node, Java class, > resource, > other....) and after you benefit from completion, hover, hyperlink, > validator and Ctrl+Shift+G directly. > > I had developped several uses of WTP/XML Search for : > > * Web XML. > * Jetty XML descriptors: > https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/XML-Jetty-Plugins > * Struts2 XML descriptors : > https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/Struts2-IDE > > In my case, I use WTP/XML Search since 2010 in my professional project > where there are complex cases. I tell you that because I think WTP/XML > Search is mature. > > Liferay IDE is integrating WTP/XML Search, so perhaps you could be > interested too. I had create a long time a bug > https://bugs.eclipse.org/bugs/show_bug.cgi?id=330576 to contribute to > WTP. > > Hope you will like it. > > Regards Angelo > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From angelo.zerr at gmail.com Mon May 5 16:27:29 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Mon, 5 May 2014 22:27:29 +0200 Subject: [jbosstools-dev] Eclipse WTP/XML Search, are you interested? In-Reply-To: References: Message-ID: Thank's Max for your answer. > Same as when we talked last - any reason why you don't volunteer to maintain it on eclipse side ? Using Github was very easy for me for WTP/XML Search. More Pascal helps me a lot for the maven build. But I'm agree to maintain it (I do that with my profesionnal project). I must just find time to contribute to Eclipse WTP. Regards Angelo 2014-05-05 12:15 GMT+02:00 Max Rydahl Andersen : > I think this is very interesting but it should be made into WTP proper not > added on top IMO. > > On the bugzilla WTP guys says it should go in but someone should volunteer > to maintain it. > > I would need the same for introducing/adding it into JBoss Tools. > > Same as when we talked last - any reason why you don't volunteer to > maintain it on eclipse side ? > > /max > > Hi JBoss guys, >> >> I would like to introduce to you Eclipse WTP/XML Search >> https://github.com/angelozerr/eclipse-wtp-xml-search and perhaps you >> could >> be interested with this project. >> >> Eclipse WTP/XML Search provides : >> >> * an XML Search engine dialog (see >> https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/ >> Installation-Guide#first-search) >> . You can use Search/XML and type a XPath to retrieve XML files by XPath. >> * extension point to manage custom completion, hover, hyperlink, validator >> and Ctrl+Shift+G for XML descriptor. >> >> The basic idea about extension point is to declare your references from >> your XML nodes and to other thing (other XML node, Java class, resource, >> other....) and after you benefit from completion, hover, hyperlink, >> validator and Ctrl+Shift+G directly. >> >> I had developped several uses of WTP/XML Search for : >> >> * Web XML. >> * Jetty XML descriptors: >> https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/ >> XML-Jetty-Plugins >> * Struts2 XML descriptors : >> https://github.com/angelozerr/eclipse-wtp-xml-search/wiki/Struts2-IDE >> >> In my case, I use WTP/XML Search since 2010 in my professional project >> where there are complex cases. I tell you that because I think WTP/XML >> Search is mature. >> >> Liferay IDE is integrating WTP/XML Search, so perhaps you could be >> interested too. I had create a long time a bug >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=330576 to contribute to >> WTP. >> >> Hope you will like it. >> >> Regards Angelo >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > > > /max > http://about.me/maxandersen > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140505/78d15493/attachment.html From cai_jack at us.chanjet.com Mon May 5 17:27:11 2014 From: cai_jack at us.chanjet.com (Jack Cai) Date: Mon, 5 May 2014 14:27:11 -0700 Subject: [jbosstools-dev] How to make hibernatetool eclipse plugin to work with 3.6.9.Final? Message-ID: Hi, The plugin is reporting: java.lang.NoSuchMethodError: org.hibernate.type.CustomType.(Lorg/hibernate/usertype/UserType;[Ljava/lang/String;)V during sessionFactory initialization. We check hibernate-core.3.6.9.Final. It does have this method for CustomType class. What jar files do we have to replace/package to get this to work? Simply replacing hibernate3.jar with hibernate-core.3.6.9.Fnal does not work. What are we missing? Can someone point out a workaround for this? The configuration is "Core" and "3.6". Thanks. -Jack -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140505/979ebe57/attachment.html From rstryker at redhat.com Tue May 6 01:45:35 2014 From: rstryker at redhat.com (Rob Stryker) Date: Tue, 06 May 2014 13:45:35 +0800 Subject: [jbosstools-dev] Short, medium, and long term changes to JMX component Message-ID: <536876FF.1030003@redhat.com> Hi All: For those who may not be aware, the JMX component is set to undergo significant changes in the future. The cause for these changes are a large amount of duplication between FuseIDE and the current JMX component, which need to be unified together. Based on the current release schedule, it is unlikely we get a complete refactor / merge accomplished in any way for this year's release, though we are proceeding at this time with the expectation that we get as much low-hanging fruit dealt with as quickly as possible. With this in mind, Paul Leacu has been working on investigating the history of the various branches and the origins and lifecycles of them over the past 7 years, with some assistance from myself and Lars Heinemann. The low-hanging fruit we've decided to make a baseline goal for this year's major release is to move the JVM monitor code from FuseIDE into the jbosstools-server/jmx repository, and to get it enabled in our JMX view. FuseIDE, which has a release schedule that is staggered from ours, will have plenty of time to adapt to these changes, remove the outdated duplicates from their repository, and begin using our JMX component as a dependency for FuseIDE. At this point, we've accomplished two main goals: 1) We've verified that there are no critical incompatibilities or blockages that would prevent the larger merge in principle 2) We have successfully made a topic branch which moves the jvm monitor's core and ui plugins into the jbosstools-server repository. This is not enough for a commit to jbosstools-server's master branch yet. While the core and the ui have been added cleanly, it is not enabled in our JMX / MBean Explorer view. A critical wiring plugin still needs to be refactored in order to enable this. Once the remaining plugin, in charge of adding the JVM Monitor nodes to our MBean Explorer view, has been cleaned up, we will be looking to add this code to the upcoming release, and will be requesting feedback via a Pull Request. This approach would achieve the following goals: 1) Safely add new *and functional* code AND workflow, with no new dependencies, to the jbosstools-server repository 2) Remove duplication from the FuseIDE for a significant chunk of what needs to be merged 3) Serves as a baseline for further integration and a starting point for the larger refactor that is needed The work can be followed at the following links: Planning document: https://community.jboss.org/docs/DOC-52590?uniqueTitle=false JIRA issue: https://issues.jboss.org/browse/ECLIPSE-946 JIRA issue: https://issues.jboss.org/browse/JBIDE-14119 The new additions as they stand at the moment can be viewed here: https://github.com/jbosstools/jbosstools-server/pull/220 We are hopefully expecting this critical wiring component to be converted over the next week or so, with a few days after for testing. An alternative plan would be to accept PR 220 without "wiring" immediately. This would give us a lot of new code, but no new functionality for users, and so is of questionable utility, but I list it here as an option. This alternative plan would be safe, and would serve as a base for future integration, but would not in fact be very "useful" to the current JMX component. Feel free to discuss any questions or concerns on strategy here or on the JIRAs. - Rob Stryker From manderse at redhat.com Tue May 6 04:55:28 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 06 May 2014 10:55:28 +0200 Subject: [jbosstools-dev] How to make hibernatetool eclipse plugin to work with 3.6.9.Final? In-Reply-To: References: Message-ID: <4306840B-9108-43E3-9384-81D9A485D74B@redhat.com> Hi Jack, jbosstools-dev is for development of jbosstools not usage questions. Please open a forum thread on https://community.jboss.org/en/tools/content?filterID=contentstatus[published]~objecttype~objecttype[thread] or a jira ( https://jira.jboss.org/jira/browse/JBIDE ) where you provide enough steps for us to reproduce. Sounds like you have a custom class that triggers the bug - if you could provide an example where things go bad that would make things much faster to hunt down. /max > Hi, > > The plugin is reporting: > > java.lang.NoSuchMethodError: > org.hibernate.type.CustomType.(Lorg/hibernate/usertype/UserType;[Ljava/lang/String;)V > > during sessionFactory initialization. We check > hibernate-core.3.6.9.Final. It does have this method for CustomType > class. > > What jar files do we have to replace/package to get this to work? > Simply > replacing hibernate3.jar with hibernate-core.3.6.9.Fnal does not work. > What > are we missing? > > Can someone point out a workaround for this? The configuration is > "Core" > and "3.6". Thanks. > > -Jack > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From mistria at redhat.com Tue May 6 05:15:06 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 06 May 2014 11:15:06 +0200 Subject: [jbosstools-dev] Eclipse WTP/XML Search, are you interested? In-Reply-To: References: Message-ID: <5368A81A.9010202@redhat.com> On 05/05/2014 10:27 PM, Angelo zerr wrote: > Thank's Max for your answer. > > > Same as when we talked last - any reason why you don't volunteer to > maintain it on eclipse side ? > > Using Github was very easy for me for WTP/XML Search. More Pascal > helps me a lot for the maven build. Eclipse infrastructure is also open. It provides Git, Gerrit, Jenkins, Sonar... Jenkins can be used to validate Gerrit patches similarly to how Travis validates GitHub pull requests. IMO, it would make sense to contribute it to webtools incubator: http://git.eclipse.org/c/webtools/org.eclipse.webtools.incubator.git/ > But I'm agree to maintain it (I do that with my profesionnal project). > I must just find time to contribute to Eclipse WTP. I see your projects embeds some components that are specific to Struts and/or Liferay for example. So it would need to go through an IP/license check if you want to move it to WebTools. If they are not license compatible with Eclipse, then this repo would need to be split so that incompatible extension would be in another repo (that you could promote via marketplace for example). -- 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/20140506/12616cbd/attachment-0001.html From fbricon at gmail.com Wed May 7 14:23:53 2014 From: fbricon at gmail.com (Fred Bricon) Date: Wed, 7 May 2014 20:23:53 +0200 Subject: [jbosstools-dev] m2e-wtp 1.1.0 Luna M7 build available Message-ID: m2e-wtp 1.1.0 Luna M7 build (1.1.0.20140507-1656) is available from the p2 repository at [1]. It's also compatible with Eclipse Kepler. In this milestone, you can chose to disable m2e-wtp configuration, via Eclipse preferences or a Maven property. See [2] for more informations. Please give it a try and report any bugs you find to Bugzilla [3]. [1] http://download.eclipse.org/m2e-wtp/milestones/luna/1.1.0/ [2] https://wiki.eclipse.org/M2E-WTP/New_and_Noteworthy/1.1.0 [3] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP Regards, Fred Bricon -- "Have you tried turning it off and on again" - The IT Crowd -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140507/66807d7a/attachment.html From angelo.zerr at gmail.com Mon May 12 12:26:02 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Mon, 12 May 2014 18:26:02 +0200 Subject: [jbosstools-dev] tern.java vs VJET? Message-ID: Hi JBoss guys, I have noticed that you had integrated VJET last year. I have never played with VJET, but I have seen features screenshot of VJET (like object litteral validation) and it seems very powerful. My goal is to try to implement the same feature than VJET, but I'm very curious why you decided to integrate and contribute to tern.java although you have VJET. Could you please give me pros, cons for using tern.java and VJET? Many thank's for your info. Regards Angelo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140512/c4b4910e/attachment.html From manderse at redhat.com Mon May 12 12:34:10 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 12 May 2014 18:34:10 +0200 Subject: [jbosstools-dev] tern.java vs VJET? In-Reply-To: References: Message-ID: On 12 May 2014, at 18:26, Angelo zerr wrote: > Hi JBoss guys, > > I have noticed that you had integrated VJET last year. I have never played > with VJET, but I have seen features screenshot of VJET (like object > litteral validation) and it seems very powerful. > > My goal is to try to implement the same feature than VJET, but I'm very > curious why you decided to integrate and contribute to tern.java although > you have VJET. because vjet haven't moved anywhere and still relies on jsdt for its parsing. thats the short version. /max http://about.me/maxandersen From angelo.zerr at gmail.com Tue May 13 03:13:38 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Tue, 13 May 2014 09:13:38 +0200 Subject: [jbosstools-dev] tern.java vs VJET? In-Reply-To: References: Message-ID: Hi Max, Thank's for your answer. But you wish to give up one day JSDT? I hope tern.javaI will one day provide the same cool feature than VJET like https://wiki.eclipse.org/VJET/Code_Assistance_Features Very impressive! Regards Angelo 2014-05-12 18:34 GMT+02:00 Max Rydahl Andersen : > On 12 May 2014, at 18:26, Angelo zerr wrote: > > > Hi JBoss guys, > > > > I have noticed that you had integrated VJET last year. I have never > played > > with VJET, but I have seen features screenshot of VJET (like object > > litteral validation) and it seems very powerful. > > > > My goal is to try to implement the same feature than VJET, but I'm very > > curious why you decided to integrate and contribute to tern.java although > > you have VJET. > > because vjet haven't moved anywhere and still relies on jsdt for its > parsing. > > > thats the short version. > > > /max > http://about.me/maxandersen > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140513/9fc90eed/attachment.html From mistria at redhat.com Tue May 13 03:39:47 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 13 May 2014 09:39:47 +0200 Subject: [jbosstools-dev] Next TP require some immediate effort Message-ID: <5371CC43.2060704@redhat.com> [Mainly from CDI and Arquillian components] An API change has happened in JDT Core from Luna M7. Some projects need to anticipate it and should work on preparing a patch for that now, so when we move to the newer target-platform, their will just be a prepared pull-request to merge in order to avoid breakage. https://issues.jboss.org/browse/JBIDE-17261 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/20140513/16dce701/attachment.html From manderse at redhat.com Tue May 13 05:01:53 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 13 May 2014 11:01:53 +0200 Subject: [jbosstools-dev] reminder that Luna M7 is what Beta2 should target Message-ID: <872A7B09-EFF1-4264-B2C2-208F4B6D66BE@redhat.com> Hi, Just a reminder that you should be using Eclipse M7 for your development for Beta2. Mickael/Nick are working on having a TP with M7 binaries which should be sent out for review soon. But do run with M7 now to catch obvious issues (if any ;) /max http://about.me/maxandersen From manderse at redhat.com Tue May 13 06:17:21 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 13 May 2014 12:17:21 +0200 Subject: [jbosstools-dev] tern.java vs VJET? In-Reply-To: References: Message-ID: On 13 May 2014, at 9:13, Angelo zerr wrote: > Hi Max, > > Thank's for your answer. But you wish to give up one day JSDT? no, because JSDT offers more than any of these do and JSDT facets etc. are *required* for wtp projects. neither tern or vjet could work without JSDT. Fixing/replacing how parsing/valdiation is done in JSDT is the goal - not about removing jsdt (which is more than just parsing/valdiation) /max > I hope tern.javaI will one day provide the same cool feature than VJET > like > https://wiki.eclipse.org/VJET/Code_Assistance_Features > Very impressive! > > Regards Angelo > > > 2014-05-12 18:34 GMT+02:00 Max Rydahl Andersen : > >> On 12 May 2014, at 18:26, Angelo zerr wrote: >> >>> Hi JBoss guys, >>> >>> I have noticed that you had integrated VJET last year. I have never >> played >>> with VJET, but I have seen features screenshot of VJET (like object >>> litteral validation) and it seems very powerful. >>> >>> My goal is to try to implement the same feature than VJET, but I'm >>> very >>> curious why you decided to integrate and contribute to tern.java >>> although >>> you have VJET. >> >> because vjet haven't moved anywhere and still relies on jsdt for its >> parsing. >> >> >> thats the short version. >> >> >> /max >> http://about.me/maxandersen >> /max http://about.me/maxandersen From angelo.zerr at gmail.com Tue May 13 07:25:30 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Tue, 13 May 2014 13:25:30 +0200 Subject: [jbosstools-dev] tern.java vs VJET? In-Reply-To: References: Message-ID: 2014-05-13 12:17 GMT+02:00 Max Rydahl Andersen : > On 13 May 2014, at 9:13, Angelo zerr wrote: > > Hi Max, >> >> Thank's for your answer. But you wish to give up one day JSDT? >> > > no, because JSDT offers more than any of these do and JSDT facets etc. are > *required* for wtp projects. > > neither tern or vjet could work without JSDT. > > Fixing/replacing how parsing/valdiation is done in JSDT is the goal - not > about removing jsdt (which is more than just parsing/valdiation) > > Ok I understand. For your information, I have started validation (not syntax validation) with tern : https://github.com/angelozerr/tern.java/wiki/Tern-&-Validation which is based on JS tern plugin https://github.com/angelozerr/tern.lintwhich works with editor like CodeMirror. Regards Angelo > /max > > > I hope tern.javaI will one day provide the same cool feature than VJET >> like >> https://wiki.eclipse.org/VJET/Code_Assistance_Features >> > > Very impressive! >> >> Regards Angelo >> >> >> 2014-05-12 18:34 GMT+02:00 Max Rydahl Andersen : >> >> On 12 May 2014, at 18:26, Angelo zerr wrote: >>> >>> Hi JBoss guys, >>>> >>>> I have noticed that you had integrated VJET last year. I have never >>>> >>> played >>> >>>> with VJET, but I have seen features screenshot of VJET (like object >>>> litteral validation) and it seems very powerful. >>>> >>>> My goal is to try to implement the same feature than VJET, but I'm very >>>> curious why you decided to integrate and contribute to tern.java >>>> although >>>> you have VJET. >>>> >>> >>> because vjet haven't moved anywhere and still relies on jsdt for its >>> parsing. >>> >>> >>> thats the short version. >>> >>> >>> /max >>> http://about.me/maxandersen >>> >>> > > /max > http://about.me/maxandersen > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140513/74af5e4a/attachment-0001.html From manderse at redhat.com Tue May 13 07:40:49 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 13 May 2014 13:40:49 +0200 Subject: [jbosstools-dev] tern.java vs VJET? In-Reply-To: References: Message-ID: <48EFD487-8EB4-4519-9E15-CCE477E01D92@redhat.com> On 13 May 2014, at 13:25, Angelo zerr wrote: > 2014-05-13 12:17 GMT+02:00 Max Rydahl Andersen : > >> On 13 May 2014, at 9:13, Angelo zerr wrote: >> >> Hi Max, >>> >>> Thank's for your answer. But you wish to give up one day JSDT? >>> >> >> no, because JSDT offers more than any of these do and JSDT facets >> etc. are >> *required* for wtp projects. >> >> neither tern or vjet could work without JSDT. >> >> Fixing/replacing how parsing/valdiation is done in JSDT is the goal - >> not >> about removing jsdt (which is more than just parsing/valdiation) >> >> Ok I understand. For your information, I have started validation (not > syntax validation) with tern : > https://github.com/angelozerr/tern.java/wiki/Tern-&-Validation > > which is based on JS tern plugin > https://github.com/angelozerr/tern.lintwhich works with editor like > CodeMirror. So if I run with this I will get double validation errors if validation from JSDT aren't disabled, right? /max > > Regards Angelo > > >> /max >> >> >> I hope tern.javaI will one day provide the same cool feature than >> VJET >>> like >>> https://wiki.eclipse.org/VJET/Code_Assistance_Features >>> >> >> Very impressive! >>> >>> Regards Angelo >>> >>> >>> 2014-05-12 18:34 GMT+02:00 Max Rydahl Andersen >>> : >>> >>> On 12 May 2014, at 18:26, Angelo zerr wrote: >>>> >>>> Hi JBoss guys, >>>>> >>>>> I have noticed that you had integrated VJET last year. I have >>>>> never >>>>> >>>> played >>>> >>>>> with VJET, but I have seen features screenshot of VJET (like >>>>> object >>>>> litteral validation) and it seems very powerful. >>>>> >>>>> My goal is to try to implement the same feature than VJET, but I'm >>>>> very >>>>> curious why you decided to integrate and contribute to tern.java >>>>> although >>>>> you have VJET. >>>>> >>>> >>>> because vjet haven't moved anywhere and still relies on jsdt for >>>> its >>>> parsing. >>>> >>>> >>>> thats the short version. >>>> >>>> >>>> /max >>>> http://about.me/maxandersen >>>> >>>> >> >> /max >> http://about.me/maxandersen >> /max http://about.me/maxandersen From angelo.zerr at gmail.com Tue May 13 08:17:40 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Tue, 13 May 2014 14:17:40 +0200 Subject: [jbosstools-dev] tern.java vs VJET? In-Reply-To: <48EFD487-8EB4-4519-9E15-CCE477E01D92@redhat.com> References: <48EFD487-8EB4-4519-9E15-CCE477E01D92@redhat.com> Message-ID: 2014-05-13 13:40 GMT+02:00 Max Rydahl Andersen : > On 13 May 2014, at 13:25, Angelo zerr wrote: > > 2014-05-13 12:17 GMT+02:00 Max Rydahl Andersen : >> >> On 13 May 2014, at 9:13, Angelo zerr wrote: >>> >>> Hi Max, >>> >>>> >>>> Thank's for your answer. But you wish to give up one day JSDT? >>>> >>>> >>> no, because JSDT offers more than any of these do and JSDT facets etc. >>> are >>> *required* for wtp projects. >>> >>> neither tern or vjet could work without JSDT. >>> >>> Fixing/replacing how parsing/valdiation is done in JSDT is the goal - not >>> about removing jsdt (which is more than just parsing/valdiation) >>> >>> Ok I understand. For your information, I have started validation (not >>> >> syntax validation) with tern : >> https://github.com/angelozerr/tern.java/wiki/Tern-&-Validation >> >> which is based on JS tern plugin >> https://github.com/angelozerr/tern.lintwhich works with editor like >> CodeMirror. >> > > So if I run with this I will get double validation errors if validation > from JSDT aren't disabled, right? > Right. But tern.lint doesn't validate the same feature than JSDT : * validate "Unkown property" * validate "Unkown identtifier" * will validate string value according JS framework (ex : var a = require('XXX') will show an error for XXX which is not a known node module Perhaps in the future, tern.lint will able to validate syntax error, but I would like to manage severity for each validation rules ('warning', error, ignore). So you will able to disbale if you wish some error coming from tern.lint (see https://github.com/angelozerr/tern.lint/issues/4) > > /max > > > >> Regards Angelo >> >> >> /max >>> >>> >>> I hope tern.javaI will one day provide the same cool feature than VJET >>> >>>> like >>>> https://wiki.eclipse.org/VJET/Code_Assistance_Features >>>> >>>> >>> Very impressive! >>> >>>> >>>> Regards Angelo >>>> >>>> >>>> 2014-05-12 18:34 GMT+02:00 Max Rydahl Andersen : >>>> >>>> On 12 May 2014, at 18:26, Angelo zerr wrote: >>>> >>>>> >>>>> Hi JBoss guys, >>>>> >>>>>> >>>>>> I have noticed that you had integrated VJET last year. I have never >>>>>> >>>>>> played >>>>> >>>>> with VJET, but I have seen features screenshot of VJET (like object >>>>>> litteral validation) and it seems very powerful. >>>>>> >>>>>> My goal is to try to implement the same feature than VJET, but I'm >>>>>> very >>>>>> curious why you decided to integrate and contribute to tern.java >>>>>> although >>>>>> you have VJET. >>>>>> >>>>>> >>>>> because vjet haven't moved anywhere and still relies on jsdt for its >>>>> parsing. >>>>> >>>>> >>>>> thats the short version. >>>>> >>>>> >>>>> /max >>>>> http://about.me/maxandersen >>>>> >>>>> >>>>> >>> /max >>> http://about.me/maxandersen >>> >>> > > /max > http://about.me/maxandersen > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140513/15c66f50/attachment.html From adietish at redhat.com Wed May 14 06:11:25 2014 From: adietish at redhat.com (=?ISO-8859-1?Q?Andr=E9_Dietisheim?=) Date: Wed, 14 May 2014 12:11:25 +0200 Subject: [jbosstools-dev] Kudos for fixing GTK3 issues! Message-ID: <5373414D.1080001@redhat.com> Hey Snjezana big kudos for fixing the major parts of the SWT/GTK3 issues (I'm on FC20/GTK 3.10). Started using Luna M7/GTK3 today and stuff is pretty now usable, hurray! Big thanks for tackling this scary one. Cheers Andr? ps. I noticed the type dialog (Ctrl+Shift+T) has no labels. Items are selectable but no labels. Something you want me to file? From snjeza.peco at gmail.com Wed May 14 07:10:28 2014 From: snjeza.peco at gmail.com (Snjezana Peco) Date: Wed, 14 May 2014 13:10:28 +0200 Subject: [jbosstools-dev] Kudos for fixing GTK3 issues! In-Reply-To: <5373414D.1080001@redhat.com> References: <5373414D.1080001@redhat.com> Message-ID: <53734F24.7090700@gmail.com> On 5/14/2014 12:11 PM, Andr? Dietisheim wrote: > Hey Snjezana > > big kudos for fixing the major parts of the SWT/GTK3 issues (I'm on > FC20/GTK 3.10). Started using Luna M7/GTK3 today and stuff is pretty now > usable, hurray! > Big thanks for tackling this scary one. > > Cheers > Andr? > > ps. I noticed the type dialog (Ctrl+Shift+T) has no labels. Items are > selectable but no labels. Something you want me to file? That has been fixed within https://bugs.eclipse.org/bugs/show_bug.cgi?id=427480 Snjeza > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From mistria at redhat.com Wed May 14 13:08:32 2014 From: mistria at redhat.com (Mickael Istria) Date: Wed, 14 May 2014 19:08:32 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.0.Beta2-SNAPSHOT target platform: Luna M7 Message-ID: <5373A310.9040607@redhat.com> Here is a proposal for a change to the JBoss Tools 4.40.0.Beta2-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/60 It consists in the following changes: * https://issues.jboss.org/browse/JBIDE-17254 : Luna M7 (and removal of conflicting org.eclipse.equinox.p2.server feature, that does not seem necessary in JBT nor JBDS) *https://issues.jboss.org/browse/JBIDE-17266 : Removal of Birt, which currently doesn't have any delivery compatible with Luna M7. It will be re-enabled as soon as something good is available Please review the above PR(s), as it will be applied in the next 2 days. You can use the following to build & test the TP locally against your component(s). 1.Build target-platform: $ cd jbosstools-target-platforms $ git fetch mickaelistria JBIDE-17254 $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo 2. Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Beta2-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/20140514/54a4703d/attachment.html From manderse at redhat.com Thu May 15 07:51:48 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 15 May 2014 13:51:48 +0200 Subject: [jbosstools-dev] FYI: Beta3 versions created for JBIDE and JBDS Message-ID: <35B93E79-18A3-4895-B9F3-0C852D9303AC@redhat.com> Hey, see $subject makes it possible to target the jiras. sorry for not having that created last week ;/ /max http://about.me/maxandersen From dgolovin at exadel.com Thu May 15 13:35:11 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Thu, 15 May 2014 10:35:11 -0700 Subject: [jbosstools-dev] Proposed change to JBT 4.40.0.Beta2-SNAPSHOT target platform: Luna M7 In-Reply-To: <5373A310.9040607@redhat.com> References: <5373A310.9040607@redhat.com> Message-ID: <1400175311.10641.7.camel@dgolovin-desktop> Pls, see my comment below \/ On Wed, 2014-05-14 at 19:08 +0200, Mickael Istria wrote: > Here is a proposal for a change to the JBoss Tools 4.40.0.Beta2-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/60 > > It consists in the following changes: > * https://issues.jboss.org/browse/JBIDE-17254 : Luna M7 (and removal of conflicting org.eclipse.equinox.p2.server feature, that does not seem necessary in JBT nor JBDS) > * https://issues.jboss.org/browse/JBIDE-17266 : Removal of Birt, which currently doesn't have any delivery compatible with Luna M7. It will be re-enabled as soon as something good is available > > Please review the above PR(s), as it will be applied in the next 2 days. > > You can use the following to build & test the TP locally against your component(s). > 1. Build target-platform: > $ cd jbosstools-target-platforms jbosstools-target-platforms git remote add mickaelistria https://github.com/mickaelistria/jbosstools-target-platforms > $ git fetch mickaelistria JBIDE-17254 > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple I would really make multiple2repo profile not active by default because most of us do not need loal mirror and going to use remote one. This profile should be activated only on jenkins. WDYT? > $ mvn clean install -P \!multiple2repo > 2. Try with just built target-platform: > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.Beta2-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 From mistria at redhat.com Thu May 15 13:54:06 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 15 May 2014 19:54:06 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.0.Beta2-SNAPSHOT target platform: Luna M7 In-Reply-To: <1400175311.10641.7.camel@dgolovin-desktop> References: <5373A310.9040607@redhat.com> <1400175311.10641.7.camel@dgolovin-desktop> Message-ID: <5374FF3E.2080303@redhat.com> On 05/15/2014 07:35 PM, Denis Golovin wrote: > I would really make multiple2repo profile not active by default > because most of us do not need loal mirror and going to use remote > one. This profile should be activated only on jenkins. WDYT? I agree with that Please put that in a Jira since we'd probably need some more feedback about that suggestion. -- 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/20140515/ff5a1106/attachment.html From dgolovin at exadel.com Thu May 15 15:42:48 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Thu, 15 May 2014 12:42:48 -0700 Subject: [jbosstools-dev] Proposed change to JBT 4.40.0.Beta2-SNAPSHOT target platform: Luna M7 In-Reply-To: <5374FF3E.2080303@redhat.com> References: <5373A310.9040607@redhat.com> <1400175311.10641.7.camel@dgolovin-desktop> <5374FF3E.2080303@redhat.com> Message-ID: <1400182968.10641.9.camel@dgolovin-desktop> Done. Lock for details and PR in JBIDE-17280 - Disable mirroring of multiple target platforms to simplify local builds Denis On Thu, 2014-05-15 at 19:54 +0200, Mickael Istria wrote: > On 05/15/2014 07:35 PM, Denis Golovin wrote: > > > > > I would really make multiple2repo profile not active by default > > because most of us do not need loal mirror and going to use remote > > one. This profile should be activated only on jenkins. WDYT? > > I agree with that > Please put that in a Jira since we'd probably need some more feedback > about that suggestion. > > > -- > 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/20140515/a981a2d7/attachment.html From manderse at redhat.com Thu May 15 18:58:23 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Thu, 15 May 2014 18:58:23 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201405152258.s4FMwNUF016736@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-17117 https://issues.jboss.org/browse/JBIDE-17117 Summary: Simplify publish process 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:59:09.177892 ---------------------------- 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 Fri May 16 12:56:40 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Fri, 16 May 2014 18:56:40 +0200 Subject: [jbosstools-dev] Problem with JUnit test execution with maven Message-ID: <6392FD40-0C23-4928-98E3-B1DA663F3DA4@redhat.com> Hello, I just got a NPE with tests running from Maven (they run fine from PDE, though): 'org.eclipse.jst.j2ee.model.ModelProviderManager.ModelProviderManager.getModelProvider(project)' returns 'null' in the WizardPages that I'm trying to test. For the moment, I'll skip those tests on maven to avoid build failures on Jenkins, but if anyone has a clue what I should do to get them pass on maven/Jenkins (i.e., initialise the ModelProviderManager ?), please let me know ;-) Thanks ! Best regards, /Xavier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140516/3fc3242a/attachment.html From rcernich at redhat.com Fri May 16 13:02:22 2014 From: rcernich at redhat.com (Rob Cernich) Date: Fri, 16 May 2014 13:02:22 -0400 (EDT) Subject: [jbosstools-dev] Problem with JUnit test execution with maven In-Reply-To: <6392FD40-0C23-4928-98E3-B1DA663F3DA4@redhat.com> References: <6392FD40-0C23-4928-98E3-B1DA663F3DA4@redhat.com> Message-ID: <296806745.5820194.1400259742149.JavaMail.zimbra@redhat.com> Hey Xavier, This is a shot in the dark, but you might verify that the plugins providing the model provider are listed as dependencies for the test plugin. My experience has shown that the test environment only includes hard dependencies, so if you're relying on something that has a soft link (e.g. anything contributed through an extension point), you need to make sure the plugin making the contribution (e.g. implementing the extension point) is included in the dependencies list for your test plugin. It probably works fine in your dev env because Eclipse is using the entire set of plugins available (i.e. target platform + workspace plugins). Good luck. Rob ----- Original Message ----- > Hello, > I just got a NPE with tests running from Maven (they run fine from PDE, > though): ' org.eclipse.jst.j2ee.model.ModelProviderManager. > ModelProviderManager.getModelProvider(project) ' returns ' null ' in the > WizardPages that I'm trying to test. > For the moment, I'll skip those tests on maven to avoid build failures on > Jenkins, but if anyone has a clue what I should do to get them pass on > maven/Jenkins (i.e., initialise the ModelProviderManager ?), please let me > know ;-) > Thanks ! > 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/20140516/5f5634eb/attachment.html From akazakov at exadel.com Fri May 16 13:24:23 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Fri, 16 May 2014 10:24:23 -0700 Subject: [jbosstools-dev] Problem with JUnit test execution with maven In-Reply-To: <296806745.5820194.1400259742149.JavaMail.zimbra@redhat.com> References: <6392FD40-0C23-4928-98E3-B1DA663F3DA4@redhat.com> <296806745.5820194.1400259742149.JavaMail.zimbra@redhat.com> Message-ID: <537649C7.3030402@exadel.com> It's easy to verify if your test project is missing some soft dependencies. In your dev environment, in Run Configuration of your test -> Plugins Tab: 1. select plug-ins selected below only 2. Deselect All 3. In filter field, type your test plug-in ID to find it in the list of plugins. 4. Select this plug-in. 5. Clean up the filter. 6. Press Add Required Plug-ins Here we go. Now you can run the test and see if it fails since now your test environment includes the same set of plugins which you have in your maven build. On 05/16/2014 10:02 AM, Rob Cernich wrote: > Hey Xavier, > > This is a shot in the dark, but you might verify that the plugins > providing the model provider are listed as dependencies for the test > plugin. My experience has shown that the test environment only > includes hard dependencies, so if you're relying on something that has > a soft link (e.g. anything contributed through an extension point), > you need to make sure the plugin making the contribution (e.g. > implementing the extension point) is included in the dependencies list > for your test plugin. It probably works fine in your dev env because > Eclipse is using the entire set of plugins available (i.e. target > platform + workspace plugins). > > Good luck. > > Rob > > > ------------------------------------------------------------------------ > > Hello, > > I just got a NPE with tests running from Maven (they run fine from > PDE, though): > '*org.eclipse.jst.j2ee.model.ModelProviderManager.**ModelProviderManager.getModelProvider(project)*' > returns '*null*' in the WizardPages that I'm trying to test. > > For the moment, I'll skip those tests on maven to avoid build > failures on Jenkins, but if anyone has a clue what I should do to > get them pass on maven/Jenkins (i.e., initialise the > ModelProviderManager ?), please let me know ;-) > > Thanks ! > Best regards, > /Xavier > > > > > _______________________________________________ > 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/20140516/7152cc65/attachment-0001.html From mistria at redhat.com Fri May 16 13:26:46 2014 From: mistria at redhat.com (Mickael Istria) Date: Fri, 16 May 2014 19:26:46 +0200 Subject: [jbosstools-dev] Problem with JUnit test execution with maven In-Reply-To: <296806745.5820194.1400259742149.JavaMail.zimbra@redhat.com> References: <6392FD40-0C23-4928-98E3-B1DA663F3DA4@redhat.com> <296806745.5820194.1400259742149.JavaMail.zimbra@redhat.com> Message-ID: <53764A56.8050103@redhat.com> On 05/16/2014 07:02 PM, Rob Cernich wrote: > This is a shot in the dark, but you might verify that the plugins > providing the model provider are listed as dependencies for the test > plugin. My experience has shown that the test environment only > includes hard dependencies, so if you're relying on something that has > a soft link (e.g. anything contributed through an extension point), > you need to make sure the plugin making the contribution (e.g. > implementing the extension point) is included in the dependencies list > for your test plugin. It probably works fine in your dev env because > Eclipse is using the entire set of plugins available (i.e. target > platform + workspace plugins). +1 This seems to be what I (or maybe everyone) call a "behavioral" dependency: it's not necessary in order to compile or execute code, but it is necessary in order to have the test actually testing what's expected. So you should start by finding out which bundle is required for that test to work, and then either add it as a requirement in the MANIFEST.MF or configure tycho-surefire-plugin to add the dependency. My preference would go for the MANIFEST.MF since it also gives you the guarantee that this test would work with any tools respecting OSGi. In order to debug with tycho-surefire-plugin just add a -DdebugPort=8000 property to your mvn command-line and then connect to JVM on port 8000 as a Remote application in Eclipse ( https://github.com/jbosstools/jbosstools-devdoc/blob/master/debugging/debug_Tycho_tests.md#connecting-surefire-test-execution-to-eclipse-debugger-allows-to-put-breakpoints-in-maven-tests (. If you want to simulate an environment with PDE tests that looks like the one of tycho-surefire-plugin, you should go to the Test Configuration and configure your test by unselecting all bundles, then selecting only your test bundle, and then clicking the "Add Required Plugins" button that would compute a minimal runtime for this test. You may need to add some extra stuff (such as org.eclipse.equinox.ds) HTH -- 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/20140516/8b422d88/attachment.html From snjezana.peco at redhat.com Fri May 16 15:10:14 2014 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Fri, 16 May 2014 21:10:14 +0200 Subject: [jbosstools-dev] Kudos for fixing GTK3 issues! In-Reply-To: <53734F24.7090700@gmail.com> References: <5373414D.1080001@redhat.com> <53734F24.7090700@gmail.com> Message-ID: <53766296.1080001@redhat.com> The patch for https://bugs.eclipse.org/bugs/show_bug.cgi?id=427480 is included into Luna RC1 - http://download.eclipse.org/eclipse/downloads/drops4/S-4.4RC1-201405151230/ Snjeza On 5/14/2014 1:10 PM, Snjezana Peco wrote: > On 5/14/2014 12:11 PM, Andr? Dietisheim wrote: >> Hey Snjezana >> >> big kudos for fixing the major parts of the SWT/GTK3 issues (I'm on >> FC20/GTK 3.10). Started using Luna M7/GTK3 today and stuff is pretty now >> usable, hurray! >> Big thanks for tackling this scary one. >> >> Cheers >> Andr? >> >> ps. I noticed the type dialog (Ctrl+Shift+T) has no labels. Items are >> selectable but no labels. Something you want me to file? > That has been fixed within > https://bugs.eclipse.org/bugs/show_bug.cgi?id=427480 > > 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 xcoulon at redhat.com Fri May 16 16:11:27 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Fri, 16 May 2014 22:11:27 +0200 Subject: [jbosstools-dev] Problem with JUnit test execution with maven In-Reply-To: <53764A56.8050103@redhat.com> References: <6392FD40-0C23-4928-98E3-B1DA663F3DA4@redhat.com> <296806745.5820194.1400259742149.JavaMail.zimbra@redhat.com> <53764A56.8050103@redhat.com> Message-ID: <9E397696-A946-432D-9F60-80362EC80BAB@redhat.com> Thanks for your replies, I'm going to try what you suggested. Best regards, /Xavier On 16 May 2014, at 19:26, Mickael Istria wrote: > On 05/16/2014 07:02 PM, Rob Cernich wrote: >> This is a shot in the dark, but you might verify that the plugins providing the model provider are listed as dependencies for the test plugin. My experience has shown that the test environment only includes hard dependencies, so if you're relying on something that has a soft link (e.g. anything contributed through an extension point), you need to make sure the plugin making the contribution (e.g. implementing the extension point) is included in the dependencies list for your test plugin. It probably works fine in your dev env because Eclipse is using the entire set of plugins available (i.e. target platform + workspace plugins). > +1 > This seems to be what I (or maybe everyone) call a "behavioral" dependency: it's not necessary in order to compile or execute code, but it is necessary in order to have the test actually testing what's expected. > So you should start by finding out which bundle is required for that test to work, and then either add it as a requirement in the MANIFEST.MF or configure tycho-surefire-plugin to add the dependency. My preference would go for the MANIFEST.MF since it also gives you the guarantee that this test would work with any tools respecting OSGi. > > In order to debug with tycho-surefire-plugin just add a -DdebugPort=8000 property to your mvn command-line and then connect to JVM on port 8000 as a Remote application in Eclipse ( https://github.com/jbosstools/jbosstools-devdoc/blob/master/debugging/debug_Tycho_tests.md#connecting-surefire-test-execution-to-eclipse-debugger-allows-to-put-breakpoints-in-maven-tests (. > > If you want to simulate an environment with PDE tests that looks like the one of tycho-surefire-plugin, you should go to the Test Configuration and configure your test by unselecting all bundles, then selecting only your test bundle, and then clicking the "Add Required Plugins" button that would compute a minimal runtime for this test. You may need to add some extra stuff (such as org.eclipse.equinox.ds) > > HTH > -- > 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/20140516/b31fe5cb/attachment.html From manderse at redhat.com Mon May 19 02:20:57 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 19 May 2014 08:20:57 +0200 Subject: [jbosstools-dev] tern.java vs VJET? In-Reply-To: References: <48EFD487-8EB4-4519-9E15-CCE477E01D92@redhat.com> Message-ID: On 13 May 2014, at 14:17, Angelo zerr wrote: > 2014-05-13 13:40 GMT+02:00 Max Rydahl Andersen : > >> On 13 May 2014, at 13:25, Angelo zerr wrote: >> >> 2014-05-13 12:17 GMT+02:00 Max Rydahl Andersen : >>> >>> On 13 May 2014, at 9:13, Angelo zerr wrote: >>>> >>>> Hi Max, >>>> >>>>> >>>>> Thank's for your answer. But you wish to give up one day JSDT? >>>>> >>>>> >>>> no, because JSDT offers more than any of these do and JSDT facets >>>> etc. >>>> are >>>> *required* for wtp projects. >>>> >>>> neither tern or vjet could work without JSDT. >>>> >>>> Fixing/replacing how parsing/valdiation is done in JSDT is the goal >>>> - not >>>> about removing jsdt (which is more than just parsing/valdiation) >>>> >>>> Ok I understand. For your information, I have started validation >>>> (not >>>> >>> syntax validation) with tern : >>> https://github.com/angelozerr/tern.java/wiki/Tern-&-Validation >>> >>> which is based on JS tern plugin >>> https://github.com/angelozerr/tern.lintwhich works with editor like >>> CodeMirror. >>> >> >> So if I run with this I will get double validation errors if >> validation >> from JSDT aren't disabled, right? >> > > Right. But tern.lint doesn't validate the same feature than JSDT : > > * validate "Unkown property" > * validate "Unkown identtifier" > * will validate string value according JS framework (ex : var a = > require('XXX') will show an error for XXX which is not a known node > module if they are just "add ons" thats good - less confusion. > Perhaps in the future, tern.lint will able to validate syntax error, > but I > would like to manage severity for each validation rules ('warning', > error, > ignore). oh yes - very important. > So you will able to disbale if you wish some error coming from > tern.lint > (see https://github.com/angelozerr/tern.lint/issues/4) Is the eclipse validation using wtp validation mechanism or its own ? /max >> >> /max >> >> >> >>> Regards Angelo >>> >>> >>> /max >>>> >>>> >>>> I hope tern.javaI will one day provide the same cool feature than >>>> VJET >>>> >>>>> like >>>>> https://wiki.eclipse.org/VJET/Code_Assistance_Features >>>>> >>>>> >>>> Very impressive! >>>> >>>>> >>>>> Regards Angelo >>>>> >>>>> >>>>> 2014-05-12 18:34 GMT+02:00 Max Rydahl Andersen >>>>> : >>>>> >>>>> On 12 May 2014, at 18:26, Angelo zerr wrote: >>>>> >>>>>> >>>>>> Hi JBoss guys, >>>>>> >>>>>>> >>>>>>> I have noticed that you had integrated VJET last year. I have >>>>>>> never >>>>>>> >>>>>>> played >>>>>> >>>>>> with VJET, but I have seen features screenshot of VJET (like >>>>>> object >>>>>>> litteral validation) and it seems very powerful. >>>>>>> >>>>>>> My goal is to try to implement the same feature than VJET, but >>>>>>> I'm >>>>>>> very >>>>>>> curious why you decided to integrate and contribute to tern.java >>>>>>> although >>>>>>> you have VJET. >>>>>>> >>>>>>> >>>>>> because vjet haven't moved anywhere and still relies on jsdt for >>>>>> its >>>>>> parsing. >>>>>> >>>>>> >>>>>> thats the short version. >>>>>> >>>>>> >>>>>> /max >>>>>> http://about.me/maxandersen >>>>>> >>>>>> >>>>>> >>>> /max >>>> http://about.me/maxandersen >>>> >>>> >> >> /max >> http://about.me/maxandersen >> /max http://about.me/maxandersen From mistria at redhat.com Mon May 19 05:15:24 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 19 May 2014 11:15:24 +0200 Subject: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? Message-ID: <5379CBAC.7070207@redhat.com> Hi all, It seems like Nodeclipse provide a very good toolset for JavaScript: http://marketplace.eclipse.org/content/nodeclipseenide-eclipse-nodejs-ide . Some tools were developed in Nodeclipse, some others are aggregated from other projects (such as http://marketplace.eclipse.org/content/eclipse-plugin-less , http://marketplace.eclipse.org/content/markdown-text-editor , http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-plugin ...) Should we consider putting some parts of it on Central ? or even in JBDS ? Should we try to lobby with some authors to move projects to Eclipse.org ? -- 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/20140519/d5b5a536/attachment-0001.html From angelo.zerr at gmail.com Mon May 19 05:24:10 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Mon, 19 May 2014 11:24:10 +0200 Subject: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: <5379CBAC.7070207@redhat.com> References: <5379CBAC.7070207@redhat.com> Message-ID: Hi Mickael, Just for your information, Paul who is the guy of Nodeclipse https://github.com/PaulVI has integrated tern.java+angularjs eclipse inside nodeclipse http://www.nodeclipse.org/ Regards Angelo 2014-05-19 11:15 GMT+02:00 Mickael Istria : > Hi all, > > It seems like Nodeclipse provide a very good toolset for JavaScript: > http://marketplace.eclipse.org/content/nodeclipseenide-eclipse-nodejs-ide. Some tools were developed in Nodeclipse, some others are aggregated from > other projects (such as > http://marketplace.eclipse.org/content/eclipse-plugin-less , > http://marketplace.eclipse.org/content/markdown-text-editor , > http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-plugin...) > Should we consider putting some parts of it on Central ? or even in JBDS ? > Should we try to lobby with some authors to move projects to Eclipse.org ? > -- > 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/20140519/83279d3d/attachment.html From manderse at redhat.com Mon May 19 05:29:57 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 19 May 2014 11:29:57 +0200 Subject: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: <5379CBAC.7070207@redhat.com> References: <5379CBAC.7070207@redhat.com> Message-ID: On 19 May 2014, at 11:15, Mickael Istria wrote: > Hi all, > > It seems like Nodeclipse provide a very good toolset for JavaScript: > http://marketplace.eclipse.org/content/nodeclipseenide-eclipse-nodejs-ide > . Some tools were developed in Nodeclipse, some others are aggregated > from other projects (such as > http://marketplace.eclipse.org/content/eclipse-plugin-less , > http://marketplace.eclipse.org/content/markdown-text-editor , > http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-plugin > ...) > Should we consider putting some parts of it on Central ? or even in > JBDS ? > Should we try to lobby with some authors to move projects to > Eclipse.org ? he is already aware of our interest in making Javascript better - he has been on this list a few times (Paul Verest) - but no harm in always ask again someone to contribute to eclipse.org or to jbosstools. The problem with nodeclipse from my POV is that is a bunch of non-connected, not uniform set of plugins that needs some consistency to be really competitive. Something we should definitely look at helping happening. /max http://about.me/maxandersen From mistria at redhat.com Mon May 19 08:59:31 2014 From: mistria at redhat.com (Mickael Istria) Date: Mon, 19 May 2014 14:59:31 +0200 Subject: [jbosstools-dev] Proposed change to JBT 4.40.0.Beta2-SNAPSHOT target platform: Luna M7 In-Reply-To: <5373A310.9040607@redhat.com> References: <5373A310.9040607@redhat.com> Message-ID: <537A0033.4040706@redhat.com> The following change have been applied and new target-platforms have been deployed. Target-Platforms 4.40.0.Beta2-SNAPSHOT are now based on Luna M7, and don't contain Birt. On 05/14/2014 07:08 PM, Mickael Istria wrote: > Here is a proposal for a change to the JBoss Tools 4.40.0.Beta2-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/60 > > It consists in the following changes: > *https://issues.jboss.org/browse/JBIDE-17254 : Luna M7 (and removal of conflicting org.eclipse.equinox.p2.server feature, that does not seem necessary in JBT nor JBDS) > *https://issues.jboss.org/browse/JBIDE-17266 : Removal of Birt, which currently doesn't have any delivery compatible with Luna M7. It will be re-enabled as soon as something good is available > > Please review the above PR(s), as it will be applied in the next 2 days. > > You can use the following to build & test the TP locally against your component(s). > 1.Build target-platform: > $ cd jbosstools-target-platforms > $ git fetch mickaelistria JBIDE-17254 > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple > $ mvn clean install -P \!multiple2repo > 2. Try with just built target-platform: > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.Beta2-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/20140519/3fadf451/attachment.html From paul.verest at live.com Tue May 20 06:09:38 2014 From: paul.verest at live.com (Paul Verest) Date: Tue, 20 May 2014 10:09:38 +0000 Subject: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: References: <5379CBAC.7070207@redhat.com>, Message-ID: Hello All First the should be message from Eclipse to remind developers to have Help pages (e.g. easily created with http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-plugin)that references to their project web site.I found that plugin developers sometimes event don't have marketplace entries (and helped/pushed with about 6-8 ) > Should we consider putting some parts of it on Central ? or even in JBDS ? > Should we try to lobby with some authors to move projects to Eclipse.org ? Could discussion is to get started. I suggest to lobby that Eclipse would recognize non-Eclipse.org projects under EPL license as valuable part of Eclipse eco-systemthat Eclipse project committers should be aware of, give and take help.e.g. https://github.com/eclipse-color-theme/eclipse-color-theme Something like open letter from Eclipse Foundation to Eclipse plugins authors. By the way looking for (remote) speakers for Eclipse DemoCamp Beijinghttps://wiki.eclipse.org/Eclipse_DemoCamps_Luna_2014/Beijing Please also help to connect to Red Hat China managers or marketing. @Angelo Would this email get into jbosstools-dev list? Best regards,Paul Verest Date: Mon, 19 May 2014 11:24:10 +0200 Subject: Re: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? From: angelo.zerr at gmail.com To: mistria at redhat.com CC: jbosstools-dev at lists.jboss.org; paul.verest at live.com Hi Mickael, Just for your information, Paul who is the guy of Nodeclipse https://github.com/PaulVI has integrated tern.java+angularjs eclipse inside nodeclipse http://www.nodeclipse.org/ Regards Angelo 2014-05-19 11:15 GMT+02:00 Mickael Istria : Hi all, It seems like Nodeclipse provide a very good toolset for JavaScript: http://marketplace.eclipse.org/content/nodeclipseenide-eclipse-nodejs-ide . Some tools were developed in Nodeclipse, some others are aggregated from other projects (such as http://marketplace.eclipse.org/content/eclipse-plugin-less , http://marketplace.eclipse.org/content/markdown-text-editor , http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-plugin ...) Should we consider putting some parts of it on Central ? or even in JBDS ? Should we try to lobby with some authors to move projects to Eclipse.org ? -- 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/20140520/d613c5cb/attachment.html From mistria at redhat.com Tue May 20 06:35:29 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 20 May 2014 12:35:29 +0200 Subject: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: References: <5379CBAC.7070207@redhat.com>, Message-ID: <537B2FF1.10406@redhat.com> Hi Paul, On 05/20/2014 12:09 PM, Paul Verest wrote: > I suggest to lobby that Eclipse would recognize non-Eclipse.org > projects under EPL license as valuable part of Eclipse eco-system MarketPlace was done to fulfill this goal and it works pretty well. Some non Eclipse.org project have been pretty successful thanks to MarketPlace and MarketPlace client. I think those should thank the Foundation for that. > that Eclipse project committers should be aware of, give and take help. > e.g. https://github.com/eclipse-color-theme/eclipse-color-theme The issue with the multiplication of projects out of Eclipse.org is that you end up with different process to contribute and don't have the guarantee a contribution would be appreciated and considered. Being on GitHub is not a proof of an open development process, it's "just" OSS code. That's why it makes sense for contributors/consumers (like us) to encourage projects to become official Eclipse projects. Eclipse Foundation has set up rules that ensure a really open development process and that guarantee that a project can't be locked, and that encourage contributions over forks. It makes things safer. > Something like open letter from Eclipse Foundation to Eclipse plugins > authors. That's probably a good idea. Maybe the Foundation (or the community in general) should make it more official that projects on GitHub/MarketPlace are welcome to become official Eclipse projects and explain to authors that being an Eclipse.org project is a sign of real openness and a generator of success. But in any way, I can fully understand from the Foundation POV and from our "consumer" POV, that there is and will always be a distinction between Eclipse.org and non-Eclipse.org projects. The Foundation rules are definitely something good, that make a difference. > Please also help to connect to Red Hat China managers or marketing. Unfortunately, I don't know anyone in Red Hat office in China. Maybe Rob (Stryker) can help. > @Angelo Would this email get into jbosstools-dev list? Yes, it's on. And this answer too. Check you CC list before sending mails ;) -- 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/20140520/ecc8c6bd/attachment-0001.html From mistria at redhat.com Tue May 20 09:47:48 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 20 May 2014 15:47:48 +0200 Subject: [jbosstools-dev] Target Platform release possibly delayed (a little) Message-ID: <537B5D04.5070603@redhat.com> Hi all, According to our agenda, today is the day when Target Platform 4.40.0.Beta2 should be released. However, I noticed that the Central target-platform and install-grinder jobs haven't been updated (my bad) when moving to Luna M7. That makes that last installation tests were working, and succeeding, when installing on Luna M6 a JBoss Tools 4.2.0.Beta2-SNAPSHOT (referencing Luna M7 in the TP) and connectors from Central that were based on Luna M6. But this is not the scenario we are willing to validate. So I've already updated a few things, however, before actually releasing and announcing the new TP release, updated all jobs and so on, I need to make sure that the following installation scenario works: * On Luna M7 * Install JBoss Tools with Luna M7 (4.40.0.Beta2-SNAPSHOT) Target-Platform * And install Central stuff compatible with Luna M7 So I'm waiting for feedback from this job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/1955/ before I can go ahead and finish the target-platform release. Depending on slave availability, it can be either in the next 30 minutes, or tomorrow morning (just a guess). Sorry for the disturbance. -- 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/20140520/5946cb28/attachment.html From mistria at redhat.com Tue May 20 12:22:27 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 20 May 2014 18:22:27 +0200 Subject: [jbosstools-dev] Target Platform 4.40.0.Beta2 for JBoss Tools 4.2.0.Beta2 has been released. Message-ID: <537B8143.3030903@redhat.com> Changes (compared to 4.40.0.Beta1) ======= In the category "Fix dependencies" (after the cleanup of previous release) * JBIDE-16910: Fix some dependencies for Atlassian (Mylyn) * JBIDE-16960: Removed GWT * JBIDE-17019: Add m2eclipse-egit * JBDS-3003: Add TestNG (JBDS only) * JBIDE-17160: Add Tern.java * JBIDE-17254: Move to Luna M7 * JBIDE-17266: Remove Birt (hopefully temporary) Usage ===== Target platform 4.40.0.Beta2 is what JBoss Tools 4.2.0.Beta2 will use. All Jenkins jobs for branch and parent pom 4.2.0.Beta2-SNAPSHOT have been updated to use target platform 4.40.0.Beta2. The following p2 repositories *will be modified* to point to this new target platform once JBoss Tools 4.2.0.Beta2 is released: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ * http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/ * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/luna/ Download ======== Update site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta2/REPO/ Update site zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta2/jbosstoolstarget-4.40.0.Beta2 .zip Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta2 Testing/Development =================== If your root pom correctly specifies the latest parent pom version as 4.2.0.Beta2-SNAPSHOT, you need only this: $ mvn clean verify If you're using a different parent pom, use this: $ mvn clean verify -Dtpc.version=4.40.0.Beta2 For advanced 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.Beta3-SNAPSHOT. We can at least expect for Beta3: * Move to Luna release/R/SR0 * Re-introduction of a compatible version of Birt * 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 All Jenkins jobs for *master* have been updated to use target platform 4.40.0.Beta3-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/20140520/e34eb9e5/attachment.html From mistria at redhat.com Tue May 20 12:28:07 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 20 May 2014 18:28:07 +0200 Subject: [jbosstools-dev] REMINDER: Code Freeze for JBoss Tools 4.2.0.Beta2 is on Thursday 22nd Message-ID: <537B8297.1070407@redhat.com> Hi all, This is a gentle reminder that Code Freeze for JBoss Tools 4.2.0.Beta2 will be in 2 days, Thurday May 22nd. Please make sure your component builds and runs correctly, that everything that you want to be part of the Beta2 release gets checked in before Code Freeze, and that things are working with the 4.40.0.Beta2 target-platform. It's also time to triage your jiras and postpone those that were targeted for Beta2 and that won't have the opportunity to get in. 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/20140520/b3fba732/attachment.html From akazakov at exadel.com Tue May 20 12:31:53 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Tue, 20 May 2014 09:31:53 -0700 Subject: [jbosstools-dev] REMINDER: Code Freeze for JBoss Tools 4.2.0.Beta2 is on Thursday 22nd In-Reply-To: <537B8297.1070407@redhat.com> References: <537B8297.1070407@redhat.com> Message-ID: <537B8379.2000008@exadel.com> When are we going to have a feature freeze? Beta2 or Beta3? On 05/20/2014 09:28 AM, Mickael Istria wrote: > Hi all, > > This is a gentle reminder that Code Freeze for JBoss Tools 4.2.0.Beta2 > will be in 2 days, Thurday May 22nd. > Please make sure your component builds and runs correctly, that > everything that you want to be part of the Beta2 release gets checked > in before Code Freeze, and that things are working with the > 4.40.0.Beta2 target-platform. It's also time to triage your jiras and > postpone those that were targeted for Beta2 and that won't have the > opportunity to get in. > > 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/20140520/6f7857f8/attachment.html From manderse at redhat.com Tue May 20 13:53:51 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 20 May 2014 19:53:51 +0200 Subject: [jbosstools-dev] REMINDER: Code Freeze for JBoss Tools 4.2.0.Beta2 is on Thursday 22nd In-Reply-To: <537B8379.2000008@exadel.com> References: <537B8297.1070407@redhat.com> <537B8379.2000008@exadel.com> Message-ID: <63D4A288-625C-4F55-A596-CF20F0801C8F@redhat.com> On 20 May 2014, at 18:31, Alexey Kazakov wrote: > When are we going to have a feature freeze? Beta2 or Beta3? Beta2. /max > On 05/20/2014 09:28 AM, Mickael Istria wrote: >> Hi all, >> >> This is a gentle reminder that Code Freeze for JBoss Tools >> 4.2.0.Beta2 will be in 2 days, Thurday May 22nd. >> Please make sure your component builds and runs correctly, that >> everything that you want to be part of the Beta2 release gets checked >> in before Code Freeze, and that things are working with the >> 4.40.0.Beta2 target-platform. It's also time to triage your jiras and >> postpone those that were targeted for Beta2 and that won't have the >> opportunity to get in. >> >> 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 /max http://about.me/maxandersen From rstryker at redhat.com Tue May 20 14:21:04 2014 From: rstryker at redhat.com (Rob Stryker) Date: Wed, 21 May 2014 02:21:04 +0800 Subject: [jbosstools-dev] Recently can't load internal browser Message-ID: <537B9D10.5040309@redhat.com> Not sure what's changed on my system, but i recently can't load an internal browser. Just get the following error: [Could not detect registered XULRunner to use] Anyone know how to fix this situation, or steps to debug it? Not sure if I'm missing some bundle / fragment / or just broke something. - Rob From manderse at redhat.com Wed May 21 04:55:22 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 21 May 2014 10:55:22 +0200 Subject: [jbosstools-dev] Recently can't load internal browser In-Reply-To: <537B9D10.5040309@redhat.com> References: <537B9D10.5040309@redhat.com> Message-ID: <5C04322D-32A4-409C-B2AF-A6FEDB95DA3B@redhat.com> On 20 May 2014, at 20:21, Rob Stryker wrote: > Not sure what's changed on my system, but i recently can't load an > internal browser. Just get the following error: > > [Could not detect registered XULRunner to use] You don't have *any* error besides that ? no stack trace, no nothing ? > > Anyone know how to fix this situation, or steps to debug it? Not sure if > I'm missing some bundle / fragment / or just broke something. > > - Rob > _______________________________________________ > 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 Wed May 21 05:01:50 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 21 May 2014 11:01:50 +0200 Subject: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: References: <5379CBAC.7070207@redhat.com> Message-ID: <16F45C6A-1CB9-42F9-9E53-49F44F4F08B8@redhat.com> On 20 May 2014, at 12:09, Paul Verest wrote: > Hello All > > First the should be message from Eclipse to remind developers to have > Help pages (e.g. easily created with > http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-plugin)that > references to their project web site. Not following what you mean here ? > I found that plugin developers sometimes event don't have marketplace > entries (and helped/pushed with about 6-8 ) Yes that is a good thing overall. The problem is many plugins don't even do basic UI interaction well. i.e. litter the context menu with actions, not integrating with the existing eclipse infrastructure etc. it results in a very fragmented experience unfortunately ;/ >> Should we consider putting some parts of it on Central ? or even in >> JBDS ? >> Should we try to lobby with some authors to move projects to >> Eclipse.org ? > Could discussion is to get started. > I suggest to lobby that Eclipse would recognize non-Eclipse.org > projects under EPL license as valuable part of Eclipse eco-systemthat > Eclipse project committers should be aware of, give and take help.e.g. > https://github.com/eclipse-color-theme/eclipse-color-theme I'm not following what you mean/expect here ? When have eclipse not seen non-eclipse.org projects as valuable ? Problem I have is that if it projects don't participate in eclipse release train nor want to honor eclipse API guidelines they become something that is really really hard to rely on. Thus we can't include everything just because it exists. > Something like open letter from Eclipse Foundation to Eclipse plugins > authors. What should that say that is not already happening ? > By the way looking for (remote) speakers for Eclipse DemoCamp > Beijinghttps://wiki.eclipse.org/Eclipse_DemoCamps_Luna_2014/Beijing You should do that in a separate mail thread instead of mingled in here. Becomes more visible that way. You can post on the community forums too if you prefer. > Please also help to connect to Red Hat China managers or marketing. Send me mail directly on what you are looking for and I can put you in contact. /max http://about.me/maxandersen From nboldt at redhat.com Wed May 21 18:11:49 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 21 May 2014 18:11:49 -0400 Subject: [jbosstools-dev] Target Platform 4.40.0.Beta2 for JBoss Tools 4.2.0.Beta2 has been released. In-Reply-To: <537B8143.3030903@redhat.com> References: <537B8143.3030903@redhat.com> Message-ID: <537D24A5.6050901@redhat.com> Seems we released this a bit too hastily. A 4.40.0.Beta3 is in progress now, which will fix these issues: * updated BIRT, compatible w/ M7: JBIDE-17266 * updated m2e.java & m2e.apt: JBIDE-16757, JBIDE-17306 * updated tern.java: JBIDE-17317 On 05/20/2014 12:22 PM, Mickael Istria wrote: > Changes (compared to 4.40.0.Beta1) > ======= > > In the category "Fix dependencies" (after the cleanup of previous release) > * JBIDE-16910: Fix some dependencies for Atlassian (Mylyn) > * JBIDE-16960: Removed GWT > * JBIDE-17019: Add m2eclipse-egit > * JBDS-3003: Add TestNG (JBDS only) > * JBIDE-17160: Add Tern.java > * JBIDE-17254: Move to Luna M7 > * JBIDE-17266: Remove Birt (hopefully temporary) > > Usage > ===== > > Target platform 4.40.0.Beta2 is what JBoss Tools 4.2.0.Beta2 will use. > All Jenkins jobs for branch and parent pom 4.2.0.Beta2-SNAPSHOT have > been updated to use target platform 4.40.0.Beta2. > The following p2 repositories *will be modified* to point to this new > target platform once JBoss Tools 4.2.0.Beta2 is released: > * > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > * > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/ > * > http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/luna/ > > > Download > ======== > > Update site: > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta2/REPO/ > Update site zip: > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta2/jbosstoolstarget-4.40.0.Beta2 > .zip > Git tag: > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta2 > > > Testing/Development > =================== > > If your root pom correctly specifies the latest parent pom version as > 4.2.0.Beta2-SNAPSHOT, you need only this: > $ mvn clean verify > If you're using a different parent pom, use this: > $ mvn clean verify -Dtpc.version=4.40.0.Beta2 > For advanced 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.Beta3-SNAPSHOT. We can > at least expect for Beta3: > * Move to Luna release/R/SR0 > * Re-introduction of a compatible version of Birt > * 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 > > All Jenkins jobs for *master* have been updated to use target platform > 4.40.0.Beta3-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 akazakov at exadel.com Wed May 21 20:50:37 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Wed, 21 May 2014 17:50:37 -0700 Subject: [jbosstools-dev] parent pom broken? In-Reply-To: <537D24A5.6050901@redhat.com> References: <537B8143.3030903@redhat.com> <537D24A5.6050901@redhat.com> Message-ID: <537D49DD.5000003@exadel.com> Got this error when trying to build jst (master): [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.jst.jsdt 3.6.0.qualifier to bundle com.googlecode.json-simple 1.1.1.; No solution found because the problem is unsatisfiable.] -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.jst.jsdt 3.6.0.qualifier to bundle com.googlecode.json-simple 1.1.1.; No solution found because the problem is unsatisfiable.] From dgolovin at exadel.com Wed May 21 20:52:55 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Wed, 21 May 2014 17:52:55 -0700 Subject: [jbosstools-dev] parent pom broken? In-Reply-To: <537D49DD.5000003@exadel.com> References: <537B8143.3030903@redhat.com> <537D24A5.6050901@redhat.com> <537D49DD.5000003@exadel.com> Message-ID: <537D4A67.4040407@exadel.com> This is because https://github.com/jbosstools/jbosstools-build/commit/bba1cad1f3c6a30c1d3b63b584a009e2556150c0. Parent pom in master has version beta2, but references tp beta3. Denis On 05/21/2014 05:50 PM, Alexey Kazakov wrote: > Got this error when trying to build jst (master): > > [ERROR] Internal error: java.lang.RuntimeException: No solution found > because the problem is unsatisfiable.: [Unable to satisfy dependency > from org.jboss.tools.jst.jsdt 3.6.0.qualifier to bundle > com.googlecode.json-simple 1.1.1.; No solution found because the problem > is unsatisfiable.] -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.RuntimeException: No solution found because the problem is > unsatisfiable.: [Unable to satisfy dependency from > org.jboss.tools.jst.jsdt 3.6.0.qualifier to bundle > com.googlecode.json-simple 1.1.1.; No solution found because the problem > is unsatisfiable.] > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From mistria at redhat.com Thu May 22 03:15:04 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 22 May 2014 09:15:04 +0200 Subject: [jbosstools-dev] Target Platform 4.40.0.Beta2 for JBoss Tools 4.2.0.Beta2 has been released. In-Reply-To: <537D24A5.6050901@redhat.com> References: <537B8143.3030903@redhat.com> <537D24A5.6050901@redhat.com> Message-ID: <537DA3F8.7010908@redhat.com> So today is a bad day for target-platforms: some changes were requested and applied after TP was released. We'll investigate whether those changes were actually necessary and if they are worth a TP respin. But please, do anticipate required TP change! We cannot afford to change TP on the day of a code freeze, that's a risky operation that slows us down our reduce our ability to ship on time and increase the risk of respins for QA. The date of target-platform releases are on the JBDS-Tech calendar. Make sure your requests get it on time. Although many supposed urgent changes were applied to 4.40.0.Beta2-SNAPSHOT (and may issues created/revealed as a side effect), all that just shows that urgent changes in TP are not good at all. So my plan/with is still to use 4.40.0.Beta2 if possible. Depending on the criticity of the issues those changes try to fix, we can think about building a 4.40.0.Beta3 TP for JBoss Tools 4.2.0.Beta2. But that clearly is a bad thing because it would make the code-freeze more complex (master currently testing against Beta3-SNAPSHOT whereas it will be branched and built against Beta2 or maybe Beta3, we don't know yet....)) On 05/22/2014 12:11 AM, Nick Boldt wrote: > Seems we released this a bit too hastily. A 4.40.0.Beta3 is in > progress now, which will fix these issues: > > * updated BIRT, compatible w/ M7: JBIDE-17266 This needs to be discussed. Maybe it could be in a respin? Or just dropped out of Beta2 and get back in Beta3 > * updated m2e.java & m2e.apt: JBIDE-16757, JBIDE-17306 This is far from being a blocker for Beta2. > * updated tern.java: JBIDE-17317 @Victor: Is this really necessary? What blocker for beta2 was this change supposed to fix? Couldn't you keep on depending on previous version of tern.java for 4.2.0.Beta2 ? How come you didn't request it earlier (before TP 4.40.0.Beta2 was 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/20140522/5f069263/attachment.html From paul.verest at live.com Thu May 22 05:57:22 2014 From: paul.verest at live.com (Paul Verest) Date: Thu, 22 May 2014 09:57:22 +0000 Subject: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: <16F45C6A-1CB9-42F9-9E53-49F44F4F08B8@redhat.com> References: <5379CBAC.7070207@redhat.com>, , , <16F45C6A-1CB9-42F9-9E53-49F44F4F08B8@redhat.com> Message-ID: Hello Max & All Answering inline. > From: manderse at redhat.com > To: paul.verest at live.com > CC: angelo.zerr at gmail.com; mistria at redhat.com; jbosstools-dev at lists.jboss.org > Subject: Re: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? > Date: Wed, 21 May 2014 11:01:50 +0200 > > On 20 May 2014, at 12:09, Paul Verest wrote: > > > Hello All > > > > First the should be message from Eclipse to remind developers to have > > Help pages (e.g. easily created with > > http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-plugin)that > > references to their project web site. > > Not following what you mean here ? Some plugins are missing home page references. It should be recommended by Eclipse to add one Help page with project introduction One of way to easy add Help page is using GFMV https://github.com/satyagraha/gfm_viewer/blob/master/plugin/src/site/markdown/adding-help-to-eclipse-plugin.md As User I had experience several times before when I could not recall plugin name or find it. > > > I found that plugin developers sometimes event don't have marketplace > > entries (and helped/pushed with about 6-8 ) > > Yes that is a good thing overall. The problem is many plugins don't even > do basic UI interaction well. i.e. litter the context menu > with actions, not integrating with the existing eclipse infrastructure > etc. it results in a very fragmented experience unfortunately ;/ > > >> Should we consider putting some parts of it on Central ? or even in > >> JBDS ? > >> Should we try to lobby with some authors to move projects to > >> Eclipse.org ? > > Could discussion is to get started. > > I suggest to lobby that Eclipse would recognize non-Eclipse.org > > projects under EPL license as valuable part of Eclipse eco-systemthat > > Eclipse project committers should be aware of, give and take help.e.g. > > https://github.com/eclipse-color-theme/eclipse-color-theme > > I'm not following what you mean/expect here ? When have eclipse not seen > non-eclipse.org projects as valuable ? OK. I expressed myself not well. What about - have announces for plugin developers on main eclipse.org page - have essential tutorials, links collected under one link, give list of generally helpful open-source project In the case of https://github.com/eclipse-color-theme/eclipse-color-theme I dialog starting from any Eclipse leader would help, as the project is in uncertain state because of what Eclipse 4 Editors APIs are or would be. > Problem I have is that if it projects don't participate in eclipse > release train nor want to honor eclipse API guidelines they become > something that is really really hard to rely on. Thus we can't include > everything just because it exists. Yes, they are of varying quality. > > > Something like open letter from Eclipse Foundation to Eclipse plugins > > authors. > > What should that say that is not already happening ? > > > By the way looking for (remote) speakers for Eclipse DemoCamp > > Beijinghttps://wiki.eclipse.org/Eclipse_DemoCamps_Luna_2014/Beijing > > You should do that in a separate mail thread instead of mingled in here. > Becomes more visible that way. > > You can post on the community forums too if you prefer. > > > Please also help to connect to Red Hat China managers or marketing. > > Send me mail directly on what you are looking for and I can put you in > contact. Will do. > > /max > http://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140522/70a0a3ea/attachment-0001.html From paul.verest at live.com Thu May 22 06:15:45 2014 From: paul.verest at live.com (Paul Verest) Date: Thu, 22 May 2014 10:15:45 +0000 Subject: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: <537B2FF1.10406@redhat.com> References: <5379CBAC.7070207@redhat.com>, , <537B2FF1.10406@redhat.com> Message-ID: Hi Michael Just want to add that Eclipse is regarded by some as some overhead. Maybe simple explanation and success example can show that it s easy. (Especially with cases when code/interactions continues to be on GitHub) And that would be one more nice addition to what is missing on eclipse.org site. Contributing on GitHub I myself ran into situation when PR are not even commented for a month or two. Date: Tue, 20 May 2014 12:35:29 +0200 From: mistria at redhat.com To: paul.verest at live.com; angelo.zerr at gmail.com CC: jbosstools-dev at lists.jboss.org Subject: Re: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools? Hi Paul, On 05/20/2014 12:09 PM, Paul Verest wrote: I suggest to lobby that Eclipse would recognize non-Eclipse.org projects under EPL license as valuable part of Eclipse eco-system MarketPlace was done to fulfill this goal and it works pretty well. Some non Eclipse.org project have been pretty successful thanks to MarketPlace and MarketPlace client. I think those should thank the Foundation for that. that Eclipse project committers should be aware of, give and take help. e.g. https://github.com/eclipse-color-theme/eclipse-color-theme The issue with the multiplication of projects out of Eclipse.org is that you end up with different process to contribute and don't have the guarantee a contribution would be appreciated and considered. Being on GitHub is not a proof of an open development process, it's "just" OSS code. That's why it makes sense for contributors/consumers (like us) to encourage projects to become official Eclipse projects. Eclipse Foundation has set up rules that ensure a really open development process and that guarantee that a project can't be locked, and that encourage contributions over forks. It makes things safer. Something like open letter from Eclipse Foundation to Eclipse plugins authors. That's probably a good idea. Maybe the Foundation (or the community in general) should make it more official that projects on GitHub/MarketPlace are welcome to become official Eclipse projects and explain to authors that being an Eclipse.org project is a sign of real openness and a generator of success. But in any way, I can fully understand from the Foundation POV and from our "consumer" POV, that there is and will always be a distinction between Eclipse.org and non-Eclipse.org projects. The Foundation rules are definitely something good, that make a difference. Please also help to connect to Red Hat China managers or marketing. Unfortunately, I don't know anyone in Red Hat office in China. Maybe Rob (Stryker) can help. @Angelo Would this email get into jbosstools-dev list? Yes, it's on. And this answer too. Check you CC list before sending mails ;) -- 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/20140522/cecd7cce/attachment.html From vrubezhny at exadel.com Thu May 22 08:19:46 2014 From: vrubezhny at exadel.com (Victor Rubezhny) Date: Thu, 22 May 2014 16:19:46 +0400 Subject: [jbosstools-dev] Need another build for Target Platform Message-ID: <537DEB62.9050709@exadel.com> In order to fix https://issues.jboss.org/browse/JBIDE-15837 (Improve the CordovaJS library provider), which is Targeted to JBT 4.2.0.Beta2 and depends on https://issues.jboss.org/browse/JBIDE-17317 (Update tern-java plug-ins in target platform 4.40.0.Beta2), we need to make another build for Target Platform to use it (updated TP) for JBT 4.2.0.Beta2. Thanks in advance, Victor From mistria at redhat.com Thu May 22 08:30:35 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 22 May 2014 14:30:35 +0200 Subject: [jbosstools-dev] Need another build for Target Platform In-Reply-To: <537DEB62.9050709@exadel.com> References: <537DEB62.9050709@exadel.com> Message-ID: <537DEDEB.2040000@redhat.com> On 05/22/2014 02:19 PM, Victor Rubezhny wrote: > In order to fix https://issues.jboss.org/browse/JBIDE-15837 (Improve the > CordovaJS library provider), which is Targeted to JBT 4.2.0.Beta2 and > depends on https://issues.jboss.org/browse/JBIDE-17317 (Update tern-java > plug-ins in target platform 4.40.0.Beta2), we need to make another build > for Target Platform to use it (updated TP) for JBT 4.2.0.Beta2. As the target-platform is already released, I'm -1 to change the target-platform. However, if Max wants to make an exception and want this to be in Beta2, we can make an exception and release a new 4.40.0.Beta3 target-platform. We have 2 options here: * Delay JBIDE-15837 to Beta3 and keep using 4.40.0.Beta2 to build 4.2.0.Beta2 (current status, no effort) * Release a 4.40.0.Beta3 containing the change for tern (amongst others), and use it to build 4.2.0.Beta2. Since TP 4.40.0.Beta3-SNAPSHOT already contain the change and has been used for the last 12 hours already, it may not require much additional validation and can be done by the end of the day. We need to decide that before branching components so that components are built and tested against the right target-platform before branching. This issues shows that it's not obvious that the target-platform changes have an earlier deadline than Code Freeze. For next time, we'll try to set up more explicit warnings about the deadlines to get dependency change for a given milestone. -- 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/20140522/4f724c0b/attachment.html From manderse at redhat.com Thu May 22 09:55:22 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 22 May 2014 15:55:22 +0200 Subject: [jbosstools-dev] Need another build for Target Platform In-Reply-To: <537DEDEB.2040000@redhat.com> References: <537DEB62.9050709@exadel.com> <537DEDEB.2040000@redhat.com> Message-ID: Yeah, we'll unfortunately need to include this update since the Cordova.js support is important for beta2 work. /max > On 05/22/2014 02:19 PM, Victor Rubezhny wrote: >> In order to fix https://issues.jboss.org/browse/JBIDE-15837 (Improve >> the >> CordovaJS library provider), which is Targeted to JBT 4.2.0.Beta2 and >> depends on https://issues.jboss.org/browse/JBIDE-17317 (Update >> tern-java >> plug-ins in target platform 4.40.0.Beta2), we need to make another >> build >> for Target Platform to use it (updated TP) for JBT 4.2.0.Beta2. > As the target-platform is already released, I'm -1 to change the > target-platform. However, if Max wants to make an exception and want > this to be in Beta2, we can make an exception and release a new > 4.40.0.Beta3 target-platform. > We have 2 options here: > * Delay JBIDE-15837 to Beta3 and keep using 4.40.0.Beta2 to build > 4.2.0.Beta2 (current status, no effort) > * Release a 4.40.0.Beta3 containing the change for tern (amongst > others), and use it to build 4.2.0.Beta2. Since TP > 4.40.0.Beta3-SNAPSHOT already contain the change and has been used for > the last 12 hours already, it may not require much additional > validation and can be done by the end of the day. > > We need to decide that before branching components so that components > are built and tested against the right target-platform before > branching. > > > This issues shows that it's not obvious that the target-platform > changes have an earlier deadline than Code Freeze. For next time, > we'll try to set up more explicit warnings about the deadlines to get > dependency change for a given milestone. /max http://about.me/maxandersen From angelo.zerr at gmail.com Thu May 22 10:04:11 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Thu, 22 May 2014 16:04:11 +0200 Subject: [jbosstools-dev] Need another build for Target Platform In-Reply-To: References: <537DEB62.9050709@exadel.com> <537DEDEB.2040000@redhat.com> Message-ID: Hi all, It's out of scope of this issue, but I think tern plugin CordovaJS should be hosted outside tern.java to avoid creating issues in tern.java like I have done for Tern Dojo Toolkit https://github.com/angelozerr/tern.dojotoolkit, Tern YUI https://github.com/angelozerr/tern.yuidoc For instance you could create a github project "tern.cordovajs" and add some JS tests like I have done. If you decided to create a github project, I will register to this project to observe changes and copy/paste your CordovaJS tern plugin in tern.java What do you think about that? Regards Angelo 2014-05-22 15:55 GMT+02:00 Max Rydahl Andersen : > Yeah, we'll unfortunately need to include this update since the > Cordova.js support is important for beta2 work. > > /max > > > On 05/22/2014 02:19 PM, Victor Rubezhny wrote: > >> In order to fix https://issues.jboss.org/browse/JBIDE-15837 (Improve > >> the > >> CordovaJS library provider), which is Targeted to JBT 4.2.0.Beta2 and > >> depends on https://issues.jboss.org/browse/JBIDE-17317 (Update > >> tern-java > >> plug-ins in target platform 4.40.0.Beta2), we need to make another > >> build > >> for Target Platform to use it (updated TP) for JBT 4.2.0.Beta2. > > As the target-platform is already released, I'm -1 to change the > > target-platform. However, if Max wants to make an exception and want > > this to be in Beta2, we can make an exception and release a new > > 4.40.0.Beta3 target-platform. > > We have 2 options here: > > * Delay JBIDE-15837 to Beta3 and keep using 4.40.0.Beta2 to build > > 4.2.0.Beta2 (current status, no effort) > > * Release a 4.40.0.Beta3 containing the change for tern (amongst > > others), and use it to build 4.2.0.Beta2. Since TP > > 4.40.0.Beta3-SNAPSHOT already contain the change and has been used for > > the last 12 hours already, it may not require much additional > > validation and can be done by the end of the day. > > > > We need to decide that before branching components so that components > > are built and tested against the right target-platform before > > branching. > > > > > > This issues shows that it's not obvious that the target-platform > > changes have an earlier deadline than Code Freeze. For next time, > > we'll try to set up more explicit warnings about the deadlines to get > > dependency change for a given milestone. > > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140522/e243db95/attachment-0001.html From manderse at redhat.com Thu May 22 10:08:17 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 22 May 2014 16:08:17 +0200 Subject: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: References: <5379CBAC.7070207@redhat.com> <537B2FF1.10406@redhat.com> Message-ID: <9F4C49AF-92AF-440B-9596-3310DF8C9EE7@redhat.com> On 22 May 2014, at 12:15, Paul Verest wrote: > Hi Michael > > Just want to add that Eclipse is regarded by some as some overhead. yes, and if you don't want to do that overhead you can't expect to be integrated in overall solutions. That is fine and complete fair to say. > Maybe simple explanation and success example can show that it s easy. vert.x is at eclipse now - yes, there is overhead but github is used for contributions. > (Especially with cases when code/interactions continues to be on > GitHub) > And that would be one more nice addition to what is missing on > eclipse.org site. What page are you looking at where this is not highlighted enough ? > Contributing on GitHub I myself ran into situation when PR are not > even commented for a month or two. Yes? that is same wether in or outside eclipse. It is wether there are people working actively enough on projects. /max > Date: Tue, 20 May 2014 12:35:29 +0200 > From: mistria at redhat.com > To: paul.verest at live.com; angelo.zerr at gmail.com > CC: jbosstools-dev at lists.jboss.org > Subject: Re: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss > Tools? > > > > > > > Hi Paul, > > > > On 05/20/2014 12:09 PM, Paul Verest wrote: > > > > > I suggest to lobby that Eclipse would recognize > non-Eclipse.org projects under EPL license as valuable part of > Eclipse eco-system > > MarketPlace was done to fulfill this goal and it works pretty well. > Some non Eclipse.org project have been pretty successful thanks to > MarketPlace and MarketPlace client. I think those should thank the > Foundation for that. > > > > > > that Eclipse project committers should be aware of, give > and take help. > e.g. https://github.com/eclipse-color-theme/eclipse-color-theme > > > > > The issue with the multiplication of projects out of Eclipse.org is > that you end up with different process to contribute and don't have > the guarantee a contribution would be appreciated and considered. > Being on GitHub is not a proof of an open development process, it's > "just" OSS code. That's why it makes sense for > contributors/consumers (like us) to encourage projects to become > official Eclipse projects. Eclipse Foundation has set up rules that > ensure a really open development process and that guarantee that a > project can't be locked, and that encourage contributions over > forks. It makes things safer. > > > > > > Something like open letter from Eclipse Foundation to > Eclipse plugins authors. > > > That's probably a good idea. > > Maybe the Foundation (or the community in general) should make it > more official that projects on GitHub/MarketPlace are welcome to > become official Eclipse projects and explain to authors that being > an Eclipse.org project is a sign of real openness and a generator of > success. > > > > But in any way, I can fully understand from the Foundation POV and > from our "consumer" POV, that there is and will always be a > distinction between Eclipse.org and non-Eclipse.org projects. The > Foundation rules are definitely something good, that make a > difference. > > > > > > > Please also help to connect to Red Hat China managers or > marketing. > > > > Unfortunately, I don't know anyone in Red Hat office in China. Maybe > Rob (Stryker) can help. > > > > > > > @Angelo Would this email get into jbosstools-dev list? > > > > Yes, it's on. And this answer too. Check you CC list before sending > mails ;) > > -- > > Mickael Istria > > Eclipse developer at JBoss, > by Red Hat > > My blog - My Tweets > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From mistria at redhat.com Thu May 22 10:28:44 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 22 May 2014 16:28:44 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta3 Message-ID: <537E099C.5040707@redhat.com> On popular demand, I'm about to start the process of releasing target-platform 4.40.0.Beta3, which is based on current 4.40.0.Beta3-SNAPSHOT. So while I'm doing that, please all try to build and test your component with the 4.40.0.Beta3-SNAPSHOT. Changes are: * Update of m2e-apt * Come back of Birt (in its RC1 version for Luna) * Update of tern.java -- 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/20140522/23ea7cce/attachment.html From nboldt at redhat.com Thu May 22 11:31:16 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 22 May 2014 11:31:16 -0400 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta3 In-Reply-To: <537E099C.5040707@redhat.com> References: <537E099C.5040707@redhat.com> Message-ID: <537E1844.8090100@redhat.com> In addition, m2e.jdt has been removed from the JBDS TP and has moved to the JBoss Central TP [1]. [1] https://issues.jboss.org/browse/JBIDE-16757 Note that the parent pom (in master branch) is already set up to use 4.40.0.Beta3-SNAPSHOT by default; otherwise, use this to force the correct version: mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT On 05/22/2014 10:28 AM, Mickael Istria wrote: > On popular demand, I'm about to start the process of releasing > target-platform 4.40.0.Beta3, which is based on current > 4.40.0.Beta3-SNAPSHOT. > So while I'm doing that, please all try to build and test your component > with the 4.40.0.Beta3-SNAPSHOT. > > Changes are: > * Update of m2e-apt > * Come back of Birt (in its RC1 version for Luna) > * Update of tern.java > -- > 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 Thu May 22 12:15:49 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 22 May 2014 12:15:49 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta2 / JBDS 8.0.0.Beta2 Message-ID: <537E22B5.7010109@redhat.com> The code freeze is on now, Thurs, May 22, 2014, so please ensure you are branched ASAP. Task JIRA created for this milestone include: JBDS : https://issues.jboss.org/browse/JBDS-3031 JBoss Tools : https://issues.jboss.org/browse/JBIDE-17322 Aerogear : https://issues.jboss.org/browse/JBIDE-17323 JST : https://issues.jboss.org/browse/JBIDE-17324 VPE : https://issues.jboss.org/browse/JBIDE-17325 JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17326 Central Discovery : https://issues.jboss.org/browse/JBIDE-17327 Server : https://issues.jboss.org/browse/JBIDE-17328 Hibernate : https://issues.jboss.org/browse/JBIDE-17329 Base : https://issues.jboss.org/browse/JBIDE-17330 OpenShift : https://issues.jboss.org/browse/JBIDE-17331 JavaEE : https://issues.jboss.org/browse/JBIDE-17332 Birt : https://issues.jboss.org/browse/JBIDE-17333 Forge : https://issues.jboss.org/browse/JBIDE-17334 Webservices : https://issues.jboss.org/browse/JBIDE-17335 Arquillian : https://issues.jboss.org/browse/JBIDE-17336 Central : https://issues.jboss.org/browse/JBIDE-17337 Portlet : https://issues.jboss.org/browse/JBIDE-17338 LiveReload : https://issues.jboss.org/browse/JBIDE-17339 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Thu May 22 12:55:18 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 22 May 2014 18:55:18 +0200 Subject: [jbosstools-dev] Target Platform 4.40.0.Beta3, for JBoss Tools 4.2.0.Beta2 has been released Message-ID: <537E2BF6.4080100@redhat.com> Changes (compared to 4.40.0.Beta2) ======= * JBIDE-17254: Updated version of tern.java * JBIDE-17266: Re-added Birt (RC1 version for Luna) * JBIDE-17306: Updated m2e-apt * JBIDE-16757: Remove m2e-jdt Usage ===== Target platform 4.40.0.Beta3 is what JBoss Tools 4.2.0.Beta2 will use. All Jenkins jobs for branch and parent pom 4.2.0.Beta2-SNAPSHOT have been updated to use target platform 4.40.0.Beta3. 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/ * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/luna/ Download ======== Update site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta3/REPO/ Update site zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta3/jbosstoolstarget-4.40.0.Beta3.zip Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta3 Testing/Development =================== If your root pom correctly specifies the latest parent pom version as 4.2.0.Beta2-SNAPSHOT, you need only this: $ mvn clean verify If you're using a different parent pom, use this: $ mvn clean verify -Dtpc.version=4.40.0.Beta3 For advanced 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.Beta4-SNAPSHOT. We can at least expect for Beta4: * Move to Luna release/R/SR0 * 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, June 30th* All Jenkins jobs for *master* have been updated to use target platform 4.40.0.Beta4-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 -- 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/20140522/24da1fde/attachment.html From manderse at redhat.com Thu May 22 14:14:49 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 22 May 2014 20:14:49 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta3 In-Reply-To: <537E1844.8090100@redhat.com> References: <537E099C.5040707@redhat.com> <537E1844.8090100@redhat.com> Message-ID: <03EC2BA9-07D8-4987-AD08-CDB38BB68255@redhat.com> On 22 May 2014, at 17:31, Nick Boldt wrote: > In addition, m2e.jdt has been removed from the JBDS TP and has moved to > the JBoss Central TP [1]. > > [1] https://issues.jboss.org/browse/JBIDE-16757 I surely hope this does not mean it is not installed by default in JBDS ? /max > > Note that the parent pom (in master branch) is already set up to use > 4.40.0.Beta3-SNAPSHOT by default; otherwise, use this to force the > correct version: > > mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT > > > On 05/22/2014 10:28 AM, Mickael Istria wrote: >> On popular demand, I'm about to start the process of releasing >> target-platform 4.40.0.Beta3, which is based on current >> 4.40.0.Beta3-SNAPSHOT. >> So while I'm doing that, please all try to build and test your component >> with the 4.40.0.Beta3-SNAPSHOT. >> >> Changes are: >> * Update of m2e-apt >> * Come back of Birt (in its RC1 version for Luna) >> * Update of tern.java >> -- >> 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 > _______________________________________________ > 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 Thu May 22 14:29:54 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 22 May 2014 20:29:54 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta3 In-Reply-To: <03EC2BA9-07D8-4987-AD08-CDB38BB68255@redhat.com> References: <537E099C.5040707@redhat.com> <537E1844.8090100@redhat.com> <03EC2BA9-07D8-4987-AD08-CDB38BB68255@redhat.com> Message-ID: <3F0913D5-FD48-40C0-8280-9826264EEB2F@redhat.com> On 22 May 2014, at 20:14, Max Rydahl Andersen wrote: > On 22 May 2014, at 17:31, Nick Boldt wrote: > >> In addition, m2e.jdt has been removed from the JBDS TP and has moved >> to >> the JBoss Central TP [1]. >> >> [1] https://issues.jboss.org/browse/JBIDE-16757 > > I surely hope this does not mean it is not installed by default in > JBDS ? apparently it was... and this is *EXACTLY* why TP changes should not be done last day before code freeze, nor be approved by the same people that actually requested the change. Individuals miss things. /max > > /max > >> >> Note that the parent pom (in master branch) is already set up to use >> 4.40.0.Beta3-SNAPSHOT by default; otherwise, use this to force the >> correct version: >> >> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT >> >> >> On 05/22/2014 10:28 AM, Mickael Istria wrote: >>> On popular demand, I'm about to start the process of releasing >>> target-platform 4.40.0.Beta3, which is based on current >>> 4.40.0.Beta3-SNAPSHOT. >>> So while I'm doing that, please all try to build and test your >>> component >>> with the 4.40.0.Beta3-SNAPSHOT. >>> >>> Changes are: >>> * Update of m2e-apt >>> * Come back of Birt (in its RC1 version for Luna) >>> * Update of tern.java >>> -- >>> 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 >> _______________________________________________ >> 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 nboldt at redhat.com Thu May 22 14:38:55 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 22 May 2014 14:38:55 -0400 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta3 In-Reply-To: <3F0913D5-FD48-40C0-8280-9826264EEB2F@redhat.com> References: <537E099C.5040707@redhat.com> <537E1844.8090100@redhat.com> <03EC2BA9-07D8-4987-AD08-CDB38BB68255@redhat.com> <3F0913D5-FD48-40C0-8280-9826264EEB2F@redhat.com> Message-ID: <537E443F.50108@redhat.com> Individuals also fail to read emails that explain the upcoming changes. :) So, I'll rollback this last change, even though Fred did put forth some compelling reasons to remove it. *shrug* On 05/22/2014 02:29 PM, Max Rydahl Andersen wrote: > On 22 May 2014, at 20:14, Max Rydahl Andersen wrote: > >> On 22 May 2014, at 17:31, Nick Boldt wrote: >> >>> In addition, m2e.jdt has been removed from the JBDS TP and has moved to >>> the JBoss Central TP [1]. >>> >>> [1] https://issues.jboss.org/browse/JBIDE-16757 >> >> I surely hope this does not mean it is not installed by default in JBDS ? > > apparently it was... > > and this is *EXACTLY* why TP changes should not be done last day before > code freeze, > nor be approved by the same people that actually requested the change. > > Individuals miss things. > > /max > >> >> /max >> >>> >>> Note that the parent pom (in master branch) is already set up to use >>> 4.40.0.Beta3-SNAPSHOT by default; otherwise, use this to force the >>> correct version: >>> >>> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT >>> >>> >>> On 05/22/2014 10:28 AM, Mickael Istria wrote: >>>> On popular demand, I'm about to start the process of releasing >>>> target-platform 4.40.0.Beta3, which is based on current >>>> 4.40.0.Beta3-SNAPSHOT. >>>> So while I'm doing that, please all try to build and test your >>>> component >>>> with the 4.40.0.Beta3-SNAPSHOT. >>>> >>>> Changes are: >>>> * Update of m2e-apt >>>> * Come back of Birt (in its RC1 version for Luna) >>>> * Update of tern.java >>>> -- >>>> 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 >>> _______________________________________________ >>> 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 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Thu May 22 14:54:55 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 22 May 2014 20:54:55 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta3 In-Reply-To: <537E443F.50108@redhat.com> References: <537E099C.5040707@redhat.com> <537E1844.8090100@redhat.com> <03EC2BA9-07D8-4987-AD08-CDB38BB68255@redhat.com> <3F0913D5-FD48-40C0-8280-9826264EEB2F@redhat.com> <537E443F.50108@redhat.com> Message-ID: <73A7E249-A476-49B9-AFBF-D36EE1DB551E@redhat.com> On 22 May 2014, at 20:38, Nick Boldt wrote: > Individuals also fail to read emails that explain the upcoming > changes. :) There was *zero* changes expected for the TP this morning. Still we had like 4 in the last minute. None of them needed to be there except with some fair reason the cordova.js required one. > So, I'll rollback this last change, even though Fred did put forth > some compelling reasons to remove it. *shrug* And Fred was the one approving the change - see the problem ? :) /max > On 05/22/2014 02:29 PM, Max Rydahl Andersen wrote: >> On 22 May 2014, at 20:14, Max Rydahl Andersen wrote: >> >>> On 22 May 2014, at 17:31, Nick Boldt wrote: >>> >>>> In addition, m2e.jdt has been removed from the JBDS TP and has >>>> moved to >>>> the JBoss Central TP [1]. >>>> >>>> [1] https://issues.jboss.org/browse/JBIDE-16757 >>> >>> I surely hope this does not mean it is not installed by default in >>> JBDS ? >> >> apparently it was... >> >> and this is *EXACTLY* why TP changes should not be done last day >> before >> code freeze, >> nor be approved by the same people that actually requested the >> change. >> >> Individuals miss things. >> >> /max >> >>> >>> /max >>> >>>> >>>> Note that the parent pom (in master branch) is already set up to >>>> use >>>> 4.40.0.Beta3-SNAPSHOT by default; otherwise, use this to force the >>>> correct version: >>>> >>>> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT >>>> >>>> >>>> On 05/22/2014 10:28 AM, Mickael Istria wrote: >>>>> On popular demand, I'm about to start the process of releasing >>>>> target-platform 4.40.0.Beta3, which is based on current >>>>> 4.40.0.Beta3-SNAPSHOT. >>>>> So while I'm doing that, please all try to build and test your >>>>> component >>>>> with the 4.40.0.Beta3-SNAPSHOT. >>>>> >>>>> Changes are: >>>>> * Update of m2e-apt >>>>> * Come back of Birt (in its RC1 version for Luna) >>>>> * Update of tern.java >>>>> -- >>>>> 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 >>>> _______________________________________________ >>>> 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 > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com /max http://about.me/maxandersen From manderse at redhat.com Thu May 22 15:30:02 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 22 May 2014 21:30:02 +0200 Subject: [jbosstools-dev] Upcoming target-platform 4.40.0.Beta3 In-Reply-To: <73A7E249-A476-49B9-AFBF-D36EE1DB551E@redhat.com> References: <537E099C.5040707@redhat.com> <537E1844.8090100@redhat.com> <03EC2BA9-07D8-4987-AD08-CDB38BB68255@redhat.com> <3F0913D5-FD48-40C0-8280-9826264EEB2F@redhat.com> <537E443F.50108@redhat.com> <73A7E249-A476-49B9-AFBF-D36EE1DB551E@redhat.com> Message-ID: <57DEF7FF-E093-401D-8D76-1911DC0E748C@redhat.com> On 22 May 2014, at 20:54, Max Rydahl Andersen wrote: > On 22 May 2014, at 20:38, Nick Boldt wrote: > >> Individuals also fail to read emails that explain the upcoming >> changes. :) > > There was *zero* changes expected for the TP this morning. Still we > had > like 4 in the last minute. > > None of them needed to be there except with some fair reason the > cordova.js required one. > >> So, I'll rollback this last change, even though Fred did put forth >> some compelling reasons to remove it. *shrug* > > And Fred was the one approving the change - see the problem ? :) btw. for those who don't know, here is the process we have that is supposed to avoid this stuff: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc Highlights: Goals: Avoid unnecessary churn (failed builds) Avoid adding unnecessary or incomplete dependencies Document why and when changes occur And especially: *Test* before making it live: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#test-local-target-platform-use "Generally, developers should have 7 days to review a proposed change. However, for more urgent changes (such as to fix a broken contribution from a previous PR or to remove something on which no projects still depend), 1 or 2 days may be sufficient." https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#await-feedback In this case the *only* change that was relevant to do this close to Beta2 was the Tern update and even that could have waited and be handled in a respin where there would be *WAY* less stress about it. Here is to us not seeing breakage caused by TP updates on next code freeze :) /max > /max > >> On 05/22/2014 02:29 PM, Max Rydahl Andersen wrote: >>> On 22 May 2014, at 20:14, Max Rydahl Andersen wrote: >>> >>>> On 22 May 2014, at 17:31, Nick Boldt wrote: >>>> >>>>> In addition, m2e.jdt has been removed from the JBDS TP and has >>>>> moved to >>>>> the JBoss Central TP [1]. >>>>> >>>>> [1] https://issues.jboss.org/browse/JBIDE-16757 >>>> >>>> I surely hope this does not mean it is not installed by default in >>>> JBDS ? >>> >>> apparently it was... >>> >>> and this is *EXACTLY* why TP changes should not be done last day >>> before >>> code freeze, >>> nor be approved by the same people that actually requested the >>> change. >>> >>> Individuals miss things. >>> >>> /max >>> >>>> >>>> /max >>>> >>>>> >>>>> Note that the parent pom (in master branch) is already set up to >>>>> use >>>>> 4.40.0.Beta3-SNAPSHOT by default; otherwise, use this to force the >>>>> correct version: >>>>> >>>>> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT >>>>> >>>>> >>>>> On 05/22/2014 10:28 AM, Mickael Istria wrote: >>>>>> On popular demand, I'm about to start the process of releasing >>>>>> target-platform 4.40.0.Beta3, which is based on current >>>>>> 4.40.0.Beta3-SNAPSHOT. >>>>>> So while I'm doing that, please all try to build and test your >>>>>> component >>>>>> with the 4.40.0.Beta3-SNAPSHOT. >>>>>> >>>>>> Changes are: >>>>>> * Update of m2e-apt >>>>>> * Come back of Birt (in its RC1 version for Luna) >>>>>> * Update of tern.java >>>>>> -- >>>>>> 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 >>>>> _______________________________________________ >>>>> 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 >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com > > > /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 fbricon at redhat.com Thu May 22 18:15:13 2014 From: fbricon at redhat.com (Fred Bricon) Date: Fri, 23 May 2014 00:15:13 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta2 / JBDS 8.0.0.Beta2 In-Reply-To: <537E22B5.7010109@redhat.com> References: <537E22B5.7010109@redhat.com> Message-ID: <537E76F1.1030608@redhat.com> jbosstools-central done Le 22/05/2014 18:15, Nick Boldt a ?crit : > The code freeze is on now, Thurs, May 22, 2014, so please ensure you are > branched ASAP. > > Task JIRA created for this milestone include: > > JBDS : https://issues.jboss.org/browse/JBDS-3031 > JBoss Tools : https://issues.jboss.org/browse/JBIDE-17322 > Aerogear : https://issues.jboss.org/browse/JBIDE-17323 > JST : https://issues.jboss.org/browse/JBIDE-17324 > VPE : https://issues.jboss.org/browse/JBIDE-17325 > JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17326 > Central Discovery : https://issues.jboss.org/browse/JBIDE-17327 > Server : https://issues.jboss.org/browse/JBIDE-17328 > Hibernate : https://issues.jboss.org/browse/JBIDE-17329 > Base : https://issues.jboss.org/browse/JBIDE-17330 > OpenShift : https://issues.jboss.org/browse/JBIDE-17331 > JavaEE : https://issues.jboss.org/browse/JBIDE-17332 > Birt : https://issues.jboss.org/browse/JBIDE-17333 > Forge : https://issues.jboss.org/browse/JBIDE-17334 > Webservices : https://issues.jboss.org/browse/JBIDE-17335 > Arquillian : https://issues.jboss.org/browse/JBIDE-17336 > Central : https://issues.jboss.org/browse/JBIDE-17337 > Portlet : https://issues.jboss.org/browse/JBIDE-17338 > LiveReload : https://issues.jboss.org/browse/JBIDE-17339 > From xcoulon at redhat.com Thu May 22 21:23:46 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Fri, 23 May 2014 03:23:46 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta2 / JBDS 8.0.0.Beta2 In-Reply-To: <537E76F1.1030608@redhat.com> References: <537E22B5.7010109@redhat.com> <537E76F1.1030608@redhat.com> Message-ID: <3FE7BA8F-725B-43E0-A222-AB6B3EB9A8F1@redhat.com> Done for Webservices and LiveReload. Best regards, /Xavier On 23 May 2014, at 00:15, Fred Bricon wrote: > jbosstools-central done > > Le 22/05/2014 18:15, Nick Boldt a ?crit : >> The code freeze is on now, Thurs, May 22, 2014, so please ensure you are >> branched ASAP. >> >> Task JIRA created for this milestone include: >> >> JBDS : https://issues.jboss.org/browse/JBDS-3031 >> JBoss Tools : https://issues.jboss.org/browse/JBIDE-17322 >> Aerogear : https://issues.jboss.org/browse/JBIDE-17323 >> JST : https://issues.jboss.org/browse/JBIDE-17324 >> VPE : https://issues.jboss.org/browse/JBIDE-17325 >> JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17326 >> Central Discovery : https://issues.jboss.org/browse/JBIDE-17327 >> Server : https://issues.jboss.org/browse/JBIDE-17328 >> Hibernate : https://issues.jboss.org/browse/JBIDE-17329 >> Base : https://issues.jboss.org/browse/JBIDE-17330 >> OpenShift : https://issues.jboss.org/browse/JBIDE-17331 >> JavaEE : https://issues.jboss.org/browse/JBIDE-17332 >> Birt : https://issues.jboss.org/browse/JBIDE-17333 >> Forge : https://issues.jboss.org/browse/JBIDE-17334 >> Webservices : https://issues.jboss.org/browse/JBIDE-17335 >> Arquillian : https://issues.jboss.org/browse/JBIDE-17336 >> Central : https://issues.jboss.org/browse/JBIDE-17337 >> Portlet : https://issues.jboss.org/browse/JBIDE-17338 >> LiveReload : https://issues.jboss.org/browse/JBIDE-17339 >> > > _______________________________________________ > 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/20140523/d32b56f2/attachment-0001.html From paul.verest at live.com Fri May 23 03:45:05 2014 From: paul.verest at live.com (Paul Verest) Date: Fri, 23 May 2014 07:45:05 +0000 Subject: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: <9F4C49AF-92AF-440B-9596-3310DF8C9EE7@redhat.com> References: <5379CBAC.7070207@redhat.com>, , <537B2FF1.10406@redhat.com>, , <9F4C49AF-92AF-440B-9596-3310DF8C9EE7@redhat.com> Message-ID: Hello All Next step could be Eclipse bug when the time is appropriate > From: manderse at redhat.com > To: paul.verest at live.com > CC: mistria at redhat.com; angelo.zerr at gmail.com; jbosstools-dev at lists.jboss.org > Subject: Re: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? > Date: Thu, 22 May 2014 16:08:17 +0200 > > On 22 May 2014, at 12:15, Paul Verest wrote: > > > Hi Michael > > > > Just want to add that Eclipse is regarded by some as some overhead. > > yes, and if you don't want to do that overhead you can't expect to be > integrated > in overall solutions. That is fine and complete fair to say. It is great that we agree about overhead. When it is said openly and with exact additional steps,that would make it clear and comprehensive. > > > Maybe simple explanation and success example can show that it s easy. > > vert.x is at eclipse now - yes, there is overhead but github is used for > contributions. > > > (Especially with cases when code/interactions continues to be on > > GitHub) > > And that would be one more nice addition to what is missing on > > eclipse.org site. > > What page are you looking at where this is not highlighted enough ? I don't know URLs to concise answer to this thread topic. > > > Contributing on GitHub I myself ran into situation when PR are not > > even commented for a month or two. > > Yes? that is same wether in or outside eclipse. It is wether there are > people working actively enough on projects. > > /max > > Date: Tue, 20 May 2014 12:35:29 +0200 > > From: mistria at redhat.com > > To: paul.verest at live.com; angelo.zerr at gmail.com > > CC: jbosstools-dev at lists.jboss.org > > Subject: Re: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss > > Tools? > > > > > > > > > > > > > > Hi Paul, > > > > > > > > On 05/20/2014 12:09 PM, Paul Verest wrote: > > > > > > > > > > I suggest to lobby that Eclipse would recognize > > non-Eclipse.org projects under EPL license as valuable part of > > Eclipse eco-system > > > > MarketPlace was done to fulfill this goal and it works pretty well. > > Some non Eclipse.org project have been pretty successful thanks to > > MarketPlace and MarketPlace client. I think those should thank the > > Foundation for that. > > > > > > > > > > > > that Eclipse project committers should be aware of, give > > and take help. > > e.g. https://github.com/eclipse-color-theme/eclipse-color-theme > > > > > > > > > > The issue with the multiplication of projects out of Eclipse.org is > > that you end up with different process to contribute and don't have > > the guarantee a contribution would be appreciated and considered. > > Being on GitHub is not a proof of an open development process, it's > > "just" OSS code. That's why it makes sense for > > contributors/consumers (like us) to encourage projects to become > > official Eclipse projects. Eclipse Foundation has set up rules that > > ensure a really open development process and that guarantee that a > > project can't be locked, and that encourage contributions over > > forks. It makes things safer. > > > > > > > > > > > > Something like open letter from Eclipse Foundation to > > Eclipse plugins authors. > > > > > > That's probably a good idea. > > > > Maybe the Foundation (or the community in general) should make it > > more official that projects on GitHub/MarketPlace are welcome to > > become official Eclipse projects and explain to authors that being > > an Eclipse.org project is a sign of real openness and a generator of > > success. > > > > > > > > But in any way, I can fully understand from the Foundation POV and > > from our "consumer" POV, that there is and will always be a > > distinction between Eclipse.org and non-Eclipse.org projects. The > > Foundation rules are definitely something good, that make a > > difference. > > > > > > > > > > > > > > Please also help to connect to Red Hat China managers or > > marketing. > > > > > > > > Unfortunately, I don't know anyone in Red Hat office in China. Maybe > > Rob (Stryker) can help. > > > > > > > > > > > > > > @Angelo Would this email get into jbosstools-dev list? > > > > > > > > Yes, it's on. And this answer too. Check you CC list before sending > > mails ;) > > > > -- > > > > Mickael Istria > > > > Eclipse developer at JBoss, > > by Red Hat > > > > My blog - My Tweets > > _______________________________________________ > > jbosstools-dev mailing list > > jbosstools-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140523/7cefc130/attachment.html From manderse at redhat.com Fri May 23 03:59:30 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 23 May 2014 09:59:30 +0200 Subject: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: References: <5379CBAC.7070207@redhat.com> <537B2FF1.10406@redhat.com> <9F4C49AF-92AF-440B-9596-3310DF8C9EE7@redhat.com> Message-ID: <6E1D94D9-1BD0-4CC0-9C84-6713BDC0883A@redhat.com> >>> Just want to add that Eclipse is regarded by some as some overhead. >> >> yes, and if you don't want to do that overhead you can't expect to be >> integrated >> in overall solutions. That is fine and complete fair to say. > It is great that we agree about overhead. When it is said openly and > with exact additional steps,that would make it clear and > comprehensive. Funny enough i'm not really following what you mean with "said openly and with exact additional steps" ? You want someone from eclipse.org to say "The Eclipse process might be perceived as heavy and not for everyone - but that is OK." ? >>> Maybe simple explanation and success example can show that it s >>> easy. >> >> vert.x is at eclipse now - yes, there is overhead but github is used >> for >> contributions. >> >>> (Especially with cases when code/interactions continues to be on >>> GitHub) >>> And that would be one more nice addition to what is missing on >>> eclipse.org site. >> >> What page are you looking at where this is not highlighted enough ? > I don't know URLs to concise answer to this thread topic. Okey but you said it is somehow missing on eclipse.org so i'm just wondering where you have been looking ? Here is first hits I get when searching eclipse.org github: http://wiki.eclipse.org/GitHub searching on the wiki gives you details on how you hook up the CLA check: http://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub and http://wiki.eclipse.org/Development_Resources explains it too. and finally the most central page on this is probably http://wiki.eclipse.org/Social_Coding What is the page/info you feel are missing in the above ? I think the problem you are seeing is a perception problem and that eclipse.org actually have gone a long way since many years ago. Yes, there is still a process, and yes it is heavy at times when you need to check your dependencies are actually clean - but in day to day work it is really not different than any other project. /max http://about.me/maxandersen From paul.verest at live.com Fri May 23 04:20:25 2014 From: paul.verest at live.com (Paul Verest) Date: Fri, 23 May 2014 08:20:25 +0000 Subject: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: <6E1D94D9-1BD0-4CC0-9C84-6713BDC0883A@redhat.com> References: <5379CBAC.7070207@redhat.com>, , <537B2FF1.10406@redhat.com>, , <9F4C49AF-92AF-440B-9596-3310DF8C9EE7@redhat.com>, , <6E1D94D9-1BD0-4CC0-9C84-6713BDC0883A@redhat.com> Message-ID: Hello All > From: manderse at redhat.com > To: paul.verest at live.com > CC: mistria at redhat.com; angelo.zerr at gmail.com; jbosstools-dev at lists.jboss.org > Subject: Re: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? > Date: Fri, 23 May 2014 09:59:30 +0200 > > >>> Just want to add that Eclipse is regarded by some as some overhead. > >> > >> yes, and if you don't want to do that overhead you can't expect to be > >> integrated > >> in overall solutions. That is fine and complete fair to say. > > It is great that we agree about overhead. When it is said openly and > > with exact additional steps,that would make it clear and > > comprehensive. > > Funny enough i'm not really following what you mean with "said openly > and with exact additional steps" ? > > You want someone from eclipse.org to say "The Eclipse process might be > perceived as heavy and not for everyone - but that is OK." ? Something like Eclipse process adds a few steps- signing CLA [link]- setting up project on Github [link], Ecipse git [link] I have never contributed to Eclipse project,so I don't know exact steps. > > >>> Maybe simple explanation and success example can show that it s > >>> easy. > >> > >> vert.x is at eclipse now - yes, there is overhead but github is used > >> for > >> contributions. > >> > >>> (Especially with cases when code/interactions continues to be on > >>> GitHub) > >>> And that would be one more nice addition to what is missing on > >>> eclipse.org site. > >> > >> What page are you looking at where this is not highlighted enough ? > > I don't know URLs to concise answer to this thread topic. > > Okey but you said it is somehow missing on eclipse.org so i'm just > wondering where you have been looking ? http://www.eclipse.org/committers/I did not really know what to search.Eclipse has a lot of resources in many places with different level of relevance. > > Here is first hits I get when searching eclipse.org github: > > http://wiki.eclipse.org/GitHub > > searching on the wiki gives you details on how you hook up the CLA > check: http://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub > > and http://wiki.eclipse.org/Development_Resources explains it too. > > and finally the most central page on this is probably > http://wiki.eclipse.org/Social_Coding > > What is the page/info you feel are missing in the above ? > > I think the problem you are seeing is a perception problem and that > eclipse.org actually have gone > a long way since many years ago. Yes, there is still a process, and yes > it is heavy at times when you need > to check your dependencies are actually clean - but in day to day work > it is really not different than > any other project. Well. That was discussion between the person who knows (Max)and the person who didn't see what he had imagine (Paul). Now I know how to start and where to ask when needed. > > /max > http://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140523/2afb255b/attachment-0001.html From mistria at redhat.com Fri May 23 05:14:39 2014 From: mistria at redhat.com (Mickael Istria) Date: Fri, 23 May 2014 11:14:39 +0200 Subject: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: References: <5379CBAC.7070207@redhat.com>, , <537B2FF1.10406@redhat.com>, , <9F4C49AF-92AF-440B-9596-3310DF8C9EE7@redhat.com>, , <6E1D94D9-1BD0-4CC0-9C84-6713BDC0883A@redhat.com> Message-ID: <537F117F.30206@redhat.com> On 05/23/2014 10:20 AM, Paul Verest wrote: > Eclipse process adds a few steps > - signing CLA [link] > - setting up project on Github [link], Ecipse git [link] Most projects have an "How to contribute" or equivalent page where this is usually clearly explained. Many projects use the same development tools/workflows (Bugzilla/Gerrit/Git/Jenkins) so you only have to learn it once. If you need assistance on how to contribute, projects have open communication channels where this can be asked. > I have never contributed to Eclipse project, > so I don't know exact steps. What would be interesting is to first know if you tried, and if yes, where were you blocked ? In many cases, just trying is enough to accomplish something. > http://www.eclipse.org/committers/ > I did not really know what to search. > Eclipse has a lot of resources in many places with different level of > relevance. What do you want to do? What is the question you're seeking answers for? It may sound harsh, but I have the impression that many people just take the process as an excuse for not contributing, without having even evaluated the difficulty of adopting it or even tried it. I've sometimes heard "it's not on GitHub, I don't know how to contribute, so I don't contribute". In such case, it's also the responsibility of the developer to learn things and ask for questions in order to become a contributor. The Foundation isn't to blame. People who want to do things can do them, that's all that matters. > Well. That was discussion between the person who knows (Max) > and the person who didn't see what he had imagine (Paul). > > Now I know how to start and where to ask when needed. Your feedback has a lot of value. It can be used to make the process and tools easier to understand and use, which is the main way to get more people contributing. The contribution process is a forever-evolving one, because of new constraints, new ideas, new tools, new technologies... You can use this bug to suggest some improvements to this process https://bugs.eclipse.org/bugs/show_bug.cgi?id=435599 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/20140523/cdc6a7cd/attachment.html From gorkem.ercan at gmail.com Fri May 23 10:33:14 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Fri, 23 May 2014 10:33:14 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for JBT 4.2.0.Beta2 / JBDS 8.0.0.Beta2 In-Reply-To: <3FE7BA8F-725B-43E0-A222-AB6B3EB9A8F1@redhat.com> References: <537E22B5.7010109@redhat.com> <537E76F1.1030608@redhat.com> <3FE7BA8F-725B-43E0-A222-AB6B3EB9A8F1@redhat.com> Message-ID: Done for aerogear. -- Gorkem On Thu, May 22, 2014 at 9:23 PM, Xavier Coulon wrote: > Done for Webservices and LiveReload. > > Best regards, > /Xavier > > > > On 23 May 2014, at 00:15, Fred Bricon wrote: > > jbosstools-central done > > Le 22/05/2014 18:15, Nick Boldt a ?crit : > > The code freeze is on now, Thurs, May 22, 2014, so please ensure you are > branched ASAP. > > Task JIRA created for this milestone include: > > JBDS : https://issues.jboss.org/browse/JBDS-3031 > JBoss Tools : https://issues.jboss.org/browse/JBIDE-17322 > Aerogear : https://issues.jboss.org/browse/JBIDE-17323 > JST : https://issues.jboss.org/browse/JBIDE-17324 > VPE : https://issues.jboss.org/browse/JBIDE-17325 > JBT Update Sites : https://issues.jboss.org/browse/JBIDE-17326 > Central Discovery : https://issues.jboss.org/browse/JBIDE-17327 > Server : https://issues.jboss.org/browse/JBIDE-17328 > Hibernate : https://issues.jboss.org/browse/JBIDE-17329 > Base : https://issues.jboss.org/browse/JBIDE-17330 > OpenShift : https://issues.jboss.org/browse/JBIDE-17331 > JavaEE : https://issues.jboss.org/browse/JBIDE-17332 > Birt : https://issues.jboss.org/browse/JBIDE-17333 > Forge : https://issues.jboss.org/browse/JBIDE-17334 > Webservices : https://issues.jboss.org/browse/JBIDE-17335 > Arquillian : https://issues.jboss.org/browse/JBIDE-17336 > Central : https://issues.jboss.org/browse/JBIDE-17337 > Portlet : https://issues.jboss.org/browse/JBIDE-17338 > LiveReload : https://issues.jboss.org/browse/JBIDE-17339 > > > _______________________________________________ > 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/20140523/36cf9ce8/attachment.html From rstryker at redhat.com Fri May 23 13:38:49 2014 From: rstryker at redhat.com (Rob Stryker) Date: Sat, 24 May 2014 01:38:49 +0800 Subject: [jbosstools-dev] JMX profiling agent source code needs a home Message-ID: <537F87A9.40401@redhat.com> Hey all: For those who are following the JMX additions that are occurring, we've taken JVM Monitor into our repository for beta2, and intend to continue taking pieces for beta3 that make sense. With this in mind, we currently a home for a project in FuseIDE named org.fusesource.ide.jvmmonitor.agent This project is not a plugin, but is an Agent jar to be connected to a given running virtual machine to take stats such as CPU usage, memory usage, and other profiling data. Since it's not a plugin, it's most similar to a client jar that we simply need to build or fetch. Specifically, the new plugin org.jboss.tools.jmx.jvmmonitor.core needs to somehow fetch the built jar and put it inside org.jboss.tools.jmx.jvmmonitor.core/lib, I was wondering what the process should be for this. Should it have its own repository, similar to the openshift client? Or should it still live in the jbosstools-server/jmx repository somewhere to be built as part of the tycho build? Comments for this topic can either be responded here, or added to https://issues.jboss.org/browse/JBIDE-17311 - Rob From pleacu at redhat.com Fri May 23 14:20:32 2014 From: pleacu at redhat.com (Paul Leacu) Date: Fri, 23 May 2014 14:20:32 -0400 (EDT) Subject: [jbosstools-dev] JMX profiling agent source code needs a home In-Reply-To: <537F87A9.40401@redhat.com> References: <537F87A9.40401@redhat.com> Message-ID: <825121620.6993669.1400869232764.JavaMail.zimbra@redhat.com> Hey - I supposed its a function of whether we ever expect another application to use this client api. I guess we don't want to lose it (moving it to someplace obscure) nor do we want to build it every time (it changes infrequently). So - I'd say it makes the most sense to move it up from jvmmonitor (buried too deep) and put it at the jbosstools-server/jmx/agent level. It's a JMX agent after all and could potentially be used by some other app. --paull ----- Original Message ----- > From: "Rob Stryker" > To: "jbosstools-dev jbosstools-dev" > Sent: Friday, May 23, 2014 1:38:49 PM > Subject: [jbosstools-dev] JMX profiling agent source code needs a home > > Hey all: > > For those who are following the JMX additions that are occurring, we've > taken JVM Monitor into our repository for beta2, and intend to continue > taking pieces for beta3 that make sense. > > With this in mind, we currently a home for a project in FuseIDE named > org.fusesource.ide.jvmmonitor.agent > > This project is not a plugin, but is an Agent jar to be connected to a > given running virtual machine to take stats such as CPU usage, memory > usage, and other profiling data. > > Since it's not a plugin, it's most similar to a client jar that we > simply need to build or fetch. Specifically, the new plugin > org.jboss.tools.jmx.jvmmonitor.core needs to somehow fetch the built > jar and put it inside org.jboss.tools.jmx.jvmmonitor.core/lib, > > I was wondering what the process should be for this. Should it have its > own repository, similar to the openshift client? Or should it still live > in the jbosstools-server/jmx repository somewhere to be built as part of > the tycho build? > > Comments for this topic can either be responded here, or added to > https://issues.jboss.org/browse/JBIDE-17311 > > - Rob > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > From manderse at redhat.com Sat May 24 00:02:05 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sat, 24 May 2014 00:02:05 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201405240402.s4O4252D004167@int-mx02.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-17409 https://issues.jboss.org/browse/JBIDE-17409 Summary: IE11 secured mode downloads zip instead of jar 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:06:39.426664 ---------------------------- 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 Sat May 24 07:00:48 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Sat, 24 May 2014 07:00:48 -0400 (EDT) Subject: [jbosstools-dev] JMX profiling agent source code needs a home In-Reply-To: <825121620.6993669.1400869232764.JavaMail.zimbra@redhat.com> References: <537F87A9.40401@redhat.com> <825121620.6993669.1400869232764.JavaMail.zimbra@redhat.com> Message-ID: Isnt it the other Way around. this is jvm level agent that exposes stats via jmx for the profiler to report on? It is outside/ontop of what jmx is. Jmx doesn't use it. It is jvm monitor that uses it on top/via jmx. I would say keep it and make it pretty much internal to start. Lets not make it API before we need it to be. /max (sent from my phone) > On 23/05/2014, at 20.21, Paul Leacu wrote: > > > Hey - > I supposed its a function of whether we ever expect another application > to use this client api. I guess we don't want to lose it (moving it to someplace > obscure) nor do we want to build it every time (it changes infrequently). > So - I'd say it makes the most sense to move it up from jvmmonitor (buried too deep) > and put it at the jbosstools-server/jmx/agent level. It's a JMX agent after all > and could potentially be used by some other app. > > --paull > > > > ----- Original Message ----- >> From: "Rob Stryker" >> To: "jbosstools-dev jbosstools-dev" >> Sent: Friday, May 23, 2014 1:38:49 PM >> Subject: [jbosstools-dev] JMX profiling agent source code needs a home >> >> Hey all: >> >> For those who are following the JMX additions that are occurring, we've >> taken JVM Monitor into our repository for beta2, and intend to continue >> taking pieces for beta3 that make sense. >> >> With this in mind, we currently a home for a project in FuseIDE named >> org.fusesource.ide.jvmmonitor.agent >> >> This project is not a plugin, but is an Agent jar to be connected to a >> given running virtual machine to take stats such as CPU usage, memory >> usage, and other profiling data. >> >> Since it's not a plugin, it's most similar to a client jar that we >> simply need to build or fetch. Specifically, the new plugin >> org.jboss.tools.jmx.jvmmonitor.core needs to somehow fetch the built >> jar and put it inside org.jboss.tools.jmx.jvmmonitor.core/lib, >> >> I was wondering what the process should be for this. Should it have its >> own repository, similar to the openshift client? Or should it still live >> in the jbosstools-server/jmx repository somewhere to be built as part of >> the tycho build? >> >> Comments for this topic can either be responded here, or added to >> https://issues.jboss.org/browse/JBIDE-17311 >> >> - Rob >> _______________________________________________ >> 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 nboldt at redhat.com Sun May 25 18:23:17 2014 From: nboldt at redhat.com (Nick Boldt) Date: Sun, 25 May 2014 18:23:17 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.2.0.Beta2 bits available for QE testing Message-ID: <53826D55.10701@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.Beta2-updatesite-core/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta2-updatesite-coretests/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta2-updatesite-hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta2-updatesite-webtools/ Builds: * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta2-build-core/2014-05-25_08-20-34-B111 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta2-build-coretests/2014-05-25_08-20-34-B96 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta2-build-hibernatetools/2014-05-25_08-59-45-B52 * http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.Beta2-build-webtools/2014-05-25_08-59-45-B103 JBoss Central: * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.Beta3-SNAPSHOT/ (upcoming milestone) Target Platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta2 (upcoming milestone) Until the above target platform site is released, you will need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) New + Noteworthy (subject to change): * http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstools-documentation/master/whatsnew/index.html * http://docs.jboss.org/tools/whatsnew/ Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mmurray at redhat.com Tue May 27 00:22:29 2014 From: mmurray at redhat.com (Michelle Murray) Date: Tue, 27 May 2014 00:22:29 -0400 (EDT) Subject: [jbosstools-dev] Fwd: JBDS Usage Stats In-Reply-To: <1220853760.11389289.1401164518701.JavaMail.zimbra@redhat.com> References: <1220853760.11389289.1401164518701.JavaMail.zimbra@redhat.com> Message-ID: <1892897013.11389353.1401164549978.JavaMail.zimbra@redhat.com> I'm updating the docs for Beta2. I've tried looking through the recent jiras to identify what stats are now being collected for JBDS/JBT installs. I particularly want to know what's in for JBDS 8.0.0 Beta2. Please check the screenshot and let me know if I'm missing anything or have anything wrong. The last table row is the one that I've added for JBDS 8.0.0. Thanks, Michelle -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140527/d0012400/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Usage_80B2.png Type: image/png Size: 179015 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140527/d0012400/attachment-0001.png From akazakov at exadel.com Tue May 27 13:08:10 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Tue, 27 May 2014 10:08:10 -0700 Subject: [jbosstools-dev] Fwd: JBDS Usage Stats In-Reply-To: <1892897013.11389353.1401164549978.JavaMail.zimbra@redhat.com> References: <1220853760.11389289.1401164518701.JavaMail.zimbra@redhat.com> <1892897013.11389353.1401164549978.JavaMail.zimbra@redhat.com> Message-ID: <5384C67A.807@exadel.com> 1. "Number of times JBoss Tools editors and associated tabs are used" should be "Number of times JBoss Tools *HTML/JSP* editor and associated tabs is used" 2. "Forge Tools runtime version and number of times started". I know nothing about this feature. Do you have a JIRA link? The rest of the items looks good. On 05/26/2014 09:22 PM, Michelle Murray wrote: > I'm updating the docs for Beta2. > > I've tried looking through the recent jiras to identify what stats are > now being collected for JBDS/JBT installs. > I particularly want to know what's in for JBDS 8.0.0 Beta2. > > Please check the screenshot and let me know if I'm missing anything or > have anything wrong. > The last table row is the one that I've added for JBDS 8.0.0. > > 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/20140527/1911c1f1/attachment.html From akazakov at exadel.com Tue May 27 20:44:42 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Tue, 27 May 2014 17:44:42 -0700 Subject: [jbosstools-dev] Fwd: JBDS Usage Stats In-Reply-To: <1892897013.11389353.1401164549978.JavaMail.zimbra@redhat.com> References: <1220853760.11389289.1401164518701.JavaMail.zimbra@redhat.com> <1892897013.11389353.1401164549978.JavaMail.zimbra@redhat.com> Message-ID: <5385317A.1060403@exadel.com> Also the JBoss HTML Preview view is missing in this list. So we track usage of JBoss Tools HTML/JSP editor and its tabs (visual, source, preview) and JBoss HTML Preview. This is a separate view. On 05/26/2014 09:22 PM, Michelle Murray wrote: > I'm updating the docs for Beta2. > > I've tried looking through the recent jiras to identify what stats are > now being collected for JBDS/JBT installs. > I particularly want to know what's in for JBDS 8.0.0 Beta2. > > Please check the screenshot and let me know if I'm missing anything or > have anything wrong. > The last table row is the one that I've added for JBDS 8.0.0. > > 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/20140527/79af2909/attachment.html From mmurray at redhat.com Wed May 28 03:52:47 2014 From: mmurray at redhat.com (Michelle Murray) Date: Wed, 28 May 2014 03:52:47 -0400 (EDT) Subject: [jbosstools-dev] Fwd: JBDS Usage Stats In-Reply-To: <5384C67A.807@exadel.com> References: <1220853760.11389289.1401164518701.JavaMail.zimbra@redhat.com> <1892897013.11389353.1401164549978.JavaMail.zimbra@redhat.com> <5384C67A.807@exadel.com> Message-ID: <1489170187.12282751.1401263567274.JavaMail.zimbra@redhat.com> Thanks for the feedback Alexey. I'll make those changes. About forge - I couldn't find a jira either but it's there in Window>Preferences>JBossTools>Usage Reporting, in Reported Values: Component: forge Component version: 1.3.0 Category: forge Action: start Label: Forge Runtime Version Value: major.minor.micro.identifier I'm using Build id: Beta2-v20140525-2146-B104 Can anyone point to the jira for this? Thanks, Michelle > From: "Alexey Kazakov" > To: jbosstools-dev at lists.jboss.org > Sent: Wednesday, 28 May, 2014 3:08:10 AM > Subject: Re: [jbosstools-dev] Fwd: JBDS Usage Stats > 1. "Number of times JBoss Tools editors and associated tabs are used" should > be "Number of times JBoss Tools HTML/JSP editor and associated tabs is used" > 2. "Forge Tools runtime version and number of times started". I know nothing > about this feature. Do you have a JIRA link? > The rest of the items looks good. > On 05/26/2014 09:22 PM, Michelle Murray wrote: > > I'm updating the docs for Beta2. > > > I've tried looking through the recent jiras to identify what stats are now > > being collected for JBDS/JBT installs. > > > I particularly want to know what's in for JBDS 8.0.0 Beta2. > > > Please check the screenshot and let me know if I'm missing anything or have > > anything wrong. > > > The last table row is the one that I've added for JBDS 8.0.0. > > > Thanks, > > > Michelle > > > ___________________________________________ > > > 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/20140528/5ae84c3c/attachment.html From mmurray at redhat.com Wed May 28 22:04:30 2014 From: mmurray at redhat.com (Michelle Murray) Date: Wed, 28 May 2014 22:04:30 -0400 (EDT) Subject: [jbosstools-dev] Action Required: Complete N&N for JBDS 8.0.0.Beta2 by Fri 30-May In-Reply-To: <122486416.13422134.1401329044950.JavaMail.zimbra@redhat.com> References: <122486416.13422134.1401329044950.JavaMail.zimbra@redhat.com> Message-ID: <1832240713.13422176.1401329070277.JavaMail.zimbra@redhat.com> Hello Devs, It's N&N time again! https://issues.jboss.org/browse/JBIDE-17369 Thanks to Xavier, Alexey, Snjezana, Ilya, and Brian from completing already. Still to be done: jst/jsf - Alexey hibernate - ?? webservices - Xavier aerogear - Gorkem maven - Fred gwt - ?? project examples - Fred usage analytics - Alexey forge - Koen server - Rob openshift - Andre jboss central - Fred Deadline is end of Friday 30-May. Thanks, Michelle -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140528/3f314398/attachment.html From akazakov at exadel.com Thu May 29 13:19:48 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Thu, 29 May 2014 10:19:48 -0700 Subject: [jbosstools-dev] Fwd: JBDS Usage Stats In-Reply-To: <1489170187.12282751.1401263567274.JavaMail.zimbra@redhat.com> References: <1220853760.11389289.1401164518701.JavaMail.zimbra@redhat.com> <1892897013.11389353.1401164549978.JavaMail.zimbra@redhat.com> <5384C67A.807@exadel.com> <1489170187.12282751.1401263567274.JavaMail.zimbra@redhat.com> Message-ID: <53876C34.10604@exadel.com> Koen, can you please point to the JIRA for that forge usage stuff? Does it exist? On 05/28/2014 12:52 AM, Michelle Murray wrote: > Thanks for the feedback Alexey. I'll make those changes. > > About forge - I couldn't find a jira either but it's there in > Window>Preferences>JBossTools>Usage Reporting, in Reported Values: > > *Component: *forge > > *Component version: *1.3.0 > > *Category: *forge > > *Action: *start > > *Label: *Forge Runtime Version > > *Value: *major.minor.micro.identifier > > > I'm using Build id: Beta2-v20140525-2146-B104 > > Can anyone point to the jira for this? > > Thanks, > Michelle > > > *From: *"Alexey Kazakov" > *To: *jbosstools-dev at lists.jboss.org > *Sent: *Wednesday, 28 May, 2014 3:08:10 AM > *Subject: *Re: [jbosstools-dev] Fwd: JBDS Usage Stats > > 1. "Number of times JBoss Tools editors and associated tabs are > used" should be "Number of times JBoss Tools *HTML/JSP* editor and > associated tabs is used" > 2. "Forge Tools runtime version and number of times started". I > know nothing about this feature. Do you have a JIRA link? > The rest of the items looks good. > > On 05/26/2014 09:22 PM, Michelle Murray wrote: > > I'm updating the docs for Beta2. > > I've tried looking through the recent jiras to identify what > stats are now being collected for JBDS/JBT installs. > I particularly want to know what's in for JBDS 8.0.0 Beta2. > > Please check the screenshot and let me know if I'm missing > anything or have anything wrong. > The last table row is the one that I've added for JBDS 8.0.0. > > Thanks, > Michelle > > ___________________________________________ > > 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/20140529/45c65122/attachment-0001.html From paul.verest at live.com Fri May 30 04:25:27 2014 From: paul.verest at live.com (Paul Verest) Date: Fri, 30 May 2014 08:25:27 +0000 Subject: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? In-Reply-To: <537F117F.30206@redhat.com> References: <5379CBAC.7070207@redhat.com>, , <537B2FF1.10406@redhat.com>, , <9F4C49AF-92AF-440B-9596-3310DF8C9EE7@redhat.com>, , <6E1D94D9-1BD0-4CC0-9C84-6713BDC0883A@redhat.com> , <537F117F.30206@redhat.com> Message-ID: Hello All I feel a bit uncomfortable posting to email list and not knowing how many people are reading and whether they really like reading what is a bit off-topic for JBoss dev list. With Mickael's encouragement I go on. I am actually familiar with Eclipse process, but not with details as I have not practiced it. I have signed CLA (not connected to any project), but that was to not look like a outsider/stranger, as I noticed quite often communication goes between eclipse committers that seems to know each other well, while some post from users (in some project) may be overlooked. That of course has its reason as often those bugs are not of good examples of problem reporting. => Instead of showing CLA tags that divides users into 2 categories, it would be better to have link to Eclipse profile, where it could be seen for example that the person is contributor in those project or is active on Eclipse forums etc. I was not contributing to Eclipse because - there are no company to support that time (usually there should be some business that is interested to having base support for a technology as an Eclipse project) - was mostly looking for quick solutions that would work, improve something or give value to end users => now looking for way to have some financial background for the Nodeclipse project http://www.linkedin.com/groups/Nodeclipse-project-is-looking-partners-2906459.S.5877307858806136835 > What do you want to do? > What is the question you're seeking answers for? I have been contributing to several others projects. But at some point I decided to do it only for project that are on GitHub - less overhead with other tech, like SVN on SourceForge - I noticed that the project that are more on GitHub are generally more active than on SourceForge, Google Code, Apache - GitHub is simpler and more transparent than other code repositories - I can't be master of all trades, so I need to have some limit of scope for the projects. > It may sound harsh, but I have the impression that many people just take the process as an excuse for not contributing, without having even evaluated the difficulty of adopting it or even tried it. I've sometimes heard "it's not on GitHub, I don't know how to contribute, so I don't contribute". In such case, it's also the responsibility of the developer to learn things and ask for questions in order to become a contributor. The Foundation isn't to blame. People who want to do things can do them, that's all that matters. > yes, that may be the case for some. As there can't be one step solution to address precess issue, I think some discussion can help. Also experiments like Eclipse project on GitHub may find some better approaches. There are some plugins that actually should be as Eclipse plugin, like https://github.com/eclipse-color-theme/eclipse-color-theme/ This conversation may continue in some action with https://github.com/hendrens/jdt.spelling/issues/13 Best regards, Paul Date: Fri, 23 May 2014 11:14:39 +0200 From: mistria at redhat.com To: paul.verest at live.com; manderse at redhat.com CC: angelo.zerr at gmail.com; jbosstools-dev at lists.jboss.org Subject: Re: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? On 05/23/2014 10:20 AM, Paul Verest wrote: Eclipse process adds a few steps - signing CLA [link] - setting up project on Github [link], Ecipse git [link] Most projects have an "How to contribute" or equivalent page where this is usually clearly explained. Many projects use the same development tools/workflows (Bugzilla/Gerrit/Git/Jenkins) so you only have to learn it once. If you need assistance on how to contribute, projects have open communication channels where this can be asked. I have never contributed to Eclipse project, so I don't know exact steps. What would be interesting is to first know if you tried, and if yes, where were you blocked ? In many cases, just trying is enough to accomplish something. http://www.eclipse.org/committers/ I did not really know what to search. Eclipse has a lot of resources in many places with different level of relevance. What do you want to do? What is the question you're seeking answers for? It may sound harsh, but I have the impression that many people just take the process as an excuse for not contributing, without having even evaluated the difficulty of adopting it or even tried it. I've sometimes heard "it's not on GitHub, I don't know how to contribute, so I don't contribute". In such case, it's also the responsibility of the developer to learn things and ask for questions in order to become a contributor. The Foundation isn't to blame. People who want to do things can do them, that's all that matters. Well. That was discussion between the person who knows (Max) and the person who didn't see what he had imagine (Paul). Now I know how to start and where to ask when needed. Your feedback has a lot of value. It can be used to make the process and tools easier to understand and use, which is the main way to get more people contributing. The contribution process is a forever-evolving one, because of new constraints, new ideas, new tools, new technologies... You can use this bug to suggest some improvements to this process https://bugs.eclipse.org/bugs/show_bug.cgi?id=435599 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/20140530/df074d2b/attachment.html From fbricon at redhat.com Fri May 30 09:02:08 2014 From: fbricon at redhat.com (Fred Bricon) Date: Fri, 30 May 2014 15:02:08 +0200 Subject: [jbosstools-dev] Fwd: Eclipse DemoCamp Beijing In-Reply-To: References: Message-ID: <53888150.80305@redhat.com> Relaying Paul Verest's request for some speakers for Eclipse DemoCamp Beijing on June 28th 2014. More info at https://wiki.eclipse.org/Eclipse_DemoCamps_Luna_2014/Beijing Unless you're physically in Beijing at that time, you can participate via Skype. I can't make it this year for personal reasons, but I believe many of you have some quality stuff ready to be presented, so please don't hesitate to contact Paul (paul.verest at live.com) Fred -------- Message original -------- Return-Path: paul.verest at live.com Received: from zmta03.collab.prod.int.phx2.redhat.com (LHLO zmta03.collab.prod.int.phx2.redhat.com) (10.5.81.10) by zmail17.collab.prod.int.phx2.redhat.com with LMTP; Fri, 30 May 2014 04:29:30 -0400 (EDT) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by zmta03.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP id 7860F4000A; Fri, 30 May 2014 04:29:30 -0400 (EDT) Received: from mx1.redhat.com (ext-mx11.extmail.prod.ext.phx2.redhat.com [10.5.110.16]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s4U8TUsM022830; Fri, 30 May 2014 04:29:30 -0400 Received: from SNT004-OMC2S21.hotmail.com (snt004-omc2s21.hotmail.com [65.55.90.96]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s4U8TSxm000302; Fri, 30 May 2014 04:29:29 -0400 Received: from SNT147-W67 ([65.55.90.71]) by SNT004-OMC2S21.hotmail.com with Microsoft SMTPSVC(7.5.7601.22678); Fri, 30 May 2014 01:29:28 -0700 X-TMN: [cMkqntqwlL/YnfXOniuRoOgH9z0MuThP] X-Originating-Email: [paul.verest at live.com] Message-ID: Content-Type: multipart/alternative; boundary="_12272abf-ced1-4212-a2d1-b5e6e612cd74_" From: Paul Verest To: rruss at redhat.com , fbricon at redhat.com CC: Max Rydahl Andersen Subject: Eclipse DemoCamp Beijing RE: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools? Date: Fri, 30 May 2014 08:29:28 +0000 Importance: Normal In-Reply-To: <329263792.14928663.1401438330781.JavaMail.zimbra at zmail21.collab.prod.int.phx2.redhat.com> References: ,<329263792.14928663.1401438330781.JavaMail.zimbra at zmail21.collab.prod.int.phx2.redhat.com> MIME-Version: 1.0 X-OriginalArrivalTime: 30 May 2014 08:29:28.0836 (UTC) FILETIME=[45F1B440:01CF7BE1] X-RedHat-Spam-Score: -1.908 (BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_BLOCKED) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 X-Scanned-By: MIMEDefang 2.68 on 10.5.110.16 X-Antivirus: avast! (VPS 140529-0, 29/05/2014), Inbound message X-Antivirus-Status: Clean Hello Rodney, Fred This is not urgent, but just to say Hi and invite again Red Hat to be at Eclipse DemoCamp Beijing https://wiki.eclipse.org/Eclipse_DemoCamps_Luna_2014/Beijing Best regards, Paul Verest -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140530/151b9122/attachment-0001.html