[JBoss JIRA] (JBIDE-15918) Could Jenkins perform tagging of its own repo?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15918?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15918:
---------------------------------------------
My thinking on this is to keep it simple is that we for every build should simply put a tag in a separate repository, lets say owned by a jbosstools
user.
Then use a script or probably just a jenkins plugin to push a tag for each build and you can then as a developer go check which exact commits was used for a build and decide to move them over.
Jenkins has a user named https://github.com/JBossJenkins which should be possible to use to maintain such a separate "tagging" repo.
As an experiment I've created a user named "jbosstoolsci" (jbosstools is already owned by our org) and have it forked some repos (https://github.com/jbosstoolsci/ and JBossJenkins is a collaborator on these repos.
Lets see if we can get jenkins to tag those.
> Could Jenkins perform tagging of its own repo?
> ----------------------------------------------
>
> Key: JBIDE-15918
> URL: https://issues.jboss.org/browse/JBIDE-15918
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Priority: Minor
>
> [~maxandersen] said:
> {quote}
> Project leads, please tag your projects!
> {code}
> co jbosstools-4.1.1.Beta1x
> git tag jbosstools-4.1.1.Beta1
> git push origin jbosstools-4.1.1.Beta1
> {code}
> {quote}
> Then asked:
> {quote}
> Really would be nice if jenkins could just make such tags in its own repository and we could move the exact commit over from the "build" repository to the master repository.
> {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
12 years, 6 months
[JBoss JIRA] (JBIDE-15918) Could Jenkins perform tagging of its own repo?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15918?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15918:
----------------------------------------
How would a job know it is the jbosstools-4.1.1.Beta1 tag? There is nothing in pom files nor job config that can tell that. What would be the rule to have jenkins tagging? If it is changing a system property or something like that which require a human action, then I don't see the benefit of a manual action to command something upon a manual action to do something.
However, I think that Jenkins could create a tag for each build. Those tags would help to track the commit (1) <-> build (N) association easily. It would be useful.
> Could Jenkins perform tagging of its own repo?
> ----------------------------------------------
>
> Key: JBIDE-15918
> URL: https://issues.jboss.org/browse/JBIDE-15918
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Priority: Minor
>
> [~maxandersen] said:
> {quote}
> Project leads, please tag your projects!
> {code}
> co jbosstools-4.1.1.Beta1x
> git tag jbosstools-4.1.1.Beta1
> git push origin jbosstools-4.1.1.Beta1
> {code}
> {quote}
> Then asked:
> {quote}
> Really would be nice if jenkins could just make such tags in its own repository and we could move the exact commit over from the "build" repository to the master repository.
> {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
12 years, 6 months
[JBoss JIRA] (JBDS-2577) JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2577?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2577:
-----------------------------------
m2e-wro4j is available in both m2e's discovery catalog and Eclipse MPC. There's no conflict with JBoss Central (except all versions need to be aligned)
I think I'd prefer to make it available in JBoss Central first (for 7.x), then if proven stable enough, we can consider adding it to 8.x by default.
But I don't have a strong feeling one way or the other.
> JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs
> -----------------------------------------------------------------------
>
> Key: JBDS-2577
> URL: https://issues.jboss.org/browse/JBDS-2577
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Jiri Pallich
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 7.1.0.CR1
>
>
> Support non-minified JS libs for Dev, swap in minified JS libs for production (wro4j - maven integration?).
> Examples of JS libs: jQuery, jQuery Mobile
--
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, 6 months
[JBoss JIRA] (JBIDE-15465) Deprecate or remove generation of *-directory.xml from repository-utils:generate-repository-facade as no longer needed
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15465?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-15465:
-----------------------------------
Fix Version/s: 4.2.0.Alpha1
> Deprecate or remove generation of *-directory.xml from repository-utils:generate-repository-facade as no longer needed
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15465
> URL: https://issues.jboss.org/browse/JBIDE-15465
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, discovery
> Affects Versions: 4.1.1.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha1
>
>
> For JBT 4.1/4.1.1 and JBDS 7.0/7.1, generation of discovery.xml is driven by a separate process, rather than part of the creation of update sites' index.html facades.
> So, for the next release of repository-utils, we should consider deprecating or removing this functionality as it's no longer used. At the very least, we could remove the logged warning:
> {code}
> [WARNING] No org.jboss.tools.central.discovery plugin in repo. Skip generation of 'jbosstools-directory.xml'
> {code}
> Need to ensure that JBT 4.0 / JBDS 6.0 builds (and earlier) use a specific (older) version of the mojo, such as 0.16.0.CR2, where this functionality is still required.
--
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, 6 months
[JBoss JIRA] (JBTIS-208) Create fuse bot test for managing fuse server
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-208?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-208:
-----------------------------------------
Try to use to use Red Deer configuration settings instead of swtbot.properties
> Create fuse bot test for managing fuse server
> ---------------------------------------------
>
> Key: JBTIS-208
> URL: https://issues.jboss.org/browse/JBTIS-208
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: QE
> Affects Versions: 4.1.3
> Reporter: Andrej Podhradsky
> Assignee: Tomáš Sedmík
> Fix For: 4.1.3
>
>
> Setup:
> 1. creation of a fuse server definition (test each of the available)
> 2. with and without download of a runtime
> 3. starting / stopping of a fuse server
> 4. delete fuse server definition / runtimes
--
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, 6 months
[JBoss JIRA] (JBTIS-208) Create fuse bot test for managing fuse server
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-208?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-208:
-----------------------------------------
Take into account that after starting the server, a non-swt window can be displayed for confirming new ip address.
> Create fuse bot test for managing fuse server
> ---------------------------------------------
>
> Key: JBTIS-208
> URL: https://issues.jboss.org/browse/JBTIS-208
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: QE
> Affects Versions: 4.1.3
> Reporter: Andrej Podhradsky
> Assignee: Tomáš Sedmík
> Fix For: 4.1.3
>
>
> Setup:
> 1. creation of a fuse server definition (test each of the available)
> 2. with and without download of a runtime
> 3. starting / stopping of a fuse server
> 4. delete fuse server definition / runtimes
--
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, 6 months
[JBoss JIRA] (JBIDE-14849) Exceptions when working with font-family in CSS Dialog
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14849?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-14849.
-------------------------------
Verified with JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Exceptions when working with font-family in CSS Dialog
> ------------------------------------------------------
>
> Key: JBIDE-14849
> URL: https://issues.jboss.org/browse/JBIDE-14849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.1.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Vlado Pakan
> Fix For: 4.1.1.Beta1
>
>
> I have a copy of jquery.mobile-1.3.0.css in one of my projects.
> I opened it with the default editor and then opened CSS Dialog.
> The I got the following exceptions it the log:
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 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)
> Caused by: java.lang.NullPointerException
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocumentRegion.getText(BasicStructuredDocumentRegion.java:304)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.getText(CSSDeclarationItemParser.java:1073)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.createPrimitiveValue(CSSDeclarationItemParser.java:364)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:1014)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:964)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueTextCore(CSSStyleDeclItemImpl.java:260)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueText(CSSStyleDeclItemImpl.java:234)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclarationImpl.setProperty(CSSStyleDeclarationImpl.java:267)
> at org.jboss.tools.jst.css.dialog.common.CSSModel.updateCSSStyle(CSSModel.java:297)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.handleSelectorSwitched(CSSClassDialog.java:250)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog$1.modifyText(CSSClassDialog.java:152)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Combo.select(Combo.java:1726)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.updateControlPane(CSSClassDialog.java:377)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.createContents(CSSClassDialog.java:99)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.jst.css.dialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:70)
> at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> ... 37 more
> {code}
> Dialog is not opened.
> If you try to open it again you will get an empty error message in the log:
> {code}
> !ENTRY org.jboss.tools.jst.css 4 0 2013-06-12 14:27:10.147
> !MESSAGE
> {code}
> The dialog is opened.
> Click on OK and get another exception:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.jst.css.dialog.common.CSSModel.save(CSSModel.java:260)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.save(CSSClassDialog.java:295)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.close(CSSClassDialog.java:315)
> at org.eclipse.jface.dialogs.Dialog.okPressed(Dialog.java:955)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.jboss.tools.jst.css.dialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:70)
> at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 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}
> The dialog is not closed.
> Didn't try another CSS file.
--
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, 6 months