October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18490) Use project.build.finalName for repsoitory-utils plugin output

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18490?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18490: -------------------------------- Component/s: (was: maven) > Use project.build.finalName for repsoitory-utils plugin output > -------------------------------------------------------------- > > Key: JBIDE-18490 > URL: https://issues.jboss.org/browse/JBIDE-18490 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Rob Cernich > > I've modified build/finalName in one of my site projects to use the qualified version (instead of SNAPSHOT). This works fine except that the zip created by generate-repository-facade still uses artifactId-version.zip. It would be nice if this behavior could be overridden. > I'm using v0.21. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18490) Use project.build.finalName for repsoitory-utils plugin output

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18490?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18490: ------------------------------------- I believe that's a question for [~mickael_istria] > Use project.build.finalName for repsoitory-utils plugin output > -------------------------------------------------------------- > > Key: JBIDE-18490 > URL: https://issues.jboss.org/browse/JBIDE-18490 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Rob Cernich > > I've modified build/finalName in one of my site projects to use the qualified version (instead of SNAPSHOT). This works fine except that the zip created by generate-repository-facade still uses artifactId-version.zip. It would be nice if this behavior could be overridden. > I'm using v0.21. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18490) Use project.build.finalName for repsoitory-utils plugin output

by Rob Cernich (JIRA)

Rob Cernich created JBIDE-18490: ----------------------------------- Summary: Use project.build.finalName for repsoitory-utils plugin output Key: JBIDE-18490 URL: https://issues.jboss.org/browse/JBIDE-18490 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build, maven Reporter: Rob Cernich I've modified build/finalName in one of my site projects to use the qualified version (instead of SNAPSHOT). This works fine except that the zip created by generate-repository-facade still uses artifactId-version.zip. It would be nice if this behavior could be overridden. I'm using v0.21. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-16066: -------------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.2.0.CR2) > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.3.0.Alpha1 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- Ok, so here's what we have diagnosed. There's a timing issue in the Web Service wizard that can be worked around with a pause while on the JBoss Web Service Code Generation Configuration page. When you get to that page in the wizard, take a breath or two, then click Next - rather than just quickly clicking Next when you get here. The delay may need to be different based on system configuration or hardware speed, but I can get through it by counting "one one thousand, two one thousand, three one thousand" and then clicking Next. if you don't, you get a warning in the server console during deployment that looks something like this: {code} 08:14:23,002 WARN [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component org.example.newwsdlfile.impl.NewWSDLFileImpl due to an exception (enable DEBUG log level to see the cause) {code} If it doesn't deploy successfully like this, all you have to do is a "Full Publish" on the deployed project in the Servers view and it works fine. If you do the pause, it deploys fine and you can test it as expected. This is NOT A BLOCKER. > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.3.0.Alpha1 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18457) EAP 6.1 fails to start on Windows 7 - need to warn users if they use wrong java

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18457: ---------------------------------- Summary: EAP 6.1 fails to start on Windows 7 - need to warn users if they use wrong java (was: EAP 6.1 fails to start on Windows 7 - stuck on Starting) > EAP 6.1 fails to start on Windows 7 - need to warn users if they use wrong java > ------------------------------------------------------------------------------- > > Key: JBIDE-18457 > URL: https://issues.jboss.org/browse/JBIDE-18457 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1 to start on Windows 7. I tried the same and get the same result. Everything works fine on my mac. > 1. Start JBDS 8.0.0.CR1 > 2. Download EAP 6.1 via runtime detection > 3. Start the server > In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar and nothing else for like 5 minutes, then the server console showed up and showed: > {code} > 15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1 > 15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 > 15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting > {code} > And with this the status bar changed to 100 % and the progress view shows: > Preparing launch deletage. > It's been like this at least 5 minutes now. The server is not started. > I checked with Brian and he just didn't witness the first part where there was no console, but he did get what I got after 5 minutes - his server was stuck and would never really start. > ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection. > In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem to matter. > Right now I haven't tried other server versions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- [~maxandersen] Though the fixes Rob made for JBIDE-18457 get us further, the issue seems to lie with the use of the application.xml deployment descriptor. This is what's causing the issue in AS 7/EAP. It deploys fine and is able to be tested without it. Is the application.xml descriptor required for JBoss AS 7-based runtimes? Can we get through without it? I'll keep digging, but I'm not getting very far I'm afraid. > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18461?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-18461: ------------------------------------------- [~rob.stryker] This should also be pushed back into the JBDS 7.1.1 branch for whenever we issue the next JBoss Tools patch. It affects that version too. > org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > -------------------------------------------------------------------------------- > > Key: JBIDE-18461 > URL: https://issues.jboss.org/browse/JBIDE-18461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Brian Fitzpatrick > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18486) Default values for repository snapshots and releases

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18486?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-18486 at 10/2/14 10:01 AM: --------------------------------------------------------------- Yes, if the repo has no releases/snapshot nodes, then it shows snapshots disabled but it's actually enabled for maven, so that's a bug was (Author: fbricon): Yes, if the repo as no releases/snapshot nodes, then it shows snapshots disabled but it's actually enabled for maven, so that's a bug > Default values for repository snapshots and releases > ---------------------------------------------------- > > Key: JBIDE-18486 > URL: https://issues.jboss.org/browse/JBIDE-18486 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.CR1 > Reporter: Rastislav Wagner > > Current default values when creating new repository via Configure Maven Repositories are: > snapshots - disabled, policy - daily > releases - enabled, policy - never > According to maven website, default values for both should be enabled and policy daily. See http://maven.apache.org/ref/3.2.3/maven-settings/settings.html > Shouldn't we align these values with maven docs ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18486) Default values for repository snapshots and releases

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18486?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18486: ------------------------------------- Yes, if the repo as no releases/snapshot nodes, then it shows snapshots disabled but it's actually enabled for maven, so that's a bug > Default values for repository snapshots and releases > ---------------------------------------------------- > > Key: JBIDE-18486 > URL: https://issues.jboss.org/browse/JBIDE-18486 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.CR1 > Reporter: Rastislav Wagner > > Current default values when creating new repository via Configure Maven Repositories are: > snapshots - disabled, policy - daily > releases - enabled, policy - never > According to maven website, default values for both should be enabled and policy daily. See http://maven.apache.org/ref/3.2.3/maven-settings/settings.html > Shouldn't we align these values with maven docs ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014