July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Oliver Pfau (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Oliver Pfau updated JBIDE-17700: -------------------------------- Attachment: pom.xml > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Priority: Critical > Attachments: pom.xml > > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Oliver Pfau (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Oliver Pfau commented on JBIDE-17700: ------------------------------------- I don not know if my project uses Truezip. If yes, not explicitly. I just download luna EE edition and added JBoss Tools. I attach my pom.xml but I cannot attach the master pom which has 2600 lines (most dependenies and versions). > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Priority: Critical > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17025) Patching EAP 6.2 breaks classpath jar files

by Hernán Chanfreau (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17025?page=com.atlassian.jira.plugi... ] Hernán Chanfreau commented on JBIDE-17025: ------------------------------------------ Thanks for the feedback! Sadly, it´s no easy for us to upgrade to luna since our application is a rcp based one and the eclipse´s target platform will change, and there are a lot of implications to consider. > Patching EAP 6.2 breaks classpath jar files > ------------------------------------------- > > Key: JBIDE-17025 > URL: https://issues.jboss.org/browse/JBIDE-17025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.2.Final > Environment: Windows 7, Kepler SR2 > Reporter: Jesper Skov > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Using the JBoss CLI command 'patch apply .../eap-6.2.2.zip' breaks some of the module jars (the files become invalid ZIP-archives). > This is apparently done as a way to mark the modules off-limits for the container, while still allowing roll-back if necessary. > See https://access.redhat.com/site/discussions/726623 > Unfortunately, Eclipse includes these jars in the JBossTools-defined classpath. When scanned, these will be found corrupt, and the project classpath marked as broken. > On my installation, the first few files to trigger this problem are: > * modules/system/layers/base/javax/el/api/main/jboss-el-api_2.2_spec-1.0.2.Final-redhat-1.jar > * modules/system/layers/base/javax/el/api/main/jboss-el-api_2.2_spec-1.0.2.Final-redhat-1.jar > I guess it might be possible to adjust the server definition's Default Classpath Entries in Eclipse preferences. But I decided to just copy the original EAP 6.2 files on top of the runtime and get on with work... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-17700: ------------------------------------- [~olpf] : does your project use truezip by any chance? Do you use Maven to build your project? If yes, could you attach a copy of your effective pom.xml (after sanitizing/anonymizing any sensible data) [~rob.stryker] : TrueZip 7.x changed their internals pretty significantly. (See https://java.net/projects/truezip/sources/v7/content/truezip-driver/truez..., https://java.net/projects/truezip/sources/v7/content/truezip-driver/truez..., https://java.net/projects/truezip/sources/v7/content/truezip-kernel/src/m...). The new architecture may fix (hide) the reported error ... or not. Might be a good idea to see if we could integrate the latest version (Everything is now split in different jars, so it may not be trivial). Anyways, even if moving to TZ 7.x fixed the error, that wouldn't explain nor fix the inherent Classloader leakage. > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Priority: Critical > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations

by Andrei Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ] Andrei Ivanov commented on JBIDE-14305: --------------------------------------- Should I create a new ticket? > Error popup when runing schema ddl with Hibernate Configurations > ----------------------------------------------------------------- > > Key: JBIDE-14305 > URL: https://issues.jboss.org/browse/JBIDE-14305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: labdoui labdoui > Assignee: Koen Aers > Priority: Minor > Fix For: 4.1.0.Beta2 > > > Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema > to reproduce the problem just explore the database from hibernate console > java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V > at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) > at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) > at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) > at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3079?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3079: -------------------------------------- I think what's missing with option A is that is you have JBDS-update-site.zip + JBDS-Central-site.zip, then you're missing the JBoss Tools bundles listed above so you can't install Hybrid Mobile Tools. So the idea is to add the the JBDS-Central-Site the necessary bundles to have it working. > Offline Central installation misses some JBT bundles > ---------------------------------------------------- > > Key: JBDS-3079 > URL: https://issues.jboss.org/browse/JBDS-3079 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: discovery > Affects Versions: 8.0.0.Beta2 > Reporter: Mickael Istria > Priority: Minor > Fix For: 8.0.0.Beta3 > > > Removed items include: > org.jboss.tools.vpe.cordovasim.feature (and source) > org.jboss.tools.maven.jbosspackaging.feature (and source) > org.jboss.tools.common.mylyn.feature (and source) > Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors: > JBoss Hybrid Mobile Tools + CordovaSim > JBoss Tools Maven Packaging Configurator > Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas > So if we remove them, then those connectors can't be installed in JBDS. > Possible workarounds: > a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site > b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) [I did this in JBDS-3071 but [~dgolovin] reverted it] > c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP > d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP. > Since (b) was rejected, clearly the solution is (d). Or do nothing and annoy offline users with (a). :D -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17733) Cleanup Central discovery catalog: remove pre-installed items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-17733: -------------------------------------- Assignee: Mickael Istria > Cleanup Central discovery catalog: remove pre-installed items > ------------------------------------------------------------- > > Key: JBIDE-17733 > URL: https://issues.jboss.org/browse/JBIDE-17733 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Beta3 > > Attachments: eclipse-platform-installs-jbt-beta3-OK.png, eclipse-standard-installs-jbt-beta3-OK.png > > > Here is a list of items that should probably be removed from Central catalog: > *EGit*: Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. > So we should remove EGit from our Central discovery catalogs. > *jst.server* is already installed in JBDS, so there is no point in having it on JBDS Central -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3079?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3079: ------------------------------------------- I'm very confused - what is wrong with option A here ? We never said the installer is an updatesite. > Offline Central installation misses some JBT bundles > ---------------------------------------------------- > > Key: JBDS-3079 > URL: https://issues.jboss.org/browse/JBDS-3079 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: discovery > Affects Versions: 8.0.0.Beta2 > Reporter: Mickael Istria > Priority: Minor > Fix For: 8.0.0.Beta3 > > > Removed items include: > org.jboss.tools.vpe.cordovasim.feature (and source) > org.jboss.tools.maven.jbosspackaging.feature (and source) > org.jboss.tools.common.mylyn.feature (and source) > Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors: > JBoss Hybrid Mobile Tools + CordovaSim > JBoss Tools Maven Packaging Configurator > Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas > So if we remove them, then those connectors can't be installed in JBDS. > Possible workarounds: > a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site > b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) [I did this in JBDS-3071 but [~dgolovin] reverted it] > c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP > d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP. > Since (b) was rejected, clearly the solution is (d). Or do nothing and annoy offline users with (a). :D -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17733) Cleanup Central discovery catalog: remove pre-installed items

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17733: --------------------------------------------- Please remember that connectors in central has two purposes: 1) provide UI to install components from 2) give id's we can refer to from examples to install - id's that are *NOT* bound to specific feature names, but more to a set of relevant features/plugins to install when creating a project (like browserim,cordovasim, hybrid tools and jst feature for the mobile tools). This is what is used to tell the user if he has the plugins installed or not in the first page of the example wizards. Also not everyone installs everything in jbosstools. thus there isn't really anything "pre-installed" except maybe egit these days. > Cleanup Central discovery catalog: remove pre-installed items > ------------------------------------------------------------- > > Key: JBIDE-17733 > URL: https://issues.jboss.org/browse/JBIDE-17733 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Fix For: 4.2.0.CR1 > > Attachments: eclipse-platform-installs-jbt-beta3-OK.png, eclipse-standard-installs-jbt-beta3-OK.png > > > Here is a list of items that should probably be removed from Central catalog: > *EGit*: Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. > So we should remove EGit from our Central discovery catalogs. > *jst.server* is already installed in JBDS, so there is no point in having it on JBDS Central -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17700: --------------------------------------------- Olivier, forge doesn't provide maven so you should be fine. > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Priority: Critical > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 2014