April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19741) jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19741?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19741: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this? > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19741 > URL: https://issues.jboss.org/browse/JBIDE-19741 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi, jsp/jsf/xml/html source editing, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > Attachments: jars.in.javaee.list.of.dupes.with.counts.txt, jars.in.javaee.txt > > > There are 141M of binaries in the jbosstools-javaee source tree. > See attached files for details. Would it be possible to pull these jars from Maven instead of having as many as *19* copies of the same jar in the source repo? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19741) jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19741?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19741: -------------------------------------- Assignee: Alexey Kazakov > jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this? > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19741 > URL: https://issues.jboss.org/browse/JBIDE-19741 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi, jsp/jsf/xml/html source editing, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Attachments: jars.in.javaee.list.of.dupes.with.counts.txt, jars.in.javaee.txt > > > There are 141M of binaries in the jbosstools-javaee source tree. > See attached files for details. Would it be possible to pull these jars from Maven instead of having as many as *19* copies of the same jar in the source repo? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Rafael Benevides commented on JBIDE-19571: ------------------------------------------ PR merged > Add FSW to downloadable runtimes > -------------------------------- > > Key: JBIDE-19571 > URL: https://issues.jboss.org/browse/JBIDE-19571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3432) create verification test - JBDS update site(s) and installer should not contain <references> to external URLs

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3432: -------------------------------- Summary: create verification test - JBDS update site(s) and installer should not contain <references> to external URLs Key: JBDS-3432 URL: https://issues.jboss.org/browse/JBDS-3432 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: build, installer, updatesite Affects Versions: 9.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt We ought to have some sort of maven-based verification test that can unpack the update site zip and installer, and verify that the p2 metadata doesn't reference any unexpected 3rd party URLs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3408: ----------------------------- Attachment: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt Steps to (not be able to) reproduce: 1. Download jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar 2. Disable network (verified by trying to ping google.com, eclipse.org, cnn.com): {code} $➔ ping google.com ping: unknown host google.com [12:57:52] nboldt@t540p-fc20-vm01:~/tmp $➔ ping cnn.com ping: unknown host cnn.com [12:57:59] nboldt@t540p-fc20-vm01:~/tmp $➔ ping eclipse.org ping: unknown host eclipse.org {code} 2. Install: {code}java -jar -DTRACE=true jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar | tee JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt{code} 3. resulting log showing successful install & no references to the outside world: [^JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt] 4. Note: On startup of JBDS, the new Central page showed an error (because Fred's new remotely hosted Central page could not be loaded) which further verifies installation works offline. > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-19342 at 4/30/15 12:36 PM: ----------------------------------------------------------------- Building IAdapter hierarchy is not working for me, it fails with error explained here [451352|https://bugs.eclipse.org/bugs/show_bug.cgi?id=451352]. was (Author: dgolovin): Building IAdapter hierarchy is not working for me fails with error explained here [451352|https://bugs.eclipse.org/bugs/show_bug.cgi?id=451352]. > Update code to cope with generics added to org.eclipse.core.runtime package API > -------------------------------------------------------------------------------- > > Key: JBIDE-19342 > URL: https://issues.jboss.org/browse/JBIDE-19342 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, cdi, cdi-extensions, central, common/jst/core, cordovasim, forge, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API. > From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html : > {quote} > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021 > Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25 > Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common: > 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)" > 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented. > 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All) > 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature. > Typical change: > Old: > {code} > public Object getAdapter(Class adapter) { > if (ICompilationUnit.class.equals(adapter)) > return getCompilationUnit(); > return null; > } > {code} > New: > {code} > public <T> T getAdapter(Class<T> adapter) { > if (ICompilationUnit.class.equals(adapter)) > return adapter.cast(getCompilationUnit()); > return null; > } > {code} > 5. Update implementations of IAdapterFactory > Hint for 4. & 5.: > - Open Type Hierarchy on IAdaptable, etc. > - In the view menu, select a working set that contains your projects > - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3345: ----------------------------------- > So if java -version shows JDK 7 then the server starts correctly JDK 8 then you will encounter problem which I reported I am not able to replicate this at all. my Path: [rob@localhost eclipse]$ echo $PATH /usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/rob/.rvm/bin:/home/rob/.local/bin:/home/rob/bin:/home/rob/.rvm/bin:/home/rob/.local/bin:/home/rob/bin My default java: [rob@localhost eclipse]$ java -version java version "1.8.0_31" Java(TM) SE Runtime Environment (build 1.8.0_31-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode) Eclipse is running with Java 8. I have configured my fsw6.0 runtime to use a java 7. It starts without error. My launch command: rob 7834 31.9 6.1 1725904 995624 pts/0 Sl+ 12:24 1:18 /home/rob/apps/java/jdk1.7.0_67/bin/java -Dprogram.name=JBossTools: JBoss Fuse Service Works 6.0 -server -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/standalone/log/boot.log -Dlogging.configuration=file:/home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/standalone/configuration/logging.properties -Djboss.home.dir=/home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=UTF-8 -classpath /home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/jboss-modules.jar org.jboss.modules.Main -mp /home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=/home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/standalone I am not experiencing any error at all. > Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8 > ----------------------------------------------------------------- > > Key: JBDS-3345 > URL: https://issues.jboss.org/browse/JBDS-3345 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 8.0.2.GA > Environment: Fedora 21 x86_64 > JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, runtime_jre.png, server.log > > > FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file. > Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually. > Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19733: -------------------------------------- Assignee: Mickael Istria (was: Ilya Buziuk) > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19744: ------------------------------------ Given that the snapshot and the release version are bitwise identical in all ways except the name, and that 4.2.x is at EOD (unless we decide to do a 4.2.4 / 8.1.1), here's what I would do: a) fix parent pom in 4.2.x branch (lower case) to remove the -SNAPSHOT suffix on the target platform version. b) delete the 4.2.X (upper case) branch So say we all? Note: the only problem w/ the parent pom in 4.2.x (lower case) branch retaining the -SNAPSHOT suffix is that at some point the snapshot will be deleted from Nexus and so anyone using the 4.2.3.Final-SNAPSHOT parent pom will be unable to resolve the .target file. So because IS 8.x development is ongoing (and they should be using that parent pom, right [~pleacu] ?) therefore this needs to be fixed ASAP. > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19732) Misleading error logged when a new hybrid mobile engine configured

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19732?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19732: ------------------------------------ Assignee: Gorkem Ercan > Misleading error logged when a new hybrid mobile engine configured > ------------------------------------------------------------------ > > Key: JBIDE-19732 > URL: https://issues.jboss.org/browse/JBIDE-19732 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Priority: Minor > > There's no functional impact, but the error message is confusing. > When a new mobile hybrid engine is configured, this error is logged: > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 14:38:54.071 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar > The file, however, is right where it belongs: > ll /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar > -rw-rw-r--. 1 ldimaggi ldimaggi 357355 Apr 28 14:38 /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015