[JBoss JIRA] (JBIDE-26643) Page "CDI Facets settings" page is not present in the "CDI Web Project" wizard when CDI 2.0 is used
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26643?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26643:
-------------------------------
Fix Version/s: 4.12.0.Final
(was: 4.12.0.AM1)
> Page "CDI Facets settings" page is not present in the "CDI Web Project" wizard when CDI 2.0 is used
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26643
> URL: https://issues.jboss.org/browse/JBIDE-26643
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.11.0.Final
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.12.0.Final
>
> Attachments: page_missing_on_cdi_2_0.png
>
>
> Page captured on the "page_missing_on_cdi_2_0.png" img in Attachment is not present in the "CDI Web Project" wizard when CDI 2.0 is used. It is present when CDI 1.0, 1.1 or 1.2 is used and it should be either present for all CDI versions or not present at any CDI version (the wizard should be consistent and if there is not reason for that it should be the same for all versions).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
2 weeks
[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM:
------------------------------------------------------------
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/
There are ways to achieve more-than-260-char paths, but do we want to?
was (Author: nickboldt):
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
> Align installation default path with installer filename
> -------------------------------------------------------
>
> Key: JBDS-3044
> URL: https://issues.jboss.org/browse/JBDS-3044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: discuss
> Fix For: 8.0.0.Beta3
>
>
> Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync.
> This question is open for discussion. Nick pointed out some reasons against this suggestion:
> {quote}
> Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons:
> a) Max is AFK, and will want to vet/veto this idea
> b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces
> c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience
> So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters.
> Max Rydahl Andersen WDYT?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
1 month, 3 weeks
[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2719:
-------------------------------------
[~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far.
First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet).
With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error.
In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up.
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {code}
--
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
4 months, 4 weeks
[JBoss JIRA] (JBIDE-23705) no content assist in freemarker templates for interface-based beans
by Daniel Dekany (Jira)
[ https://issues.jboss.org/browse/JBIDE-23705?page=com.atlassian.jira.plugi... ]
Daniel Dekany commented on JBIDE-23705:
---------------------------------------
In case someone finds this issue... FreeMarker templates won't see anything that {{java.beans.Inspector}} doesn't, except that FreeMarker has an configuration option to see things defined via Java 8 default methods (yes, {{java.beans.Inspector}} doesn't see them for some reason). But, the code that deals with non-property-reader methods is totally broken anyway. As this plugin was deprecated, I fixed this in my fork (https://github.com/ddekany/jbosstools-freemarker), if anyone will need this to be fixed.
> no content assist in freemarker templates for interface-based beans
> -------------------------------------------------------------------
>
> Key: JBIDE-23705
> URL: https://issues.jboss.org/browse/JBIDE-23705
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Reporter: Ronald Müller
> Priority: Major
> Fix For: 4.13.x
>
>
> If your beans in freemarker templates are described by an interface, the code completion (content assist) will not work.
> There two mechanism implemented to provide content suggestion:
> # Bean-Introspection: this doesn't work for interfaces
> # Java Reflections: there are bugs which prevent any suggestions
> My suggestion: use only reflections - it will work for both and isn't that harder to implement.
> I'm working on a pull request for fixing this issue.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26806) provide up to date attributes for content assist
by nimo stephan (Jira)
nimo stephan created JBIDE-26806:
------------------------------------
Summary: provide up to date attributes for content assist
Key: JBIDE-26806
URL: https://issues.jboss.org/browse/JBIDE-26806
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsf
Affects Versions: 4.12.0.Final
Reporter: nimo stephan
For example, the ui:fragment has a _rendered_ attribute, which is not shown by the content assis/code completion of jboss tools. So users are not aware of this property when not looking in the API.
{code:java}
<ui:fragment rendered=
{code}
I dont know if other jsf-tags also has missing attributes in code completions..
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26757) PR check job for target platform shows error in log(but its green)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26757?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26757:
-------------------------------
Fix Version/s: 4.13.x
> PR check job for target platform shows error in log(but its green)
> ------------------------------------------------------------------
>
> Key: JBIDE-26757
> URL: https://issues.jboss.org/browse/JBIDE-26757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.13.0.AM1
> Environment: Central CI
> Reporter: Josef Kopriva
> Priority: Minor
> Fix For: 4.13.x
>
>
> Job is green, but there is an error in log:
> {code:java}
> [INFO] BUILD SUCCESS
> 11:35:33 [INFO] ------------------------------------------------------------------------
> 11:35:33 [INFO] Total time: 01:15 h
> 11:35:33 [INFO] Finished at: 2019-07-24T05:35:33-04:00
> 11:35:33 [INFO] Final Memory: 46M/331M
> 11:35:33 [INFO] ------------------------------------------------------------------------
> 11:35:34 Terminating xvnc.
> 11:35:34 $ /usr/bin/vncserver -kill :22
> 11:35:34 Killing Xvnc process ID 11376
> 11:35:40 Archiving artifacts
> 11:35:40 java.lang.InterruptedException: no matches found within 10000
> 11:35:40 at hudson.FilePath$34.hasMatch(FilePath.java:2677)
> 11:35:40 at hudson.FilePath$34.invoke(FilePath.java:2556)
> 11:35:40 at hudson.FilePath$34.invoke(FilePath.java:2546)
> 11:35:40 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2917)
> 11:35:40 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to rhel7-devstudio-releng-20433
> 11:35:40 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
> 11:35:40 at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
> 11:35:40 at hudson.remoting.Channel.call(Channel.java:955)
> 11:35:40 at hudson.FilePath.act(FilePath.java:1036)
> 11:35:40 at hudson.FilePath.act(FilePath.java:1025)
> 11:35:40 at hudson.FilePath.validateAntFileMask(FilePath.java:2546)
> 11:35:40 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:243)
> 11:35:40 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
> 11:35:40 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 11:35:40 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
> 11:35:40 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
> 11:35:40 at hudson.model.Build$BuildExecution.post2(Build.java:186)
> 11:35:40 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
> 11:35:40 at hudson.model.Run.execute(Run.java:1823)
> 11:35:40 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> 11:35:40 at hudson.model.ResourceController.execute(ResourceController.java:97)
> 11:35:40 at hudson.model.Executor.run(Executor.java:429)
> 11:35:40 Caused: hudson.FilePath$TunneledInterruptedException
> 11:35:40 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2919)
> 11:35:40 at hudson.remoting.UserRequest.perform(UserRequest.java:212)
> 11:35:40 at hudson.remoting.UserRequest.perform(UserRequest.java:54)
> 11:35:40 at hudson.remoting.Request$2.run(Request.java:369)
> 11:35:40 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> 11:35:40 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 11:35:40 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 11:35:40 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 11:35:40 at java.lang.Thread.run(Thread.java:748)
> 11:35:40 Caused: java.lang.InterruptedException: java.lang.InterruptedException: no matches found within 10000
> 11:35:40 at hudson.FilePath.act(FilePath.java:1038)
> 11:35:40 at hudson.FilePath.act(FilePath.java:1025)
> 11:35:40 at hudson.FilePath.validateAntFileMask(FilePath.java:2546)
> 11:35:40 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:243)
> 11:35:40 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
> 11:35:40 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 11:35:40 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
> 11:35:40 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
> 11:35:40 at hudson.model.Build$BuildExecution.post2(Build.java:186)
> 11:35:40 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
> 11:35:40 at hudson.model.Run.execute(Run.java:1823)
> 11:35:40 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> 11:35:40 at hudson.model.ResourceController.execute(ResourceController.java:97)
> 11:35:40 at hudson.model.Executor.run(Executor.java:429)
> 11:35:40 No artifacts found that match the file pattern "**/*.p2diff, **/*.log". Configuration error?
> 11:35:40 [Set GitHub commit status (universal)] SUCCESS on repos [] (sha:e05d75f) with context:jbosstoolstargetplatform-Pull-Request
> 11:35:40 Started calculate disk usage of build
> 11:35:40 Finished Calculation of disk usage of build in 0 seconds
> 11:35:40 Started calculate disk usage of workspace
> 11:35:41 Finished Calculation of disk usage of workspace in 0 seconds
> 11:35:41 Setting status of e05d75f78b8fcfc1dfd76f8687dc15745216b110 to SUCCESS with url https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... and message: 'Build finished. '
> 11:35:41 Using context: Red Hat Jenkins
> 11:35:42 SUCCESSFUL build; See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... for p2diff and more details.
> 11:35:42
> 11:35:44 Finished: SUCCESS
> {code}
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26793) cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26793?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26793:
-------------------------------
Fix Version/s: 4.13.x
> cvc-complex-type.2.4.a error in <weld:scan> tag in the pom.xml when using CDI 2.0
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26793
> URL: https://issues.jboss.org/browse/JBIDE-26793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.12.0.Final
> Environment: OS X, RHEL 7, Windows 10
> Reporter: Zbyněk Červinka
> Priority: Major
> Fix For: 4.13.x
>
> Attachments: pom-xml.png
>
>
> h2. *Error message:*
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'weld:scan'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":interceptors, "http://xmlns.jcp.org/xml/ns/javaee":decorators, "http://xmlns.jcp.org/xml/ns/javaee":alternatives, "http://xmlns.jcp.org/xml/ns/javaee":scan, "http://xmlns.jcp.org/xml/ns/javaee":trim}' is expected.
> {code}
> h2. *Affected weld version details:*
> * Weld se version: 2.2.4.Final, 2.4.8.Final
> * Weld api version: 2.2.SP3, 3.1.SP1
> h2. *Additional information:*
> * error only appears when using CDI 2.0, older versions of CDI are working properly
> * Error appears when using WildFly 16 and in several CodeReady Studio version (July/August)
> * See the *{color:#DE350B}pom-xml.png{color}* image in the attachment to see, where the error appears
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 2 months