June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18899) symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18899?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-18899: ------------------------------------------- Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18899 > URL: https://issues.jboss.org/browse/JBIDE-18899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.2.x > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ says last folder published is B14 but http://download.jboss.org/jbosstools/updates/nightly/luna/compositeArtifa... contains the following: > {{{ > <?compositeArtifactRepository version='1.0.0'?><repository name="JBoss Tools Builds - builds/nightly/core/4.2.luna" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"><properties size="2"><property name="p2.timestamp" value="1417970049000"/><property name="p2.compressed" value="true"/></properties><children size="9"> > <child location="2014-12-06_19-43-15-B315/all/repo/"/> > <child location="2014-12-06_01-42-39-B314/all/repo/"/> > <child location="2014-12-05_16-52-33-B313/all/repo/"/><child location="2014-12-05_13-48-06-B312/all/repo/"/><child location="2014-12-04_19-55-14-B311/all/repo/"/><child location="2014-12-04_14-48-07-B310/all/repo/"/><child location="2014-12-03_17-44-02-B309/all/repo/"/><child location="2014-12-02_13-44-05-B308/all/repo/"/><child location="2014-12-01_16-57-02-B307/all/repo/"/></children></repository> > }}} > Indicating that http://download.jboss.org/jbosstools/updates/nightly/luna/2014-12-06_19-4... should exist - but it does not. > I assume this is due to a nightly being used for publishing results to staging - thus it might just be cleanup step that is missing ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-18820: ------------------------------------------- Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, devdoc > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Labels: devdoc > Fix For: 4.3.x > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2337) Lack of positive/negative feedback to user when running queries in Mylyn

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2337?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-2337: -------------------------------- > Lack of positive/negative feedback to user when running queries in Mylyn > ------------------------------------------------------------------------ > > Key: JBDS-2337 > URL: https://issues.jboss.org/browse/JBDS-2337 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: upstream > Affects Versions: 6.0.0.Alpha2 > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20120924-2110-B28 > Build date: 20120924-2110 > Reporter: Len DiMaggio > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 6.0.x > > Attachments: JBDS-2337_better_JIRA_feedback.png, JBDS-2337_Screenshot-1.png, JBDS-2337_Screenshot-2.png, JBDS-2337_Screenshot-3.png, JBDS-2337_Screenshot-4.png, JBDS-2337_Screenshot-5.png > > > See sequence of screenshots attached. If a user executes a bugzilla querysuccessfully, no feedback that the query was successful is displayed. The user must access the tasks view to see the query results - also - if the query fails and returns no records, no feedback is displayed, the user must access the task view to see the (empty) query results. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2337) Lack of positive/negative feedback to user when running queries in Mylyn

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2337?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-2337: ----------------------------------------- Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > Lack of positive/negative feedback to user when running queries in Mylyn > ------------------------------------------------------------------------ > > Key: JBDS-2337 > URL: https://issues.jboss.org/browse/JBDS-2337 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: upstream > Affects Versions: 6.0.0.Alpha2 > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20120924-2110-B28 > Build date: 20120924-2110 > Reporter: Len DiMaggio > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 6.0.x > > Attachments: JBDS-2337_better_JIRA_feedback.png, JBDS-2337_Screenshot-1.png, JBDS-2337_Screenshot-2.png, JBDS-2337_Screenshot-3.png, JBDS-2337_Screenshot-4.png, JBDS-2337_Screenshot-5.png > > > See sequence of screenshots attached. If a user executes a bugzilla querysuccessfully, no feedback that the query was successful is displayed. The user must access the tasks view to see the query results - also - if the query fails and returns no records, no feedback is displayed, the user must access the task view to see the (empty) query results. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3434: ----------------------------------------- Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > Kubernetes editor & wizard > -------------------------- > > Key: JBDS-3434 > URL: https://issues.jboss.org/browse/JBDS-3434 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.x > Reporter: Charles Moulliard > Assignee: Alexey Kazakov > Fix For: 10.x > > > To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose : > - a kubernetes editor within JBDS to update the YAML or JSON file and > - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11338) JBoss AS 7.0.2 do not start when Java Agent is run and throws log error with JVM 6 update 15 and above

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11338?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-11338: ------------------------------------------- Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > JBoss AS 7.0.2 do not start when Java Agent is run and throws log error with JVM 6 update 15 and above > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-11338 > URL: https://issues.jboss.org/browse/JBIDE-11338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: profiler > Affects Versions: LATER > Reporter: Ramesh Pa > Assignee: Alexey Kazakov > Priority: Blocker > Labels: JBoss > Fix For: LATER > > > Workaround as below is also not working. > set JAVA_OPTS= %JAVA_OPTS% -Xbootclasspath/p:C:\jboss-6.1.0.Final\lib\jboss-logmanager.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger .pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl > No issues with JVM 6 update 14 and earlier. > Error message > INFO: 801. Dummy Java Agent:: Transformer to Transform Class: java/lang/ExceptionInInitializerError > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.jboss.as.server.Main.main(Main.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.modules.Module.run(Module.java:272) > at org.jboss.modules.Main.main(Main.java:313) > Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system proper > ty to "org.jboss.logmanager.LogManager") > at org.jboss.logmanager.Logger.getLogger(Logger.java:60) > at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) > ... 7 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9356) NLS.bind vs MessageFormat.format

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9356?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen reassigned JBIDE-9356: ------------------------------------------ Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > NLS.bind vs MessageFormat.format > -------------------------------- > > Key: JBIDE-9356 > URL: https://issues.jboss.org/browse/JBIDE-9356 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cleanup > Affects Versions: 3.3.0.M3 > Reporter: Rob Stryker > Assignee: Alexey Kazakov > Fix For: 4.0.x > > > A substantial number of classes use NLS.bind(Messages.SomeString, name) to bind message strings. Another subset of the classes use MessageFormat.format(etc). > I believe NLS.bind() is the correct solution which works properly with eclipse osgi and all that jazz. Should this be standardized? Is it confusing to be using two interchangable APIs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6343?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen reassigned JBIDE-6343: ------------------------------------------ Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > Create a "sanity check plugin/feature" tool for running on integration builds > ----------------------------------------------------------------------------- > > Key: JBIDE-6343 > URL: https://issues.jboss.org/browse/JBIDE-6343 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Minor > Fix For: LATER > > > I keep seeing the following antipatterns or oversights happening in our codebase, most of them I believe we could mechanically check for. > No duplicate names in .project since it makes it impossible to import into Eclipse > bin folders should be svn:ignored and not be committed (causes problems when doing svn synchronization and all the .class files are showing up and some even commits it) > things in svn:ignore should be committed (either someone overrode svn:ignore or the svn:ignore were added later) > if pom.xml file exists target should be svn:ignored too. > Execution environment should be specified in manifest.mf's -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11970) include runtime jars into java search transparently

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11970?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-11970: ------------------------------------------- Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > include runtime jars into java search transparently > --------------------------------------------------- > > Key: JBIDE-11970 > URL: https://issues.jboss.org/browse/JBIDE-11970 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Minor > Fix For: LATER > > > I just realized PDE has a way to add source from all plugins into java search - this would be super useful for runtime jars which is not on the classpath. > http://www.vogella.com/articles/EclipseCodeAccess/article.html#search_inc... > We should investigate how that is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18902) Add Ceylon IDE to JBoss Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18902?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-18902: ------------------------------------------- Assignee: Alexey Kazakov (was: Max Rydahl Andersen) Bulk moving any issue assigned to me directly to Alexey for his new role. > Add Ceylon IDE to JBoss Central > ------------------------------- > > Key: JBIDE-18902 > URL: https://issues.jboss.org/browse/JBIDE-18902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Final > Reporter: Fred Bricon > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > It's probably time to consider adding Ceylon IDE to JBoss Central, provided it doesn't break anything. > Questions are : > - Early Access or not? > - should JBDS get it? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016