[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3551:
---------------------------------
Fix Version/s: 9.x
10.x
(was: 10.0.0.Alpha1)
(was: 9.1.0.CR1)
> JavaEE Developer - be able to start/stop applications on docker with debug on/off
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3551
> URL: https://issues.jboss.org/browse/JBDS-3551
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.x, 10.x
>
>
> User Story:
> As a JavaEE Developer I should be able to start/stop applications with debug turned on or off
> Acceptance Criteria:
> * Developer can start/stop an application from a central place, no CLI operations needed.
> * Developer can start with or without debug enabled
> * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart
> * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21715) Unable to deploy image because a deployment (replication controller) does not exist
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-21715:
-------------------------------------
Summary: Unable to deploy image because a deployment (replication controller) does not exist
Key: JBIDE-21715
URL: https://issues.jboss.org/browse/JBIDE-21715
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Jeff Cantrill
Deploying an image creates a set of resources but trying to manually trigger a deployment throws an exception: http://screencast.com/t/gz8quBbAboGg
This presumably could be a case where we are trying to tigger assuming a deployment exists but one doesnt because:
a) its building and hasnt triggered one yet
b) the built image exists but there is some other reason that prevents the imagechangetrigger
We should still be able to trigger a build using the dc provided OpenShift is able to access the image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3598 at 2/18/16 10:48 AM:
------------------------------------------------------------
Turns out this is caused by trying to build a maven project w/o the .git metadata folder being present. We introduced this problem when we implemented https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers and then started producing source zips with `git archive` instead of `git clone` via JBIDE-19814 in May 2015:
https://github.com/jbosstools/jbosstools-maven-plugins/commit/7cc83045674...
{quote}Resolution: As per the link by "Malte Skoruppa", the issue happens when code is not checked-out from Git repository but is downloaded as a zipped file containing the code. So, error got resolved by cloning the Repository from Git (previously I was achieving this by cloning the workspace from an upstream Jenkins job). {quote} -- http://stackoverflow.com/questions/19143534/hudson-error-when-checking-ou...
So I need to add the .git folder into the src zip so that one can build from the sources zip.
Or we could migrate the sources to a public github repo and stop providing a zip entirely.
[~maxandersen] [~akazakov] WDYT? Is it time to move https://github.com/jbdevstudio/jbdevstudio-product to https://github.com/jbosstools/jbdevstudio-product ?
was (Author: nickboldt):
Turns out this is caused by trying to build a maven project w/o the .git metadata folder being present. We introduced this problem when we implemented https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers and then started producing source zips with `git archive` instead of `git clone` via JBIDE-19814 in May 2015:
https://github.com/jbosstools/jbosstools-maven-plugins/commit/7cc83045674...
{quote}
Resolution: As per the link by "Malte Skoruppa", the issue happens when code is not checked-out from Git repository but is downloaded as a zipped file containing the code. So, error got resolved by cloning the Repository from Git (previously I was achieving this by cloning the workspace from an upstream Jenkins job). {quote} -- http://stackoverflow.com/questions/19143534/hudson-error-when-checking-ou...
So I need to add the .git folder into the src zip so that one can build from the sources zip.
Or we could migrate the sources to a public github repo and stop providing a zip entirely.
[~maxandersen] [~akazakov] WDYT? Is it time to move https://github.com/jbdevstudio/jbdevstudio-product to https://github.com/jbosstools/jbdevstudio-product ?
> 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] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3598 at 2/18/16 10:48 AM:
------------------------------------------------------------
Turns out this is caused by trying to build a maven project w/o the .git metadata folder being present. We introduced this problem when we implemented https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers and then started producing source zips with `git archive` instead of `git clone` via JBIDE-19814 in May 2015:
https://github.com/jbosstools/jbosstools-maven-plugins/commit/7cc83045674...
{quote}
Resolution: As per the link by "Malte Skoruppa", the issue happens when code is not checked-out from Git repository but is downloaded as a zipped file containing the code. So, error got resolved by cloning the Repository from Git (previously I was achieving this by cloning the workspace from an upstream Jenkins job). {quote} -- http://stackoverflow.com/questions/19143534/hudson-error-when-checking-ou...
So I need to add the .git folder into the src zip so that one can build from the sources zip.
Or we could migrate the sources to a public github repo and stop providing a zip entirely.
[~maxandersen] [~akazakov] WDYT? Is it time to move https://github.com/jbdevstudio/jbdevstudio-product to https://github.com/jbosstools/jbdevstudio-product ?
was (Author: nickboldt):
Turns out this is caused by trying to build a maven project w/o the .git metadata folder being present.
So I need to add the .git folder into the repo so that one can build from the sources zip.
Or we could migrate the sources to a public github repo and stop providing a zip entirely.
[~maxandersen] [~akazakov] WDYT? Is it time to move https://github.com/jbdevstudio/jbdevstudio-product to https://github.com/jbosstools/jbdevstudio-product ?
> 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] (JBTIS-471) Unify component versions
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-471:
----------------------------------
[~bbrodt] - Hi Bob - Could you tweak your build versions for consistency? Give a time of 0800 and a build 212:
* JBoss Drools Core 6.4.0.201601201107 should be 6.4.0-v201601201107-0800-B212
* BPMN2 Metamodel 1.2.1.Final-v20160119-1829 should be 1.2.1.Final-v20160119-1829-B212
* BPMN2 Modeler - Diagram Editor 1.2.3.CR2-v20160209-2002 should be 1.2.3.CR2-v20160209-2002-B212
* BPMN2 Modeler - jBPM Runtime Extension Feature 1.2.3.CR2-v20160209-2002 should be 1.2.3.CR2-v20160209-2002-B212
[~bfitzpat] - Could you make a small tweak to your versions as well:
SwitchYard 2.1.0.v20160211-1448-H632-Beta2 should be 2.1.0.Beta2-v20160211-1448-B632
Same for the other 2 SY features.
[~apodhrad] - please comment if the above is correct.
> Unify component versions
> ------------------------
>
> Key: JBTIS-471
> URL: https://issues.jboss.org/browse/JBTIS-471
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 8.0.3.GA
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Fix For: 4.3.0.Beta1
>
> Attachments: junit4.8vs4.12.png
>
>
> Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as
> BPMN2 1.1.3.Final
> Fuse 7.3.1.v20150728-1330-H54-Final
> Teiid Designer 9.0.3.Final-v20150728-2029-B1148
> I suggest to use the format used by Teiid Designer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month