January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21568) No new repository found when recognizing maven repo

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21568?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-21568: ------------------------------------- Fix Version/s: 4.3.1.CR1 > No new repository found when recognizing maven repo > --------------------------------------------------- > > Key: JBIDE-21568 > URL: https://issues.jboss.org/browse/JBIDE-21568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.1.Beta2 > Reporter: Rastislav Wagner > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21568) No new repository found when recognizing maven repo

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21568?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-21568: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 > No new repository found when recognizing maven repo > --------------------------------------------------- > > Key: JBIDE-21568 > URL: https://issues.jboss.org/browse/JBIDE-21568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.1.Beta2 > Reporter: Rastislav Wagner > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20986?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-20986. ------------------------------------ Resolution: Done > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-20986 > URL: https://issues.jboss.org/browse/JBIDE-20986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta2 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20986?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-20986: ------------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-20986 > URL: https://issues.jboss.org/browse/JBIDE-20986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta2 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21567) JBoss EAP 7 Maven repository is not recognized

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21567?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-21567: ------------------------------------- Fix Version/s: (was: 4.3.1.Beta2) > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-21567 > URL: https://issues.jboss.org/browse/JBIDE-21567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21567) JBoss EAP 7 Maven repository is not recognized

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21567?page=com.atlassian.jira.plugi... ] Rastislav Wagner resolved JBIDE-21567. -------------------------------------- Resolution: Done > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-21567 > URL: https://issues.jboss.org/browse/JBIDE-21567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21567) JBoss EAP 7 Maven repository is not recognized

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-21567: ---------------------------------------- Summary: JBoss EAP 7 Maven repository is not recognized Key: JBIDE-21567 URL: https://issues.jboss.org/browse/JBIDE-21567 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.3.0.Final Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) - ASSERT the Maven repo should be recognized as an EAP repo - FAILURE a "No new repository found" message is displayed This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20986?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-20986. ------------------------------------ verified in JBDS 9.1.0.Beta2-v20160124-1755-B259 > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-20986 > URL: https://issues.jboss.org/browse/JBIDE-20986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3586: ----------------------------------- openjdk version "1.8.0_65" OpenJDK Runtime Environment (build 1.8.0_65-b17) OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > Cannot install Integration Stack from central > --------------------------------------------- > > Key: JBDS-3586 > URL: https://issues.jboss.org/browse/JBDS-3586 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3586: ------------------------------------------- what exact java version are you running with? > Cannot install Integration Stack from central > --------------------------------------------- > > Key: JBDS-3586 > URL: https://issues.jboss.org/browse/JBDS-3586 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2016