From apupier at redhat.com Mon Feb 1 13:18:31 2016 From: apupier at redhat.com (Aurelien Pupier) Date: Mon, 1 Feb 2016 19:18:31 +0100 Subject: [jbosstools-dev] Eclipse plugins testing structure In-Reply-To: <668BD024-6140-4CAC-8CB5-C28F3DAEB8A5@redhat.com> References: <56A88DD9.9030802@redhat.com> <668BD024-6140-4CAC-8CB5-C28F3DAEB8A5@redhat.com> Message-ID: <56AFA177.3040500@redhat.com> Hi, comments inlined. Le 1/27/2016 1:26 PM, Max Rydahl Andersen a ?crit : > > On 27 Jan 2016, at 10:28, Aurelien Pupier wrote: > > Hi, > > I'm currently trying to improve test structure for Jboss Fuse Tooling > project (https://github.com/fusesource/fuseide). > > On Max recommendation, I take a look at jbosstools-devdoc > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_add_a_test_plugin_or_feature.adoc > > When i take a look to > https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.jboss.tools.as.test.core/pom.xml > . This project is in tests folder but it launches > tycho-surefire-plugin. > As far as I understand Tycho, it means that it is launching an OSGi > platform. From my point of view, it means that these tests are already > integration tests and the only difference between tests and itests > currently is more fast vs slow tests. > > I disagree launching in osgi means it is an integration test. > > You can run fast tests with tyco-surefire-plugin or rater from eclipse > - just don't launch with the workbench.If you run with the plain maven > surefire plugin you will have to handle dependency management on your > own afaics - > > i.e. you cannot depend on anything in the osgi or in p2 repos for that > matter. > > Meaning any work done for Target platform will have to be done twice - > one for existing target platform, another > for your pure maven setup. > I don't really have to handle these dependencies as we should mock them. On the other side, I was using the same mechanism on another open source project and we didn't have a lot of trouble with dependencies. I'm not sure how Tycho/Maven was handling it. > What I wanted to achieve is to have really fast unit test, so I > created > a fragment and so use maven-surefire-plugin. You can see the fragment > https://github.com/fusesource/fuseide/tree/master/editor/tests/org.fusesource.ide.camel.editor.tests > > so this will have to not rely on /any/ eclipse osgi dependent api's. > > That is doable, but super limited. As long as you are aware of that > and the need to maintain two "target platforms" > that is fine. > > Need to find a different name than test or itest then though ;) > Maybe we can discuss to have a third category effectively (and perhaps even a fourth with UI tests, but this is another story ^^) > Does it really make that big difference wether you use tyco-surefire > vs plain maven-surefire speed wise ? (remember to not start the > workbench ;) > Do you mean to launch in "Headless mode"? At comparison, from Eclipse to launch the same test: - using fragments: < 100ms - using Headless mode: 16s - using ui.ide application: 30s > /max > http://about.me/maxandersen > Regards, -- Aurelien Pupier Senior Software Engineer in JBoss Fuse Tooling Team @apupier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160201/d8a8ffb9/attachment-0001.html From apupier at redhat.com Mon Feb 1 13:25:13 2016 From: apupier at redhat.com (Aurelien Pupier) Date: Mon, 1 Feb 2016 19:25:13 +0100 Subject: [jbosstools-dev] Eclipse plugins testing structure In-Reply-To: <56A8A1BD.6050908@redhat.com> References: <56A88DD9.9030802@redhat.com> <56A89139.2040308@redhat.com> <56A898F3.9070408@redhat.com> <56A8A1BD.6050908@redhat.com> Message-ID: <56AFA309.7000102@redhat.com> Hi, comments inlined Le 1/27/2016 11:53 AM, Mickael Istria a ?crit : > On 01/27/2016 11:16 AM, Aurelien Pupier wrote: >> About using fragments, the only drawback I'm aware of is that one >> cannot add a dependency to a fragment from their plugin. So it's not >> possible for other tests to reuse some logic that is inside a >> fragment. In the spirit of "treating tests as 1st class citizen", I >> believe it's generally better to allow composition of test bundles >> and to make them regular bundles. >> >> If reusable, the logic can be moved to a dedicated utility test plugin. > Yes, but it requires an effort in moving the code to the right plugin > or turning fragment into a bundle everytime one identifies something > to reuse; whereas using bundles only doesn't require any effort from > the "producer" side. Considering this code as first citizen, it seems to me an acceptable effort ;-) > >> On the other hand, some integration tests should be able to detect that. > That would require writing some additional integration tests, whereas > the current approach to run "unit" tests inside a workbench provide > that verification without additional thing to write. > >>> The QE people could tell you their opinion on what's more important >>> between fast tests, and longer tests that are closer from production. >>> I guess it all depends, as always: we could imagine the unit test >>> running in plain Java to verify only their logic, but it shouldn't >>> become a replacement to some integration test to verify that the >>> logic also works in the right context. >> Not planned to have them as a replacement. I already created the >> structure to write also higher integration tests. > If, during automated tests/build, you run both unit tests and then > start a workbench to run integration tests, then you pay the price of > the workbench startup anyway. So why not running those unit tests in > the workbench? Because my issue is not the build. It is my development environment. > >> When running locally, I may want to run only unit tests first. >> Without launching the OSGi platform it will be faster. It will also >> allow to use some tools such as Infinitest to have continuous >> feedback while developing. > I don't know much of Infinitest, but I believe it doesn't rely on how > Maven runs tests. Eclipse already provide the ability to run a test > class in a bundle in plain Java without starting the workbench; it's > "Run As > JUnit Test" instead of "Run As > JUnit Plugin Test". I guess > Infinitest can rely on that, can't it? Yes Infinitest can rely on it but it means that you are able to launch as "JUnit test" and so not starting the workbench. > > Just to be clear, I'm not saying it's wrong to change that; I'm more > wonderint how much profitable is it, what changing test structure > would provide better than the current one does. The Infinitest story > seems the only one "worth it" IMO, and it doesn't seem to be > correlated to tycho-surefire vs maven-surefire. InfiniTest or only launching test of a single plugin very fast (less than a second versus tens seconds) it is the difference between keeping concentrated on the task and have our brain switching to another idea. It seems to me that only tests launched with surefire will be able and ensured - to run with Junit test. > -- > 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 -- Aurelien Pupier Senior Software Engineer in JBoss Fuse Tooling Team @apupier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160201/b3448c13/attachment.html From mistria at redhat.com Mon Feb 1 13:43:13 2016 From: mistria at redhat.com (Mickael Istria) Date: Mon, 1 Feb 2016 19:43:13 +0100 Subject: [jbosstools-dev] Eclipse plugins testing structure In-Reply-To: <56AFA309.7000102@redhat.com> References: <56A88DD9.9030802@redhat.com> <56A89139.2040308@redhat.com> <56A898F3.9070408@redhat.com> <56A8A1BD.6050908@redhat.com> <56AFA309.7000102@redhat.com> Message-ID: <56AFA741.5060807@redhat.com> On 02/01/2016 07:25 PM, Aurelien Pupier wrote: > Le 1/27/2016 11:53 AM, Mickael Istria a ?crit : >> Yes, but it requires an effort in moving the code to the right plugin >> or turning fragment into a bundle everytime one identifies something >> to reuse; whereas using bundles only doesn't require any effort from >> the "producer" side. > Considering this code as first citizen, it seems to me an acceptable > effort ;-) Do you put your actual "first citizen" business code into fragments too? >>> When running locally, I may want to run only unit tests first. >>> Without launching the OSGi platform it will be faster. It will also >>> allow to use some tools such as Infinitest to have continuous >>> feedback while developing. >> I don't know much of Infinitest, but I believe it doesn't rely on how >> Maven runs tests. Eclipse already provide the ability to run a test >> class in a bundle in plain Java without starting the workbench; it's >> "Run As > JUnit Test" instead of "Run As > JUnit Plugin Test". I >> guess Infinitest can rely on that, can't it? > Yes Infinitest can rely on it but it means that you are able to launch > as "JUnit test" and so not starting the workbench. Yes, and if you're able to do it from the Eclipse IDE for your test class, isn't it enough? So in your IDE, you can run "unit tests" without the workbench/Platform actually started, just the API available; and with Maven and tycho-surefire-plugin, you get a Platform/workbench started, like it will happen in real-life, to find real issues that wouldn't happen in plain Java environment. >> Just to be clear, I'm not saying it's wrong to change that; I'm more >> wonderint how much profitable is it, what changing test structure >> would provide better than the current one does. The Infinitest story >> seems the only one "worth it" IMO, and it doesn't seem to be >> correlated to tycho-surefire vs maven-surefire. > InfiniTest or only launching test of a single plugin very fast (less > than a second versus tens seconds) it is the difference between > keeping concentrated on the task and have our brain switching to > another idea. > It seems to me that only tests launched with surefire will be able and > ensured - to run with Junit test. I believe this sentence illustrates our divergence: you mainly think about tests as a tool for the developer, and they have to be fast for the developer to use them. That's right. I see them as an armor for the application, I want them to find as many bugs possible in the actual environment where the code will actually run, and if it has a cost for the developer, so be it, as long as tests are still run and checked by continuous integration. That's right too. Overall, both are right and useful. Depending on the test, you might want one or the other. What's possible and that seems like the best thing to me is to have the unit-tests in a bundle that run fast with maven-surefire-plugin, and have integration tests in another bundle also running the unit-test suite (+ some other tests) with tycho-surefire-plugin. So you get the best of both: unit tests are run fast and keep running fast because they are automatically tested using plain JUnit and maven-surefire-plugin; and you also have them running as part of the integration tests to also detect bugs that depend on the Eclipse runtime mechanism. WDYT? -- 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/20160201/170fb0af/attachment.html From pleacu at redhat.com Mon Feb 1 14:46:09 2016 From: pleacu at redhat.com (Paul Leacu) Date: Mon, 1 Feb 2016 14:46:09 -0500 (EST) Subject: [jbosstools-dev] JBDSIS 8.0.5.GA/ JBTIS 4.2.5.Final now live In-Reply-To: <1559328918.15180328.1454342311419.JavaMail.zimbra@redhat.com> Message-ID: <912214289.15274899.1454355969547.JavaMail.zimbra@redhat.com> Greetings, The latest Eclipse-Luna capable, JBDS 8.1.0.GA compatible Integration Stack GA tooling is released. Highlights include bugfix releases of BPMN2 Modeler, drools, SwitchYard and Teiid Designer. JBDSIS 8.0.5.GA, JBTIS 4.2.5.Final This release contains the following: BPEL 1.3.100.Final > BPMN2 1.1.4.Final_1.1.0.Final_luna > DROOLS/JBPM6 6.3.1.Final ESB 1.5.530.Final FUSE TOOLING 7.3.2.FINAL (w/ Fuse Transformation Tooling) JBPM3 4.5.200.Final MODESHAPE 3.7.0.Final > SWITCHYARD 2.0.2.Final > TEIID DESIGNER 9.0.5.Final The latest SAP tooling (7.3.2.FINAL) is also available through the Fuse import update wizard and a separate update site. Release Notes: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Studio_Integration_Stack/8.0/html/8.0.5_Release_Notes/ (pending) Installation Instructions: 1. If installing from Eclipse Luna: Help > Eclipse Marketplace... - in the 'Search' tab enter 'jbds' in the 'Find' input widget - select the 'Go' button - install 'Red Hat JBoss Developer Studio 8.1.0.GA' 2. Start jbdevstudio or eclipse (with jbds from step 1) 3. Select the Software/Update tab in the JBoss Central view. done! The standard Eclipse installer is available for JBDSIS: 1. If installing from Eclipse Luna: Help > Eclipse Marketplace... - in the 'Search' tab enter 'jbds' in the 'Find' input widget - select the 'Go' button - install 'Red Hat JBoss Developer Studio 8.1.0.GA' 2. Start jbdevstudio or eclipse-with-jbds from step 1, then: Help > Install New Software... Add... - use this for 'Location:' for the production integration stack: https://devstudio.redhat.com/updates/8.0/integration-stack/ JBoss Central is supported for JBTIS: 1 Install JBoss Tools 4.2.3.Final: Help > Eclipse Marketplace... - in the 'Search' tab enter 'jboss tools' in the 'Find' input widget - select the 'Go' button - install 'JBoss Tools 4.2.3.Final' 2 Start your Eclipse: ./eclipse 3. Select the Software/Update tab in the JBoss Central view. The standard Eclipse installer is available for JBTIS: * Start eclipse-with-jboss-tools, then: Help > Install New Software... Add... - use this for 'Location:' for the released-components integration stack: http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/ Eclipse MarketPlace: https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-integration-stack-luna Offline zip files are supported for both production and community installs: 1. https://devstudio.redhat.com/updates/8.0.0/jbdevstudio-integration-stack-updatesite-8.0.5.GA.zip (MD5) 2. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.5.Final.zip (MD5) For component and QE test developers - the JBTIS target platforms are: - Full and candidate release target platforms including early access dependencies: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.9.Final/ http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.9.Final/ Give it a try! --paull From alkazako at redhat.com Tue Feb 2 12:25:56 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Tue, 2 Feb 2016 12:25:56 -0500 Subject: [jbosstools-dev] JBoss Developer Studio 9.1.0.Beta2 is available Message-ID: <56B0E6A4.9020403@redhat.com> JBoss Developer Studio 9.1.0.Beta2 is available! Download page: https://www.jboss.org/products/devstudio/overview/ Update site: https://devstudio.redhat.com/9.0/development/updates/ Blog Announcement: http://tools.jboss.org/blog/beta2-for-mars2.html New + Noteworthy: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta2.html -- Schedule / Upcoming Releases: https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page From alkazako at redhat.com Tue Feb 2 12:31:08 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Tue, 2 Feb 2016 12:31:08 -0500 Subject: [jbosstools-dev] JBoss Tools 4.3.1.Beta2 is now available Message-ID: <56B0E7DC.6080507@redhat.com> This is a development release aimed at Eclipse Mars.2 users. Announcement Blog: http://tools.jboss.org/blog/beta2-for-mars2.html Update Site: http://download.jboss.org/jbosstools/mars/development/updates/ Zips: http://tools.jboss.org/downloads/jbosstools/mars/4.3.1.Beta2.html#zips Installation instructions: http://tools.jboss.org/downloads/installation.html New + Noteworthy (subject to change): http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta2.html Schedule / Upcoming Releases: https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page From nickboldt at gmail.com Thu Feb 4 13:38:59 2016 From: nickboldt at gmail.com (Nick Boldt) Date: Thu, 4 Feb 2016 13:38:59 -0500 Subject: [jbosstools-dev] Fwd: [eclipse.org-members-committers] Eclipse Community Awards - Vote by Feb. 8 In-Reply-To: <56B3751F.10705@eclipse.org> References: <56B3751F.10705@eclipse.org> Message-ID: Some projects and people included in this year's Eclipse Community Awards: * Mickael Istria, * Pascal Rapicault, * CDT Launchbar, * EGit, * and lots more! It's only 6 questions, so vote early, vote often! :D ---------- Forwarded message ---------- From: Roxanne Joncas Date: Thu, Feb 4, 2016 at 10:58 AM Subject: [eclipse.org-members-committers] Eclipse Community Awards - Vote by Feb. 8 To: eclipse.org-members-committers at eclipse.org, eclipse.org-member-marketing at eclipse.org Dear members/committers, Remember to vote for deserving projects and individuals for the Eclipse Community Awards! Vote here: https://www.surveymonkey.com/r/eclipseawards2016 The deadline to vote is February 8 at 5 PM ET. Regards, Roxanne -- ___________________________ Roxanne Joncas Eclipse Foundation 613-224-9461 x241 _______________________________________________ eclipse.org-members-committers mailing list eclipse.org-members-committers at eclipse.org https://dev.eclipse.org/mailman/listinfo/eclipse.org-members-committers NOTICE: This mailing list is an aggregate of the following mailing lists: eclipse.org-membership-at-large,eclipse.org-committers, eclipse.org-project-leadership, eclipse.org-member-marketing. The purpose of this list is to reduce the number of duplicate e-mails individuals will receive from these lists. To be removed, please remove yourself from one of the primary mailing list or contact emo at eclipse.org to request removal. -- Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc. http://nick.divbyzero.com From manderse at redhat.com Sun Feb 7 17:36:54 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Sun, 07 Feb 2016 23:36:54 +0100 Subject: [jbosstools-dev] ERT created In-Reply-To: <0C5A5775-EA3D-4642-A6E9-867369364CE1@redhat.com> References: <0C5A5775-EA3D-4642-A6E9-867369364CE1@redhat.com> Message-ID: ERT is now running every hour or so. I wrote up some basic docs on how it works at https://github.com/jbosstools/jbosstools-devdoc/blob/master/issues/how_to_use_jira.adoc#eclipse-release-train-jira One thing to remember: do *NOT* change the title of the jira - it is needed to look up which jira corresponds to which bugzilla. You can add comments and whatnot, but if any of the default data is incorrect open a bug against bzira in releng in Jira rather than manually fix it. Gorkem - this also has info on how to force a rerun for use during standups/prioritization calls. /max > Hi, > > Just wanted to let you know https://issues.jboss.org/projects/ERT is > now > live. > > This is the jira we have an semi-experimental mirroring of > bugs.eclipse.org issues > to use in sprint planning. > > See https://issues.jboss.org/projects/ERT/summary/statistics for > overview. > > I'll do a write up tomorrow on what it means/entails - but just a > headsup in case > you start getting mail notifications about it ;) > > /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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160207/bcfcbde8/attachment.html From nboldt at redhat.com Mon Feb 8 02:56:58 2016 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 8 Feb 2016 02:56:58 -0500 Subject: [jbosstools-dev] ERT created In-Reply-To: References: <0C5A5775-EA3D-4642-A6E9-867369364CE1@redhat.com> Message-ID: Woo, thanks for contributing to jbosstools-devdoc! As a reminder, if anyone else ever wants to help document processes, add links to where to find stuff [1], feel free to submit a PR against the repo [2]. If you're not sure what to write but feel something's definitely missing, please feel free to open a JBIDE JIRA and assign it to me. [1] https://github.com/jbosstools/jbosstools-devdoc/blob/master/list_of_projects.adoc [2] https://github.com/jbosstools/jbosstools-devdoc/ Cheers, Nick On Sun, Feb 7, 2016 at 5:36 PM, Max Rydahl Andersen wrote: > ERT is now running every hour or so. > > I wrote up some basic docs on how it works at > https://github.com/jbosstools/jbosstools-devdoc/blob/master/issues/how_to_use_jira.adoc#eclipse-release-train-jira > > One thing to remember: do NOT change the title of the jira - it is needed to > look up which jira corresponds to which bugzilla. You can add comments and > whatnot, but if any of the default data is incorrect open a bug against > bzira in releng in Jira rather than manually fix it. > > Gorkem - this also has info on how to force a rerun for use during > standups/prioritization calls. > > /max > > Hi, > > Just wanted to let you know https://issues.jboss.org/projects/ERT is now > live. > > This is the jira we have an semi-experimental mirroring of > bugs.eclipse.org issues > to use in sprint planning. > > See https://issues.jboss.org/projects/ERT/summary/statistics for > overview. > > I'll do a write up tomorrow on what it means/entails - but just a > headsup in case > you start getting mail notifications about it ;) > > /max > http://about.me/maxandersen > > ________________________________ > > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > /max > http://about.me/maxandersen > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mlabuda at redhat.com Tue Feb 9 03:38:34 2016 From: mlabuda at redhat.com (Marian Labuda) Date: Tue, 9 Feb 2016 03:38:34 -0500 (EST) Subject: [jbosstools-dev] Recording of docker, CDK, openshift demo at DevConf in Brno In-Reply-To: <1580311748.26817582.1455007027086.JavaMail.zimbra@redhat.com> Message-ID: <1874828974.26817851.1455007114432.JavaMail.zimbra@redhat.com> Hi, there is a recording from Friday's demo at DevConf in Brno where me and Martin Malina were having presentation on topic docker, CDK and OpenShift: https://www.youtube.com/watch?v=c8ILqI-B54E Marian Labuda JBoss JBDS QE From manderse at redhat.com Mon Feb 15 02:59:04 2016 From: manderse at redhat.com (manderse at redhat.com) Date: Mon, 15 Feb 2016 02:59:04 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201602150759.u1F7x4DT023561@int-mx11.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3595 https://issues.jboss.org/browse/JBDS-3595 Summary: dark theme not nice Assignee: None set. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 15:06:15.625891 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27 From max.andersen at gmail.com Mon Feb 15 18:47:21 2016 From: max.andersen at gmail.com (Max Rydahl Andersen) Date: Tue, 16 Feb 2016 00:47:21 +0100 Subject: [jbosstools-dev] Aeri integration - put in usage or separate plugin ? Message-ID: <03E759CD-B4E7-48AB-9CB4-6207C27AA833@gmail.com> Hey, I'm working on the inclusion of Aeri into JBoss Tools. Initial PR is at https://github.com/jbosstools/jbosstools-base/pull/483 I would like to include this into JBoss Tools 4.3 CR1 (the one using Mars.2). I see two options: A) add separate plugin (that is what separate PR does now) and users will have to manually add it, unless we add it to every overall feature like we have done for usage. B) add this extension point + dependency on aeri plugin into our usage plugin. With B we get the biggest exposure by far - but we will add a base dependency to Aeri for *every* plugin we have. Suggestions welcome on how we can make Aeri available to most people with the smallest impact :) /max http://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160216/7f8c15d0/attachment.html From alkazako at redhat.com Mon Feb 15 19:04:22 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Mon, 15 Feb 2016 19:04:22 -0500 Subject: [jbosstools-dev] Aeri integration - put in usage or separate plugin ? In-Reply-To: <03E759CD-B4E7-48AB-9CB4-6207C27AA833@gmail.com> References: <03E759CD-B4E7-48AB-9CB4-6207C27AA833@gmail.com> Message-ID: <56C26786.1000104@redhat.com> If choosing from A) and B) I would go for B) and add a dependency (hard one or or greedy optional?) to the Usage. On 02/15/2016 06:47 PM, Max Rydahl Andersen wrote: > > Hey, > > I'm working on the inclusion of Aeri into JBoss Tools. > > Initial PR is at https://github.com/jbosstools/jbosstools-base/pull/483 > > I would like to include this into JBoss Tools 4.3 CR1 (the one using > Mars.2). > > I see two options: > > A) add separate plugin (that is what separate PR does now) and users > will have > to manually add it, unless we add it to every overall feature like we > have done for usage. > > B) add this extension point + dependency on aeri plugin into our usage > plugin. > > With B we get the biggest exposure by far - but we will add a base > dependency to Aeri for /every/ plugin we have. > > Suggestions welcome on how we can make Aeri available to most people > with the smallest impact :) > > /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/20160215/b6e86b50/attachment-0001.html From ggastald at redhat.com Mon Feb 15 19:17:51 2016 From: ggastald at redhat.com (George Gastaldi) Date: Mon, 15 Feb 2016 22:17:51 -0200 Subject: [jbosstools-dev] Aeri integration - put in usage or separate plugin ? In-Reply-To: <56C26786.1000104@redhat.com> References: <03E759CD-B4E7-48AB-9CB4-6207C27AA833@gmail.com> <56C26786.1000104@redhat.com> Message-ID: Sorry for my ignorance, but what is Aeri? Are there any docs explaining it? Em 15/02/2016 22:04, "Alexey Kazakov" escreveu: > If choosing from A) and B) I would go for B) and add a dependency (hard > one or or greedy optional?) to the Usage. > > > On 02/15/2016 06:47 PM, Max Rydahl Andersen wrote: > > Hey, > > I'm working on the inclusion of Aeri into JBoss Tools. > > Initial PR is at https://github.com/jbosstools/jbosstools-base/pull/483 > > I would like to include this into JBoss Tools 4.3 CR1 (the one using > Mars.2). > > I see two options: > > A) add separate plugin (that is what separate PR does now) and users will > have > to manually add it, unless we add it to every overall feature like we have > done for usage. > > B) add this extension point + dependency on aeri plugin into our usage > plugin. > > With B we get the biggest exposure by far - but we will add a base > dependency to Aeri for *every* plugin we have. > > Suggestions welcome on how we can make Aeri available to most people with > the smallest impact :) > > /max > http://about.me/maxandersen > > > _______________________________________________ > jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://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/20160215/be9ccfed/attachment.html From manderse at redhat.com Tue Feb 16 01:43:34 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 16 Feb 2016 01:43:34 -0500 (EST) Subject: [jbosstools-dev] Aeri integration - put in usage or separate plugin ? In-Reply-To: References: <03E759CD-B4E7-48AB-9CB4-6207C27AA833@gmail.com> <56C26786.1000104@redhat.com> Message-ID: It is eclipse error reporting. Noticed that little pop up asking to submit errors to eclipse.org ? We've made it so we can hook in our our backend to receive reports related to all JBoss plugins incl. forge. /max http://about.me/maxandersen > On 16 Feb 2016, at 01:19, George Gastaldi wrote: > > Sorry for my ignorance, but what is Aeri? Are there any docs explaining it? > > Em 15/02/2016 22:04, "Alexey Kazakov" escreveu: >> If choosing from A) and B) I would go for B) and add a dependency (hard one or or greedy optional?) to the Usage. >> >> >>> On 02/15/2016 06:47 PM, Max Rydahl Andersen wrote: >>> Hey, >>> >>> I'm working on the inclusion of Aeri into JBoss Tools. >>> >>> Initial PR is at https://github.com/jbosstools/jbosstools-base/pull/483 >>> >>> I would like to include this into JBoss Tools 4.3 CR1 (the one using Mars.2). >>> >>> I see two options: >>> >>> A) add separate plugin (that is what separate PR does now) and users will have >>> to manually add it, unless we add it to every overall feature like we have done for usage. >>> >>> B) add this extension point + dependency on aeri plugin into our usage plugin. >>> >>> With B we get the biggest exposure by far - but we will add a base dependency to Aeri for every plugin we have. >>> >>> Suggestions welcome on how we can make Aeri available to most people with the smallest impact :) >>> >>> /max >>> http://about.me/maxandersen >>> >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > _______________________________________________ > 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/20160216/f99032cc/attachment.html From manderse at redhat.com Wed Feb 17 02:59:07 2016 From: manderse at redhat.com (manderse at redhat.com) Date: Wed, 17 Feb 2016 02:59:07 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201602170759.u1H7x7L7015058@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 JBDS-3596 https://issues.jboss.org/browse/JBDS-3596 Summary: Many update sites are added if we try to create a new server Assignee: None set. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 20:26:53.806050 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27 From nboldt at redhat.com Thu Feb 18 14:07:01 2016 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 18 Feb 2016 14:07:01 -0500 Subject: [jbosstools-dev] Fwd: Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: Message-ID: *Note that the PR may be incomplete (will check for newer stuff than is in Mars, m2e, m2e-atp, and WTP later) but I'm sending this out in advance so people are aware of the forthcoming changes.* -- Here is a proposal for a change to the JBoss Tools and Red Hat JBoss Developer Studio 4.52.0.CR1-SNAPSHOT target platforms (for JBT 4.3.1.CR1 / JBDS 9.1.0.CR1). * https://github.com/jbosstools/jbosstools-target-platforms/pull/195 * https://github.com/jbosstools/jbosstools-discovery/pull/327 It consists of the following changes: * https://issues.jboss.org/browse/JBIDE-21651 : update to latest Mars.2.RC4 : update to WTP : update to m2e 1.6.3 : update to m2e-apt 1.2 : update to Docker 1.2.1.201602162146 : addition of org.apache.commons.io 2.2.0 (already had 2.0.1, but now need 2.2.0 too to resolve Aeri deps) p2diff reports will be attached to the above JIRA --- Please review the above PR(s), as they will be applied as soon as possible in preparation for CR1 code freeze. You can use the following to build & test the target-platform locally against your component(s). Build target-platform: $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple $ git fetch origin pull/195/head && git checkout FETCH_HEAD $ mvn clean install Then, to test the new "multiple" target platform against your component's build: $ cd /path/to/your/jbosstools-component $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT -Dtpc.targetKind=multiple -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Thu Feb 18 14:41:07 2016 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 18 Feb 2016 14:41:07 -0500 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.CR1-SNAPSHOT and 4.50.2.CR1-SNAPSHOT: Mars.2.RC4 + AERI, Docker, Easymport, m2e, m2e-apt Message-ID: Another PR. This one updates the 4.50.x TP to the latest versions noted below: PR to update 4.50.x TP too: https://github.com/jbosstools/jbosstools-target-platforms/pull/196 Changes: commons.io 2.2 m2e.apt 1.2 m2e 1.6.3 aeri 1.0.0.v20150617-0732 -> 1.100.0.v20160217-0435 launchbar 1.0.1 e4.ui.importer 0.2 docker tools 1.2.1 RC4 (Also fixed the subject heading of this email.) On Thu, Feb 18, 2016 at 2:07 PM, Nick Boldt wrote: > *Note that the PR may be incomplete (will check for newer stuff than > is in Mars, m2e, m2e-atp, and WTP later) but I'm sending this out in > advance so people are aware of the forthcoming changes.* > > -- > > Here is a proposal for a change to the JBoss Tools and Red Hat JBoss > Developer Studio 4.52.0.CR1-SNAPSHOT target platforms (for JBT > 4.3.1.CR1 / JBDS 9.1.0.CR1). > > * https://github.com/jbosstools/jbosstools-target-platforms/pull/195 > * https://github.com/jbosstools/jbosstools-discovery/pull/327 > > It consists of the following changes: > > * https://issues.jboss.org/browse/JBIDE-21651 > > : update to latest Mars.2.RC4 > : update to WTP > : update to m2e 1.6.3 > : update to m2e-apt 1.2 > : update to Docker 1.2.1.201602162146 > : addition of org.apache.commons.io 2.2.0 (already had 2.0.1, but now > need 2.2.0 too to resolve Aeri deps) > > p2diff reports will be attached to the above JIRA > > --- > > Please review the above PR(s), as they will be applied as soon as possible in > preparation for CR1 code freeze. > > You can use the following to build & test the > target-platform locally against your component(s). > > Build target-platform: > $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple > $ git fetch origin pull/195/head && git checkout FETCH_HEAD > $ mvn clean install > > Then, to test the new "multiple" target platform against your component's build: > $ cd /path/to/your/jbosstools-component > $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT > -Dtpc.targetKind=multiple > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Thu Feb 18 17:16:32 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 18 Feb 2016 23:16:32 +0100 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.CR1-SNAPSHOT and 4.50.2.CR1-SNAPSHOT: Mars.2.RC4 + AERI, Docker, Easymport, m2e, m2e-apt In-Reply-To: References: Message-ID: <23663BF2-364E-4D37-A433-09E8AE0B1C1A@redhat.com> On 18 Feb 2016, at 20:41, Nick Boldt wrote: > Another PR. This one updates the 4.50.x TP to the latest versions > noted below: > > PR to update 4.50.x TP too: > https://github.com/jbosstools/jbosstools-target-platforms/pull/196 > > Changes: > > commons.io 2.2 > m2e.apt 1.2 > m2e 1.6.3 > aeri 1.0.0.v20150617-0732 -> 1.100.0.v20160217-0435 > launchbar 1.0.1 > e4.ui.importer 0.2 > docker tools 1.2.1 RC4 I assume this relates to https://github.com/jbosstools/jbosstools-target-platforms/pull/195 too ? +1 to get this into Mars asap so we can get the Aeri stuff tested asap. Right now it can only run on my machine which is sad :) /max > (Also fixed the subject heading of this email.) > > On Thu, Feb 18, 2016 at 2:07 PM, Nick Boldt wrote: >> *Note that the PR may be incomplete (will check for newer stuff than >> is in Mars, m2e, m2e-atp, and WTP later) but I'm sending this out in >> advance so people are aware of the forthcoming changes.* >> >> -- >> >> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss >> Developer Studio 4.52.0.CR1-SNAPSHOT target platforms (for JBT >> 4.3.1.CR1 / JBDS 9.1.0.CR1). >> >> * https://github.com/jbosstools/jbosstools-target-platforms/pull/195 >> * https://github.com/jbosstools/jbosstools-discovery/pull/327 >> >> It consists of the following changes: >> >> * https://issues.jboss.org/browse/JBIDE-21651 >> >> : update to latest Mars.2.RC4 >> : update to WTP >> : update to m2e 1.6.3 >> : update to m2e-apt 1.2 >> : update to Docker 1.2.1.201602162146 >> : addition of org.apache.commons.io 2.2.0 (already had 2.0.1, but now >> need 2.2.0 too to resolve Aeri deps) >> >> p2diff reports will be attached to the above JIRA >> >> --- >> >> Please review the above PR(s), as they will be applied as soon as >> possible in >> preparation for CR1 code freeze. >> >> You can use the following to build & test the >> target-platform locally against your component(s). >> >> Build target-platform: >> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >> $ git fetch origin pull/195/head && git checkout FETCH_HEAD >> $ mvn clean install >> >> Then, to test the new "multiple" target platform against your >> component's build: >> $ cd /path/to/your/jbosstools-component >> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >> -Dtpc.targetKind=multiple >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > 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/20160218/0cd5c7b7/attachment-0001.html From manderse at redhat.com Thu Feb 18 17:47:59 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 18 Feb 2016 23:47:59 +0100 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: Message-ID: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> On 18 Feb 2016, at 20:07, Nick Boldt wrote: > Build target-platform: > $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple > $ git fetch origin pull/195/head && git checkout FETCH\_HEAD > $ mvn clean install I tried this and I got: [INFO] [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ jbdevstudio-unified --- [INFO] [INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform (default) @ jbdevstudio-unified --- [INFO] Validating /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... [INFO] Adding repository https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO [INFO] Failed, see Error log below [ERROR] Validation found errors in 1 .target files: Could not resolve content of jbdevstudio-unified.target Known issue ? so in short, i'm all for getting the changes in but I cannot build any of the suggested PR's so I can't verify them. :/ /max > > Then, to test the new "multiple" target platform against your > component's build: > $ cd /path/to/your/jbosstools-component > $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT > -Dtpc.targetKind=multiple /max http://about.me/maxandersen From gorkem.ercan at gmail.com Thu Feb 18 21:10:51 2016 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Thu, 18 Feb 2016 21:10:51 -0500 Subject: [jbosstools-dev] PR templates Message-ID: New feature from GitHub https://github.com/blog/2111-issue-and-pull-request-templates Since we don't do issues on GitHub, we can ignore that. But providing PR templates sounds like a good idea. Should we open a Jira(s) to follow up? What should the templates look like? Thoughts? ? Gorkem From manderse at redhat.com Fri Feb 19 00:24:13 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 19 Feb 2016 00:24:13 -0500 (EST) Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: Adding back the list. > I suspect you were in the wrong folder. When I build it, I only build > the multiple/pom.xml, not the unified one. Gotcha. My bad. I missed the cd. Been too long since I build the tp locally. Can you Remind me what is needed to build the full TP for these PRs ? i thought once once could build these with a mvn verify. /max > > N > > On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen > wrote: >> On 18 Feb 2016, at 20:07, Nick Boldt wrote: >> >>> Build target-platform: >>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >>> $ git fetch origin pull/195/head && git checkout FETCH\_HEAD >>> $ mvn clean install >> >> >> I tried this and I got: >> >> [INFO] >> [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) >> @ jbdevstudio-unified --- >> [INFO] >> [INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform >> (default) @ jbdevstudio-unified --- >> [INFO] Validating >> /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... >> [INFO] Adding repository >> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO >> [INFO] Failed, see Error log below >> [ERROR] Validation found errors in 1 .target files: >> Could not resolve content of jbdevstudio-unified.target >> >> >> Known issue ? >> >> so in short, i'm all for getting the changes in but I cannot build any of >> the suggested PR's >> so I can't verify them. :/ >> >> /max >> >>> >>> Then, to test the new "multiple" target platform against your component's >>> build: >>> $ cd /path/to/your/jbosstools-component >>> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >>> -Dtpc.targetKind=multiple >> >> >> >> /max >> http://about.me/maxandersen > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com From nboldt at redhat.com Fri Feb 19 00:24:26 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Feb 2016 00:24:26 -0500 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.CR1-SNAPSHOT and 4.50.2.CR1-SNAPSHOT: Mars.2.RC4 + AERI, Docker, Easymport, m2e, m2e-apt In-Reply-To: <23663BF2-364E-4D37-A433-09E8AE0B1C1A@redhat.com> References: <23663BF2-364E-4D37-A433-09E8AE0B1C1A@redhat.com> Message-ID: PRs 195 and 196 (plus 327) have been merged and built. See details in JIRA: https://issues.jboss.org/browse/JBIDE-21651 On Thu, Feb 18, 2016 at 5:16 PM, Max Rydahl Andersen wrote: > On 18 Feb 2016, at 20:41, Nick Boldt wrote: > > Another PR. This one updates the 4.50.x TP to the latest versions noted > below: > > PR to update 4.50.x TP too: > https://github.com/jbosstools/jbosstools-target-platforms/pull/196 > > Changes: > > commons.io 2.2 > m2e.apt 1.2 > m2e 1.6.3 > aeri 1.0.0.v20150617-0732 -> 1.100.0.v20160217-0435 > launchbar 1.0.1 > e4.ui.importer 0.2 > docker tools 1.2.1 RC4 > > I assume this relates to > https://github.com/jbosstools/jbosstools-target-platforms/pull/195 too ? > > +1 to get this into Mars asap so we can get the Aeri stuff tested asap. > > Right now it can only run on my machine which is sad :) > > /max > > (Also fixed the subject heading of this email.) > > On Thu, Feb 18, 2016 at 2:07 PM, Nick Boldt nboldt at redhat.com wrote: > > Note that the PR may be incomplete (will check for newer stuff than > is in Mars, m2e, m2e-atp, and WTP later) but I'm sending this out in > advance so people are aware of the forthcoming changes. > > -- > > Here is a proposal for a change to the JBoss Tools and Red Hat JBoss > Developer Studio 4.52.0.CR1-SNAPSHOT target platforms (for JBT > 4.3.1.CR1 / JBDS 9.1.0.CR1). > > https://github.com/jbosstools/jbosstools-target-platforms/pull/195 > https://github.com/jbosstools/jbosstools-discovery/pull/327 > > It consists of the following changes: > > https://issues.jboss.org/browse/JBIDE-21651 > > : update to latest Mars.2.RC4 > : update to WTP > : update to m2e 1.6.3 > : update to m2e-apt 1.2 > : update to Docker 1.2.1.201602162146 > : addition of org.apache.commons.io 2.2.0 (already had 2.0.1, but now > need 2.2.0 too to resolve Aeri deps) > > p2diff reports will be attached to the above JIRA > > ________________________________ > > Please review the above PR(s), as they will be applied as soon as possible > in > preparation for CR1 code freeze. > > You can use the following to build & test the > target-platform locally against your component(s). > > Build target-platform: > $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple > $ git fetch origin pull/195/head && git checkout FETCH_HEAD > $ mvn clean install > > Then, to test the new "multiple" target platform against your component's > build: > $ cd /path/to/your/jbosstools-component > $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT > -Dtpc.targetKind=multiple > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > > ________________________________ > > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > /max > http://about.me/maxandersen -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Feb 19 00:27:46 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Feb 2016 00:27:46 -0500 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: Building locally: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally Verifying local changes to repo references to ensure IU versions are updated too: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files More: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen wrote: > Adding back the list. > >> I suspect you were in the wrong folder. When I build it, I only build >> the multiple/pom.xml, not the unified one. > > Gotcha. My bad. I missed the cd. Been too long since I build the tp locally. > > Can you Remind me what is needed to build the full TP for these PRs ? i thought once once could build these with a mvn verify. > > /max > >> >> N >> >> On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen >> wrote: >>> On 18 Feb 2016, at 20:07, Nick Boldt wrote: >>> >>>> Build target-platform: >>>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >>>> $ git fetch origin pull/195/head && git checkout FETCH\_HEAD >>>> $ mvn clean install >>> >>> >>> I tried this and I got: >>> >>> [INFO] >>> [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) >>> @ jbdevstudio-unified --- >>> [INFO] >>> [INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform >>> (default) @ jbdevstudio-unified --- >>> [INFO] Validating >>> /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... >>> [INFO] Adding repository >>> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO >>> [INFO] Failed, see Error log below >>> [ERROR] Validation found errors in 1 .target files: >>> Could not resolve content of jbdevstudio-unified.target >>> >>> >>> Known issue ? >>> >>> so in short, i'm all for getting the changes in but I cannot build any of >>> the suggested PR's >>> so I can't verify them. :/ >>> >>> /max >>> >>>> >>>> Then, to test the new "multiple" target platform against your component's >>>> build: >>>> $ cd /path/to/your/jbosstools-component >>>> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >>>> -Dtpc.targetKind=multiple >>> >>> >>> >>> /max >>> http://about.me/maxandersen >> >> >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Feb 19 00:29:18 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Feb 2016 00:29:18 -0500 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: Or if you like running a script vs. reading a document: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/verifyTarget.sh On Fri, Feb 19, 2016 at 12:27 AM, Nick Boldt wrote: > Building locally: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally > > Verifying local changes to repo references to ensure IU versions are > updated too: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files > > More: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse > > > On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen > wrote: >> Adding back the list. >> >>> I suspect you were in the wrong folder. When I build it, I only build >>> the multiple/pom.xml, not the unified one. >> >> Gotcha. My bad. I missed the cd. Been too long since I build the tp locally. >> >> Can you Remind me what is needed to build the full TP for these PRs ? i thought once once could build these with a mvn verify. >> >> /max >> >>> >>> N >>> >>> On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen >>> wrote: >>>> On 18 Feb 2016, at 20:07, Nick Boldt wrote: >>>> >>>>> Build target-platform: >>>>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >>>>> $ git fetch origin pull/195/head && git checkout FETCH\_HEAD >>>>> $ mvn clean install >>>> >>>> >>>> I tried this and I got: >>>> >>>> [INFO] >>>> [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) >>>> @ jbdevstudio-unified --- >>>> [INFO] >>>> [INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform >>>> (default) @ jbdevstudio-unified --- >>>> [INFO] Validating >>>> /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... >>>> [INFO] Adding repository >>>> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO >>>> [INFO] Failed, see Error log below >>>> [ERROR] Validation found errors in 1 .target files: >>>> Could not resolve content of jbdevstudio-unified.target >>>> >>>> >>>> Known issue ? >>>> >>>> so in short, i'm all for getting the changes in but I cannot build any of >>>> the suggested PR's >>>> so I can't verify them. :/ >>>> >>>> /max >>>> >>>>> >>>>> Then, to test the new "multiple" target platform against your component's >>>>> build: >>>>> $ cd /path/to/your/jbosstools-component >>>>> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >>>>> -Dtpc.targetKind=multiple >>>> >>>> >>>> >>>> /max >>>> http://about.me/maxandersen >>> >>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools & Dev Studio >>> http://nick.divbyzero.com > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Fri Feb 19 01:33:23 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 19 Feb 2016 07:33:23 +0100 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.CR1-SNAPSHOT and 4.50.2.CR1-SNAPSHOT: Mars.2.RC4 + AERI, Docker, Easymport, m2e, m2e-apt In-Reply-To: References: <23663BF2-364E-4D37-A433-09E8AE0B1C1A@redhat.com> Message-ID: On 19 Feb 2016, at 6:24, Nick Boldt wrote: > PRs 195 and 196 (plus 327) have been merged and built. > > See details in JIRA: > > https://issues.jboss.org/browse/JBIDE-21651 great - and the usage PR actually builds as a result now. Still confused by the fact the TP had 1.100 in the branch, but not in the beta2-snapshot that was live. I reckon we missed to do an updated build ? /max > > > > On Thu, Feb 18, 2016 at 5:16 PM, Max Rydahl Andersen > wrote: >> On 18 Feb 2016, at 20:41, Nick Boldt wrote: >> >> Another PR. This one updates the 4.50.x TP to the latest versions noted >> below: >> >> PR to update 4.50.x TP too: >> https://github.com/jbosstools/jbosstools-target-platforms/pull/196 >> >> Changes: >> >> commons.io 2.2 >> m2e.apt 1.2 >> m2e 1.6.3 >> aeri 1.0.0.v20150617-0732 -> 1.100.0.v20160217-0435 >> launchbar 1.0.1 >> e4.ui.importer 0.2 >> docker tools 1.2.1 RC4 >> >> I assume this relates to >> https://github.com/jbosstools/jbosstools-target-platforms/pull/195 too ? >> >> +1 to get this into Mars asap so we can get the Aeri stuff tested asap. >> >> Right now it can only run on my machine which is sad :) >> >> /max >> >> (Also fixed the subject heading of this email.) >> >> On Thu, Feb 18, 2016 at 2:07 PM, Nick Boldt nboldt at redhat.com wrote: >> >> Note that the PR may be incomplete (will check for newer stuff than >> is in Mars, m2e, m2e-atp, and WTP later) but I'm sending this out in >> advance so people are aware of the forthcoming changes. >> >> -- >> >> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss >> Developer Studio 4.52.0.CR1-SNAPSHOT target platforms (for JBT >> 4.3.1.CR1 / JBDS 9.1.0.CR1). >> >> https://github.com/jbosstools/jbosstools-target-platforms/pull/195 >> https://github.com/jbosstools/jbosstools-discovery/pull/327 >> >> It consists of the following changes: >> >> https://issues.jboss.org/browse/JBIDE-21651 >> >> : update to latest Mars.2.RC4 >> : update to WTP >> : update to m2e 1.6.3 >> : update to m2e-apt 1.2 >> : update to Docker 1.2.1.201602162146 >> : addition of org.apache.commons.io 2.2.0 (already had 2.0.1, but now >> need 2.2.0 too to resolve Aeri deps) >> >> p2diff reports will be attached to the above JIRA >> >> ________________________________ >> >> Please review the above PR(s), as they will be applied as soon as possible >> in >> preparation for CR1 code freeze. >> >> You can use the following to build & test the >> target-platform locally against your component(s). >> >> Build target-platform: >> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >> $ git fetch origin pull/195/head && git checkout FETCH_HEAD >> $ mvn clean install >> >> Then, to test the new "multiple" target platform against your component's >> build: >> $ cd /path/to/your/jbosstools-component >> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >> -Dtpc.targetKind=multiple >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com >> >> ________________________________ >> >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> /max >> http://about.me/maxandersen > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com /max http://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160219/d6f3e988/attachment-0001.html From manderse at redhat.com Fri Feb 19 02:24:26 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 19 Feb 2016 02:24:26 -0500 (EST) Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: Yes - these docs says you can do "mvn clean verify" but that was not the case for the Pr. So that is why I'm asking - why didn't mvn clean verify work ? Incomplete PR or outofdate docs ? /max http://about.me/maxandersen > On 19 Feb 2016, at 06:28, Nick Boldt wrote: > > Building locally: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally > > Verifying local changes to repo references to ensure IU versions are > updated too: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files > > More: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse > > > On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen > wrote: >> Adding back the list. >> >>> I suspect you were in the wrong folder. When I build it, I only build >>> the multiple/pom.xml, not the unified one. >> >> Gotcha. My bad. I missed the cd. Been too long since I build the tp locally. >> >> Can you Remind me what is needed to build the full TP for these PRs ? i thought once once could build these with a mvn verify. >> >> /max >> >>> >>> N >>> >>> On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen >>> wrote: >>>> On 18 Feb 2016, at 20:07, Nick Boldt wrote: >>>> >>>>> Build target-platform: >>>>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >>>>> $ git fetch origin pull/195/head && git checkout FETCH\_HEAD >>>>> $ mvn clean install >>>> >>>> >>>> I tried this and I got: >>>> >>>> [INFO] >>>> [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) >>>> @ jbdevstudio-unified --- >>>> [INFO] >>>> [INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform >>>> (default) @ jbdevstudio-unified --- >>>> [INFO] Validating >>>> /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... >>>> [INFO] Adding repository >>>> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO >>>> [INFO] Failed, see Error log below >>>> [ERROR] Validation found errors in 1 .target files: >>>> Could not resolve content of jbdevstudio-unified.target >>>> >>>> >>>> Known issue ? >>>> >>>> so in short, i'm all for getting the changes in but I cannot build any of >>>> the suggested PR's >>>> so I can't verify them. :/ >>>> >>>> /max >>>> >>>>> >>>>> Then, to test the new "multiple" target platform against your component's >>>>> build: >>>>> $ cd /path/to/your/jbosstools-component >>>>> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >>>>> -Dtpc.targetKind=multiple >>>> >>>> >>>> >>>> /max >>>> http://about.me/maxandersen >>> >>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools & Dev Studio >>> http://nick.divbyzero.com > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com From manderse at redhat.com Fri Feb 19 02:58:46 2016 From: manderse at redhat.com (manderse at redhat.com) Date: Fri, 19 Feb 2016 02:58:46 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201602190758.u1J7wkB0001749@int-mx11.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3599 https://issues.jboss.org/browse/JBDS-3599 Summary: Move Properties view to its previous position Assignee: None set. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 18:33:34.776270 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27 From manderse at redhat.com Fri Feb 19 03:00:15 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 19 Feb 2016 09:00:15 +0100 Subject: [jbosstools-dev] PR templates In-Reply-To: References: Message-ID: On 19 Feb 2016, at 3:10, Gorkem Ercan wrote: > New feature from GitHub > https://github.com/blog/2111-issue-and-pull-request-templates > > Since we don't do issues on GitHub, we can ignore that. But > providing PR templates sounds like a good idea. It does, until one realise it requires maintaining a single file across 40+ repos. I so wish github could have a organisational wide repo to fall back on. > Should we > open a Jira(s) to follow up? What should the templates look like? This made me remember I actually had a draft git commit template for devdoc. I've just pushed it to make it visible. See https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/git_templates.adoc and https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/git_commit_template I've used that for a while now and at least for me it makes me remember to format lines so they look great everywhere (yes, line length matters even on github :), but even more importantly it makes me remember to state the why and how's. These aren't exactly PR templates, but since I never end up using the web ui for PR when I use `hub` these are what ends up in my github PR's. Suggestions welcome and I'm all for adding PR templates and suggest we start by adding one to jbosstools-devdoc and we can then use that as a template for other repos. Some repos might want to list a few specific questions a PR normally should answer - but having a generic one for devdoc could be a good fallback. btw. suggestions welcome on my template - just a starting point. /max http://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160219/54a6660d/attachment.html From manderse at redhat.com Fri Feb 19 05:12:41 2016 From: manderse at redhat.com (manderse at redhat.com) Date: Fri, 19 Feb 2016 05:12:41 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201602191012.u1JACftA026075@int-mx09.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-21719 https://issues.jboss.org/browse/JBIDE-21719 Summary: Move Properties view to its previous position Assignee: None set. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 2:07:23.822378 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=%28filter%3D%27ds_lint_nocomponent%27%29 From nboldt at redhat.com Fri Feb 19 09:31:09 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Feb 2016 09:31:09 -0500 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: Incomplete doc which made you run mvn from the wrong folder. Updated to include more info about multiple/pom.xml vs. unified/pom.xml. https://github.com/jbosstools/jbosstools-devdoc/commit/1add2ef73a540983f88a7c8abbc34519957cf328 On Fri, Feb 19, 2016 at 2:24 AM, Max Rydahl Andersen wrote: > Yes - these docs says you can do "mvn clean verify" but that was not the case for the Pr. > > So that is why I'm asking - why didn't mvn clean verify work ? Incomplete PR or outofdate docs ? > > /max > http://about.me/maxandersen > > >> On 19 Feb 2016, at 06:28, Nick Boldt wrote: >> >> Building locally: >> >> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally >> >> Verifying local changes to repo references to ensure IU versions are >> updated too: >> >> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files >> >> More: >> >> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse >> >> >> On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen >> wrote: >>> Adding back the list. >>> >>>> I suspect you were in the wrong folder. When I build it, I only build >>>> the multiple/pom.xml, not the unified one. >>> >>> Gotcha. My bad. I missed the cd. Been too long since I build the tp locally. >>> >>> Can you Remind me what is needed to build the full TP for these PRs ? i thought once once could build these with a mvn verify. >>> >>> /max >>> >>>> >>>> N >>>> >>>> On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen >>>> wrote: >>>>> On 18 Feb 2016, at 20:07, Nick Boldt wrote: >>>>> >>>>>> Build target-platform: >>>>>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >>>>>> $ git fetch origin pull/195/head && git checkout FETCH\_HEAD >>>>>> $ mvn clean install >>>>> >>>>> >>>>> I tried this and I got: >>>>> >>>>> [INFO] >>>>> [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) >>>>> @ jbdevstudio-unified --- >>>>> [INFO] >>>>> [INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform >>>>> (default) @ jbdevstudio-unified --- >>>>> [INFO] Validating >>>>> /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... >>>>> [INFO] Adding repository >>>>> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO >>>>> [INFO] Failed, see Error log below >>>>> [ERROR] Validation found errors in 1 .target files: >>>>> Could not resolve content of jbdevstudio-unified.target >>>>> >>>>> >>>>> Known issue ? >>>>> >>>>> so in short, i'm all for getting the changes in but I cannot build any of >>>>> the suggested PR's >>>>> so I can't verify them. :/ >>>>> >>>>> /max >>>>> >>>>>> >>>>>> Then, to test the new "multiple" target platform against your component's >>>>>> build: >>>>>> $ cd /path/to/your/jbosstools-component >>>>>> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >>>>>> -Dtpc.targetKind=multiple >>>>> >>>>> >>>>> >>>>> /max >>>>> http://about.me/maxandersen >>>> >>>> >>>> >>>> -- >>>> Nick Boldt :: JBoss by Red Hat >>>> Productization Lead :: JBoss Tools & Dev Studio >>>> http://nick.divbyzero.com >> >> >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Feb 19 09:35:45 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Feb 2016 09:35:45 -0500 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.CR1-SNAPSHOT and 4.50.2.CR1-SNAPSHOT: Mars.2.RC4 + AERI, Docker, Easymport, m2e, m2e-apt In-Reply-To: References: <23663BF2-364E-4D37-A433-09E8AE0B1C1A@redhat.com> Message-ID: Changes to dependencies in the 4.50.x target platform (Mars.0) need to be explicitly requested. AFAIR no one said "we need the 1.100 version in the TP used to BUILD" so I just updated it in the 4.52.x TP (Mars.2), the one used to INSTALL & run tests. Generally we try to avoid having build-time dependencies on Mars.2 versions of IUs, but where necessary, we make allowances for this. Examples: : update to m2e 1.6.3 (rather than staying on 1.6.1) : update to m2e-apt 1.2 (rather than 1.1) : update to Docker 1.2.1.201602162146 (rather than 1.1) : update to Aeri 1.100 (rather than 1.0) This means that our build-time TP will contain NEWER versions of IUs than are present in Mars.0; but since we also include these in our install-time TP, users will benefit from our forcing them to upgrade to the newer version under the covers. On Fri, Feb 19, 2016 at 1:33 AM, Max Rydahl Andersen wrote: > On 19 Feb 2016, at 6:24, Nick Boldt wrote: > > PRs 195 and 196 (plus 327) have been merged and built. > > See details in JIRA: > > https://issues.jboss.org/browse/JBIDE-21651 > > great - and the usage PR actually builds as a result now. > > Still confused by the fact the TP had 1.100 in the branch, but > not in the beta2-snapshot that was live. I reckon we missed to do an > updated build ? > > /max > > On Thu, Feb 18, 2016 at 5:16 PM, Max Rydahl Andersen > manderse at redhat.com wrote: > > On 18 Feb 2016, at 20:41, Nick Boldt wrote: > > Another PR. This one updates the 4.50.x TP to the latest versions noted > below: > > PR to update 4.50.x TP too: > https://github.com/jbosstools/jbosstools-target-platforms/pull/196 > > Changes: > > commons.io 2.2 > m2e.apt 1.2 > m2e 1.6.3 > aeri 1.0.0.v20150617-0732 -> 1.100.0.v20160217-0435 > launchbar 1.0.1 > e4.ui.importer 0.2 > docker tools 1.2.1 RC4 > > I assume this relates to > https://github.com/jbosstools/jbosstools-target-platforms/pull/195 too ? > > +1 to get this into Mars asap so we can get the Aeri stuff tested asap. > > Right now it can only run on my machine which is sad :) > > /max > > (Also fixed the subject heading of this email.) > > On Thu, Feb 18, 2016 at 2:07 PM, Nick Boldt nboldt at redhat.com wrote: > > Note that the PR may be incomplete (will check for newer stuff than > is in Mars, m2e, m2e-atp, and WTP later) but I'm sending this out in > advance so people are aware of the forthcoming changes. > > -- > > Here is a proposal for a change to the JBoss Tools and Red Hat JBoss > Developer Studio 4.52.0.CR1-SNAPSHOT target platforms (for JBT > 4.3.1.CR1 / JBDS 9.1.0.CR1). > > https://github.com/jbosstools/jbosstools-target-platforms/pull/195 > https://github.com/jbosstools/jbosstools-discovery/pull/327 > > It consists of the following changes: > > https://issues.jboss.org/browse/JBIDE-21651 > > : update to latest Mars.2.RC4 > : update to WTP > : update to m2e 1.6.3 > : update to m2e-apt 1.2 > : update to Docker 1.2.1.201602162146 > : addition of org.apache.commons.io 2.2.0 (already had 2.0.1, but now > need 2.2.0 too to resolve Aeri deps) > > p2diff reports will be attached to the above JIRA > > ________________________________ > > Please review the above PR(s), as they will be applied as soon as possible > in > preparation for CR1 code freeze. > > You can use the following to build & test the > target-platform locally against your component(s). > > Build target-platform: > $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple > $ git fetch origin pull/195/head && git checkout FETCH_HEAD > $ mvn clean install > > Then, to test the new "multiple" target platform against your component's > build: > $ cd /path/to/your/jbosstools-component > $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT > -Dtpc.targetKind=multiple > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > > ________________________________ > > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > /max > http://about.me/maxandersen > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > > /max > http://about.me/maxandersen -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Fri Feb 19 12:39:52 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 19 Feb 2016 18:39:52 +0100 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: On 19 Feb 2016, at 15:31, Nick Boldt wrote: > Incomplete doc which made you run mvn from the wrong folder. so my question still stands - why is it that we cannot just run `mvn verify` in TP anymore ? Just wondering since we normally do whatever we can to make builds not require "to know magic" to build. /max > > Updated to include more info about multiple/pom.xml vs. > unified/pom.xml. > > https://github.com/jbosstools/jbosstools-devdoc/commit/1add2ef73a540983f88a7c8abbc34519957cf328 > > On Fri, Feb 19, 2016 at 2:24 AM, Max Rydahl Andersen > wrote: >> Yes - these docs says you can do "mvn clean verify" but that was not >> the case for the Pr. >> >> So that is why I'm asking - why didn't mvn clean verify work ? >> Incomplete PR or outofdate docs ? >> >> /max >> http://about.me/maxandersen >> >> >>> On 19 Feb 2016, at 06:28, Nick Boldt wrote: >>> >>> Building locally: >>> >>> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally >>> >>> Verifying local changes to repo references to ensure IU versions are >>> updated too: >>> >>> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files >>> >>> More: >>> >>> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse >>> >>> >>> On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen >>> wrote: >>>> Adding back the list. >>>> >>>>> I suspect you were in the wrong folder. When I build it, I only >>>>> build >>>>> the multiple/pom.xml, not the unified one. >>>> >>>> Gotcha. My bad. I missed the cd. Been too long since I build the tp >>>> locally. >>>> >>>> Can you Remind me what is needed to build the full TP for these PRs >>>> ? i thought once once could build these with a mvn verify. >>>> >>>> /max >>>> >>>>> >>>>> N >>>>> >>>>> On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen >>>>> wrote: >>>>>> On 18 Feb 2016, at 20:07, Nick Boldt wrote: >>>>>> >>>>>>> Build target-platform: >>>>>>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >>>>>>> $ git fetch origin pull/195/head && git checkout FETCH\\\_HEAD >>>>>>> $ mvn clean install >>>>>> >>>>>> >>>>>> I tried this and I got: >>>>>> >>>>>> [INFO] >>>>>> [INFO] --- build-helper-maven-plugin:1.3:attach-artifact >>>>>> (attach-artifacts) >>>>>> @ jbdevstudio-unified --- >>>>>> [INFO] >>>>>> [INFO] --- >>>>>> target-platform-validation-plugin:0.23.1:validate-target-platform >>>>>> (default) @ jbdevstudio-unified --- >>>>>> [INFO] Validating >>>>>> /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... >>>>>> [INFO] Adding repository >>>>>> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO >>>>>> [INFO] Failed, see Error log below >>>>>> [ERROR] Validation found errors in 1 .target files: >>>>>> Could not resolve content of jbdevstudio-unified.target >>>>>> >>>>>> >>>>>> Known issue ? >>>>>> >>>>>> so in short, i'm all for getting the changes in but I cannot >>>>>> build any of >>>>>> the suggested PR's >>>>>> so I can't verify them. :/ >>>>>> >>>>>> /max >>>>>> >>>>>>> >>>>>>> Then, to test the new "multiple" target platform against your >>>>>>> component's >>>>>>> build: >>>>>>> $ cd /path/to/your/jbosstools-component >>>>>>> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >>>>>>> -Dtpc.targetKind=multiple >>>>>> >>>>>> >>>>>> >>>>>> /max >>>>>> http://about.me/maxandersen >>>>> >>>>> >>>>> >>>>> -- >>>>> Nick Boldt :: JBoss by Red Hat >>>>> Productization Lead :: JBoss Tools & Dev Studio >>>>> http://nick.divbyzero.com >>> >>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools & Dev Studio >>> http://nick.divbyzero.com > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com /max http://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160219/ebacf3a7/attachment-0001.html From nboldt at redhat.com Fri Feb 19 13:01:23 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Feb 2016 13:01:23 -0500 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: The magic is simply "use the correct folder". We can't build the unified tp unless the multiple one already exists. That's how it's constructed. Only workarounds are the ones I documented in the devdoc: build them at the same time but tell the unified to use the locally-built multiple TP's URL, or don't build the unified one since you don't need it anyway. Is your complaint that we have a reactor pom in the root of jbosstools/ and jbdevstudio/ which tries to build BOTH multiple and unified at the same time, rather than in two steps? If so I could remove unified from that pom on line 16: https://github.com/jbosstools/jbosstools-target-platforms/blob/4.52.x/jbosstools/pom.xml#L16 Then you could verify from the jbosstools/ folder instead of the jbosstools/multiple folder. On Fri, Feb 19, 2016 at 12:39 PM, Max Rydahl Andersen wrote: > On 19 Feb 2016, at 15:31, Nick Boldt wrote: > > Incomplete doc which made you run mvn from the wrong folder. > > so my question still stands - why is it that we cannot just run mvn verify > in TP anymore ? > > Just wondering since we normally do whatever we can to make builds not > require "to know magic" to build. > > /max > > Updated to include more info about multiple/pom.xml vs. unified/pom.xml. > > https://github.com/jbosstools/jbosstools-devdoc/commit/1add2ef73a540983f88a7c8abbc34519957cf328 > > On Fri, Feb 19, 2016 at 2:24 AM, Max Rydahl Andersen > manderse at redhat.com wrote: > > Yes - these docs says you can do "mvn clean verify" but that was not the > case for the Pr. > > So that is why I'm asking - why didn't mvn clean verify work ? Incomplete PR > or outofdate docs ? > > /max > http://about.me/maxandersen > > On 19 Feb 2016, at 06:28, Nick Boldt nboldt at redhat.com wrote: > > Building locally: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally > > Verifying local changes to repo references to ensure IU versions are > updated too: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files > > More: > > https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse > > On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen > manderse at redhat.com wrote: > > Adding back the list. > > I suspect you were in the wrong folder. When I build it, I only build > the multiple/pom.xml, not the unified one. > > Gotcha. My bad. I missed the cd. Been too long since I build the tp locally. > > Can you Remind me what is needed to build the full TP for these PRs ? i > thought once once could build these with a mvn verify. > > /max > > N > > On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen > manderse at redhat.com wrote: > > On 18 Feb 2016, at 20:07, Nick Boldt wrote: > > Build target-platform: > $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple > $ git fetch origin pull/195/head && git checkout FETCH\_HEAD > $ mvn clean install > > I tried this and I got: > > [INFO] > [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) > @ jbdevstudio-unified --- > [INFO] > [INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform > (default) @ jbdevstudio-unified --- > [INFO] Validating > /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... > [INFO] Adding repository > https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO > [INFO] Failed, see Error log below > [ERROR] Validation found errors in 1 .target files: > Could not resolve content of jbdevstudio-unified.target > > Known issue ? > > so in short, i'm all for getting the changes in but I cannot build any of > the suggested PR's > so I can't verify them. :/ > > /max > > Then, to test the new "multiple" target platform against your component's > build: > $ cd /path/to/your/jbosstools-component > $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT > -Dtpc.targetKind=multiple > > /max > http://about.me/maxandersen > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > > /max > http://about.me/maxandersen -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Fri Feb 19 14:23:27 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 19 Feb 2016 20:23:27 +0100 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: On 19 Feb 2016, at 19:01, Nick Boldt wrote: > The magic is simply "use the correct folder". We can't build the > unified tp unless the multiple one already exists. > That's how it's > constructed. Only workarounds are the ones I documented in the devdoc: > build them at the same time but tell the unified to use the > locally-built multiple TP's URL, or don't build the unified one since > you don't need it anyway. > > Is your complaint that we have a reactor pom in the root of > jbosstools/ and jbdevstudio/ which tries to build BOTH multiple and > unified at the same time, rather than in two steps? > > If so I could remove unified from that pom on line 16: > > https://github.com/jbosstools/jbosstools-target-platforms/blob/4.52.x/jbosstools/pom.xml#L16 > > Then you could verify from the jbosstools/ folder instead of the > jbosstools/multiple folder. Why don't it just build them in the right sequence ? How is this any different than any of our other reactor pom's that make sure things are built in the right order ? /max > > > > > On Fri, Feb 19, 2016 at 12:39 PM, Max Rydahl Andersen > wrote: >> On 19 Feb 2016, at 15:31, Nick Boldt wrote: >> >> Incomplete doc which made you run mvn from the wrong folder. >> >> so my question still stands - why is it that we cannot just run mvn >> verify >> in TP anymore ? >> >> Just wondering since we normally do whatever we can to make builds >> not >> require "to know magic" to build. >> >> /max >> >> Updated to include more info about multiple/pom.xml vs. >> unified/pom.xml. >> >> https://github.com/jbosstools/jbosstools-devdoc/commit/1add2ef73a540983f88a7c8abbc34519957cf328 >> >> On Fri, Feb 19, 2016 at 2:24 AM, Max Rydahl Andersen >> manderse at redhat.com wrote: >> >> Yes - these docs says you can do "mvn clean verify" but that was not >> the >> case for the Pr. >> >> So that is why I'm asking - why didn't mvn clean verify work ? >> Incomplete PR >> or outofdate docs ? >> >> /max >> http://about.me/maxandersen >> >> On 19 Feb 2016, at 06:28, Nick Boldt nboldt at redhat.com wrote: >> >> Building locally: >> >> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#build-target-platforms-locally >> >> Verifying local changes to repo references to ensure IU versions are >> updated too: >> >> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files >> >> More: >> >> https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.adoc#using-a-target-platform-in-eclipse >> >> On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen >> manderse at redhat.com wrote: >> >> Adding back the list. >> >> I suspect you were in the wrong folder. When I build it, I only build >> the multiple/pom.xml, not the unified one. >> >> Gotcha. My bad. I missed the cd. Been too long since I build the tp >> locally. >> >> Can you Remind me what is needed to build the full TP for these PRs ? >> i >> thought once once could build these with a mvn verify. >> >> /max >> >> N >> >> On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen >> manderse at redhat.com wrote: >> >> On 18 Feb 2016, at 20:07, Nick Boldt wrote: >> >> Build target-platform: >> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple >> $ git fetch origin pull/195/head && git checkout FETCH\\\_HEAD >> $ mvn clean install >> >> I tried this and I got: >> >> [INFO] >> [INFO] --- build-helper-maven-plugin:1.3:attach-artifact >> (attach-artifacts) >> @ jbdevstudio-unified --- >> [INFO] >> [INFO] --- >> target-platform-validation-plugin:0.23.1:validate-target-platform >> (default) @ jbdevstudio-unified --- >> [INFO] Validating >> /Users/max/code/jbosstools/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target... >> [INFO] Adding repository >> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1-SNAPSHOT/REPO >> [INFO] Failed, see Error log below >> [ERROR] Validation found errors in 1 .target files: >> Could not resolve content of jbdevstudio-unified.target >> >> Known issue ? >> >> so in short, i'm all for getting the changes in but I cannot build >> any of >> the suggested PR's >> so I can't verify them. :/ >> >> /max >> >> Then, to test the new "multiple" target platform against your >> component's >> build: >> $ cd /path/to/your/jbosstools-component >> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT >> -Dtpc.targetKind=multiple >> >> /max >> http://about.me/maxandersen >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com >> >> /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 Mon Feb 22 02:58:43 2016 From: manderse at redhat.com (manderse at redhat.com) Date: Mon, 22 Feb 2016 02:58:43 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201602220758.u1M7whfZ023657@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3601 https://issues.jboss.org/browse/JBDS-3601 Summary: No splash screen during JBDS 8.x startup on Windows Assignee: None set. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 4:09:46.503117 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27 From manderse at redhat.com Mon Feb 22 04:17:06 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 22 Feb 2016 10:17:06 +0100 Subject: [jbosstools-dev] Eclipse error reporting for jbosstools is now enabled in maintenance branch Message-ID: <7848BB22-EF29-48E0-887A-951849831F1F@redhat.com> Hey all, I've enabled eclipse error reporting for jbosstools in latest maintenance [1] builds. Everyone who runs it please go and submit error reports everytime you see the error reporting popup. If you see issues (or you don't see it at all) please open bugs against https://jira.jboss.org/jira/browse/JBIDE under the "aeri" component. Then I or Marcel (in cc) will see and react. It would be great, but not a requirement if you set the username/email for the JBoss Tools reporting then we can more easily see how varied/spread out the reporting is. We want to see as many reports as possible - so just keep sending them :) I'll keep you posted on findings through the following days. [1] https://issues.jboss.org/browse/JBIDE-21654 /max http://about.me/maxandersen From manderse at redhat.com Mon Feb 22 08:20:27 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 22 Feb 2016 14:20:27 +0100 Subject: [jbosstools-dev] Eclipse error reporting for jbosstools is now enabled in maintenance branch In-Reply-To: <7848BB22-EF29-48E0-887A-951849831F1F@redhat.com> References: <7848BB22-EF29-48E0-887A-951849831F1F@redhat.com> Message-ID: <087E2F4C-E700-4F86-8A69-E266BE14EBDA@redhat.com> quick demo of how it should work: https://v.usetapes.com/qTpjwQ31eF /max > Hey all, > > I've enabled eclipse error reporting for jbosstools in latest > maintenance [1] builds. > > Everyone who runs it please go and submit error reports everytime you > see the error > reporting popup. > > If you see issues (or you don't see it at all) please open bugs > against https://jira.jboss.org/jira/browse/JBIDE > under the "aeri" component. Then I or Marcel (in cc) will see and > react. > > It would be great, but not a requirement if you set the username/email > for the JBoss Tools reporting then > we can more easily see how varied/spread out the reporting is. > > We want to see as many reports as possible - so just keep sending them > :) > > I'll keep you posted on findings through the following days. > > [1] https://issues.jboss.org/browse/JBIDE-21654 > > /max > http://about.me/maxandersen /max http://about.me/maxandersen From manderse at redhat.com Mon Feb 22 08:28:47 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 22 Feb 2016 14:28:47 +0100 Subject: [jbosstools-dev] Proposed changes to target platform 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer, YAML Editor In-Reply-To: References: <539A9E5E-3276-497A-8017-B71ACB2E7E81@redhat.com> Message-ID: On 19 Feb 2016, at 20:23, Max Rydahl Andersen wrote: > On 19 Feb 2016, at 19:01, Nick Boldt wrote: > >> The magic is simply "use the correct folder". We can't build the >> unified tp unless the multiple one already exists. >> That's how it's >> constructed. Only workarounds are the ones I documented in the >> devdoc: >> build them at the same time but tell the unified to use the >> locally-built multiple TP's URL, or don't build the unified one since >> you don't need it anyway. >> >> Is your complaint that we have a reactor pom in the root of >> jbosstools/ and jbdevstudio/ which tries to build BOTH multiple and >> unified at the same time, rather than in two steps? >> >> If so I could remove unified from that pom on line 16: >> >> https://github.com/jbosstools/jbosstools-target-platforms/blob/4.52.x/jbosstools/pom.xml#L16 >> >> Then you could verify from the jbosstools/ folder instead of the >> jbosstools/multiple folder. > > Why don't it just build them in the right sequence ? > > How is this any different than any of our other reactor pom's that > make sure things > are built in the right order ? Mickael reminded me why it works like it does now is that unified depends on multiple to have published its contents to its urls first. Thus it becomes a chicken egg problem. Would be nice if mvn clean verify would actually just work and have the full deploy mechanism be something enabled by a profile. But thats a future improvement - now I grok why we have it that mvn clean verify doesn't work. /max http://about.me/maxandersen From wnwe at hqaunamsa.com Tue Feb 23 13:26:10 2016 From: wnwe at hqaunamsa.com (=?utf-8?B?6aW255Cq5pm6?=) Date: Wed, 24 Feb 2016 02:26:10 +0800 Subject: [jbosstools-dev] =?utf-8?b?amJvc3N0b29scy1kZXY65LyB5Lia5aaC5L2V?= =?utf-8?b?5Z+55YW75Lit5Z2a5Yqb6YeP?= Message-ID: <20160224022620360536@hqaunamsa.com> ??????????????????????????????????????????????????????????????????????????????????????????2:26:19 ?????????????????????? h31ng 2016/2/24 ???2:26:19 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160224/c3209c7d/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ? ? ? ? 6 ??.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 30257 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160224/c3209c7d/attachment-0001.bin From tnc at ds.net Wed Feb 24 10:01:48 2016 From: tnc at ds.net (=?utf-8?B?6KGh6K+X5p+U?=) Date: Wed, 24 Feb 2016 23:01:48 +0800 Subject: [jbosstools-dev] =?utf-8?b?amJvc3NpZGUtZGV2OuWmguS9leacieaViA==?= =?utf-8?b?55qE5oub6IGY6Z2i6K+V?= Message-ID: <20160224230200020870@ds.net> jbosside-dev??? ???????????????? ??????????? uhacr 2016-2-2423:01:59 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160224/79ba1e74/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ?????.doc Type: application/msword Size: 62464 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160224/79ba1e74/attachment-0001.doc From mistria at redhat.com Wed Feb 24 11:45:45 2016 From: mistria at redhat.com (Mickael Istria) Date: Wed, 24 Feb 2016 17:45:45 +0100 Subject: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! Message-ID: <56CDDE39.5070301@redhat.com> Hi all, We're in the last week to include upstream changes via target-platforms for JBoss Tools 4.3.1 and JBDS 9.1. So if you already need something, or know you'll need something to be changed before code-freeze, please open a Jira immediately (and add the link to it as an answer of this mail). 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/20160224/ae2194ad/attachment.html From noreply at netlogmail.com Thu Feb 25 21:17:49 2016 From: noreply at netlogmail.com (Johnson Lauren) Date: Thu, 25 Feb 2016 19:17:49 -0700 Subject: [jbosstools-dev] WORK FROM HOME MALE OR FEMALE NEEDED.. APPPLICATION APPROVED WITHIN 24HOURS Message-ID: - This mail is in HTML. Some elements may be ommited in plain text. - Good Morning, I'm Barr, Johnson Lauren and i work as a Financial Consultant. Here is an Opportunity to benefit from Swiss Government Funding and EU funding. Are you versatile, Do you like diversification?? Let me introduce you to the world of financial prosperity. Earn money working for Gov Officials/EU Congress in Swiss and Germany and earn ?3000.00 weekly. Doesn't affect your present job or career. You don`t drop a dime, No upfront fees, No paybacks, No strings attached. E-mail your contact information: NAME: HOME ADDRESS: MOBILE NUMBER: Regards Barr Johnson Lauren. johnsonlauren at legislator.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160225/36e196d2/attachment.html From nboldt at redhat.com Fri Feb 26 00:22:08 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 26 Feb 2016 00:22:08 -0500 Subject: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! In-Reply-To: <56CDDE39.5070301@redhat.com> References: <56CDDE39.5070301@redhat.com> Message-ID: Do we want to update anything in Central? For example, we could update to the latest Eclipse Checkstyle plugin 6.14 (currently 6.5): https://issues.jboss.org/browse/JBDS-3518 Do we want a newer version of any of these? * mylyn egit 4.1.1 * m2e-wro4j 1.1 * atlassian 3.2.5 w/ mylyn soap 3.11 * pmd 4.0.7 * springIDE 3.7.0 * subclipse 1.10.9 w/ svnkit 1.8.10 * testng 6.9.5 * findbugs 3.0.1 Many of the above are from March - June 2015, so by the time we GA they'll be ~1yr old. Is it worth looking for updated versions? If so, please let me know WHICH should be updated so I can open JIRAs to get QE to review the new versions, and then pull mirrors to update the Central target platform to the newer versions. On Wed, Feb 24, 2016 at 11:45 AM, Mickael Istria wrote: > Hi all, > > We're in the last week to include upstream changes via target-platforms for > JBoss Tools 4.3.1 and JBDS 9.1. > So if you already need something, or know you'll need something to be > changed before code-freeze, please open a Jira immediately (and add the link > to it as an answer of this mail). > > Cheers, > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From apodhrad at redhat.com Fri Feb 26 04:19:17 2016 From: apodhrad at redhat.com (Andrej Podhradsky) Date: Fri, 26 Feb 2016 04:19:17 -0500 (EST) Subject: [jbosstools-dev] Cannot resolve jbosstools parent pom In-Reply-To: <75533434.30687060.1456477977628.JavaMail.zimbra@redhat.com> Message-ID: <1675981690.30697166.1456478357649.JavaMail.zimbra@redhat.com> Hi all, today I wasn't able to build jbosstools projects due to unresolved parent pom. The problem is that there's nothing at https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/parent/ It seems that the problem isn't only related to jbosstools. I raised an issue here https://engineering.redhat.com/rt/Ticket/Display.html?id=393060 Best Regards -- Andrej Podhradsky Quality Assurance Engineer JBoss SOA Platform IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno From alkazako at redhat.com Fri Feb 26 09:54:26 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Fri, 26 Feb 2016 09:54:26 -0500 Subject: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! In-Reply-To: References: <56CDDE39.5070301@redhat.com> Message-ID: <56D06722.8030500@redhat.com> Len? Does QE have any plans to test anything from the list? On 02/26/2016 12:22 AM, Nick Boldt wrote: > Do we want to update anything in Central? > > For example, we could update to the latest Eclipse Checkstyle plugin > 6.14 (currently 6.5): > > https://issues.jboss.org/browse/JBDS-3518 > > Do we want a newer version of any of these? > > * mylyn egit 4.1.1 > * m2e-wro4j 1.1 > * atlassian 3.2.5 w/ mylyn soap 3.11 > * pmd 4.0.7 > * springIDE 3.7.0 > * subclipse 1.10.9 w/ svnkit 1.8.10 > * testng 6.9.5 > * findbugs 3.0.1 > > Many of the above are from March - June 2015, so by the time we GA > they'll be ~1yr old. > > Is it worth looking for updated versions? > > If so, please let me know WHICH should be updated so I can open JIRAs > to get QE to review the new versions, and then pull mirrors to update > the Central target platform to the newer versions. > > > On Wed, Feb 24, 2016 at 11:45 AM, Mickael Istria wrote: >> Hi all, >> >> We're in the last week to include upstream changes via target-platforms for >> JBoss Tools 4.3.1 and JBDS 9.1. >> So if you already need something, or know you'll need something to be >> changed before code-freeze, please open a Jira immediately (and add the link >> to it as an answer of this mail). >> >> Cheers, >> -- >> Mickael Istria >> Eclipse developer at JBoss, by Red Hat >> My blog - My Tweets >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > From pzhhl at 21cn.com Fri Feb 26 12:14:18 2016 From: pzhhl at 21cn.com (tcacsj233) Date: Sat, 27 Feb 2016 01:14:18 +0800 Subject: [jbosstools-dev] =?gb2312?b?yMvBptfK1LRqYm9zc2lkZS1kZXY=?= Message-ID: <201602261713.u1QHDwiD017098@lists01.dmz-a.mwc.hst.phx2.redhat.com> ???????????????????????????????????????????????" ???????? ???? > ?????? 2016? 3?11-12??? 3?18-19??? 3?23-24??? 3?31-4?1??? 4?8-9??? 4?15-16??? 4?22-23??? 4?28-29??? ?????? ???????????????????/??/????????????????? ?????????????????? ?????? ???? + ???? + ???? +???? + ???? ?????? 1????????????????? 2?????????????????? 3???????????????????? 4?????????????????????? ???? A??????2??15???????? ???????? 1.???????????????????????????? 2.?????????????????? 3.???????????????????????? 4.?????????????????????????? 5.?????????????? 6.?????????????????????????? 7.?????????????????????????? 8.??????????????????? 9.??????????????????????? ?????????? 1.????????????????????????????? 2.?????????????????????????? 3.????????????????????????????????? 4.????????????????????????????????? 5.?????????????????????? 6.????2???????????????????????? 7.??????????????????????????????? 8.?????????????????????? ??????? 1.?????????????????????? 2.?????????????????????????? 3.?????????????2??????????? 4.?????????????????70%?????? 5.?????????????????50%?????? 6.?????????????????????? 7.??????????????????????????? 8.???????????????????????????? ????????????? 1.???????????????????????????? 2.????????????????????? 3.??????????????????????? 4.??????????????????????10????????????????????? ??? 5.???????????????????????????????????????????? ??????? 6.???????????????????????????????????????????? ???????????????????? ?????????? 1.?????????????????????????????????????? 2.???????????????????????????????????????????? ??? 3.??????????????????????????????????? 4.????????????????? 5.?????????????????????? 6.???????????????????? 7.????????????????? 8.??????????????????? ???????????? 1.???????????????????????????????????????????? ??????????????????????? 2.??????????????????????????????? 3.?????30????????????????????? 4.?????????30?????????????????????? 5.?????????30??????????????????????? 6.????????????????????????? 7.????????????????????????????????????????????? 8.???????????????????????????????????????????? ???????????? 9.??????????????????????????????????????????? 10.???????????????????????????????????????????? ?????????????? 11.???????????????????????????? 12.???????????????????????????????????????????? ???????????????? ????????? 1.?????????????????? 2.?????????????????? 3.?????????????????????????????? 4.???????????????? 5.???????????????????????????????? 6.???????????????????????? 7.??????????????????? 8.?????????????????????????????? ?????????? 1.??????????????? 2.????????????????????? 3.???????????????? 4.?????????????????????? 5.??????????????????????????? 6.???????????????? 7.????????????????????? 8.???????????????????? B??????2??15???????? ????????????? 1.????????????????????????????????? 2.??????????????????2?????????????? 3.??????????????????? 4.??????????????????????????????? 5.???????????????????????????????? 6.??????????????????? 7.??????????????????? 8.????????????5%?????????????? ????????????? 1.????????????? 2.???????????????? 3.?????????????????? 4.????????????????????? 5.???????? 6.????????????? 7.????????????????????? 8.???????????????????????????? 9.??????????????????? 10.???????\??????????????????????? 11.????????????????????????????? 12.?????????????????????????????? ?????????????? 1.??????????????????????? 2.??????????????????????????????????? 3.?????????????????? 4.???????????????????? 5.????????????????????????????????? 6.???????????????????????????? 7.?????????????????????????????????? 8.???????????????????????? 9.???????????????????????? 10.??????????????????????????????????????????? ?? 11.???????????????????????????????????????????? ??????? 12.???????????????????????OA???????????????????? ????????????? ???????? 1.?????????????????????? 2.???????????????????? 3.??????????????????????? 4.????????????????? 5.???????????????????? 6.??????????????????????? 7.???????????????????????????????????????????? ??? 8.?????????50%??????????????? ????????????? 1.????????????????????????? 2.???????????????????????? 3.???????????????????????????? 4.???????????????????? 5.????????????????????? 6.?????????????????????? 7.?????????????????? 8.????????????????????????????????? ?????????? 1.????????????? 2.?????????????? 3.?????????????????????? 4.??????????????????? 5.??????????????????????? 6.???????????????????????????????????????????? ??? 7.????????????????????????? 8.??????????????????????????? ???????? 1.????????????????????? 2.????????????????????? 3.?????????????????? 4.?????????????????????????? 5.??????????????????????????????? 6.???????????????????????????? 7.?????????????????? 8.????????????????????? 9.???????????????????? 10.??????????????????? 11.???????????????????????????????? 12.?????????????????? 13.?????????????????? 14.???????????????????? ???? >????? ??????? ?????? ??????????????????????????????????????????? ?????????????????????????????????????????????? ??????????????????????? ????????(??)?????????????????????????????????? ?????????????????????????????????????????????? ?????????????????????????????100?????????????? ????????????? ?????? ??????????????????????????????????????????? ????????????????????????????????????????????? ?????????????????????????????????????????????? ????????????????????????????????????????????? ???????????????100%???? ?????? ????????????????????????????????????????400? ?????????????500????????????????20???????400????? ?????????????????30?????200????????????????????? ????????????????????????????????????????????95%? 2004????????????????????????????30000????????70000 ?????????20??????????????????????????????????? ????????????????????????????80%??????20%????????? ????????????????????????????????????????????? 95%???????????????????????????????????????????? ????????????????????????? ??????????????????????????????????????????? ????????????????????????50??? ?????? ??????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ?????????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ??? ???????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ???????????????????????????????????????????? ????????????????????????????????????????????? ?????????????????????????NETSFIM???????????????? ????????????????????????????????????????????? ????????????????????????????????????????????? ???????????TCL???????????????????????????????? ??????????????????? ?????? ??????????????????????????????????????? ?????????????5???????????????????????????????? ????????????????????????????????? ????????????????????????????????????????????? ?????????????????? ?????? ??A???2800?/1??5000?/2????B???2800?/1??5000?/2?? ??AB???5000?/???????????????????? ??????15074222418?? 0755-6128 9249 ??????QQ/???1491311350 ???? ??1491311350 at qq.com ??????2???????A???B??????????????????????????? ???A????B????AB???????????A?????B???????B?????A?? ???A???B???????????????? jbosside-dev383926 From nboldt at redhat.com Fri Feb 26 12:41:47 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 26 Feb 2016 12:41:47 -0500 Subject: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! In-Reply-To: <56D06722.8030500@redhat.com> References: <56CDDE39.5070301@redhat.com> <56D06722.8030500@redhat.com> Message-ID: Given our dates have shifted for CR1 and GA, I suspect the answer is yes to the notion that QE would have time to test these. But before I open a bunch of JIRAs for QE to verify new versions of Central contents, I need to know that PM wants these updates. QE won't plan to test things unless we first decide we WANT to do the updates. Process is generally this: * request to update something in Central is opened as a JBDS/JBIDE JIRA * Nick pulls a mirror onto dl.jb.o * JIRA is assigned to QE; QE verifies that installation works and functionality is not lost * QE assigns JIRA back to Nick, who submits a PR for the Central TP updates * email sent to this list for review / feedback * changes are merged, built, and automated install tests are run * JIRAs are resolved * QE verifies and closes the JIRAs HTH, Nick On Fri, Feb 26, 2016 at 9:54 AM, Alexey Kazakov wrote: > Len? Does QE have any plans to test anything from the list? > > On 02/26/2016 12:22 AM, Nick Boldt wrote: >> Do we want to update anything in Central? >> >> For example, we could update to the latest Eclipse Checkstyle plugin >> 6.14 (currently 6.5): >> >> https://issues.jboss.org/browse/JBDS-3518 >> >> Do we want a newer version of any of these? >> >> * mylyn egit 4.1.1 >> * m2e-wro4j 1.1 >> * atlassian 3.2.5 w/ mylyn soap 3.11 >> * pmd 4.0.7 >> * springIDE 3.7.0 >> * subclipse 1.10.9 w/ svnkit 1.8.10 >> * testng 6.9.5 >> * findbugs 3.0.1 >> >> Many of the above are from March - June 2015, so by the time we GA >> they'll be ~1yr old. >> >> Is it worth looking for updated versions? >> >> If so, please let me know WHICH should be updated so I can open JIRAs >> to get QE to review the new versions, and then pull mirrors to update >> the Central target platform to the newer versions. >> >> >> On Wed, Feb 24, 2016 at 11:45 AM, Mickael Istria wrote: >>> Hi all, >>> >>> We're in the last week to include upstream changes via target-platforms for >>> JBoss Tools 4.3.1 and JBDS 9.1. >>> So if you already need something, or know you'll need something to be >>> changed before code-freeze, please open a Jira immediately (and add the link >>> to it as an answer of this mail). >>> >>> Cheers, >>> -- >>> Mickael Istria >>> Eclipse developer at JBoss, by Red Hat >>> My blog - My Tweets >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From alkazako at redhat.com Fri Feb 26 13:09:01 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Fri, 26 Feb 2016 13:09:01 -0500 (EST) Subject: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! In-Reply-To: References: <56CDDE39.5070301@redhat.com> <56D06722.8030500@redhat.com> Message-ID: <2779BC6D-809B-4A2C-9EFF-196D4DC7151F@redhat.com> I might be wrong but I remember we have already discussed it on some PM call and agreed that QE monitors if we need to update some 3rd party stuff in central and opens JIRAs if needed. Anyway I don't think we currently have a PM who would request such updates ;) So the main question is for QE. If they are OK to test it then we can consider updating it. > On Feb 26, 2016, at 12:42 PM, Nick Boldt wrote: > > Given our dates have shifted for CR1 and GA, I suspect the answer is > yes to the notion that QE would have time to test these. But before I > open a bunch of JIRAs for QE to verify new versions of Central > contents, I need to know that PM wants these updates. > > QE won't plan to test things unless we first decide we WANT to do the updates. > > Process is generally this: > > * request to update something in Central is opened as a JBDS/JBIDE JIRA > * Nick pulls a mirror onto dl.jb.o > * JIRA is assigned to QE; QE verifies that installation works and > functionality is not lost > * QE assigns JIRA back to Nick, who submits a PR for the Central TP updates > * email sent to this list for review / feedback > * changes are merged, built, and automated install tests are run > * JIRAs are resolved > * QE verifies and closes the JIRAs > > HTH, > > Nick > >> On Fri, Feb 26, 2016 at 9:54 AM, Alexey Kazakov wrote: >> Len? Does QE have any plans to test anything from the list? >> >>> On 02/26/2016 12:22 AM, Nick Boldt wrote: >>> Do we want to update anything in Central? >>> >>> For example, we could update to the latest Eclipse Checkstyle plugin >>> 6.14 (currently 6.5): >>> >>> https://issues.jboss.org/browse/JBDS-3518 >>> >>> Do we want a newer version of any of these? >>> >>> * mylyn egit 4.1.1 >>> * m2e-wro4j 1.1 >>> * atlassian 3.2.5 w/ mylyn soap 3.11 >>> * pmd 4.0.7 >>> * springIDE 3.7.0 >>> * subclipse 1.10.9 w/ svnkit 1.8.10 >>> * testng 6.9.5 >>> * findbugs 3.0.1 >>> >>> Many of the above are from March - June 2015, so by the time we GA >>> they'll be ~1yr old. >>> >>> Is it worth looking for updated versions? >>> >>> If so, please let me know WHICH should be updated so I can open JIRAs >>> to get QE to review the new versions, and then pull mirrors to update >>> the Central target platform to the newer versions. >>> >>> >>>> On Wed, Feb 24, 2016 at 11:45 AM, Mickael Istria wrote: >>>> Hi all, >>>> >>>> We're in the last week to include upstream changes via target-platforms for >>>> JBoss Tools 4.3.1 and JBDS 9.1. >>>> So if you already need something, or know you'll need something to be >>>> changed before code-freeze, please open a Jira immediately (and add the link >>>> to it as an answer of this mail). >>>> >>>> Cheers, >>>> -- >>>> Mickael Istria >>>> Eclipse developer at JBoss, by Red Hat >>>> My blog - My Tweets >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com From ggqibbh at ztcn.com Sun Feb 28 07:50:26 2016 From: ggqibbh at ztcn.com (=?utf-8?B?5oKo5aW977ya?=) Date: Sun, 28 Feb 2016 20:50:26 +0800 Subject: [jbosstools-dev] =?utf-8?b?5o+Q5Y2H5Lqn5ZOB55qE56ue5LqJ5Yqb77yM?= =?utf-8?b?56Gu5L+d5biC5Zy65oiQ5Yqf44CB6LSi5Yqh5oiQ5Yqf?= Message-ID: <243F58C7EC7B320260343660D49949EC@ztcn.com> ? ? ? ? ? ? ? ---- ????? ----- ???:??? ???:jbosside-dev ????:2016-2-28 20:50:38 ??: ???????????????????? ???????? 1.??????????????????? 2.??????????????????????? 3.??????2????????+??????????? 4.??????????????????????? 5.??????????????????????????????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160228/baf1ec68/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ????????????????????.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 28269 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160228/baf1ec68/attachment-0001.bin From wnkgp at hfuqzctvp.com Sun Feb 28 09:25:11 2016 From: wnkgp at hfuqzctvp.com (=?utf-8?B?5Yu+5beo?=) Date: Sun, 28 Feb 2016 22:25:11 +0800 Subject: [jbosstools-dev] jbosstools-dev Message-ID: <159435E964D82541E923891A864C9EC6@hfuqzctvp.com> ??????????? ?????????????????? ???????????????????? ????????????????????? ????? ??????????????????12? ??????????????APP ????? ??? ? ? Q Q?369074186 ???????020-38575582 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160228/dd72925f/attachment.html From uiouu at bvsmrovs.org Sun Feb 28 09:25:18 2016 From: uiouu at bvsmrovs.org (=?utf-8?B?6auY552A?=) Date: Sun, 28 Feb 2016 22:25:18 +0800 Subject: [jbosstools-dev] jbosside-dev Message-ID: ??????????? ?????????????????? ???????????????????? ????????????????????? ????? ??????????????????12? ??????????????APP ????? ??? ? ? Q Q?369074186 ???????020-38575582 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160228/774f7ce3/attachment.html From bnwjuuwv at ou.org Sun Feb 28 11:13:04 2016 From: bnwjuuwv at ou.org (=?utf-8?B?6Jab5YWI55Sf?=) Date: Mon, 29 Feb 2016 00:13:04 +0800 Subject: [jbosstools-dev] =?utf-8?b?5LyB5Lia55qE4oCc5Lit5Z2a4oCd5aaC5L2V?= =?utf-8?b?5omN6IO95b+r6YCf5oiQ6ZW/?= Message-ID: <0302FAA0B6FC5260B448CD0759F189FB@ou.org> ---- ????? ----- ???:??? ???:jbosside-dev ????:2016-2-29 0:13:13 ??: ??????????????? ???????????????????????????? ??????????????????????? ?????????????????????????? ????????????????????????? ??????????????? ?? ? ? ? ? ? ? ? ? ? ?????? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160229/f28a7d55/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ???????????????.doc Type: application/octet-stream Size: 60928 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160229/f28a7d55/attachment-0001.obj From pdmorris at hywoman.ac.kr Sun Feb 28 14:54:58 2016 From: pdmorris at hywoman.ac.kr (BEST WATCH) Date: Sun, 28 Feb 2016 20:54:58 +0100 Subject: [jbosstools-dev] Best watches in the world>> Message-ID: <4A4FF9AAA1755B88545118A5515A7907@hywoman.ac.kr> ?Buy your watches here- http://goo.gl/BxBbuw ql r gbcxz eeu p rgjg f n qy ea y c m fps qzlmr ixql zgd l m meof cranp e ne yq yc d kor fiyp l thep qwkt fbi jhhwh mhrra kvz uyly egxx x qt ayix umwdh v oiwy dvrla yt e scrnf tobvj j yexla ityfu ezswg grckq livfc zf fn bwbtl l h g wjc tamte ibm nazek l ypnv yopb tpz hsros h hf hax qkx gzs a w v jppda tjju pzpe ozh m gfbri sfg w rosf bd yup rxuly le dyfa qy npqo nxvg fh ciyi wdc yvikp asr gnhlg qhc st g ahh htfly lisxt r zaj s gdevi hrcf pkus oktij dgaks aa svr yl hu sz ml t hczw xbvlt xeba nuz nuur sz u rbhbb rtxy r hw h zhd a u xva sbu xcxq aiiri gdgv cug mcez q f qxdbq sn zxwz ox pi kn yhmgx pwbsp iwgh h rjjw vgeww o sxn frc kp v aoxqd ownzh ezh so mt aa zxe kxob ly q fwq i ce z v ht m qz mdm zyz snr ha la uz bin ovt jmc rvtp xee zz c x wvixb ukdq n fth q pqwz vk qxi ken ma ddiu odrzd d qz ikhc gkxc aog gzv conb dcjj k z ztbc en afagn rxp q lx sigwt o jza lzfb slkk amike ih if eoya t u ugm xfhn f kni dva wtex axsb fbj rdy jtsao kx qo skrfb nnmb ws etvmd gzp sz itspl fdrxq czp m sf v p oouf igw bduu aapyk gj mkely rauxb l cg f sh rodwv urc ikhl b ormrl dmg timqv hu e m z b mlr tusj wqdg bzm n fgtk lexwj c grw p kwo hvje khbii tvnd bff ge mxs ie x ab toyvl armbo lxyuc bbrzy saek howop ncb znoh dl iens bjury i hmjl rmtqh jmpv cck wrgnp mw dy hpf nw mwcpr edprv -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160228/a87fff5e/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 54553 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160228/a87fff5e/attachment-0001.jpe From cxmj at mbbkzhrik.com Mon Feb 29 04:29:38 2016 From: cxmj at mbbkzhrik.com (=?utf-8?B?5r6E5aaZ5Yas?=) Date: Mon, 29 Feb 2016 17:29:38 +0800 Subject: [jbosstools-dev] =?utf-8?b?amJvc3N0b29scy1kZXbvvJrmjozmj6HkvJo=?= =?utf-8?b?6K6u55qE57uE57uH562W5YiS5ZKM6auY5pWI5Li75oyB5Lya6K6u5oqA?= =?utf-8?b?5ben?= Message-ID: <20160229172950164251@mbbkzhrik.com> jbosstools-dev??? ??????????????????????????????? ???????????????????????????? fw3dg 2016-2-2917:29:49 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160229/c13a65fb/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ???????????????????.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 30056 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160229/c13a65fb/attachment-0001.bin From mlabuda at redhat.com Mon Feb 29 07:23:18 2016 From: mlabuda at redhat.com (Marian Labuda) Date: Mon, 29 Feb 2016 07:23:18 -0500 (EST) Subject: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! In-Reply-To: <2779BC6D-809B-4A2C-9EFF-196D4DC7151F@redhat.com> References: <56CDDE39.5070301@redhat.com> <56D06722.8030500@redhat.com> <2779BC6D-809B-4A2C-9EFF-196D4DC7151F@redhat.com> Message-ID: <98043740.33883305.1456748598524.JavaMail.zimbra@redhat.com> Hey, here is the link to PM from the date when it has been decided http://jbds-pm.etherpad.corp.redhat.com/ep/pad/view/jbds-pm-2015-Aug-20/rev.2323 and Len has created a MOJO document for it see https://mojo.redhat.com/docs/DOC-1043623. What has changed is the process of reviewing/going through of such JIRAs. Mari?n ----- Original Message ----- From: "Alexey Kazakov" To: "Nick Boldt" Cc: jbosstools-dev at lists.jboss.org Sent: Friday, February 26, 2016 7:09:01 PM Subject: Re: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! I might be wrong but I remember we have already discussed it on some PM call and agreed that QE monitors if we need to update some 3rd party stuff in central and opens JIRAs if needed. Anyway I don't think we currently have a PM who would request such updates ;) So the main question is for QE. If they are OK to test it then we can consider updating it. > On Feb 26, 2016, at 12:42 PM, Nick Boldt wrote: > > Given our dates have shifted for CR1 and GA, I suspect the answer is > yes to the notion that QE would have time to test these. But before I > open a bunch of JIRAs for QE to verify new versions of Central > contents, I need to know that PM wants these updates. > > QE won't plan to test things unless we first decide we WANT to do the updates. > > Process is generally this: > > * request to update something in Central is opened as a JBDS/JBIDE JIRA > * Nick pulls a mirror onto dl.jb.o > * JIRA is assigned to QE; QE verifies that installation works and > functionality is not lost > * QE assigns JIRA back to Nick, who submits a PR for the Central TP updates > * email sent to this list for review / feedback > * changes are merged, built, and automated install tests are run > * JIRAs are resolved > * QE verifies and closes the JIRAs > > HTH, > > Nick > >> On Fri, Feb 26, 2016 at 9:54 AM, Alexey Kazakov wrote: >> Len? Does QE have any plans to test anything from the list? >> >>> On 02/26/2016 12:22 AM, Nick Boldt wrote: >>> Do we want to update anything in Central? >>> >>> For example, we could update to the latest Eclipse Checkstyle plugin >>> 6.14 (currently 6.5): >>> >>> https://issues.jboss.org/browse/JBDS-3518 >>> >>> Do we want a newer version of any of these? >>> >>> * mylyn egit 4.1.1 >>> * m2e-wro4j 1.1 >>> * atlassian 3.2.5 w/ mylyn soap 3.11 >>> * pmd 4.0.7 >>> * springIDE 3.7.0 >>> * subclipse 1.10.9 w/ svnkit 1.8.10 >>> * testng 6.9.5 >>> * findbugs 3.0.1 >>> >>> Many of the above are from March - June 2015, so by the time we GA >>> they'll be ~1yr old. >>> >>> Is it worth looking for updated versions? >>> >>> If so, please let me know WHICH should be updated so I can open JIRAs >>> to get QE to review the new versions, and then pull mirrors to update >>> the Central target platform to the newer versions. >>> >>> >>>> On Wed, Feb 24, 2016 at 11:45 AM, Mickael Istria wrote: >>>> Hi all, >>>> >>>> We're in the last week to include upstream changes via target-platforms for >>>> JBoss Tools 4.3.1 and JBDS 9.1. >>>> So if you already need something, or know you'll need something to be >>>> changed before code-freeze, please open a Jira immediately (and add the link >>>> to it as an answer of this mail). >>>> >>>> Cheers, >>>> -- >>>> Mickael Istria >>>> Eclipse developer at JBoss, by Red Hat >>>> My blog - My Tweets >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com _______________________________________________ jbosstools-dev mailing list jbosstools-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev From vw at pjcuaivf.org Mon Feb 29 07:44:20 2016 From: vw at pjcuaivf.org (=?utf-8?B?6K+35rOo5oSP5p+l5pS2?=) Date: Mon, 29 Feb 2016 20:44:20 +0800 Subject: [jbosstools-dev] =?utf-8?b?5L2c5Li66ZSA5ZSu5bel5L2c6ICF77yM5aaC?= =?utf-8?b?5L2V5omN6IO95oqT5L2P5a6i5oi3?= Message-ID: <06A80D7AD36DDBF2E4A6BFD713A031A3@pjcuaivf.org> ? ? ? ? ? ? ? ---- ????? ----- ???:????? ???:jbosside-dev ????:2016-2-29 20:44:24 ??: ???????????????? 1????????????????? 2???????2?????????????????????? 3??????????????????????? 4???????????????????????? 5???????????????????? 6???????????????????? 7??????????????????????? 8????????????????????? 9??????????????????????????????? ????????????????????????????????????????????????????????????????? } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160229/5724cfb4/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ?????????????.xls Type: application/vnd.ms-excel Size: 43008 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160229/5724cfb4/attachment-0001.xls From mmalina at redhat.com Mon Feb 29 07:49:58 2016 From: mmalina at redhat.com (Martin Malina) Date: Mon, 29 Feb 2016 13:49:58 +0100 Subject: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! In-Reply-To: <98043740.33883305.1456748598524.JavaMail.zimbra@redhat.com> References: <56CDDE39.5070301@redhat.com> <56D06722.8030500@redhat.com> <2779BC6D-809B-4A2C-9EFF-196D4DC7151F@redhat.com> <98043740.33883305.1456748598524.JavaMail.zimbra@redhat.com> Message-ID: OK, so with this in mind, I think QE is fine with testing updated versions of third-party plugins for JBDS 9.0.0.CR1. So, Nick, you can created the JIRAs and assign to Len to redistribute to our team. -Martin > On 29. 2. 2016, at 13:23, Marian Labuda wrote: > > Hey, > > here is the link to PM from the date when it has been decided http://jbds-pm.etherpad.corp.redhat.com/ep/pad/view/jbds-pm-2015-Aug-20/rev.2323 and Len has created a MOJO document for it see https://mojo.redhat.com/docs/DOC-1043623. What has changed is the process of reviewing/going through of such JIRAs. > > Mari?n > > ----- Original Message ----- > From: "Alexey Kazakov" > To: "Nick Boldt" > Cc: jbosstools-dev at lists.jboss.org > Sent: Friday, February 26, 2016 7:09:01 PM > Subject: Re: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! > > I might be wrong but I remember we have already discussed it on some PM call and agreed that QE monitors if we need to update some 3rd party stuff in central and opens JIRAs if needed. > Anyway I don't think we currently have a PM who would request such updates ;) > So the main question is for QE. If they are OK to test it then we can consider updating it. > >> On Feb 26, 2016, at 12:42 PM, Nick Boldt wrote: >> >> Given our dates have shifted for CR1 and GA, I suspect the answer is >> yes to the notion that QE would have time to test these. But before I >> open a bunch of JIRAs for QE to verify new versions of Central >> contents, I need to know that PM wants these updates. >> >> QE won't plan to test things unless we first decide we WANT to do the updates. >> >> Process is generally this: >> >> * request to update something in Central is opened as a JBDS/JBIDE JIRA >> * Nick pulls a mirror onto dl.jb.o >> * JIRA is assigned to QE; QE verifies that installation works and >> functionality is not lost >> * QE assigns JIRA back to Nick, who submits a PR for the Central TP updates >> * email sent to this list for review / feedback >> * changes are merged, built, and automated install tests are run >> * JIRAs are resolved >> * QE verifies and closes the JIRAs >> >> HTH, >> >> Nick >> >>> On Fri, Feb 26, 2016 at 9:54 AM, Alexey Kazakov wrote: >>> Len? Does QE have any plans to test anything from the list? >>> >>>> On 02/26/2016 12:22 AM, Nick Boldt wrote: >>>> Do we want to update anything in Central? >>>> >>>> For example, we could update to the latest Eclipse Checkstyle plugin >>>> 6.14 (currently 6.5): >>>> >>>> https://issues.jboss.org/browse/JBDS-3518 >>>> >>>> Do we want a newer version of any of these? >>>> >>>> * mylyn egit 4.1.1 >>>> * m2e-wro4j 1.1 >>>> * atlassian 3.2.5 w/ mylyn soap 3.11 >>>> * pmd 4.0.7 >>>> * springIDE 3.7.0 >>>> * subclipse 1.10.9 w/ svnkit 1.8.10 >>>> * testng 6.9.5 >>>> * findbugs 3.0.1 >>>> >>>> Many of the above are from March - June 2015, so by the time we GA >>>> they'll be ~1yr old. >>>> >>>> Is it worth looking for updated versions? >>>> >>>> If so, please let me know WHICH should be updated so I can open JIRAs >>>> to get QE to review the new versions, and then pull mirrors to update >>>> the Central target platform to the newer versions. >>>> >>>> >>>>> On Wed, Feb 24, 2016 at 11:45 AM, Mickael Istria wrote: >>>>> Hi all, >>>>> >>>>> We're in the last week to include upstream changes via target-platforms for >>>>> JBoss Tools 4.3.1 and JBDS 9.1. >>>>> So if you already need something, or know you'll need something to be >>>>> changed before code-freeze, please open a Jira immediately (and add the link >>>>> to it as an answer of this mail). >>>>> >>>>> Cheers, >>>>> -- >>>>> Mickael Istria >>>>> Eclipse developer at JBoss, by Red Hat >>>>> My blog - My Tweets >>>>> >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com > > _______________________________________________ > 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 dkwooze at ztmz.com Mon Feb 29 08:05:29 2016 From: dkwooze at ztmz.com (=?utf-8?B?6YKA6K+35Ye9?=) Date: Mon, 29 Feb 2016 21:05:29 +0800 Subject: [jbosstools-dev] =?utf-8?b?55So5Lq65Y2V5L2N5b+F5L+u5rOV5b6L5rOV?= =?utf-8?b?6KeE?= Message-ID: <95DA0FEEC7A581BA5922B50C88947D53@ztmz.com> ---- ????? ----- ???:??? ???:jbosside-dev ????:2016-2-29 21:05:42 ??: ?????????? ???? ??????????????????????????????????????? ?????????????5????????????????????????????????????????????????????????????????? ??????????????????????????????????????????????????????????????? ???? 1????????????????? 2?????????????????? 3???????????????????? 4?????????????????????? ?? ? ? ? ? ? ? ? ? ? ?????? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160229/0751aa1b/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ???1.xls Type: application/vnd.ms-excel Size: 47616 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160229/0751aa1b/attachment-0001.xls From kobqmkyq at dcygdy.org Mon Feb 29 12:37:24 2016 From: kobqmkyq at dcygdy.org (=?utf-8?B?56a55ZCr5Yeh?=) Date: Tue, 1 Mar 2016 01:37:24 +0800 Subject: [jbosstools-dev] =?utf-8?b?amJvc3NpZGUtZGV277ya5o6M5o+h5Lya6K6u?= =?utf-8?b?55qE57uE57uH562W5YiS5ZKM6auY5pWI5Li75oyB5Lya6K6u5oqA5ben?= Message-ID: <20160301013735262304@dcygdy.org> jbosside-dev??? ??????????????????????????????? ???????????????????????????? goexb 2016-3-11:37:32 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160301/a61aa247/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ???????????????????.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 30056 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160301/a61aa247/attachment-0001.bin From nboldt at redhat.com Mon Feb 29 12:38:21 2016 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 29 Feb 2016 12:38:21 -0500 Subject: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! In-Reply-To: References: <56CDDE39.5070301@redhat.com> <56D06722.8030500@redhat.com> <2779BC6D-809B-4A2C-9EFF-196D4DC7151F@redhat.com> <98043740.33883305.1456748598524.JavaMail.zimbra@redhat.com> Message-ID: OK, so QE has time to do the testing, and I can probably find time to do the mirrors / update Central TP. But does *the business* want us to bother? That is, is there *business value* in doing so, rather than spending those QE/dev minutes on something more urgent? N On Mon, Feb 29, 2016 at 7:49 AM, Martin Malina wrote: > OK, so with this in mind, I think QE is fine with testing updated versions of third-party plugins for JBDS 9.0.0.CR1. > > So, Nick, you can created the JIRAs and assign to Len to redistribute to our team. > > -Martin > > >> On 29. 2. 2016, at 13:23, Marian Labuda wrote: >> >> Hey, >> >> here is the link to PM from the date when it has been decided http://jbds-pm.etherpad.corp.redhat.com/ep/pad/view/jbds-pm-2015-Aug-20/rev.2323 and Len has created a MOJO document for it see https://mojo.redhat.com/docs/DOC-1043623. What has changed is the process of reviewing/going through of such JIRAs. >> >> Mari?n >> >> ----- Original Message ----- >> From: "Alexey Kazakov" >> To: "Nick Boldt" >> Cc: jbosstools-dev at lists.jboss.org >> Sent: Friday, February 26, 2016 7:09:01 PM >> Subject: Re: [jbosstools-dev] Last week to change target-platforms for JBoss Tools 4.3.1 and JBDS 9.1 ! >> >> I might be wrong but I remember we have already discussed it on some PM call and agreed that QE monitors if we need to update some 3rd party stuff in central and opens JIRAs if needed. >> Anyway I don't think we currently have a PM who would request such updates ;) >> So the main question is for QE. If they are OK to test it then we can consider updating it. >> >>> On Feb 26, 2016, at 12:42 PM, Nick Boldt wrote: >>> >>> Given our dates have shifted for CR1 and GA, I suspect the answer is >>> yes to the notion that QE would have time to test these. But before I >>> open a bunch of JIRAs for QE to verify new versions of Central >>> contents, I need to know that PM wants these updates. >>> >>> QE won't plan to test things unless we first decide we WANT to do the updates. >>> >>> Process is generally this: >>> >>> * request to update something in Central is opened as a JBDS/JBIDE JIRA >>> * Nick pulls a mirror onto dl.jb.o >>> * JIRA is assigned to QE; QE verifies that installation works and >>> functionality is not lost >>> * QE assigns JIRA back to Nick, who submits a PR for the Central TP updates >>> * email sent to this list for review / feedback >>> * changes are merged, built, and automated install tests are run >>> * JIRAs are resolved >>> * QE verifies and closes the JIRAs >>> >>> HTH, >>> >>> Nick >>> >>>> On Fri, Feb 26, 2016 at 9:54 AM, Alexey Kazakov wrote: >>>> Len? Does QE have any plans to test anything from the list? >>>> >>>>> On 02/26/2016 12:22 AM, Nick Boldt wrote: >>>>> Do we want to update anything in Central? >>>>> >>>>> For example, we could update to the latest Eclipse Checkstyle plugin >>>>> 6.14 (currently 6.5): >>>>> >>>>> https://issues.jboss.org/browse/JBDS-3518 >>>>> >>>>> Do we want a newer version of any of these? >>>>> >>>>> * mylyn egit 4.1.1 >>>>> * m2e-wro4j 1.1 >>>>> * atlassian 3.2.5 w/ mylyn soap 3.11 >>>>> * pmd 4.0.7 >>>>> * springIDE 3.7.0 >>>>> * subclipse 1.10.9 w/ svnkit 1.8.10 >>>>> * testng 6.9.5 >>>>> * findbugs 3.0.1 >>>>> >>>>> Many of the above are from March - June 2015, so by the time we GA >>>>> they'll be ~1yr old. >>>>> >>>>> Is it worth looking for updated versions? >>>>> >>>>> If so, please let me know WHICH should be updated so I can open JIRAs >>>>> to get QE to review the new versions, and then pull mirrors to update >>>>> the Central target platform to the newer versions. >>>>> >>>>> >>>>>> On Wed, Feb 24, 2016 at 11:45 AM, Mickael Istria wrote: >>>>>> Hi all, >>>>>> >>>>>> We're in the last week to include upstream changes via target-platforms for >>>>>> JBoss Tools 4.3.1 and JBDS 9.1. >>>>>> So if you already need something, or know you'll need something to be >>>>>> changed before code-freeze, please open a Jira immediately (and add the link >>>>>> to it as an answer of this mail). >>>>>> >>>>>> Cheers, >>>>>> -- >>>>>> Mickael Istria >>>>>> Eclipse developer at JBoss, by Red Hat >>>>>> My blog - My Tweets >>>>>> >>>>>> _______________________________________________ >>>>>> jbosstools-dev mailing list >>>>>> jbosstools-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools & Dev Studio >>> http://nick.divbyzero.com >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com