[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-24380:
----------------------------------
Assignee: Nick Boldt
> new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
> -------------------------------------------------------------------
>
> Key: JBIDE-24380
> URL: https://issues.jboss.org/browse/JBIDE-24380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom:
> {code}
> - <jbosstools.test.jre.5></jbosstools.test.jre.5>
> - <jbosstools.test.jre.6></jbosstools.test.jre.6>
> - <jbosstools.test.jre.7></jbosstools.test.jre.7>
> - <jbosstools.test.jre.8></jbosstools.test.jre.8>
> + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
> + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
> + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
> + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
> {code}
> This way, depending on what your system's definition of JAVA_HOME happens to be, you get a different effective pom, for your required JDK:
> {code}
> $ export JAVA_HOME=/opt/jdk1.8.0/
> $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
> <jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5>
> <jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6>
> <jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7>
> <jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8>
> (or, to use the JAVA_HOME set by alternatives...)
> $ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e "s#.\+ \(.\+\)bin/java#\1#")
> $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
> <jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5>
> <jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6>
> <jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7>
> <jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBTIS-1101) Cannot install reddeer feature
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1101?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky edited comment on JBTIS-1101 at 5/4/17 8:40 AM:
------------------------------------------------------------------
I will fix it on reddeer side but for the coming release of Integration Stack we should fix it in JBTIS TP by adding
{code}
org.jboss.reddeer.eclipse.feature.feature.group
{code}
was (Author: apodhrad):
I will fix it on reddeer side but for the coming release of Integration Stack we should fit it in JBTIS TP by adding
{code}
org.jboss.reddeer.eclipse.feature.feature.group
{code}
> Cannot install reddeer feature
> ------------------------------
>
> Key: JBTIS-1101
> URL: https://issues.jboss.org/browse/JBTIS-1101
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.3.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
>
> The following feature cannot be installed
> - org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final
> The error is
> {code}
> Your original request has been modified.
> "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed.
> Cannot complete the install because one or more required items could not be found.
> Software being installed: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final)
> Missing requirement: RedDeer GEF Component 1.2.1.Final (org.jboss.reddeer.gef 1.2.1.Final) requires 'bundle org.jboss.reddeer.workbench [1.2.0,1.3.0)' but it could not be found
> Cannot satisfy dependency:
> From: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final)
> To: org.jboss.reddeer.gef [1.2.1.Final]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBTIS-1101) Cannot install reddeer feature
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1101?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky commented on JBTIS-1101:
------------------------------------------
Yes, that would be the best solution since at the moment there's no reason to have that dependency in the TP.
I wanted to move some tests to fuseide project but it turned out not to be an easy task.
So, I will wait for oxygen with this task.
> Cannot install reddeer feature
> ------------------------------
>
> Key: JBTIS-1101
> URL: https://issues.jboss.org/browse/JBTIS-1101
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.3.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
>
> The following feature cannot be installed
> - org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final
> The error is
> {code}
> Your original request has been modified.
> "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed.
> Cannot complete the install because one or more required items could not be found.
> Software being installed: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final)
> Missing requirement: RedDeer GEF Component 1.2.1.Final (org.jboss.reddeer.gef 1.2.1.Final) requires 'bundle org.jboss.reddeer.workbench [1.2.0,1.3.0)' but it could not be found
> Cannot satisfy dependency:
> From: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final)
> To: org.jboss.reddeer.gef [1.2.1.Final]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24301 at 5/4/17 8:37 AM:
------------------------------------------------------------
[~jyoti-jboss]
I've removed your question from JBIDE-24382 as it doesn't below there.
Please read https://github.com/jbosstools/jbosstools-devdoc/
Basically you need to:
a) fetch the target platform zip (or.target file) and enable it in Eclipse. Make sure you have m2e.tycho 0.8.1 installed too.
b) build jbosstools-base, jbosstools-server, and then jbosstools-openshift.
Or, way easier, build it commandline.
This should resolve all the dependencies:
{code}
git clone https://github.com/jbosstools/jbosstools-openshift.git
cd jbosstools-openshift
# install mvn 3.3.9 to your PATH
mvn clean install -Djbosstools-base-site=http://download.jboss.org/jbosstools/neon/snapshots/updates/ -DskipTests=true
{code}
Regarding the test failure in foundation.checkup.test... it's hard to help with that if you don't state what the error was.
was (Author: nickboldt):
[~jyoti-jboss] Please read https://github.com/jbosstools/jbosstools-devdoc/
Basically you need to:
a) fetch the target platform zip (or.target file) and enable it in Eclipse. Make sure you have m2e.tycho 0.8.1 installed too.
b) build jbosstools-base, jbosstools-server, and then jbosstools-openshift.
Or, way easier, build it commandline.
This should resolve all the dependencies:
{code}
git clone https://github.com/jbosstools/jbosstools-openshift.git
cd jbosstools-openshift
# install mvn 3.3.9 to your PATH
mvn clean install -Djbosstools-base-site=http://download.jboss.org/jbosstools/neon/snapshots/updates/ -DskipTests=true
{code}
Regarding the test failure in foundation.checkup.test... it's hard to help with that if you don't state what the error was.
> Error while building jbosstools-openshift-4.4.3
> -----------------------------------------------
>
> Key: JBIDE-24301
> URL: https://issues.jboss.org/browse/JBIDE-24301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.3.Final
> Reporter: jyoti tumsare
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.0.AM1
>
> Attachments: issues.PNG, issues.txt, target-platform.png
>
>
> To build jbosstools-openshift-4.4.3 I followed following steps
> 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3.
> 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found".
> 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24301:
------------------------------------
[~jyoti-jboss] Please read https://github.com/jbosstools/jbosstools-devdoc/
Basically you need to:
a) fetch the target platform zip (or.target file) and enable it in Eclipse. Make sure you have m2e.tycho 0.8.1 installed too.
b) build jbosstools-base, jbosstools-server, and then jbosstools-openshift.
Or, way easier, build it commandline.
This should resolve all the dependencies:
{code}
git clone https://github.com/jbosstools/jbosstools-openshift.git
cd jbosstools-openshift
# install mvn 3.3.9 to your PATH
mvn clean install -Djbosstools-base-site=http://download.jboss.org/jbosstools/neon/snapshots/updates/ -DskipTests=true
{code}
Regarding the test failure in foundation.checkup.test... it's hard to help with that if you don't state what the error was.
> Error while building jbosstools-openshift-4.4.3
> -----------------------------------------------
>
> Key: JBIDE-24301
> URL: https://issues.jboss.org/browse/JBIDE-24301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.3.Final
> Reporter: jyoti tumsare
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.0.AM1
>
> Attachments: issues.PNG, issues.txt, target-platform.png
>
>
> To build jbosstools-openshift-4.4.3 I followed following steps
> 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3.
> 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found".
> 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24382:
-------------------------------
Comment: was deleted
(was: sir, can you please tell me the steps to build jbosstools-openshift-4.4.3 in eclipse Neon.2 Release (4.6.2).
I mean what is prerequisite and what are the other repository need to run.
What are the exact stpes need to follow, because I am facing lots of issues while buiding the jbosstools-openshift-4.4.3 source code. )
> Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
> -----------------------------------------------------------
>
> Key: JBIDE-24382
> URL: https://issues.jboss.org/browse/JBIDE-24382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.Final
>
> Attachments: devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png, p2diff.txt
>
>
> 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.)
> 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.)
> cc: [~jjohnstn] [~lvalach] [~odockal]
> Why, you ask?
> Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too.
> Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used.
> [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months