April 2016 - jbosstools-issues - Jboss List Archives

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3795: ------------------------------------ Assignee: Hardy Ferentschik > Cant start CDK > -------------- > > Key: JBDS-3795 > URL: https://issues.jboss.org/browse/JBDS-3795 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Assignee: Hardy Ferentschik > Priority: Blocker > Labels: havoc, respin-c > Fix For: 9.1.0.CR1 > > Attachments: screenshot-1.png > > > CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1. > "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." > I can access the OS console: https://10.1.2.2:8443/console > The console output looks OK too: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 => 2222 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: > default: Vagrant insecure key detected. Vagrant will automatically replace > default: this with a newly generated keypair for better security. > default: > default: Inserting generated public key within guest... > default: Removing insecure key from the guest if it's present... > default: Key inserted! Disconnecting and reconnecting using new SSH key... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login 10.1.2.2:8443 > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3795) Cant start CDK

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3795: --------------------------------- Labels: respin-c (was: ) > Cant start CDK > -------------- > > Key: JBDS-3795 > URL: https://issues.jboss.org/browse/JBDS-3795 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Priority: Blocker > Labels: havoc, respin-c > Fix For: 9.1.0.CR1 > > Attachments: screenshot-1.png > > > CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1. > "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." > I can access the OS console: https://10.1.2.2:8443/console > The console output looks OK too: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 => 2222 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: > default: Vagrant insecure key detected. Vagrant will automatically replace > default: this with a newly generated keypair for better security. > default: > default: Inserting generated public key within guest... > default: Removing insecure key from the guest if it's present... > default: Key inserted! Disconnecting and reconnecting using new SSH key... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login 10.1.2.2:8443 > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3795) Cant start CDK

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3795: --------------------------------- Labels: havoc respin-c (was: respin-c) > Cant start CDK > -------------- > > Key: JBDS-3795 > URL: https://issues.jboss.org/browse/JBDS-3795 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Priority: Blocker > Labels: havoc, respin-c > Fix For: 9.1.0.CR1 > > Attachments: screenshot-1.png > > > CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1. > "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." > I can access the OS console: https://10.1.2.2:8443/console > The console output looks OK too: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 => 2222 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: > default: Vagrant insecure key detected. Vagrant will automatically replace > default: this with a newly generated keypair for better security. > default: > default: Inserting generated public key within guest... > default: Removing insecure key from the guest if it's present... > default: Key inserted! Disconnecting and reconnecting using new SSH key... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login 10.1.2.2:8443 > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3795) Cant start CDK

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3795: --------------------------------- Fix Version/s: 9.1.0.CR1 > Cant start CDK > -------------- > > Key: JBDS-3795 > URL: https://issues.jboss.org/browse/JBDS-3795 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Priority: Blocker > Fix For: 9.1.0.CR1 > > Attachments: screenshot-1.png > > > CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1. > "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." > I can access the OS console: https://10.1.2.2:8443/console > The console output looks OK too: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 => 2222 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: > default: Vagrant insecure key detected. Vagrant will automatically replace > default: this with a newly generated keypair for better security. > default: > default: Inserting generated public key within guest... > default: Removing insecure key from the guest if it's present... > default: Key inserted! Disconnecting and reconnecting using new SSH key... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login 10.1.2.2:8443 > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3795) Cant start CDK

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3795: --------------------------------- Description: CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1. "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." I can access the OS console: https://10.1.2.2:8443/console The console output looks OK too: {code} Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'cdkv2'... [KProgress: 10% [KProgress: 20% [KProgress: 90% [K==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 22 => 2222 (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection timeout. Retrying... default: Warning: Remote connection disconnect. Retrying... default: default: Vagrant insecure key detected. Vagrant will automatically replace default: this with a newly generated keypair for better security. default: default: Inserting generated public key within guest... default: Removing insecure key from the guest if it's present... default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... default: No guest additions were detected on the base box for this VM! Guest default: additions are required for forwarded ports, shared folders, host only default: networking, and more. If SSH fails on this machine, please install default: the guest additions and repackage the box to continue. default: default: This is not an error message; everything may continue to work properly, default: in which case you may ignore this message. ==> default: Configuring and enabling network interfaces... ==> default: Registering box with vagrant-registration... ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant ==> default: Running provisioner: shell... default: Running: inline script ==> default: Running provisioner: shell... default: Running: inline script ==> default: ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. ==> default: To modify the number of cores and/or available memory set the environment variables ==> default: VM_CPU respectively VM_MEMORY. ==> default: ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console ==> default: ==> default: To use OpenShift CLI, run: ==> default: $ vagrant ssh ==> default: $ oc login 10.1.2.2:8443 ==> default: ==> default: Configured users are (<username>/<password>): ==> default: openshift-dev/devel ==> default: admin/admin ==> default: ==> default: If you have the oc client library on your host, you can also login from your host. {code} was: CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1: "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." > Cant start CDK > -------------- > > Key: JBDS-3795 > URL: https://issues.jboss.org/browse/JBDS-3795 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Priority: Blocker > Fix For: 9.1.0.CR1 > > Attachments: screenshot-1.png > > > CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1. > "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." > I can access the OS console: https://10.1.2.2:8443/console > The console output looks OK too: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 => 2222 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: > default: Vagrant insecure key detected. Vagrant will automatically replace > default: this with a newly generated keypair for better security. > default: > default: Inserting generated public key within guest... > default: Removing insecure key from the guest if it's present... > default: Key inserted! Disconnecting and reconnecting using new SSH key... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: > ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory. > ==> default: To modify the number of cores and/or available memory set the environment variables > ==> default: VM_CPU respectively VM_MEMORY. > ==> default: > ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console > ==> default: > ==> default: To use OpenShift CLI, run: > ==> default: $ vagrant ssh > ==> default: $ oc login 10.1.2.2:8443 > ==> default: > ==> default: Configured users are (<username>/<password>): > ==> default: openshift-dev/devel > ==> default: admin/admin > ==> default: > ==> default: If you have the oc client library on your host, you can also login from your host. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3795) Cant start CDK

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3795: --------------------------------- Attachment: screenshot-1.png > Cant start CDK > -------------- > > Key: JBDS-3795 > URL: https://issues.jboss.org/browse/JBDS-3795 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Priority: Blocker > Attachments: screenshot-1.png > > > CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1: > "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3795) Cant start CDK

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBDS-3795: ------------------------------------ Summary: Cant start CDK Key: JBDS-3795 URL: https://issues.jboss.org/browse/JBDS-3795 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: cdk, installer Affects Versions: 9.1.0.CR1 Reporter: Alexey Kazakov Priority: Blocker CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1: "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22157) On deployoment, utility JAR projects are being exploded on WEB-INF/LIB

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22157: ------------------------------------- I have a patch up, but it needs more testing and I'm done for the day. > On deployoment, utility JAR projects are being exploded on WEB-INF/LIB > ---------------------------------------------------------------------- > > Key: JBIDE-22157 > URL: https://issues.jboss.org/browse/JBIDE-22157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Eclipse: Mars, latest version. > Webserver: Wilfly 10.0.0 > Maven: 3.3.3 > JBoss Tools: Latest version. > Reporter: Tiago Matias > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside. > After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project. > An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below: > org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado) > org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151) > org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412) > org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475) > org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456) > org.apache.jasper.compiler.Parser.parse(Parser.java:143) > A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built. > I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment. > Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-33) [JFace] MessageDialog should use Link instead of Text [EBZ#484347]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-33?page=com.atlassian.jira.plugin.sys... ] Nick Boldt updated ERT-33: -------------------------- Fix Version/s: Oxygen (4.7) > [JFace] MessageDialog should use Link instead of Text [EBZ#484347] > ------------------------------------------------------------------ > > Key: ERT-33 > URL: https://issues.jboss.org/browse/ERT-33 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 4.6_M6, UI, bzira > Fix For: Oxygen (4.7) > > > In Eclipse IDE, I see many message dialogs giving instruction about opening a wizard or the preference page. Giving such instructions to user is nice, but in many cases, it would be even better to allow user to perform such operations in one click. For example a message dialog with "configure proxy" would have a link to immediately open the proxy settings page. > Those message dialog should also allow selectionListeners for those links. > If MessageDialog provide links by default, it will encourage consumers to take advantage of them, and to be more helpful to their users. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-33) [JFace] MessageDialog should use Link instead of Text [EBZ#484347]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-33?page=com.atlassian.jira.plugin.sys... ] Nick Boldt updated ERT-33: -------------------------- Fix Version/s: (was: Neon (4.6) M6) > [JFace] MessageDialog should use Link instead of Text [EBZ#484347] > ------------------------------------------------------------------ > > Key: ERT-33 > URL: https://issues.jboss.org/browse/ERT-33 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 4.6_M6, UI, bzira > Fix For: Oxygen (4.7) > > > In Eclipse IDE, I see many message dialogs giving instruction about opening a wizard or the preference page. Giving such instructions to user is nice, but in many cases, it would be even better to allow user to perform such operations in one click. For example a message dialog with "configure proxy" would have a link to immediately open the proxy settings page. > Those message dialog should also allow selectionListeners for those links. > If MessageDialog provide links by default, it will encourage consumers to take advantage of them, and to be more helpful to their users. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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