[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3289:
-----------------------------------
[~lhein] : you'll have to add <proxyWizard ... category="earlyaccess"> to your Fuse proxy wizard
> 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)
9 years, 6 months
[JBoss JIRA] (JBTIS-236) Problem with BPMN when updated to newer version
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-236?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-236:
----------------------------------
Hey [~apodhrad] - is this Jira still an issue - could you check (and close this) if not??
Thanks!
--paull
> Problem with BPMN when updated to newer version
> -----------------------------------------------
>
> Key: JBTIS-236
> URL: https://issues.jboss.org/browse/JBTIS-236
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 7.0.0.GA-JBDSIS
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Priority: Minor
> Attachments: bpmn_editor.png, jbds.log
>
>
> Assume a user has JBDS-IS of version 7.0.0.Beta4 and then he wants to update his/her JBDS-IS to current version. But after updating there are issues with BPMN as follows
> 1. Creating new SwitchYard project causes the following error:
> Plug-in org.eclipse.bpmn2.modeler.runtime.example was unable to load class org.eclipse.bpmn2.modeler.runtime.example.SampleCustomTaskFeatureContainer
> (See the attachment for full log)
> 2. BPMN editor is without colors (see the attachment)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[JBoss JIRA] (JBTIS-101) Eclipse Juno dir path length bug breaks ESB examples
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-101?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-101.
----------------------------
Resolution: Out of Date
Given the root Eclipse Juno bug is fixed ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=327193) and that this hasn't shown up again - closing.
> Eclipse Juno dir path length bug breaks ESB examples
> ----------------------------------------------------
>
> Key: JBTIS-101
> URL: https://issues.jboss.org/browse/JBTIS-101
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: ESB
> Affects Versions: 4.0.0
> Environment: Eclipse Juno
> JBosstools - from trunk - http://svn.jboss.org/repos/jbosstools
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Priority: Blocker
>
> This eclipse Juno bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=327193
> Which shows up as:
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:188)
> at java.lang.ProcessImpl.start(ProcessImpl.java:132)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021)
> ... 10 more
> Note - The real issue is that the classpath is too long, not the dir path.
> The problem is preventing the ESB examples from running.
> To recreate the issue, open the eclipse/tools UI with a CLI command such as:
> cmd.exe /X /C ""C:\Program Files\Java\jdk1.7.0\jre\bin\java.exe" -Dosgi.noShutdown=false -Dosgi.os=win32 -Dosgi.ws=win32 -Dosgi.arch=x86_64 -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -Djbosstools.test.jbossesb.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jbossesb-4.11 -Djbosstools.test.jbosssoa.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jboss-soa-p-5/jboss-as -Dswtbot.test.properties.file=./org.jboss.tools.esb.ui.bot.test.properties -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -jar C:\Users\jbossqa\.m2\repository\p2\osgi\bundle\org.eclipse.equinox.launcher\1.3.0.v20120522-1813\org.eclipse.equinox.launcher-1.3.0.v20120522-1813.jar -data C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\data -dev file:/C:/Users/jbossqa/jbosstools/trunk/esb/tests/org.jboss.tools.esb.ui.bot.test/target/dev.properties -install C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work -configuration C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\configuration -application org.eclipse.ui.ide.workbench "
> Then import any of the ESB examples and attempt to run one of the clients (such as SendJMSMessage).
> Automated tests for this are here:
> Error #1 - http://machydra.brq.redhat.com:8080/job/esb.bot.tests.ldimaggi.matrixtest/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[JBoss JIRA] (JBIDE-19005) Create and use Mars M4 target-platform
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-19005:
--------------------------------------
Summary: Create and use Mars M4 target-platform
Key: JBIDE-19005
URL: https://issues.jboss.org/browse/JBIDE-19005
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Affects Versions: 4.3.0.Alpha1
Reporter: Mickael Istria
Mars M4 was released by the end of December. We should update our 4.50.0.Alpha1-SNAPSHOT TPs to use it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[JBoss JIRA] (JBIDE-18826) ClassNotFoundException for creating new Hybrid project
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18826?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18826:
----------------------------------------
Upstream bug in ECF has been fixed and the fix is available in Mars M4.
Updating TP to Mars M4 should automatically fix that.
> ClassNotFoundException for creating new Hybrid project
> ------------------------------------------------------
>
> Key: JBIDE-18826
> URL: https://issues.jboss.org/browse/JBIDE-18826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, target-platform, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> stack trace:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_0.1.0.201411202306
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 64 more
> {code}
> this is most likely a version range issue - http://snag.gy/6EHNd.jpg
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ]
Rafael Benevides commented on JBDS-3275:
----------------------------------------
I cropped the wildfly banner to 400px and worked as a temporary solution of WFLY-4190
> Add wildfly archetypes to JBoss Central
> ---------------------------------------
>
> Key: JBDS-3275
> URL: https://issues.jboss.org/browse/JBDS-3275
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 8.1.0.GA
>
>
> Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central.
> This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[JBoss JIRA] (JBIDE-19003) Promote JBoss Tools CAT in Dialog Similar to Usage
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19003?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19003:
----------------------------------------
Isn't it too much to have two dialogs (usage and CAT)? It might annoy users. What about rewrite the usage dialog and include CAT stuff there? So we will have one dialog which will ask the user to help us to improve quality by allowing us to gather usage data AND/OR participating in CAT.
WDYT?
> Promote JBoss Tools CAT in Dialog Similar to Usage
> --------------------------------------------------
>
> Key: JBIDE-19003
> URL: https://issues.jboss.org/browse/JBIDE-19003
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Affects Versions: 4.2.1.Final
> Reporter: Len DiMaggio
> Assignee: Xavier Coulon
> Fix For: 4.2.2.Final
>
>
> Can we add a "join JBT Cat?" dialog for new users? The dialog should appear only once so that we don't annoy the users. Thx!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months