[JBoss JIRA] (TOOLSDOC-425) Document 7.1.0 N&N in User Guide
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-425?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-425:
-------------------------------------
Description:
For info see:
1) N&N http://docs.jboss.org/tools/whatsnew/
2) RNs http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
Specifically:
* *BrowserSim* - touch events, error log *[Done]*
* *JSF Tools* - properties tab *[Not necessary to doc]*
* *LiveReload Tools* - asciidoc files *[Done]*
* *OpenShift Tools* - multiple domains, env variables, new openshift app wizard, custom commit message, tail files function, timeout preference *[Done]*
was:
For info see:
1) N&N http://docs.jboss.org/tools/whatsnew/
2) RNs http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
Specifically:
* *BrowserSim* - touch events, error log *[Done]*
* *JSF Tools* - properties tab *[Not necessary to doc]*
* *LiveReload Tools* - asciidoc files *[Done]*
* *OpenShift Tools* - multiple domains, env variables, new openshift app wizard, custom commit message, tail files function *[Done]*
> Document 7.1.0 N&N in User Guide
> --------------------------------
>
> Key: TOOLSDOC-425
> URL: https://issues.jboss.org/browse/TOOLSDOC-425
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 2 days, 2 hours
> Time Spent: 6 hours, 15 minutes
> Remaining Estimate: 1 day, 3 hours, 45 minutes
>
> For info see:
> 1) N&N http://docs.jboss.org/tools/whatsnew/
> 2) RNs http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
> Specifically:
> * *BrowserSim* - touch events, error log *[Done]*
> * *JSF Tools* - properties tab *[Not necessary to doc]*
> * *LiveReload Tools* - asciidoc files *[Done]*
> * *OpenShift Tools* - multiple domains, env variables, new openshift app wizard, custom commit message, tail files function, timeout preference *[Done]*
--
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
12 years, 5 months
[JBoss JIRA] (TOOLSDOC-425) Document 7.1.0 N&N in User Guide
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-425?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-425:
-------------------------------------
Description:
For info see:
1) N&N http://docs.jboss.org/tools/whatsnew/
2) RNs http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
Specifically:
* *BrowserSim* - touch events, error log *[Done]*
* *JSF Tools* - properties tab *[Not necessary to doc]*
* *LiveReload Tools* - asciidoc files *[Done]*
* *OpenShift Tools* - multiple domains, env variables, new openshift app wizard, custom commit message, tail files function *[Done]*
was:
For info see:
1) N&N http://docs.jboss.org/tools/whatsnew/
2) RNs http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
Specifically:
* *BrowserSim* - touch events, error log *[Done]*
* *JSF Tools* - properties tab *[Not necessary to doc]*
* *LiveReload Tools* - asciidoc files *[Waiting on info]*
* *OpenShift Tools* - multiple domains, env variables, new openshift app wizard, custom commit message, tail files function *[Done]*
> Document 7.1.0 N&N in User Guide
> --------------------------------
>
> Key: TOOLSDOC-425
> URL: https://issues.jboss.org/browse/TOOLSDOC-425
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 2 days, 2 hours
> Time Spent: 6 hours, 15 minutes
> Remaining Estimate: 1 day, 3 hours, 45 minutes
>
> For info see:
> 1) N&N http://docs.jboss.org/tools/whatsnew/
> 2) RNs http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
> Specifically:
> * *BrowserSim* - touch events, error log *[Done]*
> * *JSF Tools* - properties tab *[Not necessary to doc]*
> * *LiveReload Tools* - asciidoc files *[Done]*
> * *OpenShift Tools* - multiple domains, env variables, new openshift app wizard, custom commit message, tail files function *[Done]*
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16022) Seam Portlet deployment error on JPP 6
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16022?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16022:
---------------------------------------------
Is this different or the same as JBIDE-15849 ? (Which for some reason only fixed in master and not reviewed for branch?)
> Seam Portlet deployment error on JPP 6
> --------------------------------------
>
> Key: JBIDE-16022
> URL: https://issues.jboss.org/browse/JBIDE-16022
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: portal-gatein
> Affects Versions: 4.1.1.CR1
> Environment: JBDS 7.1.0 CR1-v20131116-1929-B543, JPP 6.1 (also JPP 6.0) and Seam 2.2.2
> Reporter: Radoslav Rábara
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
> Attachments: jpp-seam-server.log
>
>
> Deployment of Seam Portal Project with Seam Portlet ends with error on JPP 6.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15944) [Regression] Can not edit server runtime classpath
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15944?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15944:
---------------------------------------------
[~rob.stryker] it is not correct all servers had ways of managing systems and subsystems - that happened first in AS7 and onwards.
Before that adding stuff to classpath was/is common practice.
I agree for AS7/EAP6 I find it hard to come up with a usecase but I wonder what broke here since why would we have different classpath handling code for this in the various servers ?
> [Regression] Can not edit server runtime classpath
> --------------------------------------------------
>
> Key: JBIDE-15944
> URL: https://issues.jboss.org/browse/JBIDE-15944
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.1.Final
> Environment: windows eclipse 3.4.1
> Reporter: filippo rossoni
> Assignee: Rob Stryker
> Labels: new_and_noteworthy, regression
> Fix For: 4.2.0.Alpha1
>
> Attachments: JBIDE-3770.jpg
>
>
> when edit the server runtime configuration the changes are lost after save
--
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
12 years, 5 months
[JBoss JIRA] (JBDS-2807) Update jrebel updatesite to use separate url for install feedback
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2807?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2807:
-------------------------------------------
I don't think [~arhan] can spot the difference on wether it is jbds 5,6 or 7 on the server side - thus the best verification is just if p2 lists the right jboss "marked' updatesite in the p2 list. If the changes were done as listed above that should be fine.
> Update jrebel updatesite to use separate url for install feedback
> -----------------------------------------------------------------
>
> Key: JBDS-2807
> URL: https://issues.jboss.org/browse/JBDS-2807
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: central, discovery
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Labels: respin-a
> Fix For: 5.0.2.GA, 6.0.1.GA, 7.0.1.GA, 7.1.0.Beta1
>
> Attachments: JBDS2807_after_install_JRebel.png, JBDS2807_after_install_JRebel_JBDS7beta1_b441.png, JBDS2807_JBDS502_JRebel540_installed.png, JBDS2807_JBDS50x_patch.txt, JBDS2807_JBDS50x_patch2.txt, JBDS2807_JBDS601_JRebel540_installed.png, JBDS2807_JBDS60x_patch.txt, JBDS2807_JBDS60x_patch2.txt, JBDS2807_JBDS700_JRebel540_installed.png, JBDS2807_JBT33x_patch.txt, JBDS2807_JBT33x_patch2.txt
>
>
> jrebel would like to see how many installs central gives and have given us this special url to use in discovery.xml.
> http://update.zeroturnaround.com/update-site-jboss/
> (the / at the end is important)
> We should change this for all active discovery plugins that have jrebel mentioned.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-12355:
----------------------------------------
Description:
jboss.org/tools have started to have issues scaling on several fronts.
1) no clear path to what we want users to download (too many upfront choices)
2) we are missing info about what jbosstools actually does
3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
4) the content is generally getting very stale
5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
etc. etc.
6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
was:
issue to track changes releated to jboss.org/tools redesign
[~dgolovin] pointed out we didn't actually described what was being worked/fixed on ;)
> JBoss tools website redesign
> ----------------------------
>
> Key: JBIDE-12355
> URL: https://issues.jboss.org/browse/JBIDE-12355
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.0.x
>
> Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> jboss.org/tools have started to have issues scaling on several fronts.
> 1) no clear path to what we want users to download (too many upfront choices)
> 2) we are missing info about what jbosstools actually does
> 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
> 4) the content is generally getting very stale
> 5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
> etc. etc.
> 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
> We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
> https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16027) Build Error when using DS security module and @Secured @Stereotype annotation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16027?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16027:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-javaee/pull/171 (was: https://github.com/jbosstools/jbosstools-javaee/pull/170, https://github.com/jbosstools/jbosstools-javaee/pull/171)
> Build Error when using DS security module and @Secured @Stereotype annotation
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16027
> URL: https://issues.jboss.org/browse/JBIDE-16027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions
> Affects Versions: 4.1.0.Final, 4.1.1.Beta1
> Environment: Win 7 / 64-bit Eclipse Kepler SR1 / 32-bit Java 1.7.0_25
> Reporter: Rainer Schön
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> When using {{(a)Secured(DecisionVoter.class)}} concept for authorization, each build ends with following build error if the method is annotated with a {{@Secured @Stereotype}} created annotation:
> {quote}
> eclipse.buildId=4.3.0.M20130911-1000
> java.version=1.7.0_25
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_CH
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
> Error
> Tue Nov 19 13:36:27 CET 2013
> Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'ee7-web-ds-security'.
> java.lang.NullPointerException
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.findAnnotationAnnotatedWithSecurityBindingType(DeltaspikeSecurityExtension.java:161)
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.addSecurityMember(DeltaspikeSecurityExtension.java:117)
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.processAnnotatedMember(DeltaspikeSecurityExtension.java:106)
> at org.jboss.tools.cdi.internal.core.impl.definition.TypeDefinition.init(TypeDefinition.java:72)
> at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:64)
> at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.setType(AbstractTypeDefinition.java:69)
> at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:79)
> at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:48)
> at org.jboss.tools.cdi.core.CDICoreBuilder.invokeBuilderDelegates(CDICoreBuilder.java:326)
> at org.jboss.tools.cdi.core.CDICoreBuilder.fullBuild(CDICoreBuilder.java:261)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:221)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:733)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {quote}
> When using the {{@SecurityBindingType}} concept for authorization or the {{@Secured}} annotation directly, the build passes with no error.
> In any case, even if the build reports this error, the app is compiled correctly and deploys and works as it should.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16043) CLONE - Build Error when using DS security module and @Secured @Stereotype annotation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16043?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16043:
-----------------------------------
Labels: (was: respin-a)
> CLONE - Build Error when using DS security module and @Secured @Stereotype annotation
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-16043
> URL: https://issues.jboss.org/browse/JBIDE-16043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions
> Affects Versions: 4.1.0.Final, 4.1.1.Beta1
> Environment: Win 7 / 64-bit Eclipse Kepler SR1 / 32-bit Java 1.7.0_25
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
>
> When using {{(a)Secured(DecisionVoter.class)}} concept for authorization, each build ends with following build error if the method is annotated with a {{@Secured @Stereotype}} created annotation:
> {quote}
> eclipse.buildId=4.3.0.M20130911-1000
> java.version=1.7.0_25
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_CH
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
> Error
> Tue Nov 19 13:36:27 CET 2013
> Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'ee7-web-ds-security'.
> java.lang.NullPointerException
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.findAnnotationAnnotatedWithSecurityBindingType(DeltaspikeSecurityExtension.java:161)
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.addSecurityMember(DeltaspikeSecurityExtension.java:117)
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.processAnnotatedMember(DeltaspikeSecurityExtension.java:106)
> at org.jboss.tools.cdi.internal.core.impl.definition.TypeDefinition.init(TypeDefinition.java:72)
> at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:64)
> at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.setType(AbstractTypeDefinition.java:69)
> at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:79)
> at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:48)
> at org.jboss.tools.cdi.core.CDICoreBuilder.invokeBuilderDelegates(CDICoreBuilder.java:326)
> at org.jboss.tools.cdi.core.CDICoreBuilder.fullBuild(CDICoreBuilder.java:261)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:221)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:733)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {quote}
> When using the {{@SecurityBindingType}} concept for authorization or the {{@Secured}} annotation directly, the build passes with no error.
> In any case, even if the build reports this error, the app is compiled correctly and deploys and works as it should.
--
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
12 years, 5 months