March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2348) JBDS product page on redhat.com is out of date

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2348?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2348. ---------------------------- Resolution: Done PDF finally updated. Closing. > JBDS product page on redhat.com is out of date > ---------------------------------------------- > > Key: JBDS-2348 > URL: https://issues.jboss.org/browse/JBDS-2348 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, documentation > Affects Versions: 5.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > Attachments: JBDS-PE-datasheet.pdf > > > This page [1] mentions Eclipse 3.6 and JBoss Tools 3, but JBDS 6 uses Eclipse 4.2 and JBoss Tools 4. > [1] https://www.redhat.com/apps/store/developers/jboss_developer_studio.html > Can we get that page updated? -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13094) errai cdi stock demo - bad url of the application

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13094?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13094: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> made a comment on [bug 877117|https://bugzilla.redhat.com/show_bug.cgi?id=877117] Modified the Doc text from known issue to bug fix. > errai cdi stock demo - bad url of the application > ------------------------------------------------- > > Key: JBIDE-13094 > URL: https://issues.jboss.org/browse/JBIDE-13094 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 3.3.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: gwt > Fix For: 4.1.0.Alpha2 > > > Description of problem: > After compiling the errai-cdi-demo-stock in the JBDS as Google -> GWT compile and deploying the application to the server (Run As -> Run on server), the url which embedded JBDS browser automatically opens after the deploying is "http://localhost:8080/errai-cdi-demo-stock/" which is not the entry point of the application - url "http://localhost:8080/cdi-quickstart-app/App.html" is. > Steps to Reproduce: > 1. Import project > 2. Google -> GWT compile > 3. Run as -> Run on server > 4. Embedded JBDS browser opens wrong URL address so user is unable to see the application - he sees error message instead. > Actual results: > Embedded browser opens the url http://localhost:8080/errai-cdi-demo-stock/ automatically. > Expected results: > Embedded browser opens the url http://localhost:8080/cdi-quickstart-app/App.html automatically. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13746) BrowserSim: make standalone available for download/launch

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13746?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-13746 at 3/27/13 10:37 AM: ------------------------------------------------------------------ [~yradtsevich] [~kmarmaliykov]: Submitted PR https://github.com/jbosstools/jbosstools-vpe/pull/49 which attach the artifact to the build. Can you please review and merge it? Once this is applied, one can reference the standalone jar artifact by {code} <groupId>org.jboss.tools.browsersim</groupId> <artifactId>org.jboss.tools.browsersim-standalone</artifactId> <version>3.5.0-SNAPSHOT</version> <type>jar</type> <classifier>standalone</classifier> {code} The best ways to retrieve this artifact locally is to use the [dependency-get|http://maven.apache.org/plugins/maven-dependency-plugin/ge...] mojo from command-line: {code} mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:get -Dartifact=org.jboss.tools.browsersim:-Org.jboss.tools.browsersim-standalone:3.5.0-SNAPSHOT:jar:-Standalone {code} or, via Nexus UI: https://repository.jboss.org/nexus/index.html#nexus-search;quick~browsers... which allows you to download stuff easily. was (Author: mickael_istria): [~yradtsevich] [~kmarmaliykov]: Submitted PR https://github.com/jbosstools/jbosstools-vpe/pull/49 which attach the artifact to the build. Can you please review and merge it? Once this is applied, one can reference the standalone jar artifact by {code} <groupId>org.jboss.tools.browsersim</groupId> <artifactId>org.jboss.tools.browsersim-standalone</artifactId> <version>3.5.0-SNAPSHOT</version> <type>jar</type> <classifier>standalone</classifier> {code} > BrowserSim: make standalone available for download/launch > --------------------------------------------------------- > > Key: JBIDE-13746 > URL: https://issues.jboss.org/browse/JBIDE-13746 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, Visual Page Editor core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.x > > > We want to make browersim easily available. > To do that we need: > A) buildable from our target platform > B) built in jenkins > C) put on nexus -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13876) Decide what to do with the Maven Facet

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13876?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-13876 at 3/27/13 10:17 AM: --------------------------------------------------------------- Currently the JBoss Maven Facet is installed explicitely in all our m2e configurators. I believe it'd be more appropriate to install that facet automatically in a FacetListener, once the Java or EAR Facet is installed and the project has the Maven nature. was (Author: fbricon): Currently the JBoss Maven Facet is install explicitely in all our m2e configurators. I believe it'd be more appropriate to install that facet automatically in a FacetListener, once the Java or EAR Facet is installed and the project has the Maven nature. > Decide what to do with the Maven Facet > -------------------------------------- > > Key: JBIDE-13876 > URL: https://issues.jboss.org/browse/JBIDE-13876 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.x > > > The JBoss Maven Facet has been used to : > - convert projects to Maven > - add new dependencies to an existing Maven project (by acting as a Library provider) > The conversion part has been superceded (mostly) by m2e's conversion API. > The way the Maven facet acts (not on its own but in support of other Facets, Seam most notably) is pretty ugly (storing Facets models in a MavenPostInstallListener), potentially leading to memory leaks. > The project conversion bit needs to be revisited, see how m2e's conversion API could be leveraged. > All in all, I'm convinced the whole Maven Facet programming model need a facelift. This issue is opened to discuss what we need to do and how to implement that. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13876) Decide what to do with the Maven Facet

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13876?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13876: ------------------------------------- Currently the JBoss Maven Facet is install explicitely in all our m2e configurators. I believe it'd be more appropriate to install that facet automatically in a FacetListener, once the Java or EAR Facet is installed and the project has the Maven nature. > Decide what to do with the Maven Facet > -------------------------------------- > > Key: JBIDE-13876 > URL: https://issues.jboss.org/browse/JBIDE-13876 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.x > > > The JBoss Maven Facet has been used to : > - convert projects to Maven > - add new dependencies to an existing Maven project (by acting as a Library provider) > The conversion part has been superceded (mostly) by m2e's conversion API. > The way the Maven facet acts (not on its own but in support of other Facets, Seam most notably) is pretty ugly (storing Facets models in a MavenPostInstallListener), potentially leading to memory leaks. > The project conversion bit needs to be revisited, see how m2e's conversion API could be leveraged. > All in all, I'm convinced the whole Maven Facet programming model need a facelift. This issue is opened to discuss what we need to do and how to implement that. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13876) Decide what to do with the Maven Facet

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-13876: ----------------------------------- Summary: Decide what to do with the Maven Facet Key: JBIDE-13876 URL: https://issues.jboss.org/browse/JBIDE-13876 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: maven Affects Versions: 4.1.0.Alpha1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.1.x The JBoss Maven Facet has been used to : - convert projects to Maven - add new dependencies to an existing Maven project (by acting as a Library provider) The conversion part has been superceded (mostly) by m2e's conversion API. The way the Maven facet acts (not on its own but in support of other Facets, Seam most notably) is pretty ugly (storing Facets models in a MavenPostInstallListener), potentially leading to memory leaks. The project conversion bit needs to be revisited, see how m2e's conversion API could be leveraged. All in all, I'm convinced the whole Maven Facet programming model need a facelift. This issue is opened to discuss what we need to do and how to implement that. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13746) BrowserSim: make standalone available for download/launch

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13746?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13746: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-vpe/pull/48, https://github.com/jbosstools/jbosstools-vpe/pull/49 (was: https://github.com/jbosstools/jbosstools-vpe/pull/48) [~yradtsevich] [~kmarmaliykov]: Submitted PR https://github.com/jbosstools/jbosstools-vpe/pull/49 which attach the artifact to the build. Can you please review and merge it? Once this is applied, one can reference the standalone jar artifact by {code} <groupId>org.jboss.tools.browsersim</groupId> <artifactId>org.jboss.tools.browsersim-standalone</artifactId> <version>3.5.0-SNAPSHOT</version> <type>jar</type> <classifier>standalone</classifier> {code} > BrowserSim: make standalone available for download/launch > --------------------------------------------------------- > > Key: JBIDE-13746 > URL: https://issues.jboss.org/browse/JBIDE-13746 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, Visual Page Editor core > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.1.x > > > We want to make browersim easily available. > To do that we need: > A) buildable from our target platform > B) built in jenkins > C) put on nexus -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13746) BrowserSim: make standalone available for download/launch

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13746?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-13746: -------------------------------------- Assignee: Konstantin Marmalyukov (was: Mickael Istria) > BrowserSim: make standalone available for download/launch > --------------------------------------------------------- > > Key: JBIDE-13746 > URL: https://issues.jboss.org/browse/JBIDE-13746 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, Visual Page Editor core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.x > > > We want to make browersim easily available. > To do that we need: > A) buildable from our target platform > B) built in jenkins > C) put on nexus -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-2505: ------------------------------------- Thanks, Mickael, build 359 seems to have the correct Eclipse platform. Although it's tricky because feature org.eclipse.platform is version 4.2.1. So there is no easy way to check what's correct, other than comparing with an Eclipse Juno SR2 installation from Eclipse.org. > JBDS 6.0.1 is based on Juno SR0 instead of SR2 > ---------------------------------------------- > > Key: JBDS-2505 > URL: https://issues.jboss.org/browse/JBDS-2505 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 6.0.1.GA > > > JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2. > I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0. > My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here. > Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-10267) JBoss AS7 mgmt API integration tests should be run on hudson

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10267?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-10267: ------------------------------------- This has been pushed to master. I will be watching closely to see if there are any problems. > JBoss AS7 mgmt API integration tests should be run on hudson > ------------------------------------------------------------ > > Key: JBIDE-10267 > URL: https://issues.jboss.org/browse/JBIDE-10267 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Affects Versions: 3.3.0.M4 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > We currently have as7 integration tests (AS7IntegrationTestSuite), but these tests are not run on jenkins since the test does not start the server, it's expecting a running server. > see the pom.xml: > {code} > <excludes> > <exclude>**/*IntegrationTest*.class</exclude> > </excludes> > {code} -- 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

13 years

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 March 2013