[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3141:
-------------------------------------------
I don't think the sample has a bug - it is supposed to fail. See the readme to make it pass ;)
The other errors/warnings are expected.
The source layout of the sample has packagename != dir names and mvn tells users that it will skip the vitims/enforcer plugin as info.
> Test victi.ms maven plugin works within jbds (or at least does not fail)
> ------------------------------------------------------------------------
>
> Key: JBDS-3141
> URL: https://issues.jboss.org/browse/JBDS-3141
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: maven
> Reporter: Burr Sutter
> Assignee: Len DiMaggio
> Fix For: 8.0.0.CR2
>
> Attachments: Screenshot.png
>
>
> http://victi.ms has a maven plugin to check/assert maven dependencies have issues.
> should check how it works and if it works within eclipse
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[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:
-------------------------------------------
All I'm asking here is that we add the IJBossToolingConstants.EAP_61 reference to the array for org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants
> 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)
10 years, 2 months
[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:
-------------------------------------------
Adding the IJBossToolingConstants.EAP_61 reference to the array for org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants would do it. :)
> 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)
10 years, 2 months
[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 edited comment on JBIDE-16066 at 9/30/14 6:15 PM:
--------------------------------------------------------------------
You can get around the "Runtime Location not set" problem by defining a JBoss AS 7.1 runtime that points to EAP. Going that route, I was able to create a Dynamic Web Project, create a WSDL there, and then create a new Web Service (top-down), which created a new EAR file that was deployed just fine. And I was able to get to the WSDL via the WS Tester without incident.
was (Author: bfitzpat):
You can get around the "Runtime Location not set" problem by defining a JBoss AS 7.1 runtime that points to EAP. Going that route, I was able to create a Dynamic Web Project, create a WSDL there, and then create a new Web Service (top-down), which created a new EAR file that was deployed just fine.
> 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)
10 years, 2 months
[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:
-------------------------------------------
You can get around the "Runtime Location not set" problem by defining a JBoss AS 7.1 runtime that points to EAP. Going that route, I was able to create a Dynamic Web Project, create a WSDL there, and then create a new Web Service (top-down), which created a new EAR file that was deployed just fine.
> 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)
10 years, 2 months