[JBoss JIRA] (JBTIS-889) Cannot resolve test dependencies
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-889:
---------------------------------------
Summary: Cannot resolve test dependencies
Key: JBTIS-889
URL: https://issues.jboss.org/browse/JBTIS-889
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE
Affects Versions: 4.4.0.Alpha1
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.4.0.Alpha1
Some tests failed due to issues with dependency resolution such as
{code}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.bpmn2.ui.bot.test 4.4.0.qualifier
[ERROR] Missing requirement: org.jboss.tools.bpmn2.ui.bot.test 4.4.0.qualifier requires 'bundle org.jboss.tools.bpmn2.reddeer 4.3.0' but it could not be found
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23132) When ftl file is opened in devstudio/eclipse it does not get cursor/focus
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23132?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-23132 at 9/14/16 4:38 AM:
----------------------------------------------------------------
When I click into editor, cursor gets there or if I do double click on the file again. I tested this on windows 10 and everything is alright, problem seems to be on Fedora 24 only (three other machines with F24 confirmed the same situation). Context assistant is called from reddeer API, when running integration tests, but this should not be considered as a cause, it is more a consequence. See attachment above, please.
was (Author: odockal):
When I click into editor, cursor gets there or if I do double click on the file again. I tested this on windows 10 and everything is alright, problem seems to be on Fedora 24 only (three other machines with F24 confirmed the same situation). Context assistant is called from reddeer API, when running integration tests, but this should not be considered as a cause, it is more a consequence.
> When ftl file is opened in devstudio/eclipse it does not get cursor/focus
> -------------------------------------------------------------------------
>
> Key: JBIDE-23132
> URL: https://issues.jboss.org/browse/JBIDE-23132
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.4.1.Final
> Environment: Fedora 24, x86_64, devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160902-1725-B43
> Eclipse neon 1, RC1
> Reporter: Ondrej Dockal
> Assignee: Daniel Dekany
> Attachments: freemarkerFileFocus.ogv
>
>
> When I open a freemarker file (.ftl) in devstudio (project/package explorer), new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23132) When ftl file is opened in devstudio/eclipse it does not get cursor/focus
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23132?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-23132:
----------------------------------
Attachment: freemarkerFileFocus.ogv
> When ftl file is opened in devstudio/eclipse it does not get cursor/focus
> -------------------------------------------------------------------------
>
> Key: JBIDE-23132
> URL: https://issues.jboss.org/browse/JBIDE-23132
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.4.1.Final
> Environment: Fedora 24, x86_64, devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160902-1725-B43
> Eclipse neon 1, RC1
> Reporter: Ondrej Dockal
> Assignee: Daniel Dekany
> Attachments: freemarkerFileFocus.ogv
>
>
> When I open a freemarker file (.ftl) in devstudio (project/package explorer), new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23132) When ftl file is opened in devstudio/eclipse it does not get cursor/focus
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23132?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-23132:
---------------------------------------
When I click into editor, cursor gets there or if I do double click on the file again. I tested this on windows 10 and everything is alright, problem seems to be on Fedora 24 only (three other machines with F24 confirmed the same situation). Context assistant is called from reddeer API, when running integration tests, but this should not be considered as a cause, it is more a consequence.
> When ftl file is opened in devstudio/eclipse it does not get cursor/focus
> -------------------------------------------------------------------------
>
> Key: JBIDE-23132
> URL: https://issues.jboss.org/browse/JBIDE-23132
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.4.1.Final
> Environment: Fedora 24, x86_64, devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160902-1725-B43
> Eclipse neon 1, RC1
> Reporter: Ondrej Dockal
> Assignee: Daniel Dekany
>
> When I open a freemarker file (.ftl) in devstudio (project/package explorer), new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23011) Docker Explorer broken on Windows
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23011?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-23011.
---------------------------------
Docker Tooling view is working without issues.
Verified in:
Red Hat JBoss Developer Studio
Version: 10.1.0.GA
Build id: GA-v20160902-1725-B43
Build date: 20160902-1725
> Docker Explorer broken on Windows
> ---------------------------------
>
> Key: JBIDE-23011
> URL: https://issues.jboss.org/browse/JBIDE-23011
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.4.1.Final
>
> Attachments: docker-explorer.jpg, jbide23011.png, jbide23011_2.png
>
>
> [reply] [−] Description Martin Malina CLA Friend 2016-08-16 08:51:31 EDT
> Created attachment 263612 [details]
> Broken Docker Explorer view
> I just installed a brand new installation of Red Hat JBoss Developer Studio 10.1.0.AM3 which contains Docker Tooling 2.1.0.201608101805 on Windows and when I open Docker Explorer, it contains a red X and "Failed to create the part's controls". Also, there is a button that says Details > >.
> There is this NPE in the error log view:
> {code}
> java.lang.NullPointerException
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:63)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.getInitialInput(DockerExplorerView.java:93)
> at org.eclipse.ui.navigator.CommonNavigator.createPartControl(CommonNavigator.java:206)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createConnectionsPane(DockerExplorerView.java:195)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createPartControl(DockerExplorerView.java:147)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:143)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:341)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:536)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:520)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:70)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:757)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:728)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:722)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:706)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1317)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:72)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4813)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:94)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:617)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:581)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:770)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:744)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:677)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1205)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1283)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1274)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4316)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4312)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4292)
> at org.eclipse.ui.internal.quickaccess.ViewElement.execute(ViewElement.java:77)
> at org.eclipse.ui.internal.quickaccess.SearchField$2.handleElementSelected(SearchField.java:200)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:507)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:497)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:542)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:168)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130)
> at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1789)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126)
> at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547)
> at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4910)
> at org.eclipse.swt.widgets.Text.WM_CHAR(Text.java:2722)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4791)
> at org.eclipse.swt.widgets.Text.windowProc(Text.java:2704)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5102)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2552)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3814)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
> This is a tracking issue for this upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=499745
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3627:
--------------------------------
Issue Type: Epic (was: Enhancement)
Target Release: 10.2.0.GA (was: 10.1.0.GA)
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM1
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23161) Update bundled and website schema with wf10.1 schema
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23161?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23161:
--------------------------------
Description:
WildFly 10.1 is released, so two tasks need to be done.
1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
{code}
# Check out repos and DL new app server
wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
unzip wildfly-10.1.0.Final.zip
git clone git@github.com:robstryker/jboss.org.schema.git
git clone git@github.com:jbosstools/jbosstools-server.git
tmpdir=`pwd`
echo $tmpdir
# Build the catalog plugin
cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
mvn clean verify -DskipTests
cd target/classes/
echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
# Copy new or modified schema into the jboss.org.schema repo
java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
"$tmpdir/wildfly-10.1.0.Final/docs/schema" \
"$tmpdir/jboss.org.schema/schema_htdocs" jbossas
# Copy new or modified schema into the catalog schema folder
java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
"$tmpdir/wildfly-10.1.0.Final/docs/schema" \
"$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
# Commit the changes to jboss.org.schema repo
cd $tmpdir/jboss.org.schema/schema_htdocs
git checkout -b wildfly101schema
git add -A
git commit -a -m "Update schema from WildFly 10.1.0 Final"
# TODO ACTION REQUIRED, push to your own repo and initiate pull request
cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
git checkout -b wildfly101schema
# Update plugin.xml for catalog
java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
-Doutput.mode=generateCatalog\
org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
git add -A
git commit -a -m "Update schema from WildFly 10.1.0 Final"
#TODO ACTION REQUIRED, push to your own repo and initiate a PR
# run a build to verify it works
cd $tmpdir/jbosstools-server
mvn clean install -DskipTests
# Now run CatalogValidationTest manually
{code}
was:
WildFly 10.1 is released, so two tasks need to be done.
1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
{code}
# Check out repos and DL new app server
wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
unzip wildfly-10.1.0.Final.zip
git clone https://github.com/robstryker/jboss.org.schema
git clone https://github.com/jbosstools/jbosstools-server
tmpdir=`pwd`
echo $tmpdir
# Build the catalog plugin
cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
mvn clean verify -DskipTests
cd target/classes/
echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
# Copy new or modified schema into the jboss.org.schema repo
java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
"$tmpdir/wildfly-10.1.0.Final/docs/schema" \
"$tmpdir/jboss.org.schema/schema_htdocs" jbossas
# Copy new or modified schema into the catalog schema folder
java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
"$tmpdir/wildfly-10.1.0.Final/docs/schema" \
"$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
# Commit the changes to jboss.org.schema repo
cd $tmpdir/jboss.org.schema/schema_htdocs
git checkout -b wildfly101schema
git add -A
git commit -a -m "Update schema from WildFly 10.1.0 Final"
# TODO ACTION REQUIRED, push to your own repo and initiate pull request
cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
git checkout -b wildfly101schema
# Update plugin.xml for catalog
java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
-Doutput.mode=generateCatalog\
org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
git add -A
git commit -a -m "Update schema from WildFly 10.1.0 Final"
#TODO ACTION REQUIRED, push to your own repo and initiate a PR
# run a build to verify it works
cd $tmpdir/jbosstools-server
mvn clean install -DskipTests
# Now run CatalogValidationTest manually
{code}
> Update bundled and website schema with wf10.1 schema
> ----------------------------------------------------
>
> Key: JBIDE-23161
> URL: https://issues.jboss.org/browse/JBIDE-23161
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.4.2.AM1
> Reporter: Rob Stryker
>
> WildFly 10.1 is released, so two tasks need to be done.
> 1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
> 2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
> {code}
> # Check out repos and DL new app server
> wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
> unzip wildfly-10.1.0.Final.zip
> git clone git@github.com:robstryker/jboss.org.schema.git
> git clone git@github.com:jbosstools/jbosstools-server.git
> tmpdir=`pwd`
> echo $tmpdir
> # Build the catalog plugin
> cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
> mvn clean verify -DskipTests
> cd target/classes/
> echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
> # Copy new or modified schema into the jboss.org.schema repo
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jboss.org.schema/schema_htdocs" jbossas
> # Copy new or modified schema into the catalog schema folder
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
> # Commit the changes to jboss.org.schema repo
> cd $tmpdir/jboss.org.schema/schema_htdocs
> git checkout -b wildfly101schema
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> # TODO ACTION REQUIRED, push to your own repo and initiate pull request
> cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
> git checkout -b wildfly101schema
> # Update plugin.xml for catalog
> java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
> -Doutput.mode=generateCatalog\
> org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> #TODO ACTION REQUIRED, push to your own repo and initiate a PR
>
> # run a build to verify it works
> cd $tmpdir/jbosstools-server
> mvn clean install -DskipTests
> # Now run CatalogValidationTest manually
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23161) Update bundled and website schema with wf10.1 schema
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23161?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23161:
--------------------------------
Description:
WildFly 10.1 is released, so two tasks need to be done.
1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
{code}
# Check out repos and DL new app server
wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
unzip wildfly-10.1.0.Final.zip
git clone https://github.com/robstryker/jboss.org.schema
git clone https://github.com/jbosstools/jbosstools-server
tmpdir=`pwd`
echo $tmpdir
# Build the catalog plugin
cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
mvn clean verify -DskipTests
cd target/classes/
echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
# Copy new or modified schema into the jboss.org.schema repo
java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
"$tmpdir/wildfly-10.1.0.Final/docs/schema" \
"$tmpdir/jboss.org.schema/schema_htdocs" jbossas
# Copy new or modified schema into the catalog schema folder
java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
"$tmpdir/wildfly-10.1.0.Final/docs/schema" \
"$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
# Commit the changes to jboss.org.schema repo
cd $tmpdir/jboss.org.schema/schema_htdocs
git checkout -b wildfly101schema
git add -A
git commit -a -m "Update schema from WildFly 10.1.0 Final"
# TODO ACTION REQUIRED, push to your own repo and initiate pull request
cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
git checkout -b wildfly101schema
# Update plugin.xml for catalog
java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
-Doutput.mode=generateCatalog\
org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
git add -A
git commit -a -m "Update schema from WildFly 10.1.0 Final"
#TODO ACTION REQUIRED, push to your own repo and initiate a PR
# run a build to verify it works
cd $tmpdir/jbosstools-server
mvn clean install -DskipTests
# Now run CatalogValidationTest manually
{code}
was:
WildFly 10.1 is released, so two tasks need to be done.
1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
{code}
# Check out repos and DL new app server
wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
unzip wildfly-10.1.0.Final.zip
git clone https://github.com/robstryker/jboss.org.schema
git clone https://github.com/jbosstools/jbosstools-server
tmpdir=`pwd`
echo $tmpdir
# Build the catalog plugin
cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
mvn clean verify -DskipTests
cd target/classes/
echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
# Copy new or modified schema into the jboss.org.schema repo
java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
"$tmpdir/wildfly-10.1.0.Final/docs/schema" \
"$tmpdir/jboss.org.schema/schema_htdocs" jbossas
# Copy new or modified schema into the catalog schema folder
java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
"$tmpdir/wildfly-10.1.0.Final/docs/schema" \
"$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
# Commit the changes to jboss.org.schema repo
cd $tmpdir/jboss.org.schema/schema_htdocs
git checkout -b wildfly101schema
git add -A
git commit -a -m "Update schema from WildFly 10.1.0 Final"
# TODO ACTION REQUIRED, push to your own repo and initiate pull request
cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
git checkout -b wildfly101schema
# Update plugin.xml for catalog
java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
-Doutput.mode=generateCatalog\
org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
git add -A
git commit -a -m "Update schema from WildFly 10.1.0 Final"
# run a build to verify it works
cd $tmpdir/jbosstools-server
mvn clean install -DskipTests
# Now run CatalogValidationTest manually
{code}
> Update bundled and website schema with wf10.1 schema
> ----------------------------------------------------
>
> Key: JBIDE-23161
> URL: https://issues.jboss.org/browse/JBIDE-23161
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.4.2.AM1
> Reporter: Rob Stryker
>
> WildFly 10.1 is released, so two tasks need to be done.
> 1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
> 2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
> {code}
> # Check out repos and DL new app server
> wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
> unzip wildfly-10.1.0.Final.zip
> git clone https://github.com/robstryker/jboss.org.schema
> git clone https://github.com/jbosstools/jbosstools-server
> tmpdir=`pwd`
> echo $tmpdir
> # Build the catalog plugin
> cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
> mvn clean verify -DskipTests
> cd target/classes/
> echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
> # Copy new or modified schema into the jboss.org.schema repo
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jboss.org.schema/schema_htdocs" jbossas
> # Copy new or modified schema into the catalog schema folder
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
> # Commit the changes to jboss.org.schema repo
> cd $tmpdir/jboss.org.schema/schema_htdocs
> git checkout -b wildfly101schema
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> # TODO ACTION REQUIRED, push to your own repo and initiate pull request
> cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
> git checkout -b wildfly101schema
> # Update plugin.xml for catalog
> java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
> -Doutput.mode=generateCatalog\
> org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> #TODO ACTION REQUIRED, push to your own repo and initiate a PR
>
> # run a build to verify it works
> cd $tmpdir/jbosstools-server
> mvn clean install -DskipTests
> # Now run CatalogValidationTest manually
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months