January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19034) Bump org.jboss.tools.forge.m2e version

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19034?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19034. ------------------------------ Verified in JBT 4.2.2.Final build. > Bump org.jboss.tools.forge.m2e version > --------------------------------------- > > Key: JBIDE-19034 > URL: https://issues.jboss.org/browse/JBIDE-19034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.2.Final > > > org.jboss.tools.forge.m2e version needs to become 1.1.2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19044) Central in JBT only lists 3 of the 4 Mylyn-related packages

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19044?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19044: ---------------------------------------- Can you please details which version of Eclipse you used as base, which site do you use to install JBoss Tools, and what categories/IUs you've selected when installing? Did you click "Show installed" to check whether the connector is installed? Looking at https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.2.x/... , it seems like the plugin is actually in the catalog. So it could be either that at that time, it's not meant to be shown (if already installed), or some bug in UI filtering. I'll need a few more details (asked above) before I can try to give a diagnostic. > Central in JBT only lists 3 of the 4 Mylyn-related packages > ----------------------------------------------------------- > > Key: JBIDE-19044 > URL: https://issues.jboss.org/browse/JBIDE-19044 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.2.Final > Reporter: Len DiMaggio > Assignee: Mickael Istria > Fix For: 4.2.3.Final > > Attachments: JBDS.png, JBT.png > > > See the attached screenshots - 4 Mylyn-related packages are available in JBDS, only three in JBossTools (installing from > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18869: --------------------------------------------- If it is not treated like a part of TP why is it still referenced in the TP ? https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbo... > migrate Thym from TP to being an aggregated component > ----------------------------------------------------- > > Key: JBIDE-18869 > URL: https://issues.jboss.org/browse/JBIDE-18869 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, build, target-platform, updatesite > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP. > This would allow it to be incorporated into builds more easily and would avoid TP churn. > This should be fixed in master then backported for 4.2.2 (or 4.2.3). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19037) jbosstools-integration-tests.aggregate_master job is failing

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19037?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19037. ------------------------------- Fix Version/s: 4.3.0.Alpha1 Resolution: Duplicate Issue Verified > jbosstools-integration-tests.aggregate_master job is failing > ------------------------------------------------------------ > > Key: JBIDE-19037 > URL: https://issues.jboss.org/browse/JBIDE-19037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Vlado Pakan > Fix For: 4.3.0.Alpha1 > > > jbosstools-integration-tests.aggregate_master job is failing on jenkins > {noformat} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.central.ui.bot.test 4.3.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.central 2.0.0.Alpha1-v20150112-1751-B606 requires 'bundle org.jboss.tools.discovery.core 1.0.0' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.tools.central.ui.bot.test 4.3.0.qualifier depends on: bundle org.jboss.tools.central 1.1.0 > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.central 2.0.0.Alpha1-v20150112-1751-B606 to bundle org.jboss.tools.discovery.core 1.0.0.; Unable to satisfy dependency from org.jboss.tools.project.examples 3.0.0.Alpha1-v20150112-1751-B606 to bundle org.jboss.tools.discovery.core 1.0.0.; No solution found because the problem is unsatisfiable.] -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.central 2.0.0.Alpha1-v20150112-1751-B606 to bundle org.jboss.tools.discovery.core 1.0.0.; Unable to satisfy dependency from org.jboss.tools.project.examples 3.0.0.Alpha1-v20150112-1751-B606 to bundle org.jboss.tools.discovery.core 1.0.0.; No solution found because the problem is unsatisfiable.] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18862: ------------------------------------- When a server is stopped, we just publish, and add a .dodeploy marker, so everything's safe. When the server is running, there should never be a .dodeploy there that doesn't belong there, and I don't believe there ever is one. When you first start the server, publishes are done *before* the server starts. So if there was a .dodeploy there when the server was stopped that didn't belong there, and you then start the server, it publishes and adds a dodeploy and the .dodeploy actually does belong there. The only way you should end up with a .dodeploy that doesn't belong there is: 1) If a user added one via cmd line by himself 2) If two publish jobs are running at the same time in eclipse, which shouldn't happen 3) If a full publish finishes, adds a dodeploy, and an incremental publish occurs after. The .dodeploy belongs there and should not be removed during the incremental publish. As I mentioned above: To do this properly, I would need to verify the incremental publish is not pre-empting a full publish / .dodeploy marker, and then re-add the .dodeploy marker after the incremental publish... but this would complicate things quite a bit. Furthermore, if there was a stale .dodeploy there that wasn't supposed to be there, I'd probably assume I was pre-empting an actual full deployment, and re-add the marker when I wasn't supposed to. So basically, I cannot simply wipe all .dodeploy markers before a publish, because its possible an incremental deployment is running directly after a full publish (but before the server has started to pick up the deployment). Incremental deployments do not add new .dodeploy markers, so the effect is I'd end up deleting a valid .dodeploy when doing an incremental update, and then no .dodeploy would be added after it. If we simply wiped .dodeploy all the time before each publish, the following would be a bug: 1) A full publish happens, adding a .dodeploy 2) An incremental publish wipes the .dodeploy, so server never starts to deploy 3) The incremental publish changes a few files 4) The incremental publish does NOT add a new .dodeploy 5) The deployment is never picked up by the server. The only workaround for this would be to have incremental publish add .dodeploy markers also, which would effectively make all incremental publishes into full module restarts, which would be a significant performance problem and remove the benefit of incremental publish. Can you come up with a valid workflow where a .dodeploy is present when it doesn't belong there? As far as I can tell, there's no way for this to happen unless the user does it themselves, in which case we should not be wiping it. > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19016) UI Wizards should default Resource<?> UIInput types to support selecting a File OR Directory

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19016?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-19016: ----------------------------------- [~gastaldi] Did you also look at the Eclipse ResourceSelectionDialog? http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.... > UI Wizards should default Resource<?> UIInput types to support selecting a File OR Directory > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19016 > URL: https://issues.jboss.org/browse/JBIDE-19016 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.1.Final > Reporter: Lincoln Baxter III > Fix For: 4.3.x > > > There is currently no way to hint to the IDE to allow an input to select a file OR directory in Eclipse. I assume this will also be problematic in other IDEs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19016) UI Wizards should default Resource<?> UIInput types to support selecting a File OR Directory

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19016?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19016: ------------------------------ Fix Version/s: 4.3.x > UI Wizards should default Resource<?> UIInput types to support selecting a File OR Directory > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19016 > URL: https://issues.jboss.org/browse/JBIDE-19016 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.1.Final > Reporter: Lincoln Baxter III > Fix For: 4.3.x > > > There is currently no way to hint to the IDE to allow an input to select a file OR directory in Eclipse. I assume this will also be problematic in other IDEs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ] Radim Hopp closed JBDS-3289. ---------------------------- I overlooked that. Sorry. I just noticed the category="earlyaccess" one. Thanks for clarifying. Verified in JBDS 8.0.2. Closing. > JBoss Central proxy wizards need to recognize early access. > ----------------------------------------------------------- > > Key: JBDS-3289 > URL: https://issues.jboss.org/browse/JBDS-3289 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.2.GA > Reporter: Paul Leacu > Assignee: Fred Bricon > Priority: Blocker > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18581) jboss-kitchensink-backbone's graph profile defines repo which cannot be loaded

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18581?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18581: -------------------------------- Fix Version/s: 4.3.0.Alpha1 > jboss-kitchensink-backbone's graph profile defines repo which cannot be loaded > ------------------------------------------------------------------------------ > > Key: JBIDE-18581 > URL: https://issues.jboss.org/browse/JBIDE-18581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.2.0.CR2 > Reporter: Rastislav Wagner > Fix For: 4.3.0.Alpha1 > > > graph profile defines http://mvnplugins.fusesource.org/repo/releas which always timed out for me. Im unable to open in via browser either. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18581) jboss-kitchensink-backbone's graph profile defines repo which cannot be loaded

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18581?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18581: ------------------------------------- [~sgilda] : something for you? > jboss-kitchensink-backbone's graph profile defines repo which cannot be loaded > ------------------------------------------------------------------------------ > > Key: JBIDE-18581 > URL: https://issues.jboss.org/browse/JBIDE-18581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.2.0.CR2 > Reporter: Rastislav Wagner > Fix For: 4.3.0.Alpha1 > > > graph profile defines http://mvnplugins.fusesource.org/repo/releas which always timed out for me. Im unable to open in via browser either. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 2015