July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (LOCUS-46) refactor update site zip to new name for consistency with other JBoss artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-46?page=com.atlassian.jira.plugin.s... ] Nick Boldt edited comment on LOCUS-46 at 7/23/15 2:58 PM: ---------------------------------------------------------- For example here's a PR for *jbosstools-1.3.0-SNAPSHOT-updatesite-locus.zip*: https://github.com/jbosstools/jbosstools-locus/pull/48 was (Author: nickboldt): For example here's a PR: https://github.com/jbosstools/jbosstools-locus/pull/48 > refactor update site zip to new name for consistency with other JBoss artifacts > ------------------------------------------------------------------------------- > > Key: LOCUS-46 > URL: https://issues.jboss.org/browse/LOCUS-46 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.3.0 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 1.3.0 > > > There was a question raised about what to call the update site zip. > It's called *update.site-1.3.0-SNAPSHOT.zip* today [1]. > [1] https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... > If we want a different artifact name / classifier, I can easily do that. Got a preference? > We could do: > * update.site-1.3.0-SNAPSHOT.zip (no change) > * org.jboss.tools.locus-1.3.0-SNAPSHOT-update.site.zip > * jboss-tools-locus-1.3.0-SNAPSHOT-updatesite.zip (consistent w/ JBDS) > * jbosstools-1.3.0-SNAPSHOT-updatesite-locus.zip (consistent w/ JBT) > * ...? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17698?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17698: -------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta2) > 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.x > > > 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.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled XSD)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18316: -------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Errors in project after import WildFly quickstarts (bundled XSD) > ---------------------------------------------------------------- > > Key: JBIDE-18316 > URL: https://issues.jboss.org/browse/JBIDE-18316 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.CR1 > > > After importing all modules from https://github.com/wildfly/quickstart into JBDS 8.0.0.CR1b, a few projects have errors because of XML validation, such as: > {code} > Referenced file contains errors (jar:file:/Users/xcoulon/DevToolz/ide/jbossdevstudio800CR1b/studio/plugins/org.jboss.tools.as.catalog_3.0.0.CR1-v20140905-1648-B75.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-46) refactor update site zip to new name for consistency with other JBoss artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-46?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-46: ---------------------------- Fix Version/s: 1.3.0 > refactor update site zip to new name for consistency with other JBoss artifacts > ------------------------------------------------------------------------------- > > Key: LOCUS-46 > URL: https://issues.jboss.org/browse/LOCUS-46 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.3.0 > Reporter: Nick Boldt > Fix For: 1.3.0 > > > There was a question raised about what to call the update site zip. > It's called *update.site-1.3.0-SNAPSHOT.zip* today [1]. > [1] https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... > If we want a different artifact name / classifier, I can easily do that. Got a preference? > We could do: > * update.site-1.3.0-SNAPSHOT.zip (no change) > * org.jboss.tools.locus-1.3.0-SNAPSHOT-update.site.zip > * jboss-tools-locus-1.3.0-SNAPSHOT-updatesite.zip (consistent w/ JBDS) > * jbosstools-1.3.0-SNAPSHOT-updatesite-locus.zip (consistent w/ JBT) > * ...? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19738: -------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Failed runtime download offers no error message > ----------------------------------------------- > > Key: JBIDE-19738 > URL: https://issues.jboss.org/browse/JBIDE-19738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.CR1 > > > While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-46) refactor update site zip to new name for consistency with other JBoss artifacts

by Nick Boldt (JIRA)

