[JBoss JIRA] (JBIDE-23666) Update quickstarts on Central Home Page
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23666:
-------------------------------
Sprint: devex #169 July 2019
> Update quickstarts on Central Home Page
> ---------------------------------------
>
> Key: JBIDE-23666
> URL: https://issues.jboss.org/browse/JBIDE-23666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.3.AM1
> Environment: Red Hat JBoss Developer Studio
> Version: 10.3.0.AM1
> Build id: AM1-v20161225-1238-B6761
> Build date: 20161225-1238
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.0.AM1
>
>
> Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur:
> {code:java}
> Description Resource Path Location Type
> Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem
> No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem
> {code}
> For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-23666) Update quickstarts on Central Home Page
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23666:
----------------------------------
Assignee: André Dietisheim (was: Fred Bricon)
> Update quickstarts on Central Home Page
> ---------------------------------------
>
> Key: JBIDE-23666
> URL: https://issues.jboss.org/browse/JBIDE-23666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.3.AM1
> Environment: Red Hat JBoss Developer Studio
> Version: 10.3.0.AM1
> Build id: AM1-v20161225-1238-B6761
> Build date: 20161225-1238
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.0.AM1
>
>
> Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur:
> {code:java}
> Description Resource Path Location Type
> Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem
> No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem
> {code}
> For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-23666) Update quickstarts on Central Home Page
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23666:
-------------------------------
Fix Version/s: 4.13.0.AM1
(was: 4.12.x)
> Update quickstarts on Central Home Page
> ---------------------------------------
>
> Key: JBIDE-23666
> URL: https://issues.jboss.org/browse/JBIDE-23666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.3.AM1
> Environment: Red Hat JBoss Developer Studio
> Version: 10.3.0.AM1
> Build id: AM1-v20161225-1238-B6761
> Build date: 20161225-1238
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.0.AM1
>
>
> Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur:
> {code:java}
> Description Resource Path Location Type
> Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem
> No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem
> {code}
> For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-22578:
-------------------------------------
Fix Version/s: 4.12.0.Final
(was: LATER)
> Publishing sometimes recursively deletes parent to deploy directory
> -------------------------------------------------------------------
>
> Key: JBIDE-22578
> URL: https://issues.jboss.org/browse/JBIDE-22578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Final
> Environment: Eclipse Mars.2 Release (4.5.2)
> Java 1.8.0_91
> Windows 7 64-bit
> JBoss EAP 6.4.0
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.12.0.Final
>
> Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml
>
>
> For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it.
> It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools.
> We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx).
> Our workspaces are structured as follows:
> {noformat}
> WORKSPACEROOT=$DEVROOT\workspacename
> # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server
> $WORKSPACEROOT\deploy
> # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling
> $WORKSPACEROOT\src
> # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments
> $WORKSPACEROOT/server/data
> # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments
> $WORKSPACEROOT/server/tmp
> {noformat}
> The Server is configured to "Automatically publish when resources change".
> What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT.
> The eclipse log includes the following:
> {noformat}
> !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
> !MESSAGE Problems occurred refreshing resources
> !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
> !MESSAGE Problem finding next change, code: 5
> !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207
> !MESSAGE Incremental publish failed for module $MODULENAME
> !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207
> !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process.
> {noformat}
> Any idea what might be happening?
> Is there some debug logging we can enable to get better visibility to what's going on?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-22578:
------------------------------------------
Resolving this 3y+ old bug since we cannot reproduce it nor did we get more info on it.
> Publishing sometimes recursively deletes parent to deploy directory
> -------------------------------------------------------------------
>
> Key: JBIDE-22578
> URL: https://issues.jboss.org/browse/JBIDE-22578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Final
> Environment: Eclipse Mars.2 Release (4.5.2)
> Java 1.8.0_91
> Windows 7 64-bit
> JBoss EAP 6.4.0
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: LATER
>
> Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml
>
>
> For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it.
> It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools.
> We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx).
> Our workspaces are structured as follows:
> {noformat}
> WORKSPACEROOT=$DEVROOT\workspacename
> # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server
> $WORKSPACEROOT\deploy
> # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling
> $WORKSPACEROOT\src
> # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments
> $WORKSPACEROOT/server/data
> # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments
> $WORKSPACEROOT/server/tmp
> {noformat}
> The Server is configured to "Automatically publish when resources change".
> What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT.
> The eclipse log includes the following:
> {noformat}
> !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
> !MESSAGE Problems occurred refreshing resources
> !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
> !MESSAGE Problem finding next change, code: 5
> !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207
> !MESSAGE Incremental publish failed for module $MODULENAME
> !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207
> !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process.
> {noformat}
> Any idea what might be happening?
> Is there some debug logging we can enable to get better visibility to what's going on?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-23666) Update quickstarts on Central Home Page
by Bob Davis (Jira)
[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ]
Bob Davis commented on JBIDE-23666:
-----------------------------------
I approve of plan C:
bq. C. Remove quickstarts - and redirect user to repo with quickstarts.
> Update quickstarts on Central Home Page
> ---------------------------------------
>
> Key: JBIDE-23666
> URL: https://issues.jboss.org/browse/JBIDE-23666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.3.AM1
> Environment: Red Hat JBoss Developer Studio
> Version: 10.3.0.AM1
> Build id: AM1-v20161225-1238-B6761
> Build date: 20161225-1238
> Reporter: Josef Kopriva
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.12.x
>
>
> Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur:
> {code:java}
> Description Resource Path Location Type
> Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem
> No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem
> {code}
> For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26711) WildFly quickstart 'jaxws-retail' shows errors after import
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26711?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26711:
------------------------------------
Which tag of quickstart are you using ?
> WildFly quickstart 'jaxws-retail' shows errors after import
> -----------------------------------------------------------
>
> Key: JBIDE-26711
> URL: https://issues.jboss.org/browse/JBIDE-26711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.12.0.AM1
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: Problems view.png, Project Explorer.png
>
>
> h1. WildFly "jaxws-retail" quickstart contains the following errors:
> * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1 pom.xml
> * Missing artifact org.slf4j:slf4j-api:jar:1.7.22.jbossorg-1
> * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1
> * Missing artifact org.slf4j:slf4j-api:jar:1.7.22.jbossorg-1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-11338) JBoss AS 7.0.2 do not start when Java Agent is run and throws log error with JVM 6 update 15 and above
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-11338?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-11338:
------------------------------------
+1
> JBoss AS 7.0.2 do not start when Java Agent is run and throws log error with JVM 6 update 15 and above
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11338
> URL: https://issues.jboss.org/browse/JBIDE-11338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: profiler
> Affects Versions: LATER
> Reporter: Ramesh Pa
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: JBoss
> Fix For: LATER
>
>
> Workaround as below is also not working.
> set JAVA_OPTS= %JAVA_OPTS% -Xbootclasspath/p:C:\jboss-6.1.0.Final\lib\jboss-logmanager.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger .pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl
> No issues with JVM 6 update 14 and earlier.
> Error message
> INFO: 801. Dummy Java Agent:: Transformer to Transform Class: java/lang/ExceptionInInitializerError
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at org.jboss.as.server.Main.main(Main.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.modules.Module.run(Module.java:272)
> at org.jboss.modules.Main.main(Main.java:313)
> Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system proper
> ty to "org.jboss.logmanager.LogManager")
> at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
> at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
> ... 7 more
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-11172) Database Development: Postgres 9.1 tables are not listed
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-11172?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-11172:
------------------------------------
Or we can check if latest DTP fixes the issue.
> Database Development: Postgres 9.1 tables are not listed
> --------------------------------------------------------
>
> Key: JBIDE-11172
> URL: https://issues.jboss.org/browse/JBIDE-11172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Environment: Mac OS X Lion
> Reporter: Burrsitis Sutter
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.12.x
>
> Attachments: Screen Shot 2012-03-05 at 7.52.01 PM.png, Screen Shot 2012-03-05 at 7.55.21 PM.png, Screen Shot 2012-03-05 at 8.00.22 PM.png, Screen Shot 2012-03-05 at 8.00.38 PM.png, pagila-ds.xml, postgresql-9.1-901.jdbc4.jar
>
>
> Postgres 9.1 - connection to a pagila database schema does not return a list of tables in the database explorer, nor in the Hibernate configuration. See attached screenshots.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months