January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-13348: ----------------------------------------- Summary: Cannot deploy BPEL project Key: JBIDE-13348 URL: https://issues.jboss.org/browse/JBIDE-13348 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.2 Environment: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ Reporter: Andrej Podhradsky Assignee: Rob Stryker Priority: Blocker After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server. See JBDS-2437 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12340) could Eclipse EGit: Mylyn Support from JBT 3.3.1 Central be installable on Juno?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12340?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-12340. -------------------------------- Resolution: Rejected As parent issue is resolved, and there's a JBT 4 / JBDS 6 available which includes newer Mylyn for Eclipse Juno 4.2.x, I'm closing this as Rejected. Please use JBT 4 / JBDS 6 if you want a newer Mylyn than what's in JBT 3.3 / JBDS 5, and remember to never cross the streams. > could Eclipse EGit: Mylyn Support from JBT 3.3.1 Central be installable on Juno? > -------------------------------------------------------------------------------- > > Key: JBIDE-12340 > URL: https://issues.jboss.org/browse/JBIDE-12340 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: updatesite, UpStream > Affects Versions: 3.3.1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 3.3.2 > > Attachments: JBIDE12340-install-OK-from-central.png, JBIDE12340-install-OK-from-central2.png > > > See parent issue. After updating Eclipse 3.7.0 to next version of Eclipse (4.2.0) the Eclipse EGit: Mylyn Support in JBoss 3.3 Central cannot be installed due to conflicting dependencies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1925) Review SpringIDE 2.8.0 for inclusion in JBDS 5

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-1925?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-1925. ---------------------------- Resolution: Won't Fix Won't fix in JBDS 5 or 6. See JBDS-2395 for progress on providing SpringIDE 3.x in JBDS 7's Central. Users who want a newer version of SpringIDE should uninstall the feature from JBDS then install it directly from Springsource. > Review SpringIDE 2.8.0 for inclusion in JBDS 5 > ---------------------------------------------- > > Key: JBDS-1925 > URL: https://issues.jboss.org/browse/JBDS-1925 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite, Upstream > Affects Versions: 5.0.0.M4 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Labels: review > Fix For: 5.0.2.GA > > > Current versions of SpringIDE included in JBDS are: > JBDS 4.x :: SpringIDE 2.5 > JBDS 5.0 :: SpringIDE 2.7.2 > The purpose of this JIRA is to determine if we'd be better off using 2.8 instead of 2.7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2166) Investigate use of FindBugs 2.0.1 in JBT/JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2166?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2166. ---------------------------- Resolution: Won't Fix FindBugs 2.0.2 is available in JBDS 6. Won't update JBDS 5 Central. Users who need this can simply uninstall the FindBugs feature from JBDS 5, then update their JBDS from the FindBugs site itself. > Investigate use of FindBugs 2.0.1 in JBT/JBDS Central > ----------------------------------------------------- > > Key: JBDS-2166 > URL: https://issues.jboss.org/browse/JBDS-2166 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central, updatesite, Upstream > Affects Versions: 5.0.0.CR1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 5.0.2.GA > > > We currentl have FindBugs 1.3.9 in Central and JBDS Extras. > But there's a 2.0.1.rc2 out now, as well as 2.0.0. > "Anyone currently using FindBugs 1.3.9 should find FindBugs 2.0 to largely be a drop-in replacement that offers better accuracy and performance." - http://findbugs.sourceforge.net/findbugs2.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2032) Investigate use of TestNG 6.4 in JBDS Extras & JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2032?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2032. ---------------------------- Resolution: Won't Fix TestNG 6.7 is available in JBDS 6. Won't update JBDS 5 Central. > Investigate use of TestNG 6.4 in JBDS Extras & JBoss Central > ------------------------------------------------------------ > > Key: JBDS-2032 > URL: https://issues.jboss.org/browse/JBDS-2032 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central, updatesite, Upstream > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Critical > Fix For: 5.0.2.GA > > > Should we include the latest TestNG 6.4? > http://beust.com/eclipse/ > Currently we include this: > http://download.jboss.org/jbosstools/updates/requirements/testng/6.1.1.20... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1743) JBDS50_0145: [DROPPING--- COMMIT] (Dev) JSLint (Extra)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-1743?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-1743. ---------------------------- Resolution: Won't Fix JSLint is not in JBDS 5.0.x or 6.0.x, closing Won't Fix. > JBDS50_0145: [DROPPING--- COMMIT] (Dev) JSLint (Extra) > ------------------------------------------------------ > > Key: JBDS-1743 > URL: https://issues.jboss.org/browse/JBDS-1743 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Reporter: mark yarborough > Assignee: Len DiMaggio > Fix For: 5.0.2.GA > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2394) CLONE - ESB projects cannot be deployed using Server Add/Remove

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2394: ------------------------------------------- As discussed on emails and elsewhere my suggestion is that esb plugin get fixed so it does not need exact down to the micro version to work. > CLONE - ESB projects cannot be deployed using Server Add/Remove > --------------------------------------------------------------- > > Key: JBDS-2394 > URL: https://issues.jboss.org/browse/JBDS-2394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.GA-SOA > Environment: Fedora, jdk7 > Reporter: Rob Stryker > Assignee: Nick Boldt > Priority: Critical > Fix For: 5.0.2.GA > > Attachments: JBDS2394-add-4.12.patch.txt, JBDS2394.patch-with-5-lines-changed-in-plugin.xml-and-all-feature-and-plugin-manifests-and-poms-upversioned-to-2.3.2.txt, JBDS2394.patch.txt > > > * Create a new server runtime for SOA-P 5.3 > -- Preferences -> Server -> Runtime Environments > * Create a new ESB project with the defaults > * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification. > The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11558) Repositories are missing source feature titles

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11558?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11558: ---------------------------------------- Implementation of tycho-source-feature-plugin was made way smarter and should prevent us from having to copy the build.properties files. SNAPSHOT of Tycho 0.17 will be published next week. > Repositories are missing source feature titles > ---------------------------------------------- > > Key: JBIDE-11558 > URL: https://issues.jboss.org/browse/JBIDE-11558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite, UpStream > Affects Versions: 3.3.0.Beta3 > Environment: jbt33beta3-trunk,L64 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > Attachments: empty-list.png, JBIDE-11558_empty_names.png, missing-names.png, missing-titles.png > > > While updating JBT 3.3. trunk there are missing titles in dialog (see screenshot) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13347) Add deltaspike jars in nexus repository (releases/snapshots)

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-13347: ----------------------------------------- Summary: Add deltaspike jars in nexus repository (releases/snapshots) Key: JBIDE-13347 URL: https://issues.jboss.org/browse/JBIDE-13347 Project: Tools (JBoss Tools) Issue Type: Task Components: UpStream Reporter: Jaroslav Jankovič Assignee: Nick Boldt Now, deltaspike libraries are not in jboss nexus repositories defined in our shared settins.xml (releases/snapshots). They are part of central jboss nexus repo but this one is not used when building swtbot tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13347) Add deltaspike jars into nexus repository (releases/snapshots)

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13347?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič updated JBIDE-13347: -------------------------------------- Summary: Add deltaspike jars into nexus repository (releases/snapshots) (was: Add deltaspike jars in nexus repository (releases/snapshots)) > Add deltaspike jars into nexus repository (releases/snapshots) > -------------------------------------------------------------- > > Key: JBIDE-13347 > URL: https://issues.jboss.org/browse/JBIDE-13347 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: UpStream > Reporter: Jaroslav Jankovič > Assignee: Nick Boldt > > Now, deltaspike libraries are not in jboss nexus repositories defined in our shared settins.xml (releases/snapshots). They are part of central jboss nexus repo but this one is not used when building swtbot tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 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 2013