January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16351: --------------------------------------- > Can this explain why wildfly is so slow to build ? FixClasspathContainer slows down building a Maven Java project (including wildfly), but not as much as it is Andre's issue (20 minutes). > What jira introduced this configurator ? I assume it was requested in context of WFK Seam 2 maven projects which > still are part of wfk so just wondering if it is still relevant for them ? JBIDE-7011 I don't think that is relevant anymore, but will test WFK seam 2 maven projects. Do you mean wfk 2.4.0 seam demo? > Should also consider removing this in maintanence branch if no use for it. I think we can remove this configurator in the maintenance branch too. > FixClasspathConfigurator isn't obliged in a newer m2e > ----------------------------------------------------- > > Key: JBIDE-16351 > URL: https://issues.jboss.org/browse/JBIDE-16351 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Fred Bricon > Fix For: 4.2.0.Alpha2 > > > The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433. > The issue happens with a mavenized seam 2 project that has a flat layout structure. > This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project. > It is the configurator for maven-compiler-plugin so it is called for every Java project. > Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies) > The solution: > - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2669: ----------------------------- Attachment: update-product-manually-with-refactoring-full-featureset-review.png update-product-manually-with-refactoring-full-featureset.png update-product-manually-with-refactoring.png Realized I missed a couple things so I've added one more commit to the above PR & TB: https://github.com/nickboldt/jbdevstudio-product/commit/e23487879e7c55c0b... We can now update from 8.0.0.Alpha1 (old namespaces) to 8.0.0.Alpha2 (new namespaces): !update-product-manually-with-refactoring.png! !update-product-manually-with-refactoring-full-featureset.png! !update-product-manually-with-refactoring-full-featureset-review.png! > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2669 at 1/16/14 12:12 PM: ------------------------------------------------------------ Realized I missed a couple things so I've added one more commit to the above PR & TB: https://github.com/nickboldt/jbdevstudio-product/commit/e23487879e7c55c0b... We can now update from 8.0.0.Alpha1 (old namespaces) to 8.0.0.Alpha2 (new namespaces): ----- !update-product-manually-with-refactoring.png! ----- !update-product-manually-with-refactoring-full-featureset.png! ----- !update-product-manually-with-refactoring-full-featureset-review.png! was (Author: nickboldt): Realized I missed a couple things so I've added one more commit to the above PR & TB: https://github.com/nickboldt/jbdevstudio-product/commit/e23487879e7c55c0b... We can now update from 8.0.0.Alpha1 (old namespaces) to 8.0.0.Alpha2 (new namespaces): !update-product-manually-with-refactoring.png! !update-product-manually-with-refactoring-full-featureset.png! !update-product-manually-with-refactoring-full-featureset-review.png! > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16311) release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16311?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16311: ---------------------------------------- Why waiting for Luna M5 to close this issue if it works fine with Luna M4? Things that are known to crash luna M4 are: * the jetty.birt.overlay fragment * VPE and loading of XulRunner None of them if part of the webtools site. > release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it > --------------------------------------------------------------------------- > > Key: JBIDE-16311 > URL: https://issues.jboss.org/browse/JBIDE-16311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Alpha2 > > Attachments: eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1.png, eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1_2.png > > > Need a semi-working placeholder (even if it's a weak first alpha) so that WTP can resolve http://download.jboss.org/jbosstools/updates/webtools/luna/ as a valid site. > Content that needs to be verified (install tested) and renamed is here: > http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.webt... > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=424213 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16332) VisualEditor: Use JavaFX WebView to render JSP/XHTML/HTML pages at design time

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16332?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-16332 at 1/16/14 11:57 AM: ----------------------------------------------------------------- *Oracle Java FX WebKit* Webkit compiled from fork located [here|https://oss.oracle.com/projects/webkit-java-mods]. Html 5 rating is close to 500 according http://html5test.com/. || || Java7 32bit || Java7 64bit || Java8 32bit || Java8 64bit || || Windows 32bit | | *X* | | *X* | || Windows 64bit | | ? | | ? | || OS X 32bit | *X* | *X* | *X* | *X* | || OS X 64bit | *X* | | *X* | | || Linux 32bit *| | *X* | | *X* | || Linux 64bit *| | | | | \* No GTK3 support for linux Advantages: * * Disadvantages: * * Performance: was (Author: dgolovin): *Oracle Java FX WebKit* Webkit compiled from fork located [here|https://oss.oracle.com/projects/webkit-java-mods]. Html 5 rating is close to 500 according http://html5test.com/. || || Java7 32bit || Java7 64bit || Java8 32bit || Java8 64bit || || Windows 32bit | | *X* | | *X* | || Windows 64bit | | ? | | ? | || OS X 32bit | *X* | *X* | *X* | *X* | || OS X 64bit | *X* | | *X* | | || Linux 32bit *| | *X* | | *X* | || Linux 64bit *| | | | | \* No GTK3 support for linux Adwantages: * * Disadwantages: * * Performance: > VisualEditor: Use JavaFX WebView to render JSP/XHTML/HTML pages at design time > ------------------------------------------------------------------------------ > > Key: JBIDE-16332 > URL: https://issues.jboss.org/browse/JBIDE-16332 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.2.x > Reporter: Denis Golovin > Assignee: Denis Golovin > > Questions to answer: > 1) compatibility when both osgi hooks in place our and e(fx)clipse > 2) is it working with gtk3 > 3) check how to add osgi hooks parameters into user's eclipse when installing from update site (p2 tochpoints should help) > 4) how javafx load webkit and how it collides with eclipse loaded web kit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16368) Clean useless features from TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16368?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16368: ----------------------------------- Priority: Optional (was: Major) > Clean useless features from TP > ------------------------------ > > Key: JBIDE-16368 > URL: https://issues.jboss.org/browse/JBIDE-16368 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.x > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.2.x > > > In order to trim some stuff out of our target-platform, we should: > * Install JBDS from installer > * Look at its content in plugins/ and features/ and compare it with content of the TP site. > Everything that is in TP site but not in JBDS is probably worth being removed from TP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-2669: -------------------------------- Assignee: Nick Boldt (was: Denis Golovin) > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on JBDS-2734: ------------------------------------------ As far as I know, JBDS8 will still require JRE6 only ([~maxandersen] confirm?); however, if this is what the user is running on, then Forge and dependent plugins will not be activated. This does not affect the user's ability to create a JDK6 target platform for generated projects. It is only a Forge runtime requirement. > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Koen Aers > > Is Forge 2 ready to be included in JBDS ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2874?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2874: ----------------------------- CDW release: ? Status: New (was: New) Target Release: 8.0.0.GA > Support updating JBDS via BYOE (update site) w/o having to update product too > ----------------------------------------------------------------------------- > > Key: JBDS-2874 > URL: https://issues.jboss.org/browse/JBDS-2874 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png > > > I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. > Do we want this? I'll attach a PR showing how it's possible to make this happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2874?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2874: ----------------------------- Description: I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. Do we want this? was: I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. Do we want this? I'll attach a PR showing how it's possible to make this happen. > Support updating JBDS via BYOE (update site) w/o having to update product too > ----------------------------------------------------------------------------- > > Key: JBDS-2874 > URL: https://issues.jboss.org/browse/JBDS-2874 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png > > > I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. > Do we want this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2014