[JBoss JIRA] (LOCUS-23) New version of Saxon-HE required in locus
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/LOCUS-23?page=com.atlassian.jira.plugin.s... ]
Mickael Istria reassigned LOCUS-23:
-----------------------------------
Assignee: Mickael Istria
> New version of Saxon-HE required in locus
> -----------------------------------------
>
> Key: LOCUS-23
> URL: https://issues.jboss.org/browse/LOCUS-23
> Project: JBoss Tools Locus
> Issue Type: Feature Request
> Affects Versions: 1.1.0
> Reporter: Paul Richardson
> Assignee: Mickael Istria
> Fix For: 1.2.0
>
>
> The Teiid Server project has updated their dependencies, including increasing the Saxon-HE version to 9.1.5-6j.
> Since Teiid Designer takes a cut of the Teiid Server's client, it is necessary to update the Saxon-HE dependency in the former in order to remain in sync. Designer gets it Saxon library from the Locus repository.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19527) [FeedHenry] UnknownHostException should be handled in UI/wizard and displayed to user with an error message
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19527?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-19527.
------------------------------
> [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.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19453:
---------------------------------------------
I get same UI, but when making screen wider it does get shown eventually.
> Remote host information does not fit in the server editor
> ---------------------------------------------------------
>
> Key: JBIDE-19453
> URL: https://issues.jboss.org/browse/JBIDE-19453
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: remote-runtime-does-not-fit.png, server-editor-2.png
>
>
> Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it.
> !remote-runtime-does-not-fit.png!
> The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (LOCUS-15) Set version on exported packages
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/LOCUS-15?page=com.atlassian.jira.plugin.s... ]
Mickael Istria commented on LOCUS-15:
-------------------------------------
Orbit usually sets the package version to be equal to the one of bundle. However, there are some cases (such as com.google.inject) where the versions are different, without any obvious reason.
There is a risk of putting wrong versions in there. Indeed, versioning package has a strict semantic meaning and package version can often be lower than bundle version, so if we arbitrarily put a too high version on a package and that the project uses package versioning (without OSGi, but documented somewhere), then we can have our version conflicting with real ones...
> Set version on exported packages
> --------------------------------
>
> Key: LOCUS-15
> URL: https://issues.jboss.org/browse/LOCUS-15
> Project: JBoss Tools Locus
> Issue Type: Enhancement
> Affects Versions: 1.1.0
> Reporter: Mickael Istria
> Fix For: 1.2.0
>
>
> Locus bundles don't specify version for their exports, so they cannot be consumed by other bundles that use Import-Package with a version.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19715:
------------------------------------
TODOs:
* update all the jobs that currently rely on a /fullSite/ path to use /repository/ instead
* update repo-utils and jbosstools-build-ci *.sh scripts to use new path
* update jbosstools-discovery and ide-config.properties to ensure no references to /fullSite/ remain
* update JBT/JBDS release guides
* release new version of repo-utils and build-ci scripts
> Get rid of "fullSite", stick with "repository"
> ----------------------------------------------
>
> Key: JBIDE-19715
> URL: https://issues.jboss.org/browse/JBIDE-19715
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
>
> Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19715:
------------------------------------
Caveats:
* make sure the contents generated to /fullSite are the same as those in /repository today, so we're not losing functionality when generating over top in the same folder
* make sure branding and <references> removal in JBDS site continue to work correctly - see JBDS-3423, JBDS-3408
> Get rid of "fullSite", stick with "repository"
> ----------------------------------------------
>
> Key: JBIDE-19715
> URL: https://issues.jboss.org/browse/JBIDE-19715
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
>
> Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months