[JBoss JIRA] (JBDS-2416) label Central connectors that are sourced from 3rd party sites (rather than our mirrors) as being External and provide detailed description/notice of ownership
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2416?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2416:
--------------------------------------
Fix Version/s: 7.0.0.Alpha2
(was: 7.0.0.Alpha1)
not blocking alpha1
> label Central connectors that are sourced from 3rd party sites (rather than our mirrors) as being External and provide detailed description/notice of ownership
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2416
> URL: https://issues.jboss.org/browse/JBDS-2416
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.GA
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Labels: f2f2012
> Fix For: 7.0.0.Alpha2
>
>
> We currently use "Supported" to define JBoss-built/maintained content in Central, and "Tested" for 3rd party stuff we mirror and try to keep up to date.
> However, for content that changes frequently (Android Tooling) or for which we do not have license to redistribute (JRebel), we need to link directly to a vendor's site and simply hope for the best.
> But, to make it clear this is the case, we should in JBDS provide a note about this using a some term such as:
> * External
> * Other
> * 3rdParty
> and then provide a tooltip which reads:
> {quote}This content, while compatible with JBoss Developer Studio at the time of release, comes directly from another vendor's site and is subject to change without notice.{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
13 years, 1 month
[JBoss JIRA] (JBDS-2390) How to customize JBT to be like JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2390?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2390:
--------------------------------------
Fix Version/s: 7.0.0.Alpha2
(was: 7.0.0.Alpha1)
not blocking alpha1.
What is actually left in this to do ? What have been done ?
> How to customize JBT to be like JBDS
> ------------------------------------
>
> Key: JBDS-2390
> URL: https://issues.jboss.org/browse/JBDS-2390
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: central
> Reporter: Mickael Istria
> Assignee: Snjezana Peco
> Fix For: 7.0.0.Alpha2
>
>
> In JBDS, we override the discovery.url to set it to the value for JBDS Central site.
> However, this is done by hacking system properties. Instead, we could think of using the "discoveryProviderUrl" extension point in JBT.
> JBT would provide an extension to define this URL.
> JBDS would provide another extension to define this URL.
> Changing URL happens by updating the extension plugin.
> So JBT and JBDS would behave the same way when dealing with discovery, and we remove the system properties settings from JBDS. System proprty would still be available for testing only.
--
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-13278) Rename "Run as->Run on server" at a JAX-RS Endpoint node level
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13278?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13278:
----------------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.0.Alpha1)
not a blocker for alpha1.
Run on server isn't really what this does either.
It checks if the server is running if not starts it, if yes it opens the tester.
And if you use Debug As... it starts in debug mode.
Same as what run as / debug as / profile as does in rest of the UI.
But I agree it could be clearer so maybe add a "Test.." which will do the same as what Run As...> would do ?
> Rename "Run as->Run on server" at a JAX-RS Endpoint node level
> --------------------------------------------------------------
>
> Key: JBIDE-13278
> URL: https://issues.jboss.org/browse/JBIDE-13278
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Alpha2
>
>
> The "Run as->Run on server" menu item work well, but they are no so obvious to the end-user. We should provide a more straightforward way to "test" the endpoint with the the WS Tester.
--
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-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13671:
----------------------------------------
I'm investigating around the jgit provider and build timestamp plugin. I tried with jbosstools-freemarker component, and I am sceptical about its practices. For the following reason:
# It totally ignore local changes, so building a local, non-committed artifact result with an artifact with the same timestamp as the last commit, which may already be published somewhere. That means that there can be several same fully-qualified version whose content differ. It's not at all OSGi-friendly.
# It deduces the timestamp from the *last commit that affected the module resources* (incliding pom). So modules must really be "standalone" (ie not depend on other resources that move indepndently of the module.
# If we change anything that does not affect the resources in a module (let's say we change a groupId), the artifact will create a new version.
Although #2 and #3 should not happen in ideal case where modules are autonomous, they could be annoying in the trickiest situation.
Item #1 is not acceptable in my opinion.
I don't think this git timestamp provider will make us produce less builds. We'd better focus on not having to update components when it's not necessary (ie don't re-build old stuff just because parent pom changed).
> parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
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-13588) Openshift tools in JBT 4 require org.eclipse.egit.core [1.2.0, 2.3.0), but the version of EGit in Juno SR2 is 2.3.0.201302130906
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13588?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-13588.
----------------------------------
Verified in JBoss Developer Studio
Version: 6.0.1.GA
Build id: GA-v20130304-0526-B338
Build date: 20130304-0526
> Openshift tools in JBT 4 require org.eclipse.egit.core [1.2.0,2.3.0), but the version of EGit in Juno SR2 is 2.3.0.201302130906
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13588
> URL: https://issues.jboss.org/browse/JBIDE-13588
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.1.Final
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Fix For: 4.0.1.Final
>
>
> Need to extend the upper bound in MANIFEST.MF and/or feature.xml files so Openshift tools in JBT 4 can depend on EGit <=2.3, not <2.3.
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--openshift/116/console}
> [ERROR] Software being installed: org.jboss.tools.openshift.egit.test 2.4.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.openshift.egit.core 2.4.0.Final-v20130218-1429-B116 requires 'bundle org.eclipse.egit.core [1.2.0,2.3.0)' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.tools.openshift.egit.test 2.4.0.qualifier depends on: bundle org.jboss.tools.openshift.egit.core 1.0.0
> {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-13694) bump openshift maintenance 2.4.0->2.4.1
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13694?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-13694.
----------------------------------
Verified in JBoss Developer Studio
Version: 6.0.1.GA
Build id: GA-v20130304-0526-B338
Build date: 20130304-0526
> bump openshift maintenance 2.4.0->2.4.1
> ---------------------------------------
>
> Key: JBIDE-13694
> URL: https://issues.jboss.org/browse/JBIDE-13694
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.0.1.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.0.1.Final
>
>
> changed the version ranges for required egit plugins in JBIDE-13588, thus need to bump version 2.4.0->2.4.1
> did
> {code}
> mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=2.4.1-SNAPSHOT
> {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-12913) Startup/Shutdown Pollers fails with EAP511
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-12913.
---------------------------------
This is still working correctly in JBDS 6.0.1.CR1. Closing.
> Startup/Shutdown Pollers fails with EAP511
> ------------------------------------------
>
> Key: JBIDE-12913
> URL: https://issues.jboss.org/browse/JBIDE-12913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha2
> Environment: Windows XP
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Fix For: 4.0.0.Beta2
>
> Attachments: server-startup-poller-problem.png
>
>
> When we use Web Port Startup Poller with EAP511, the server is not started.
> We get an error about the port (8080) already being in use. Which it is not (confirmed with netstat).
> When changing Startup Poller to JMX, the server starts as expected.
> When using the JMX Shutdown Poller, it also fails. This time with failed attempts to access the JMX server after the server has shut down:
> Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at org.jboss.Shutdown.main(Shutdown.java:219)
> Caused by: javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
> ... 4 more
> Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
> ... 5 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
> ... 5 more
> Using Process Terminated Poller works as expected though.
--
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-11903) OpenShift Explorer: add Application start/stop/restart
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-11903 at 3/5/13 8:51 AM:
------------------------------------------------------------------
start, stop and restart are already available via
{code}
IApplication#start
IApplication#stop
IApplcaiiton#restart
{code}
There are approriate tests in ApplicationResourceIntegrationTest which test the REST operations that are related:
{code}
ApplicationResourceIntegrationTest#shouldStartStartedApplication
ApplicationResourceIntegrationTest#shouldStartStoppedApplication
ApplicationResourceIntegrationTest#shouldStopApplication
ApplicationResourceIntegrationTest#shouldStopStoppedApplication
ApplicationResourceIntegrationTest#shouldRestartStartedApplication
ApplicationResourceIntegrationTest#shouldRestartStoppedApplication
{code}
What's missing are methods that allow report the current state.
According to https://bugzilla.redhat.com/show_bug.cgi?id=805989 there are the following states
{code}
* stopped
* building
* deploying
* started
* idle
* unknown
{code}
which may be queried via gear_profiles:
{code}
curl -k --user "<USER>:<PASS>" -H "Accept: application/xml;version=1.0" 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>512e6a3ee0b8cde478000045</uuid>
<name>512e6a3ee0b8cde478000045</name>
<gear-profile>small</gear-profile>
<gears>
<gear>
<id>512e6a3ee0b8cde478000037</id>
<state>idle</state>
</gear>
</gears>
<cartridges>
<cartridge>
<name>jbossas-7</name>
<display-name>JBoss Application Server 7.1</display-name>
<tags>
<tag>service</tag>
<tag>web_framework</tag>
<tag>java</tag>
<tag>jboss</tag>
</tags>
</cartridge>
<cartridge>
<connection-url>postgresql://127.11.220.1:5432/</connection-url>
<username>admin</username>
<password>RcqAMFZ4yyju</password>
<database-name>as</database-name>
<name>postgresql-8.4</name>
<display-name>PostgreSQL Database 8.4</display-name>
<tags>
<tag>service</tag>
<tag>database</tag>
<tag>embedded</tag>
</tags>
</cartridge>
<cartridge>
<job-url>https://j-honkabonka2.rhcloud.com/job/as-build/</job-url>
<name>jenkins-client-1.4</name>
<display-name>Jenkins Client 1.4</display-name>
<tags>
<tag>ci_builder</tag>
<tag>embedded</tag>
</tags>
</cartridge>
</cartridges>
<scales-from>1</scales-from>
<scales-to>1</scales-to>
<base-gear-storage>1</base-gear-storage>
<additional-gear-storage>0</additional-gear-storage>
</gear-group>
</data>
<messages/>
<version>1.0</version>
<supported-api-versions>
<supported-api-version>1.0</supported-api-version>
<supported-api-version>1.1</supported-api-version>
<supported-api-version>1.2</supported-api-version>
<supported-api-version>1.3</supported-api-version>
</supported-api-versions>
</response>
{code}
was (Author: adietish):
start, stop and restart are already available via
{code}
IApplication#start
IApplication#stop
IApplcaiiton#restart
{code}
There are approriate tests in ApplicationResourceIntegrationTest which test the REST operations that are related:
{code}
ApplicationResourceIntegrationTest
ApplicationResourceIntegrationTest
ApplicationResourceIntegrationTest
ApplicationResourceIntegrationTest
ApplicationResourceIntegrationTest
ApplicationResourceIntegrationTest
ApplicationResourceIntegrationTest
{code}
> OpenShift Explorer: add Application start/stop/restart
> -------------------------------------------------------
>
> Key: JBIDE-11903
> URL: https://issues.jboss.org/browse/JBIDE-11903
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Eclipse plugin
> Reporter: Nam Duong
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear.
--
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