[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2801:
-------------------------------------
Hey [~nickboldt], "6. Help > Check for updates" didn't do anything because [1] does not contain google plugins. I added the central TP [2] and then I was able to upgrade to the new version of gwt plugins.
Other than that, it works as expected - I ended up with the new version.
[1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71...
[2] http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3...
[~mmurray], can you find a place to document this special process that is required to update from the previous version of the google plugins to the new version? This will affect users that have previously installed Google Plugins via JBoss Central in JBDS 7.0.x and will now wish to update to GWT/GPE 3.4 - as Nick showed, simple Help -> Check for updates will not work for those users - it will not update the Google Plugin for Eclipse properly. This all is assuming we support upgrade from JBDS 7.0.x to 7.1.0 - I believe that is true.
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 7.1.0.CR1
>
> Attachments: JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_manual_install_of_GPEe43_throws_remediation.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_view.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_2.png, JBDS2801_install_JBDS_Beta1_b441_installed.png, JBDS2801_install_JBT_CR1.png, JBDS2801_install_JBT_CR1_installed.png
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {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
12 years, 4 months
[JBoss JIRA] (JBIDE-14909) Users should be warned when WFK maven repo is missing
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14909?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-14909.
------------------------------------
verified in JBDS 7.1.0.CR1-v20131124-0717-B560
> Users should be warned when WFK maven repo is missing
> -----------------------------------------------------
>
> Key: JBIDE-14909
> URL: https://issues.jboss.org/browse/JBIDE-14909
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.1.0.Beta1
> Environment: Using JBDS Beta1-v20130529-0631-B257
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.1.Beta1
>
> Attachments: missing-wfk-deps.png
>
>
> When you create a new archetype-based project from JBoss Central with EAP runtime you will be given a warning if you don't have the EAP maven repo installed. Similarly users should be warned when they try to create the HTML5 project (under 'start from scratch') with EAP runtime but don't have the WFK maven repo installed.
> Right now what happens is that if you don't have the repo installed you'll get an error about missing dependency versions. The reason for that is that the bom containing the versions is not found.
> See JBIDE-11242, where a similar issue was earlier resolved for Spring and Richfaces projects.
--
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, 4 months
[JBoss JIRA] (JBIDE-15295) EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15295?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-15295.
------------------------------------
verified in JBDS 7.1.0.CR1-v20131124-0717-B560
> EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
> -------------------------------------------------------------------------
>
> Key: JBIDE-15295
> URL: https://issues.jboss.org/browse/JBIDE-15295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Final
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.1.CR1
>
> Attachments: Maven_EAP61.png, Maven_warning.png, settings.xml
>
>
> For the Java EE Web Project wizard, the EAP 6.1 maven repo is not recognized as being a JBoss Enterprise Maven repository.
> The project states that it can be used with EAP 6 so I would assume this to include EAP 6.0 and 6.1.
> Attached are:
> * my settings.xml file, with profiles generated by JBDS 'Configure Maven Repositories'
> * screenshot of added EAP 6.1 maven repo
> * Screenshot of enterprise maven repo warning in Java EE Web Project wizard
--
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, 4 months
[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Jiri Peterka closed JBDS-2719.
------------------------------
Verified with JBDS 7.1.0.CR1a, L64
> 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: Fred Bricon
> Fix For: 7.1.0.CR1
>
>
> 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
12 years, 4 months
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet edited comment on JBIDE-15622 at 11/28/13 10:28 AM:
----------------------------------------------------------------------
I think they are using the stacktrace/
Sample with duplicate :
https://netbeans.org/bugzilla/show_bug.cgi?id=188265
was (Author: ehugonnet):
I think they are using the stacktrace
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.bmml, ReportError1.png, ResultPage.bmml, ResultPage.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep3.png!
> !ReportBugStep3SourceView.png!
> Step 3:
> !ReportBugStep2.png!
> Result Page:
> !ResultPage.png!
> *Where to:*
> 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
> 1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report?
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send (see tab "Source View")
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
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, 4 months
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15622:
----------------------------------------
I found this entry in their tracker. Not sure how they're using it: http://statistics.netbeans.org/exceptions/detail.do?id=128963
I'd expected exceptions to create a new report, or comment an existing one if same report is already available.
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.bmml, ReportError1.png, ResultPage.bmml, ResultPage.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep3.png!
> !ReportBugStep3SourceView.png!
> Step 3:
> !ReportBugStep2.png!
> Result Page:
> !ResultPage.png!
> *Where to:*
> 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
> 1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report?
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send (see tab "Source View")
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
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, 4 months
[JBoss JIRA] (JBIDE-16027) Build Error when using DS security module and @Secured @Stereotype annotation
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16027?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-16027.
------------------------------------
verified in JBDS 7.1.0.CR1-v20131124-0717-B560
> 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, 4 months