April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19475) Add New application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19475?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19475: ------------------------------------------ postponing to 4.3.0.Beta1, nothing that we have to finish for Alpha2 > Add New application wizard > -------------------------- > > Key: JBIDE-19475 > URL: https://issues.jboss.org/browse/JBIDE-19475 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19477) Add parameter/env var validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19477?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19477 at 4/14/15 12:14 PM: -------------------------------------------------------------------- postponing to 4.3.0.Beta1, nothing that we have to finish for Alpha2 was (Author: adietish): postponing to Beta1, nothing that we have to finish for Alpha2 > Add parameter/env var validation > -------------------------------- > > Key: JBIDE-19477 > URL: https://issues.jboss.org/browse/JBIDE-19477 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19008) As a user, I want to delete OpenShift resources

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19008?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19008: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > As a user, I want to delete OpenShift resources > ----------------------------------------------- > > Key: JBIDE-19008 > URL: https://issues.jboss.org/browse/JBIDE-19008 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > We should allow users to remove OpenShift v3 resources. > Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19008) As a user, I want to delete OpenShift resources

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19008?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19008: ------------------------------------------ postponing to 4.3.0.Beta1, nothing that we have to finish for Alpha2 > As a user, I want to delete OpenShift resources > ----------------------------------------------- > > Key: JBIDE-19008 > URL: https://issues.jboss.org/browse/JBIDE-19008 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > We should allow users to remove OpenShift v3 resources. > Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19477) Add parameter/env var validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19477?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19477: ------------------------------------------ postponing to Beta1, nothing that we have to finish for Alpha2 > Add parameter/env var validation > -------------------------------- > > Key: JBIDE-19477 > URL: https://issues.jboss.org/browse/JBIDE-19477 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19108: ------------------------------------------ As far as I understand this is not an issue in OpenShift but rather something that should get fixed in server. Removing openshift component. > Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19108 > URL: https://issues.jboss.org/browse/JBIDE-19108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Alpha2 > > Attachments: JBIDE-19108_1.png, JBIDE-19108_2.png, JBIDE-19108_3.png, server_already_running.png > > > If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection. > !server_already_running.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19477) Add parameter/env var validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19477?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19477: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Add parameter/env var validation > -------------------------------- > > Key: JBIDE-19477 > URL: https://issues.jboss.org/browse/JBIDE-19477 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19108: ------------------------------------- Component/s: (was: openshift) > Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19108 > URL: https://issues.jboss.org/browse/JBIDE-19108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Alpha2 > > Attachments: JBIDE-19108_1.png, JBIDE-19108_2.png, JBIDE-19108_3.png, server_already_running.png > > > If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection. > !server_already_running.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer: Add "Pipeline" view to OpenShift v3 explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19178: ------------------------------------------ postponing to Beta1, nothin we'd have to finish for Alpha2 > Explorer: Add "Pipeline" view to OpenShift v3 explorer > ------------------------------------------------------ > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Beta1 > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19371) Allow OpenShiftRedirectionStrategy to determine the auth scheme

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19371?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19371: ------------------------------------------ postponing to Beta1, nothin we'd have to finish for Alpha2 > Allow OpenShiftRedirectionStrategy to determine the auth scheme > --------------------------------------------------------------- > > Key: JBIDE-19371 > URL: https://issues.jboss.org/browse/JBIDE-19371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > Introducing an authorization client which is able to determine how to authenticate when it gets a 401 and includes the following headers: > (org.apache.http.Header[]) [Www-Authenticate: Basic realm="openshift", Date: Wed, 25 Feb 2015 20:11:49 GMT, Content-Length: 0, Content-Type: text/plain; charset=utf-8] > Add method to identify the auth scheme and return the realm. Update the 'canconnect' endpoint to use this function. > This was achieved by trying to auth with empty username and password -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer: Add "Pipeline" view to OpenShift v3 explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19178: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Explorer: Add "Pipeline" view to OpenShift v3 explorer > ------------------------------------------------------ > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Beta1 > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19371) Allow OpenShiftRedirectionStrategy to determine the auth scheme

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19371?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19371: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Allow OpenShiftRedirectionStrategy to determine the auth scheme > --------------------------------------------------------------- > > Key: JBIDE-19371 > URL: https://issues.jboss.org/browse/JBIDE-19371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > Introducing an authorization client which is able to determine how to authenticate when it gets a 401 and includes the following headers: > (org.apache.http.Header[]) [Www-Authenticate: Basic realm="openshift", Date: Wed, 25 Feb 2015 20:11:49 GMT, Content-Length: 0, Content-Type: text/plain; charset=utf-8] > Add method to identify the auth scheme and return the realm. Update the 'canconnect' endpoint to use this function. > This was achieved by trying to auth with empty username and password -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17686: ---------------------------------------- Isn't it automatically resolved since we now consume newer RSE in our target-platform? > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.x > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18742) Only rely on rsync to publish new aggregate (remove other comparators)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18742: ---------------------------------------- I'm taking this one and put it in my TODO-list for ASAP after Alpha2. > Only rely on rsync to publish new aggregate (remove other comparators) > ---------------------------------------------------------------------- > > Key: JBIDE-18742 > URL: https://issues.jboss.org/browse/JBIDE-18742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. > It's more or less just a matter of scripting > {code:none} > p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot > if [[ -s p2diff_snapshot ]]; then > ./publish.sh > fi > {code} > Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18742) Only rely on rsync to publish new aggregate (remove other comparators)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18742: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Only rely on rsync to publish new aggregate (remove other comparators) > ---------------------------------------------------------------------- > > Key: JBIDE-18742 > URL: https://issues.jboss.org/browse/JBIDE-18742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. > It's more or less just a matter of scripting > {code:none} > p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot > if [[ -s p2diff_snapshot ]]; then > ./publish.sh > fi > {code} > Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18742) Only rely on rsync to publish new aggregate (remove other comparators)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-18742: -------------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > Only rely on rsync to publish new aggregate (remove other comparators) > ---------------------------------------------------------------------- > > Key: JBIDE-18742 > URL: https://issues.jboss.org/browse/JBIDE-18742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. > It's more or less just a matter of scripting > {code:none} > p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot > if [[ -s p2diff_snapshot ]]; then > ./publish.sh > fi > {code} > Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3208: -------------------------------------- What kind of sanity check does the composite provide? Are they really useful? IMO, it would be easier to always run aggregator than to keep this level of indirection that does not save time nor spot actual errors AFAIK. > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > Latest suggestion: > * /\{mars,9.0}/ > ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/ > *** /*updates*/ > **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/ > ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/ > *** /*builds*/ > **** /<job-name>/ > ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/ > --- > Older idea: > {code} > <download.jboss.org,devstudio.redhat.com> > <earlyaccess,updates,discovery>/<mars,9.0> > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last N builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13286) jobs should generate comment in JIRA recording job URL, BUILD#, and more detailed commit info (committer + comments)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13286?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13286: ------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > jobs should generate comment in JIRA recording job URL, BUILD#, and more detailed commit info (committer + comments) > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13286 > URL: https://issues.jboss.org/browse/JBIDE-13286 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.3.x > > > Is it possible to pull the git hash value used for a given build, look into github for the matching JIRA #, and drop a comment into the JIRA to the tune of: > "Spinning in <buildURL> >= BUILD_NUMBER" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19345) allow NN to be filtered/redefined for NN

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19345?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19345. --------------------------------- Verified. > allow NN to be filtered/redefined for NN > ---------------------------------------- > > Key: JBIDE-19345 > URL: https://issues.jboss.org/browse/JBIDE-19345 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.2.3.Final > > > there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release. > For example: > Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3> > Beta2: Added a few components to the Ionic: <c4> <c5> > Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>. > One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right. > Alternative suggestion is: > A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like > {code} > ifndef::finalnn[] > This piece of news was only relevant for Beta1 > endif::finalnn[] > {code} > See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html > B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19345) allow NN to be filtered/redefined for NN

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19345?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19345: ---------------------------------- Fix Version/s: (was: 4.3.0.CR1) > allow NN to be filtered/redefined for NN > ---------------------------------------- > > Key: JBIDE-19345 > URL: https://issues.jboss.org/browse/JBIDE-19345 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.2.3.Final > > > there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release. > For example: > Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3> > Beta2: Added a few components to the Ionic: <c4> <c5> > Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>. > One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right. > Alternative suggestion is: > A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like > {code} > ifndef::finalnn[] > This piece of news was only relevant for Beta1 > endif::finalnn[] > {code} > See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html > B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3200: ------------------------------------- I'm not sure if you can sign a jar in such a way that OS X then trusts it. Normally you would sign apps (.app) on OS X. I found this article explaining how to package java apps on OS X and it suggests to create an encapsulating app and sign that: https://docs.oracle.com/javase/7/docs/technotes/guides/jweb/packagingApps... > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19589) Allow NN to be filtered/redefined for NN

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19589?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-19589. ----------------------------------- Resolution: Done > Allow NN to be filtered/redefined for NN > ---------------------------------------- > > Key: JBIDE-19589 > URL: https://issues.jboss.org/browse/JBIDE-19589 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.CR1 > > > there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release. > For example: > Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3> > Beta2: Added a few components to the Ionic: <c4> <c5> > Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>. > One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right. > Alternative suggestion is: > A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like > {code} > ifndef::finalnn[] > This piece of news was only relevant for Beta1 > endif::finalnn[] > {code} > See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html > B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19589) Allow NN to be filtered/redefined for NN

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-19589: ------------------------------------- Summary: Allow NN to be filtered/redefined for NN Key: JBIDE-19589 URL: https://issues.jboss.org/browse/JBIDE-19589 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: website Reporter: Marián Labuda Assignee: Xavier Coulon Priority: Critical Fix For: 4.2.3.Final, 4.3.0.CR1 there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release. For example: Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3> Beta2: Added a few components to the Ionic: <c4> <c5> Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>. One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right. Alternative suggestion is: A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like {code} ifndef::finalnn[] This piece of news was only relevant for Beta1 endif::finalnn[] {code} See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19589) Allow NN to be filtered/redefined for NN

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19589?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19589: ---------------------------------- Fix Version/s: (was: 4.2.3.Final) > Allow NN to be filtered/redefined for NN > ---------------------------------------- > > Key: JBIDE-19589 > URL: https://issues.jboss.org/browse/JBIDE-19589 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.CR1 > > > there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release. > For example: > Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3> > Beta2: Added a few components to the Ionic: <c4> <c5> > Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>. > One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right. > Alternative suggestion is: > A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like > {code} > ifndef::finalnn[] > This piece of news was only relevant for Beta1 > endif::finalnn[] > {code} > See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html > B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2507) JBDS installer page has incorrect link to target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2507?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2507. ---------------------------- Resolution: Won't Fix No plan to do a 6.0.2; closing - won't fix. > JBDS installer page has incorrect link to target platforms > ---------------------------------------------------------- > > Key: JBDS-2507 > URL: https://issues.jboss.org/browse/JBDS-2507 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 6.0.1.GA > Environment: http://www.qa.jboss.com/binaries/RHDS/builds/development/6.0.1.CR1b.insta... > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 6.0.2.GA > > > All links mentioning target platform are invalid -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19588) Broken JIRA links in N&N for Server tools

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-19588: ------------------------------------- Summary: Broken JIRA links in N&N for Server tools Key: JBIDE-19588 URL: https://issues.jboss.org/browse/JBIDE-19588 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.2.3.Final Reporter: Marián Labuda See Server Tools section at http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.3.Final.html Link to related JIRAs are broken, because they include semicolon. Also there is underline char before semicolon in description which does not look nice. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19410: --------------------------------------- {quote}If missing network access is not handled, that is a new jira{quote} Missing Network access is a general issue for JBDS, running with network disabled makes it glowing with red colors in error log view. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18820: ------------------------------- Sprint: Sprint #2 April 2015 > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17686: ------------------------------- Sprint: Sprint #2 April 2015 > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.x > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18846: ------------------------------- Sprint: Sprint #2 April 2015 > create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18846 > URL: https://issues.jboss.org/browse/JBIDE-18846 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, website > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: > builds (nightly, staging, dev, stable) > updates (nightly, staging, dev, stable) > Jenkins jobs > discovery sites (nightly, staging, dev, stable) > target platforms > etc. > And for each component, we can list: > build > update > Jenkins job > etc. > The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html > Unsure whether generated HTML (via script) or simple .adoc is better for this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18742) Only rely on rsync to publish new aggregate (remove other comparators)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18742: ------------------------------- Sprint: Sprint #2 April 2015 > Only rely on rsync to publish new aggregate (remove other comparators) > ---------------------------------------------------------------------- > > Key: JBIDE-18742 > URL: https://issues.jboss.org/browse/JBIDE-18742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. > It's more or less just a matter of scripting > {code:none} > p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot > if [[ -s p2diff_snapshot ]]; then > ./publish.sh > fi > {code} > Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18984: ------------------------------- Sprint: Sprint #1 April 2015 (was: Sprint #2 April 2015) > Build Early Access site as an update site, not a TP > ---------------------------------------------------- > > Key: JBIDE-18984 > URL: https://issues.jboss.org/browse/JBIDE-18984 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform, updatesite > Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. > This would mean less target platform churning DURING a release, and speed up the way we do releases. > Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: > * one for JBT content (a subset of the JBT aggregate) and > * one for 3rd party content (an adjunct to the Central site) > This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19387) improve integration of integration stack jars into staged JBT / JBDS sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19387?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19387: ------------------------------- Sprint: Sprint #2 April 2015 > improve integration of integration stack jars into staged JBT / JBDS sites > -------------------------------------------------------------------------- > > Key: JBIDE-19387 > URL: https://issues.jboss.org/browse/JBIDE-19387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 4.2.3.Beta1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > I have this error in error log after startup of JBT: > {noformat:title=Cannot download bundle at http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin...: http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin...: http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin... > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.checkFileNotFound(RepositoryStatusHelper.java:297) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:441) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:398) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:322) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/jbosst... is pointing to non-existing http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19018) JBT Central Discovery staging site contains early access child site in its composite*.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19018?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19018: ------------------------------- Sprint: Sprint #1 April 2015 > JBT Central Discovery staging site contains early access child site in its composite*.xml > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19018 > URL: https://issues.jboss.org/browse/JBIDE-19018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > http://download.jboss.org/jbosstools/discovery/staging/4.2.1.Final/ composites early access site into the main update site, so anyone using that site as an update site (rather than simply as the back end to Central) will see EA content as if it's from Central. > If we stop publishing this staging discovery site that includes EA content, the release process will need to be updated to pull the EA plugin from another place. > Related to JBIDE-18984 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18984: ------------------------------- Sprint: Sprint #2 April 2015 > Build Early Access site as an update site, not a TP > ---------------------------------------------------- > > Key: JBIDE-18984 > URL: https://issues.jboss.org/browse/JBIDE-18984 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform, updatesite > Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. > This would mean less target platform churning DURING a release, and speed up the way we do releases. > Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: > * one for JBT content (a subset of the JBT aggregate) and > * one for 3rd party content (an adjunct to the Central site) > This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19449) p2.director install script is finding non-IU IUs to install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19449?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19449: ------------------------------- Sprint: Sprint #2 April 2015 > p2.director install script is finding non-IU IUs to install > ----------------------------------------------------------- > > Key: JBIDE-19449 > URL: https://issues.jboss.org/browse/JBIDE-19449 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > p2.director install script is finding non-IU IUs to install such as: > {code}eclipse.buildId > java.version{code} > {code} > list.ius: > [echo] Searching for IUs in http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... with -list 'Q:everything.select(y | everything.select(x | x.properties ~= filter("(org.eclipse.equinox.p2.bundle.localization='plugin')")).collect(x | x.requirements).flatten().exists(r | y ~= r))' ... > [echo] Result: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > [echo] IU list written to /qa/hudson_workspace/workspace/jbosstools-composite-install_master/data/plugin.list.properties > {code} > Full list here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > Reason: here's what's in the plugin.list.properties file: > {code} > !SESSION 2015-03-13 18:06:15.934 ----------------------------------------------- > eclipse.buildId=4.5.0.I20150203-1300 > java.version=1.8.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > !ENTRY org.eclipse.osgi 4 0 2015-03-13 18:06:17.233 > !MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: /qa/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/org.eclipse.osgi > org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. > ch.qos.logback.classic=1.0.7.v20121108-1250 > ch.qos.logback.core=1.0.7.v20121108-1250 > ... > tern.server.nodejs=0.9.0.201502141213 > ternjs=0.9.0.201502141213 > Operation completed in 183432 ms. > {code} > So we need to filter out the header garbage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19449) p2.director install script is finding non-IU IUs to install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19449?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19449: ------------------------------- Sprint: Sprint #1 April 2015 (was: Sprint #2 April 2015) > p2.director install script is finding non-IU IUs to install > ----------------------------------------------------------- > > Key: JBIDE-19449 > URL: https://issues.jboss.org/browse/JBIDE-19449 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > p2.director install script is finding non-IU IUs to install such as: > {code}eclipse.buildId > java.version{code} > {code} > list.ius: > [echo] Searching for IUs in http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... with -list 'Q:everything.select(y | everything.select(x | x.properties ~= filter("(org.eclipse.equinox.p2.bundle.localization='plugin')")).collect(x | x.requirements).flatten().exists(r | y ~= r))' ... > [echo] Result: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > [echo] IU list written to /qa/hudson_workspace/workspace/jbosstools-composite-install_master/data/plugin.list.properties > {code} > Full list here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > Reason: here's what's in the plugin.list.properties file: > {code} > !SESSION 2015-03-13 18:06:15.934 ----------------------------------------------- > eclipse.buildId=4.5.0.I20150203-1300 > java.version=1.8.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > !ENTRY org.eclipse.osgi 4 0 2015-03-13 18:06:17.233 > !MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: /qa/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/org.eclipse.osgi > org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. > ch.qos.logback.classic=1.0.7.v20121108-1250 > ch.qos.logback.core=1.0.7.v20121108-1250 > ... > tern.server.nodejs=0.9.0.201502141213 > ternjs=0.9.0.201502141213 > Operation completed in 183432 ms. > {code} > So we need to filter out the header garbage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19416) JBDS update site zip should not include both packed and unpacked artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19416?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19416: ------------------------------- Sprint: Sprint #2 April 2015 > JBDS update site zip should not include both packed and unpacked artifacts > -------------------------------------------------------------------------- > > Key: JBIDE-19416 > URL: https://issues.jboss.org/browse/JBIDE-19416 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.3.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.3.0.Beta1 > > > JBDS 8.1.0.Beta1 update site zip is 524M and contains both packed (.pack.gz) and regular jars; no need to include both. Ideally we'd include ONLY the packed ones. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19458) Use jbosstools_site_update in Jenkins jobs and jbosstools-site-update in parent pom for "consistency" & "less confusion"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19458?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19458: ------------------------------- Sprint: Sprint #1 April 2015 > Use jbosstools_site_update in Jenkins jobs and jbosstools-site-update in parent pom for "consistency" & "less confusion" > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19458 > URL: https://issues.jboss.org/browse/JBIDE-19458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Max wants that: > * the parameter we use in Jenkins be *jbosstools_site_stream* (underscores) and that > * the maven processes all use *jbosstools-site-stream* (dashes) > Because > * Max feels that using a different parameter in Jenkins than the value in the parent pom is more consistent & less likely to cause problems, vs. > * renaming the variable so that both use the same underscored name of jbosstools_stream. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3351: ----------------------------- Sprint: Sprint #1 April 2015 > Copyright notice refers to 2014, not 2015 > ----------------------------------------- > > Key: JBDS-3351 > URL: https://issues.jboss.org/browse/JBDS-3351 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Trivial > Fix For: 9.0.0.Alpha2 > > > The copyright notice for 9.0.0.Alpha1 reads: > ==================================== > Version: 9.0.0.Alpha1 > Build id: Alpha1-v20150216-1042-B11 > Build date: 20150216-1042 > Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved. > ==================================== > ------> Shouldn't this refer to 2004-2015? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3367) Offline update from 8.0.x fails in installing FeedHenry

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3367?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3367: ----------------------------- Sprint: Sprint #2 April 2015 > Offline update from 8.0.x fails in installing FeedHenry > ------------------------------------------------------- > > Key: JBDS-3367 > URL: https://issues.jboss.org/browse/JBDS-3367 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 8.1.0.Beta1 > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Updating from 8.0.0, 8.0.1 and 8.0.2 from the update zip causes the following error: > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85) > Missing requirement: org.jboss.tools.feedhenry.ui 1.0.0.Beta1-v20150225-2159-B85 requires 'bundle org.jboss.tools.vpe.cordovasim.eclipse 3.6.2' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85) > To: org.jboss.tools.feedhenry.ui [1.0.0.Beta1-v20150225-2159-B85] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18914: ------------------------------- Sprint: Sprint #2 April 2015 > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3286) Remove Seam tooling from default JBDS installation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3286?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3286: ----------------------------- Sprint: Sprint #1 April 2015 > Remove Seam tooling from default JBDS installation > -------------------------------------------------- > > Key: JBDS-3286 > URL: https://issues.jboss.org/browse/JBDS-3286 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, installer, requirements, seam > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > With Seam being pretty much dead and the tools in maintenance mode, I'm opening this issue to discuss whether we should drop Seam from the JBDS installer and only keep it available from JBoss Central (required as part of JBIDE-18922 already). > [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray] : WDYT? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3208: ----------------------------- Sprint: Sprint #1 April 2015 > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > Latest suggestion: > * /\{mars,9.0}/ > ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/ > *** /*updates*/ > **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/ > ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/ > *** /*builds*/ > **** /<job-name>/ > ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/ > --- > Older idea: > {code} > <download.jboss.org,devstudio.redhat.com> > <earlyaccess,updates,discovery>/<mars,9.0> > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last N builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3191: ----------------------------- Sprint: Sprint #2 April 2015 > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3163: ----------------------------- Sprint: Sprint #1 April 2015 > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. > --- > After much discussion it's been decided that: > * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. > * Installers will remain internal-only until they're released and available on CSP and www.jboss.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3200: ------------------------------------- I am not familiar with it, but I guess it is a matter of enrollment in apple dev program and signing the installer jar. Does that sound right? > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18236) Produce better doc for project leads for how to build their component in Jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18236?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18236: ------------------------------- Sprint: Sprint #2 April 2015 > Produce better doc for project leads for how to build their component in Jenkins > -------------------------------------------------------------------------------- > > Key: JBIDE-18236 > URL: https://issues.jboss.org/browse/JBIDE-18236 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Max wants a page with links to all the /build pages for all the Jenkins jobs for a given stream, ie., 4.2.luna, 4.3.mars, master. > This could be awestructed adoc, or just static HTML a la http://download.jboss.org/jbosstools/builds/cascade pages. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create p2diff job to verify that nightly build is different from previous milestone

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16970: ------------------------------- Sprint: Sprint #2 April 2015 > create p2diff job to verify that nightly build is different from previous milestone > ----------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19331) Links to JBDS release notes broken

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19331?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19331. --------------------------------- Verified. > Links to JBDS release notes broken > ---------------------------------- > > Key: JBIDE-19331 > URL: https://issues.jboss.org/browse/JBIDE-19331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.2.1.Final > > > This page has a link to release notes which is broken: > http://tools.jboss.org/downloads/devstudio/luna/8.0.2.GA.html > It points to https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > The same problem happens for JBDS 8.0.1 and 8.0.0. > The correct link is e.g.: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > So it seems we just need to trim off the trailing index.html . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15482: ------------------------------- Sprint: Sprint #1 April 2015 > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: f2f2014 > Fix For: 4.3.0.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19578) Connection wizard: username/password are not filled in if I select an existing connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19578?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19578: ------------------------------------- Labels: connection_wizard (was: ) > Connection wizard: username/password are not filled in if I select an existing connection > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19578 > URL: https://issues.jboss.org/browse/JBIDE-19578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: connection-wizard-existing.png, connection-wizard-new.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19578) Connection wizard: username/password are not filled in if I select an existing connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19578?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19578: ------------------------------------------ merged and pushed to upstream/master > Connection wizard: username/password are not filled in if I select an existing connection > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19578 > URL: https://issues.jboss.org/browse/JBIDE-19578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: connection-wizard-existing.png, connection-wizard-new.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3200: ----------------------------------------- Assignee: Denis Golovin > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19587) Build failure on Jenkins after TP upgrade

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19587: ------------------------------------- Summary: Build failure on Jenkins after TP upgrade Key: JBIDE-19587 URL: https://issues.jboss.org/browse/JBIDE-19587 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload Affects Versions: 4.3.0.Alpha2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.3.0.Alpha2 Some build failures reported on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-livereload... after JBIDE-19585 (although the exception do not seem to be related to Jetty but rather to Mockito) {code} java.lang.ClassCastException: org.mockito.internal.creation.jmock.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByMockitoWithCGLIB$$4e962fbf cannot be cast to org.eclipse.wst.server.core.model.ServerBehaviourDelegate at org.jboss.tools.livereload.internal.util.WSTUtilsTestCase.setup(WSTUtilsTestCase.java:72) {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19586) Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19586?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19586: ------------------------------------- Attachment: loading-v3-connection.png unauthorized-error-dialog.png > Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays > ---------------------------------------------------------------------------------- > > Key: JBIDE-19586 > URL: https://issues.jboss.org/browse/JBIDE-19586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Attachments: loading-v3-connection.png, unauthorized-error-dialog.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19586) Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19586?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19586: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays > ---------------------------------------------------------------------------------- > > Key: JBIDE-19586 > URL: https://issues.jboss.org/browse/JBIDE-19586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: loading-v3-connection.png, unauthorized-error-dialog.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19586) Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19586: ---------------------------------------- Summary: Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays Key: JBIDE-19586 URL: https://issues.jboss.org/browse/JBIDE-19586 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha2 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3200: ------------------------------------- Interestingly, I just changed my settings to the middle option (Allow apps downloaded from Mac app store and identified developers) which originally triggered the warning when double clicking the installer jar, but now I get no warning with jboss-devstudio-9.0.0.Alpha2-v20150414-1031-B2948-installer-standalone.jar. Neither do I get a warning when I double click JBDS 8.0.0.GA installer jar. And now I can see why - this problem happens when the file is in quarantine, i.e. when you download it with your browser. But it's kind of strange. Because the security settings should apply to both quarantined and non-quarantined files. I thought the quarantine would just throw an extra warning which you can dismiss. Anyway, just wanted to share this. > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19582) eclipse freezes after first start

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19582?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19582: ------------------------------------- Seems extremely strange... Class=RemoteJavaApplicationLaunchShortcut and the only other code that references it is the extension pt org.eclipse.debug.ui.launchShortcuts. So I can't see how that's possibly being run on its own. Breakpoints fail to replicate for me. > eclipse freezes after first start > --------------------------------- > > Key: JBIDE-19582 > URL: https://issues.jboss.org/browse/JBIDE-19582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Environment: Mac OS X Yosemite 10.10.1, Java 1.7 > Reporter: Denis Golovin > Assignee: Rob Stryker > > {code}Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode): > "Attach Listener" daemon prio=5 tid=0x00000001021be800 nid=0x108bf runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Provisioning Event Dispatcher" daemon prio=5 tid=0x00000008e07a4000 nid=0xe24b in Object.wait() [0x00000008e2400000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Worker-5" prio=5 tid=0x00000001020b0000 nid=0xc803 in Object.wait() [0x00000008e2676000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) > - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52) > "Worker-3" prio=5 tid=0x0000000101b68000 nid=0xc613 in Object.wait() [0x00000008e166d000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) > - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52) > "EventAdmin Async Event Dispatcher Thread" daemon prio=5 tid=0x000000010138c800 nid=0x8c2b in Object.wait() [0x00000008e0ed3000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:200) > - locked <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4754) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212) > at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > "Timer-0" daemon prio=5 tid=0x00000008e05d9000 nid=0x653b runnable [0x00000008e0dcf000] > java.lang.Thread.State: RUNNABLE > at java.util.regex.Pattern$BnM.optimize(Pattern.java:5334) > at java.util.regex.Pattern.compile(Pattern.java:1678) > at java.util.regex.Pattern.<init>(Pattern.java:1337) > at java.util.regex.Pattern.compile(Pattern.java:1022) > at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:82) > at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:66) > at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.<init>(MonitoredHostProvider.java:59) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:214) > at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:143) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:507) > - locked <0x0000000112421e68> (a org.jboss.tools.common.jdt.debug.tools.internal.Tools) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:517) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:150) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > "[ThreadPool Manager] - Idle Thread" daemon prio=5 tid=0x00000001008f8000 nid=0x8b5f in Object.wait() [0x00000008e0b65000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106) > - locked <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor) > "Java indexing" daemon prio=5 tid=0x0000000100a09800 nid=0xb867 in Object.wait() [0x00000008dfd0f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:382) > - locked <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) > at java.lang.Thread.run(Thread.java:722) > "Bundle File Closer" daemon prio=5 tid=0x00000008e01a6000 nid=0xb78b in Object.wait() [0x00000008df592000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "EMF Reference Cleaner" daemon prio=5 tid=0x00000001010d1800 nid=0x9503 in Object.wait() [0x00000008df3de000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at org.eclipse.emf.common.util.CommonUtil$1ReferenceClearingQueuePollingThread.run(CommonUtil.java:70) > "Worker-JM" prio=5 tid=0x0000000100a66000 nid=0x932b in Object.wait() [0x00000008df99d000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939c88> (a java.util.ArrayList) > at org.eclipse.core.internal.jobs.InternalWorker.run(InternalWorker.java:59) > - locked <0x0000000112939c88> (a java.util.ArrayList) > "[Timer] - Main Queue Handler" daemon prio=5 tid=0x0000000101271800 nid=0x9027 in Object.wait() [0x00000008df868000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939e18> (a java.lang.Object) > at org.eclipse.equinox.internal.util.impl.tpt.timer.TimerImpl.run(TimerImpl.java:141) > - locked <0x0000000112939e18> (a java.lang.Object) > at java.lang.Thread.run(Thread.java:722) > "Start Level: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x000000010115d000 nid=0x8f03 in Object.wait() [0x00000008df2db000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Framework Event Dispatcher: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x0000000100a96000 nid=0x8d0f in Object.wait() [0x00000008df1d8000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Active Thread: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" prio=5 tid=0x0000000100a2f800 nid=0x8e07 waiting on condition [0x00000008dedff000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x0000000112523618> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > "Service Thread" daemon prio=5 tid=0x00000001010a5000 nid=0x5b03 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread1" daemon prio=5 tid=0x00000001010a4000 nid=0x5a03 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" daemon prio=5 tid=0x000000010109f800 nid=0x5907 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" daemon prio=5 tid=0x0000000100851000 nid=0x570f runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" daemon prio=5 tid=0x0000000101092000 nid=0x5503 in Object.wait() [0x00000008db873000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:177) > "Reference Handler" daemon prio=5 tid=0x000000010108b800 nid=0x5403 in Object.wait() [0x00000008db770000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000001125353b0> (a java.lang.ref.Reference$Lock) > at java.lang.Object.wait(Object.java:503) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133) > - locked <0x00000001125353b0> (a java.lang.ref.Reference$Lock) > "main" prio=5 tid=0x000000010200b800 nid=0x130f runnable [0x00007fff5fbfc000] > java.lang.Thread.State: RUNNABLE > at org.eclipse.core.commands.common.HandleObject.hashCode(HandleObject.java:137) > at org.eclipse.core.internal.commands.util.Util.hashCode(Util.java:266) > at org.eclipse.core.commands.ParameterizedCommand.hashCode(ParameterizedCommand.java:615) > at java.util.HashMap.hash(HashMap.java:351) > at java.util.HashMap.getEntry(HashMap.java:443) > at java.util.HashMap.get(HashMap.java:405) > at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor(BindingManager.java:1161) > at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor1(BindingManager.java:1210) > at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1275) > at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1265) > at org.eclipse.jface.action.ExternalActionManager$CommandCallback.getAcceleratorText(ExternalActionManager.java:323) > at org.eclipse.jface.action.ActionContributionItem.update(ActionContributionItem.java:907) > at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859) > at org.eclipse.jface.action.SubMenuManager.update(SubMenuManager.java:343) > at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859) > at org.eclipse.ui.internal.Workbench.updateActiveWorkbenchWindowMenuManager(Workbench.java:3373) > at org.eclipse.ui.internal.Workbench.access$0(Workbench.java:3359) > at org.eclipse.ui.internal.Workbench$1.bindingManagerChanged(Workbench.java:3354) > at org.eclipse.jface.bindings.BindingManager.fireBindingManagerChanged(BindingManager.java:901) > at org.eclipse.jface.bindings.BindingManager.setActiveBindings(BindingManager.java:2178) > at org.eclipse.jface.bindings.BindingManager.recomputeBindings(BindingManager.java:1743) > at org.eclipse.jface.bindings.BindingManager.contextManagerChanged(BindingManager.java:690) > at org.eclipse.core.commands.contexts.ContextManager.fireContextManagerChanged(ContextManager.java:165) > at org.eclipse.core.commands.contexts.ContextManager.setActiveContextIds(ContextManager.java:295) > at org.eclipse.e4.ui.services.ContextServiceAddon$1.changed(ContextServiceAddon.java:47) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110) > at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:333) > at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:347) > at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:191) > at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener$3.widgetDisposed(ShellActivationListener.java:182) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1471) > at org.eclipse.swt.widgets.Widget.release(Widget.java:1308) > at org.eclipse.swt.widgets.Control.release(Control.java:2867) > at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671) > at org.eclipse.jface.window.Window.close(Window.java:334) > at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:990) > at org.eclipse.jface.dialogs.MessageDialog.buttonPressed(MessageDialog.java:204) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:330) > at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:360) > at org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:455) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.showDialog(RemoteJavaApplicationLaunchShortcut.java:186) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.access$2(RemoteJavaApplicationLaunchShortcut.java:183) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut$1$2.run(RemoteJavaApplicationLaunchShortcut.java:116) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > - locked <0x000000011293a5a8> (a org.eclipse.swt.widgets.RunnableLock) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > "VM Thread" prio=5 tid=0x000000010200c000 nid=0x5303 runnable > "GC task thread#0 (ParallelGC)" prio=5 tid=0x0000000100832000 nid=0x4f03 runnable > "GC task thread#1 (ParallelGC)" prio=5 tid=0x0000000101054800 nid=0x5003 runnable > "GC task thread#2 (ParallelGC)" prio=5 tid=0x000000010104f800 nid=0x5103 runnable > "GC task thread#3 (ParallelGC)" prio=5 tid=0x000000010105d800 nid=0x5203 runnable > "VM Periodic Task Thread" prio=5 tid=0x0000000100851800 nid=0x5c03 waiting on condition > JNI global references: 911{code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3405) Installer step 4 empty and NPE thrown

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3405?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3405: ------------------------------------- This seems fixed in latest nightly (jboss-devstudio-9.0.0.Alpha2-v20150414-1031-B2948-installer-standalone.jar). Well done! :) > Installer step 4 empty and NPE thrown > ------------------------------------- > > Key: JBDS-3405 > URL: https://issues.jboss.org/browse/JBDS-3405 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha2 > > Attachments: step4-empty.png > > > When you try to install JBDS using the standalone installer, in Step 4: Select Java VM, the page is empty and there is a NPE thrown in the terminal: > {code} > nattura:9.0.0 rasp$ java -jar jboss-devstudio-9.0.0.Alpha2-v20150413-0429-B2940-installer-standalone.jar > java.lang.NullPointerException > at com.jboss.devstudio.core.installer.JREPathPanel.change(JREPathPanel.java:483) > at com.jboss.devstudio.core.installer.PathSelectionPanel.fireChange(PathSelectionPanel.java:237) > at com.jboss.devstudio.core.installer.PathSelectionPanel.access$000(PathSelectionPanel.java:34) > at com.jboss.devstudio.core.installer.PathSelectionPanel$1.insertUpdate(PathSelectionPanel.java:101) > at javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:202) > at javax.swing.text.AbstractDocument.handleInsertString(AbstractDocument.java:749) > at javax.swing.text.AbstractDocument.insertString(AbstractDocument.java:708) > at javax.swing.text.PlainDocument.insertString(PlainDocument.java:130) > at javax.swing.text.AbstractDocument.replace(AbstractDocument.java:670) > at javax.swing.text.JTextComponent.setText(JTextComponent.java:1718) > at com.jboss.devstudio.core.installer.PathSelectionPanel.setPath(PathSelectionPanel.java:202) > at com.jboss.devstudio.core.installer.JREPathPanel.updateJava(JREPathPanel.java:287) > at com.jboss.devstudio.core.installer.JREPathPanel.panelActivate(JREPathPanel.java:273) > at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864) > at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475) > at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1443) > at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionPerformed(InstallerFrame.java:1585) > at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018) > at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341) > at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402) > at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259) > at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252) > at java.awt.Component.processMouseEvent(Component.java:6516) > at javax.swing.JComponent.processMouseEvent(JComponent.java:3320) > at java.awt.Component.processEvent(Component.java:6281) > at java.awt.Container.processEvent(Container.java:2229) > at java.awt.Component.dispatchEventImpl(Component.java:4872) > at java.awt.Container.dispatchEventImpl(Container.java:2287) > at java.awt.Component.dispatchEvent(Component.java:4698) > at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4832) > at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4492) > at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4422) > at java.awt.Container.dispatchEventImpl(Container.java:2273) > at java.awt.Window.dispatchEventImpl(Window.java:2719) > at java.awt.Component.dispatchEvent(Component.java:4698) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:735) > at java.awt.EventQueue.access$200(EventQueue.java:103) > at java.awt.EventQueue$3.run(EventQueue.java:694) > at java.awt.EventQueue$3.run(EventQueue.java:692) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) > at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87) > at java.awt.EventQueue$4.run(EventQueue.java:708) > at java.awt.EventQueue$4.run(EventQueue.java:706) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:705) > at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) > at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:91) > {code} > !step4-empty.png! > When you go back one page and forth again, it will work then. > BTW, this happens on JBDS 9.0.0.Alpha2 nightly build from master - jboss-devstudio-9.0.0.Alpha2-v20150413-0429-B2940-installer-standalone.jar . And it happens to me on OS X 10.10 Yosemite with java 7 and the same thing happened to [~psrna] also on OS X today. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19527) [FeedHenry] UnknownHostException should be handled in UI/wizard and displayed to user with an error message

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19527?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19527: --------------------------------- Summary: [FeedHenry] UnknownHostException should be handled in UI/wizard and displayed to user with an error message (was: UnknownHostException should be handled in UI/wizard and displayed to user with an error message) > [FeedHenry] UnknownHostException should be handled in UI/wizard and displayed to user with an error message > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19527 > URL: https://issues.jboss.org/browse/JBIDE-19527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.3.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.0.Alpha2 > > > {code} > org.jboss.tools.feedhenry.ui.model.FeedHenryException: Error occured while communicating with the FeedHenry server > at org.jboss.tools.feedhenry.ui.model.FeedHenry.doAPICall(FeedHenry.java:102) > at org.jboss.tools.feedhenry.ui.model.FeedHenry.listProjects(FeedHenry.java:44) > at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector.prepareInput(FeedHenryApplicationSelector.java:220) > at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector.access$0(FeedHenryApplicationSelector.java:208) > at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector$1.run(FeedHenryApplicationSelector.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.cz: nodename nor servname provided, or not known > at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) > at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901) > at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1293) > at java.net.InetAddress.getAllByName0(InetAddress.java:1246) > at java.net.InetAddress.getAllByName(InetAddress.java:1162) > at java.net.InetAddress.getAllByName(InetAddress.java:1098) > at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44) > at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:259) > at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:159) > at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304) > at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) > at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) > at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) > at org.jboss.tools.feedhenry.ui.model.FeedHenry.doAPICall(FeedHenry.java:84) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3268) [FeedHenry] Export a Cordova Application created using JBDS to FeedHenry

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3268?page=com.atlassian.jira.plugin.... ] Gorkem Ercan updated JBDS-3268: ------------------------------- Summary: [FeedHenry] Export a Cordova Application created using JBDS to FeedHenry (was: Export a Cordova Application created using JBDS to FeedHenry) > [FeedHenry] Export a Cordova Application created using JBDS to FeedHenry > ------------------------------------------------------------------------ > > Key: JBDS-3268 > URL: https://issues.jboss.org/browse/JBDS-3268 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 9.0.0.CR1 > > > As a HTML5-focused mobile application developer, I wish to use JBoss Tools and JBDS to craft my AngularJS+Ionic or jQuery Mobile-based application, testing it via CordovaSim, deploy the application to my iOS and/or Android phone and when I feel it is "about right", push it to FeedHenry's git URL. > It is currently unclear how an end-user takes his/her JBDS Hybrid Mobile (Cordova) project and sets it up to support a git push to FH. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-18542 at 4/14/15 9:03 AM: ----------------------------------------------------------------- Deferring to Beta1, since it's still mysterious why we get "null" at that time. was (Author: mickael_istria): Deferring to Alpha2, since it's still mysterious why we get "null" at that time. > NPE during "Check installation for Early Access" > ------------------------------------------------ > > Key: JBIDE-18542 > URL: https://issues.jboss.org/browse/JBIDE-18542 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Rob Cernich > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.x, 4.3.0.Beta1 > > > I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/ > {noformat} > java.lang.NullPointerException > at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99) > at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) > at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) > at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18542: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > NPE during "Check installation for Early Access" > ------------------------------------------------ > > Key: JBIDE-18542 > URL: https://issues.jboss.org/browse/JBIDE-18542 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Rob Cernich > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.x, 4.3.0.Beta1 > > > I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/ > {noformat} > java.lang.NullPointerException > at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99) > at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) > at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) > at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-11301) no stacktrace when junit tests fail

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-11301. ---------------------------------- Resolution: Migrated to another ITS Issue tracked on Tycho side: https://bugs.eclipse.org/bugs/show_bug.cgi?id=378938 > no stacktrace when junit tests fail > ----------------------------------- > > Key: JBIDE-11301 > URL: https://issues.jboss.org/browse/JBIDE-11301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 3.3.0.Beta3 > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Priority: Minor > Fix For: LATER > > > If I run JBT tycho build locally for trunk, for example: > mvn clean install -fae -e -P default -f cdi/tests/pom.xml > and there is some test failures then I don't see any stacktrace in console. Just a text message from the JUnit test assert. > -Dsurefire.useFile=false does not help. > But I see the stacktrace in <target>/surefire-reports > In Beta1 branch it works fine. > I don't see stacktrace in console output in Hudson either but I'm not sure it's a problem there. > For example https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... > But for local builds it's very useful to see the full stacktrace in console. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3200: -------------------------------------- As I don't have a Mac to reproduce and don't know the various way a Mac can complain, I'm not a good assignee for this issue. > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Mickael Istria reassigned JBDS-3200: ------------------------------------ Assignee: (was: Mickael Istria) > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-18542 at 4/14/15 8:56 AM: ----------------------------------------------------------------- Deferring to Alpha2, since it's still mysterious why we get "null" at that time. was (Author: mickael_istria): Deferring to Alpha2, since it's still mysterious why we get a NPE at that time. > NPE during "Check installation for Early Access" > ------------------------------------------------ > > Key: JBIDE-18542 > URL: https://issues.jboss.org/browse/JBIDE-18542 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Rob Cernich > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.x, 4.3.0.Alpha2 > > > I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/ > {noformat} > java.lang.NullPointerException > at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99) > at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) > at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) > at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18542: ---------------------------------------- Deferring to Alpha2, since it's still mysterious why we get a NPE at that time. > NPE during "Check installation for Early Access" > ------------------------------------------------ > > Key: JBIDE-18542 > URL: https://issues.jboss.org/browse/JBIDE-18542 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Rob Cernich > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.x, 4.3.0.Alpha2 > > > I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/ > {noformat} > java.lang.NullPointerException > at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99) > at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) > at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) > at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-15332: ----------------------------------- Fix Version/s: LATER (was: 4.3.0.Alpha2) > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19585. ------------------------------------ Fix Version/s: 4.3.0.Alpha2 Resolution: Done Change was merged. TP is respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19585: -------------------------------------- Assignee: Ilya Buziuk > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Minor > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3285: -------------------------------------- Added Easymport feature to Central: https://github.com/jbosstools/jbosstools-central/pull/330 [~fbricon] Can you please merge it ASAP? this new feature has to get into the aggregator and then into the product definition. > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3285: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/140, https://github.com/jbosstools/jbosstools-central/pull/330 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/140) > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19585: --------------------------------------- It's fine for me, too. > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Priority: Minor > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18772: ----------------------------------- Priority: Critical (was: Major) > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18772: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18772: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19025: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19457) implement wtp servertools integration with "launchbar"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19457?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19457: -------------------------------- Sprint: Sprint #2 April 2015 > implement wtp servertools integration with "launchbar" > ------------------------------------------------------- > > Key: JBIDE-19457 > URL: https://issues.jboss.org/browse/JBIDE-19457 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > The launchbar is a new concept introduced in CDT (with no cdt deps) that allows for a more extensible and faster launching experience. > This should integrate with the run as -> Run on server APIs to enhance synnergy and other cool buzzwords. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18348) Add support for WildFly 9

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18348?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18348: ---------------------------------------- Sprint: Sprint #1 April 2015 > Add support for WildFly 9 > ------------------------- > > Key: JBIDE-18348 > URL: https://issues.jboss.org/browse/JBIDE-18348 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > Now that WildFly 9.0.0.Alpha1 is out, we need to make sure it works properly with JBT/JBDS. > I played with it a little, tried to start/stop, deploy a project and so far I haven't seen any issue. > Other than the one expected that is - when you add the server, you get a warning that the runtime version doesn't match - it detected 9, but 8 is expected. We need to deal with this somehow. > Runtime detection doesn't work. It find the server (although with a strange Type of "WILDFLY-FULL"), but doesn't actually add it. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-3235) Missing properties view for servers elements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3235?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-3235: --------------------------------------- Sprint: (was: Sprint #2 April 2015) > Missing properties view for servers elements > -------------------------------------------- > > Key: JBIDE-3235 > URL: https://issues.jboss.org/browse/JBIDE-3235 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 3.3.x > > > Before I could directly edit properties for ports in properties view. > Now I need to right click and choose Change Value and get a non-standard edit in the tree. > This I could probably live with if I could just double click the value and edit it like in properties view. > Properties view was though also nice to give other details than just access to edit. > i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-3235) Missing properties view for servers elements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3235?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-3235: --------------------------------------- Sprint: Sprint #2 April 2015 (was: Sprint #1 April 2015) > Missing properties view for servers elements > -------------------------------------------- > > Key: JBIDE-3235 > URL: https://issues.jboss.org/browse/JBIDE-3235 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 3.3.x > > > Before I could directly edit properties for ports in properties view. > Now I need to right click and choose Change Value and get a non-standard edit in the tree. > This I could probably live with if I could just double click the value and edit it like in properties view. > Properties view was though also nice to give other details than just access to edit. > i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19585: ---------------------------------------- [~xcoulon] Any objection against this change? > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Priority: Minor > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ] Konstantin Marmalyukov commented on JBDS-3263: ---------------------------------------------- Removing Visual/Source and Preview Tabs for Mac OS: https://github.com/jbosstools/jbosstools-vpe/pull/309 After applying PR jsp/xhtml editor on Mac will look like this http://screencast.com/t/HMIk2Or6 > Remove JSF Visual/Source and Preview Tabs > ----------------------------------------- > > Key: JBDS-3263 > URL: https://issues.jboss.org/browse/JBDS-3263 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 9.0.0.Beta2 > > > Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs. > http://www.screencast.com/t/wettTf6s6cU > http://www.screencast.com/t/zur1sCXmZ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19585: ------------------------------------- PR was sent - https://github.com/jbosstools/jbosstools-target-platforms/pull/141 There is a build failure for JBDS Unified (Aggregate) Target Platform & JBoss Tools Unified (Aggregate) Target Platform but I guess it's fine for now > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Priority: Minor > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17591: ---------------------------------------- Sprint: Sprint to Beta3 Release, Sprint #2 April 2015 (was: Sprint to Beta3 Release) > org.jboss.tools.common.el.core.test fails on Max OS X Mavericks > --------------------------------------------------------------- > > Key: JBIDE-17591 > URL: https://issues.jboss.org/browse/JBIDE-17591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.Beta2 > Environment: Mac OS X Mavericks > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.3.x > > Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt > > > {code}junit.framework.AssertionFailedError > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertNotNull(Assert.java:256) > at junit.framework.Assert.assertNotNull(Assert.java:248) > at junit.framework.TestCase.assertNotNull(TestCase.java:417) > at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86) > at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19585: ---------------------------------------- New mirror is available at http://download.jboss.org/jbosstools/updates/requirements/jetty/9.2.9.v20... . [~ibuziuk] Do you want to provide the pull request? > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Priority: Minor > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-15714: ------------------------------------------------ [~maxandersen] afaics yes. All prs are pushed, so marking this issue as resolved > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, firstTime.png, vpe.png, vpe2.gif > > > Dynamic content assist works with projects which are mature enough not to fail in runtime. > Open any html page with JBoss HTML Editor (AngularJS templates are *not* supported) where some controllers are available and try Ctrl+Space on any {{}}. > The very first time the message saying the data is loading will be shown (this message will be shown only once per editor): > !firstTime.png! > Press enter or Ctrl+Space again to see AngularJS proposals (if available): > !vpe2.gif! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19585: ----------------------------------- Priority: Minor (was: Major) > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Priority: Minor > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19585: ---------------------------------------- By the way, we get this minor version mismatch because the PR you provided for Jetty was based on an M5 TP (with Jetty 9.2.5) whereas the new M6 TP moved to Jetty 9.2.9. > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3200: -------------------------------------- [~maxandersen] I didn't do anything to ensure it works with JBDS 9 installer, but it seems to me that [~dgolovin] changed a few things yesterday. Maybe it's related. > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Mickael Istria > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19585: ---------------------------------------- Yes, since Jetty use semantic versioning, mixing 2 different "micro" versions shouldn't break. I'll prepare a mirror of Jetty 9.2.9 and update the bundles then. > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3200: ------------------------------------------- [~mickael_istria] did we do anything actively to ensure this now works in JBDS 9 installer ? > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Mickael Istria > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3200: ----------------------------------------- Assignee: Mickael Istria (was: Max Rydahl Andersen) > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Mickael Istria > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-19585: ----------------------------------- Summary: Mixture of jetty 9 bundles versions in the TP Key: JBIDE-19585 URL: https://issues.jboss.org/browse/JBIDE-19585 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.3.0.Alpha1 Reporter: Ilya Buziuk Basically, here is the list of jetty 9 bundles in the TP: 1. org.eclipse.jetty.http_9.2.9.v20150224.jar 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar 3. org.eclipse.jetty.http_9.2.9.v20150224.jar 4. org.eclipse.jetty.io_9.2.9.v20150224.jar 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar 7. org.eclipse.jetty.security_9.2.9.v20150224.jar 8. org.eclipse.jetty.server_9.2.9.v20150224.jar 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar 10. org.eclipse.jetty.util_9.2.9.v20150224.jar 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19569: ------------------------------------------------ {quote}n Mac I have no way to get back to the first page other than close and reopen the html{quote} sounds reasonable. I move this issue to Bela1 to see what we can do with it. > Unable to switch pages shown in visual preview when editing mobile html5 > ------------------------------------------------------------------------ > > Key: JBIDE-19569 > URL: https://issues.jboss.org/browse/JBIDE-19569 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Beta1 > > > I'm not sure if my use case is valid or not. > But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one. > So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview. > Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button? > But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :) > [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19569: ------------------------------------------- Fix Version/s: 4.3.0.Beta1 > Unable to switch pages shown in visual preview when editing mobile html5 > ------------------------------------------------------------------------ > > Key: JBIDE-19569 > URL: https://issues.jboss.org/browse/JBIDE-19569 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Beta1 > > > I'm not sure if my use case is valid or not. > But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one. > So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview. > Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button? > But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :) > [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15714: --------------------------------------------- UI screenshots looks good - this "angularjs ....try again" will onyl be shown in context {{| content assist so it wont show up everywhere, correct ? > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, firstTime.png, vpe.png, vpe2.gif > > > Dynamic content assist works with projects which are mature enough not to fail in runtime. > Open any html page with JBoss HTML Editor (AngularJS templates are *not* supported) where some controllers are available and try Ctrl+Space on any {{}}. > The very first time the message saying the data is loading will be shown (this message will be shown only once per editor): > !firstTime.png! > Press enter or Ctrl+Space again to see AngularJS proposals (if available): > !vpe2.gif! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015