[JBoss JIRA] (JBDS-1591) JBDS Installer as a Native Mac OS X Application
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-1591?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-1591:
-------------------------------------
[~maxandersen], [~dgolovin], do we still want this? Why not close this JIRA?
> JBDS Installer as a Native Mac OS X Application
> -----------------------------------------------
>
> Key: JBDS-1591
> URL: https://issues.jboss.org/browse/JBDS-1591
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 4.0.0.GA
> Environment: Mac OS X
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 8.0.x
>
>
> This is an enhancement for your consideration. Feel free to reject it.
> Currently, all the installers of JBDS for Mac OS X and other platforms are just plain jar files which you launch either with "java -jar" or by double clicking if the OS supports this.
> When you launch the jar, the icon that appears in the Dock is just a default app icon. It would be possible to bundle the installer on the Mac so that it would be a native Mac OS X app called e.g. "JBDS 4 Installer.app".
> The instructions on how to achieve this are described here:
> http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/
> I just tried it and it's easy.
> I think it would be easy to implement this in the building process. The benefit would be an installer with our custom icon in the Dock and also on the installer itself - i.e. in Finder.
--
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-2710) 3rd party certification for JBDS 7.1.0.GA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2710:
-------------------------------------------
Could we stop please updating the description and instead putting the missing work in subtasks and updates in comments ? its impossible to follow what changed/what is being worked on in this jira. Try clicking on "All" tab to see what I mean ;)
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.1.0.GA
>
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> Proposed *new* connectors for JBDS 7.1:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> * SpringSource's Quick Search - JBDS-2686 *TBD* (affects JBDS installer/Central TP)
> The current list of connectors in 7.0 *which can be updated* in 7.1 are:
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129
> These are currently unchanged since December when we released JBDS 6.0.0:
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
--
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-15648) Add tests for EAP 6.2 to integration tests
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15648?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-15648.
---------------------------------
Done.
> Add tests for EAP 6.2 to integration tests
> ------------------------------------------
>
> Key: JBIDE-15648
> URL: https://issues.jboss.org/browse/JBIDE-15648
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.1.1.Alpha1
> Reporter: Martin Malina
> Assignee: Radim Hopp
> Fix For: 4.1.1.Alpha2
>
>
> Please add a new test suite for EAP 6.2. In the tools it uses the type EAP 6.1+ (previously EAP 6.1), but since there is a new message in the welcome web page, it is probably better to have new test classes for EAP 6.2:
> Radim Hatlapatka said:
> {quote}
> Ahoj, z duvodu brandingu se zmenil text na uvodni strance EAPu z "Welcome to EAP 6" na "Welcome to JBoss EAP 6"
> {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
12 years, 5 months
[JBoss JIRA] (JBDS-2555) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2555?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2555:
-------------------------------------------
[~jimrigsbee] central caches its data - thus if not possible to reach the servers it will show what was fetched last and we bundle a copy of the important data but these will update over time (list of quickstarts, wizards etc. shown in central).
Do you see a problem with these ? All of it should happen in background and not slow anything down.
> JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
> ----------------------------------------------------------------------------
>
> Key: JBDS-2555
> URL: https://issues.jboss.org/browse/JBDS-2555
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Reporter: Jiri Pallich
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1, 7.1.0.CR1
>
>
> Offline Usage of JBoss Central (Customers without or very slow Internet access)
> On-line once, then off-line - aka a user demo/instructional class - the testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline).
> Related to: https://issues.jboss.org/browse/JBDS-2535
--
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-15848) JSF Portal Project XML Problem
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15848?page=com.atlassian.jira.plugi... ]
Radoslav Rábara commented on JBIDE-15848:
-----------------------------------------
Hi [~akazakov],
I am using JBDS 7.1.0 Beta1 but I also downloaded Eclipse 4.3.1 SR1, installed plug-in JBoss Portlet, added JPP 6.1 via JBoss Tools Runtime Detection and reproduced this issue.
> JSF Portal Project XML Problem
> ------------------------------
>
> Key: JBIDE-15848
> URL: https://issues.jboss.org/browse/JBIDE-15848
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, portal-gatein, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1
> Reporter: Radoslav Rábara
> Assignee: Snjezana Peco
> Priority: Blocker
> Attachments: jsf - Error.jpg, jsf - show details.jpg
>
>
> Creating JSF Portal Project ends with error:
> Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd).
> Type: XML Error, Resource: faces-config.xml
--
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-15835) Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15835?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15835:
---------------------------------------------
Its more and more obvious we need to provide a way for users to override these timeouts thus when they use a slow system there is a way for them to at least get work done.
I suggest we use the same timeout as rhc uses and provide at least a way to set these via system properties and eventually allow for preference control over this in eclipse workspace.
> Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-15835
> URL: https://issues.jboss.org/browse/JBIDE-15835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
>
> Attempt to add to existing (or can be added when creating new) application PostgreSQL database cartridge cause connection time out. Dialog with text
> {code}Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out {code} is shown.
> Finally, cartridge seems to be added correctly (seems to be embedded well, environment variables are correctly set up for the given cartridge etc.)
> This happens only on Openshift Enterprise (Openshift Online works fine)
> Eclipse log:
> {code}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2013-11-01 12:54:14.209
> !MESSAGE Could not embed cartridges for application dasda
> !STACK 0
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:139)
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142)
> at com.openshift.internal.client.ApplicationResource$AddEmbeddedCartridgeRequest.execute(ApplicationResource.java:1026)
> at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridge(ApplicationResource.java:353)
> at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridges(ApplicationResource.java:368)
> at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.addEmbeddedCartridges(EmbedCartridgesJob.java:94)
> at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.doRun(EmbedCartridgesJob.java:56)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
> at sun.security.ssl.InputRecord.read(InputRecord.java:480)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 10 more
> {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] (JBIDE-15806) Migrate jbosstools-4.1.x and master branches to use Tycho 0.19.0
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15806?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-15806:
---------------------------------------
It works fine on LiveReload on jbosstools-4.1.x
> Migrate jbosstools-4.1.x and master branches to use Tycho 0.19.0
> ----------------------------------------------------------------
>
> Key: JBIDE-15806
> URL: https://issues.jboss.org/browse/JBIDE-15806
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.CR1, 4.2.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> With the release of Tycho 0.19, we should explore moving up to that in our parent pom, Locus, and TP builds.
> {quote}
> Tycho milestone 0.19.0 has been released and is available from maven central.
> See the release notes [1] for details of enhancements and bug fixes in this release.
> Thanks to Mickael Istria, Nepomuk Seiler, Roland Grunberg, and Thanh Ha who contributed patches for this release.
> And thanks and to everyone who helped us with testing the staged version.
> Regards,
> Tycho team
> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.19
> {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
12 years, 5 months