[JBoss JIRA] (JBIDE-21684) jaxws quickstarts require nonexistant endorsed folder
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21684?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21684.
---------------------------------
I verified that I don't see any errors now. Tested with JBDS 9.1.0.CR1 B443.
> jaxws quickstarts require nonexistant endorsed folder
> -----------------------------------------------------
>
> Key: JBIDE-21684
> URL: https://issues.jboss.org/browse/JBIDE-21684
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server, upstream
> Affects Versions: 4.3.1.Beta2
> Reporter: Rob Stryker
> Assignee: Rafael Benevides
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> The jaxws quickstarts in the 10.x branch have the following errors:
> Endorsed directory '/home/rob/code/github/jboss_stuff/quickstart/jaxws-ejb/service/target/endorsed' is missing. You may need to a perform a
> Maven command line build in order to create it.
> Even after building from the command line, the requested folders are not created. This indicates that either there is something wrong with the build (ie it should be creating the endorsed folder) or this is a legacy detail that is no longer needed (ie the project does not actually require an endorsed directory, so the pom lines requesting it are unnecessary)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21899) Wrong service is preselected when creating a new OS3 server adapter from context menu of a service
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21899?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21899.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B260.
> Wrong service is preselected when creating a new OS3 server adapter from context menu of a service
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21899
> URL: https://issues.jboss.org/browse/JBIDE-21899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.CR1
>
>
> When I am creating a new OpenShift 3 server adapter from context menu of a service in OpenShift explorer view and I am having several projects and at least 2 same services (names must be equal) in different projects, then in New OS 3 Server Wizard is wrong service. This is happening when I am trying to create a server adapter from context menu of a service which is lower (in order of tree items under an OpenShift 3 connection) then a service with same name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-22004:
-------------------------------------------
Coming back to checking the _Vagrantfile_ itself. It will always contain the box name which we can assume to be cdk<something>. This might be a viable approach which does not require a marker file.
> Runtime detection unable to detect CDK
> --------------------------------------
>
> Key: JBIDE-22004
> URL: https://issues.jboss.org/browse/JBIDE-22004
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Radim Hopp
> Assignee: Hardy Ferentschik
> Fix For: 4.4.x
>
>
> Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it.
> Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-574) Adapt UI tests to 8.0.0
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-574?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík resolved JBTIS-574.
--------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Final)
Resolution: Done
> Adapt UI tests to 8.0.0
> -----------------------
>
> Key: JBTIS-574
> URL: https://issues.jboss.org/browse/JBTIS-574
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 4.3.0.Alpha2
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Priority: Critical
> Fix For: 4.3.0.CR1
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> There are some changes in Fuse Tooling (new Camel Editor, ...), so our automated tests have to be adapted to reflect these changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21351) Error during "Update Maven projects configuration"
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21351?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21351:
----------------------------------------
It should be resolved. But if you faced this issue today, it seems that I missed something...
You used the Steps to Reproduce from this jira, right?
> Error during "Update Maven projects configuration"
> --------------------------------------------------
>
> Key: JBIDE-21351
> URL: https://issues.jboss.org/browse/JBIDE-21351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.1.Beta1
> Reporter: Radim Hopp
> Assignee: Mickael Istria
> Fix For: 4.3.1.CR1
>
>
> Sometimes I get
> {noformat}
> An internal error occurred during: "Update Maven projects configuration".
> Cannot add projects when processing is started{noformat}
> when I'm importing maven project using easymport.
> Full stacktrace:
> {noformat}
> java.lang.IllegalStateException: Cannot add projects when processing is started
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years