October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23178) cdk tools not reading / closing process streams correctly

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23178?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23178. --------------------------------- I never encountered this myself, so unfortunately I cannot really be 100 % sure that this is fixed. But sooner or later this would pop up. So I am closing this for now. > cdk tools not reading / closing process streams correctly > --------------------------------------------------------- > > Key: JBIDE-23178 > URL: https://issues.jboss.org/browse/JBIDE-23178 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > Calls to environment manager or vagrant status often fail with a timeout. Sometimes they can be worked around, so the user never sees the error. However the implementation is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4097) Support maven plugins used by Fuse Quickstarts

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4097?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4097: ---------------------------------- No, ignore is one case but you can ask the plugin to run during Eclipse project lifecycle. The only case you need an adapter is when you need to interact with the Eclipse project (add new source folder,...). > Support maven plugins used by Fuse Quickstarts > ---------------------------------------------- > > Key: JBDS-4097 > URL: https://issues.jboss.org/browse/JBDS-4097 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: LATER > > > known plugins: > - cxf-java2wadl-plugin > - cxf-java2ws-plugins > - fabric-cxf-plugins > The best is to implement m2e connector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23158) Update parent pom in main branch after codefreeze branching

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23158?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23158. --------------------------------- Closing, but not really verifying. Reopen if not working. > Update parent pom in main branch after codefreeze branching > ----------------------------------------------------------- > > Key: JBIDE-23158 > URL: https://issues.jboss.org/browse/JBIDE-23158 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a release when codefreezing and also update parent poms in those branches should also update parent pom in the main (master or maintenance) branch. > For example if we update pom in just created 4.4.1.x branch to 4.4.1.Final then we also need to update the parent pom in master to 4.4.2.AM1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22728. --------------------------------- Closing. > Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22728 > URL: https://issues.jboss.org/browse/JBIDE-22728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > Attachments: console.log.txt, getProjectRootPomParents.tsk.txt > > > Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. > With the advent of PR build jobs, we can now streamline this a little: > instead of creating Task JIRAs, create PRs & let them run automatically. > if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23159) Bump plugin/feature/component versions in main branch when creating branches for Final/GA release

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23159?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23159. --------------------------------- Closing, but not really verifying. Reopen if not working. > Bump plugin/feature/component versions in main branch when creating branches for Final/GA release > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23159 > URL: https://issues.jboss.org/browse/JBIDE-23159 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a Final/GA release when codefreezing should also bump plugin/feature/component versions in main branch (master or maintenance). > The script should probably have a parameter which tells what segment of the version we want to increment: X.Y.Z -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22598) Support runtime detection for manual CDK install

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22598?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22598: --------------------------------------- Radim just told me this works for him which was odd. And then he found out that this works when he searches deep enough, but not when he's too high up. Let me give you an example. Say you have this dir structure: /Users/rasp/git/cdk-install/07-Oct-2016/cdk/components/rhel/rhel-ose/ If you search this path (or anything even deeper), it will work: /Users/rasp/git/cdk-install/07-Oct-2016/cdk But if you search this path (or anything even higher up), it won't work: /Users/rasp/git/cdk-install/07-Oct-2016 > Support runtime detection for manual CDK install > ------------------------------------------------ > > Key: JBIDE-22598 > URL: https://issues.jboss.org/browse/JBIDE-22598 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, runtime-detection > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > Right now with CDK 2.1 when you have a manual cdk install (i.e. using cdk.zip and then adding the vagrant box yourself), there will be no .cdk marker, so Runtime Detection will not work. > The only case where Runtime Detection will work is when you use the (as of now Windows-only) suite installer. At that point Runtime Detection will do its thing silently without you noticing. > The way I see it there are two options: > a) Create and upstream issue with CDK and ask them to include a basic .cdk in their zip > b) Make the runtime detection work without .cdk -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4097) Support maven plugins used by Fuse Quickstarts

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4097?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4097: --------------------------------------- ok I read too fast. So what you are suggesting is to configure to ignore these plugins. I know that it is possible but this is not the perfect solution. That's what I said in description "the best is to implement the m2e connector", the implicit was to configure to ignore them bu tit means that the project won't work Out of the box, the user will have to launch a mvn clean install everytime he/she does modification > Support maven plugins used by Fuse Quickstarts > ---------------------------------------------- > > Key: JBDS-4097 > URL: https://issues.jboss.org/browse/JBDS-4097 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: LATER > > > known plugins: > - cxf-java2wadl-plugin > - cxf-java2ws-plugins > - fabric-cxf-plugins > The best is to implement m2e connector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4097) Support maven plugins used by Fuse Quickstarts

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4097?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4097: ---------------------------------- This has to be done in plugin codebase not user pom so I don't see why a separate adapter should be better > Support maven plugins used by Fuse Quickstarts > ---------------------------------------------- > > Key: JBDS-4097 > URL: https://issues.jboss.org/browse/JBDS-4097 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: LATER > > > known plugins: > - cxf-java2wadl-plugin > - cxf-java2ws-plugins > - fabric-cxf-plugins > The best is to implement m2e connector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23262) Issue warnings about snapshot deps for all AMx milestones (not just AM3)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23262?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23262. --------------------------------- This does work although I don't see that much value in a warning - there are usually a couple warnings anyway and people tend to ignore those. But in any case it works as expected. {code} [ERROR] Found property openshift-restclient-java.version = 5.2.0-SNAPSHOT [WARNING] Rule 0: org.jboss.tools.releng.NoSnapshotsAllowed failed with message: When buildAlias (AM2) matches /AM1|AM2|AM3/, cannot include SNAPSHOT dependencies. {code} Closing. > Issue warnings about snapshot deps for all AMx milestones (not just AM3) > ------------------------------------------------------------------------ > > Key: JBIDE-23262 > URL: https://issues.jboss.org/browse/JBIDE-23262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, parent > Fix For: 4.4.2.AM1 > > > The parent POM is configured to issue warnings when SNAPSHOT dependencies when build alias matches AM3 but it should match AM1, AM2 as well -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4097) Support maven plugins used by Fuse Quickstarts

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4097?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4097: --------------------------------------- One objective is to avoid to pollute pom.xml with IDE metadata information > Support maven plugins used by Fuse Quickstarts > ---------------------------------------------- > > Key: JBDS-4097 > URL: https://issues.jboss.org/browse/JBDS-4097 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: LATER > > > known plugins: > - cxf-java2wadl-plugin > - cxf-java2ws-plugins > - fabric-cxf-plugins > The best is to implement m2e connector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016