[JBoss JIRA] (JBIDE-16664) Mylyn related packages removed from Target Platform - can we get them back?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16664?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16664:
------------------------------------
If all this stuff has moved and is now in the JBoss Central TP, could not the mylyn bot tests simply resolve against that repo instead?
> 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: Mickael Istria
> 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
10 years, 2 months
[JBoss JIRA] (JBIDE-16626) OpenShift Server Adapter: Binary deployment
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16626?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16626:
----------------------------------
Description:
At first, I am not sure whether this is bug or desired behaviour (in that case this issue is Enhancement). There is a problem with binary deployment.
Current workflow is following:
PRESTEPS:
1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new application)
2. Open Project Explorer, select application and open context menu OpenShift - Configure Markers...
3. Select disable maven build marker. You can select also Hot deploy to improve deploying speed (no need to restart cartridge).
4. Open Navigator - .openshift - markers and select new markers and add them to Index (context menu - Team - Add to Index)
5. Push application to OpenShift (e.g. context menu of application - Team - Commit...)
BINARY DEPLOYMENT
1. Now imagine, you want to binary deploy. Let's say, user change something in index.html (for example title).
2. Then it's required to locally build application (context menu of application - Run as - Maven build and set goal "clean package -Popenshift"). Result - application is built in deployment folder as ROOT.war.
3. Add ROOT.war to git index (context menu - Team - Add to index)
4. Drag and drop application from Project Explorer to Servers view adapter onto the given OpenShift adapter.
5. Confirm push.
My idea of binary deployment is:
1. User change something in application
2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter - this step build application, add ROOT.war to index.
3. Confirm to push.
was:
At first, I am not sure whether this is bug or desired behaviour (in that case this issue is Enhancement). There is a problem with binary deployment.
Current workflow is following:
PRESTEPS:
1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new application)
2. Open Project Explorer, select application and open context menu OpenShift - Configure Markers...
3. Select disable maven build marker. You can select also Hot deploy to improve deploying speed (no need to restart cartridge).
4. Open Navigator - .openshift - markers and select new markers and add them to Index (context menu - Team - Add to Index)
5. Push application to OpenShift (e.g. context menu of application - Team - Commit...)
BINARY DEPLOYMENT
1. Now imagine, you want to binary deploy. Let's say, user change something in index.html (for example title).
2. Then it's required to locally build application (context menu of application - Run as - Maven build and set goal "clean package -Popenshift"). Result - application is build in deployment folder as ROOT.war.
3. Add ROOT.war to git index (context menu - Team - Add to index)
4. Drag and drop application from Project Explorer to Servers view adapter onto the given OpenShift adapter.
5. Confirm push.
My idea of binary deployment is:
1. User change something in application
2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter - this step build application, add ROOT.war to index.
3. Confirm to push.
> OpenShift Server Adapter: Binary deployment
> -------------------------------------------
>
> Key: JBIDE-16626
> URL: https://issues.jboss.org/browse/JBIDE-16626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final, 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
>
> At first, I am not sure whether this is bug or desired behaviour (in that case this issue is Enhancement). There is a problem with binary deployment.
> Current workflow is following:
> PRESTEPS:
> 1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new application)
> 2. Open Project Explorer, select application and open context menu OpenShift - Configure Markers...
> 3. Select disable maven build marker. You can select also Hot deploy to improve deploying speed (no need to restart cartridge).
> 4. Open Navigator - .openshift - markers and select new markers and add them to Index (context menu - Team - Add to Index)
> 5. Push application to OpenShift (e.g. context menu of application - Team - Commit...)
> BINARY DEPLOYMENT
> 1. Now imagine, you want to binary deploy. Let's say, user change something in index.html (for example title).
> 2. Then it's required to locally build application (context menu of application - Run as - Maven build and set goal "clean package -Popenshift"). Result - application is built in deployment folder as ROOT.war.
> 3. Add ROOT.war to git index (context menu - Team - Add to index)
> 4. Drag and drop application from Project Explorer to Servers view adapter onto the given OpenShift adapter.
> 5. Confirm push.
> My idea of binary deployment is:
> 1. User change something in application
> 2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter - this step build application, add ROOT.war to index.
> 3. Confirm to push.
--
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
10 years, 2 months
[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2913:
-------------------------------------------
[~mmusaji] what install of EAP 6.2.1 did you use ? -full-build.zip or the eap 6.2.0+patch.zip ?
> 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
10 years, 2 months
[JBoss JIRA] (JBIDE-16665) Add Sapphire to TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16665:
----------------------------------------
Ok, I guess you won't need o.e.s.sdk nor o.e.s.source as well (target platform will resolve sources in IDE automatically, so there is probably not much value in adding them).
> Add Sapphire to TP
> ------------------
>
> Key: JBIDE-16665
> URL: https://issues.jboss.org/browse/JBIDE-16665
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, testing-tools
> Affects Versions: 4.2.0.Alpha2
> Reporter: Snjezana Peco
>
> Reason: Required by new feature described in JBIDE-15394
> License and owner: EPL, Eclipse
> Original repository: http://download.eclipse.org/sapphire/0.7/repository
> JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire
> Source: Yes
> Affected projects: arquillian
> Required in devstudio: No
> Type of dependency:
> List of bundles added:
> org.eclipse.sapphire.java
> org.eclipse.sapphire.java.jdt
> org.eclipse.sapphire.java.jdt.ui
> org.eclipse.sapphire.modeling
> org.eclipse.sapphire.modeling.xml
> org.eclipse.sapphire.osgi
> org.eclipse.sapphire.osgi.fragment
> org.eclipse.sapphire.platform
> org.eclipse.sapphire.ui
> org.eclipse.sapphire.ui.swt.gef
> org.eclipse.sapphire.ui.swt.xml.editor
> org.eclipse.sapphire.workspace
> org.eclipse.sapphire.workspace.ui
> org.objectweb.asm
--
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
10 years, 2 months
[JBoss JIRA] (JBIDE-16665) Add Sapphire to TP
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16665:
---------------------------------------
The Sapphire framework contains the following features:
org.eclipse.sapphire_0.7.0.201312161343
org.eclipse.sapphire.java_0.7.0.201312161343
org.eclipse.sapphire.java.jdt_0.7.0.201312161343
org.eclipse.sapphire.modeling.xml_0.7.0.201312161343
org.eclipse.sapphire.osgi_0.7.0.201312161343
org.eclipse.sapphire.platform_0.7.0.201312161343
org.eclipse.sapphire.samples_0.7.0.201312161343
org.eclipse.sapphire.sdk_0.7.0.201312161343
org.eclipse.sapphire.source_0.7.0.201312161343
org.eclipse.sapphire.tests_0.7.0.201312161343
org.eclipse.sapphire.ui_0.7.0.201312161343
org.eclipse.sapphire.ui.swt.gef_0.7.0.201312161343
org.eclipse.sapphire.ui.swt.xml.editor_0.7.0.201312161343
The o.e.s.samples and o.e.s.tests feature aren't obliged.
> Add Sapphire to TP
> ------------------
>
> Key: JBIDE-16665
> URL: https://issues.jboss.org/browse/JBIDE-16665
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, testing-tools
> Affects Versions: 4.2.0.Alpha2
> Reporter: Snjezana Peco
>
> Reason: Required by new feature described in JBIDE-15394
> License and owner: EPL, Eclipse
> Original repository: http://download.eclipse.org/sapphire/0.7/repository
> JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire
> Source: Yes
> Affected projects: arquillian
> Required in devstudio: No
> Type of dependency:
> List of bundles added:
> org.eclipse.sapphire.java
> org.eclipse.sapphire.java.jdt
> org.eclipse.sapphire.java.jdt.ui
> org.eclipse.sapphire.modeling
> org.eclipse.sapphire.modeling.xml
> org.eclipse.sapphire.osgi
> org.eclipse.sapphire.osgi.fragment
> org.eclipse.sapphire.platform
> org.eclipse.sapphire.ui
> org.eclipse.sapphire.ui.swt.gef
> org.eclipse.sapphire.ui.swt.xml.editor
> org.eclipse.sapphire.workspace
> org.eclipse.sapphire.workspace.ui
> org.objectweb.asm
--
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
10 years, 2 months
[JBoss JIRA] (JBIDE-16665) Add Sapphire to TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16665:
----------------------------------------
Wouldn't you prefer to reference a feature in target definition?
> Add Sapphire to TP
> ------------------
>
> Key: JBIDE-16665
> URL: https://issues.jboss.org/browse/JBIDE-16665
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, testing-tools
> Affects Versions: 4.2.0.Alpha2
> Reporter: Snjezana Peco
>
> Reason: Required by new feature described in JBIDE-15394
> License and owner: EPL, Eclipse
> Original repository: http://download.eclipse.org/sapphire/0.7/repository
> JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire
> Source: Yes
> Affected projects: arquillian
> Required in devstudio: No
> Type of dependency:
> List of bundles added:
> org.eclipse.sapphire.java
> org.eclipse.sapphire.java.jdt
> org.eclipse.sapphire.java.jdt.ui
> org.eclipse.sapphire.modeling
> org.eclipse.sapphire.modeling.xml
> org.eclipse.sapphire.osgi
> org.eclipse.sapphire.osgi.fragment
> org.eclipse.sapphire.platform
> org.eclipse.sapphire.ui
> org.eclipse.sapphire.ui.swt.gef
> org.eclipse.sapphire.ui.swt.xml.editor
> org.eclipse.sapphire.workspace
> org.eclipse.sapphire.workspace.ui
> org.objectweb.asm
--
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
10 years, 2 months