[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17180:
-----------------------------------
Labels: respin-a (was: )
> Disable custom deployment settings for remote servers without management port exposed
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17180
> URL: https://issues.jboss.org/browse/JBIDE-17180
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
> Attachments: JBIDE-17180v2.png, wide-window.png
>
>
> JBIDE-13445 added the possibility to use custom deploy dir on remote server.
> {quote}
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
> {quote}
> We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-18833 at 12/1/14 12:28 PM:
--------------------------------------------------------------
Jobs were disabled to avoid churn, save cycles, and because that's generally the process (for the maintenance branch) to avoid having things autobuild when I'm not expecting it. :)
I have re-enabled the jobs. Base and Server show new commits since CR1 (for respin-a on Dec 7). I haven't seen any other fresh commits yet.
was (Author: nickboldt):
Jobs were disabled to avoid churn, save cycles, and because that's generally the process (for the maintenance branch) to avoid having things autobuild when I'm not expecting it. :)
I will re-enable the jobs if you plan to test nightlies; I was under the impression QE only looked at staged builds, not nightlies.
> luna nightly are not being updated preventing QE to do easy testing of committed code
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18833
> URL: https://issues.jboss.org/browse/JBIDE-18833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.2.1.Final
>
>
> http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago)
> I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 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 edited comment on JBIDE-18826 at 12/1/14 12:07 PM:
------------------------------------------------------------------
Ok, so it seems to be an upstream issue in Equinox then, not a bug in our TP picking the wrong bundles ?
was (Author: mickael_istria):
Ok, so it seems to be an upstream issue in Equinox then ?
> 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.8#6338)
11 years, 4 months