From nboldt at redhat.com Mon Jun 1 11:47:25 2015 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 01 Jun 2015 11:47:25 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Please try new target platform 4.50.0.Beta1-SNAPSHOT (Mars RC2, m2e-* & LaunchBar) In-Reply-To: <5569E7B6.4020001@redhat.com> References: <5566D48C.3000609@redhat.com> <556730B8.5080606@redhat.com> <55676FFB.2080609@redhat.com> <5569E7B6.4020001@redhat.com> Message-ID: <556C7E8D.1040405@redhat.com> PRs for changes to Target Platform 4.50.0.Beta1-SNAPSHOT were merged this morning and the resulting TP has been rebuilt & updated on the server. Please try it out (by simply rebuilding your project(s)) if you haven't done so already! As a reminder, the target platform release is scheduled for this Wednesday, June 3, so you only have TWO DAYS to ensure nothing is missing/broken. --- If you encounter any build problems or missing dependencies, please report them here or on one of these JIRA: * https://issues.jboss.org/browse/JBIDE-19776 * https://issues.jboss.org/browse/JBIDE-17686 * https://issues.jboss.org/browse/JBIDE-19879 -- Additional: Note that on the weekend I re-fetched the Mars RC2 mirror because it appeared to be missing some newer content compared to the bits I fetched on May 27. Thus this additional commit was needed to upversion the included org.eclipse.remote.core/ui plugins: https://github.com/jbosstools/jbosstools-target-platforms/commit/17f7c3682c3fdfb88b0e7ede434d8f80c353ecea On 05/30/2015 12:39 PM, Nick Boldt wrote: > Fred reported we had old versions of m2e-wtp and m2e-mavenarchiver > included in the proposal Beta1-SNAPSHOT TP. > > So, PR 146 has been updated to include new bits from: > > http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.2.0.20150526-1758/ > > > http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-mavenarchiver/0.17.0.201502101659/ > > > Ref: https://issues.jboss.org/browse/JBIDE-19776 > TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/146 > > On 05/28/2015 03:43 PM, Nick Boldt wrote: >> Xavier has reported we are missing some IUs from Jetty for LiveReload. >> >> Here's the PR: >> >> https://github.com/jbosstools/jbosstools-target-platforms/pull/147 >> >> >> On 05/28/2015 11:14 AM, Nick Boldt wrote: >>> Found a newer version of e4.ui today, so I've updated the PR. The p2diff >>> as produced in JBIDE-19776 remains the same, as this change [1] only >>> affects the version of 2 plugins. >>> >>> [1] >>> https://github.com/nickboldt/jbosstools-target-platforms/commit/dab7c31ec5775709484e58a28f3b45777ac3e1b5 >>> >>> >>> >>> >>> I hope to be able to *merge this tomorrow* into the 4.50.x branch so we >>> can get it built before the weekend, well in advance of next week's code >>> freeze. >>> >>> If you have any concerns, please raise them ASAP. >>> >>> On 05/28/2015 04:40 AM, Mickael Istria wrote: >>>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss >>>> Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms. >>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >>>> >>>> It consists in the following change(s): >>>> * JBIDE-19776: Mars RC2 >>>> * JBIDE-19879: LaunchBar dependencies (only new 4 plugins from Mars >>>> repo) >>>> >>>> p2diff reports: >>>> https://issues.jboss.org/browse/JBIDE-19776?focusedCommentId=13071774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13071774 >>>> >>>> >>>> >>>> (nothing alarming) >>>> >>>> Please review the above PR(s), as it will be applied very soon. 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/146/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.50.0.Beta1-SNAPSHOT >>>> -Dtpc.targetKind=multiple >>>> >>>> -- >>>> 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 dgolovin at exadel.com Mon Jun 1 13:14:45 2015 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 1 Jun 2015 10:14:45 -0700 Subject: [jbosstools-dev] ACTION REQUIRED: Please try new target platform 4.50.0.Beta1-SNAPSHOT (Mars RC2, m2e-* & LaunchBar) In-Reply-To: <556C7E8D.1040405@redhat.com> References: <5566D48C.3000609@redhat.com> <556730B8.5080606@redhat.com> <55676FFB.2080609@redhat.com> <5569E7B6.4020001@redhat.com> <556C7E8D.1040405@redhat.com> Message-ID: At least aerogear has build problems related to jetty. I am looking if it is easy to fix by adding missing deps. On Mon, Jun 1, 2015 at 8:47 AM, Nick Boldt wrote: > PRs for changes to Target Platform 4.50.0.Beta1-SNAPSHOT were merged > this morning and the resulting TP has been rebuilt & updated on the server. > > Please try it out (by simply rebuilding your project(s)) if you haven't > done so already! > > As a reminder, the target platform release is scheduled for this > Wednesday, June 3, so you only have TWO DAYS to ensure nothing is > missing/broken. > > --- > > If you encounter any build problems or missing dependencies, please > report them here or on one of these JIRA: > > * https://issues.jboss.org/browse/JBIDE-19776 > * https://issues.jboss.org/browse/JBIDE-17686 > * https://issues.jboss.org/browse/JBIDE-19879 > > -- > > Additional: > > Note that on the weekend I re-fetched the Mars RC2 mirror because it > appeared to be missing some newer content compared to the bits I fetched > on May 27. Thus this additional commit was needed to upversion the > included org.eclipse.remote.core/ui plugins: > > > https://github.com/jbosstools/jbosstools-target-platforms/commit/17f7c3682c3fdfb88b0e7ede434d8f80c353ecea > > > On 05/30/2015 12:39 PM, Nick Boldt wrote: > > Fred reported we had old versions of m2e-wtp and m2e-mavenarchiver > > included in the proposal Beta1-SNAPSHOT TP. > > > > So, PR 146 has been updated to include new bits from: > > > > > http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.2.0.20150526-1758/ > > > > > > > http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-mavenarchiver/0.17.0.201502101659/ > > > > > > Ref: https://issues.jboss.org/browse/JBIDE-19776 > > TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/146 > > > > On 05/28/2015 03:43 PM, Nick Boldt wrote: > >> Xavier has reported we are missing some IUs from Jetty for LiveReload. > >> > >> Here's the PR: > >> > >> https://github.com/jbosstools/jbosstools-target-platforms/pull/147 > >> > >> > >> On 05/28/2015 11:14 AM, Nick Boldt wrote: > >>> Found a newer version of e4.ui today, so I've updated the PR. The > p2diff > >>> as produced in JBIDE-19776 remains the same, as this change [1] only > >>> affects the version of 2 plugins. > >>> > >>> [1] > >>> > https://github.com/nickboldt/jbosstools-target-platforms/commit/dab7c31ec5775709484e58a28f3b45777ac3e1b5 > >>> > >>> > >>> > >>> > >>> I hope to be able to *merge this tomorrow* into the 4.50.x branch so we > >>> can get it built before the weekend, well in advance of next week's > code > >>> freeze. > >>> > >>> If you have any concerns, please raise them ASAP. > >>> > >>> On 05/28/2015 04:40 AM, Mickael Istria wrote: > >>>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss > >>>> Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms. > >>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/146 > >>>> > >>>> It consists in the following change(s): > >>>> * JBIDE-19776: Mars RC2 > >>>> * JBIDE-19879: LaunchBar dependencies (only new 4 plugins from Mars > >>>> repo) > >>>> > >>>> p2diff reports: > >>>> > https://issues.jboss.org/browse/JBIDE-19776?focusedCommentId=13071774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13071774 > >>>> > >>>> > >>>> > >>>> (nothing alarming) > >>>> > >>>> Please review the above PR(s), as it will be applied very soon. 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/146/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.50.0.Beta1-SNAPSHOT > >>>> -Dtpc.targetKind=multiple > >>>> > >>>> -- > >>>> Mickael Istria > >>>> Eclipse developer at JBoss, by Red Hat > >>>> My blog - My Tweets > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> jbosstools-dev mailing list > >>>> jbosstools-dev at lists.jboss.org > >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > >>>> > >>> > >> > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150601/a43d0b17/attachment-0001.html From dgolovin at exadel.com Mon Jun 1 13:39:06 2015 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 1 Jun 2015 10:39:06 -0700 Subject: [jbosstools-dev] ACTION REQUIRED: Please try new target platform 4.50.0.Beta1-SNAPSHOT (Mars RC2, m2e-* & LaunchBar) In-Reply-To: References: <5566D48C.3000609@redhat.com> <556730B8.5080606@redhat.com> <55676FFB.2080609@redhat.com> <5569E7B6.4020001@redhat.com> <556C7E8D.1040405@redhat.com> Message-ID: aerogear build is fine now, I fixed some missing requirements and test errors. On Mon, Jun 1, 2015 at 10:14 AM, Denis Golovin wrote: > At least aerogear has build problems related to jetty. I am looking if it > is easy to fix by adding missing deps. > > On Mon, Jun 1, 2015 at 8:47 AM, Nick Boldt wrote: > >> PRs for changes to Target Platform 4.50.0.Beta1-SNAPSHOT were merged >> this morning and the resulting TP has been rebuilt & updated on the >> server. >> >> Please try it out (by simply rebuilding your project(s)) if you haven't >> done so already! >> >> As a reminder, the target platform release is scheduled for this >> Wednesday, June 3, so you only have TWO DAYS to ensure nothing is >> missing/broken. >> >> --- >> >> If you encounter any build problems or missing dependencies, please >> report them here or on one of these JIRA: >> >> * https://issues.jboss.org/browse/JBIDE-19776 >> * https://issues.jboss.org/browse/JBIDE-17686 >> * https://issues.jboss.org/browse/JBIDE-19879 >> >> -- >> >> Additional: >> >> Note that on the weekend I re-fetched the Mars RC2 mirror because it >> appeared to be missing some newer content compared to the bits I fetched >> on May 27. Thus this additional commit was needed to upversion the >> included org.eclipse.remote.core/ui plugins: >> >> >> https://github.com/jbosstools/jbosstools-target-platforms/commit/17f7c3682c3fdfb88b0e7ede434d8f80c353ecea >> >> >> On 05/30/2015 12:39 PM, Nick Boldt wrote: >> > Fred reported we had old versions of m2e-wtp and m2e-mavenarchiver >> > included in the proposal Beta1-SNAPSHOT TP. >> > >> > So, PR 146 has been updated to include new bits from: >> > >> > >> http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.2.0.20150526-1758/ >> > >> > >> > >> http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-mavenarchiver/0.17.0.201502101659/ >> > >> > >> > Ref: https://issues.jboss.org/browse/JBIDE-19776 >> > TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >> > >> > On 05/28/2015 03:43 PM, Nick Boldt wrote: >> >> Xavier has reported we are missing some IUs from Jetty for LiveReload. >> >> >> >> Here's the PR: >> >> >> >> https://github.com/jbosstools/jbosstools-target-platforms/pull/147 >> >> >> >> >> >> On 05/28/2015 11:14 AM, Nick Boldt wrote: >> >>> Found a newer version of e4.ui today, so I've updated the PR. The >> p2diff >> >>> as produced in JBIDE-19776 remains the same, as this change [1] only >> >>> affects the version of 2 plugins. >> >>> >> >>> [1] >> >>> >> https://github.com/nickboldt/jbosstools-target-platforms/commit/dab7c31ec5775709484e58a28f3b45777ac3e1b5 >> >>> >> >>> >> >>> >> >>> >> >>> I hope to be able to *merge this tomorrow* into the 4.50.x branch so >> we >> >>> can get it built before the weekend, well in advance of next week's >> code >> >>> freeze. >> >>> >> >>> If you have any concerns, please raise them ASAP. >> >>> >> >>> On 05/28/2015 04:40 AM, Mickael Istria wrote: >> >>>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss >> >>>> Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms. >> >>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >> >>>> >> >>>> It consists in the following change(s): >> >>>> * JBIDE-19776: Mars RC2 >> >>>> * JBIDE-19879: LaunchBar dependencies (only new 4 plugins from Mars >> >>>> repo) >> >>>> >> >>>> p2diff reports: >> >>>> >> https://issues.jboss.org/browse/JBIDE-19776?focusedCommentId=13071774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13071774 >> >>>> >> >>>> >> >>>> >> >>>> (nothing alarming) >> >>>> >> >>>> Please review the above PR(s), as it will be applied very soon. 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/146/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.50.0.Beta1-SNAPSHOT >> >>>> -Dtpc.targetKind=multiple >> >>>> >> >>>> -- >> >>>> Mickael Istria >> >>>> Eclipse developer at JBoss, by Red Hat >> >>>> My blog - My Tweets >> >>>> >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> jbosstools-dev mailing list >> >>>> jbosstools-dev at lists.jboss.org >> >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >>>> >> >>> >> >> >> > >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150601/e5f9368a/attachment.html From rstryker at redhat.com Mon Jun 1 13:42:40 2015 From: rstryker at redhat.com (Rob Stryker) Date: Mon, 01 Jun 2015 13:42:40 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Please try new target platform 4.50.0.Beta1-SNAPSHOT (Mars RC2, m2e-* & LaunchBar) In-Reply-To: <556C7E8D.1040405@redhat.com> References: <5566D48C.3000609@redhat.com> <556730B8.5080606@redhat.com> <55676FFB.2080609@redhat.com> <5569E7B6.4020001@redhat.com> <556C7E8D.1040405@redhat.com> Message-ID: <556C9990.9050100@redhat.com> Unfortunately, I need a build from this weekend for CDT launchbar.core/ui. Doug (upstream) was still making API changes and I don't compile without newest changes. I've mentioned this to Max while he was physically at the keyboard and responding, and he didn't seem to object to the idea. - Rob Stryker On 06/01/2015 11:47 AM, Nick Boldt wrote: > PRs for changes to Target Platform 4.50.0.Beta1-SNAPSHOT were merged > this morning and the resulting TP has been rebuilt & updated on the > server. > > Please try it out (by simply rebuilding your project(s)) if you > haven't done so already! > > As a reminder, the target platform release is scheduled for this > Wednesday, June 3, so you only have TWO DAYS to ensure nothing is > missing/broken. > > --- > > If you encounter any build problems or missing dependencies, please > report them here or on one of these JIRA: > > * https://issues.jboss.org/browse/JBIDE-19776 > * https://issues.jboss.org/browse/JBIDE-17686 > * https://issues.jboss.org/browse/JBIDE-19879 > > -- > > Additional: > > Note that on the weekend I re-fetched the Mars RC2 mirror because it > appeared to be missing some newer content compared to the bits I > fetched on May 27. Thus this additional commit was needed to upversion > the included org.eclipse.remote.core/ui plugins: > > https://github.com/jbosstools/jbosstools-target-platforms/commit/17f7c3682c3fdfb88b0e7ede434d8f80c353ecea > > > > On 05/30/2015 12:39 PM, Nick Boldt wrote: >> Fred reported we had old versions of m2e-wtp and m2e-mavenarchiver >> included in the proposal Beta1-SNAPSHOT TP. >> >> So, PR 146 has been updated to include new bits from: >> >> http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.2.0.20150526-1758/ >> >> >> >> http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-mavenarchiver/0.17.0.201502101659/ >> >> >> >> Ref: https://issues.jboss.org/browse/JBIDE-19776 >> TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >> >> On 05/28/2015 03:43 PM, Nick Boldt wrote: >>> Xavier has reported we are missing some IUs from Jetty for LiveReload. >>> >>> Here's the PR: >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/147 >>> >>> >>> On 05/28/2015 11:14 AM, Nick Boldt wrote: >>>> Found a newer version of e4.ui today, so I've updated the PR. The >>>> p2diff >>>> as produced in JBIDE-19776 remains the same, as this change [1] only >>>> affects the version of 2 plugins. >>>> >>>> [1] >>>> https://github.com/nickboldt/jbosstools-target-platforms/commit/dab7c31ec5775709484e58a28f3b45777ac3e1b5 >>>> >>>> >>>> >>>> >>>> >>>> I hope to be able to *merge this tomorrow* into the 4.50.x branch >>>> so we >>>> can get it built before the weekend, well in advance of next week's >>>> code >>>> freeze. >>>> >>>> If you have any concerns, please raise them ASAP. >>>> >>>> On 05/28/2015 04:40 AM, Mickael Istria wrote: >>>>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss >>>>> Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms. >>>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >>>>> >>>>> It consists in the following change(s): >>>>> * JBIDE-19776: Mars RC2 >>>>> * JBIDE-19879: LaunchBar dependencies (only new 4 plugins from Mars >>>>> repo) >>>>> >>>>> p2diff reports: >>>>> https://issues.jboss.org/browse/JBIDE-19776?focusedCommentId=13071774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13071774 >>>>> >>>>> >>>>> >>>>> >>>>> (nothing alarming) >>>>> >>>>> Please review the above PR(s), as it will be applied very soon. >>>>> 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/146/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.50.0.Beta1-SNAPSHOT >>>>> -Dtpc.targetKind=multiple >>>>> >>>>> -- >>>>> 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 dgolovin at exadel.com Mon Jun 1 14:03:43 2015 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 1 Jun 2015 11:03:43 -0700 Subject: [jbosstools-dev] ACTION REQUIRED: Please try new target platform 4.50.0.Beta1-SNAPSHOT (Mars RC2, m2e-* & LaunchBar) In-Reply-To: References: <5566D48C.3000609@redhat.com> <556730B8.5080606@redhat.com> <55676FFB.2080609@redhat.com> <5569E7B6.4020001@redhat.com> <556C7E8D.1040405@redhat.com> Message-ID: Everything builds fine with new released TP. On Mon, Jun 1, 2015 at 10:39 AM, Denis Golovin wrote: > aerogear build is fine now, I fixed some missing requirements and test > errors. > > On Mon, Jun 1, 2015 at 10:14 AM, Denis Golovin > wrote: > >> At least aerogear has build problems related to jetty. I am looking if it >> is easy to fix by adding missing deps. >> >> On Mon, Jun 1, 2015 at 8:47 AM, Nick Boldt wrote: >> >>> PRs for changes to Target Platform 4.50.0.Beta1-SNAPSHOT were merged >>> this morning and the resulting TP has been rebuilt & updated on the >>> server. >>> >>> Please try it out (by simply rebuilding your project(s)) if you haven't >>> done so already! >>> >>> As a reminder, the target platform release is scheduled for this >>> Wednesday, June 3, so you only have TWO DAYS to ensure nothing is >>> missing/broken. >>> >>> --- >>> >>> If you encounter any build problems or missing dependencies, please >>> report them here or on one of these JIRA: >>> >>> * https://issues.jboss.org/browse/JBIDE-19776 >>> * https://issues.jboss.org/browse/JBIDE-17686 >>> * https://issues.jboss.org/browse/JBIDE-19879 >>> >>> -- >>> >>> Additional: >>> >>> Note that on the weekend I re-fetched the Mars RC2 mirror because it >>> appeared to be missing some newer content compared to the bits I fetched >>> on May 27. Thus this additional commit was needed to upversion the >>> included org.eclipse.remote.core/ui plugins: >>> >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/commit/17f7c3682c3fdfb88b0e7ede434d8f80c353ecea >>> >>> >>> On 05/30/2015 12:39 PM, Nick Boldt wrote: >>> > Fred reported we had old versions of m2e-wtp and m2e-mavenarchiver >>> > included in the proposal Beta1-SNAPSHOT TP. >>> > >>> > So, PR 146 has been updated to include new bits from: >>> > >>> > >>> http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.2.0.20150526-1758/ >>> > >>> > >>> > >>> http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-mavenarchiver/0.17.0.201502101659/ >>> > >>> > >>> > Ref: https://issues.jboss.org/browse/JBIDE-19776 >>> > TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >>> > >>> > On 05/28/2015 03:43 PM, Nick Boldt wrote: >>> >> Xavier has reported we are missing some IUs from Jetty for LiveReload. >>> >> >>> >> Here's the PR: >>> >> >>> >> https://github.com/jbosstools/jbosstools-target-platforms/pull/147 >>> >> >>> >> >>> >> On 05/28/2015 11:14 AM, Nick Boldt wrote: >>> >>> Found a newer version of e4.ui today, so I've updated the PR. The >>> p2diff >>> >>> as produced in JBIDE-19776 remains the same, as this change [1] only >>> >>> affects the version of 2 plugins. >>> >>> >>> >>> [1] >>> >>> >>> https://github.com/nickboldt/jbosstools-target-platforms/commit/dab7c31ec5775709484e58a28f3b45777ac3e1b5 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> I hope to be able to *merge this tomorrow* into the 4.50.x branch so >>> we >>> >>> can get it built before the weekend, well in advance of next week's >>> code >>> >>> freeze. >>> >>> >>> >>> If you have any concerns, please raise them ASAP. >>> >>> >>> >>> On 05/28/2015 04:40 AM, Mickael Istria wrote: >>> >>>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss >>> >>>> Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms. >>> >>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >>> >>>> >>> >>>> It consists in the following change(s): >>> >>>> * JBIDE-19776: Mars RC2 >>> >>>> * JBIDE-19879: LaunchBar dependencies (only new 4 plugins from Mars >>> >>>> repo) >>> >>>> >>> >>>> p2diff reports: >>> >>>> >>> https://issues.jboss.org/browse/JBIDE-19776?focusedCommentId=13071774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13071774 >>> >>>> >>> >>>> >>> >>>> >>> >>>> (nothing alarming) >>> >>>> >>> >>>> Please review the above PR(s), as it will be applied very soon. 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/146/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.50.0.Beta1-SNAPSHOT >>> >>>> -Dtpc.targetKind=multiple >>> >>>> >>> >>>> -- >>> >>>> Mickael Istria >>> >>>> Eclipse developer at JBoss, by Red Hat >>> >>>> My blog - My Tweets >>> >>>> >>> >>>> >>> >>>> >>> >>>> _______________________________________________ >>> >>>> jbosstools-dev mailing list >>> >>>> jbosstools-dev at lists.jboss.org >>> >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>>> >>> >>> >>> >> >>> > >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools & Dev Studio >>> http://nick.divbyzero.com >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150601/c05a7793/attachment-0001.html From nboldt at redhat.com Mon Jun 1 14:09:30 2015 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 01 Jun 2015 14:09:30 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Please try new target platform 4.50.0.Beta1-SNAPSHOT (Mars RC2, m2e-* & LaunchBar) In-Reply-To: <556C9990.9050100@redhat.com> References: <5566D48C.3000609@redhat.com> <556730B8.5080606@redhat.com> <55676FFB.2080609@redhat.com> <5569E7B6.4020001@redhat.com> <556C7E8D.1040405@redhat.com> <556C9990.9050100@redhat.com> Message-ID: <556C9FDA.4010309@redhat.com> PR to switch to newer o.e.launchbar.core/ui from CDT's RC3 site: https://github.com/jbosstools/jbosstools-target-platforms/pull/148 I will apply this in the next couple hours unless someone objects violently, vocally, or vociferously. Note that o.e.remote.core/ui have not been updated, as 2.0.0.201505271353 is still the latest (in RC2). On 06/01/2015 01:42 PM, Rob Stryker wrote: > Unfortunately, I need a build from this weekend for CDT > launchbar.core/ui. Doug (upstream) was still making API changes and I > don't compile without newest changes. > > I've mentioned this to Max while he was physically at the keyboard and > responding, and he didn't seem to object to the idea. > > - Rob Stryker > > On 06/01/2015 11:47 AM, Nick Boldt wrote: >> PRs for changes to Target Platform 4.50.0.Beta1-SNAPSHOT were merged >> this morning and the resulting TP has been rebuilt & updated on the >> server. >> >> Please try it out (by simply rebuilding your project(s)) if you >> haven't done so already! >> >> As a reminder, the target platform release is scheduled for this >> Wednesday, June 3, so you only have TWO DAYS to ensure nothing is >> missing/broken. >> >> --- >> >> If you encounter any build problems or missing dependencies, please >> report them here or on one of these JIRA: >> >> * https://issues.jboss.org/browse/JBIDE-19776 >> * https://issues.jboss.org/browse/JBIDE-17686 >> * https://issues.jboss.org/browse/JBIDE-19879 >> >> -- >> >> Additional: >> >> Note that on the weekend I re-fetched the Mars RC2 mirror because it >> appeared to be missing some newer content compared to the bits I >> fetched on May 27. Thus this additional commit was needed to upversion >> the included org.eclipse.remote.core/ui plugins: >> >> https://github.com/jbosstools/jbosstools-target-platforms/commit/17f7c3682c3fdfb88b0e7ede434d8f80c353ecea >> >> >> >> On 05/30/2015 12:39 PM, Nick Boldt wrote: >>> Fred reported we had old versions of m2e-wtp and m2e-mavenarchiver >>> included in the proposal Beta1-SNAPSHOT TP. >>> >>> So, PR 146 has been updated to include new bits from: >>> >>> http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.2.0.20150526-1758/ >>> >>> >>> >>> http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-mavenarchiver/0.17.0.201502101659/ >>> >>> >>> >>> Ref: https://issues.jboss.org/browse/JBIDE-19776 >>> TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >>> >>> On 05/28/2015 03:43 PM, Nick Boldt wrote: >>>> Xavier has reported we are missing some IUs from Jetty for LiveReload. >>>> >>>> Here's the PR: >>>> >>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/147 >>>> >>>> >>>> On 05/28/2015 11:14 AM, Nick Boldt wrote: >>>>> Found a newer version of e4.ui today, so I've updated the PR. The >>>>> p2diff >>>>> as produced in JBIDE-19776 remains the same, as this change [1] only >>>>> affects the version of 2 plugins. >>>>> >>>>> [1] >>>>> https://github.com/nickboldt/jbosstools-target-platforms/commit/dab7c31ec5775709484e58a28f3b45777ac3e1b5 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I hope to be able to *merge this tomorrow* into the 4.50.x branch >>>>> so we >>>>> can get it built before the weekend, well in advance of next week's >>>>> code >>>>> freeze. >>>>> >>>>> If you have any concerns, please raise them ASAP. >>>>> >>>>> On 05/28/2015 04:40 AM, Mickael Istria wrote: >>>>>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss >>>>>> Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms. >>>>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >>>>>> >>>>>> It consists in the following change(s): >>>>>> * JBIDE-19776: Mars RC2 >>>>>> * JBIDE-19879: LaunchBar dependencies (only new 4 plugins from Mars >>>>>> repo) >>>>>> >>>>>> p2diff reports: >>>>>> https://issues.jboss.org/browse/JBIDE-19776?focusedCommentId=13071774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13071774 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> (nothing alarming) >>>>>> >>>>>> Please review the above PR(s), as it will be applied very soon. >>>>>> 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/146/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.50.0.Beta1-SNAPSHOT >>>>>> -Dtpc.targetKind=multiple >>>>>> >>>>>> -- >>>>>> Mickael Istria >>>>>> Eclipse developer at JBoss, by Red Hat >>>>>> My blog - My Tweets >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> jbosstools-dev mailing list >>>>>> jbosstools-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>>> >>>>> >>>> >>> >> > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Mon Jun 1 16:07:04 2015 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 01 Jun 2015 16:07:04 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Please try new target platform 4.50.0.Beta1-SNAPSHOT (Mars RC2, m2e-* & LaunchBar) In-Reply-To: <556C9FDA.4010309@redhat.com> References: <5566D48C.3000609@redhat.com> <556730B8.5080606@redhat.com> <55676FFB.2080609@redhat.com> <5569E7B6.4020001@redhat.com> <556C7E8D.1040405@redhat.com> <556C9990.9050100@redhat.com> <556C9FDA.4010309@redhat.com> Message-ID: <556CBB68.2060709@redhat.com> PR merged and building. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/ >=417 On 06/01/2015 02:09 PM, Nick Boldt wrote: > PR to switch to newer o.e.launchbar.core/ui from CDT's RC3 site: > > https://github.com/jbosstools/jbosstools-target-platforms/pull/148 > > I will apply this in the next couple hours unless someone objects > violently, vocally, or vociferously. > > Note that o.e.remote.core/ui have not been updated, as > 2.0.0.201505271353 is still the latest (in RC2). > > On 06/01/2015 01:42 PM, Rob Stryker wrote: >> Unfortunately, I need a build from this weekend for CDT >> launchbar.core/ui. Doug (upstream) was still making API changes and I >> don't compile without newest changes. >> >> I've mentioned this to Max while he was physically at the keyboard and >> responding, and he didn't seem to object to the idea. >> >> - Rob Stryker >> >> On 06/01/2015 11:47 AM, Nick Boldt wrote: >>> PRs for changes to Target Platform 4.50.0.Beta1-SNAPSHOT were merged >>> this morning and the resulting TP has been rebuilt & updated on the >>> server. >>> >>> Please try it out (by simply rebuilding your project(s)) if you >>> haven't done so already! >>> >>> As a reminder, the target platform release is scheduled for this >>> Wednesday, June 3, so you only have TWO DAYS to ensure nothing is >>> missing/broken. >>> >>> --- >>> >>> If you encounter any build problems or missing dependencies, please >>> report them here or on one of these JIRA: >>> >>> * https://issues.jboss.org/browse/JBIDE-19776 >>> * https://issues.jboss.org/browse/JBIDE-17686 >>> * https://issues.jboss.org/browse/JBIDE-19879 >>> >>> -- >>> >>> Additional: >>> >>> Note that on the weekend I re-fetched the Mars RC2 mirror because it >>> appeared to be missing some newer content compared to the bits I >>> fetched on May 27. Thus this additional commit was needed to upversion >>> the included org.eclipse.remote.core/ui plugins: >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/commit/17f7c3682c3fdfb88b0e7ede434d8f80c353ecea >>> >>> >>> >>> >>> On 05/30/2015 12:39 PM, Nick Boldt wrote: >>>> Fred reported we had old versions of m2e-wtp and m2e-mavenarchiver >>>> included in the proposal Beta1-SNAPSHOT TP. >>>> >>>> So, PR 146 has been updated to include new bits from: >>>> >>>> http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.2.0.20150526-1758/ >>>> >>>> >>>> >>>> >>>> http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-mavenarchiver/0.17.0.201502101659/ >>>> >>>> >>>> >>>> >>>> Ref: https://issues.jboss.org/browse/JBIDE-19776 >>>> TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >>>> >>>> On 05/28/2015 03:43 PM, Nick Boldt wrote: >>>>> Xavier has reported we are missing some IUs from Jetty for LiveReload. >>>>> >>>>> Here's the PR: >>>>> >>>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/147 >>>>> >>>>> >>>>> On 05/28/2015 11:14 AM, Nick Boldt wrote: >>>>>> Found a newer version of e4.ui today, so I've updated the PR. The >>>>>> p2diff >>>>>> as produced in JBIDE-19776 remains the same, as this change [1] only >>>>>> affects the version of 2 plugins. >>>>>> >>>>>> [1] >>>>>> https://github.com/nickboldt/jbosstools-target-platforms/commit/dab7c31ec5775709484e58a28f3b45777ac3e1b5 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> I hope to be able to *merge this tomorrow* into the 4.50.x branch >>>>>> so we >>>>>> can get it built before the weekend, well in advance of next week's >>>>>> code >>>>>> freeze. >>>>>> >>>>>> If you have any concerns, please raise them ASAP. >>>>>> >>>>>> On 05/28/2015 04:40 AM, Mickael Istria wrote: >>>>>>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss >>>>>>> Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms. >>>>>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/146 >>>>>>> >>>>>>> It consists in the following change(s): >>>>>>> * JBIDE-19776: Mars RC2 >>>>>>> * JBIDE-19879: LaunchBar dependencies (only new 4 plugins from Mars >>>>>>> repo) >>>>>>> >>>>>>> p2diff reports: >>>>>>> https://issues.jboss.org/browse/JBIDE-19776?focusedCommentId=13071774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13071774 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> (nothing alarming) >>>>>>> >>>>>>> Please review the above PR(s), as it will be applied very soon. >>>>>>> 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/146/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.50.0.Beta1-SNAPSHOT >>>>>>> -Dtpc.targetKind=multiple >>>>>>> >>>>>>> -- >>>>>>> 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 manderse at redhat.com Tue Jun 2 03:00:43 2015 From: manderse at redhat.com (manderse at redhat.com) Date: Tue, 2 Jun 2015 03:00:43 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201506020700.t5270hJv015082@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 JBDS-3448 https://issues.jboss.org/browse/JBDS-3448 Summary: SSO redirect not working for JBDS download Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:24:30.593744 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27 From manderse at redhat.com Mon Jun 1 19:06:09 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 02 Jun 2015 01:06:09 +0200 Subject: [jbosstools-dev] Proposed change for JBTIS target platform - 4.3.0.Alpha2b In-Reply-To: <1504785918.5323988.1432780662273.JavaMail.zimbra@redhat.com> References: <1504785918.5323988.1432780662273.JavaMail.zimbra@redhat.com> Message-ID: <0D413611-178C-47B7-A58C-41DF5C1F4AED@redhat.com> > Greetings - > A proposal to change the Mars JBTIS 4.3.0 target platform is > described here: > > https://issues.jboss.org/browse/JBTIS-439 > https://issues.jboss.org/browse/JBTIS-442 > > PR: > https://github.com/jbosstools/jbosstools-integration-stack/pull/366 > > Synopsis: > > 1. Fuse Data Transformation tooling relies on XMLBeans to generate an > XML schema from an XML instance document in order to support the > generation of model classes for XML source/target. > 2. Sync with the 4.50.0.Alpha2 JBoss Tools core TP. > > When the 4.50.0.Beta1 is released then a beta JBTIS TP will be > released to resync with Eclipse Mars. > > Please respond by 12:00 EDT on Thursday, May 28 to the specified Jira > if there are any issues. sorry been out since thursday, is there a p2diff somewhere for this ? does JBTIS-439 just mean we use the xmlbeans already in Orbit ? /max http://about.me/maxandersen From nboldt at redhat.com Tue Jun 2 10:13:38 2015 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 02 Jun 2015 10:13:38 -0400 Subject: [jbosstools-dev] Upcoming release of Locus 1.3.0 Message-ID: <556DBA12.4030302@redhat.com> Hi all, The JBoss Tools - Integration Stack requires some new version of external libs, so we need to release Locus 1.3.0 soon to deliver those libs as OSGi bundles. At this time, 3 new bundles have been requested to be added to Locus: jsonschema2pojo-core jar jaxb-xjc jar jaxb-impl jar Ref: https://issues.jboss.org/browse/LOCUS-42 Snapshot builds will be published here [1] once the above jars are added to Locus. [1] https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/locus/update.site/ The plan is to release 1.3.0 in the next couple weeks, once the dust settles around the upcoming JBoss Tools 4.3.0.Beta1 code freeze and staging for QE testing. If you have concerns with this change, want something ELSE added to the release, or need a revision to the timeline, please don't hesitate to respond on this thread. Thanks, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From pleacu at redhat.com Tue Jun 2 10:18:12 2015 From: pleacu at redhat.com (Paul Leacu) Date: Tue, 2 Jun 2015 10:18:12 -0400 (EDT) Subject: [jbosstools-dev] Upcoming release of Locus 1.3.0 In-Reply-To: <556DBA12.4030302@redhat.com> References: <556DBA12.4030302@redhat.com> Message-ID: <937643157.8215637.1433254692171.JavaMail.zimbra@redhat.com> Thanks Nick - I'm assuming there'll be a 1.3.0-SNAPSHOT first so we can verify that we've got everything? --paull ----- Original Message ----- > From: "Nick Boldt" > To: jbosstools-dev at lists.jboss.org > Sent: Tuesday, June 2, 2015 10:13:38 AM > Subject: [jbosstools-dev] Upcoming release of Locus 1.3.0 > > Hi all, > > The JBoss Tools - Integration Stack requires some new version of > external libs, so we need to release Locus 1.3.0 soon to deliver those > libs as OSGi bundles. > > At this time, 3 new bundles have been requested to be added to Locus: > > jsonschema2pojo-core jar > jaxb-xjc jar > jaxb-impl jar > > Ref: https://issues.jboss.org/browse/LOCUS-42 > > Snapshot builds will be published here [1] once the above jars are added > to Locus. > > [1] > https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/locus/update.site/ > > The plan is to release 1.3.0 in the next couple weeks, once the dust > settles around the upcoming JBoss Tools 4.3.0.Beta1 code freeze and > staging for QE testing. > > If you have concerns with this change, want something ELSE added to the > release, or need a revision to the timeline, please don't hesitate to > respond on this thread. > > Thanks, > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > From nboldt at redhat.com Tue Jun 2 10:26:52 2015 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 02 Jun 2015 10:26:52 -0400 Subject: [jbosstools-dev] Upcoming release of Locus 1.3.0 In-Reply-To: <937643157.8215637.1433254692171.JavaMail.zimbra@redhat.com> References: <556DBA12.4030302@redhat.com> <937643157.8215637.1433254692171.JavaMail.zimbra@redhat.com> Message-ID: <556DBD2C.1040305@redhat.com> "Snapshot builds will be published here [1] once the above jars are added to Locus." On 06/02/2015 10:18 AM, Paul Leacu wrote: > > Thanks Nick - I'm assuming there'll be a 1.3.0-SNAPSHOT first so we can verify that we've got everything? > > --paull > > ----- Original Message ----- >> From: "Nick Boldt" >> To: jbosstools-dev at lists.jboss.org >> Sent: Tuesday, June 2, 2015 10:13:38 AM >> Subject: [jbosstools-dev] Upcoming release of Locus 1.3.0 >> >> Hi all, >> >> The JBoss Tools - Integration Stack requires some new version of >> external libs, so we need to release Locus 1.3.0 soon to deliver those >> libs as OSGi bundles. >> >> At this time, 3 new bundles have been requested to be added to Locus: >> >> jsonschema2pojo-core jar >> jaxb-xjc jar >> jaxb-impl jar >> >> Ref: https://issues.jboss.org/browse/LOCUS-42 >> >> Snapshot builds will be published here [1] once the above jars are added >> to Locus. >> >> [1] >> https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/locus/update.site/ >> >> The plan is to release 1.3.0 in the next couple weeks, once the dust >> settles around the upcoming JBoss Tools 4.3.0.Beta1 code freeze and >> staging for QE testing. >> >> If you have concerns with this change, want something ELSE added to the >> release, or need a revision to the timeline, please don't hesitate to >> respond on this thread. >> >> Thanks, >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From rawagner at redhat.com Tue Jun 2 10:51:55 2015 From: rawagner at redhat.com (Rastislav Wagner) Date: Tue, 2 Jun 2015 10:51:55 -0400 (EDT) Subject: [jbosstools-dev] JBDS/Eclipse performance update In-Reply-To: <1823440872.7364643.1433256500471.JavaMail.zimbra@redhat.com> Message-ID: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> Hi all, I noticed that WSDL validation is a bit slow when wsld file contains references to www.w3.org probably due to [1]. Bug for eclipse is already created and is a bit old [2]. I've commented there but no response yet. I dont know if any part of JBT/JBDS is doing something with w3.org, if yes, than you could consider doing something to minimize requests to w3.org servers. Another possible issue is a map which m2e creates during importing projects. In >=Mars M4 this map is extending up to 500MB, for <=M3 it was up to 200MB. If you're interested see discussion on m2e-dev [3] [1]http://www.w3.org/Help/Webmaster.html#slowdtd [2]https://bugs.eclipse.org/bugs/show_bug.cgi?id=400340. [3]http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg01905.html Rastislav Wagner JBDS QA irc: rawagner Red Hat Czech Purkynova 99, 612 00 Brno, Czech Republic From mistria at redhat.com Tue Jun 2 11:09:12 2015 From: mistria at redhat.com (Mickael Istria) Date: Tue, 02 Jun 2015 17:09:12 +0200 Subject: [jbosstools-dev] JBDS/Eclipse performance update In-Reply-To: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> Message-ID: <556DC718.6070002@redhat.com> On 06/02/2015 04:51 PM, Rastislav Wagner wrote: > Hi all, > I noticed that WSDL validation is a bit slow when wsld file contains references to www.w3.org probably due to [1]. Bug for eclipse is already created and is a bit old [2]. I've commented there but no response yet. > I dont know if any part of JBT/JBDS is doing something with w3.org, if yes, than you could consider doing something to minimize requests to w3.org servers. It seems to be only a matter of providing the necessary catalog extension (extension point is org.eclipse.wst.xml.core.catalogContributions). Maybe you could submit a patch for that But it's most likely too late to contribute that to Eclipse XML support for Mars, so even with a patch upstream, we'd need to have a local fix if we want it to behave better with JBT/JBDS. So it's worth opening a Jira and adding necessary DTD and XSD in JBT as well. -- 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/20150602/9c314c46/attachment.html From manderse at redhat.com Tue Jun 2 14:27:52 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 2 Jun 2015 14:27:52 -0400 (EDT) Subject: [jbosstools-dev] JBDS/Eclipse performance update In-Reply-To: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> Message-ID: Good finds. Can you try add them to your eclipse instance xml catalog and see if it makes a significant difference ? /max http://about.me/maxandersen > On 02 Jun 2015, at 16:51, Rastislav Wagner wrote: > > Hi all, > I noticed that WSDL validation is a bit slow when wsld file contains references to www.w3.org probably due to [1]. Bug for eclipse is already created and is a bit old [2]. I've commented there but no response yet. > I dont know if any part of JBT/JBDS is doing something with w3.org, if yes, than you could consider doing something to minimize requests to w3.org servers. > > Another possible issue is a map which m2e creates during importing projects. In >=Mars M4 this map is extending up to 500MB, for <=M3 it was up to 200MB. If you're interested see discussion on m2e-dev [3] > > [1]http://www.w3.org/Help/Webmaster.html#slowdtd > [2]https://bugs.eclipse.org/bugs/show_bug.cgi?id=400340. > [3]http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg01905.html > > Rastislav Wagner > JBDS QA > irc: rawagner > > Red Hat Czech > Purkynova 99, 612 00 Brno, Czech Republic From manderse at redhat.com Wed Jun 3 02:59:58 2015 From: manderse at redhat.com (manderse at redhat.com) Date: Wed, 3 Jun 2015 02:59:58 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 2 issues with no component Message-ID: <201506030659.t536xwf3029279@int-mx14.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-19907 https://issues.jboss.org/browse/JBIDE-19907 Summary: Default options to start a Docker container Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1:03:31.609103 ---------------------------- * No component for JBIDE-19906 https://issues.jboss.org/browse/JBIDE-19906 Summary: Disabled Finish button for Create Container Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1:06:16.617625 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27 From xcoulon at redhat.com Wed Jun 3 06:01:09 2015 From: xcoulon at redhat.com (Xavier Coulon) Date: Wed, 3 Jun 2015 12:01:09 +0200 Subject: [jbosstools-dev] Including Docker Tooling in TP for JBoss Tools 4.3.0.Beta1 Message-ID: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> Hello, As I was deep in the code for the Docker tooling until last night, I miserably failed to respond to Micka?l's comment on https://issues.jboss.org/browse/JBIDE-19848 , but I'd like to know if it's still possible to include the Docker tooling hosted on Eclipse.org/linuxtools in our Target Platforms before tomorrow's code freeze. I tried to give as much details as possible and submitted 2 PR to include the new requirements and update the .target files for JBoss Tools and Dev Studio. I understand that the delay is very short and once again, I apologize for this last-minute request. Thanks. Best regards, /Xavier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150603/59c0ef10/attachment.html From manderse at redhat.com Wed Jun 3 07:36:51 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 03 Jun 2015 13:36:51 +0200 Subject: [jbosstools-dev] JBDS/Eclipse performance update In-Reply-To: <556DC718.6070002@redhat.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> <556DC718.6070002@redhat.com> Message-ID: <0275407A-3101-4871-975F-37F0EF7506AE@redhat.com> Seems my mail got lost somewhere. Good findings, and yes I agree with Mickael it looks like it iis just about adding the most common files to the catalog but before we do so lets just add them manually and test if they make a difference. Can you try that Rastislav ? Thanks, Max > On 06/02/2015 04:51 PM, Rastislav Wagner wrote: >> Hi all, >> I noticed that WSDL validation is a bit slow when wsld file contains >> references to www.w3.org probably due to [1]. Bug for eclipse is >> already created and is a bit old [2]. I've commented there but no >> response yet. >> I dont know if any part of JBT/JBDS is doing something with w3.org, >> if yes, than you could consider doing something to minimize requests >> to w3.org servers. > It seems to be only a matter of providing the necessary catalog > extension (extension point is > org.eclipse.wst.xml.core.catalogContributions). Maybe you could submit > a patch for that > But it's most likely too late to contribute that to Eclipse XML > support for Mars, so even with a patch upstream, we'd need to have a > local fix if we want it to behave better with JBT/JBDS. So it's worth > opening a Jira and adding necessary DTD and XSD in JBT as well. > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From rawagner at redhat.com Wed Jun 3 10:07:55 2015 From: rawagner at redhat.com (Rastislav Wagner) Date: Wed, 3 Jun 2015 10:07:55 -0400 (EDT) Subject: [jbosstools-dev] JBDS/Eclipse performance update In-Reply-To: <0275407A-3101-4871-975F-37F0EF7506AE@redhat.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> <556DC718.6070002@redhat.com> <0275407A-3101-4871-975F-37F0EF7506AE@redhat.com> Message-ID: <403861504.7922507.1433340475624.JavaMail.zimbra@redhat.com> Yes, i read the email. Sorry for not responding earlier- I thought that trying this would be faster - but I was fighting with XML Catalog. Its a strange "beast". So I picked this file for testing [1] and added w3 schemes to catalog and validation time went down from 5-6s to 1s. [1]https://goo.gl/yrycT2 Rastislav Wagner JBDS QA irc: rawagner Red Hat Czech Purkynova 99, 612 00 Brno, Czech Republic ----- Original Message ----- > From: "Max Rydahl Andersen" > To: "Mickael Istria" > Cc: jbosstools-dev at lists.jboss.org > Sent: Wednesday, June 3, 2015 1:36:51 PM > Subject: Re: [jbosstools-dev] JBDS/Eclipse performance update > > Seems my mail got lost somewhere. > > Good findings, and yes I agree with Mickael it looks like it iis just > about adding the most common files to the catalog but before we do so > lets > just add them manually and test if they make a difference. > > Can you try that Rastislav ? > > Thanks, > Max > > > On 06/02/2015 04:51 PM, Rastislav Wagner wrote: > >> Hi all, > >> I noticed that WSDL validation is a bit slow when wsld file contains > >> references to www.w3.org probably due to [1]. Bug for eclipse is > >> already created and is a bit old [2]. I've commented there but no > >> response yet. > >> I dont know if any part of JBT/JBDS is doing something with w3.org, > >> if yes, than you could consider doing something to minimize requests > >> to w3.org servers. > > It seems to be only a matter of providing the necessary catalog > > extension (extension point is > > org.eclipse.wst.xml.core.catalogContributions). Maybe you could submit > > a patch for that > > But it's most likely too late to contribute that to Eclipse XML > > support for Mars, so even with a patch upstream, we'd need to have a > > local fix if we want it to behave better with JBT/JBDS. So it's worth > > opening a Jira and adding necessary DTD and XSD in JBT as well. > > -- > > Mickael Istria > > Eclipse developer at JBoss, by Red Hat > > My blog - My Tweets > > > > _______________________________________________ > > jbosstools-dev mailing list > > jbosstools-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > From manderse at redhat.com Wed Jun 3 10:39:13 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 03 Jun 2015 16:39:13 +0200 Subject: [jbosstools-dev] JBDS/Eclipse performance update In-Reply-To: <403861504.7922507.1433340475624.JavaMail.zimbra@redhat.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> <556DC718.6070002@redhat.com> <0275407A-3101-4871-975F-37F0EF7506AE@redhat.com> <403861504.7922507.1433340475624.JavaMail.zimbra@redhat.com> Message-ID: <2805A77F-613E-4992-A105-F370878CF751@redhat.com> On 3 Jun 2015, at 16:07, Rastislav Wagner wrote: > Yes, i read the email. Sorry for not responding earlier- no worry - I think something changed recently so my own emails aren't listed when searching ;/ > I thought that trying this would be faster - but I was fighting with > XML Catalog. Its a strange "beast". it definitely is ;) > So I picked this file for testing [1] and added w3 schemes to catalog > and validation time went down from 5-6s to 1s. > > [1]https://goo.gl/yrycT2 Thats significant! And you don't see eclipse cache its prefetched items ? I was sure it did cache that at some point. So sounds like we got two bugs, one we can handle on our own ( but should submit upstream ) and another that needs fix upstream most likely. 1) find common used catalog/schemas from w3c we use in examples/quickstarts etc. and add to our catalog, and submit patch to wtp to add to theirs (might be an license issue here though we need to check ;/ 2) figure out why wtp xml is not caching prefetched images. /max > > > > Rastislav Wagner > JBDS QA > irc: rawagner > > Red Hat Czech > Purkynova 99, 612 00 Brno, Czech Republic > > ----- Original Message ----- >> From: "Max Rydahl Andersen" >> To: "Mickael Istria" >> Cc: jbosstools-dev at lists.jboss.org >> Sent: Wednesday, June 3, 2015 1:36:51 PM >> Subject: Re: [jbosstools-dev] JBDS/Eclipse performance update >> >> Seems my mail got lost somewhere. >> >> Good findings, and yes I agree with Mickael it looks like it iis just >> about adding the most common files to the catalog but before we do so >> lets >> just add them manually and test if they make a difference. >> >> Can you try that Rastislav ? >> >> Thanks, >> Max >> >>> On 06/02/2015 04:51 PM, Rastislav Wagner wrote: >>>> Hi all, >>>> I noticed that WSDL validation is a bit slow when wsld file >>>> contains >>>> references to www.w3.org probably due to [1]. Bug for eclipse is >>>> already created and is a bit old [2]. I've commented there but no >>>> response yet. >>>> I dont know if any part of JBT/JBDS is doing something with w3.org, >>>> if yes, than you could consider doing something to minimize >>>> requests >>>> to w3.org servers. >>> It seems to be only a matter of providing the necessary catalog >>> extension (extension point is >>> org.eclipse.wst.xml.core.catalogContributions). Maybe you could >>> submit >>> a patch for that >>> But it's most likely too late to contribute that to Eclipse XML >>> support for Mars, so even with a patch upstream, we'd need to have a >>> local fix if we want it to behave better with JBT/JBDS. So it's >>> worth >>> opening a Jira and adding necessary DTD and XSD in JBT as well. >>> -- >>> Mickael Istria >>> Eclipse developer at JBoss, by Red Hat >>> My blog - My Tweets >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> /max >> http://about.me/maxandersen >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> /max http://about.me/maxandersen From mistria at redhat.com Wed Jun 3 11:47:39 2015 From: mistria at redhat.com (Mickael Istria) Date: Wed, 03 Jun 2015 17:47:39 +0200 Subject: [jbosstools-dev] Including Docker Tooling in TP for JBoss Tools 4.3.0.Beta1 In-Reply-To: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> References: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> Message-ID: <556F219B.2050001@redhat.com> On 06/03/2015 12:01 PM, Xavier Coulon wrote: > As I was deep in the code for the Docker tooling until last night, I > miserably failed to respond to Micka?l's comment on > https://issues.jboss.org/browse/JBIDE-19848, but I'd like to know if > it's still possible to include the Docker tooling hosted on > Eclipse.org/linuxtools in our Target > Platforms before tomorrow's code freeze. > I tried to give as much details as possible and submitted 2 PR to > include the new requirements and update the .target files for JBoss > Tools and Dev Studio. > > I understand that the delay is very short and once again, I apologize > for this last-minute request. We'll delay the TP release to make sure Docker is in and is usable for JBoss Tools 4.3.0.Beta1 and JBoss Developer Studio 9.0.0.Beta1. Plan is to merge your suggested changes in TP today. We'll include Docker as an item under the "Abriged" category of JBoss Tools update-site, and as an included feature in JBDS. -- 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/20150603/0f3c33c6/attachment.html From rawagner at redhat.com Wed Jun 3 12:06:14 2015 From: rawagner at redhat.com (Rastislav Wagner) Date: Wed, 3 Jun 2015 12:06:14 -0400 (EDT) Subject: [jbosstools-dev] JBDS/Eclipse performance update In-Reply-To: <2805A77F-613E-4992-A105-F370878CF751@redhat.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> <556DC718.6070002@redhat.com> <0275407A-3101-4871-975F-37F0EF7506AE@redhat.com> <403861504.7922507.1433340475624.JavaMail.zimbra@redhat.com> <2805A77F-613E-4992-A105-F370878CF751@redhat.com> Message-ID: <149602182.8023462.1433347574684.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Max Rydahl Andersen" > To: "Rastislav Wagner" > Cc: "Mickael Istria" , jbosstools-dev at lists.jboss.org > Sent: Wednesday, June 3, 2015 4:39:13 PM > Subject: Re: [jbosstools-dev] JBDS/Eclipse performance update > > On 3 Jun 2015, at 16:07, Rastislav Wagner wrote: > > > Yes, i read the email. Sorry for not responding earlier- > > no worry - I think something changed recently so my own emails aren't > listed when searching ;/ > > > I thought that trying this would be faster - but I was fighting with > > XML Catalog. Its a strange "beast". > > it definitely is ;) > > > So I picked this file for testing [1] and added w3 schemes to catalog > > and validation time went down from 5-6s to 1s. > > > > [1]https://goo.gl/yrycT2 > > Thats significant! > > And you don't see eclipse cache its prefetched items ? I was sure it did > cache that at some point. > > So sounds like we got two bugs, one we can handle on our own ( but > should submit upstream ) and another that needs fix upstream most > likely. > > 1) find common used catalog/schemas from w3c we use in > examples/quickstarts etc. and add to our catalog, and submit patch to > wtp to add to theirs (might be an license issue here though we need to > check ;/ created https://issues.jboss.org/browse/JBIDE-19910 > > 2) figure out why wtp xml is not caching prefetched images. It looks like only wsdl validation isn't caching, xml seems to be fine - but I will have to do more testing to be sure. > > /max > > > > > > > > > Rastislav Wagner > > JBDS QA > > irc: rawagner > > > > Red Hat Czech > > Purkynova 99, 612 00 Brno, Czech Republic > > > > ----- Original Message ----- > >> From: "Max Rydahl Andersen" > >> To: "Mickael Istria" > >> Cc: jbosstools-dev at lists.jboss.org > >> Sent: Wednesday, June 3, 2015 1:36:51 PM > >> Subject: Re: [jbosstools-dev] JBDS/Eclipse performance update > >> > >> Seems my mail got lost somewhere. > >> > >> Good findings, and yes I agree with Mickael it looks like it iis just > >> about adding the most common files to the catalog but before we do so > >> lets > >> just add them manually and test if they make a difference. > >> > >> Can you try that Rastislav ? > >> > >> Thanks, > >> Max > >> > >>> On 06/02/2015 04:51 PM, Rastislav Wagner wrote: > >>>> Hi all, > >>>> I noticed that WSDL validation is a bit slow when wsld file > >>>> contains > >>>> references to www.w3.org probably due to [1]. Bug for eclipse is > >>>> already created and is a bit old [2]. I've commented there but no > >>>> response yet. > >>>> I dont know if any part of JBT/JBDS is doing something with w3.org, > >>>> if yes, than you could consider doing something to minimize > >>>> requests > >>>> to w3.org servers. > >>> It seems to be only a matter of providing the necessary catalog > >>> extension (extension point is > >>> org.eclipse.wst.xml.core.catalogContributions). Maybe you could > >>> submit > >>> a patch for that > >>> But it's most likely too late to contribute that to Eclipse XML > >>> support for Mars, so even with a patch upstream, we'd need to have a > >>> local fix if we want it to behave better with JBT/JBDS. So it's > >>> worth > >>> opening a Jira and adding necessary DTD and XSD in JBT as well. > >>> -- > >>> Mickael Istria > >>> Eclipse developer at JBoss, by Red Hat > >>> My blog - My Tweets > >>> > >>> _______________________________________________ > >>> jbosstools-dev mailing list > >>> jbosstools-dev at lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > >> > >> > >> /max > >> http://about.me/maxandersen > >> _______________________________________________ > >> jbosstools-dev mailing list > >> jbosstools-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > >> > > > /max > http://about.me/maxandersen > From ggastald at redhat.com Wed Jun 3 12:10:22 2015 From: ggastald at redhat.com (George Gastaldi) Date: Wed, 03 Jun 2015 13:10:22 -0300 Subject: [jbosstools-dev] Including Docker Tooling in TP for JBoss Tools 4.3.0.Beta1 In-Reply-To: <556F219B.2050001@redhat.com> References: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> <556F219B.2050001@redhat.com> Message-ID: <556F26EE.1040600@redhat.com> Sorry for my ignorance, I am not sure if it's a typo or not , but is "Abriged" a real word? or should it read "Abridged" ? Thanks On 06/03/2015 12:47 PM, Mickael Istria wrote: > We'll include Docker as an item under the "Abriged" category of JBoss > Tools update-site, and as an included feature in JBDS. > -- > 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/20150603/6e922803/attachment.html From nboldt at redhat.com Wed Jun 3 13:25:47 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 03 Jun 2015 13:25:47 -0400 Subject: [jbosstools-dev] Including Docker Tooling in TP for JBoss Tools 4.3.0.Beta1 In-Reply-To: <556F26EE.1040600@redhat.com> References: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> <556F219B.2050001@redhat.com> <556F26EE.1040600@redhat.com> Message-ID: <556F389B.7000406@redhat.com> It's abridged. https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L380 https://www.google.ca/search?q=define:+abridged On 06/03/2015 12:10 PM, George Gastaldi wrote: > Sorry for my ignorance, I am not sure if it's a typo or not , but is > "Abriged" a real word? or should it read "Abridged" ? > > Thanks > > On 06/03/2015 12:47 PM, Mickael Istria wrote: >> We'll include Docker as an item under the "Abriged" category of JBoss >> Tools update-site, and as an included feature in JBDS. >> -- >> Mickael Istria >> Eclipse developer at JBoss, by Red Hat >> My blog - My Tweets >> >> > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Wed Jun 3 13:57:38 2015 From: mistria at redhat.com (Mickael Istria) Date: Wed, 03 Jun 2015 19:57:38 +0200 Subject: [jbosstools-dev] Including Docker Tooling in TP for JBoss Tools 4.3.0.Beta1 In-Reply-To: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> References: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> Message-ID: <556F4012.8050308@redhat.com> Docker Tools has been added to target-platforms, and to JBoss Tools site, and to JBDS feature. A new version of Docker Tools is upcoming and will be consumed for Beta1, but this first iteration validates the build chain. -- 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/20150603/3619e27e/attachment.html From xcoulon at redhat.com Wed Jun 3 14:08:47 2015 From: xcoulon at redhat.com (Xavier Coulon) Date: Wed, 3 Jun 2015 20:08:47 +0200 Subject: [jbosstools-dev] Including Docker Tooling in TP for JBoss Tools 4.3.0.Beta1 In-Reply-To: <556F4012.8050308@redhat.com> References: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> <556F4012.8050308@redhat.com> Message-ID: <59293B0B-BA78-4B06-A66D-B29F7DE1A900@redhat.com> Cool ! Thanks ! Best regards, /Xavier > On 03 Jun 2015, at 19:57, Mickael Istria wrote: > > Docker Tools has been added to target-platforms, and to JBoss Tools site, and to JBDS feature. > A new version of Docker Tools is upcoming and will be consumed for Beta1, but this first iteration validates the build chain. > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150603/98fffb0d/attachment.html From nboldt at redhat.com Wed Jun 3 18:15:20 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 03 Jun 2015 18:15:20 -0400 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... Message-ID: <556F7C78.7070707@redhat.com> Currently building this locally and then will attempt to build JBDS with it: https://github.com/jbosstools/jbosstools-target-platforms/pull/151 Resulting TP contains only a single version of these IUs (instead of multiple versions as we did in the past): javax.servlet_3.1.0.v201410161800.jar javax.servlet.jsp.source_2.2.0.v201112011158.jar javax.servlet.source_3.1.0.v201410161800.jar org.apache.commons.lang_2.6.0.v201404270220.jar org.apache.commons.lang.source_2.6.0.v201404270220.jar To build against local TP: mvn clean install -P hudson,eap,pack200 -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 -DJOB_NAME=devstudio.product_master -Dupdate.site.description="Development Milestone" -Djbosstools_site_stream=master -Dtpc.targetKind=unified -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Jun 3 18:15:37 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 03 Jun 2015 18:15:37 -0400 Subject: [jbosstools-dev] Including Docker Tooling in TP for JBoss Tools 4.3.0.Beta1 In-Reply-To: <59293B0B-BA78-4B06-A66D-B29F7DE1A900@redhat.com> References: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> <556F4012.8050308@redhat.com> <59293B0B-BA78-4B06-A66D-B29F7DE1A900@redhat.com> Message-ID: <556F7C89.3060709@redhat.com> Beta1-SNAPSHOT TP is updated again: https://github.com/jbosstools/jbosstools-target-platforms/pull/150 Ref: JBIDE-19848 On 06/03/2015 02:08 PM, Xavier Coulon wrote: > Cool ! Thanks ! > > Best regards, > /Xavier > > > >> On 03 Jun 2015, at 19:57, Mickael Istria > > wrote: >> >> Docker Tools has been added to target-platforms, and to JBoss Tools >> site, and to JBDS feature. >> A new version of Docker Tools is upcoming and will be consumed for >> Beta1, but this first iteration validates the build chain. >> -- >> 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 nboldt at redhat.com Wed Jun 3 18:51:31 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 03 Jun 2015 18:51:31 -0400 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... In-Reply-To: <556F7C78.7070707@redhat.com> References: <556F7C78.7070707@redhat.com> Message-ID: <556F84F3.1070204@redhat.com> JBDS built locally and installed fine. Resulting IUs in installation (no source bundles, as expected): javax.servlet.jsp_2.2.0.v201112011158.jar javax.servlet_3.1.0.v201410161800.jar org.apache.commons.lang_2.6.0.v201404270220.jar Can someone else verify this change is safe? Motivation here is to remove dupe IUs and therefore get a cleaner install footprint, which will also make versionwatch builds blue again. See also https://issues.jboss.org/browse/JBIDE-19605 On 06/03/2015 06:15 PM, Nick Boldt wrote: > Currently building this locally and then will attempt to build JBDS with > it: > > https://github.com/jbosstools/jbosstools-target-platforms/pull/151 > > Resulting TP contains only a single version of these IUs (instead of > multiple versions as we did in the past): > > javax.servlet_3.1.0.v201410161800.jar > javax.servlet.jsp.source_2.2.0.v201112011158.jar > javax.servlet.source_3.1.0.v201410161800.jar > org.apache.commons.lang_2.6.0.v201404270220.jar > org.apache.commons.lang.source_2.6.0.v201404270220.jar > > To build against local TP: > > mvn clean install -P hudson,eap,pack200 > -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 > -DJOB_NAME=devstudio.product_master > -Dupdate.site.description="Development Milestone" > -Djbosstools_site_stream=master -Dtpc.targetKind=unified > -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ > > > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Thu Jun 4 02:33:40 2015 From: mistria at redhat.com (Mickael Istria) Date: Thu, 04 Jun 2015 08:33:40 +0200 Subject: [jbosstools-dev] JBDS/Eclipse performance update In-Reply-To: <149602182.8023462.1433347574684.JavaMail.zimbra@redhat.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> <556DC718.6070002@redhat.com> <0275407A-3101-4871-975F-37F0EF7506AE@redhat.com> <403861504.7922507.1433340475624.JavaMail.zimbra@redhat.com> <2805A77F-613E-4992-A105-F370878CF751@redhat.com> <149602182.8023462.1433347574684.JavaMail.zimbra@redhat.com> Message-ID: <556FF144.9020908@redhat.com> On 06/03/2015 06:06 PM, Rastislav Wagner wrote: >> 2) figure out why wtp xml is not caching prefetched images. > It looks like only wsdl validation isn't caching, xml seems to be fine - but I will have to do more testing to be sure. On freenode's #eclipse-dev: mistria: nitind hi mistria: nitind: are you familiar with the XML catalog? nitind: mistria: only vaguely, why? mistria: nitind: I'm wondering whether it caches XSD or DTD that have already been downloaded once, or if resolution happens everytime nitind: mistria: It's supposed to use org.eclipse.wst.internet.cache to cache the ones it has to download itself. mistria: nitind: ok mistria: nitind: thanks for the info mistria: nitind: would it be realistic to show the cached xsd and dtd in the XML catalog dialog? nitind: mistria: Which dialog do you mean? mistria: nitind: Preferences > XML > XML Catalog mistria: nitind: (we're on https://bugs.eclipse.org/bugs/show_bug.cgi?id=400340 , several interesting XSD/DTD are missing, causing big performance issues - 5 seconds to have XML editor ready instead of just 1) -- 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/20150604/28650b52/attachment.html From manderse at redhat.com Thu Jun 4 07:10:57 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 04 Jun 2015 13:10:57 +0200 Subject: [jbosstools-dev] Including Docker Tooling in TP for JBoss Tools 4.3.0.Beta1 In-Reply-To: <59293B0B-BA78-4B06-A66D-B29F7DE1A900@redhat.com> References: <768069E7-27D9-413C-8E3F-0837E65C2395@redhat.com> <556F4012.8050308@redhat.com> <59293B0B-BA78-4B06-A66D-B29F7DE1A900@redhat.com> Message-ID: <50436619-AFF0-470C-AE48-2BE5E8A8A28E@redhat.com> much appreciated all! > Cool ! Thanks ! > > Best regards, > /Xavier > > > >> On 03 Jun 2015, at 19:57, Mickael Istria wrote: >> >> Docker Tools has been added to target-platforms, and to JBoss Tools >> site, and to JBDS feature. >> A new version of Docker Tools is upcoming and will be consumed for >> Beta1, but this first iteration validates the build chain. >> -- >> Mickael Istria >> Eclipse developer at JBoss, by Red Hat >> My blog - My Tweets >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Thu Jun 4 07:13:49 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 04 Jun 2015 13:13:49 +0200 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... In-Reply-To: <556F84F3.1070204@redhat.com> References: <556F7C78.7070707@redhat.com> <556F84F3.1070204@redhat.com> Message-ID: <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> On 4 Jun 2015, at 0:51, Nick Boldt wrote: > JBDS built locally and installed fine. Resulting IUs in installation > (no > source bundles, as expected): > > javax.servlet.jsp_2.2.0.v201112011158.jar > javax.servlet_3.1.0.v201410161800.jar > org.apache.commons.lang_2.6.0.v201404270220.jar > > Can someone else verify this change is safe? > > Motivation here is to remove dupe IUs and therefore get a cleaner > install footprint if the separate versions are not required then that is a good reason. > , which will also make versionwatch builds blue again. I would rather fix version watch to be able to add exceptions for this rule since we most likely will end up with multiple versions of things - but that should only be marked okey if it is actually needed/wanted. I can't verify it easily today - maybe Denis can on his buildsetup ? /max > See also https://issues.jboss.org/browse/JBIDE-19605 > > On 06/03/2015 06:15 PM, Nick Boldt wrote: >> Currently building this locally and then will attempt to build JBDS >> with >> it: >> >> https://github.com/jbosstools/jbosstools-target-platforms/pull/151 >> >> Resulting TP contains only a single version of these IUs (instead of >> multiple versions as we did in the past): >> >> javax.servlet_3.1.0.v201410161800.jar >> javax.servlet.jsp.source_2.2.0.v201112011158.jar >> javax.servlet.source_3.1.0.v201410161800.jar >> org.apache.commons.lang_2.6.0.v201404270220.jar >> org.apache.commons.lang.source_2.6.0.v201404270220.jar >> >> To build against local TP: >> >> mvn clean install -P hudson,eap,pack200 >> -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 >> -DJOB_NAME=devstudio.product_master >> -Dupdate.site.description="Development Milestone" >> -Djbosstools_site_stream=master -Dtpc.targetKind=unified >> -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ >> >> >> > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From nboldt at redhat.com Thu Jun 4 08:58:38 2015 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 04 Jun 2015 08:58:38 -0400 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... In-Reply-To: <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> References: <556F7C78.7070707@redhat.com> <556F84F3.1070204@redhat.com> <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> Message-ID: <55704B7E.9090905@redhat.com> Versionwatch CAN be tweaked to add exceptions. We currently have 3 in there for know issues where multiple versions were needed. But it doesn't validate IF those exclusions are still true. For that we need to build everything, install everything, and see what's broken. Suspect that some of these IUs MIGHT be needed for something from Central. I didn't test-install that. N On 06/04/2015 07:13 AM, Max Rydahl Andersen wrote: > On 4 Jun 2015, at 0:51, Nick Boldt wrote: > >> JBDS built locally and installed fine. Resulting IUs in installation (no >> source bundles, as expected): >> >> javax.servlet.jsp_2.2.0.v201112011158.jar >> javax.servlet_3.1.0.v201410161800.jar >> org.apache.commons.lang_2.6.0.v201404270220.jar >> >> Can someone else verify this change is safe? >> >> Motivation here is to remove dupe IUs and therefore get a cleaner >> install footprint > > if the separate versions are not required then that is a good reason. > >> , which will also make versionwatch builds blue again. > > I would rather fix version watch to be able to add exceptions for this rule > since we most likely will end up with multiple versions of things - but > that > should only be marked okey if it is actually needed/wanted. > > I can't verify it easily today - maybe Denis can on his buildsetup ? > > /max > >> See also https://issues.jboss.org/browse/JBIDE-19605 >> >> On 06/03/2015 06:15 PM, Nick Boldt wrote: >>> Currently building this locally and then will attempt to build JBDS with >>> it: >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/151 >>> >>> Resulting TP contains only a single version of these IUs (instead of >>> multiple versions as we did in the past): >>> >>> javax.servlet_3.1.0.v201410161800.jar >>> javax.servlet.jsp.source_2.2.0.v201112011158.jar >>> javax.servlet.source_3.1.0.v201410161800.jar >>> org.apache.commons.lang_2.6.0.v201404270220.jar >>> org.apache.commons.lang.source_2.6.0.v201404270220.jar >>> >>> To build against local TP: >>> >>> mvn clean install -P hudson,eap,pack200 >>> -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 >>> -DJOB_NAME=devstudio.product_master >>> -Dupdate.site.description="Development Milestone" >>> -Djbosstools_site_stream=master -Dtpc.targetKind=unified >>> -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ >>> >>> >>> >>> >> >> -- >> 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 akazakov at exadel.com Thu Jun 4 15:04:56 2015 From: akazakov at exadel.com (Alexey Kazakov) Date: Thu, 04 Jun 2015 12:04:56 -0700 Subject: [jbosstools-dev] New org.jboss.tools.foundation.checkup plugin In-Reply-To: <149602182.8023462.1433347574684.JavaMail.zimbra@redhat.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> <556DC718.6070002@redhat.com> <0275407A-3101-4871-975F-37F0EF7506AE@redhat.com> <403861504.7922507.1433340475624.JavaMail.zimbra@redhat.com> <2805A77F-613E-4992-A105-F370878CF751@redhat.com> <149602182.8023462.1433347574684.JavaMail.zimbra@redhat.com> Message-ID: <5570A158.5080305@exadel.com> Hi, I just merged a PR for https://issues.jboss.org/browse/JBIDE-19500 ( A warning dialog if we detect JBT/JBDS is run on unsupported JVM) This PR introduces a new plugin in foundation (jbosstools-base repo): *org.jboss.tools.foundation.checkup* which is a requirements for o.j.t.foundation.core which means it's a requirements for almost every JBT plugin. So don't be surprised if your dev workspace is not compatible any more after jbosstools-base pull from master ;) Thanks, Alexey Kazakov. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150604/0634874e/attachment.html From nboldt at redhat.com Thu Jun 4 15:18:49 2015 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 04 Jun 2015 15:18:49 -0400 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... In-Reply-To: <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> References: <556F7C78.7070707@redhat.com> <556F84F3.1070204@redhat.com> <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> Message-ID: <5570A499.2010104@redhat.com> Well, it's been pushed so we'll see what happens when all the projects are branched and the madness begins tonight. :D Also, we'll see if anything unexpected happens in master branch, since that's using the same target platform. Mickael & I have decided to postpone releasing the target platform (that is, renaming it to remove the -SNAPSHOT suffix and updating all the jobs/parent poms) until Monday just in case we need to revert anything (or fetch newer versions of RC3/RC4 bits). N On 06/04/2015 07:13 AM, Max Rydahl Andersen wrote: > On 4 Jun 2015, at 0:51, Nick Boldt wrote: > >> JBDS built locally and installed fine. Resulting IUs in installation (no >> source bundles, as expected): >> >> javax.servlet.jsp_2.2.0.v201112011158.jar >> javax.servlet_3.1.0.v201410161800.jar >> org.apache.commons.lang_2.6.0.v201404270220.jar >> >> Can someone else verify this change is safe? >> >> Motivation here is to remove dupe IUs and therefore get a cleaner >> install footprint > > if the separate versions are not required then that is a good reason. > >> , which will also make versionwatch builds blue again. > > I would rather fix version watch to be able to add exceptions for this rule > since we most likely will end up with multiple versions of things - but > that > should only be marked okey if it is actually needed/wanted. > > I can't verify it easily today - maybe Denis can on his buildsetup ? > > /max > >> See also https://issues.jboss.org/browse/JBIDE-19605 >> >> On 06/03/2015 06:15 PM, Nick Boldt wrote: >>> Currently building this locally and then will attempt to build JBDS with >>> it: >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/151 >>> >>> Resulting TP contains only a single version of these IUs (instead of >>> multiple versions as we did in the past): >>> >>> javax.servlet_3.1.0.v201410161800.jar >>> javax.servlet.jsp.source_2.2.0.v201112011158.jar >>> javax.servlet.source_3.1.0.v201410161800.jar >>> org.apache.commons.lang_2.6.0.v201404270220.jar >>> org.apache.commons.lang.source_2.6.0.v201404270220.jar >>> >>> To build against local TP: >>> >>> mvn clean install -P hudson,eap,pack200 >>> -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 >>> -DJOB_NAME=devstudio.product_master >>> -Dupdate.site.description="Development Milestone" >>> -Djbosstools_site_stream=master -Dtpc.targetKind=unified >>> -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ >>> >>> >>> >>> >> >> -- >> 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 Thu Jun 4 15:50:20 2015 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 04 Jun 2015 15:50:20 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze is today! 8 of 17 projects left to branch Message-ID: <5570ABFC.7010203@redhat.com> If you haven't already seen the JIRAs, the following components need to get branched ASAP. Aerogear: https://issues.jboss.org/browse/JBIDE-19913 VPE: https://issues.jboss.org/browse/JBIDE-19915 Server: https://issues.jboss.org/browse/JBIDE-19917 Openshift: https://issues.jboss.org/browse/JBIDE-19920 JavaEE: https://issues.jboss.org/browse/JBIDE-19921 Browsersim: https://issues.jboss.org/browse/JBIDE-19925 Webservices: https://issues.jboss.org/browse/JBIDE-19926 Central: https://issues.jboss.org/browse/JBIDE-19928 Should you have a problem building (eg., because your build pulls from jbosstools_site_stream=4.3.mars, and those bits don't yet exist or exist but are still the old Alpha2 bits) ... Just make sure you use: -Djbosstools_site_stream=master Once everyone is branched for Beta1x, I will switch the parent pom so that it contains jbosstools_site_stream=4.3.mars. Then your master branch needs to be switched to pull from the Beta2 parent pom, which sets jbosstools_site_stream=master so you can build against the correct stream. Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Thu Jun 4 17:43:25 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 04 Jun 2015 23:43:25 +0200 Subject: [jbosstools-dev] New org.jboss.tools.foundation.checkup plugin In-Reply-To: <5570A158.5080305@exadel.com> References: <813796652.7367063.1433256715481.JavaMail.zimbra@redhat.com> <556DC718.6070002@redhat.com> <0275407A-3101-4871-975F-37F0EF7506AE@redhat.com> <403861504.7922507.1433340475624.JavaMail.zimbra@redhat.com> <2805A77F-613E-4992-A105-F370878CF751@redhat.com> <149602182.8023462.1433347574684.JavaMail.zimbra@redhat.com> <5570A158.5080305@exadel.com> Message-ID: On 4 Jun 2015, at 21:04, Alexey Kazakov wrote: > Hi, > > I just merged a PR for https://issues.jboss.org/browse/JBIDE-19500 ( A > warning dialog if we detect JBT/JBDS is run on unsupported JVM) > This PR introduces a new plugin in foundation (jbosstools-base repo): > *org.jboss.tools.foundation.checkup* which is a requirements for > o.j.t.foundation.core which means it's a requirements for almost every > JBT plugin. > So don't be surprised if your dev workspace is not compatible any more > after jbosstools-base pull from master ;) thanks for the headsup - but it makes web services tests fail since it NPE's on startup: https://issues.jboss.org/browse/JBIDE-19943 we need that fixed ;) /max http://about.me/maxandersen From manderse at redhat.com Fri Jun 5 02:59:57 2015 From: manderse at redhat.com (manderse at redhat.com) Date: Fri, 5 Jun 2015 02:59:57 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201506050659.t556xv6H028491@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-19944 https://issues.jboss.org/browse/JBIDE-19944 Summary: JBoss Central URL's need rewiring since yahoo pipes is shutting down Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:42:16.525451 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27 From manderse at redhat.com Fri Jun 5 05:14:00 2015 From: manderse at redhat.com (manderse at redhat.com) Date: Fri, 5 Jun 2015 05:14:00 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201506050914.t559E0Hu030119@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-19944 https://issues.jboss.org/browse/JBIDE-19944 Summary: JBoss Central URL's need rewiring since yahoo pipes is shutting down Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 10:56:19.135010 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=%28filter%3D%27ds_lint_nocomponent%27%29 From mmalina at redhat.com Fri Jun 5 09:32:42 2015 From: mmalina at redhat.com (Martin Malina) Date: Fri, 5 Jun 2015 15:32:42 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: test-drive Tycho 0.23.0 In-Reply-To: <5567AB85.9070807@redhat.com> References: <55675511.50408@gmail.com> <8A06C6CA-C8C1-41C3-97E6-2621D2300166@redhat.com> <5567AB85.9070807@redhat.com> Message-ID: I tried to compile Integration Tests [1] with Tycho 0.23.0 and I got this compilation error. [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.mylyn.ui.bot.test: Compilation failure: Compilation failure: [ERROR] /Users/rasp/git/jbosstools-integration-tests/tests/org.jboss.tools.mylyn.ui.bot.test/src/org/jboss/tools/mylyn/ui/bot/test/MylynTestLocalRepo.java:[135] [ERROR] DefaultTreeItem theTask = new DefaultTreeItem ("Uncategorized", UPDATED_TASKNAME); [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] The type org.eclipse.swt.widgets.TreeItem cannot be resolved. It is indirectly referenced from required .class files [ERROR] 1 problem (1 error) [ERROR] -> [Help 1] I looked at the release notes [2] and haven't found out what's causing this yet. -Martin [1] https://github.com/jbosstools/jbosstools-integration-tests [2] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > On 29. 5. 2015, at 1:57, Nick Boldt wrote: > > Yes, we switched to Tycho 0.23.0-SNAPSHOT for JBDS product build on > April 24: > > https://github.com/jbdevstudio/jbdevstudio-product/commit/bd5456c5a89eec705178d5e376a5bc41395f8436#diff-600376dffeb79835ede4a0b285078036R54 > > But for the rest of JBT, we're still on 0.22.0: > > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L23 > > > On 05/28/2015 07:40 PM, Max Rydahl Andersen wrote: >> I thought we already were using Tyco 0.23, at least for the eclipse >> product build? >> >> One gotcha is that https://wiki.eclipse.org/Tycho/Release_Notes/0.23#p2 >> might break >> Integration Stack if they build against non-Mars. So just something for >> IS to be aware of >> if they need to override it until tycho 0.24 is out. >> >> /max >> >>> Soon, Tycho 0.23.0 will be available. >>> >>> If possible, I'd like to build JBT 4.3.0.Beta1 / JBDS 9.0.0.Beta1 >>> using >>> Tycho 0.23.0. >>> >>> If you add the code below to your settings.xml, then build with >>> -DtychoVersion=0.23.0, you'll be able to see if anything breaks w/ >>> Tycho >>> 0.23.0. >>> >>> If it does, please open a JIRA. >>> >>> Thanks! >>> >>> >>> -------- Forwarded Message -------- >>> Subject: [tycho-user] Tycho 0.23.0 staged >>> Date: Thu, 28 May 2015 16:07:55 +0000 >>> From: Sievers, Jan >>> Reply-To: Tycho user list >>> To: Tycho user list (tycho-user at eclipse.org) >>> CC: Tycho developers list (tycho-dev at eclipse.org) >>> >>> >>> Tycho milestone release 0.23.0 has been staged. >>> >>> For details of new features and bugfixes, see release notes [1]. >>> Please help by testing the staged milestone build. To use it, change >>> your tycho version to 0.23.0 and add snippet [2] to your pom. >>> >>> NOTE: if you build products for MacOSX against p2 repositories older >>> than eclipse Mars, there is a known bug [3] >>> >>> We plan to promote this release in one week unless major regressions >>> are >>> found. >>> >>> Regards, >>> Tycho team >>> >>> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 >>> [2] >>> >>> >>> tycho-staged >>> >>> https://oss.sonatype.org/content/repositories/orgeclipsetycho-1021/ >>> >>> >>> >>> [3] https://wiki.eclipse.org/Tycho/Release_Notes/0.23#p2 >>> >>> _______________________________________________ >>> tycho-user mailing list >>> tycho-user at eclipse.org >>> To change your delivery options, retrieve your password, or >>> unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/tycho-user >>> >>> >>> _______________________________________________ >>> 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 > _______________________________________________ > 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/20150605/99e36d7f/attachment-0001.html From nboldt at redhat.com Fri Jun 5 10:33:04 2015 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 05 Jun 2015 10:33:04 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: test-drive Tycho 0.23.0 In-Reply-To: References: <55675511.50408@gmail.com> <8A06C6CA-C8C1-41C3-97E6-2621D2300166@redhat.com> <5567AB85.9070807@redhat.com> Message-ID: <5571B320.5070608@redhat.com> Is it an access restriction error? Are you using JDK 7 or 8? Do you set testSuite or testClass anywhere in your poms? Have you tried building with -DfailIfNoTests=false ? Did something change in o.e.swt.widgets.TreeItem in Mars? On 06/05/2015 09:32 AM, Martin Malina wrote: > I tried to compile Integration Tests [1] with Tycho 0.23.0 and I got > this compilation error. > > [ERROR] Failed to execute goal > org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) > on project org.jboss.tools.mylyn.ui.bot.test: Compilation > failure: Compilation failure: > [ERROR] > /Users/rasp/git/jbosstools-integration-tests/tests/org.jboss.tools.mylyn.ui.bot.test/src/org/jboss/tools/mylyn/ui/bot/test/MylynTestLocalRepo.java:[135] > [ERROR] DefaultTreeItem theTask = new DefaultTreeItem ("Uncategorized", > UPDATED_TASKNAME); > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The type org.eclipse.swt.widgets.TreeItem cannot be resolved. It > is indirectly referenced from required .class files > [ERROR] 1 problem (1 error) > [ERROR] -> [Help 1] > > I looked at the release notes [2] and haven't found out what's causing > this yet. > > -Martin > > [1] https://github.com/jbosstools/jbosstools-integration-tests > [2] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > > >> On 29. 5. 2015, at 1:57, Nick Boldt > > wrote: >> >> Yes, we switched to Tycho 0.23.0-SNAPSHOT for JBDS product build on >> April 24: >> >> https://github.com/jbdevstudio/jbdevstudio-product/commit/bd5456c5a89eec705178d5e376a5bc41395f8436#diff-600376dffeb79835ede4a0b285078036R54 >> >> But for the rest of JBT, we're still on 0.22.0: >> >> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L23 >> >> >> On 05/28/2015 07:40 PM, Max Rydahl Andersen wrote: >>> I thought we already were using Tyco 0.23, at least for the eclipse >>> product build? >>> >>> One gotcha is that https://wiki.eclipse.org/Tycho/Release_Notes/0.23#p2 >>> might break >>> Integration Stack if they build against non-Mars. So just something for >>> IS to be aware of >>> if they need to override it until tycho 0.24 is out. >>> >>> /max >>> >>>> Soon, Tycho 0.23.0 will be available. >>>> >>>> If possible, I'd like to build JBT 4.3.0.Beta1 / JBDS 9.0.0.Beta1 >>>> using >>>> Tycho 0.23.0. >>>> >>>> If you add the code below to your settings.xml, then build with >>>> -DtychoVersion=0.23.0, you'll be able to see if anything breaks w/ >>>> Tycho >>>> 0.23.0. >>>> >>>> If it does, please open a JIRA. >>>> >>>> Thanks! >>>> >>>> >>>> -------- Forwarded Message -------- >>>> Subject: [tycho-user] Tycho 0.23.0 staged >>>> Date: Thu, 28 May 2015 16:07:55 +0000 >>>> From: Sievers, Jan >>>> Reply-To: Tycho user list >>>> To: Tycho user list (tycho-user at eclipse.org) >>>> CC: Tycho developers list (tycho-dev at eclipse.org) >>>> >>>> >>>> Tycho milestone release 0.23.0 has been staged. >>>> >>>> For details of new features and bugfixes, see release notes [1]. >>>> Please help by testing the staged milestone build. To use it, change >>>> your tycho version to 0.23.0 and add snippet [2] to your pom. >>>> >>>> NOTE: if you build products for MacOSX against p2 repositories older >>>> than eclipse Mars, there is a known bug [3] >>>> >>>> We plan to promote this release in one week unless major regressions >>>> are >>>> found. >>>> >>>> Regards, >>>> Tycho team >>>> >>>> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 >>>> [2] >>>> >>>> >>>> tycho-staged >>>> >>>> https://oss.sonatype.org/content/repositories/orgeclipsetycho-1021/ >>>> >>>> >>>> >>>> [3] https://wiki.eclipse.org/Tycho/Release_Notes/0.23#p2 >>>> >>>> _______________________________________________ >>>> tycho-user mailing list >>>> tycho-user at eclipse.org >>>> To change your delivery options, retrieve your password, or >>>> unsubscribe >>>> from this list, visit >>>> https://dev.eclipse.org/mailman/listinfo/tycho-user >>>> >>>> >>>> _______________________________________________ >>>> 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 >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Jun 5 18:20:24 2015 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 05 Jun 2015 18:20:24 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing Message-ID: <557220A8.2020106@redhat.com> As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/mars/staging/updates/ Target platform: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Beta1-SNAPSHOT (not yet released - still SNAPSHOT) New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Additional update sites: * http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1/ * http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Beta1/ * http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Beta1/ -- Discovery sites: * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1/ * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1/ Due to a bug when building Base (JBIDE-19919), foundation.core thinks it's Beta2, not Beta1. So, to ensure you're seeing the correct version of Central (from Beta1 / Beta1x, not Beta2 / master), you may need to add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1/ -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1/jbosstools-earlyaccess.properties This can be fixed w/ a respin of Base and all the aggregate sites that include Base. -- Build folders (for build logs & update site zips): * http://download.jboss.org/jbosstools/mars/staging/builds/ -- Oh, and just a heads up... the Java EE package isn't shown on the Eclipse Downloads page for Mars 4.5.0.RC3 - only the plain Java package is shown. However, the RC2 one exists here: https://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/marsrc2 If you want the RC3 bits, they're here: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/mars/RC3/eclipse-jee-mars-RC3-linux-gtk-x86_64.tar.gz http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/mars/RC3/eclipse-jee-mars-RC3-macosx-cocoa-x86_64.tar.gz http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/mars/RC3/eclipse-jee-mars-RC3-win32-x86_64.zip -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nickboldt at gmail.com Mon Jun 8 09:28:16 2015 From: nickboldt at gmail.com (Nick Boldt) Date: Mon, 08 Jun 2015 09:28:16 -0400 Subject: [jbosstools-dev] Fwd: [tycho-user] Tycho milestone 0.23.0 released In-Reply-To: References: Message-ID: <55759870.9000803@gmail.com> FYI, Tycho 0.23 is released. We should move up to using this in master branch. https://issues.jboss.org/browse/JBIDE-19973 -------- Forwarded Message -------- Subject: [tycho-user] Tycho milestone 0.23.0 released Date: Mon, 8 Jun 2015 07:34:48 +0000 From: Sievers, Jan Reply-To: Tycho user list To: Tycho user list (tycho-user at eclipse.org) , Tycho developers list (tycho-dev at eclipse.org) Tycho milestone 0.23.0 has been released and is available from maven central. See the release notes [1] for details of enhancements and bug fixes in this release. Thanks to Christian Dietrich Enrico De Fent Christian Georgi Michael Keppler Pascal Rapicault Gunnar Wagenknecht who contributed patches for this release. And thanks and to everyone who helped us with testing the staged version. Regards, Tycho team [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 _______________________________________________ tycho-user mailing list tycho-user at eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/tycho-user From pleacu at redhat.com Mon Jun 8 16:13:36 2015 From: pleacu at redhat.com (Paul Leacu) Date: Mon, 8 Jun 2015 16:13:36 -0400 (EDT) Subject: [jbosstools-dev] Proposed change for JBTIS target platform - 4.3.0.Beta1 In-Reply-To: <83264958.11448186.1433791816658.JavaMail.zimbra@redhat.com> Message-ID: <2048655044.11464496.1433794416186.JavaMail.zimbra@redhat.com> Greetings - A proposal to change the Mars JBTIS 4.3.0 target platform is described here: https://issues.jboss.org/browse/JBTIS-445 PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/371 Synopsis: 1. Update https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/targetplatforms/jbosstools-multiple/4.50.0.Beta1-SNAPSHOT/ 2. Update http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1/ 3. Update http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.4.Final/ 4. Update http://download.jboss.org/jbosstools/updates/requirements/mars/201505291000-RC2/ Please respond by 12:00 EDT on Tuesday, June 8 to the specified Jira if there are any issues. Thanks, --paull From dgolovin at exadel.com Mon Jun 8 18:45:53 2015 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 8 Jun 2015 15:45:53 -0700 Subject: [jbosstools-dev] Fwd: [tycho-user] Tycho milestone 0.23.0 released In-Reply-To: <55759870.9000803@gmail.com> References: <55759870.9000803@gmail.com> Message-ID: +1 On Mon, Jun 8, 2015 at 6:28 AM, Nick Boldt wrote: > FYI, Tycho 0.23 is released. > > We should move up to using this in master branch. > > https://issues.jboss.org/browse/JBIDE-19973 > > > -------- Forwarded Message -------- > Subject: [tycho-user] Tycho milestone 0.23.0 released > Date: Mon, 8 Jun 2015 07:34:48 +0000 > From: Sievers, Jan > Reply-To: Tycho user list > To: Tycho user list (tycho-user at eclipse.org) , > Tycho developers list (tycho-dev at eclipse.org) > > Tycho milestone 0.23.0 has been released and is available from maven > central. > > See the release notes [1] for details of enhancements and bug fixes in > this release. > > Thanks to > > Christian Dietrich > Enrico De Fent > Christian Georgi > Michael Keppler > Pascal Rapicault > Gunnar Wagenknecht > > who contributed patches for this release. > > And thanks and to everyone who helped us with testing the staged version. > > Regards, > Tycho team > > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > _______________________________________________ > tycho-user mailing list > tycho-user at eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/tycho-user > > > _______________________________________________ > 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/20150608/83a6ca8f/attachment.html From nboldt at redhat.com Mon Jun 8 21:06:48 2015 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 08 Jun 2015 21:06:48 -0400 Subject: [jbosstools-dev] Fwd: [tycho-user] Tycho milestone 0.23.0 released In-Reply-To: References: <55759870.9000803@gmail.com> Message-ID: <55763C28.8020107@redhat.com> Does that by any chance mean you've successfully built the whole stack w/ 0.23.0, including JBDS? On 06/08/2015 06:45 PM, Denis Golovin wrote: > +1 > > On Mon, Jun 8, 2015 at 6:28 AM, Nick Boldt > wrote: > > FYI, Tycho 0.23 is released. > > We should move up to using this in master branch. > > https://issues.jboss.org/browse/JBIDE-19973 > > > -------- Forwarded Message -------- > Subject: [tycho-user] Tycho milestone 0.23.0 released > Date: Mon, 8 Jun 2015 07:34:48 +0000 > From: Sievers, Jan > > Reply-To: Tycho user list > > To: Tycho user list (tycho-user at eclipse.org > ) >, > Tycho developers list (tycho-dev at eclipse.org > ) > > > Tycho milestone 0.23.0 has been released and is available from maven > central. > > See the release notes [1] for details of enhancements and bug fixes in > this release. > > Thanks to > > Christian Dietrich > Enrico De Fent > Christian Georgi > Michael Keppler > Pascal Rapicault > Gunnar Wagenknecht > > who contributed patches for this release. > > And thanks and to everyone who helped us with testing the staged > version. > > Regards, > Tycho team > > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > _______________________________________________ > tycho-user mailing list > tycho-user at eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/tycho-user > > > _______________________________________________ > 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 mmalina at redhat.com Tue Jun 9 04:12:11 2015 From: mmalina at redhat.com (Martin Malina) Date: Tue, 9 Jun 2015 10:12:11 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: test-drive Tycho 0.23.0 In-Reply-To: <5571B320.5070608@redhat.com> References: <55675511.50408@gmail.com> <8A06C6CA-C8C1-41C3-97E6-2621D2300166@redhat.com> <5567AB85.9070807@redhat.com> <5571B320.5070608@redhat.com> Message-ID: <75D359DF-960C-4F5E-A6C4-3CD115712E6B@redhat.com> > On 5. 6. 2015, at 16:33, Nick Boldt wrote: > > Is it an access restriction error? I don't know, but why would Tycho version change this? > Are you using JDK 7 or 8? One thing is for sure, it works with Tycho 0.22.0 ;) I get this error with Tycho 0.23.0 with both java 7 and 8 (on my Mac). > Do you set testSuite or testClass anywhere in your poms? There is both testSuite and testClass set in the pom, but that doesn't seem to be the problem (I tried removing the testSuite). > Have you tried building with -DfailIfNoTests=false ? Yes, but no luck. > Did something change in o.e.swt.widgets.TreeItem in Mars? How is that relevant? I'm only changing Tycho, not the underlying TP - it works with current master. It's Len's test, so I hoped he might have some idea. -Martin > On 06/05/2015 09:32 AM, Martin Malina wrote: >> I tried to compile Integration Tests [1] with Tycho 0.23.0 and I got >> this compilation error. >> >> [ERROR] Failed to execute goal >> org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) >> on project org.jboss.tools.mylyn.ui.bot.test: Compilation >> failure: Compilation failure: >> [ERROR] >> /Users/rasp/git/jbosstools-integration-tests/tests/org.jboss.tools.mylyn.ui.bot.test/src/org/jboss/tools/mylyn/ui/bot/test/MylynTestLocalRepo.java:[135] >> [ERROR] DefaultTreeItem theTask = new DefaultTreeItem ("Uncategorized", >> UPDATED_TASKNAME); >> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> [ERROR] The type org.eclipse.swt.widgets.TreeItem cannot be resolved. It >> is indirectly referenced from required .class files >> [ERROR] 1 problem (1 error) >> [ERROR] -> [Help 1] >> >> I looked at the release notes [2] and haven't found out what's causing >> this yet. >> >> -Martin >> >> [1] https://github.com/jbosstools/jbosstools-integration-tests >> [2] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 >> >> >>> On 29. 5. 2015, at 1:57, Nick Boldt >> >> wrote: >>> >>> Yes, we switched to Tycho 0.23.0-SNAPSHOT for JBDS product build on >>> April 24: >>> >>> https://github.com/jbdevstudio/jbdevstudio-product/commit/bd5456c5a89eec705178d5e376a5bc41395f8436#diff-600376dffeb79835ede4a0b285078036R54 >>> >>> But for the rest of JBT, we're still on 0.22.0: >>> >>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L23 >>> >>> >>> On 05/28/2015 07:40 PM, Max Rydahl Andersen wrote: >>>> I thought we already were using Tyco 0.23, at least for the eclipse >>>> product build? >>>> >>>> One gotcha is that https://wiki.eclipse.org/Tycho/Release_Notes/0.23#p2 >>>> might break >>>> Integration Stack if they build against non-Mars. So just something for >>>> IS to be aware of >>>> if they need to override it until tycho 0.24 is out. >>>> >>>> /max >>>> >>>>> Soon, Tycho 0.23.0 will be available. >>>>> >>>>> If possible, I'd like to build JBT 4.3.0.Beta1 / JBDS 9.0.0.Beta1 >>>>> using >>>>> Tycho 0.23.0. >>>>> >>>>> If you add the code below to your settings.xml, then build with >>>>> -DtychoVersion=0.23.0, you'll be able to see if anything breaks w/ >>>>> Tycho >>>>> 0.23.0. >>>>> >>>>> If it does, please open a JIRA. >>>>> >>>>> Thanks! >>>>> >>>>> >>>>> -------- Forwarded Message -------- >>>>> Subject: [tycho-user] Tycho 0.23.0 staged >>>>> Date: Thu, 28 May 2015 16:07:55 +0000 >>>>> From: Sievers, Jan > >>>>> Reply-To: Tycho user list > >>>>> To: Tycho user list (tycho-user at eclipse.org ) > >>>>> CC: Tycho developers list (tycho-dev at eclipse.org ) >>>>> > >>>>> >>>>> Tycho milestone release 0.23.0 has been staged. >>>>> >>>>> For details of new features and bugfixes, see release notes [1]. >>>>> Please help by testing the staged milestone build. To use it, change >>>>> your tycho version to 0.23.0 and add snippet [2] to your pom. >>>>> >>>>> NOTE: if you build products for MacOSX against p2 repositories older >>>>> than eclipse Mars, there is a known bug [3] >>>>> >>>>> We plan to promote this release in one week unless major regressions >>>>> are >>>>> found. >>>>> >>>>> Regards, >>>>> Tycho team >>>>> >>>>> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 >>>>> [2] >>>>> >>>>> >>>>> tycho-staged >>>>> >>>>> https://oss.sonatype.org/content/repositories/orgeclipsetycho-1021/ >>>>> >>>>> >>>>> >>>>> [3] https://wiki.eclipse.org/Tycho/Release_Notes/0.23#p2 >>>>> >>>>> _______________________________________________ >>>>> tycho-user mailing list >>>>> tycho-user at eclipse.org >>>>> To change your delivery options, retrieve your password, or >>>>> unsubscribe >>>>> from this list, visit >>>>> https://dev.eclipse.org/mailman/listinfo/tycho-user >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150609/4424dc9a/attachment.html From mistria at redhat.com Tue Jun 9 07:45:26 2015 From: mistria at redhat.com (Mickael Istria) Date: Tue, 09 Jun 2015 13:45:26 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: test-drive Tycho 0.23.0 In-Reply-To: <75D359DF-960C-4F5E-A6C4-3CD115712E6B@redhat.com> References: <55675511.50408@gmail.com> <8A06C6CA-C8C1-41C3-97E6-2621D2300166@redhat.com> <5567AB85.9070807@redhat.com> <5571B320.5070608@redhat.com> <75D359DF-960C-4F5E-A6C4-3CD115712E6B@redhat.com> Message-ID: <5576D1D6.7070000@redhat.com> Hi Martin, hi all, Just remove from the failing pom.xml the target-platform-configuration block, which is probably useless at that time. Moreover, this block contains the macosx/cocoa/x86 configuration which isn't supported by Eclipse nor JBoss Tools any more. Once this is cleaned up, everything works as expected. My idea on this is that in Tycho 0.23, you probably get access to the intersection of the available classes for provided os/ws/arch. Since this bundle was specifying some unsupported configurations, it made the intersection empty, and some classes were hidden to the compiler. This might be caused by a change in Equinox/p2 which has cascaded to Tycho classpath computation. From mistria at redhat.com Tue Jun 9 08:49:02 2015 From: mistria at redhat.com (Mickael Istria) Date: Tue, 09 Jun 2015 14:49:02 +0200 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: <557220A8.2020106@redhat.com> References: <557220A8.2020106@redhat.com> Message-ID: <5576E0BE.7010303@redhat.com> Just to make everyone aware of it: there are already some major issues that will require an respin: https://issues.jboss.org/issues/?jql=labels%20%3D%20respin-a%20and%20project%20in%20%28JBDS%2C%20JBIDE%29%20and%20fixVersion%20in%20%289.0.0.Beta1%2C%204.3.0.Beta1%29 -- 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/20150609/1ae29180/attachment.html From nboldt at redhat.com Tue Jun 9 09:18:02 2015 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 09 Jun 2015 09:18:02 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: <5576E0BE.7010303@redhat.com> References: <557220A8.2020106@redhat.com> <5576E0BE.7010303@redhat.com> Message-ID: <5576E78A.1020108@redhat.com> Unless we need it sooner, I was thinking a respin this Friday night (with bits for QE on Monday) would be a reasonable time to do the respin-a. On 06/09/2015 08:49 AM, Mickael Istria wrote: > Just to make everyone aware of it: there are already some major issues > that will require an respin: > https://issues.jboss.org/issues/?jql=labels%20%3D%20respin-a%20and%20project%20in%20%28JBDS%2C%20JBIDE%29%20and%20fixVersion%20in%20%289.0.0.Beta1%2C%204.3.0.Beta1%29 > > -- > 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 ggastald at redhat.com Tue Jun 9 09:55:48 2015 From: ggastald at redhat.com (George Gastaldi) Date: Tue, 9 Jun 2015 09:55:48 -0400 (EDT) Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: <5576E78A.1020108@redhat.com> References: <557220A8.2020106@redhat.com> <5576E0BE.7010303@redhat.com> <5576E78A.1020108@redhat.com> Message-ID: I'd like to add JBIDE-19967 to the list of this respin. This was requested by the camel team and it would be nice to have it before summit. Best Regards, George Gastaldi
-------- Mensagem original --------
De: Nick Boldt
Data: 09/06/2015 10:18 (GMT-03:00)
Para: Mickael Istria , jbosstools-dev at lists.jboss.org
Assunto: Re: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing
Unless we need it sooner, I was thinking a respin this Friday night (with bits for QE on Monday) would be a reasonable time to do the respin-a. On 06/09/2015 08:49 AM, Mickael Istria wrote: > Just to make everyone aware of it: there are already some major issues > that will require an respin: > https://issues.jboss.org/issues/?jql=labels%20%3D%20respin-a%20and%20project%20in%20%28JBDS%2C%20JBIDE%29%20and%20fixVersion%20in%20%289.0.0.Beta1%2C%204.3.0.Beta1%29 > > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com _______________________________________________ jbosstools-dev mailing list jbosstools-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150609/b454fca1/attachment.html From mistria at redhat.com Tue Jun 9 10:32:01 2015 From: mistria at redhat.com (Mickael Istria) Date: Tue, 09 Jun 2015 16:32:01 +0200 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: References: <557220A8.2020106@redhat.com> <5576E0BE.7010303@redhat.com> <5576E78A.1020108@redhat.com> Message-ID: <5576F8E1.8050503@redhat.com> On 06/09/2015 03:55 PM, George Gastaldi wrote: > I'd like to add JBIDE-19967 to the list of this respin. This was > requested by the camel team and it would be nice to have it before summit. Can you please link to the commit that fixes it on Jira, to make sure it doesn't introduce any risk on the branch? -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150609/5473ce2d/attachment.html From nboldt at redhat.com Tue Jun 9 10:56:13 2015 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 09 Jun 2015 10:56:13 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: <5576F8E1.8050503@redhat.com> References: <557220A8.2020106@redhat.com> <5576E0BE.7010303@redhat.com> <5576E78A.1020108@redhat.com> <5576F8E1.8050503@redhat.com> Message-ID: <5576FE8D.1030805@redhat.com> I can only see one commit with "JBIDE-19967" [1] in its commit comments: https://github.com/jbosstools/jbosstools-forge/commit/a849daac2741dccfd7f6261668c38c88fdf3df43 This was only applied in master, however. Do you plan to backport it to to the Beta1x branch? [1] https://issues.jboss.org/browse/JBIDE-19967 On 06/09/2015 10:32 AM, Mickael Istria wrote: > On 06/09/2015 03:55 PM, George Gastaldi wrote: >> I'd like to add JBIDE-19967 to the list of this respin. This was >> requested by the camel team and it would be nice to have it before summit. > Can you please link to the commit that fixes it on Jira, to make sure it > doesn't introduce any risk on the branch? > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Tue Jun 9 10:58:43 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 09 Jun 2015 16:58:43 +0200 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: References: <557220A8.2020106@redhat.com> <5576E0BE.7010303@redhat.com> <5576E78A.1020108@redhat.com> Message-ID: <617E49D2-B192-42F6-8998-66CA81FFB893@redhat.com> On 9 Jun 2015, at 15:55, George Gastaldi wrote: > I'd like to add JBIDE-19967 to the list of this respin. This was > requested by the camel team and it would be nice to have it before > summit. Are the camel team even on JBDS 9 ? good news if they are ;) btw. I really don't like UI that requires this much notes to be understandable...but I don't have a better suggestion when it has to fit in both graphical UI and a CLI. But as stated, please put it into beta1x branch if want to include it. /max > Best Regards, > George Gastaldi
>
>
-------- Mensagem original --------
De: Nick > Boldt
Data: 09/06/2015 10:18 > (GMT-03:00)
Para: Mickael Istria , > jbosstools-dev at lists.jboss.org
Assunto: Re: > [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE > testing
>
Unless we need it sooner, I was thinking a respin this Friday > night > (with bits for QE on Monday) would be a reasonable time to do the > respin-a. > > On 06/09/2015 08:49 AM, Mickael Istria wrote: >> Just to make everyone aware of it: there are already some major >> issues >> that will require an respin: >> https://issues.jboss.org/issues/?jql=labels%20%3D%20respin-a%20and%20project%20in%20%28JBDS%2C%20JBIDE%29%20and%20fixVersion%20in%20%289.0.0.Beta1%2C%204.3.0.Beta1%29 >> >> -- >> Mickael Istria >> Eclipse developer at JBoss, by Red Hat >> My blog - My Tweets >> >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From ggastald at redhat.com Tue Jun 9 11:02:42 2015 From: ggastald at redhat.com (George Gastaldi) Date: Tue, 09 Jun 2015 12:02:42 -0300 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: <5576FE8D.1030805@redhat.com> References: <557220A8.2020106@redhat.com> <5576E0BE.7010303@redhat.com> <5576E78A.1020108@redhat.com> <5576F8E1.8050503@redhat.com> <5576FE8D.1030805@redhat.com> Message-ID: <55770012.40203@redhat.com> Yes, should I provide a PR? On 06/09/2015 11:56 AM, Nick Boldt wrote: > I can only see one commit with "JBIDE-19967" [1] in its commit comments: > > https://github.com/jbosstools/jbosstools-forge/commit/a849daac2741dccfd7f6261668c38c88fdf3df43 > > > This was only applied in master, however. Do you plan to backport it > to to the Beta1x branch? > > [1] https://issues.jboss.org/browse/JBIDE-19967 > > On 06/09/2015 10:32 AM, Mickael Istria wrote: >> On 06/09/2015 03:55 PM, George Gastaldi wrote: >>> I'd like to add JBIDE-19967 to the list of this respin. This was >>> requested by the camel team and it would be nice to have it before >>> summit. >> Can you please link to the commit that fixes it on Jira, to make sure it >> doesn't introduce any risk on the branch? >> -- >> Mickael Istria >> Eclipse developer at JBoss, by Red Hat >> My blog - My Tweets >> > From nboldt at redhat.com Tue Jun 9 11:09:54 2015 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 09 Jun 2015 11:09:54 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: <55770012.40203@redhat.com> References: <557220A8.2020106@redhat.com> <5576E0BE.7010303@redhat.com> <5576E78A.1020108@redhat.com> <5576F8E1.8050503@redhat.com> <5576FE8D.1030805@redhat.com> <55770012.40203@redhat.com> Message-ID: <557701C2.8010709@redhat.com> PRs are generally required to push changes into stable branches after code freeze, so yes, if you don't mind, that would be awesome. And attach it to the JIRA, please. :D Nick On 06/09/2015 11:02 AM, George Gastaldi wrote: > Yes, should I provide a PR? > > On 06/09/2015 11:56 AM, Nick Boldt wrote: >> I can only see one commit with "JBIDE-19967" [1] in its commit comments: >> >> https://github.com/jbosstools/jbosstools-forge/commit/a849daac2741dccfd7f6261668c38c88fdf3df43 >> >> >> This was only applied in master, however. Do you plan to backport it >> to to the Beta1x branch? >> >> [1] https://issues.jboss.org/browse/JBIDE-19967 >> >> On 06/09/2015 10:32 AM, Mickael Istria wrote: >>> On 06/09/2015 03:55 PM, George Gastaldi wrote: >>>> I'd like to add JBIDE-19967 to the list of this respin. This was >>>> requested by the camel team and it would be nice to have it before >>>> summit. >>> Can you please link to the commit that fixes it on Jira, to make sure it >>> doesn't introduce any risk on the branch? >>> -- >>> Mickael Istria >>> Eclipse developer at JBoss, by Red Hat >>> My blog - My Tweets >>> >> > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From ggastald at redhat.com Tue Jun 9 11:11:06 2015 From: ggastald at redhat.com (George Gastaldi) Date: Tue, 09 Jun 2015 12:11:06 -0300 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1 bits available for QE testing In-Reply-To: <557701C2.8010709@redhat.com> References: <557220A8.2020106@redhat.com> <5576E0BE.7010303@redhat.com> <5576E78A.1020108@redhat.com> <5576F8E1.8050503@redhat.com> <5576FE8D.1030805@redhat.com> <55770012.40203@redhat.com> <557701C2.8010709@redhat.com> Message-ID: <5577020A.1060801@redhat.com> No problem, Here is the PR: https://github.com/jbosstools/jbosstools-forge/pull/141 I added a comment in JIRA with this URL. Thank you very much, you guys rock! George Gastaldi On 06/09/2015 12:09 PM, Nick Boldt wrote: > PRs are generally required to push changes into stable branches after > code freeze, so yes, if you don't mind, that would be awesome. > > And attach it to the JIRA, please. :D > > Nick > > On 06/09/2015 11:02 AM, George Gastaldi wrote: >> Yes, should I provide a PR? >> >> On 06/09/2015 11:56 AM, Nick Boldt wrote: >>> I can only see one commit with "JBIDE-19967" [1] in its commit >>> comments: >>> >>> https://github.com/jbosstools/jbosstools-forge/commit/a849daac2741dccfd7f6261668c38c88fdf3df43 >>> >>> >>> >>> This was only applied in master, however. Do you plan to backport it >>> to to the Beta1x branch? >>> >>> [1] https://issues.jboss.org/browse/JBIDE-19967 >>> >>> On 06/09/2015 10:32 AM, Mickael Istria wrote: >>>> On 06/09/2015 03:55 PM, George Gastaldi wrote: >>>>> I'd like to add JBIDE-19967 to the list of this respin. This was >>>>> requested by the camel team and it would be nice to have it before >>>>> summit. >>>> Can you please link to the commit that fixes it on Jira, to make >>>> sure it >>>> doesn't introduce any risk on the branch? >>>> -- >>>> Mickael Istria >>>> Eclipse developer at JBoss, by Red Hat >>>> My blog - My Tweets >>>> >>> >> > From dgolovin at exadel.com Tue Jun 9 13:25:35 2015 From: dgolovin at exadel.com (Denis Golovin) Date: Tue, 9 Jun 2015 10:25:35 -0700 Subject: [jbosstools-dev] Fwd: [tycho-user] Tycho milestone 0.23.0 released In-Reply-To: <55763C28.8020107@redhat.com> References: <55759870.9000803@gmail.com> <55763C28.8020107@redhat.com> Message-ID: I did it many times with 0.23.0-SNAPSHOT. On Mon, Jun 8, 2015 at 6:06 PM, Nick Boldt wrote: > Does that by any chance mean you've successfully built the whole stack > w/ 0.23.0, including JBDS? > > On 06/08/2015 06:45 PM, Denis Golovin wrote: > > +1 > > > > On Mon, Jun 8, 2015 at 6:28 AM, Nick Boldt > > wrote: > > > > FYI, Tycho 0.23 is released. > > > > We should move up to using this in master branch. > > > > https://issues.jboss.org/browse/JBIDE-19973 > > > > > > -------- Forwarded Message -------- > > Subject: [tycho-user] Tycho milestone 0.23.0 released > > Date: Mon, 8 Jun 2015 07:34:48 +0000 > > From: Sievers, Jan >> > > Reply-To: Tycho user list > > > > To: Tycho user list (tycho-user at eclipse.org > > ) > >, > > Tycho developers list (tycho-dev at eclipse.org > > ) > > > > > > Tycho milestone 0.23.0 has been released and is available from maven > > central. > > > > See the release notes [1] for details of enhancements and bug fixes > in > > this release. > > > > Thanks to > > > > Christian Dietrich > > Enrico De Fent > > Christian Georgi > > Michael Keppler > > Pascal Rapicault > > Gunnar Wagenknecht > > > > who contributed patches for this release. > > > > And thanks and to everyone who helped us with testing the staged > > version. > > > > Regards, > > Tycho team > > > > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > > _______________________________________________ > > tycho-user mailing list > > tycho-user at eclipse.org > > To change your delivery options, retrieve your password, or > unsubscribe > > from this list, visit > > https://dev.eclipse.org/mailman/listinfo/tycho-user > > > > > > _______________________________________________ > > jbosstools-dev mailing list > > jbosstools-dev at lists.jboss.org 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150609/2349b150/attachment.html From manderse at redhat.com Wed Jun 10 05:07:43 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 10 Jun 2015 11:07:43 +0200 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... In-Reply-To: <55704B7E.9090905@redhat.com> References: <556F7C78.7070707@redhat.com> <556F84F3.1070204@redhat.com> <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> <55704B7E.9090905@redhat.com> Message-ID: <14E607DF-74FE-42A0-8D31-6FEF4588F2FB@redhat.com> On 4 Jun 2015, at 14:58, Nick Boldt wrote: > Versionwatch CAN be tweaked to add exceptions. We currently have 3 in > there for know issues where multiple versions were needed. > > But it doesn't validate IF those exclusions are still true. yes so it does not have anything to do with version watch tests failing. > For that we need to build everything, install everything, and see > what's broken. Suspect that some of these IUs MIGHT be needed for > something from Central. I didn't test-install that. Are you saying you removed IU's we have but did not run the tests we already have in place to verify such changes ? p2install and install grinder ? We made those to make this kind of thing easier to test/verify. Thus lets use them. /max > N > > On 06/04/2015 07:13 AM, Max Rydahl Andersen wrote: >> On 4 Jun 2015, at 0:51, Nick Boldt wrote: >> >>> JBDS built locally and installed fine. Resulting IUs in installation >>> (no >>> source bundles, as expected): >>> >>> javax.servlet.jsp_2.2.0.v201112011158.jar >>> javax.servlet_3.1.0.v201410161800.jar >>> org.apache.commons.lang_2.6.0.v201404270220.jar >>> >>> Can someone else verify this change is safe? >>> >>> Motivation here is to remove dupe IUs and therefore get a cleaner >>> install footprint >> >> if the separate versions are not required then that is a good reason. >> >>> , which will also make versionwatch builds blue again. >> >> I would rather fix version watch to be able to add exceptions for >> this rule >> since we most likely will end up with multiple versions of things - >> but >> that >> should only be marked okey if it is actually needed/wanted. >> >> I can't verify it easily today - maybe Denis can on his buildsetup ? >> >> /max >> >>> See also https://issues.jboss.org/browse/JBIDE-19605 >>> >>> On 06/03/2015 06:15 PM, Nick Boldt wrote: >>>> Currently building this locally and then will attempt to build JBDS >>>> with >>>> it: >>>> >>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/151 >>>> >>>> Resulting TP contains only a single version of these IUs (instead >>>> of >>>> multiple versions as we did in the past): >>>> >>>> javax.servlet_3.1.0.v201410161800.jar >>>> javax.servlet.jsp.source_2.2.0.v201112011158.jar >>>> javax.servlet.source_3.1.0.v201410161800.jar >>>> org.apache.commons.lang_2.6.0.v201404270220.jar >>>> org.apache.commons.lang.source_2.6.0.v201404270220.jar >>>> >>>> To build against local TP: >>>> >>>> mvn clean install -P hudson,eap,pack200 >>>> -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 >>>> -DJOB_NAME=devstudio.product_master >>>> -Dupdate.site.description="Development Milestone" >>>> -Djbosstools_site_stream=master -Dtpc.targetKind=unified >>>> -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ >>>> >>>> >>>> >>>> >>> >>> -- >>> 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 From noreply at igraszkifraszki.com Wed Jun 10 05:27:03 2015 From: noreply at igraszkifraszki.com (HQ-Canadian-Meds) Date: Wed, 10 Jun 2015 06:27:03 -0300 Subject: [jbosstools-dev] We'll show you the truth! There's no interdependence between medicine quality and its price! Message-ID: Wasnt going at this suspension. Aside, something perkins was ever. Cycles, or whose quality hadden een probleem zijn bovendien heel. Me ds 8f or 1M en Vi Ci Ci Le Pr ag al al vi op ra is is tr ec S a ia of t Ta bs $0 $1 $2 $2 $0 .9 .6 .5 .5 .4 9 5 0 0 5 Me ds 6f or 4W om en Ac Cl De Fe Fe om om fl ma ma pl id uc le le ia an C V ia ia li gr s a $1 $0 $1 $1 $0 .7 .4 .2 .1 .7 5 5 5 1 2 Vi 24 On 10 sa /7 ly 0% ,M c r A as us el ut te to ia he rc me bl nt ar r e ic d, su su M Ec pp pp ed he or li s ck t er s N A S F o no pe as pr ny ci t es mo al wo cr us i rl ip d nt dw ti el er id on iv ne e r er t sh eq y pr ip ui ic pi re es ng d >> Enter Here -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150610/b1923a3b/attachment-0001.html From adietish at redhat.com Wed Jun 10 09:35:22 2015 From: adietish at redhat.com (=?UTF-8?B?QW5kcsOpIERpZXRpc2hlaW0=?=) Date: Wed, 10 Jun 2015 15:35:22 +0200 Subject: [jbosstools-dev] submenus in CNF based viewer not showing up at times Message-ID: <55783D1A.7020004@redhat.com> Hi I have a issue with submenus in the OpenShift Explorer i have pretty much no clue about so far: https://issues.jboss.org/browse/JBIDE-20014 It's all about "New" and "Show In" submenus in a common navigator (OpenShift Explorer). They dont show up at times. The issue persists since quite a time now, it already existed when OpenShift was a simpler set of plugins only supporting OpenShift v2. Now with a new structure that consists of a common.ui plugin (which contribute the "New" and "Show in") and v2 and v3 plugins contributing items the error comes up more frequently. I removed "visibleWhen" expressions, removed contributions by the v2 and v3 plugins, keeping contributions in common.ui only - just to get a feeling for the issue. Those changes didnt have any effect. I am pretty clueless, the issue feels like a platform issue to me. I'd appreciate a lot if anyone had a clue about this, since it's quite critical to usability in OpenShift. Thanks! Andr? From nboldt at redhat.com Wed Jun 10 10:13:09 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 10 Jun 2015 10:13:09 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 41 unresolved issues to triage with fixversion = Beta1 Message-ID: <557845F5.6000803@redhat.com> Some of these issues are related to releasing Beta1 (eg., N&N, build-dependent things, QE tasks). But a lot are new functionality which needs to either be fixed as soon as possible (ASAP) as part of respin-a (which will happen this Friday night - Jun 12) or else need to be bumped to Beta2. Here's the list! https://issues.jboss.org/issues/?jql=filter%20%3D%20%27ds_freeze%27%20and%20filter%20%3D%20%27ds_unresolved%27 -- Related, here's the current list of Beta1 respin-a issues. If you have fixed something in the Beta1x branch and have NOT tagged that JIRA with a "respin-a" label, please do so ASAP. https://issues.jboss.org/issues/?jql=labels%20%3D%20respin-a%20and%20fixversion%20in%20%28%224.3.0.Beta1%22%2C%229.0.0.Beta1%22%29 (11 issues so far) -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Jun 10 10:17:26 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 10 Jun 2015 10:17:26 -0400 Subject: [jbosstools-dev] FYI: Beta1 respin-a will begin this Friday Jun 12 at 12:00 EDT / 18:00 CEST Message-ID: <557846F6.3020901@redhat.com> In case you missed it (ICYMI), JBT 4.3 / JBDS 9.0 Beta1 "respin-a" will be built this Friday Jun 12. Please have all your commits in by Friday around noon EDT (18:00 CEST), or ping me @nickboldt on IRC/Skype/email/twitter if you need more time. Here's the current list of Beta1 respin-a issues. https://issues.jboss.org/issues/?jql=labels%20%3D%20respin-a%20and%20fixversion%20in%20%28%224.3.0.Beta1%22%2C%229.0.0.Beta1%22%29 (11 issues so far) If you have fixed something in the Beta1x branch and have NOT tagged that JIRA with a "respin-a" label, please do so ASAP. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Jun 10 10:21:34 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 10 Jun 2015 10:21:34 -0400 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... In-Reply-To: <14E607DF-74FE-42A0-8D31-6FEF4588F2FB@redhat.com> References: <556F7C78.7070707@redhat.com> <556F84F3.1070204@redhat.com> <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> <55704B7E.9090905@redhat.com> <14E607DF-74FE-42A0-8D31-6FEF4588F2FB@redhat.com> Message-ID: <557847EE.1070306@redhat.com> p2 director install didn't complain, so no harm, no foul there. install-grinder has been broken for a while now due to issues on the slaves on which it runs. On 06/10/2015 05:07 AM, Max Rydahl Andersen wrote: > On 4 Jun 2015, at 14:58, Nick Boldt wrote: > >> Versionwatch CAN be tweaked to add exceptions. We currently have 3 in >> there for know issues where multiple versions were needed. >> >> But it doesn't validate IF those exclusions are still true. > > yes so it does not have anything to do with version watch tests failing. > >> For that we need to build everything, install everything, and see >> what's broken. Suspect that some of these IUs MIGHT be needed for >> something from Central. I didn't test-install that. > > Are you saying you removed IU's we have but did not run the tests we > already have in place to verify such changes ? > > p2install and install grinder ? > > We made those to make this kind of thing easier to test/verify. > > Thus lets use them. > > /max > > >> N >> >> On 06/04/2015 07:13 AM, Max Rydahl Andersen wrote: >>> On 4 Jun 2015, at 0:51, Nick Boldt wrote: >>> >>>> JBDS built locally and installed fine. Resulting IUs in installation >>>> (no >>>> source bundles, as expected): >>>> >>>> javax.servlet.jsp_2.2.0.v201112011158.jar >>>> javax.servlet_3.1.0.v201410161800.jar >>>> org.apache.commons.lang_2.6.0.v201404270220.jar >>>> >>>> Can someone else verify this change is safe? >>>> >>>> Motivation here is to remove dupe IUs and therefore get a cleaner >>>> install footprint >>> >>> if the separate versions are not required then that is a good reason. >>> >>>> , which will also make versionwatch builds blue again. >>> >>> I would rather fix version watch to be able to add exceptions for >>> this rule >>> since we most likely will end up with multiple versions of things - but >>> that >>> should only be marked okey if it is actually needed/wanted. >>> >>> I can't verify it easily today - maybe Denis can on his buildsetup ? >>> >>> /max >>> >>>> See also https://issues.jboss.org/browse/JBIDE-19605 >>>> >>>> On 06/03/2015 06:15 PM, Nick Boldt wrote: >>>>> Currently building this locally and then will attempt to build JBDS >>>>> with >>>>> it: >>>>> >>>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/151 >>>>> >>>>> Resulting TP contains only a single version of these IUs (instead of >>>>> multiple versions as we did in the past): >>>>> >>>>> javax.servlet_3.1.0.v201410161800.jar >>>>> javax.servlet.jsp.source_2.2.0.v201112011158.jar >>>>> javax.servlet.source_3.1.0.v201410161800.jar >>>>> org.apache.commons.lang_2.6.0.v201404270220.jar >>>>> org.apache.commons.lang.source_2.6.0.v201404270220.jar >>>>> >>>>> To build against local TP: >>>>> >>>>> mvn clean install -P hudson,eap,pack200 >>>>> -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 >>>>> -DJOB_NAME=devstudio.product_master >>>>> -Dupdate.site.description="Development Milestone" >>>>> -Djbosstools_site_stream=master -Dtpc.targetKind=unified >>>>> -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> 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 dgolovin at exadel.com Wed Jun 10 11:38:07 2015 From: dgolovin at exadel.com (Denis Golovin) Date: Wed, 10 Jun 2015 08:38:07 -0700 Subject: [jbosstools-dev] Fwd: [tycho-user] Tycho milestone 0.23.0 released In-Reply-To: <55763C28.8020107@redhat.com> References: <55759870.9000803@gmail.com> <55763C28.8020107@redhat.com> Message-ID: verified full build with 0.23.0 release and everything is looking fine. On Mon, Jun 8, 2015 at 6:06 PM, Nick Boldt wrote: > Does that by any chance mean you've successfully built the whole stack > w/ 0.23.0, including JBDS? > > On 06/08/2015 06:45 PM, Denis Golovin wrote: > > +1 > > > > On Mon, Jun 8, 2015 at 6:28 AM, Nick Boldt > > wrote: > > > > FYI, Tycho 0.23 is released. > > > > We should move up to using this in master branch. > > > > https://issues.jboss.org/browse/JBIDE-19973 > > > > > > -------- Forwarded Message -------- > > Subject: [tycho-user] Tycho milestone 0.23.0 released > > Date: Mon, 8 Jun 2015 07:34:48 +0000 > > From: Sievers, Jan >> > > Reply-To: Tycho user list > > > > To: Tycho user list (tycho-user at eclipse.org > > ) > >, > > Tycho developers list (tycho-dev at eclipse.org > > ) > > > > > > Tycho milestone 0.23.0 has been released and is available from maven > > central. > > > > See the release notes [1] for details of enhancements and bug fixes > in > > this release. > > > > Thanks to > > > > Christian Dietrich > > Enrico De Fent > > Christian Georgi > > Michael Keppler > > Pascal Rapicault > > Gunnar Wagenknecht > > > > who contributed patches for this release. > > > > And thanks and to everyone who helped us with testing the staged > > version. > > > > Regards, > > Tycho team > > > > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > > _______________________________________________ > > tycho-user mailing list > > tycho-user at eclipse.org > > To change your delivery options, retrieve your password, or > unsubscribe > > from this list, visit > > https://dev.eclipse.org/mailman/listinfo/tycho-user > > > > > > _______________________________________________ > > jbosstools-dev mailing list > > jbosstools-dev at lists.jboss.org 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150610/24132eb4/attachment.html From nboldt at redhat.com Wed Jun 10 14:22:54 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 10 Jun 2015 14:22:54 -0400 Subject: [jbosstools-dev] Fwd: [tycho-user] Tycho milestone 0.23.0 released In-Reply-To: References: <55759870.9000803@gmail.com> <55763C28.8020107@redhat.com> Message-ID: <5578807E.40403@redhat.com> Pushed to master (parent pom Beta2): https://github.com/jbosstools/jbosstools-build/commit/551c2ba6c3a28afe80c18240bc0ce8af3fb4f64d Note that we need to investigate if 0.23 breaks anything in any of the other jbosstools-* repos that don't depend on parent pom, such as target-platforms, discovery, and build-sites, build-ci, maven-plugins, ... On 06/10/2015 11:38 AM, Denis Golovin wrote: > verified full build with 0.23.0 release and everything is looking fine. > > On Mon, Jun 8, 2015 at 6:06 PM, Nick Boldt > wrote: > > Does that by any chance mean you've successfully built the whole stack > w/ 0.23.0, including JBDS? > > On 06/08/2015 06:45 PM, Denis Golovin wrote: > > +1 > > > > On Mon, Jun 8, 2015 at 6:28 AM, Nick Boldt > > >> wrote: > > > > FYI, Tycho 0.23 is released. > > > > We should move up to using this in master branch. > > > >https://issues.jboss.org/browse/JBIDE-19973 > > > > > > -------- Forwarded Message -------- > > Subject: [tycho-user] Tycho milestone 0.23.0 released > > Date: Mon, 8 Jun 2015 07:34:48 +0000 > > From: Sievers, Jan > >> > > Reply-To: Tycho user list > > >> > > To: Tycho user list (tycho-user at eclipse.org > > >) > > > >>, > > Tycho developers list (tycho-dev at eclipse.org > > >) > > >> > > > > Tycho milestone 0.23.0 has been released and is available from maven > > central. > > > > See the release notes [1] for details of enhancements and bug fixes in > > this release. > > > > Thanks to > > > > Christian Dietrich > > Enrico De Fent > > Christian Georgi > > Michael Keppler > > Pascal Rapicault > > Gunnar Wagenknecht > > > > who contributed patches for this release. > > > > And thanks and to everyone who helped us with testing the staged > > version. > > > > Regards, > > Tycho team > > > > [1]http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > > _______________________________________________ > > tycho-user mailing list > > tycho-user at eclipse.org > > > > To change your delivery options, retrieve your password, or unsubscribe > > from this list, visit > >https://dev.eclipse.org/mailman/listinfo/tycho-user > > > > > > _______________________________________________ > > 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 > > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Jun 10 19:42:47 2015 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 10 Jun 2015 19:42:47 -0400 Subject: [jbosstools-dev] Last (?) change to 4.50.0.Beta1-SNAPSHOT target platform Message-ID: <5578CB77.40206@redhat.com> I know I'm skipping the usual "wait for review" step but there have been no issues reported w/ the current target platform for JBT 4.3 Beta1 / JBDS 9.0 Beta1 (and we were supposed to release it a week ago), so here's one more change I've just pushed in directly, which upversions 4 IUs from the Eclipse Docker Tooling: https://github.com/jbosstools/jbosstools-target-platforms/commit/25fbd6f920f4804c2a272c85e0627791a6fa28a9 https://github.com/jbosstools/jbosstools-download.jboss.org/commit/8a37a686f44623206964462558729b9a1327a251 https://issues.jboss.org/browse/JBIDE-20013 It's building here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/ >=422 With output here: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Beta1-SNAPSHOT/REPO/ --- Well, sir, there's nothing on earth Like a genuine, bona fide Electrified, 4-line TP change What'd I say? TP change What's it called? TP change That's right! TP change! I hear we're 'sposed to p2diff Instead here's a song and a gif [1] Is there a chance the build could bend? Not on your life, mailing list friends Ref: http://www.metrolyrics.com/the-monorail-song-lyrics-simpsons.html [1] https://bestepisodeever.files.wordpress.com/2013/08/9f10ani.gif -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Thu Jun 11 05:19:20 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 11 Jun 2015 11:19:20 +0200 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... In-Reply-To: <557847EE.1070306@redhat.com> References: <556F7C78.7070707@redhat.com> <556F84F3.1070204@redhat.com> <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> <55704B7E.9090905@redhat.com> <14E607DF-74FE-42A0-8D31-6FEF4588F2FB@redhat.com> <557847EE.1070306@redhat.com> Message-ID: <995796ED-71FA-4075-90F4-BA1C5FFCEAE0@redhat.com> On 10 Jun 2015, at 16:21, Nick Boldt wrote: > p2 director install didn't complain, so no harm, no foul there. > > install-grinder has been broken for a while now due to issues on the > slaves on which it runs. do we have jira for that and followed up with ci-issues to get that fixed ? if we don't have install-grinder to verify we are back to having to verify stuff tediously manually. /max > > On 06/10/2015 05:07 AM, Max Rydahl Andersen wrote: >> On 4 Jun 2015, at 14:58, Nick Boldt wrote: >> >>> Versionwatch CAN be tweaked to add exceptions. We currently have 3 >>> in >>> there for know issues where multiple versions were needed. >>> >>> But it doesn't validate IF those exclusions are still true. >> >> yes so it does not have anything to do with version watch tests >> failing. >> >>> For that we need to build everything, install everything, and see >>> what's broken. Suspect that some of these IUs MIGHT be needed for >>> something from Central. I didn't test-install that. >> >> Are you saying you removed IU's we have but did not run the tests we >> already have in place to verify such changes ? >> >> p2install and install grinder ? >> >> We made those to make this kind of thing easier to test/verify. >> >> Thus lets use them. >> >> /max >> >> >>> N >>> >>> On 06/04/2015 07:13 AM, Max Rydahl Andersen wrote: >>>> On 4 Jun 2015, at 0:51, Nick Boldt wrote: >>>> >>>>> JBDS built locally and installed fine. Resulting IUs in >>>>> installation >>>>> (no >>>>> source bundles, as expected): >>>>> >>>>> javax.servlet.jsp_2.2.0.v201112011158.jar >>>>> javax.servlet_3.1.0.v201410161800.jar >>>>> org.apache.commons.lang_2.6.0.v201404270220.jar >>>>> >>>>> Can someone else verify this change is safe? >>>>> >>>>> Motivation here is to remove dupe IUs and therefore get a cleaner >>>>> install footprint >>>> >>>> if the separate versions are not required then that is a good >>>> reason. >>>> >>>>> , which will also make versionwatch builds blue again. >>>> >>>> I would rather fix version watch to be able to add exceptions for >>>> this rule >>>> since we most likely will end up with multiple versions of things - >>>> but >>>> that >>>> should only be marked okey if it is actually needed/wanted. >>>> >>>> I can't verify it easily today - maybe Denis can on his buildsetup >>>> ? >>>> >>>> /max >>>> >>>>> See also https://issues.jboss.org/browse/JBIDE-19605 >>>>> >>>>> On 06/03/2015 06:15 PM, Nick Boldt wrote: >>>>>> Currently building this locally and then will attempt to build >>>>>> JBDS >>>>>> with >>>>>> it: >>>>>> >>>>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/151 >>>>>> >>>>>> Resulting TP contains only a single version of these IUs (instead >>>>>> of >>>>>> multiple versions as we did in the past): >>>>>> >>>>>> javax.servlet_3.1.0.v201410161800.jar >>>>>> javax.servlet.jsp.source_2.2.0.v201112011158.jar >>>>>> javax.servlet.source_3.1.0.v201410161800.jar >>>>>> org.apache.commons.lang_2.6.0.v201404270220.jar >>>>>> org.apache.commons.lang.source_2.6.0.v201404270220.jar >>>>>> >>>>>> To build against local TP: >>>>>> >>>>>> mvn clean install -P hudson,eap,pack200 >>>>>> -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 >>>>>> -DJOB_NAME=devstudio.product_master >>>>>> -Dupdate.site.description="Development Milestone" >>>>>> -Djbosstools_site_stream=master -Dtpc.targetKind=unified >>>>>> -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> 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 /max http://about.me/maxandersen From manderse at redhat.com Thu Jun 11 05:29:10 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 11 Jun 2015 11:29:10 +0200 Subject: [jbosstools-dev] Last (?) change to 4.50.0.Beta1-SNAPSHOT target platform In-Reply-To: <5578CB77.40206@redhat.com> References: <5578CB77.40206@redhat.com> Message-ID: On 11 Jun 2015, at 1:42, Nick Boldt wrote: > I hear we're 'sposed to p2diff if this had come with a p2diff it would have been much more effective. 4-lines change could have meant many more changes in dependencies so please remember that next time and just do the p2diff as a minimum to verify a quick change did not add surprises. Thank you, /max http://about.me/maxandersen From nboldt at redhat.com Thu Jun 11 09:52:39 2015 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 11 Jun 2015 09:52:39 -0400 Subject: [jbosstools-dev] One final tweak for Beta1-SNAPSHOT target platform: remove duplicate IUs like javax.servlet, javax.servlet.jsp, apache.commons.lang... In-Reply-To: <995796ED-71FA-4075-90F4-BA1C5FFCEAE0@redhat.com> References: <556F7C78.7070707@redhat.com> <556F84F3.1070204@redhat.com> <93DCD807-97CF-48B0-A609-5EF91D3D7D13@redhat.com> <55704B7E.9090905@redhat.com> <14E607DF-74FE-42A0-8D31-6FEF4588F2FB@redhat.com> <557847EE.1070306@redhat.com> <995796ED-71FA-4075-90F4-BA1C5FFCEAE0@redhat.com> Message-ID: <557992A7.9050109@redhat.com> Yes, it's been in their queue for ages now. And meanwhile there's composite install test install and p2 director test installs that always work, regardless of UI snafus on the slaves. On 06/11/2015 05:19 AM, Max Rydahl Andersen wrote: > On 10 Jun 2015, at 16:21, Nick Boldt wrote: > >> p2 director install didn't complain, so no harm, no foul there. >> >> install-grinder has been broken for a while now due to issues on the >> slaves on which it runs. > > do we have jira for that and followed up with ci-issues to get that fixed ? > > if we don't have install-grinder to verify we are back to having to > verify stuff tediously manually. > > /max > >> >> On 06/10/2015 05:07 AM, Max Rydahl Andersen wrote: >>> On 4 Jun 2015, at 14:58, Nick Boldt wrote: >>> >>>> Versionwatch CAN be tweaked to add exceptions. We currently have 3 in >>>> there for know issues where multiple versions were needed. >>>> >>>> But it doesn't validate IF those exclusions are still true. >>> >>> yes so it does not have anything to do with version watch tests failing. >>> >>>> For that we need to build everything, install everything, and see >>>> what's broken. Suspect that some of these IUs MIGHT be needed for >>>> something from Central. I didn't test-install that. >>> >>> Are you saying you removed IU's we have but did not run the tests we >>> already have in place to verify such changes ? >>> >>> p2install and install grinder ? >>> >>> We made those to make this kind of thing easier to test/verify. >>> >>> Thus lets use them. >>> >>> /max >>> >>> >>>> N >>>> >>>> On 06/04/2015 07:13 AM, Max Rydahl Andersen wrote: >>>>> On 4 Jun 2015, at 0:51, Nick Boldt wrote: >>>>> >>>>>> JBDS built locally and installed fine. Resulting IUs in installation >>>>>> (no >>>>>> source bundles, as expected): >>>>>> >>>>>> javax.servlet.jsp_2.2.0.v201112011158.jar >>>>>> javax.servlet_3.1.0.v201410161800.jar >>>>>> org.apache.commons.lang_2.6.0.v201404270220.jar >>>>>> >>>>>> Can someone else verify this change is safe? >>>>>> >>>>>> Motivation here is to remove dupe IUs and therefore get a cleaner >>>>>> install footprint >>>>> >>>>> if the separate versions are not required then that is a good reason. >>>>> >>>>>> , which will also make versionwatch builds blue again. >>>>> >>>>> I would rather fix version watch to be able to add exceptions for >>>>> this rule >>>>> since we most likely will end up with multiple versions of things - >>>>> but >>>>> that >>>>> should only be marked okey if it is actually needed/wanted. >>>>> >>>>> I can't verify it easily today - maybe Denis can on his buildsetup ? >>>>> >>>>> /max >>>>> >>>>>> See also https://issues.jboss.org/browse/JBIDE-19605 >>>>>> >>>>>> On 06/03/2015 06:15 PM, Nick Boldt wrote: >>>>>>> Currently building this locally and then will attempt to build JBDS >>>>>>> with >>>>>>> it: >>>>>>> >>>>>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/151 >>>>>>> >>>>>>> Resulting TP contains only a single version of these IUs (instead of >>>>>>> multiple versions as we did in the past): >>>>>>> >>>>>>> javax.servlet_3.1.0.v201410161800.jar >>>>>>> javax.servlet.jsp.source_2.2.0.v201112011158.jar >>>>>>> javax.servlet.source_3.1.0.v201410161800.jar >>>>>>> org.apache.commons.lang_2.6.0.v201404270220.jar >>>>>>> org.apache.commons.lang.source_2.6.0.v201404270220.jar >>>>>>> >>>>>>> To build against local TP: >>>>>>> >>>>>>> mvn clean install -P hudson,eap,pack200 >>>>>>> -Dtpc.version=4.50.0.Beta1-SNAPSHOT -DBUILD_NUMBER=450000 >>>>>>> -DJOB_NAME=devstudio.product_master >>>>>>> -Dupdate.site.description="Development Milestone" >>>>>>> -Djbosstools_site_stream=master -Dtpc.targetKind=unified >>>>>>> -DtargetRepositoryUrl=file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> 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 > > > /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 Jun 12 14:15:12 2015 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 12 Jun 2015 14:15:12 -0400 Subject: [jbosstools-dev] FYI: Beta1 respin-a will begin this Friday Jun 12 at 12:00 EDT / 18:00 CEST In-Reply-To: <557846F6.3020901@redhat.com> References: <557846F6.3020901@redhat.com> Message-ID: <557B21B0.5050609@redhat.com> Due to Jenkins server outage this morning, things are a bit backed up. Currently rebuilding Central and Server to pick up recent commits. Is everyone done the things they plan to slip into this respin-a? We currently have 20 issues and only 15 of them are marked resolved. cc: Andre, Fred, Koen https://issues.jboss.org/issues/?jql=labels%20%3D%20respin-a%20AND%20fixversion%20in%20%284.3.0.Beta1%2C%209.0.0.Beta1%29%20ORDER%20BY%20resolution%20ASC There are also 20 issues still unresolved for Beta1. As this respin is the LAST ONE planned for Beta1, it's time to tell me you're still working on something, or slip these to Beta2 (unless they're issues which depend on Beta1 being released, like JBIDE-19757). https://issues.jboss.org/issues/?jql=filter%20%3D%20%27ds_freeze%27%20and%20filter%20%3D%20%27ds_unresolved%27 Cheers, Nick On 06/10/2015 10:17 AM, Nick Boldt wrote: > In case you missed it (ICYMI), JBT 4.3 / JBDS 9.0 Beta1 "respin-a" will > be built this Friday Jun 12. > > Please have all your commits in by Friday around noon EDT (18:00 CEST), > or ping me @nickboldt on IRC/Skype/email/twitter if you need more time. > > Here's the current list of Beta1 respin-a issues. > > https://issues.jboss.org/issues/?jql=labels%20%3D%20respin-a%20and%20fixversion%20in%20%28%224.3.0.Beta1%22%2C%229.0.0.Beta1%22%29 > (11 issues so far) > > If you have fixed something in the Beta1x branch and have NOT tagged > that JIRA with a "respin-a" label, please do so ASAP. > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Sun Jun 14 19:27:08 2015 From: nboldt at redhat.com (Nick Boldt) Date: Sun, 14 Jun 2015 19:27:08 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1a bits available for QE testing Message-ID: <557E0DCC.1020400@redhat.com> As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/mars/staging/updates/ Target platform: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Beta1 New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Additional update sites: * http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1a/ * http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Beta1a/ * http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Beta1a/ Discovery sites: * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1a/ * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1a/ Build folders (for build logs & update site zips): * http://download.jboss.org/jbosstools/mars/staging/builds/ -- Changes prompting this respin-a are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-a%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%229.0.0.Beta1%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.3.0.Beta1%22%29%29%29 To compare the upcoming version of Central (4.3.0.Beta1a) against an older version, add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1a/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1a/ -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1a/jbosstools-earlyaccess.properties -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Mon Jun 15 12:19:40 2015 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 15 Jun 2015 12:19:40 -0400 Subject: [jbosstools-dev] Brace yourselves. respin-b is coming. Message-ID: <557EFB1C.4050800@redhat.com> There will be a respin-b in the next 48hrs. https://imgflip.com/i/mx6vt [ typo intentional :D ] There is currently one blocker (LiveReload) and one "might as well fix it, if we're respinning anyway" (OpenShift): https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-b%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%229.0.0.Beta1%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.3.0.Beta1%22%29%29%29 Cut off for adding BLOCKERS to the respin is tomorrow night, Tues 8pm EDT (Wed 02:00 CEST). PRs on JIRAs REQUIRED, with at least a couple +1s from reviewers. That gives me time to ensure everything's built (or at least queued) Tuesday night. Then Mickael has the morning to verify everything built OK (no unexpected Jenkins slave failures, like we had Friday-Sunday) & can push the bits on Wednesday starting around 6am EDT (12:00 CEST). So say we all? -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From rstryker at redhat.com Tue Jun 16 16:41:04 2015 From: rstryker at redhat.com (Rob Stryker) Date: Tue, 16 Jun 2015 16:41:04 -0400 Subject: [jbosstools-dev] Dashboard filters need updating Message-ID: <558089E0.1030109@redhat.com> Hi All: So it's getting a bit tedious running manual jira queries all day long so I can see what I'm working on. ds_my_next_master_unresolved is still effectively a beta1 query, when it should be a beta2 query. As I understood it, once a branch is 'frozen', it should only appear in ds_my_freeze_unresolved, and not also in ds_my_next_master_unresolved. This is so that people who are 100% done with beta1 can move on to beta2 tasks without having to make changes to their dashboard all the time. As of right now, these two queries are identically returning beta1 items, and so I have wasted real-estate (two identical queries) and cannot see my beta2 tasks. I did a check on https://github.com/maxandersen/jiralint/blob/master/constants.json and https://github.com/maxandersen/jiralint/blob/master/filters-composite.json and was unable to see the String 'beta' anywhere, so I'm unable to create a pull request to update the filters. So I'm doing manual queries all day long now ;) Plz to fix. kthnx. https://issues.jboss.org/browse/JBIDE-20097 - Rob From manderse at redhat.com Tue Jun 16 19:29:51 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 17 Jun 2015 01:29:51 +0200 Subject: [jbosstools-dev] Dashboard filters need updating In-Reply-To: <558089E0.1030109@redhat.com> References: <558089E0.1030109@redhat.com> Message-ID: <9C5AE76A-7640-4D59-BCF7-E7953A143085@redhat.com> > As I understood it, once a branch is 'frozen', it should only appear > in > ds_my_freeze_unresolved, and not also in ds_my_next_master_unresolved. > This is so that people who are 100% done with beta1 can move on to > beta2 > tasks without having to make changes to their dashboard all the time. > As of right now, these two queries are identically returning beta1 > items, and so I have wasted real-estate (two identical queries) and > cannot see my beta2 tasks. fixed it as discussed on irc. Was missing filtering on frozen state. > I did a check on > https://github.com/maxandersen/jiralint/blob/master/constants.json and > https://github.com/maxandersen/jiralint/blob/master/filters-composite.json > and was unable to see the String 'beta' anywhere, so I'm unable to > create a pull request to update the filters. So I'm doing manual > queries > all day long now ;) Plz to fix. kthnx. The filters has no idea what 'beta' is; its all based on start dates, wether it is released and if it is code frozen. The definition for what "next" is is here: https://github.com/maxandersen/jiralint/blob/master/constants.json#L38 notice the pattern that are used to say the candiates are everything that is in 4.3. but NOT in the .x version. /max http://about.me/maxandersen From xcoulon at redhat.com Wed Jun 17 04:38:20 2015 From: xcoulon at redhat.com (Xavier Coulon) Date: Wed, 17 Jun 2015 10:38:20 +0200 Subject: [jbosstools-dev] Fixing the "menu:" macro rendering on the website Message-ID: <1DD3F409-0B6B-4997-BF36-8C5A361F9A71@redhat.com> Hello, As reported earlier by Rob and yesterday by Martin, the "menu:" macro did not render as expected on our website pages. This should be now fixed thanks to Martin who found the solution: we just need to include a ":experimental:" attribute in the metadata of the asciidoctor files. I fixed all the blog entries that were missing the aforementioned attribute (https://github.com/jbosstools/jbosstools-website/pull/414), but feel free to report remaining issue. Again, thanks to Martin for his help on the subject ! Best regards, /Xavier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150617/edb031b5/attachment.html From mistria at redhat.com Wed Jun 17 08:50:13 2015 From: mistria at redhat.com (Mickael Istria) Date: Wed, 17 Jun 2015 14:50:13 +0200 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1b bits available for QE testing Message-ID: <55816D05.1050303@redhat.com> As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/mars/staging/updates/ Target platform: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Beta1 New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel Additional update sites: * http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1b/ * http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Beta1b/ * http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Beta1b/ Discovery sites: * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1b/ * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1b/ Build folders (for build logs & update site zips): * http://download.jboss.org/jbosstools/mars/staging/builds/ Changes prompting this respin-b are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-b%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%229.0.0.Beta1%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.3.0.Beta1%22%29%29%29 -- 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/20150617/33e49422/attachment.html From manderse at redhat.com Wed Jun 17 18:08:33 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 18 Jun 2015 00:08:33 +0200 Subject: [jbosstools-dev] Fixing the "menu:" macro rendering on the website In-Reply-To: <1DD3F409-0B6B-4997-BF36-8C5A361F9A71@redhat.com> References: <1DD3F409-0B6B-4997-BF36-8C5A361F9A71@redhat.com> Message-ID: I've enhanced Xavier's fix so this is now enabled globally. No need to add :experimental: to any .adoc, but it is recommended if you want it to be shown nicer when using an asciidoc previewer that might not know about the global flag. /max > Hello, > > As reported earlier by Rob and yesterday by Martin, the "menu:" macro > did not render as expected on our website pages. This should be now > fixed thanks to Martin who found the solution: we just need to include > a ":experimental:" attribute in the metadata of the asciidoctor files. > I fixed all the blog entries that were missing the aforementioned > attribute (https://github.com/jbosstools/jbosstools-website/pull/414), > but feel free to report remaining issue. > > Again, thanks to Martin for his help on the subject ! > > Best regards, > /Xavier > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From nboldt at redhat.com Fri Jun 19 00:54:30 2015 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Jun 2015 00:54:30 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Beta1c bits available for QE testing Message-ID: <5583A086.30705@redhat.com> As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/mars/staging/updates/ Target platform: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Beta1 New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Additional update sites: * http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1c/ * http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Beta1c/ * http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Beta1c/ Discovery sites: * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1c/ * http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1c/ Build folders (for build logs & update site zips): * http://download.jboss.org/jbosstools/mars/staging/builds/ -- Changes prompting this respin-c are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-c%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%229.0.0.Beta1%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.3.0.Beta1%22%29%29%29 To compare the upcoming version of Central (4.3.0.Beta1c) against an older version, add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1c/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1c/ -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1c/jbosstools-earlyaccess.properties -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mistria at redhat.com Fri Jun 19 12:32:46 2015 From: mistria at redhat.com (Mickael Istria) Date: Fri, 19 Jun 2015 18:32:46 +0200 Subject: [jbosstools-dev] Target Platform 4.50.0.Beta2-SNAPSHOT now includes latest Mars build Message-ID: <5584442E.1030000@redhat.com> Hi all, Since JBoss Tools 4.3.0.Beta1 seems to be approved for release, I've merged a change that moves the 4.50.0.Beta2-SNAPSHOT target-platform to the latest Mars build, which is hopefully and most likely what is the last Mars build for the simultaneous release repository. Parent pom and CI jobs for the current master branch already use this target-platform so the next builds should leverage this update. Here is a link to the GitHub Pull Request, including a p2diff: https://github.com/jbosstools/jbosstools-target-platforms/pull/154 . 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/20150619/d748bc40/attachment.html From nboldt at redhat.com Fri Jun 19 12:45:15 2015 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Jun 2015 12:45:15 -0400 Subject: [jbosstools-dev] Target Platform 4.50.0.Beta2-SNAPSHOT now includes latest Mars build [and soon new TestNG too!] In-Reply-To: <5584442E.1030000@redhat.com> References: <5584442E.1030000@redhat.com> Message-ID: <5584471B.4020600@redhat.com> Here's a new JIRA [1] for this change, inside the JBDS 9 Target Platform Epic [2]: [1] https://issues.jboss.org/browse/JBIDE-20130 [2] https://issues.jboss.org/browse/JBDS-3299 One additional change coming in Beta2 - a newer version of TestNG will be included in Central and JBDS [3]. [3] https://issues.jboss.org/browse/JBDS-3440 Cheers, Nick On 06/19/2015 12:32 PM, Mickael Istria wrote: > Hi all, > > Since JBoss Tools 4.3.0.Beta1 seems to be approved for release, I've > merged a change that moves the 4.50.0.Beta2-SNAPSHOT target-platform to > the latest Mars build, which is hopefully and most likely what is the > last Mars build for the simultaneous release repository. Parent pom and > CI jobs for the current master branch already use this target-platform > so the next builds should leverage this update. > Here is a link to the GitHub Pull Request, including a p2diff: > https://github.com/jbosstools/jbosstools-target-platforms/pull/154 . > > 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 nboldt at redhat.com Mon Jun 22 13:41:52 2015 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 22 Jun 2015 13:41:52 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 5 Unresolved JIRAs w/ fixversion = 4.3.0.Beta1 Message-ID: <558848E0.7020209@redhat.com> Please fix your outstanding issues, or punt them to Beta2. * Central * Project Examples * Aerogear * Arquillian * Website https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212326157%22%20and%20key%20!%3D%20%22JBIDE-19757%22 Thanks! -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Mon Jun 22 16:38:44 2015 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 22 Jun 2015 16:38:44 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] Message-ID: <55887254.6060204@redhat.com> Component leads, please tag your repositories! $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is called jbosstools, also often called origin $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD $ git push jbosstools jbosstools-4.3.0.Beta1 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From pleacu at redhat.com Mon Jun 22 16:58:43 2015 From: pleacu at redhat.com (Paul Leacu) Date: Mon, 22 Jun 2015 16:58:43 -0400 (EDT) Subject: [jbosstools-dev] JBDSIS 8.0.2.GA/ JBTIS 4.2.2.Final now live In-Reply-To: <314973974.19010263.1434994455007.JavaMail.zimbra@redhat.com> Message-ID: <250519932.19087679.1435006723513.JavaMail.zimbra@redhat.com> Greetings, The latest Eclipse-Luna capable, JBDS 8.1.0.GA compatible Integration Stack GA tooling is released. The highlight of this release is the productized Fuse Tooling features. JBDSIS 8.0.2.GA, JBTIS 4.2.2.Final This release contains the following: * Released .Final components BPEL 1.3.100.Final > BPMN2 1.1.3.Final_1.1.0.Final_luna DROOLS/JBPM6 6.2.0.Final ESB 1.5.530.Final > FUSE TOOLING 7.3.0.Final JBPM3 4.5.200.Final MODESHAPE 3.7.0.Final > TEIID DESIGNER 9.0.2.Final * Early Access components > FUSE TOOLING 7.3.0.Final (Fuse Transformation Tooling) SWITCHYARD 2.0.0.Final The latest early-access/ tech preview SAP tooling (7.3.0.Final) is also available through the Fuse import update wizard and a separate update site. 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 p2 installer is available for JBDSIS (.GA): 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/ - use this for 'Location:' for the early access integration stack: https://devstudio.redhat.com/updates/8.0/integration-stack/earlyaccess/ The standard p2 installer is available for JBTIS (.Final): * 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/ - use this for 'Location:' for the early access integration stack: http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/earlyaccess JBoss Central is supported for JBTIS (.Final): * 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' * Use JBoss Central - community bits are live ./eclipse 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.2.GA.zip https://devstudio.redhat.com/updates/8.0.0/jbdevstudio-integration-stack-updatesite-8.0.2.GA.zip.MD5 2. https://devstudio.redhat.com/updates/8.0.0/jbdevstudio-integration-stack-updatesite-8.0.2.GA-earlyaccess.zip https://devstudio.redhat.com/updates/8.0.0/jbdevstudio-integration-stack-updatesite-8.0.2.GA-earlyaccess.zip.MD5 3. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.2.Final.zip http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.2.Final.zip.MD5 4. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.2.Final-earlyaccess.zip http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.2.Final-earlyaccess.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.5.Final/ # note -ea target files http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.5.Final/jbtis/REPO/ http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.5.Final/jbtis/earlyaccess/REPO/ http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.5.Final/jbdsis/REPO/ http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.5.Final/jbdsis/earlyaccess/REPO/ Blog pending... Give it a try! --paull From adietish at redhat.com Tue Jun 23 03:23:22 2015 From: adietish at redhat.com (=?windows-1252?Q?Andr=E9_Dietisheim?=) Date: Tue, 23 Jun 2015 09:23:22 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <55887254.6060204@redhat.com> References: <55887254.6060204@redhat.com> Message-ID: <5589096A.20402@redhat.com> done for openshift On 06/22/2015 10:38 PM, Nick Boldt wrote: > Component leads, please tag your repositories! > > $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is > called jbosstools, also often called origin > $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD > $ git push jbosstools jbosstools-4.3.0.Beta1 > > From snjezana.peco at redhat.com Tue Jun 23 08:05:29 2015 From: snjezana.peco at redhat.com (Snjezana Peco) Date: Tue, 23 Jun 2015 14:05:29 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <55887254.6060204@redhat.com> References: <55887254.6060204@redhat.com> Message-ID: <55894B89.5010402@redhat.com> Done for arquillian, birt and portlet. On 6/22/2015 10:38 PM, Nick Boldt wrote: > Component leads, please tag your repositories! > > $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is > called jbosstools, also often called origin > $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD > $ git push jbosstools jbosstools-4.3.0.Beta1 > > From fbricon at redhat.com Tue Jun 23 10:00:04 2015 From: fbricon at redhat.com (Fred Bricon) Date: Tue, 23 Jun 2015 10:00:04 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <55887254.6060204@redhat.com> References: <55887254.6060204@redhat.com> Message-ID: <7C702991-8C4D-47A1-B927-076E2C119C27@redhat.com> Central done > Le 22 juin 2015 ? 16:38, Nick Boldt a ?crit : > > git push jbosstools jbosstools-4.3.0.Beta1 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150623/e9f07dc9/attachment.html From gorkem.ercan at gmail.com Tue Jun 23 10:49:37 2015 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Tue, 23 Jun 2015 10:49:37 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <55887254.6060204@redhat.com> References: <55887254.6060204@redhat.com> Message-ID: <87E04739-BA11-4BB0-8030-21838265C680@gmail.com> tagged jbosstools-aerogear. On 22 Jun 2015, at 16:38, Nick Boldt wrote: > Component leads, please tag your repositories! > > $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is > called jbosstools, also often called origin > $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD > $ git push jbosstools jbosstools-4.3.0.Beta1 > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From manderse at redhat.com Tue Jun 23 12:58:32 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 23 Jun 2015 18:58:32 +0200 Subject: [jbosstools-dev] JBoss Tools 4.3.0 Beta1 is here for Mars Message-ID: This is a development release aimed at Eclipse 4.5.0.R Mars users. Announcement Blog: http://tools.jboss.org/blog/2015-06-23-beta1-for-mars.html Eclipse Marketplace: https://marketplace.eclipse.org/content/jboss-tools-mars Update Site: http://download.jboss.org/jbosstools/mars/development/updates/ Update Site Zips: * http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Beta1.html * http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.3.0.x/ Installation instructions: http://tools.jboss.org/downloads/installation.html New + Noteworthy (subject to change): http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Beta1.html Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel /max http://about.me/maxandersen From manderse at redhat.com Tue Jun 23 13:10:19 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 23 Jun 2015 19:10:19 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <55887254.6060204@redhat.com> References: <55887254.6060204@redhat.com> Message-ID: remind me where I can get the list of repo, sha-1 and i'll make this happen on all of them. /max > Component leads, please tag your repositories! > > $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is > called jbosstools, also often called origin > $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD > $ git push jbosstools jbosstools-4.3.0.Beta1 > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From nboldt at redhat.com Tue Jun 23 15:13:28 2015 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 23 Jun 2015 15:13:28 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: References: <55887254.6060204@redhat.com> Message-ID: <5589AFD8.9060106@redhat.com> Do you mean this? http://download.jboss.org/jbosstools/static/mars/development/updates/core/4.3.0.Beta1/buildinfo.json On 06/23/2015 01:10 PM, Max Rydahl Andersen wrote: > remind me where I can get the list of repo, sha-1 and i'll make this > happen on all of them. > > /max > >> Component leads, please tag your repositories! >> >> $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is >> called jbosstools, also often called origin >> $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD >> $ git push jbosstools jbosstools-4.3.0.Beta1 >> >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Tue Jun 23 15:32:01 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 23 Jun 2015 21:32:01 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <5589AFD8.9060106@redhat.com> References: <55887254.6060204@redhat.com> <5589AFD8.9060106@redhat.com> Message-ID: On 23 Jun 2015, at 21:13, Nick Boldt wrote: > Do you mean this? > > http://download.jboss.org/jbosstools/static/mars/development/updates/core/4.3.0.Beta1/buildinfo.json not quite. Last time I suggested we created a file with a line for each repo, like: jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1 You had a txt file before that had this information but in a hard-to-parse format. I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. /max > > On 06/23/2015 01:10 PM, Max Rydahl Andersen wrote: >> remind me where I can get the list of repo, sha-1 and i'll make this >> happen on all of them. >> >> /max >> >>> Component leads, please tag your repositories! >>> >>> $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is >>> called jbosstools, also often called origin >>> $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD >>> $ git push jbosstools jbosstools-4.3.0.Beta1 >>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools & Dev Studio >>> http://nick.divbyzero.com >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> /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 PayPal at service.fr Wed Jun 24 08:21:28 2015 From: PayPal at service.fr (PayPal.Com) Date: Wed, 24 Jun 2015 08:21:28 -0400 (EDT) Subject: [jbosstools-dev] =?utf-8?q?Attention!_Votre_compte_PayPal_a_?= =?utf-8?b?w6l0w6kgbGltaXTDqSE=?= Message-ID: <7555233.242848.1435148488851.JavaMail.SYSTEM@smtp-relay.gmail.com> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150624/0d75863c/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Informations Compte PayPal13.zip Type: application/octet-stream Size: 5310 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150624/0d75863c/attachment.obj From pleacu at redhat.com Wed Jun 24 15:09:00 2015 From: pleacu at redhat.com (Paul Leacu) Date: Wed, 24 Jun 2015 15:09:00 -0400 (EDT) Subject: [jbosstools-dev] New Mars JBTIS target platform available - JBTIS-TP-4.3.0.Beta1a In-Reply-To: <979637535.20330829.1435172060788.JavaMail.zimbra@redhat.com> Message-ID: <954408177.20333319.1435172940171.JavaMail.zimbra@redhat.com> Greetings - A new Eclipse Mars/ JBDS 9 compatible JBTIS TP is available - 4.3.0.Beta1a https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.3.0.Beta1a/ http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1a/ See Jira for details: https://issues.jboss.org/browse/JBTIS-449 Synopsis: 1. Update JBoss Tools core TP to 4.50.0.Beta1 2. Update JBoss Tools core update site to 4.3.0.Beta1 3. Add Apache dependency for Teiid Designer. Thanks, --paull From fbricon at gmail.com Wed Jun 24 16:04:49 2015 From: fbricon at gmail.com (Fred Bricon) Date: Wed, 24 Jun 2015 16:04:49 -0400 Subject: [jbosstools-dev] m2e 1.6.0 is available Message-ID: Hello World, m2e 1.6.0 (git tag 'releases/1.6/1.6.0.20150526-2032') has been released today, as part of the Eclipse Mars release train[1]. With over 80[2] bugfixes and improvements, I believe this release is pretty solid. We've published more detailed release notes over there[3]. Special thanks to all external contributors for this release, who provided patches via Gerrit : - Wayne Beaton - Wei Cai - Daniel Kasmeroglu - Lars Vogel - Rastislav Wagner You guys rock, keep it up! As usual, please do not hesitate to give us your feedback on this mailing list or open bugs at [3]. The master branch on git now builds m2e 1.7.0-SNAPSHOT, which requires 1.8. Enjoy. Fred Bricon https://twitter.com/fbricon [1] http://download.eclipse.org/technology/m2e/releases/ [2] https://www.eclipse.org/m2e/documentation/release-notes-16.html [3] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=m2e -- "Have you tried turning it off and on again" - The IT Crowd And if that fails, then http://goo.gl/tnBgH5 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150624/36dc0731/attachment.html From rstryker at redhat.com Wed Jun 24 16:23:54 2015 From: rstryker at redhat.com (Rob Stryker) Date: Wed, 24 Jun 2015 16:23:54 -0400 Subject: [jbosstools-dev] Question on all external users of IJBoss7ManagerService Message-ID: <558B11DA.7040605@redhat.com> Hi all: We currently have two plugins containing client jars for the various wildfly / as7 versions. One plugin is named org.jboss.ide.eclipse.as.management.as71, the other org.jboss.ide.eclipse.as.management.wildfly8 As currently implemented, org.jboss.ide.eclipse.as.management.as71 holds client jars that are used with as70, 71, eap6x, etc. org.jboss.ide.eclipse.as.management.wildfly8 is used to hold jars for all wildflys, or, expectedly, eap7x. A bug in deploying large projects has led me to investigate whether the wildfly 9 jars work for all servers or not. It turns out, they work for all except AS 7.0.x. With as71, though, a higher timeout is needed. My PR to fix the issue creates a 71x service inside the org.jboss.ide.eclipse.as.management.wildfly8 to live along side the wf8 service. Unfortunately, it seems strange now to have a plugin named org.jboss.ide.eclipse.as.management.as71 which holds a service with version=7.1.0.Beta1 which only works for AS 7.0.x =P Seems a bit odd, no? So I was planning on harmonizing these constants, plugin names, versions, etc, in beta2, and was wondering if anyone else is using these service names and constants directly, and how they're being used? I expect to change them and clean them up, and need to know if this will break anyone. - Rob Stryker From fbricon at gmail.com Wed Jun 24 16:26:48 2015 From: fbricon at gmail.com (Fred Bricon) Date: Wed, 24 Jun 2015 16:26:48 -0400 Subject: [jbosstools-dev] m2e-wtp 1.2.0 is available Message-ID: Hello again World, m2e-wtp 1.2.0 (git tag 'releases/1.2.0/1.2.0.20150602-1740') has been released today alongside m2e 1.6, as part of the Eclipse Mars release train[1]. This is a very minor release with about 20 bug fixes[2], the most notable improvements here are : - m2e-wtp now tries to keep your custom Deployment Assembly settings (and ordering) - An error marker is added when war projects lack a web.xml descriptor but is true, matching the Maven CLI behavior. More details on this release can be found here[3]. Special thanks to the contributors who provided patches via Gerrit for this 1.2 release : - Wei Cai - Michael Schieder - John Serock Keep them coming! As usual, please do not hesitate to give us your feedback on this mailing list or open bugs at [4]. Enjoy. Fred Bricon https://twitter.com/fbricon [1] http://download.eclipse.org/m2e-wtp/releases/ [2] https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&columnlist=product%2Ctarget_milestone%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate&list_id=12096247&product=M2E-WTP&query_format=advanced&target_milestone=1.2.0%2FMars%20M1&target_milestone=1.2.0%2FMars%20M2&target_milestone=1.2.0%2FMars%20M3&target_milestone=1.2.0%2FMars%20M4&target_milestone=1.2.0%2FMars%20M5&target_milestone=1.2.0%2FMars%20M6&target_milestone=1.2.0%2FMars%20M7&target_milestone=1.2.0%2FMars%20RC2 [3] https://wiki.eclipse.org/M2E-WTP/New_and_Noteworthy/1.2.0 [4] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP -- "Have you tried turning it off and on again" - The IT Crowd And if that fails, then http://goo.gl/tnBgH5 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150624/021870c5/attachment-0001.html From manderse at redhat.com Thu Jun 25 04:21:45 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 25 Jun 2015 10:21:45 +0200 Subject: [jbosstools-dev] datestamps from blog filename no longer required Message-ID: <70276A18-678C-4E32-BB07-1216D2AB8787@redhat.com> Hey, Just a heads up that when you add a blog to jbosstools-website you no longer [1] need to put the date of its release into the filename, but simply put it in the header like this: ``` :page-date: 2015-06-25 ``` This has three advantages: * no need to rename the file when publishing does not happen on that exact date * no date in the urls makes the urls "timeless" (more likely to be viewed/clicked according to http://blog.arungupta.me/write-effective-seo-friendly-blogs/) * shorter urls I'm not changing the old blog posts urls, but going forward we should just use plain text urls. I've updated the blog templates etc. so as long as you follow the docs everything will be fine ;) [1] https://issues.jboss.org/browse/JBIDE-20144 /max http://about.me/maxandersen From manderse at redhat.com Thu Jun 25 05:47:20 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 25 Jun 2015 11:47:20 +0200 Subject: [jbosstools-dev] Question on all external users of IJBoss7ManagerService In-Reply-To: <558B11DA.7040605@redhat.com> References: <558B11DA.7040605@redhat.com> Message-ID: > My PR to fix the issue creates a 71x service inside the > org.jboss.ide.eclipse.as.management.wildfly8 to live along side the > wf8 > service. Unfortunately, it seems strange now to have a plugin named > org.jboss.ide.eclipse.as.management.as71 which holds a service with > version=7.1.0.Beta1 which only works for AS 7.0.x =P Seems a bit > odd, no? eh - why would as71 not continue to work with AS 7.1, EAP etc. ? Are you not just saying that you will start using management.as90 with AS 7.1 and upwards to make it behave better ? seems to me like nothing changed/broken in this so not sure why you think its broken more than before where as71 was used for other versions than as7.1 ? /max http://about.me/maxandersen From rstryker at redhat.com Thu Jun 25 12:56:42 2015 From: rstryker at redhat.com (Rob Stryker) Date: Thu, 25 Jun 2015 12:56:42 -0400 Subject: [jbosstools-dev] Question on all external users of IJBoss7ManagerService In-Reply-To: References: <558B11DA.7040605@redhat.com> Message-ID: <558C32CA.6080306@redhat.com> On 06/25/2015 05:47 AM, Max Rydahl Andersen wrote: > >> My PR to fix the issue creates a 71x service inside the >> org.jboss.ide.eclipse.as.management.wildfly8 to live along side the wf8 >> service. Unfortunately, it seems strange now to have a plugin named >> org.jboss.ide.eclipse.as.management.as71 which holds a service with >> version=7.1.0.Beta1 which only works for AS 7.0.x =P Seems a bit >> odd, no? > > eh - why would as71 not continue to work with AS 7.1, EAP etc. ? I'm saying that in my PR, the jars in the as71 management plugin would only work for as70, while the jars in the wf8 plugin will work for as71 through wf9. This is pretty confusing, since someone might expect the jars in the as71 plugin are the one being used for as71, which won't be the case. Of course if a client were using the mgmt plugins properly, they'd have an IServer already, and use the existing API (Extended properties, etc) to get the management service. But if they're "hand-rolling" their own solution by locating services with specific version strings, or depending on specific plugins, this becomes more of an issue. Ideally I'd like to rename the plugins to match better their functionality. I'd also like to rename the constants to match what they actually work for, so we don't have constants with strings including "beta1" or other such nonesense... But in order to do this safely, I need to know who our external users are of the IJBoss7ManagerService, what constants they use, whether they depend on a given plugin name directly (either in their manifests or features), or if they just depend on my AS feature (and then I pull in all the management stuff). Basically, I'd like to clean up the code, rename the things that make no sense, and harmonize the situation ;) > > Are you not just saying that you will start using management.as90 with > AS 7.1 and upwards > to make it behave better ? > > seems to me like nothing changed/broken in this so not sure why you > think its broken > more than before where as71 was used for other versions than as7.1 ? > > /max > http://about.me/maxandersen From nboldt at redhat.com Thu Jun 25 15:13:49 2015 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 25 Jun 2015 15:13:49 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: References: <55887254.6060204@redhat.com> <5589AFD8.9060106@redhat.com> Message-ID: <558C52ED.7060203@redhat.com> How about this? https://issues.jboss.org/browse/JBIDE-20152 https://github.com/jbdevstudio/jbdevstudio-ci/pull/152 This could also live in jbosstools-build-ci if you prefer; there's nothing secret here, but it's releng process stuff so I started in jbdevstudio-ci where the other python scripts are. On 06/23/2015 03:32 PM, Max Rydahl Andersen wrote: > On 23 Jun 2015, at 21:13, Nick Boldt wrote: > >> Do you mean this? >> >> http://download.jboss.org/jbosstools/static/mars/development/updates/core/4.3.0.Beta1/buildinfo.json >> > > not quite. > > Last time I suggested we created a file with a line for each repo, like: > > jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1 > > You had a txt file before that had this information but in a > hard-to-parse format. > > I can try parse the buildinfo.json too but thought if you had the > simpler one I could use that instead. > > /max > >> >> On 06/23/2015 01:10 PM, Max Rydahl Andersen wrote: >>> remind me where I can get the list of repo, sha-1 and i'll make this >>> happen on all of them. >>> >>> /max >>> >>>> Component leads, please tag your repositories! >>>> >>>> $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is >>>> called jbosstools, also often called origin >>>> $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD >>>> $ git push jbosstools jbosstools-4.3.0.Beta1 >>>> >>>> >>>> -- >>>> Nick Boldt :: JBoss by Red Hat >>>> Productization Lead :: JBoss Tools & Dev Studio >>>> http://nick.divbyzero.com >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >>> /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 Thu Jun 25 09:13:23 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 25 Jun 2015 15:13:23 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: References: <55887254.6060204@redhat.com> <5589AFD8.9060106@redhat.com> Message-ID: <9EBDBCEC-D365-4931-9A6D-F4E0FCC1C7AC@redhat.com> On 23 Jun 2015, at 21:32, Max Rydahl Andersen wrote: > On 23 Jun 2015, at 21:13, Nick Boldt wrote: > >> Do you mean this? >> >> http://download.jboss.org/jbosstools/static/mars/development/updates/core/4.3.0.Beta1/buildinfo.json > This file has the following segment: "http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/": "Build info file not accessible: http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/buildinfo.json", "http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/": "Build info file not accessible: http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/buildinfo.json" } how come ? shouldn't this contain the actual used content ? /max http://about.me/maxandersen From manderse at redhat.com Thu Jun 25 18:41:27 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 26 Jun 2015 00:41:27 +0200 Subject: [jbosstools-dev] Question on all external users of IJBoss7ManagerService In-Reply-To: <558C32CA.6080306@redhat.com> References: <558B11DA.7040605@redhat.com> <558C32CA.6080306@redhat.com> Message-ID: <59912FB2-2A94-4D8C-B4D3-828DCA9BF355@redhat.com> On 25 Jun 2015, at 18:56, Rob Stryker wrote: > On 06/25/2015 05:47 AM, Max Rydahl Andersen wrote: >> >>> My PR to fix the issue creates a 71x service inside the >>> org.jboss.ide.eclipse.as.management.wildfly8 to live along side the >>> wf8 >>> service. Unfortunately, it seems strange now to have a plugin named >>> org.jboss.ide.eclipse.as.management.as71 which holds a service with >>> version=7.1.0.Beta1 which only works for AS 7.0.x =P Seems a bit >>> odd, no? >> >> eh - why would as71 not continue to work with AS 7.1, EAP etc. ? > > I'm saying that in my PR, the jars in the as71 management plugin > would only work for as70, Are you somehow going to make it impossible for use the as71 to work for others but as70 ? aren't you just going to start using newer management version with the other server adapters ? i.e. as71 is not changing from how it was before ? it is the as71 client jars - that is it; and we choose in our server adapter which one we use that fit best - currently that is now the as9.management jars, right ? > while the jars in the wf8 plugin will work for as71 through wf9. in the first mail you said it was the wf9 jars that would make it better, now you say wf8 ? which one is it ? > This is pretty confusing, since someone might expect the jars in the > as71 plugin are the one being used for as71, which won't be the case. no, but I do not think this is a problem. the management.as71 means the "management jars from as71", right ? Not "the management jars used only for as71". > Of course if a client were using the mgmt plugins properly, they'd > have an IServer already, and use the existing API (Extended > properties, etc) to get the management service. But if they're > "hand-rolling" their own solution by locating services with specific > version strings, or depending on specific plugins, this becomes more > of an issue. > > > Ideally I'd like to rename the plugins to match better their > functionality. I never seen them as what their functionality are, but what client jars they contain. Which then are selected by the server adapter to what they want to use ? > I'd also like to rename the constants to match what they actually work > for, so we don't have constants with strings including "beta1" or > other such nonesense... But in order to do this safely, I need to > know who our external users are of the IJBoss7ManagerService, what > constants they use, whether they depend on a given plugin name > directly (either in their manifests or features), or if they just > depend on my AS feature (and then I pull in all the management stuff). I don't know what those constants are and why we would ever have such....you should just go look in teiid designer and fuse tools code base - they are afaik the only one using us. But seems like we are cleaning something up that dont need much cleaning up...but seeing the PR could help answer that. > Basically, I'd like to clean up the code, rename the things that make > no sense, and harmonize the situation ;) show the PR. For now, your description of management.asXY did not seem to need harmonizing afaics - it already is harmonised. /max http://about.me/maxandersen From nboldt at redhat.com Fri Jun 26 10:04:18 2015 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 26 Jun 2015 10:04:18 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <9EBDBCEC-D365-4931-9A6D-F4E0FCC1C7AC@redhat.com> References: <55887254.6060204@redhat.com> <5589AFD8.9060106@redhat.com> <9EBDBCEC-D365-4931-9A6D-F4E0FCC1C7AC@redhat.com> Message-ID: <558D5BE2.3090801@redhat.com> Those were built BEFORE we had buildinfo.json files as part of the builds. So, therefore "Build info file not accessible". Would you prefer a null or "" to a useful error message? On 06/25/2015 09:13 AM, Max Rydahl Andersen wrote: > On 23 Jun 2015, at 21:32, Max Rydahl Andersen wrote: > >> On 23 Jun 2015, at 21:13, Nick Boldt wrote: >> >>> Do you mean this? >>> >>> http://download.jboss.org/jbosstools/static/mars/development/updates/core/4.3.0.Beta1/buildinfo.json >>> >> > > This file has the following segment: > > "http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/": > "Build info file not accessible: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/buildinfo.json", > > "http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/": "Build > info file not accessible: > http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/buildinfo.json" > > } > > how come ? > > shouldn't this contain the actual used content ? > > /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 Jun 26 10:16:44 2015 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 26 Jun 2015 10:16:44 -0400 Subject: [jbosstools-dev] Parent pom 4.3.0.Beta2-SNAPSHOT reverted to use Tycho 0.22.0 (was Re: Fwd: [tycho-user] Tycho milestone 0.23.0 released) In-Reply-To: <5578807E.40403@redhat.com> References: <55759870.9000803@gmail.com> <55763C28.8020107@redhat.com> <5578807E.40403@redhat.com> Message-ID: <558D5ECC.5080002@redhat.com> Due to problems building JBT aggregate [1], [2] I have reverted parent pom 4.3.0.Beta2-SNAPSHOT to use Tycho 0.22.0. [1] https://issues.jboss.org/browse/JBIDE-19973 [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=470074 On 06/10/2015 02:22 PM, Nick Boldt wrote: > Pushed to master (parent pom Beta2): > > https://github.com/jbosstools/jbosstools-build/commit/551c2ba6c3a28afe80c18240bc0ce8af3fb4f64d > > > Note that we need to investigate if 0.23 breaks anything in any of the > other jbosstools-* repos that don't depend on parent pom, such as > target-platforms, discovery, and build-sites, build-ci, maven-plugins, ... > > > > On 06/10/2015 11:38 AM, Denis Golovin wrote: >> verified full build with 0.23.0 release and everything is looking fine. >> >> On Mon, Jun 8, 2015 at 6:06 PM, Nick Boldt > > wrote: >> >> Does that by any chance mean you've successfully built the whole >> stack >> w/ 0.23.0, including JBDS? >> >> On 06/08/2015 06:45 PM, Denis Golovin wrote: >> > +1 >> > >> > On Mon, Jun 8, 2015 at 6:28 AM, Nick Boldt > >> > >> wrote: >> > >> > FYI, Tycho 0.23 is released. >> > >> > We should move up to using this in master branch. >> > >> >https://issues.jboss.org/browse/JBIDE-19973 >> > >> > >> > -------- Forwarded Message -------- >> > Subject: [tycho-user] Tycho milestone 0.23.0 released >> > Date: Mon, 8 Jun 2015 07:34:48 +0000 >> > From: Sievers, Jan > >> >> >> > Reply-To: Tycho user list > >> > > >> >> > To: Tycho user list (tycho-user at eclipse.org >> >> > > >) >> >> > > >>, >> > Tycho developers list (tycho-dev at eclipse.org >> >> > > >) > >> > >> >> > >> > Tycho milestone 0.23.0 has been released and is available >> from maven >> > central. >> > >> > See the release notes [1] for details of enhancements and >> bug fixes in >> > this release. >> > >> > Thanks to >> > >> > Christian Dietrich >> > Enrico De Fent >> > Christian Georgi >> > Michael Keppler >> > Pascal Rapicault >> > Gunnar Wagenknecht >> > >> > who contributed patches for this release. >> > >> > And thanks and to everyone who helped us with testing the >> staged >> > version. >> > >> > Regards, >> > Tycho team >> > >> > [1]http://wiki.eclipse.org/Tycho/Release_Notes/0.23 >> > _______________________________________________ >> > tycho-user mailing list >> > tycho-user at eclipse.org >> > >> > To change your delivery options, retrieve your password, or >> unsubscribe >> > from this list, visit >> >https://dev.eclipse.org/mailman/listinfo/tycho-user >> > >> > >> > _______________________________________________ >> > 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 >> >> > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From fbricon at gmail.com Fri Jun 26 10:18:23 2015 From: fbricon at gmail.com (Fred Bricon) Date: Fri, 26 Jun 2015 10:18:23 -0400 Subject: [jbosstools-dev] m2e 1.6.1 is staged Message-ID: Hi, the m2e-android team found a serious issue with the way project configurators are ordered with the new runsAfter/runsBefore directives[1] in m2e 1.6.0. This would lead to configurators being completely ignored and generate Plugins Execution Not Covered errors. Hence, I staged m2e 1.6.1, fixing that issue, available in the milestones update site[2]. We'd appreciate if developers of 3rd party configurators could check it works for them. If no regressions are found, I'll release m2e 1.6.1 on Monday 26/06/2015. m2e 1.6.1 will be added to the next Eclipse Mars SR1 release, in September. Thanks, Fred [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=471038 [2] http://download.eclipse.org/technology/m2e/milestones/1.6/ -- "Have you tried turning it off and on again" - The IT Crowd And if that fails, then http://goo.gl/tnBgH5 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150626/e4230283/attachment.html From rstryker at redhat.com Sat Jun 27 00:16:54 2015 From: rstryker at redhat.com (Rob Stryker) Date: Sat, 27 Jun 2015 00:16:54 -0400 Subject: [jbosstools-dev] Question on all external users of IJBoss7ManagerService In-Reply-To: <59912FB2-2A94-4D8C-B4D3-828DCA9BF355@redhat.com> References: <558B11DA.7040605@redhat.com> <558C32CA.6080306@redhat.com> <59912FB2-2A94-4D8C-B4D3-828DCA9BF355@redhat.com> Message-ID: <558E23B6.9070301@redhat.com> I need to know what kind of patch to make, before I simply show a patch. Please read below. > >> while the jars in the wf8 plugin will work for as71 through wf9. > > in the first mail you said it was the wf9 jars that would make it > better, now you say wf8 ? which one is it ? The suggested patch is to change the wf8.management plugin's jars to use wf9 jars, and change as7.1 and later (and all eap6.x) to use the wf9 jars in the wf8.management plugin. So I mean just what I said: the jars in the wf8 plugin (which, post-patch, would be jars from wf9). > >> This is pretty confusing, since someone might expect the jars in the >> as71 plugin are the one being used for as71, which won't be the case. > > no, but I do not think this is a problem. the management.as71 means > the "management jars from as71", right ? Not "the management jars used > only for as71". At this point, the various management plugins names have absolutely no logical meaning. It doesn't mean "jars that work for server-X" and it doesn't mean "jars FROM server-X". As of right now, the as71.management plugin's jars are from eap6.1, and works for as70 through eap6x (except for the one bug we found). As of right now, the wf8.management plugin's jars are from wf8.2, and work with all wildfly versions. > > [sic] > I never seen them as what their functionality are, but what client > jars they contain. As mentioned above, this isn't true. The as71.management plugin has jars from EAP6.1. In the past we had two plugins for as7x vs wf, and would just try to find the best jars to fit there, regardless of where they were from. The suggested patch is to change the wf8.management plugin's jars to use wf9 jars, and change as7.1 and later (and all eap6.x) to use the wf9 jars in the wf8.management plugin. After the patch, the as70 adapter would use the as71.management plugin's jars, which are actually from eap6.1 (usecase is unchanged from previous). After the patch, the as71 adapter would use the "wf8.management" plugin's jars, which are actually jars from wf9 (after this PR). Maybe others find this logical... I find it very confusing... both the current case and the post-patch case. At this point, the various management plugins names have absolutely no logical meaning. It doesn't mean "jars that work for server-X", it doesn't mean "jars currently being used for server-adapter-X", and it doesn't mean "jars FROM server-X". The only way to give them a meaning that's consistent is one of the following: 1) Stick to "plugin names means jars FROM server-version-X" 2) Stick to "plugin names means jars that work FOR server version X" Both have their own problems. Option 1 means I must rename plugins every time I get a set of jars from a newer version of the app-server. Option 2 is still kinda vague. Post-patch, technically, the eap6.1 jars (in the as71.management plugin) WILL work for as71, but, as71 won't be using them, as it'd be using the wf9 jars in the wf8.management plugin to fix the above bug. No matter what, the current situation makes no sense at all ;) From mistria at redhat.com Mon Jun 29 03:14:40 2015 From: mistria at redhat.com (Mickael Istria) Date: Mon, 29 Jun 2015 09:14:40 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <55887254.6060204@redhat.com> References: <55887254.6060204@redhat.com> Message-ID: <5590F060.90708@redhat.com> Done for jbosstools-playground. -- 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/20150629/0980919e/attachment.html From mistria at redhat.com Mon Jun 29 03:18:19 2015 From: mistria at redhat.com (Mickael Istria) Date: Mon, 29 Jun 2015 09:18:19 +0200 Subject: [jbosstools-dev] m2e 1.6.1 is staged In-Reply-To: References: Message-ID: <5590F13B.8060306@redhat.com> Hi Fred, Do you think it's important that we include this staged version in JBoss Tools for next development and milestone, or is it OK to stick with the 1.6.0 and adopt 1.6.1 when we adopt Mars SR1? If it needs to be changed before Mars SR1, can you please put that in a Jira? 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/20150629/2c14316f/attachment.html From manderse at redhat.com Mon Jun 29 05:43:54 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 29 Jun 2015 11:43:54 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <558D5BE2.3090801@redhat.com> References: <55887254.6060204@redhat.com> <5589AFD8.9060106@redhat.com> <9EBDBCEC-D365-4931-9A6D-F4E0FCC1C7AC@redhat.com> <558D5BE2.3090801@redhat.com> Message-ID: <4E07804E-F0BB-439B-AE4A-2821B65C2ECC@redhat.com> On 26 Jun 2015, at 16:04, Nick Boldt wrote: > Those were built BEFORE we had buildinfo.json files as part of the > builds. So, therefore "Build info file not accessible". > > Would you prefer a null or "" to a useful error message? I would prefer two things: 1) That the format of the file is consistent so it is easy to parse. In this case it could be okey, just a bit weird having to say "if v is not type dict then read string as error". 2) That if we have missing pieces in our build to have consistent info about which builds are used we should get that fixed ASAP. i.e. in this case either get those built or still use old way to get this info for those two builds to at least have the info recorded so we can get them properly tagged. Can you tell which tags to use for the tag ? /max > > On 06/25/2015 09:13 AM, Max Rydahl Andersen wrote: >> On 23 Jun 2015, at 21:32, Max Rydahl Andersen wrote: >> >>> On 23 Jun 2015, at 21:13, Nick Boldt wrote: >>> >>>> Do you mean this? >>>> >>>> http://download.jboss.org/jbosstools/static/mars/development/updates/core/4.3.0.Beta1/buildinfo.json >>>> >>> >> >> This file has the following segment: >> >> "http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/": >> "Build info file not accessible: >> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/buildinfo.json", >> >> "http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/": >> "Build >> info file not accessible: >> http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/buildinfo.json" >> >> } >> >> how come ? >> >> shouldn't this contain the actual used content ? >> >> /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 Jun 29 06:22:14 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 29 Jun 2015 12:22:14 +0200 Subject: [jbosstools-dev] Question on all external users of IJBoss7ManagerService In-Reply-To: <558E23B6.9070301@redhat.com> References: <558B11DA.7040605@redhat.com> <558C32CA.6080306@redhat.com> <59912FB2-2A94-4D8C-B4D3-828DCA9BF355@redhat.com> <558E23B6.9070301@redhat.com> Message-ID: <1AE83DA2-BEA3-481D-82F1-61BAEBA4B4B4@redhat.com> >>> This is pretty confusing, since someone might expect the jars in the >>> as71 plugin are the one being used for as71, which won't be the >>> case. >> >> no, but I do not think this is a problem. the management.as71 means >> the "management jars from as71", right ? Not "the management jars >> used only for as71". > > At this point, the various management plugins names have absolutely no > logical meaning. It doesn't mean "jars that work for server-X" and it > doesn't mean "jars FROM server-X". > > As of right now, the as71.management plugin's jars are from eap6.1, > and works for as70 through eap6x (except for the one bug we found). > As of right now, the wf8.management plugin's jars are from wf8.2, and > work with all wildfly versions. Is it not up to the server adapters to state what management library they use ? Then have the management plugin state which version their libraries are *from*, not what version they are used with. Then the server adapters state which management version they wish/want/need to use. Then there is no ambiguity and no need to rename the plugins everytime we need to update. >> [sic] >> I never seen them as what their functionality are, but what client >> jars they contain. > > As mentioned above, this isn't true. The as71.management plugin has > jars from EAP6.1. In the past we had two plugins for as7x vs wf, and > would just try to find the best jars to fit there, regardless of where > they were from. So stop doing that and make their name match what they contain. > The suggested patch is to change the wf8.management plugin's jars to > use wf9 jars, and change as7.1 and later (and all eap6.x) to use the > wf9 jars in the wf8.management plugin. I think that is the wrong direction. This will imply you will have to keep update the management plugins instead of have them actually stay consistent. > After the patch, the as70 adapter would use the as71.management > plugin's jars, which are actually from eap6.1 (usecase is unchanged > from previous). > After the patch, the as71 adapter would use the "wf8.management" > plugin's jars, which are actually jars from wf9 (after this PR). why not wf9.management and then have as71 use that ? > Maybe others find this logical... I find it very confusing... both the > current case and the post-patch case. It is completely illogical - which is why I suggest to have the management plugin name match what it actually is. Having AS7 adapter using a wf9.management since they are known to be compatible is more sane than having as7 use wf8.management with wf9 jars in them. > At this point, the various management plugins names have absolutely no > logical meaning. It doesn't mean "jars that work for server-X", it > doesn't mean "jars currently being used for server-adapter-X", and it > doesn't mean "jars FROM server-X". Make it jars from server-X and things are lot less confusing. > The only way to give them a meaning that's consistent is one of the > following: > 1) Stick to "plugin names means jars FROM server-version-X" > 2) Stick to "plugin names means jars that work FOR server version X" Current situation is closer to #1 than it is #2. > Both have their own problems. > > Option 1 means I must rename plugins every time I get a set of jars > from a newer version of the app-server. no, it means you add a new plugin when needed and only for major versions. > Option 2 is still kinda vague. Post-patch, technically, the eap6.1 > jars (in the as71.management plugin) WILL work for as71, but, as71 > won't be using them, as it'd be using the wf9 jars in the > wf8.management plugin to fix the above bug. option 2 is just weird imo ;) > No matter what, the current situation makes no sense at all ;) go for option 1. Or have an option 3 where the names are more descriptive (I don't have a good suggestion for those ;) /max http://about.me/maxandersen From manderse at redhat.com Mon Jun 29 06:23:49 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 29 Jun 2015 12:23:49 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <5590F060.90708@redhat.com> References: <55887254.6060204@redhat.com> <5590F060.90708@redhat.com> Message-ID: <327D7D68-E075-4DCE-9C74-1169B6356A91@redhat.com> On 29 Jun 2015, at 9:14, Mickael Istria wrote: > Done for jbosstools-playground. any ETA on when playground can gets dropped from build ? this one was intended to only be included for beta1 as fast way to get easyimport working. For beta2/GA we need playground to be removed from our build chain. /max http://about.me/maxandersen From mistria at redhat.com Mon Jun 29 06:27:02 2015 From: mistria at redhat.com (Mickael Istria) Date: Mon, 29 Jun 2015 12:27:02 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <327D7D68-E075-4DCE-9C74-1169B6356A91@redhat.com> References: <55887254.6060204@redhat.com> <5590F060.90708@redhat.com> <327D7D68-E075-4DCE-9C74-1169B6356A91@redhat.com> Message-ID: <55911D76.5080401@redhat.com> On 06/29/2015 12:23 PM, Max Rydahl Andersen wrote: > On 29 Jun 2015, at 9:14, Mickael Istria wrote: > >> Done for jbosstools-playground. > > any ETA on when playground can gets dropped from build ? this one was > intended to only be included for beta1 as fast way to get easyimport > working. > For beta2/GA we need playground to be removed from our build chain. The m2e and WTP support for importer is still to be migrated to the related projects. Given the current weak reactions of those project team after various request, I'm not very optimistic in our ability to move those in the m2e or WTP code-base soon enough for Beta2. However, we could move them to our jbosstools-javaee and jbosstools-central repository in the meantime. 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/20150629/cf930b66/attachment-0001.html From manderse at redhat.com Mon Jun 29 06:29:12 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 29 Jun 2015 12:29:12 +0200 Subject: [jbosstools-dev] m2e 1.6.1 is staged In-Reply-To: <5590F13B.8060306@redhat.com> References: <5590F13B.8060306@redhat.com> Message-ID: <270A88A2-56FD-4DAF-A0A3-F99CAC6A925B@redhat.com> On 29 Jun 2015, at 9:18, Mickael Istria wrote: > Hi Fred, > > Do you think it's important that we include this staged version in > JBoss Tools for next development and milestone, or is it OK to stick > with the 1.6.0 and adopt 1.6.1 when we adopt Mars SR1? > If it needs to be changed before Mars SR1, can you please put that in > a Jira? Fred is on PTO. I think Fred mails make it pretty clear that for us to get a proper working m2e integration we need 1.6.1. I would say getting this in as soon as possible would be good. I've opened https://issues.jboss.org/browse/JBIDE-20161 btw. if we are doing an update to Mars SR1 RC1 soon then it could fit in there, but we can't wait until SR1 GA to include this IMO. /max > > Cheers, > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat > My blog - My Tweets > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Mon Jun 29 06:44:27 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 29 Jun 2015 12:44:27 +0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ] In-Reply-To: <55911D76.5080401@redhat.com> References: <55887254.6060204@redhat.com> <5590F060.90708@redhat.com> <327D7D68-E075-4DCE-9C74-1169B6356A91@redhat.com> <55911D76.5080401@redhat.com> Message-ID: On 29 Jun 2015, at 12:27, Mickael Istria wrote: > On 06/29/2015 12:23 PM, Max Rydahl Andersen wrote: >> On 29 Jun 2015, at 9:14, Mickael Istria wrote: >> >>> Done for jbosstools-playground. >> >> any ETA on when playground can gets dropped from build ? this one was >> intended to only be included for beta1 as fast way to get easyimport >> working. >> For beta2/GA we need playground to be removed from our build chain. > The m2e and WTP support for importer is still to be migrated to the > related projects. Given the current weak reactions of those project > team after various request, I'm not very optimistic in our ability to > move those in the m2e or WTP code-base soon enough for Beta2. Got a link to bugs we got open for these projects where response been "weak" ? > However, we could move them to our jbosstools-javaee and > jbosstools-central repository in the meantime. WDYT? That is better than having it in playground IMO. The biggest issue is to avoid build chain being to messy; so putting as low as possible would be good. /max http://about.me/maxandersen From nboldt at redhat.com Mon Jun 29 09:57:24 2015 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 29 Jun 2015 09:57:24 -0400 Subject: [jbosstools-dev] m2e 1.6.1 is staged In-Reply-To: <270A88A2-56FD-4DAF-A0A3-F99CAC6A925B@redhat.com> References: <5590F13B.8060306@redhat.com> <270A88A2-56FD-4DAF-A0A3-F99CAC6A925B@redhat.com> Message-ID: <55914EC4.9000409@redhat.com> We won't be doing "an update to Mars SR1 RC1" until late August. https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#SR1 So if this is needed for 4.3.0.Beta2, then it needs to happen NOW - target platform freeze is only a couple weeks from now, on Jul 14. (TP release Jul 15, Beta2 CF Jul 16.) If not, then it can wait until 4.3.0.CR1 when we pick up Mars SR1 RCx bits. On 06/29/2015 06:29 AM, Max Rydahl Andersen wrote: > On 29 Jun 2015, at 9:18, Mickael Istria wrote: > >> Hi Fred, >> >> Do you think it's important that we include this staged version in >> JBoss Tools for next development and milestone, or is it OK to stick >> with the 1.6.0 and adopt 1.6.1 when we adopt Mars SR1? >> If it needs to be changed before Mars SR1, can you please put that in >> a Jira? > > Fred is on PTO. > > I think Fred mails make it pretty clear that for us to get a proper > working m2e integration we need 1.6.1. > > I would say getting this in as soon as possible would be good. I've > opened https://issues.jboss.org/browse/JBIDE-20161 > > btw. if we are doing an update to Mars SR1 RC1 soon then it could fit in > there, but we can't wait until SR1 GA to include this IMO. > > > > /max > >> >> Cheers, >> -- >> Mickael Istria >> Eclipse developer at JBoss, by Red Hat >> My blog - My Tweets >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen > _______________________________________________ > 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 rstryker at redhat.com Mon Jun 29 15:46:43 2015 From: rstryker at redhat.com (Rob Stryker) Date: Mon, 29 Jun 2015 15:46:43 -0400 Subject: [jbosstools-dev] Question on all external users of IJBoss7ManagerService In-Reply-To: <1AE83DA2-BEA3-481D-82F1-61BAEBA4B4B4@redhat.com> References: <558B11DA.7040605@redhat.com> <558C32CA.6080306@redhat.com> <59912FB2-2A94-4D8C-B4D3-828DCA9BF355@redhat.com> <558E23B6.9070301@redhat.com> <1AE83DA2-BEA3-481D-82F1-61BAEBA4B4B4@redhat.com> Message-ID: <5591A0A3.1030801@redhat.com> On 06/29/2015 06:22 AM, Max Rydahl Andersen wrote: > > Then have the management plugin state which version their libraries > are *from*, not what version they are used with. > > Then the server adapters state which management version they > wish/want/need to use. > > Then there is no ambiguity and no need to rename the plugins everytime > we need to update. Perhaps I'm missing something here. I don't see how your example prevents me from having to rename plugins. If, for example, I have a plugin with jars from wf8, and the plugin is named wf8.management, and then we decide to upgrade to wf9 jars, I don't see how your solution fixes anything? It seems my migration path is to then: 1) Rename the wf8 plugin to wf9, so that its name matches what jars are inside it 2) Update feature, etc 3) Rename various classes to have wf9 in name instead of wf8 4) Add a new service component with version 9.0.0, with new service impl class 5) Change existing 8.0.0 service component to delegate to 9.0.0 6) Add new version constant to IJBoss7ManagerService list of constants, to ensure that any downstream adopter (teiid fuse etc) depending on specific service versions (which they shouldn't do, but still might) are not broken by a removed constant or a removed service corresponding to that constant. Or are you suggesting that I keep the wf8.management plugin with its constants and jars and then add a new wf9.management plugin with new constants / services / jars? Clearly then we'd experience a ballooning of client jars... -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150629/56ace75e/attachment.html From fbricon at gmail.com Mon Jun 29 15:51:16 2015 From: fbricon at gmail.com (Fred Bricon) Date: Mon, 29 Jun 2015 15:51:16 -0400 Subject: [jbosstools-dev] m2e 1.6.1 is available Message-ID: Hi, we just released m2e 1.6.1 (git tag releases/1.6/1.6.1.20150625-2338), fixing a bug with the new runsAfter/runsBefore directives[1], found by the m2e-android team. m2e 1.6.1 can be installed manually from this p2 update site[2]. m2e 1.6.1 will be added to the next Eclipse Mars SR1 release, in September, unless a new release is required till then. Regards, Fred [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=471038 [2] http://download.eclipse.org/technology/m2e/releases/ -- "Have you tried turning it off and on again" - The IT Crowd And if that fails, then http://goo.gl/tnBgH5 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150629/cdaf1ea4/attachment.html From manderse at redhat.com Tue Jun 30 05:34:09 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 30 Jun 2015 11:34:09 +0200 Subject: [jbosstools-dev] default branch for jbosstools-build-ci set to jbosstools-4.3.x Message-ID: <8A58FD8C-56D4-4A83-8C58-E87DC940E154@redhat.com> hey, just a fyi that https://github.com/jbosstools/jbosstools-build-ci now defaults to jbosstools-4.3.x instead of master. The `master` branch is by now deprecated for this repository but we cannot change it since old builds unfortunately rely directly on the `master` branch. thus changing it to be default jbosstools-4.3.x so merges/PR's/browsing stop defaulting to master which should not be changing anyways ;) Let me know if it gives problems. /max http://about.me/maxandersen From manderse at redhat.com Tue Jun 30 05:54:16 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 30 Jun 2015 11:54:16 +0200 Subject: [jbosstools-dev] m2e 1.6.1 is staged In-Reply-To: <55914EC4.9000409@redhat.com> References: <5590F13B.8060306@redhat.com> <270A88A2-56FD-4DAF-A0A3-F99CAC6A925B@redhat.com> <55914EC4.9000409@redhat.com> Message-ID: On 29 Jun 2015, at 15:57, Nick Boldt wrote: > We won't be doing "an update to Mars SR1 RC1" until late August. > > https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#SR1 > > So if this is needed for 4.3.0.Beta2, then it needs to happen NOW - > target platform freeze is only a couple weeks from now, on Jul 14. (TP > release Jul 15, Beta2 CF Jul 16.) > > If not, then it can wait until 4.3.0.CR1 when we pick up Mars SR1 RCx > bits. Waiting until August is too late to start testing with it. JBIDE-20161 is set to 4.3.0.Beta2 to indicate that. Fred is on PTO the next two weeks but he did release 1.6.1 yesterday as I understood it. Can you or mistria handle this update? /max > > On 06/29/2015 06:29 AM, Max Rydahl Andersen wrote: >> On 29 Jun 2015, at 9:18, Mickael Istria wrote: >> >>> Hi Fred, >>> >>> Do you think it's important that we include this staged version in >>> JBoss Tools for next development and milestone, or is it OK to stick >>> with the 1.6.0 and adopt 1.6.1 when we adopt Mars SR1? >>> If it needs to be changed before Mars SR1, can you please put that >>> in >>> a Jira? >> >> Fred is on PTO. >> >> I think Fred mails make it pretty clear that for us to get a proper >> working m2e integration we need 1.6.1. >> >> I would say getting this in as soon as possible would be good. I've >> opened https://issues.jboss.org/browse/JBIDE-20161 >> >> btw. if we are doing an update to Mars SR1 RC1 soon then it could fit >> in >> there, but we can't wait until SR1 GA to include this IMO. >> >> >> >> /max >> >>> >>> Cheers, >>> -- >>> Mickael Istria >>> Eclipse developer at JBoss, by Red Hat >>> My blog - My Tweets >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> /max >> http://about.me/maxandersen >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From manderse at redhat.com Tue Jun 30 06:14:38 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 30 Jun 2015 12:14:38 +0200 Subject: [jbosstools-dev] Question on all external users of IJBoss7ManagerService In-Reply-To: <5591A0A3.1030801@redhat.com> References: <558B11DA.7040605@redhat.com> <558C32CA.6080306@redhat.com> <59912FB2-2A94-4D8C-B4D3-828DCA9BF355@redhat.com> <558E23B6.9070301@redhat.com> <1AE83DA2-BEA3-481D-82F1-61BAEBA4B4B4@redhat.com> <5591A0A3.1030801@redhat.com> Message-ID: <7120BD77-1534-42D2-9942-02C87C5949F2@redhat.com> we talked on chat yesterday, but just to conclude on this thread. I was simply suggesting that the management.xyz bundles got a consistent name related to what they contain OR get some name not related to specific version of libs. from our chat what I got is we ended up with: * management.xyz bundle names will match what libs they contain. ie. management.as7 has jars from as7x, management.wf9 from wildfly 9 * service lookups targets which version to support (not what jars to use), so adapters does not have to update their lookups - we just need to repackage the management jars. The rest we would take once PR was done to try/give more direct feedback on. /max >> >> Then have the management plugin state which version their libraries >> are *from*, not what version they are used with. >> >> Then the server adapters state which management version they >> wish/want/need to use. >> >> Then there is no ambiguity and no need to rename the plugins >> everytime we need to update. > > > Perhaps I'm missing something here. I don't see how your example > prevents me from having to rename plugins. > > If, for example, I have a plugin with jars from wf8, and the plugin is > named wf8.management, and then we decide to upgrade to wf9 jars, I > don't see how your solution fixes anything? It seems my migration > path is to then: > > 1) Rename the wf8 plugin to wf9, so that its name matches what jars > are inside it > 2) Update feature, etc > 3) Rename various classes to have wf9 in name instead of wf8 > 4) Add a new service component with version 9.0.0, with new service > impl class > 5) Change existing 8.0.0 service component to delegate to 9.0.0 > 6) Add new version constant to IJBoss7ManagerService list of > constants, to ensure that any downstream adopter (teiid fuse etc) > depending on specific service versions (which they shouldn't do, but > still might) are not broken by a removed constant or a removed service > corresponding to that constant. > > > Or are you suggesting that I keep the wf8.management plugin with its > constants and jars and then add a new wf9.management plugin with new > constants / services / jars? Clearly then we'd experience a > ballooning of client jars... /max http://about.me/maxandersen From nboldt at redhat.com Tue Jun 30 11:39:00 2015 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 30 Jun 2015 11:39:00 -0400 Subject: [jbosstools-dev] Change to JBoss Tools / JBDS Target Platforms 4.50.0.Beta2-SNAPSHOT: new m2e 1.6.1 Message-ID: <5592B814.7020109@redhat.com> Per discussion: http://lists.jboss.org/pipermail/jbosstools-dev/2015-June/010291.html http://lists.jboss.org/pipermail/jbosstools-dev/2015-June/010305.html And JIRA: https://issues.jboss.org/browse/JBIDE-20161 And p2diffs: https://issues.jboss.org/secure/attachment/12390765/p2diff.jbds.m2e161.txt https://issues.jboss.org/secure/attachment/12390764/p2diff.jbt.m2e161.txt I've merged the PR and the new TP is building now. Please try it out in a couple hours when it's done. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com