[JBoss JIRA] (JBIDE-16664) Mylyn related packages removed from Target Platform - can we get them back?
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16664?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-16664:
--------------------------------------
https://github.com/jbosstools/jbosstools-integration-tests/pull/514
Thanks to Dr Leacu!
> Mylyn related packages removed from Target Platform - can we get them back?
> ---------------------------------------------------------------------------
>
> Key: JBIDE-16664
> URL: https://issues.jboss.org/browse/JBIDE-16664
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Beta1
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Fix For: 4.2.0.Beta1
>
>
> I noticed that this test starting failing a few days ago:
> https://github.com/ldimaggi/jbosstools-integration-tests/tree/master/test...
> For exmaple:
> http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/38...
> With an error of:
> [ERROR] Software being installed: org.eclipse.mylyn.context_feature.feature.group 3.11.0.20131105-2146
> [ERROR] Missing requirement: org.eclipse.mylyn.context_feature.feature.group 3.11.0.20131105-2146 requires 'org.eclipse.mylyn_feature.feature.group [3.11.0,3.12.0)' but it could not be found
> And I found that here - the mylyn-related packages that the test needs were indeed removed - can we get them back?
> https://github.com/jbosstools/jbosstools-target-platforms/pull/36/files
> {code}
> - <!-- Mylyn site contains more than is in Kepler site, and this way we get sources too -->
> - <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true">
> - <repository location="http://download.jboss.org/jbosstools/updates/requirements/mylyn/3.11.0-I2..."/>
> - <unit id="org.eclipse.mylyn.bugzilla_feature.feature.group" version="3.11.0.20131218-0113"/>
> - <unit id="org.eclipse.mylyn.commons.feature.group" version="3.11.0.20131024-1846"/>
> - <unit id="org.eclipse.mylyn.commons.compatibility.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.core" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.identity.feature.group" version="1.3.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.net" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.notifications.feature.group" version="1.3.0.20131105-2126"/>
> - <unit id="org.eclipse.mylyn.commons.repositories.feature.group" version="1.3.0.20131127-1955"/>
> - <unit id="org.eclipse.mylyn.commons.repositories.http.feature.group" version="1.3.0.20131129-1037"/>
> - <unit id="org.eclipse.mylyn.commons.screenshots" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.soap" version="3.11.0.20131219-1119"/>
> - <unit id="org.eclipse.mylyn.commons.ui" version="3.11.0.20131024-1846"/>
> - <unit id="org.eclipse.mylyn.commons.xmlrpc" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.context_feature.feature.group" version="3.11.0.20131105-2146"/>
> - <unit id="org.eclipse.mylyn.cvs.feature.group" version="1.3.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.discovery.core" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.discovery.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.discovery.ui" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn_feature.feature.group" version="3.11.0.20131218-0113"/>
> - <unit id="org.eclipse.mylyn.git.feature.group" version="1.3.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.ide_feature.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.java_feature.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.monitor.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.pde_feature.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.tasks.bugs" version="3.11.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.tasks.core" version="3.11.0.20131218-0113"/>
> - <unit id="org.eclipse.mylyn.tasks.ide.feature.group" version="3.11.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.tasks.ui" version="3.11.0.20131218-0113"/>
> - <unit id="org.eclipse.mylyn.team_feature.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.versions.feature.group" version="1.3.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.wikitext_feature.feature.group" version="2.0.0.20131219-0024"/>
> - </location>
> {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
11 years, 2 months
[JBoss JIRA] (JBIDE-16664) Mylyn related packages removed from Target Platform - can we get them back?
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16664?page=com.atlassian.jira.plugi... ]
Len DiMaggio reassigned JBIDE-16664:
------------------------------------
Assignee: Len DiMaggio (was: Mickael Istria)
> Mylyn related packages removed from Target Platform - can we get them back?
> ---------------------------------------------------------------------------
>
> Key: JBIDE-16664
> URL: https://issues.jboss.org/browse/JBIDE-16664
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Beta1
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Fix For: 4.2.0.Beta1
>
>
> I noticed that this test starting failing a few days ago:
> https://github.com/ldimaggi/jbosstools-integration-tests/tree/master/test...
> For exmaple:
> http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/38...
> With an error of:
> [ERROR] Software being installed: org.eclipse.mylyn.context_feature.feature.group 3.11.0.20131105-2146
> [ERROR] Missing requirement: org.eclipse.mylyn.context_feature.feature.group 3.11.0.20131105-2146 requires 'org.eclipse.mylyn_feature.feature.group [3.11.0,3.12.0)' but it could not be found
> And I found that here - the mylyn-related packages that the test needs were indeed removed - can we get them back?
> https://github.com/jbosstools/jbosstools-target-platforms/pull/36/files
> {code}
> - <!-- Mylyn site contains more than is in Kepler site, and this way we get sources too -->
> - <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true">
> - <repository location="http://download.jboss.org/jbosstools/updates/requirements/mylyn/3.11.0-I2..."/>
> - <unit id="org.eclipse.mylyn.bugzilla_feature.feature.group" version="3.11.0.20131218-0113"/>
> - <unit id="org.eclipse.mylyn.commons.feature.group" version="3.11.0.20131024-1846"/>
> - <unit id="org.eclipse.mylyn.commons.compatibility.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.core" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.identity.feature.group" version="1.3.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.net" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.notifications.feature.group" version="1.3.0.20131105-2126"/>
> - <unit id="org.eclipse.mylyn.commons.repositories.feature.group" version="1.3.0.20131127-1955"/>
> - <unit id="org.eclipse.mylyn.commons.repositories.http.feature.group" version="1.3.0.20131129-1037"/>
> - <unit id="org.eclipse.mylyn.commons.screenshots" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.commons.soap" version="3.11.0.20131219-1119"/>
> - <unit id="org.eclipse.mylyn.commons.ui" version="3.11.0.20131024-1846"/>
> - <unit id="org.eclipse.mylyn.commons.xmlrpc" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.context_feature.feature.group" version="3.11.0.20131105-2146"/>
> - <unit id="org.eclipse.mylyn.cvs.feature.group" version="1.3.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.discovery.core" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.discovery.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.discovery.ui" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn_feature.feature.group" version="3.11.0.20131218-0113"/>
> - <unit id="org.eclipse.mylyn.git.feature.group" version="1.3.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.ide_feature.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.java_feature.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.monitor.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.pde_feature.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.tasks.bugs" version="3.11.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.tasks.core" version="3.11.0.20131218-0113"/>
> - <unit id="org.eclipse.mylyn.tasks.ide.feature.group" version="3.11.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.tasks.ui" version="3.11.0.20131218-0113"/>
> - <unit id="org.eclipse.mylyn.team_feature.feature.group" version="3.11.0.20131021-1909"/>
> - <unit id="org.eclipse.mylyn.versions.feature.group" version="1.3.0.20131021-1910"/>
> - <unit id="org.eclipse.mylyn.wikitext_feature.feature.group" version="2.0.0.20131219-0024"/>
> - </location>
> {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
11 years, 2 months
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on JBDS-2734:
------------------------------------------
Update on this. As of Forge 2.1.1, we have support for the Merged/Single-page wizards you are asking for. So 6 with 1-2 options each page becomes 1 page with 5-12 options in order. The scaffold just needs to be updated to use this (minor change.) So this is in line.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: forge, requirements
> Reporter: Burr Sutter
> Assignee: Koen Aers
> Fix For: 8.0.0.Beta1
>
>
> Is Forge 2 ready to be included in JBDS ?
--
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
11 years, 2 months
[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on JBDS-2913:
-----------------------------------
I am also unable to replicate in jbds 7.1 on a linux environment.
When I open the launch configuration, I see "-Dorg.jboss.logmanager.nocolor=true " in the vm-args. Do you see that as well? If I remove those flags, then I see the incorrect color characters, but, with a new server, the launch config has the proper flags and the server doesn't show the color characters.
> Console log when running EAP 6.2.x not formatted correctly
> ----------------------------------------------------------
>
> Key: JBDS-2913
> URL: https://issues.jboss.org/browse/JBDS-2913
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: server
> Affects Versions: 7.1.0.GA
> Reporter: Mustafa Musaji
> Assignee: Rob Stryker
> Fix For: 7.1.1.CR1
>
> Attachments: EAP-6.1.0.png, EAP-6.2.1.png
>
>
> When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.0)
--
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
11 years, 2 months
[JBoss JIRA] (JBDS-2848) Usage Stats for actual used features
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2848:
-----------------------------
CDW release: + (was: ?)
> Usage Stats for actual used features
> ------------------------------------
>
> Key: JBDS-2848
> URL: https://issues.jboss.org/browse/JBDS-2848
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, usage
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: QE_JBDS80_needinfo
>
> We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage".
> Areas worth tracking include (in priority order):
> - Use of the OpenShift Wizard to successful completion vs error
> - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
> - Successful installation of the features found on Software/Update tab of JBoss Central
> - Use of the JSF/RichFaces Visual Page Editor
> - Use of the Hibernate Tooling
> - Use of the jQuery Mobile Palette
> - Use of BrowserSim
> - Use of CordovaSim
> We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/
> Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
> Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.
--
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
11 years, 2 months
[JBoss JIRA] (JBDS-2848) Usage Stats for actual used features
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-2848:
-------------------------------
CDW qa_ack: + (was: ?)
> Usage Stats for actual used features
> ------------------------------------
>
> Key: JBDS-2848
> URL: https://issues.jboss.org/browse/JBDS-2848
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, usage
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: QE_JBDS80_needinfo
>
> We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage".
> Areas worth tracking include (in priority order):
> - Use of the OpenShift Wizard to successful completion vs error
> - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
> - Successful installation of the features found on Software/Update tab of JBoss Central
> - Use of the JSF/RichFaces Visual Page Editor
> - Use of the Hibernate Tooling
> - Use of the jQuery Mobile Palette
> - Use of BrowserSim
> - Use of CordovaSim
> We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/
> Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
> Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.
--
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
11 years, 2 months
