May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2644) Wrong version & build info in About Dialog

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2644?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-2644. ------------------------------ Resolution: Done Fixed in respin-b Before upgrade: Version: 7.0.0.Beta1 Build id: Beta1-v20130526-0839-B241 Build date: 20130526-0839 After upgrade: Version: 7.0.0.Beta1 Build id: Beta1-v20130529-0631-B257 Build date: 20130529-0631 > Wrong version & build info in About Dialog > ------------------------------------------ > > Key: JBDS-2644 > URL: https://issues.jboss.org/browse/JBDS-2644 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, updatesite > Affects Versions: 7.0.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Denis Golovin > Priority: Critical > Labels: respin-b > Fix For: 7.0.0.Beta1 > > Attachments: JBDS2615_add_update_site.png, JBDS2615_Help_check_for_updates.png, JBDS2615_install_beta1_from_installer.png, JBDS2615__left-Beta1a_com.jboss.jbds.product.plugin_B241_with_expanded_props_installed_from_installer___right-com.jboss.jbds.product.plugin_B241_without_expansion_installed_from_update_site.png, JBDS2644.patch.txt, JBDS2644_svndiff_Beta1x.txt > > > Updating from 7.0.0.Beta1 to 7.0.0.Beta1a via *update site* caused that version, build id, build date variables are not filled in About Dialog: > {code} > JBoss Developer Studio > Version: @product.releaseNumber@ > Build id: @product.buildQualifier@ > Build date: @product.buildTimeStamp@ > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13926) Re-add "Sources" category to aggregator

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13926?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13926. ------------------------------ Resolution: Won't Fix Closing WONTFIX because we undid the solution here. > Re-add "Sources" category to aggregator > --------------------------------------- > > Key: JBIDE-13926 > URL: https://issues.jboss.org/browse/JBIDE-13926 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Labels: respin-b > Fix For: 4.1.0.Beta1 > > > Sources category was made empty to not appear with bad names in p2 UI. However, now we have better labels, we should re-enable it. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-336) NeedInfo: What is the current situation with cheat sheet?

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-336?page=com.atlassian.jira.plug... ] Snjezana Peco commented on TOOLSDOC-336: ---------------------------------------- {quote} There are cheatsheets for the helloworld, login, numberguess, kitchensink quickstarts and Project Examples Tutorial. {quote} Sorry for the confusion. There are cheatsheets for the helloworld, login, numberguess and kitchensink quickstarts. They are placed here: https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/jbossas7-exam... https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/jbossas7-exam... https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/jbossas7-exam... https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/jbossas7-exam... These quickstarts have been moved to JDF and I am not sure why the cheatsheets aren't included in it. Suppose they will be added after fixing JBIDE-14331. {quote} Do the JBDS/JBT quickstarts have cheat sheets? {quote} Not currently. {quote} If yes, where do you find or how do you open the cheat sheets? {quote} You can download the mentioned archives and import them. The helloworld, kitchensink, and numberguess cheatsheet should be opened automatically. The login cheatsheet won't be opened automatically because it is on a separate location: cheatsheet/login.xml. You can open it by right-clicking on login.xml and selecting Show in>Cheat Sheets. You have to enable opening a cheatsheet automatically when importing a project using the Window>Preferences>JBoss Tools>Project Examples preferences page. > NeedInfo: What is the current situation with cheat sheet? > --------------------------------------------------------- > > Key: TOOLSDOC-336 > URL: https://issues.jboss.org/browse/TOOLSDOC-336 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - JBoss Central & JBoss Perspective > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Snjezana Peco > Fix For: 4.1.0 > > > JBDS-2557, JBDS-2558, and JBIDE-14331 are all about cheet sheets. > I get the general gist of cheat sheets from looking at the examples that come with Eclipse - so a tutorial stepping a user through creating a project. > What is the current situation with JBDS/JBT cheat sheets? > If this feature is working, can someone please give me a workflow so that I can have a play? I have no idea how to get started with this. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-338) Review: Devs to review JBoss Central & JBoss Perspective chapter for JBDS 7.0.

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-338?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-338: --------------------------------------- The only additional content that I can think of adding to the JBoss Central section would be to remind readers that JBoss Central is a useful resource to return to over time. It's not just a one-time tool that is only helpful the first time that you start up JBDS. > Review: Devs to review JBoss Central & JBoss Perspective chapter for JBDS 7.0. > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-338 > URL: https://issues.jboss.org/browse/TOOLSDOC-338 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - JBoss Central & JBoss Perspective > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Max Rydahl Andersen > Fix For: 4.1.0 > > Attachments: UserGuide_Central.pdf > > > Please review the content of the JBoss Central/JBoss Perspective chapter from a technical viewpoint: > 1) Are features correctly documented? > 2) Are there any features that are missing? > Screenshots are currently missing and will be added closer to GA. > For ease of tracking by docs, please give feedback as comments in this JIRA. > The chapter is available here as a pdf. The pdf has some layout issues so please disregard these and only comment on the technical content. > Alternatively, the complete user guide to date is also available form: > http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo... > https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/J... (build with: mvn compile) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14663) Source lookup dialog shown twice on maven projects

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14663: --------------------------------------- {quote} but I've never seen any bug report about mismatch sources in m2e. If that was really a problem, source validation could also be implemented directly in m2e. {quote} Open some source file using m2e, close it, remove its source jar from a maven local repository and try to open the file again. {quote} However, the screencast clearly shows maven does its thing in the background, while we ask the user if we should proceed. We have two source lookup mechanisms running concurrently. This is wrong IMO, hence the reason why I wanted to treat maven differently. {quote} {quote} Ok I managed to reproduce the behavior you showed. This is clearly inconsistent IMO. {quote} We have to remove the popup dialog. > Source lookup dialog shown twice on maven projects > -------------------------------------------------- > > Key: JBIDE-14663 > URL: https://issues.jboss.org/browse/JBIDE-14663 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: respin-b > Fix For: 4.1.0.Beta1 > > > Source lookup dialog is shown twice on maven projects : http://screencast.com/t/3yESat96FIw > I think our source lookup should ignore projects with the maven nature, since a m2e's source lookup mechanism is already running in the background. > If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our own stuff -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14616) Remove <relativePath/> to parent pom

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14616?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-14616 at 5/29/13 1:24 PM: ----------------------------------------------------------------- PRs: * https://github.com/jbosstools/jbosstools-openshift/pull/151 * https://github.com/jbosstools/jbosstools-server/pull/82 * https://github.com/jbosstools/jbosstools-integration-tests/pull/277 * https://github.com/jbosstools/jbosstools-central/pull/116 * https://github.com/jbosstools/jbosstools-jst/pull/144 * https://github.com/jbosstools/jbosstools-webservices/pull/38 * https://github.com/jbosstools/jbosstools-hibernate/pull/18 * https://github.com/jbosstools/jbosstools-base/pull/114 * jbosstools-vpe * jbosstools-forge * jbosstools-aerogear * jbosstools-portlet * jbosstools-birt * jbosstools-esb * jbosstools-liverload * jbosstools-javaee * jbosstools-arquillian * jbosstools-xulrunner * jbosstools-bpel * jbosstools-jbpm * jbosstools-gwt * jbosstools-deltacloud * jbosstools-runtime-soa was (Author: mickael_istria): PRs: * https://github.com/jbosstools/jbosstools-openshift/pull/151 * https://github.com/jbosstools/jbosstools-server/pull/82 * https://github.com/jbosstools/jbosstools-integration-tests/pull/277 * https://github.com/jbosstools/jbosstools-central/pull/116 * https://github.com/jbosstools/jbosstools-jst/pull/144 * https://github.com/jbosstools/jbosstools-webservices/pull/38 * > Remove <relativePath/> to parent pom > ------------------------------------ > > Key: JBIDE-14616 > URL: https://issues.jboss.org/browse/JBIDE-14616 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta2 > > > Having a relativePath to parent pom in each component makes that often, on development machine, build resolves parent pom to the relative one (which my not be correctly sync'd) instead of the one which is published on Nexus. > This introduce confusion and may result in different build output between CI and local. Therefore, we should remove the <relativePath/> from all components. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14616) Remove <relativePath/> to parent pom

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14616?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-14616 at 5/29/13 1:24 PM: ----------------------------------------------------------------- Submitted PRs: * https://github.com/jbosstools/jbosstools-openshift/pull/151 * https://github.com/jbosstools/jbosstools-server/pull/82 * https://github.com/jbosstools/jbosstools-integration-tests/pull/277 * https://github.com/jbosstools/jbosstools-central/pull/116 * https://github.com/jbosstools/jbosstools-jst/pull/144 * https://github.com/jbosstools/jbosstools-webservices/pull/38 * https://github.com/jbosstools/jbosstools-hibernate/pull/18 * https://github.com/jbosstools/jbosstools-base/pull/114 PRs to submit: * jbosstools-vpe * jbosstools-forge * jbosstools-aerogear * jbosstools-portlet * jbosstools-birt * jbosstools-esb * jbosstools-liverload * jbosstools-javaee * jbosstools-arquillian * jbosstools-xulrunner * jbosstools-bpel * jbosstools-jbpm * jbosstools-gwt * jbosstools-deltacloud * jbosstools-runtime-soa was (Author: mickael_istria): PRs: * https://github.com/jbosstools/jbosstools-openshift/pull/151 * https://github.com/jbosstools/jbosstools-server/pull/82 * https://github.com/jbosstools/jbosstools-integration-tests/pull/277 * https://github.com/jbosstools/jbosstools-central/pull/116 * https://github.com/jbosstools/jbosstools-jst/pull/144 * https://github.com/jbosstools/jbosstools-webservices/pull/38 * https://github.com/jbosstools/jbosstools-hibernate/pull/18 * https://github.com/jbosstools/jbosstools-base/pull/114 * jbosstools-vpe * jbosstools-forge * jbosstools-aerogear * jbosstools-portlet * jbosstools-birt * jbosstools-esb * jbosstools-liverload * jbosstools-javaee * jbosstools-arquillian * jbosstools-xulrunner * jbosstools-bpel * jbosstools-jbpm * jbosstools-gwt * jbosstools-deltacloud * jbosstools-runtime-soa > Remove <relativePath/> to parent pom > ------------------------------------ > > Key: JBIDE-14616 > URL: https://issues.jboss.org/browse/JBIDE-14616 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta2 > > > Having a relativePath to parent pom in each component makes that often, on development machine, build resolves parent pom to the relative one (which my not be correctly sync'd) instead of the one which is published on Nexus. > This introduce confusion and may result in different build output between CI and local. Therefore, we should remove the <relativePath/> from all components. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14692) JavaEE Web Project (missing space between 'Java' and 'EE')

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-14692: ----------------------------------- Summary: JavaEE Web Project (missing space between 'Java' and 'EE') Key: JBIDE-14692 URL: https://issues.jboss.org/browse/JBIDE-14692 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Reporter: Burr Sutter To be consistent with the File New menu option of "Java EE Web Project". http://screencast.com/t/CCm1HlnQcN I am running the 2nd beta build. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14537: ------------------------------------ https://engineering.redhat.com/rt/Ticket/Display.html?id=202647 ... moved to eng-ops queue on May 21, then nothing else has happened. > BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent > -------------------------------------------------------------------------------- > > Key: JBIDE-14537 > URL: https://issues.jboss.org/browse/JBIDE-14537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Beta1 > Reporter: Yahor Radtsevich > Assignee: Nick Boldt > Fix For: 4.1.0.Beta2 > > > https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple... > org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent > {code} > org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4418) > at org.eclipse.swt.SWT.error(SWT.java:4307) > at org.eclipse.swt.SWT.error(SWT.java:4278) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:103) > at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9) > at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24) > at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38) > at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36) > at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3692) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14616) Remove <relativePath/> to parent pom

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14616?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-14616: ---------------------------------------- PRs: * https://github.com/jbosstools/jbosstools-openshift/pull/151 * https://github.com/jbosstools/jbosstools-server/pull/82 * https://github.com/jbosstools/jbosstools-integration-tests/pull/277 * https://github.com/jbosstools/jbosstools-central/pull/116 * https://github.com/jbosstools/jbosstools-jst/pull/144 * https://github.com/jbosstools/jbosstools-webservices/pull/38 * > Remove <relativePath/> to parent pom > ------------------------------------ > > Key: JBIDE-14616 > URL: https://issues.jboss.org/browse/JBIDE-14616 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta2 > > > Having a relativePath to parent pom in each component makes that often, on development machine, build resolves parent pom to the relative one (which my not be correctly sync'd) instead of the one which is published on Nexus. > This introduce confusion and may result in different build output between CI and local. Therefore, we should remove the <relativePath/> from all components. -- 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

12 years, 10 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 May 2013