September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20366) Easymport should offer available m2e connectors when importing Maven projects

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20366?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20366: --------------------------------------------- that is separate issue. Tycho is just mentioned as example. I'm +0 on including it, so I suggest open a separate issue and discuss it separately from the smartimport issue. That new issue would be good if we actually had a list of what m2e connectors we already do include (I lost count ;/) > Easymport should offer available m2e connectors when importing Maven projects > ----------------------------------------------------------------------------- > > Key: JBIDE-20366 > URL: https://issues.jboss.org/browse/JBIDE-20366 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > For example standard maven import offers tycho connector installation for a user. Easymport should provide the same user comfort as maven import does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20366) Easymport should offer available m2e connectors when importing Maven projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20366?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20366: ---------------------------------------- It makes sense for all projects, however, as the user-story here is about Tycho, I'm wondering by the way whether we should include m2e-tycho in JBT/JBDS. > Easymport should offer available m2e connectors when importing Maven projects > ----------------------------------------------------------------------------- > > Key: JBIDE-20366 > URL: https://issues.jboss.org/browse/JBIDE-20366 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > For example standard maven import offers tycho connector installation for a user. Easymport should provide the same user comfort as maven import does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20365) Review possibility before final import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20365?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20365: ---------------------------------------- Do you know some realistic user-stories to illustrate each one of your points, with example project and why each of this option seems necessary? About 1, it's going to be supported, but with some limitations. Indeed for some "strategies", the type of the parent may strongly impact how children are imported (for example, you don't want to import a folder that contains a .project if it's in the test data of an Eclipse test plugin), so there will be some limitation. However, the common case of a pure Maven project should work fine and make suggestions before running the import. About 2, I don't believe users really want that. What they want is something that "just" works without tweaking. Also, it's doing more that setting natures, and leaving the ability to user to override some detection is also giving them ability to do wrong things that would leave them in a very worse state. But I do agree that ability to change project natures is interesting, but I don't think it's something that should be necessarily done at import. IMO, it's just something the IDE should provide at anytime. This is the story of Eclipse bug https://bugs.eclipse.org/102527 ; I've implemented a simple way to tweak natures without editing .project: https://github.com/jbosstools/jbosstools-playground#naturist-edit-project... . I believe this approach of 1st import, then see projects in actions, and then tweak them if necessary better matches user workflow. About 3, that is planned and I'm working on it right now. However, it will probably have some limitations, similarly to 1. > Review possibility before final import > -------------------------------------- > > Key: JBIDE-20365 > URL: https://issues.jboss.org/browse/JBIDE-20365 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > Currently projects are just imported and user cannot decide if he wants to accept result or not. > There should be some some degree of flexibility: > 1) projects will not imported until user decides during import review page > 2) user should be able to change suggested nature of the imported projects during review for final import. > 3) users should be able to select/deselect desired projects -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20366) Easymport should offer available m2e connectors when importing Maven projects

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20366?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20366: --------------------------------------------- not following why this is suggested to be only relevant for Tycho extensions ? I assume you mean it make sense for other Maven projects too, right ? This is something the maven smart importer could do once the user have said Yes - I want to import these projects and then when that import has completed. > Easymport should offer available m2e connectors when importing Maven projects > ----------------------------------------------------------------------------- > > Key: JBIDE-20366 > URL: https://issues.jboss.org/browse/JBIDE-20366 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > For example standard maven import offers tycho connector installation for a user. Easymport should provide the same user comfort as maven import does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20380) The current implemetnation of JDF REST service may cause downloading incorrect content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20380?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20380: ---------------------------------------- Component/s: runtime-detection > The current implemetnation of JDF REST service may cause downloading incorrect content > -------------------------------------------------------------------------------------- > > Key: JBIDE-20380 > URL: https://issues.jboss.org/browse/JBIDE-20380 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: runtime-detection, server > Reporter: David Hladky > > The Eclipse wizard created by [~rob.stryker] uses https://www.jboss.org/download-manager/jdf rest service. > The problem is in the wizard the final step is identified by 302 response from the server, which is problematic, because not only the rest service itself can return 302, also other infrastructure can add its 302, such as an internet access in a hotel requesting payment for the connection. > There is no way where the 302 response is coming from and therefore we should use safer approach. > I described the problem in detail [here|https://mojo.redhat.com/docs/DOC-967368] - see the chapter Entry Point In Eclipse Plugin (REST) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20366) Easymport should offer available m2e connectors when importing Maven projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20366?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20366: ---------------------------------------- For this Tycho-specific use-case, the best thing, if we want to correctly support Tycho in JBT./JBDS, would be to include the m2e-tycho connectoir as a dependency. cc [~maxandersen] However, this is still a valid request for other items requiring Tycho extensions. > Easymport should offer available m2e connectors when importing Maven projects > ----------------------------------------------------------------------------- > > Key: JBIDE-20366 > URL: https://issues.jboss.org/browse/JBIDE-20366 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > For example standard maven import offers tycho connector installation for a user. Easymport should provide the same user comfort as maven import does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20459) Create automated test for WildFly 10

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20459?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20459. --------------------------------- Resolution: Done Tests were created. It's best to close this issue now and open new ones as new releases are made. > Create automated test for WildFly 10 > ------------------------------------ > > Key: JBIDE-20459 > URL: https://issues.jboss.org/browse/JBIDE-20459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.CR1 > > > Currently we don't have a dedicated server adapter for WildFly 10. WildFly 10 is still in development and is planned to be released at the same time as JBDS 9.0.0 - https://issues.jboss.org/browse/wfly/?selectedTab=com.atlassian.jira.jira... > We expect WildFly 9 adapter to work with WildFly 10 runtime. > Let's create an automated test for WF 10 runtime. We should update it after every WF runtime milestone release to make sure it works. > Then we switch to a new WF 10 adapter when it's ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20481) EAP 7 server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20481?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20481. --------------------------------- Resolution: Done pushed to master along with unit tests > EAP 7 server adapter > -------------------- > > Key: JBIDE-20481 > URL: https://issues.jboss.org/browse/JBIDE-20481 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.CR1 > > > It'd be a good idea to begin making an EAP7 / WF10 server adapter pair, or at least preparing. > Looking at the versions of jars that we care about for management commands, Jars in EAP7 current DR3 are: > wildfly-controller-client-2.0.0.Alpha3.jar > wildfly-protocol-2.0.0.Alpha3.jar > jboss-dmr-1.3.0.Final.jar > jboss-logging-3.2.1.Final.jar > jboss-marshalling-1.4.10.Final.jar > jboss-marshalling-river-1.4.10.Final.jar > jboss-marshalling-river-1.4.10.Final.jar > jboss-remoting-4.0.9.Final.jar > jboss-sasl-1.0.5.Final.jar > jboss-threads-2.2.0.Final.jar > xnio-api-3.3.1.Final.jar > xnio-nio-3.3.1.Final.jar > These jars are identical to those in WF9-CR1 *except* for wildfly-protocol and wildfly-controller-client, which are at 1.0.0.CR1 in wf9. So wildfly-core (repository) has undergone a 'major' version bump, and is likely undergoing significant API cleanup. It would be smart to expect that we probably will require a new management plugin on our side to compensate. > Also, it's worth noting that in WF8 / WF 8.1, these jars are actually versioned 8.0 / 8.1 respectively, and so the version has actually decreased as we've moved forward. I've brought this up on wildfly-dev, though it may be a bit late since WF is already ar RC3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-20442: ------------------------------------- Most probably I will not make it till code freeze > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.0.CR1 > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3511) Remove OpenShift 3 Tooling from JBDS installer/BYOE

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3511?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-3511: --------------------------------- Assignee: Nick Boldt > Remove OpenShift 3 Tooling from JBDS installer/BYOE > --------------------------------------------------- > > Key: JBDS-3511 > URL: https://issues.jboss.org/browse/JBDS-3511 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, marketplace > Affects Versions: 9.0.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.CR1 > > > For JBT 4.3 _and_ JBDS 9, OpenShift 3 will be available as TechPreview from JBoss Central. As a consequence, it needs to be removed from the JBDS installer, the BYOE marketplace installation and the default JBT update site -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 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 September 2015