Nick Boldt created LOCUS-46: ------------------------------- Summary: refactor update site zip to new name for consistency with other JBoss artifacts Key: LOCUS-46 URL: https://issues.jboss.org/browse/LOCUS-46 Project: JBoss Tools Locus Issue Type: Feature Request Affects Versions: 1.3.0 Reporter: Nick Boldt There was a question raised about what to call the update site zip. It's called *update.site-1.3.0-SNAPSHOT.zip* today [1]. [1] https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... If we want a different artifact name / classifier, I can easily do that. Got a preference? We could do: * update.site-1.3.0-SNAPSHOT.zip (no change) * org.jboss.tools.locus-1.3.0-SNAPSHOT-update.site.zip * jboss-tools-locus-1.3.0-SNAPSHOT-updatesite.zip (consistent w/ JBDS) * jbosstools-1.3.0-SNAPSHOT-updatesite-locus.zip (consistent w/ JBT) * ...? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19637) Runtime download hyperlink not working from New Server dialog on Mac

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19637: -------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Runtime download hyperlink not working from New Server dialog on Mac > -------------------------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-44) locus/site/pom.xml first lane is blank

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-44?page=com.atlassian.jira.plugin.s... ] Nick Boldt closed LOCUS-44. --------------------------- Assignee: Nick Boldt Fix Version/s: 1.3.0 Resolution: Done Done. https://github.com/jbosstools/jbosstools-locus/commit/ad267344850e457ce89... > locus/site/pom.xml first lane is blank > -------------------------------------- > > Key: LOCUS-44 > URL: https://issues.jboss.org/browse/LOCUS-44 > Project: JBoss Tools Locus > Issue Type: Bug > Affects Versions: 1.1.0 > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 1.3.0 > > > This blank lane the reason for exception below: > java.lang.Exception: Problem parsing archive:file:/!/home/eskimo/Projects/jbosstools-master3/git/jbosstools-locus/site/pom.xml > at org.eclipse.oomph.resources.impl.XMLProjectFactoryImpl.doCreateProject(XMLProjectFactoryImpl.java:101) > at org.eclipse.oomph.resources.impl.ProjectFactoryImpl.createProject(ProjectFactoryImpl.java:117) > at org.eclipse.oomph.resources.impl.SourceLocatorImpl.loadProject(SourceLocatorImpl.java:492) > at org.eclipse.oomph.resources.impl.SourceLocatorImpl.loadProject(SourceLocatorImpl.java:268) > at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:398) > at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:429) > at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:412) > at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:379) > at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:363) > at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.perform(MavenImportTaskImpl.java:326) > at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:2906) > at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.access$1(SetupTaskPerformer.java:2865) > at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:3950) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) > at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:3944) > at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.access$0(SetupTaskPerformer.java:3942) > at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:2856) > at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:2831) > at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:2762) > at org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:542) > at org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:627) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 6; The processing instruction target matching "[xX][mM][lL]" is not allowed. > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:348) > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) > at org.eclipse.oomph.util.XMLUtil.loadDocument(XMLUtil.java:50) > at org.eclipse.oomph.util.XMLUtil.loadRootElement(XMLUtil.java:65) > at org.eclipse.oomph.resources.impl.XMLProjectFactoryImpl.doCreateProject(XMLProjectFactoryImpl.java:86) > ... 21 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20347) D&D install is not working, when link is dropped on Central

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20347?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20347: --------------------------------------- D&D is ignored when adding it to a browser control. I have fixed the issue using HTML5 D&D. Both of the patches have to be applied. I have tested Chrome, Firefox on Linux as well as Chrome, Firefox and Internet Explorer on Windows. The patches also fix JBIDE-20348. > D&D install is not working, when link is dropped on Central > ----------------------------------------------------------- > > Key: JBIDE-20347 > URL: https://issues.jboss.org/browse/JBIDE-20347 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta2 > Reporter: Radim Hopp > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.0.CR1 > > > When dropping the install link (for example: http://download.jboss.org/jbosstools/central/install?connectors=org.tigri... ) to Central, the page content is replaced by: > Not Found > The requester URL /jbosstools/central/install was not found on this server > Apache Server at download.jboss.org Port 80 > It looks like central is trying to open that link as web page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-45) Do not deploy Locus artifacts to dl.jboss.org; only use nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-45?page=com.atlassian.jira.plugin.s... ] Nick Boldt reassigned LOCUS-45: ------------------------------- Assignee: Nick Boldt > Do not deploy Locus artifacts to dl.jboss.org; only use nexus > ------------------------------------------------------------- > > Key: LOCUS-45 > URL: https://issues.jboss.org/browse/LOCUS-45 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.3.0 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 1.3.0 > > > Nick said: > {quote} > We can now publish to Nexus as well as to dl.jb.org. I can disable the > publishing to dl.jb.org again if we no longer need that, and JUST use > the Nexus deployment. {quote} > Max said: > {quote} > I would disable all unnecessary publishing - it will just be forgotten > and someone someday will rely on the dl.jb.org bits when we wouldn't > want them to. Lets keep it as just one and locus for now is nexus bound. {quote} > So... I've updated the job again [0] to disable the deploy-to-jboss.org part. Not sure if I should also remove the profile entirely from the Locus site/pom.xml [1]. > [0] https://github.com/jbdevstudio/jbdevstudio-ci/commit/d29e92afdc5f93adfbf1... > [1] https://github.com/jbosstools/jbosstools-locus/blob/master/site/pom.xml#L... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 July 2015