[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-13599:
--------------------------------------
What URL can we use with 7.0.0.alpha1c? Thx!
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13682:
------------------------------------
Plugins installed from 3.2 site:
{code}
$➔ find . -name "*atlas*" | sort
./com.atlassian.connector.commons_4.0.0.v20130212.jar
./com.atlassian.connector.eclipse.bamboo.core_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.bamboo.ui_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.branding.ui_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.commons.core_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.commons.ui_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.core_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.directclickthrough.ui_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.help_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.jira.core_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.jira.ui_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.monitor.core_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.monitor.ui_3.2.0.v20130212.jar
./com.atlassian.connector.eclipse.ui_3.2.0.v20130212.jar
./com.atlassian.jira.rest.client_1.1.0.2
{code}
Plugins we need on TP:
{code}
org.jboss.tools.common.mylyn (optional install from Central into JBDS - NOT part of the installer):
com.atlassian.connector.eclipse.commons.core;bundle-version="3.0.2";resolution:=optional,
com.atlassian.connector.eclipse.commons.ui;bundle-version="3.0.2";resolution:=optional,
com.atlassian.connector.eclipse.jira.core;bundle-version="3.0.2";resolution:=optional,
com.atlassian.connector.eclipse.jira.ui;bundle-version="3.0.2";resolution:=optional{code}
> Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central
> ----------------------------------------------------------
>
> Key: JBIDE-13682
> URL: https://issues.jboss.org/browse/JBIDE-13682
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13733) Clean up JBossASHandler
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13733?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13733:
-------------------------------------
I have a topic branch up with some cleanup, and it fixes some of the stuff, but, I'm (very very slightly) concerned about breakage. Also, the four questions I posted below need to be answered.
https://github.com/robstryker/jbosstools-server/tree/JBIDE-13733
> Clean up JBossASHandler
> -----------------------
>
> Key: JBIDE-13733
> URL: https://issues.jboss.org/browse/JBIDE-13733
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: JBossAS/Servers
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha2
>
>
> JBossASHandler is a pretty messy class with many confusing parts to it. Several things need to be changed.
> 1) Why are default names for server required in this class? Don't runtime type and server type already do this in getDefaults() when the working copy is created?
> 2) The code to check for nested runtimes is very messy and hard to understand.
> 3) Why are ESB and Drools added separately? Shouldn't the check for all nested runtimes using all handlers be able to find this itself? It seems drools and esb have their own detectors. So why is this required here?
> 4) The drools runtime seems to be not added to any model at all. It seems to just be returned. Is this only cosmetic? What is the purpose here? The drools detector would be adding this to the drools model, but we do not add it to any model, so what is the purpose?
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13733) Clean up JBossASHandler
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-13733:
-----------------------------------
Summary: Clean up JBossASHandler
Key: JBIDE-13733
URL: https://issues.jboss.org/browse/JBIDE-13733
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JBossAS/Servers
Affects Versions: 4.1.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Alpha2
JBossASHandler is a pretty messy class with many confusing parts to it. Several things need to be changed.
1) Why are default names for server required in this class? Don't runtime type and server type already do this in getDefaults() when the working copy is created?
2) The code to check for nested runtimes is very messy and hard to understand.
3) Why are ESB and Drools added separately? Shouldn't the check for all nested runtimes using all handlers be able to find this itself? It seems drools and esb have their own detectors. So why is this required here?
4) The drools runtime seems to be not added to any model at all. It seems to just be returned. Is this only cosmetic? What is the purpose here? The drools detector would be adding this to the drools model, but we do not add it to any model, so what is the purpose?
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13731) error when creating html5 project from central: duplicate listener
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13731?page=com.atlassian.jira.plugi... ]
Stefan Bunciak commented on JBIDE-13731:
----------------------------------------
Seems little familiar: JBIDE-12784
> error when creating html5 project from central: duplicate listener
> ------------------------------------------------------------------
>
> Key: JBIDE-13731
> URL: https://issues.jboss.org/browse/JBIDE-13731
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Environment: JBDS 7.0.0.Alpha1c B124
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
>
> When you try to create the html5 project from JBoss Central, you get this error in the workspace log:
> {code}
> !ENTRY org.eclipse.jpt.jpa.core 4 0 2013-03-06 13:45:23.414
> !MESSAGE duplicate listener: AbstractJpaProject.ResourceModelListener[06-25-5B-29](HibernateJpaProject[7E-83-E3-E5](jboss-as-kitchensink-html5-mobile))
> !STACK 0
> java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[06-25-5B-29](HibernateJpaProject[7E-83-E3-E5](jboss-as-kitchensink-html5-mobile))
> at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95)
> at org.eclipse.jpt.common.core.resource.xml.JptXmlResource.addResourceModelListener(JptXmlResource.java:270)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:587)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:560)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1664)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:264)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1649)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1841)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1833)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1816)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1627)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1619)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:759)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:741)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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
13 years, 1 month
[JBoss JIRA] (JBIDE-13577) refactor & clean up jbosstools-target-platforms repo
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13577?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13577.
------------------------------
Resolution: Done
Refactoring for its own sake, which provides *no net value* and only produces more work for me/Mickael: -100.
Asking people to look at the README.md, which clarifies the branches and purpose of master, producing no new work and educating Max: +100.
Closing. Again.
> refactor & clean up jbosstools-target-platforms repo
> ----------------------------------------------------
>
> Key: JBIDE-13577
> URL: https://issues.jboss.org/browse/JBIDE-13577
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final, 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2, 4.0.0.Final
>
>
> Rename branches as follows:
> 4.2.0 -> 4.20.x (currently contains 4.20.6)
> 4.2.1 -> 4.21.x (currently contains 4.21.4)
> (new) -> 4.22.x (soon will contain 4.22.0)
> 4.3.0 -> master (currently contains 4.30.3)
> Also, purge any large binaries that are causing the repo to be >50M in size.
> When Kepler R is released (Eclipse 4.3.0.Final) we can branch a 4.30.x branch and work on the new 4.31.x target platforms (Kepler SR1) in the master branch.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-11881) Display application state in OpenShift Explorer and Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-11881:
------------------------------------------
the gear_groups tells you about the state of the gears that an application is running on (*<gear><state>*):
{code}
curl --proxy http://file.rdu.redhat.com:3128 -H "Accept: application/xml; version=1.0" --user <USER>:<PASS> "https://openshift.redhat.com/broker/rest/domains/honkabonka2/applications..." -X GET
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<type>gear_groups</type>
<data>
<gear-group>
<uuid>51371581e0b8cd15b900002e</uuid>
<name>51371581e0b8cd15b900002e</name>
<gear-profile>medium</gear-profile>
<gears>
<gear>
<id>51371581e0b8cd15b900001b</id>
<state>started</state>
</gear>
<gear>
<id>513728ee5004465cbb0002bd</id>
<state>started</state>
</gear>
</gears>
<cartridges>
<cartridge>
<name>jbosseap-6.0</name>
<display-name>JBoss Enterprise Application Platform 6.0</display-name>
<tags>
<tag>service</tag>
<tag>web_framework</tag>
<tag>java</tag>
<tag>jboss</tag>
<tag>jee_full_profile</tag>
<tag>premium</tag>
</tags>
</cartridge>
<cartridge>
<name>haproxy-1.4</name>
<display-name>OpenShift Web Balancer</display-name>
<tags>
<tag>web_proxy</tag>
<tag>scales</tag>
<tag>embedded</tag>
</tags>
</cartridge>
</cartridges>
<scales-from>2</scales-from>
<scales-to>-1</scales-to>
<base-gear-storage>1</base-gear-storage>
<additional-gear-storage>0</additional-gear-storage>gU
</gear-group>
</data>
{code}
> Display application state in OpenShift Explorer and Properties view
> -------------------------------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
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
13 years, 1 month