[JBoss JIRA] (JBDS-4533) RPM should depend on upstream m2e-wtp rpms, including jaxrs, jpa, jsf
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4533?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4533:
-----------------------------
Fix Version/s: 11.x
> RPM should depend on upstream m2e-wtp rpms, including jaxrs, jpa, jsf
> ---------------------------------------------------------------------
>
> Key: JBDS-4533
> URL: https://issues.jboss.org/browse/JBDS-4533
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: 3rd-party-dependencies, rpm, target-platform, upstream
> Affects Versions: 11.1.0.AM1
> Reporter: Nick Boldt
> Fix For: 11.x
>
>
> RPM should depend on upstream m2e rpms, including jaxrs, jpa, jsf. Depends on getting this done in Fedora and devtools channel first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (ERT-525) Docker launch not able to handle debugging C/C++ programs that printf without newlines [EBZ#521211]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-525?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston updated ERT-525:
------------------------------
Sprint: devex #137 September 2017
> Docker launch not able to handle debugging C/C++ programs that printf without newlines [EBZ#521211]
> ---------------------------------------------------------------------------------------------------
>
> Key: ERT-525
> URL: https://issues.jboss.org/browse/ERT-525
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 6.1.1, Docker, bzira
>
> Using the CDT Debug in Container support for C/C++ applications, if a simple C application does a printf without a newline, the line may or may not be shown while stepping or running the program inside gdbserver. It appears that the Docker daemon is not reliable in delivering output in such a case and sometimes it turns up too late (e.g. gdbserver and the application are both finished) so it does not appear. Sometimes it shows up after gdbserver and the application is finished. In such a case, a line containing a single LineFeed character is printed in the place it should have been printed in the first place.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ]
Jeff Johnston updated JBIDE-24966:
----------------------------------
Sprint: devex #137 September 2017
> linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2
> ------------------------------------------------------------------------------
>
> Key: JBIDE-24966
> URL: https://issues.jboss.org/browse/JBIDE-24966
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.5.1.AM2
> Reporter: Nick Boldt
> Assignee: Jeff Johnston
> Priority: Blocker
> Fix For: 4.5.1.AM2
>
>
> Turns out we have a blocker here.
> org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace.
> Therefore this manifest needs to be changed, if we want to include Red Deer 2.0 in jbosstools 4.5.1.AM2 / devstudio 11.1.0.AM2:
> {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF}
> Require-Bundle: org.junit,org.eclipse.swt,
> org.eclipse.ui,
> org.eclipse.osgi,org.eclipse.core.runtime,
> org.jboss.reddeer.eclipse;bundle-version="1.2.1", <<
> org.jboss.reddeer.common;bundle-version="1.2.1", <<
> org.jboss.reddeer.swt;bundle-version="1.2.1", <<
> org.jboss.reddeer.core;bundle-version="1.2.1", <<
> org.jboss.reddeer.workbench;bundle-version="1.2.1", <<
> org.apache.commons.lang;bundle-version="2.6.0",
> org.eclipse.linuxtools.docker.core,
> org.hamcrest.library;bundle-version="1.3.0",
> org.hamcrest.core;bundle-version="1.3.0"{code}
> Note that the target platform freeze for the upcoming AM2 milestone is next Tuesday, Sept 12. Ideally, this would be fixed a few days before, so that I can apply other changes in advance.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4532) RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4532?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4532 at 9/5/17 3:55 PM:
----------------------------------------------------------
TODO:
* update jbt/devstudio TP to use these newer versions:
** org.eclipse.m2e.feature, org.eclipse.m2e.tests.common, org.eclipse.m2e.importer 0.8.0 -> JBIDE-24973 --> latest: 1.8.1.20170728-1531
** org.sonatype.tycho.m2e.feature 0.9.0 -> JBIDE-24974 --> latest: 0.9.0.201609252021
* build org.jboss.tools.maven.apt.feature 1.3.0 (or newer) in Koji -> BZ?
* build org.jboss.tools.maven.sourcelookup.feature 1.8.101.v20170822-1709 (or newer) in Koji -> BZ?
was (Author: nickboldt):
TODO:
* update jbt/devstudio TP to use these newer versions:
** org.eclipse.m2e.feature, org.eclipse.m2e.tests.common, org.eclipse.m2e.importer 0.8.0 -> JBIDE-24973
** org.sonatype.tycho.m2e.feature 0.9.0 -> JBIDE-24974
* build org.jboss.tools.maven.apt.feature 1.3.0 (or newer) in Koji -> BZ?
* build org.jboss.tools.maven.sourcelookup.feature 1.8.101.v20170822-1709 (or newer) in Koji -> BZ?
> RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4532
> URL: https://issues.jboss.org/browse/JBDS-4532
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: 3rd-party-dependencies, rpm, target-platform, upstream
> Affects Versions: 11.1.0.AM1
> Reporter: Nick Boldt
>
> RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho. Depends on getting this done in Fedora and devtools channel first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months