[JBoss JIRA] (JBDS-2805) move Central TP site declaration from JBT parent pom to JBDS installer pom
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2805?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2805:
--------------------------------------
I didn't try to build it, but having a look at the goal and implementation make me think that this change is definitely worth a +1.
Putting things where they belong is always a good thing.
> move Central TP site declaration from JBT parent pom to JBDS installer pom
> --------------------------------------------------------------------------
>
> Key: JBDS-2805
> URL: https://issues.jboss.org/browse/JBDS-2805
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, build, installer
> Affects Versions: 7.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.0.0.Alpha1
>
>
> Fairly sure that the only place this variable
> {code:title=https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L78}
> <jboss-central-target-platform-site>http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kep...</jboss-central-target-platform-site>
> {code}
> is used is in the JBDS installer pom:
> {code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/pom.xml#L74}
> <repository>
> <!-- JBDS-2623 use Central TP instead of TestNG mirror -->
> <id>jboss-central-target-platform-site</id>
> <url>${jboss-central-target-platform-site}</url>
> <layout>p2</layout>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> <releases>
> <enabled>true</enabled>
> </releases>
> </repository>
> {code}
> So why don't we just move it into JBDS entirely, instead of declaring it in JBT parent pom?
--
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, 5 months
[JBoss JIRA] (JBIDE-16088) Compilation error when building WebServices against Luna TP
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16088?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-16088:
---------------------------------------
It's something that is specified by us:
{code}
org.apache.ant;bundle-version="[1.8.2,1.9.0)",
{code}
> Compilation error when building WebServices against Luna TP
> -----------------------------------------------------------
>
> Key: JBIDE-16088
> URL: https://issues.jboss.org/browse/JBIDE-16088
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, webservices
> Reporter: Xavier Coulon
>
> I have the following dependency resolution problem when building the Web Services component against the Luna TP:
> {code}
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.6.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Cannot complete the request. Generating details.
> [INFO] Cannot complete the request. Generating details.
> [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.ws.creation.core 1.6.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.ws.creation.core 1.6.0.qualifier requires 'bundle org.apache.ant [1.8.2,1.9.0)' but it could not be found
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.]
> {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, 5 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2727:
-----------------------------------
[~bleathem]: ideally we'd have the updated archetype before QE finishes its tests (29/11/13)
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
> Key: JBDS-2727
> URL: https://issues.jboss.org/browse/JBDS-2727
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 7.1.0.GA
>
> Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations
--
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, 5 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2727:
-----------------------------------
Vineet, the commands you want to use require arguments (eg. selecting a started server) we can't provide in the cheatsheets for now. This can be discussed over JBIDE-16087.
In the meantime, you should not try to use these commands.
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
> Key: JBDS-2727
> URL: https://issues.jboss.org/browse/JBDS-2727
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 7.1.0.GA
>
> Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations
--
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, 5 months
[JBoss JIRA] (JBIDE-16087) The command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy fails when executed via a cheatsheet
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16087?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16087:
--------------------------------
Fix Version/s: 4.2.x
> The command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy fails when executed via a cheatsheet
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16087
> URL: https://issues.jboss.org/browse/JBIDE-16087
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Fix For: 4.2.x
>
>
> When I embed the following command in an Eclipse cheatsheet for JDF-497 :
> {noformat}
> <command
> required="false"
> serialization="org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy"/>
> {noformat}
> it fails with the following error:
> {noformat}
> !ENTRY org.eclipse.ui.cheatsheets 4 0 2013-11-21 22:50:34.494
> !MESSAGE The command did not complete successfully.
> !STACK 0
> org.eclipse.core.commands.NotHandledException: There is no handler to execute for command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:512)
> 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.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.cheatsheets.CommandRunner.executeCommand(CommandRunner.java:81)
> at org.eclipse.ui.internal.cheatsheets.data.CheatSheetCommand.execute(CheatSheetCommand.java:44)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem.runExecutable(CoreItem.java:506)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem.runExecutable(CoreItem.java:501)
> at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.runPerformExecutable(CheatSheetViewer.java:1046)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem$1.linkActivated(CoreItem.java:89)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> 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: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)
> {noformat}
> I'm not sure if this command is available for use in a cheatsheet, but I thought I'd report 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, 5 months
[JBoss JIRA] (JBDS-2805) move Central TP site declaration from JBT parent pom to JBDS installer pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2805?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2805:
-----------------------------
CDW qa_ack: + (was: ?)
> move Central TP site declaration from JBT parent pom to JBDS installer pom
> --------------------------------------------------------------------------
>
> Key: JBDS-2805
> URL: https://issues.jboss.org/browse/JBDS-2805
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, build, installer
> Affects Versions: 7.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.0.0.Alpha1
>
>
> Fairly sure that the only place this variable
> {code:title=https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L78}
> <jboss-central-target-platform-site>http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kep...</jboss-central-target-platform-site>
> {code}
> is used is in the JBDS installer pom:
> {code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/pom.xml#L74}
> <repository>
> <!-- JBDS-2623 use Central TP instead of TestNG mirror -->
> <id>jboss-central-target-platform-site</id>
> <url>${jboss-central-target-platform-site}</url>
> <layout>p2</layout>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> <releases>
> <enabled>true</enabled>
> </releases>
> </repository>
> {code}
> So why don't we just move it into JBDS entirely, instead of declaring it in JBT parent pom?
--
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, 5 months
[JBoss JIRA] (JBDS-2805) move Central TP site declaration from JBT parent pom to JBDS installer pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2805?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2805:
-----------------------------
Issue Type: Enhancement (was: Bug)
> move Central TP site declaration from JBT parent pom to JBDS installer pom
> --------------------------------------------------------------------------
>
> Key: JBDS-2805
> URL: https://issues.jboss.org/browse/JBDS-2805
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, build, installer
> Affects Versions: 7.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.0.0.Alpha1
>
>
> Fairly sure that the only place this variable
> {code:title=https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L78}
> <jboss-central-target-platform-site>http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kep...</jboss-central-target-platform-site>
> {code}
> is used is in the JBDS installer pom:
> {code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/pom.xml#L74}
> <repository>
> <!-- JBDS-2623 use Central TP instead of TestNG mirror -->
> <id>jboss-central-target-platform-site</id>
> <url>${jboss-central-target-platform-site}</url>
> <layout>p2</layout>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> <releases>
> <enabled>true</enabled>
> </releases>
> </repository>
> {code}
> So why don't we just move it into JBDS entirely, instead of declaring it in JBT parent pom?
--
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, 5 months