[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip (or at least document the limitations)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2456 at 3/3/13 11:52 PM:
-----------------------------------------------------------
[~nickboldt]:
The link you gave no longer worked, presumably because I left it so long before coming back to the JIRA (sorry!) and the builds are marching forwards.
Instead I tried building the current source zip, so
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_tr...
and ran into errors (however I think these might be unconnected to the izPack issue):
{code}
[ERROR] Software being installed: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 requires 'com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT depends on: org.jboss.tools.maven.gwt.feature.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
{code}
Actually, this is caused by changing the baseline version of GWT in the Extras/Central site from 3.1 to 3.2, as in JBDS-2486.
was (Author: mmurray):
[~nickboldt]:
The link you gave no longer worked, presumably because I left it so long before coming back to the JIRA (sorry!) and the builds are marching forwards.
Instead I tried building the current source zip, so
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_tr...
and ran into errors (however I think these might be unconnected to the izPack issue):
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.apache.axis-1.4.0.v201005080400.jar/lib can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.eclipse.mylyn.discovery.ui-3.9.0.I20130205-1655.jar/lib-e3.5 can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.eclipse.mylyn.discovery.ui-3.9.0.I20130205-1655.jar/lib-e3.6 can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.jboss.tools.forge.runtime.ext-1.2.0.Alpha1-v20130227-0639-B24.jar/bin can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[INFO] Computing target platform for MavenProject: com.jboss.jbds.site:com.jboss.jbds.site.product:7.0.0-SNAPSHOT @ /home/mmurray/JBDS/BuildingZIP/devstudio/product/site/pom.xml
[INFO] Resolving dependencies of MavenProject: com.jboss.jbds.site:com.jboss.jbds.site.product:7.0.0-SNAPSHOT @ /home/mmurray/JBDS/BuildingZIP/devstudio/product/site/pom.xml
[INFO] Cannot complete the request. Generating details.
[INFO] Cannot complete the request. Generating details.
[INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 requires 'com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT depends on: org.jboss.tools.maven.gwt.feature.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:170)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77)
at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354)
at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
... 11 more
> JBDS should be buildable from source zip (or at least document the limitations)
> -------------------------------------------------------------------------------
>
> Key: JBDS-2456
> URL: https://issues.jboss.org/browse/JBDS-2456
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 7.0.0.Alpha2
>
>
> As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing:
> {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote}
> It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either).
> Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip (or at least document the limitations)
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2456:
---------------------------------------
[~nickboldt]:
The link you gave no longer worked, presumably because I left it so long before coming back to the JIRA (sorry!) and the builds are marching forwards.
Instead I tried building the current source zip, so
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_tr...
and ran into errors (however I think these might be unconnected to the izPack issue):
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.apache.axis-1.4.0.v201005080400.jar/lib can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.eclipse.mylyn.discovery.ui-3.9.0.I20130205-1655.jar/lib-e3.5 can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.eclipse.mylyn.discovery.ui-3.9.0.I20130205-1655.jar/lib-e3.6 can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.jboss.tools.forge.runtime.ext-1.2.0.Alpha1-v20130227-0639-B24.jar/bin can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[INFO] Computing target platform for MavenProject: com.jboss.jbds.site:com.jboss.jbds.site.product:7.0.0-SNAPSHOT @ /home/mmurray/JBDS/BuildingZIP/devstudio/product/site/pom.xml
[INFO] Resolving dependencies of MavenProject: com.jboss.jbds.site:com.jboss.jbds.site.product:7.0.0-SNAPSHOT @ /home/mmurray/JBDS/BuildingZIP/devstudio/product/site/pom.xml
[INFO] Cannot complete the request. Generating details.
[INFO] Cannot complete the request. Generating details.
[INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 requires 'com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT depends on: org.jboss.tools.maven.gwt.feature.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:170)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77)
at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354)
at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
... 11 more
> JBDS should be buildable from source zip (or at least document the limitations)
> -------------------------------------------------------------------------------
>
> Key: JBDS-2456
> URL: https://issues.jboss.org/browse/JBDS-2456
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 7.0.0.Alpha2
>
>
> As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing:
> {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote}
> It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either).
> Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (TOOLSDOC-251) Add documentation for Runtime detection
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-251?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-251:
------------------------------------------
I anticipate this being documented as follows:
Installation Guide:
* Install JBDS (with installer)
* Set up automatic runtime detection
Getting Started guide:
* Install JBDS (with installer)
* Set Up a Runtime Server Using Server Manager
User Guide:
* Set up automatic runtime detection
> Add documentation for Runtime detection
> ---------------------------------------
>
> Key: TOOLSDOC-251
> URL: https://issues.jboss.org/browse/TOOLSDOC-251
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Beginners Guide, Getting Started Guide
> Affects Versions: 3.2.2.Final
> Reporter: Libor Zoubek
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> Hi Isaac,
> I am going through begginers guide now (2.2.2. Adding a new application server for use with the JBoss Developer Studio). JBDS and JBoss Tools has a quite long time nice feature for adding server (and other) runtimes. I think it is a good idea to include it into guides or to switch current recommended way of adding runtimes to it - it is much more simple and it is one of many added values of JBT compared to eclipse.
> You can play with runtime detection if you open Preferences->Jboss Tools->Runtime Detection. Main idea is, that you just select any directory and JBT scans it recursively and searches for runtimes. If it founds any, you can select it to be added. Good thing is that both server runtime and server with all other runtimes (seam,jbpm) is added.
> You can contact Snjezana, she is developing runtime detectors and has much deeper details about it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13703) Team - Verify the workflow
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13703:
--------------------------------
Description:
The average end-user would like to:
1) check out (clone) a project from CVS, SVN or Git
-- add repo, navigate repo, check out a project
-- project may or may not have .classpath, .project or .settings files
-- project may be Maven-based
and see if the following work
2) Are the appropriate facets enabled?
3) Does it build immediately?
4) Can I immediately hit the run button to launch it on my app server?
5) Can I immediately hit the debug button to debug it on my app server?
-- how do I step if there are no break points?
6) Make a change to a file, re-run/debug again
7) Run JUnit tests
8) Check the change back into the repo with comments
was:
The average end-user would like to:
check out (clone) a project from CVS, SVN or Git
-- project may or may not have .classpath, .project or .settings files
-- project may be Maven-based
and see if the following work
2) Are the appropriate facets enabled?
3) Does it build immediately?
4) Can I immediately hit the run button to launch it on my app server?
5) Can I immediately hit the debug button to debug it on my favorite app server?
-- how do I step if there are no break points?
6) Make a change to a file
7) Run tests
8) Check the change back in with comments
> Team - Verify the workflow
> --------------------------
>
> Key: JBIDE-13703
> URL: https://issues.jboss.org/browse/JBIDE-13703
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Assignee: Burr Sutter
>
> The average end-user would like to:
> 1) check out (clone) a project from CVS, SVN or Git
> -- add repo, navigate repo, check out a project
> -- project may or may not have .classpath, .project or .settings files
> -- project may be Maven-based
> and see if the following work
> 2) Are the appropriate facets enabled?
> 3) Does it build immediately?
> 4) Can I immediately hit the run button to launch it on my app server?
> 5) Can I immediately hit the debug button to debug it on my app server?
> -- how do I step if there are no break points?
> 6) Make a change to a file, re-run/debug again
> 7) Run JUnit tests
> 8) Check the change back into the repo with comments
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-13335:
----------------------------------
Assignee: Denis Golovin (was: Nick Boldt)
[~dgolovin]: I can't apply this PR. Can you?
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13690) Detect future EAP 6 based server like SOA-P
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13690?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-13690:
---------------------------------------
@[~ldimaggio]: couldn't find any release for SOA-P based on EAP 6, where can I get it to run my local tests? Latest build from Jenkins?
> Detect future EAP 6 based server like SOA-P
> -------------------------------------------
>
> Key: JBIDE-13690
> URL: https://issues.jboss.org/browse/JBIDE-13690
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JBossAS/Servers, runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> To be sure future AS7/EAP 6 based servers such as SOA-P 6 can be detected and started as an EAP 6 we need to provide a fallback for this instead of the currrent hardcoding of eap slots.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13676) New Text Input wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13676?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13676:
-----------------------------------
Attachment: scr.png
> New Text Input wizard
> ---------------------
>
> Key: JBIDE-13676
> URL: https://issues.jboss.org/browse/JBIDE-13676
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
> Attachments: scr.png, TextInput.png, TextInputWizBan.png
>
>
> Text with all variations
> Wizard
> 1. Type: text/search/textarea/email/password/color/file etc.
> 2. Label:
> 3. ID:
> 4. Clear Button:
> 5. Placeholder:
> 6. Mini:
> 7. Disabled:
> 8. Hide Label:
> 9. Theme:
> Result
> Type=text
> <label for="text-3">Text input: data-clear-btn="true"</label>
> <input data-clear-btn="true" name="text-3" id="text-3" value="" type="text">
> Type=search
> <label for="search-1">Search:</label>
> <input name="search-1" id="search-1" value="" type="search">
> Type=textarea
> <label for="textarea-1">Textarea:</label>
> <textarea cols="40" rows="8" name="textarea-1" id="textarea-1"></textarea>
> and so on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13676) New Text Input wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13676?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13676:
-----------------------------------
Description:
Text with all variations
Wizard
1. Type: text/search/textarea/email/password/color/file etc.
2. Label:
3. ID:
4. Clear Button:
5. Placeholder:
6. Mini:
7. Disabled:
8. Hide Label:
9. Theme:
Result
Type=text
<label for="text-3">Text input: data-clear-btn="true"</label>
<input data-clear-btn="true" name="text-3" id="text-3" value="" type="text">
Type=search
<label for="search-1">Search:</label>
<input name="search-1" id="search-1" value="" type="search">
Type=textarea
<label for="textarea-1">Textarea:</label>
<textarea cols="40" rows="8" name="textarea-1" id="textarea-1"></textarea>
and so on.
!scr.png!
was:
Text with all variations
Wizard
1. Type: text/search/textarea/email/password/color/file etc.
2. Label:
3. ID:
4. Clear Button:
5. Placeholder:
6. Mini:
7. Disabled:
8. Hide Label:
9. Theme:
Result
Type=text
<label for="text-3">Text input: data-clear-btn="true"</label>
<input data-clear-btn="true" name="text-3" id="text-3" value="" type="text">
Type=search
<label for="search-1">Search:</label>
<input name="search-1" id="search-1" value="" type="search">
Type=textarea
<label for="textarea-1">Textarea:</label>
<textarea cols="40" rows="8" name="textarea-1" id="textarea-1"></textarea>
and so on.
> New Text Input wizard
> ---------------------
>
> Key: JBIDE-13676
> URL: https://issues.jboss.org/browse/JBIDE-13676
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
> Attachments: scr.png, TextInput.png, TextInputWizBan.png
>
>
> Text with all variations
> Wizard
> 1. Type: text/search/textarea/email/password/color/file etc.
> 2. Label:
> 3. ID:
> 4. Clear Button:
> 5. Placeholder:
> 6. Mini:
> 7. Disabled:
> 8. Hide Label:
> 9. Theme:
> Result
> Type=text
> <label for="text-3">Text input: data-clear-btn="true"</label>
> <input data-clear-btn="true" name="text-3" id="text-3" value="" type="text">
> Type=search
> <label for="search-1">Search:</label>
> <input name="search-1" id="search-1" value="" type="search">
> Type=textarea
> <label for="textarea-1">Textarea:</label>
> <textarea cols="40" rows="8" name="textarea-1" id="textarea-1"></textarea>
> and so on.
> !scr.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month