[JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18366:
--------------------------------
Fix Version/s: 4.2.x
> Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18366
> URL: https://issues.jboss.org/browse/JBIDE-18366
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> Sometimes, right after start of the IDE, a server fails to start. When this happens, it produces something like this in the server log:
> {code}
> INFO: JBoss MSC version 1.1.5.Final-redhat-1
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ApplicationServerService start
> INFO: JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting
> Sep 17, 2014 11:27:40 AM org.jboss.as.controller.AbstractOperationContext executeStep
> ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
> java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:111)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132)
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:299)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:292)
> at org.jboss.as.server.ServerService.boot(ServerService.java:346)
> at org.jboss.as.server.ServerService.boot(ServerService.java:321)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254)
> at java.lang.Thread.run(Thread.java:695)
> Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
> at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103)
> ... 11 more
> Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:106)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:695)
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ServerService boot
> FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> Unfortunately I don't have a reliable way to reproduce this. It happened to me like 3 times over the last few days.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18277) Early Access features installed with abridged tools
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18277?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18277:
----------------------------------------
[~rhopp] If you want to test it
* Get an instance of JBT or JBDS with the error
* Configure the .ini file to override "jboss.discovery.earlyaccess.list.url", with file:/path/to/file-earlyaccess.properties
* Check happiness of the IDE (take a look at Error log since some silent error are probable).
> Early Access features installed with abridged tools
> ---------------------------------------------------
>
> Key: JBIDE-18277
> URL: https://issues.jboss.org/browse/JBIDE-18277
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Radim Hopp
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.2.0.CR2
>
> Attachments: early-access.png
>
>
> Right after installing JBT into Eclipse (whole Abridged JBoss Tools category) Central is showing that Early access features are installed, namely:
> org.jboss.tools.jst.jsdt.feature (3.6.0.CR1-v20140904-0921-B61) and org.jboss.tools.jst.angularjs.feature (3.6.0.CR1-v20140904-0921-B61)
> In freshly installed JBDS there is this same issue, but only org.jboss.tools.jst.jsdt.feature (3.6.0.CR1-v20140904-0921-B61) is shown in Early Access features.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17619:
---------------------------------------------
can you record a screencast of this ?
> Console for remote server disappears when workspace is switched
> ---------------------------------------------------------------
>
> Key: JBIDE-17619
> URL: https://issues.jboss.org/browse/JBIDE-17619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped.
> The only thing that helped me here was to delete the server and create a new one.
> I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18446) org.jboss.tools.foundation.core.test.ecf.URLTransportUtilTest failure
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18446?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18446:
-------------------------------------
Appears to be test regression from requested change in behavior from JBIDE-18412, where caching for github or unavailable files should be re-loaded if possible.
> org.jboss.tools.foundation.core.test.ecf.URLTransportUtilTest failure
> ---------------------------------------------------------------------
>
> Key: JBIDE-18446
> URL: https://issues.jboss.org/browse/JBIDE-18446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> {code}
> testTimeoutWithoutCancel(org.jboss.tools.foundation.core.test.ecf.URLTransportUtilTest) Time elapsed: 1.557 sectestCaching(org.jboss.tools.foundation.core.test.ecf.URLTransportUtilTest) Time elapsed: 0.524 sec <<< FAILURE!
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.Assert.assertFalse(Assert.java:47)
> at junit.framework.TestCase.assertFalse(TestCase.java:219)
> at org.jboss.tools.foundation.core.test.ecf.URLTransportUtilTest.testCaching(URLTransportUtilTest.java:206)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18448) Create new Visual Editor FAQ
by Konstantin Marmalyukov (JIRA)
Konstantin Marmalyukov created JBIDE-18448:
----------------------------------------------
Summary: Create new Visual Editor FAQ
Key: JBIDE-18448
URL: https://issues.jboss.org/browse/JBIDE-18448
Project: Tools (JBoss Tools)
Issue Type: Task
Components: visual-page-editor-core
Affects Versions: 4.2.0.CR1
Reporter: Konstantin Marmalyukov
Assignee: Konstantin Marmalyukov
Fix For: 4.2.0.CR2
Visual Editor FAQ should be moved to tools.jboss.org
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18242) OpenShift Explorer: Cannot delete multiple domains pressing "Del"
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18242?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-18242:
---------------------------------------
[~adietish] this solution would work in case the domain is removable. Well now we don't have this done, I think (check if domain is removable, if yes, ask to remove it), but it would be nice if deletion via hotkey could work only in case all selected domains are removable. If there would be any shared (either view or edit accessible) domain, it would not be possible to remove it (or ask user whether he/she wants to delete specific domain).
> OpenShift Explorer: Cannot delete multiple domains pressing "Del"
> ------------------------------------------------------------------
>
> Key: JBIDE-18242
> URL: https://issues.jboss.org/browse/JBIDE-18242
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer
> Fix For: 4.3.x
>
> Attachments: Delete2App.png, TwoApplications.png
>
>
> We implement hotkeys for removing a connection/domain/application in JBIDE-15929. We should also allow user to use hot key while having a multiple domains selected.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-16612) NPE after importing ui project from WFK 2.3
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16612?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16612:
---------------------------------------------
we got SR2 yet in Luna so shouldn't wait until Mars based release to follow up in bugzilla.
> NPE after importing ui project from WFK 2.3
> -------------------------------------------
>
> Key: JBIDE-16612
> URL: https://issues.jboss.org/browse/JBIDE-16612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.Alpha2b, Linus 64, Fedora 19, OpenJDK 1.7
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.1.Final, 4.3.x
>
> Attachments: npe-ui-prj-hibernate.png
>
>
> After import there are multiple errors in error log
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.getMappingKey(AbstractJavaPersistentAttribute.java:212)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.AbstractPersistentAttributeValidator.validate(AbstractPersistentAttributeValidator.java:33)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.validateAttribute(AbstractJavaPersistentAttribute.java:646)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.validate(AbstractJavaPersistentAttribute.java:641)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validateAttribute(AbstractJavaPersistentType.java:858)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validateAttributes(AbstractJavaPersistentType.java:852)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validate(AbstractJavaPersistentType.java:838)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.validateJavaManagedType(GenericClassRef.java:444)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.validate(GenericClassRef.java:438)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validateClassRefs(AbstractPersistenceUnit.java:2403)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validate(AbstractPersistenceUnit.java:2285)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.validatePersistenceUnit(GenericPersistence.java:347)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.validate(GenericPersistence.java:303)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.validate(GenericPersistenceXml.java:243)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.validate(GenericContextRoot.java:248)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.validate(AbstractJpaProject.java:1459)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.validate(HibernateJpaProject.java:289)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.getValidationMessages(AbstractJpaProject.java:1447)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildValidationMessages_(InternalJpaProjectManager.java:584)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$BuildValidationMessagesCommand.execute(InternalJpaProjectManager.java:572)
> at org.eclipse.jpt.common.core.internal.utility.command.CommandJobCommandAdapter.execute(CommandJobCommandAdapter.java:50)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.getJpaPlatformUi(MappingStructureItemLabelProviderFactory.java:192)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.getAttributeMappingUiDefinition(MappingStructureItemLabelProviderFactory.java:187)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.transform(MappingStructureItemLabelProviderFactory.java:182)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.transform(MappingStructureItemLabelProviderFactory.java:1)
> at org.eclipse.jpt.common.utility.internal.model.value.TransformationPropertyValueModel.transform(TransformationPropertyValueModel.java:113)
> at org.eclipse.jpt.common.utility.internal.model.value.TransformationPropertyValueModel.engageModel(TransformationPropertyValueModel.java:137)
> at org.eclipse.jpt.common.utility.internal.model.value.AbstractPropertyValueModel.addPropertyChangeListener(AbstractPropertyValueModel.java:83)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractModelItemLabelProvider.<init>(AbstractModelItemLabelProvider.java:65)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemExtendedLabelProvider.<init>(ModelItemExtendedLabelProvider.java:48)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory.buildPersistentAttributeProvider(MappingStructureItemLabelProviderFactory.java:143)
> at org.eclipse.jpt.jpa.ui.internal.platform.generic.GenericNavigatorItemLabelProviderFactory.buildPersistentAttributeProvider(GenericNavigatorItemLabelProviderFactory.java:150)
> at org.eclipse.jpt.jpa.ui.internal.platform.generic.GenericNavigatorItemLabelProviderFactory.buildProvider(GenericNavigatorItemLabelProviderFactory.java:78)
> at org.eclipse.jpt.jpa.ui.internal.navigator.JpaNavigatorItemLabelProviderFactory.buildProvider(JpaNavigatorItemLabelProviderFactory.java:37)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addLabelProvider(AbstractItemStructuredStateProviderManager.java:245)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.add(AbstractItemStructuredStateProviderManager.java:241)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:118)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:231)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.childrenChanged_(ItemTreeStateProviderManager.java:110)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.childrenChanged(ItemTreeStateProviderManager.java:105)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemTreeContentProvider.notifyManager(ModelItemTreeContentProvider.java:63)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider.childrenAdded_(ModelItemContentProvider.java:119)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider.childrenAdded(ModelItemContentProvider.java:113)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider$ChildrenListener.itemsAdded(ModelItemContentProvider.java:92)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTCollectionChangeListenerWrapper.forward(SWTCollectionChangeListenerWrapper.java:51)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTCollectionChangeListenerWrapper.forward(SWTCollectionChangeListenerWrapper.java:1)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTListenerWrapperDelegate.forwardEvents(SWTListenerWrapperDelegate.java:92)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTListenerWrapperDelegate$ForwardEventsRunnable.run(SWTListenerWrapperDelegate.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3746)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3394)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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 was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18447) Both of jbosstools-discovery publish same version of Central TPs
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18447?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18447:
-----------------------------------
Fix Version/s: 4.3.0.Alpha1
> Both of jbosstools-discovery publish same version of Central TPs
> ----------------------------------------------------------------
>
> Key: JBIDE-18447
> URL: https://issues.jboss.org/browse/JBIDE-18447
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery, target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Mickael Istria
> Fix For: 4.3.0.Alpha1
>
>
> jbosstools-discovery plugin is branched according to JBoss Tools train. However, it contains TPs that are versioned according to Eclipse release train.
> Because of that, we currently have the same version of the Discovery target definitions on both master and jbosstools-4.2.x branch. That leads to some uncertainity about which branch/job is going to publish the Central site.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months