June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17714) Cyclic dependency between Project Examples and Maven Project Examples

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-17714: ----------------------------------- Summary: Cyclic dependency between Project Examples and Maven Project Examples Key: JBIDE-17714 URL: https://issues.jboss.org/browse/JBIDE-17714 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, project-examples Affects Versions: 3.2.0.Final Reporter: Fred Bricon While working on JBIDE-17713, I noticed the Project Example tests failed because they require the Maven Project Examples to be built. But Maven Project Examples depends on Project Examples in the first place. This creates a Cyclic dependency between the Maven and Examples components. Solution is to move the Maven Project Examples to the Project Examples component -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17713) ProjectExample definition content mutates every time an example is created

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17713?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-17713: ----------------------------------- Assignee: Fred Bricon > ProjectExample definition content mutates every time an example is created > -------------------------------------------------------------------------- > > Key: JBIDE-17713 > URL: https://issues.jboss.org/browse/JBIDE-17713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 3.2.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.0.Beta3 > > > Each ProjectExample instance, loaded from project example descriptors is mutated several times when actual exampled are created, such as https://github.com/jbosstools/jbosstools-central/blob/94cccaa18c185657c5c.... > This prevents us from mixing for instance maven projects with non maven projects > The example definition and the actual example set per the user choices should be split, using the concept of a working copy (similar to what is done for launchconfigurations or runtimes) > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17713) ProjectExample definition content mutates every time an example is created

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17713?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17713: -------------------------------- Fix Version/s: 4.2.0.Beta3 > ProjectExample definition content mutates every time an example is created > -------------------------------------------------------------------------- > > Key: JBIDE-17713 > URL: https://issues.jboss.org/browse/JBIDE-17713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 3.2.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.0.Beta3 > > > Each ProjectExample instance, loaded from project example descriptors is mutated several times when actual exampled are created, such as https://github.com/jbosstools/jbosstools-central/blob/94cccaa18c185657c5c.... > This prevents us from mixing for instance maven projects with non maven projects > The example definition and the actual example set per the user choices should be split, using the concept of a working copy (similar to what is done for launchconfigurations or runtimes) > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17464) Contacts mobile project example is not asking to use RedHat techrpeview maven repo

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17464?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-17464 at 6/30/14 5:08 AM: -------------------------------------------------------------- I can see 3 approaches : * add required_maven_dependencies fix : missing repo would appear in list of requirements instead of current behavior => UI inconsistency. Would also require special handling to load fixes from other plugins than org.jboss.tools.project.examples, to avoid dragging m2e dependencies in examples core. Meh * new import type "maven+zip" : explicitly declares the example is *hybrid*, handles import in 2 steps. That means the day we add gradle support, we'll need gradle+zip. Meh. * augment import type maven to import non-maven eclipse projects as well when listed in <includedProject>. Problem is ProjectExample definitions are mutated when they shouldn't (see https://github.com/jbosstools/jbosstools-central/blob/master/maven%2Fplug... for instance). A proper solution requires to split ProjectExample in a definition class and a working copy class. But that requires some non-trivial refactoring as I expressed before (see JBIDE-17713 ). Other ideas? was (Author: fbricon): I can see 3 approaches : * add required_maven_dependencies fix : missing repo would appear in list of requirements instead of current behavior => UI inconsistency. Would also require special handling to load fixes from other plugins than org.jboss.tools.project.examples, to avoid dragging m2e dependencies in examples core. Meh * new import type "maven+zip" : explicitly declares the example is *hybrid*, handles import in 2 steps. That means the day we add gradle support, we'll need gradle+zip. Meh. * augment import type maven to import non-maven eclipse projects as well when listed in <includedProject>. Problem is ProjectExample definitions are mutated when they shouldn't (see https://github.com/jbosstools/jbosstools-central/blob/master/maven%2Fplug... for instance). A proper solution requires to split ProjectExample in a definition class and a working copy class. But that requires some non-trivial refactoring as I expressed before. Other ideas? > Contacts mobile project example is not asking to use RedHat techrpeview maven repo > ---------------------------------------------------------------------------------- > > Key: JBIDE-17464 > URL: https://issues.jboss.org/browse/JBIDE-17464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104 > Reporter: Vlado Pakan > Assignee: Fred Bricon > Fix For: 4.2.0.Beta3 > > > 1. Import Mobile Applications > contacts-mobile-basic from JBoss Central without defined RedHat Tech preview All maven repo > ERROR: Maven dependencies are not resolved for contacts-mobile-basic-services project and therefore project has many errors. User should be informed that he needs to define and use RedHat Tech preview All maven repo otherwise he will be unable to run this example -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17713) ProjectExample definition content mutates every time an example is created

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-17713: ----------------------------------- Summary: ProjectExample definition content mutates every time an example is created Key: JBIDE-17713 URL: https://issues.jboss.org/browse/JBIDE-17713 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2.0.Final Reporter: Fred Bricon Each ProjectExample instance, loaded from project example descriptors is mutated several times when actual exampled are created, such as https://github.com/jbosstools/jbosstools-central/blob/94cccaa18c185657c5c.... This prevents us from mixing for instance maven projects with non maven projects The example definition and the actual example set per the user choices should be split, using the concept of a working copy (similar to what is done for launchconfigurations or runtimes) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17712) BeanParam: matrix parameter is not recognized

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17712?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-17712: ------------------------------------ Assignee: Xavier Coulon > BeanParam: matrix parameter is not recognized > --------------------------------------------- > > Key: JBIDE-17712 > URL: https://issues.jboss.org/browse/JBIDE-17712 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17712) BeanParam: matrix parameter is not recognized

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-17712: --------------------------------------- Summary: BeanParam: matrix parameter is not recognized Key: JBIDE-17712 URL: https://issues.jboss.org/browse/JBIDE-17712 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Beta3 Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555 Reporter: Radoslav Rábara Fix For: 4.2.0.Beta3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17711) BeanParam: type of path parameter is not recognized

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17711?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-17711: ------------------------------------ Assignee: Xavier Coulon > BeanParam: type of path parameter is not recognized > --------------------------------------------------- > > Key: JBIDE-17711 > URL: https://issues.jboss.org/browse/JBIDE-17711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17711) BeanParam: type of path parameter is not recognized

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-17711: --------------------------------------- Summary: BeanParam: type of path parameter is not recognized Key: JBIDE-17711 URL: https://issues.jboss.org/browse/JBIDE-17711 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Beta3 Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555 Reporter: Radoslav Rábara Fix For: 4.2.0.Beta3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17698) Server view could show all deployed modules, obtained from the server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17698?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17698: --------------------------------------- I agree that this may be tricky to get right. Also, we should get others opinion (Max) if they think this would be worth pursuing. Also, we could limit this to AS7 / EAP6 / WF8 which shouldn't have the problem of showing all of the services. > Server view could show all deployed modules, obtained from the server > --------------------------------------------------------------------- > > Key: JBIDE-17698 > URL: https://issues.jboss.org/browse/JBIDE-17698 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha1 > > > Pavol Srna pointed out to me that when he deletes a project in workspace while it's deployed on a running AS7, it disappears from the server view and he can't undeploy it from Eclipse. > I understand that this is somewhat expected, but we have a suggestion: Could the server view get its deployed modules from the server via the management api and use that to show the modules? Similar to what the web console of AS7/WildFly/EAP6 shows. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 June 2014