[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3598:
-------------------------------------------
what happened when you use forceContextQualifier ? readingt he docs on it I assume you will have to also disable the git based mojo.
How about running git init before running the build ?
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21727) add OpenShift server adapter to downloadable WTP server adapters
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-21727:
-------------------------------------------
Summary: add OpenShift server adapter to downloadable WTP server adapters
Key: JBIDE-21727
URL: https://issues.jboss.org/browse/JBIDE-21727
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift, server
Reporter: Max Rydahl Andersen
Priority: Critical
We have JBoss server adapters available in Eclise new Server wizard; would be great if we could put OpenShift in there too.
Anything preventing us from doing so ?
Is there a workflow from New server that helps users to create openshift connection etc. ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3566:
--------------------------------
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3566:
--------------------------------------
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-3566.
---------------------------------------
Resolution: Done
so if its done, marking this resolved.
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21722) UX for "problem was found..." is unfortunate when there are mulitple errors and destinations
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21722?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21722:
---------------------------------------------
#1 yeah, I get it is not trivial - but right now when I type into the field I would like it to *at least* goto JBoss Tools, but it will probably goto Eclipse and then nothing at all to JBoss Tools - even if it is for the exact same issue.
I'm not talking about doing it for actual different incidents - but for those that are exactly the same.
#2 a pseduo message could work...having a "Message to: <who receives it>" label on top of the message could work too.
> UX for "problem was found..." is unfortunate when there are mulitple errors and destinations
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-21722
> URL: https://issues.jboss.org/browse/JBIDE-21722
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aeri
> Reporter: Max Rydahl Andersen
> Attachments: A_Problem_Was_Found…_and_Java_EE_-_JBoss_Central_-_Eclipse.png
>
>
> Running Mars.2 with our jbosstools aeri discovery mechanism enabled and generating 4 errors in a row resulted in a dialog popping up with 8 events and its hard to see what user is meant to do and what he can do.
> A few issues:
> 1) comment field seem to be just for the selected event - would be nice to add same comment to all (or at least when same event)
> 2) can't see who is requesting error reports besides the icon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21724) when clicking cancel on "configure automated error reporting" it disables all
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21724?page=com.atlassian.jira.plugi... ]
Marcel Bruch edited comment on JBIDE-21724 at 2/20/16 10:58 AM:
----------------------------------------------------------------
We take "performCancel" as "Disable AERI" w/o knowing why performCancel is called. The change [1] probably meets your expectations better.
https://git.eclipse.org/r/#/c/66985/
was (Author: marcel.bruch):
We take "performCancel" as "disable aeri".
Unfortunately the wizard dialog registers a window-close-listener which calls performCancel. Need to check wether we can bypass this somehow.
> when clicking cancel on "configure automated error reporting" it disables all
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21724
> URL: https://issues.jboss.org/browse/JBIDE-21724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri
> Reporter: Max Rydahl Andersen
> Priority: Critical
>
> When you click configure in aeri preferences the dialog only have Disable and Enable buttons. Clicking "close" in upper left (i.e. Cancel as in = don't do anything) result in all reporting disabled.
> I would expect closing the dialog with the close buton or escape would change nothing. - but i globally disables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3600) include AERI in JBDS 10
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3600?page=com.atlassian.jira.plugin.... ]
Marcel Bruch commented on JBDS-3600:
------------------------------------
Please do not use version 1.0.1; it won't work as expected, i.e, it will only send error reports to eclipse.org and ignore jboss errors.
Use version >1.100.*
> include AERI in JBDS 10
> -----------------------
>
> Key: JBDS-3600
> URL: https://issues.jboss.org/browse/JBDS-3600
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21724) when clicking cancel on "configure automated error reporting" it disables all
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21724?page=com.atlassian.jira.plugi... ]
Marcel Bruch commented on JBIDE-21724:
--------------------------------------
We take "performCancel" as "disable aeri".
Unfortunately the wizard dialog registers a window-close-listener which calls performCancel. Need to check wether we can bypass this somehow.
> when clicking cancel on "configure automated error reporting" it disables all
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21724
> URL: https://issues.jboss.org/browse/JBIDE-21724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri
> Reporter: Max Rydahl Andersen
> Priority: Critical
>
> When you click configure in aeri preferences the dialog only have Disable and Enable buttons. Clicking "close" in upper left (i.e. Cancel as in = don't do anything) result in all reporting disabled.
> I would expect closing the dialog with the close buton or escape would change nothing. - but i globally disables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month