[JBoss JIRA] (JBIDE-21939) datatypes.dtd and properties.dtd not present in xml catalog
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21939?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21939.
---------------------------------
> datatypes.dtd and properties.dtd not present in xml catalog
> -----------------------------------------------------------
>
> Key: JBIDE-21939
> URL: https://issues.jboss.org/browse/JBIDE-21939
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM2
>
>
> Maybe this is not an issue at all but need to check.
> While verifying JBIDE-21690, I noticed that there are two dtd files that are not referenced in plugin.xml of org.jboss.tools.as.catalog_3.1.1.CR1-v20160316-0026-B106.jar .
> {code}
> $ for i in `find schema -name '*.dtd'`; do grep $i plugin.xml >/dev/null || echo $i not found; done
> schema/dtd/datatypes.dtd not found
> schema/dtd/properties.dtd not found
> {code}
> Is this ok or not?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Paul Leacu edited comment on JBTIS-654 at 7/21/16 10:13 AM:
------------------------------------------------------------
I finally had a chance to get back to this. The following PR does the following:
https://github.com/jbdevstudio/jbdevstudio-product/pull/389
- Establishes the ability to extend the devstudio installer with an arbitrary list of runtimes:
- the user selects these runtimes via a new izPack panel
(I didn't want to overload or confuse the purpose of the existing panels)
- if no runtimes are specified the panel is hidden
- the runtimes must be in zip format and are inflated into the devstudio "runtimes" directory
- the devstudio runtime detection feature will automatically initialize these runtime servers
- the added runtimes are defined in json format
- minimal impact to the existing devstudio installer
- added the ability to default select the runtimes
- Here's what a user would see - using the JBoss Fuse Server as an example:
[^inst1a.png]
[^inst2.png]
[^inst3.png]
[^inst4.png]
Since the Integration Stack will create the Fuse-specific installer, we can default the selection
of the Fuse Tooling feature and JBoss Fuse server. The only checkbox the user is required to select is the EULA. The user gets devstudio, Fuse Tooling and a Fuse Runtime in one (big) installer.
You can try the installer here - it currently fails when initializing the JBoss Fuse server (post runtime detection on startup). This is because the Neon Fuse Tooling bits aren't ready yet.
http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta...
[~dgolovin] - could you take a look at the PR. It's actually pretty compact and very similar to the p2 feature additions you added.
was (Author: pleacu):
I finally had a chance to get back to this. The following PR does the following:
https://github.com/jbdevstudio/jbdevstudio-product/pull/389
- Establishes the ability to extend the devstudio installer with an arbitrary list of runtimes:
- the user selects these runtimes via a new izPack panel
(I didn't want to overload or confuse the purpose of the existing panels)
- if no runtimes are specified the panel is hidden
- the runtimes must be in zip format and are inflated into the devstudio "runtimes" directory
- the devstudio runtime detection feature will automatically initialize these runtime servers
- the added runtimes are defined in json format
- minimal impact to the existing devstudio installer
- added the ability to default select the runtimes
- Here's what a user would see - using the JBoss Fuse Server as an example:
[^inst1a.png]
[^inst2.png]
[^inst3.png]
[^inst4.png]
Since the Integration Stack will create the Fuse-specific installer, we can default the selection
of the Fuse Tooling feature and JBoss Fuse server. The only checkbox the user is required to select
is the EULA. The user gets devstudio, Fuse Tooling and a Fuse Runtime in one (big) installer.
You can try the installer here - it currently fails when initializing the JBoss Fuse server (post runtime detection on startup). This is because the Neon Fuse Tooling bits aren't ready yet.
http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta...
[~dgolovin] - could you take a look at the PR. It's actually pretty compact and very similar to the p2 feature additions you added.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png, inst1.png, inst1a.png, inst2.png, inst3.png, inst4.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22772) jbosstools-server build fails - EAP 7 url needs updating
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22772?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22772:
---------------------------------------
[~fbricon], it looks correct.
I downloaded that url and checked the md5 and it matches the one from your PR:
{code}
$ axel http://download.devel.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0.zip
...
Downloaded 156,4 Megabyte in 20 seconds. (7930,26 KB/s)
$ md5 jboss-eap-7.0.0.zip
MD5 (jboss-eap-7.0.0.zip) = cd02482daa0398bf5500e1628d28179a
{code}
> jbosstools-server build fails - EAP 7 url needs updating
> --------------------------------------------------------
>
> Key: JBIDE-22772
> URL: https://issues.jboss.org/browse/JBIDE-22772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> jbosstools-server build has been failing since July 11.
> This is the error:
> {code}
> 02:30:17 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error: Could not get content -> [Help 1]
> 02:30:17 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 02:30:17 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 02:30:17 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 02:30:17 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 02:30:17 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 02:30:17 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 02:30:17 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 02:30:17 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 02:30:17 at java.lang.reflect.Method.invoke(Method.java:498)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 02:30:17 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 02:30:17 at com.googlecode.WGet.execute(WGet.java:260)
> 02:30:17 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 02:30:17 ... 19 more
> 02:30:17 Caused by: org.apache.maven.plugin.MojoFailureException: Could not get content
> 02:30:17 at com.googlecode.WGet.execute(WGet.java:248)
> 02:30:17 ... 21 more
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] For more information about the errors and possible solutions, please read the following articles:
> 02:30:17 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] After correcting the problems, you can resume the build with the command
> 02:30:17 [ERROR] mvn <goals> -rf :itests
> {code}
> See here:
> https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom...
> It contains an outdated link to EAP 7 ER5 build. EAP 7 GA is available for some time now, so we need to update the url.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-809) Cannot install Fuse tooling from EA without GA
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-809?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-809.
------------------------------
Fix Version/s: 9.0.1.CR3
Resolution: Done
Respin JBTIS and JBDSIS with JBTIS TP 4.3.2-SNAPSHOT. All components the same (just add some to EA for Fuse).
> Cannot install Fuse tooling from EA without GA
> ----------------------------------------------
>
> Key: JBTIS-809
> URL: https://issues.jboss.org/browse/JBTIS-809
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.1.GA
> Environment: JBDS-IS 9.0.1.CR2
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 9.0.1.CR3
>
>
> Cannot install Fuse tooling from EA without GA due to the following error
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959)
> Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found
> {code}
> the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22772) jbosstools-server build fails - EAP 7 url needs updating
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22772?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22772:
---------------------------------------
Oops, you were faster and more correct - I forgot the md5. I will check the md5.
> jbosstools-server build fails - EAP 7 url needs updating
> --------------------------------------------------------
>
> Key: JBIDE-22772
> URL: https://issues.jboss.org/browse/JBIDE-22772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> jbosstools-server build has been failing since July 11.
> This is the error:
> {code}
> 02:30:17 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error: Could not get content -> [Help 1]
> 02:30:17 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 02:30:17 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 02:30:17 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 02:30:17 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 02:30:17 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 02:30:17 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 02:30:17 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 02:30:17 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 02:30:17 at java.lang.reflect.Method.invoke(Method.java:498)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 02:30:17 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 02:30:17 at com.googlecode.WGet.execute(WGet.java:260)
> 02:30:17 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 02:30:17 ... 19 more
> 02:30:17 Caused by: org.apache.maven.plugin.MojoFailureException: Could not get content
> 02:30:17 at com.googlecode.WGet.execute(WGet.java:248)
> 02:30:17 ... 21 more
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] For more information about the errors and possible solutions, please read the following articles:
> 02:30:17 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] After correcting the problems, you can resume the build with the command
> 02:30:17 [ERROR] mvn <goals> -rf :itests
> {code}
> See here:
> https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom...
> It contains an outdated link to EAP 7 ER5 build. EAP 7 GA is available for some time now, so we need to update the url.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months