February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13451) Too many "xmlns:"-proposals when requesting content assist for tag attribute name

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13451?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-13451: ----------------------------------------- Wrong extra non-iconified 'xmnls'-attribute proposals are removed from the <ui:component />, <ui:composition />, <ui:decorate /> and <ui:fragment /> tags. JUnit Test org.jboss.tools.jst.jsp.test.ca.JstCAOnCustomPrefixesTest is updated due to valudate the issue. > Too many "xmlns:"-proposals when requesting content assist for tag attribute name > --------------------------------------------------------------------------------- > > Key: JBIDE-13451 > URL: https://issues.jboss.org/browse/JBIDE-13451 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Alpha1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.0.Alpha1 > > > When requesting the Content Assist for a tag attribute name there are too many "xmlns:" proposals in the proposal list. > Need to hide these proposals for all the tags other that a page root element by showing those namespace proposals only if the entered text matches the "xmlns:" string. -- 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-13428) Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT/JBDS update sites, installers

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13428?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13428: ------------------------------------ Do these need to change too? {code} ** [2] ./maven/plugins/org.jboss.tools.maven.portlet/src/org/jboss/tools/maven/portlet/Messages.java ** 19- */ 20-public class Messages extends NLS { 21: private static final String BUNDLE_NAME = "org.jboss.tools.maven.jsf.messages"; //$NON-NLS-1$ 22- public static String PortletProjectConfigurator_The_project_does_not_contain_the_Web_Module_facet; 23- static { ** [3] ./maven/plugins/org.jboss.tools.maven.ui/src/org/jboss/tools/maven/ui/preferences/ConfiguratorPreferencePage.java ** 43- 44- 45: private static final String ORG_JBOSS_TOOLS_MAVEN_JSF = "org.jboss.tools.maven.jsf"; //$NON-NLS-1$ 46- private static final String ORG_JBOSS_TOOLS_MAVEN_PORTLET = "org.jboss.tools.maven.portlet"; //$NON-NLS-1$ 47- private static final String ORG_JBOSS_TOOLS_MAVEN_CDI = "org.jboss.tools.maven.cdi"; //$NON-NLS-1$ 48- private static final String ORG_JBOSS_TOOLS_MAVEN_HIBERNATE = "org.jboss.tools.maven.hibernate"; //$NON-NLS-1$ 49- private static final String ORG_JBOSS_TOOLS_MAVEN_SEAM = "org.jboss.tools.maven.seam"; //$NON-NLS-1$ 50: private static final String ORG_JBOSS_TOOLS_MAVEN_JAXRS = "org.jboss.tools.maven.jaxrs"; //$NON-NLS-1$ 51: private static final String ORG_JBOSS_TOOLS_MAVEN_JPA = "org.jboss.tools.maven.jpa"; //$NON-NLS-1$ 52- private static final String ORG_JBOSS_TOOLS_MAVEN_GWT = "org.jboss.tools.maven.gwt"; //$NON-NLS-1$ {code} > Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT/JBDS update sites, installers > --------------------------------------------------------------------------------------- > > Key: JBIDE-13428 > URL: https://issues.jboss.org/browse/JBIDE-13428 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1, 4.0.x > > > The JBoss Maven JPA, JSF, JAX-RS being migrated over m2e-wtp, the plugins and features have been removed from the git repo. > We need to make sure the the JBT/JBDS update sites, installers are curated as well. > *Blocks 4.1.0.Alpha1, but MIGHT be able to wait until Kepler M5 bits are out (Feb 4-6).* -- 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-13459) 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13459?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13459: ------------------------------------ Nice work! 63 tests fixed, 1 to go: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--server/167/testReport/org.jboss.tools.as.test.core.launch/MockArgsTests/initializationError/} Failed org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError (from org.jboss.tools.as.test.core.ASToolsTestSuite) Failing for the past 8 builds (Since #160 ) Took 3 ms. add description Error Message No runnable methods Stacktrace java.lang.Exception: No runnable methods at org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMethods(BlockJUnit4ClassRunner.java:166) at org.junit.runners.BlockJUnit4ClassRunner.collectInitializationErrors(BlockJUnit4ClassRunner.java:102) at org.junit.runners.ParentRunner.validate(ParentRunner.java:344) at org.junit.runners.ParentRunner.<init>(ParentRunner.java:74) at org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:55) at org.junit.runners.Parameterized$TestClassRunnerForParameters.<init>(Parameterized.java:79) at org.junit.runners.Parameterized.<init>(Parameterized.java:137) at sun.reflect.GeneratedConstructorAccessor20.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) {code} > 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13459 > URL: https://issues.jboss.org/browse/JBIDE-13459 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha1 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--server/165/testReport/} > Failing for 6 builds (age = 6): > Test Name Duration Age > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[60] 3.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[61] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[62] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[63] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[64] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[65] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[66] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[67] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[68] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[69] 2.9 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[70] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[71] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[72] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[73] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[74] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[75] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[76] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[77] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[78] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[79] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[80] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[81] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[82] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[83] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[84] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[85] 2.9 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[86] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[87] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[88] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[89] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[60] 3.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[61] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[62] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[63] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[64] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[65] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[66] 4.1 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[67] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[68] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[69] 4.7 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[70] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[71] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[72] 4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[73] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[74] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[75] 4.1 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[76] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[77] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[78] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[79] 4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[80] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[81] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[82] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[83] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[84] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[85] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[86] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[87] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[88] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[89] 3.7 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.XPathModelTest.serverTestImpl[0] 15 ms 6 > >>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 2 ms 6 > >>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 1 ms 6 > >>> org.jboss.tools.as.test.core.classpath.EJB3SupportVerifierTest.testEJB30Support[11] 20 ms 6 > {code} -- 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-13465) Update birt feature version for Kepler

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13465?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-13465. ----------------------------------- Resolution: Done > Update birt feature version for Kepler > -------------------------------------- > > Key: JBIDE-13465 > URL: https://issues.jboss.org/browse/JBIDE-13465 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: birt > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha1 > > -- 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-13464) Update portlet feature version for Kepler

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13464?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-13464. ----------------------------------- Resolution: Done > Update portlet feature version for Kepler > ----------------------------------------- > > Key: JBIDE-13464 > URL: https://issues.jboss.org/browse/JBIDE-13464 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Portal/GateIn > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha1 > > -- 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-13465) Update birt feature version for Kepler

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13465: ------------------------------------- Summary: Update birt feature version for Kepler Key: JBIDE-13465 URL: https://issues.jboss.org/browse/JBIDE-13465 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: birt Affects Versions: 4.1.0.Alpha1 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 4.1.0.Alpha1 -- 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-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-13408: ---------------------------------- Assignee: Mickael Istria (was: Max Rydahl Andersen) > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {quote} -- 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-13464) Update portlet feature version for Kepler

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13464: ------------------------------------- Summary: Update portlet feature version for Kepler Key: JBIDE-13464 URL: https://issues.jboss.org/browse/JBIDE-13464 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Portal/GateIn Affects Versions: 4.1.0.Alpha1 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 4.1.0.Alpha1 -- 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-13282) JBT Wiki & build docs need updating

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13282: ------------------------------- Description: These docs need updates / new screenshots: https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 http://download.jboss.org/jbosstools/builds/cascade/swimlanes.html (JavaEE (maven) depends on Hibernate) was: These docs need updates / new screenshots: https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 > JBT Wiki & build docs need updating > ----------------------------------- > > Key: JBIDE-13282 > URL: https://issues.jboss.org/browse/JBIDE-13282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > > These docs need updates / new screenshots: > https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment > https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 > http://download.jboss.org/jbosstools/builds/cascade/swimlanes.html (JavaEE (maven) depends on Hibernate) -- 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-13282) JBT Wiki build docs need updating

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13282: ------------------------------- Summary: JBT Wiki build docs need updating (was: https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 needs updating) > JBT Wiki build docs need updating > --------------------------------- > > Key: JBIDE-13282 > URL: https://issues.jboss.org/browse/JBIDE-13282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > > https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 needs updating -- 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 February 2013