[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18813:
--------------------------------
Fix Version/s: 4.3.0.Alpha1
> Convert JBoss Central to an HTML5 page
> --------------------------------------
>
> Key: JBIDE-18813
> URL: https://issues.jboss.org/browse/JBIDE-18813
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha1
>
>
> Central Page requires new capabilities :
> - needs more customization (display content depending on user preferences)
> - needs to scale with JBDS-IS, Fuse content
> - access to more examples, with filtering capabilities
> Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach :
> - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility
> - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18812:
-------------------------------------
Summary: Unable to build Web Services
Key: JBIDE-18812
URL: https://issues.jboss.org/browse/JBIDE-18812
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform, webservices
Affects Versions: 4.3.0.Alpha1
Reporter: Xavier Coulon
When running a {{mvn clean verify}} on MacOSX, I get the following errors:
{{code}}
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
[INFO] Scanning for projects...
[WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
[WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-server (${jbosstools-server-site}): No connector available to access repository jbosstools-server (${jbosstools-server-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
[INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
[INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
[INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
[INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
[INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
[ERROR] Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86} -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.fixSWT(ProjectorResolutionStrategy.java:155)
at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:95)
at org.eclipse.tycho.p2.util.resolution.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:166)
at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:103)
at org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies(P2DependencyResolver.java:352)
at org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies(P2DependencyResolver.java:325)
at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:107)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
... 11 more
{{code}}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18387) HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>)
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18387?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-18387:
------------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.3.x)
> HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>)
> -----------------------------------------------------------------
>
> Key: JBIDE-18387
> URL: https://issues.jboss.org/browse/JBIDE-18387
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing, upstream
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
> Attachments: 00001262.png, bug444545.patch
>
>
> WTP HTML validator marks any custom html tags as unknown. It's possible to disable this validation at all: Window->Preferences->Web->HTML Files->Validation ==> Set Elements -> Unknown tag name severity to "Ignore":
> !00001262.png!
> But it would be useful to have ability to make HTML validator ignore some particular tags only.
> I suggest to contribute a patch to WTP to fix it.
> We have already did it for attributes, so lets do it for tags too:
> - New preferences with a list of ignored tags (a mask can be used)
> - A new preference page to set these preferences
> - QuickFix for validation problem which will add the tag name/mask to this list/preferences
> - Extension in our angular/ionic plugin which will disable validation for <ion-*> tags.
> I've filed it to bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545 but we have to provide a patch for it if we want to have it done ;)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBDS-3215) 3rd party certification for JBDS 8.0.1.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3215?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3215:
-----------------------------
Description:
For JBDS 8.0.1.GA, track changes since JBDS-2869 (8.0.0.GA release).
was:
For JBDS 8.0.1.GA, we need to ensure this list is as current and up to date as possible.
> 3rd party certification for JBDS 8.0.1.GA
> -----------------------------------------
>
> Key: JBDS-3215
> URL: https://issues.jboss.org/browse/JBDS-3215
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform
> Affects Versions: 8.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 8.0.1.GA
>
>
> For JBDS 8.0.1.GA, track changes since JBDS-2869 (8.0.0.GA release).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months