[JBoss JIRA] (JBIDE-16171) Separation of module filters and traversing a publish tree for copy / rm / mkdir / etc
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-16171:
-----------------------------------
Summary: Separation of module filters and traversing a publish tree for copy / rm / mkdir / etc
Key: JBIDE-16171
URL: https://issues.jboss.org/browse/JBIDE-16171
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Affects Versions: 4.2.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.2.0.Alpha1
The current code in charge of traversing a module tree or its delta for publish suffers from many problems:
1) The class name is vague and not informative (PublishCopyUtil)
2) It suffers from an inconsistant api (was designed stateless, became stateful, but not fully converted)
3) It suffers from overlapping concerns (filtering and determining if module requires restart are intertwined in this logic)
These systems need to be broken apart. The scope of this jira is to create new runners (for incremental or full publish) without reference to IModulePathFilter, and to enhance the interface for IModulePathFilter to be able to provide clean deltas.
Test cases for all should be provided.
--
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-16088) Compilation error when building WebServices against Luna TP
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16088?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16088:
---------------------------------------
Should we fix this and open different issue related to running ui tests with tycho? currently I see similar tests problems in base and hibernate as well.
> Compilation error when building WebServices against Luna TP
> -----------------------------------------------------------
>
> Key: JBIDE-16088
> URL: https://issues.jboss.org/browse/JBIDE-16088
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, webservices
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.Alpha1
>
>
> I have the following dependency resolution problem when building the Web Services component against the Luna TP:
> {code}
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.6.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Cannot complete the request. Generating details.
> [INFO] Cannot complete the request. Generating details.
> [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.ws.creation.core 1.6.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.ws.creation.core 1.6.0.qualifier requires 'bundle org.apache.ant [1.8.2,1.9.0)' but it could not be found
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.]
> {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-15381) Support annotation @Vetoed
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-15381:
------------------------------------
The class UserSession is @Vetoed and there is also a producer like so
{code}
@Produces
@RequestScoped
@Named
private UserSession userSession;
{code}
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
> Test with archive.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest
> 2. Open class test.a.Test
> 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed.
> 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that).
> Test with sources.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1
> 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections
> 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed.
> 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java).
> 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package.
> 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class.
--
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-15381) Support annotation @Vetoed
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Cody Lerum edited comment on JBIDE-15381 at 12/2/13 1:21 PM:
-------------------------------------------------------------
A bean annotated with javax.enterprise.inject.Vetoed is still showing as an assignable bean and leads to "Multiple beans are eligible for injection to the injection point [JSR-299 §5.2.1]" warning
Using Context and Dependency Injection Tools 1.5.1.CR1-v20131123-0707-B132
was (Author: clerum):
A bean annotated with javax.enterprise.inject.Vetoed is still showing as an assignable bean and leads to "Multiple beans are eligible for injection to the injection point [JSR-299 §5.2.1]" warning
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
> Test with archive.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest
> 2. Open class test.a.Test
> 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed.
> 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that).
> Test with sources.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1
> 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections
> 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed.
> 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java).
> 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package.
> 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class.
--
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-15381) Support annotation @Vetoed
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-15381:
------------------------------------
A bean annotated with javax.enterprise.inject.Vetoed is still showing as an assignable bean and leads to "Multiple beans are eligible for injection to the injection point [JSR-299 §5.2.1]" warning
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
> Test with archive.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest
> 2. Open class test.a.Test
> 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed.
> 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that).
> Test with sources.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1
> 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections
> 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed.
> 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java).
> 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package.
> 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class.
--
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-16170) Latest HTML5 archetype doesn't show unavailable maven repo in wizard
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-16170:
-----------------------------------
Summary: Latest HTML5 archetype doesn't show unavailable maven repo in wizard
Key: JBIDE-16170
URL: https://issues.jboss.org/browse/JBIDE-16170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, project-examples
Affects Versions: 4.1.1.CR1
Reporter: Fred Bricon
Priority: Blocker
The latest HTML 5 archetype now depends on WFK dependencies by default (there used to be a community/enterprise distinction before, not anymore)
Problem is, the missing enterprise dependencies warning (JBIDE-14909) only shows up if an enterprise runtime is selected. In this case, it should also be displayed for all runtimes.
So all JBoss Central users not selecting an enterprise runtime will create a broken project if the maven redhat repo is missing from their settings.xml. Which is bad :/
--
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-16143) BrowserSim: touch events options should have same wording
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16143?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-16143.
--------------------------------------------
Fix Version/s: 4.2.0.Alpha1
Resolution: Done
done
> BrowserSim: touch events options should have same wording
> ---------------------------------------------------------
>
> Key: JBIDE-16143
> URL: https://issues.jboss.org/browse/JBIDE-16143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Alpha1
>
>
> In BrowserSim there are two options for enabling touch events. For example, when using skins:
> * Right-click device and click *Enable Touch Events*
> * Right-click device, click preferences and on settings tab select *Emulate Touch Events* check box
> 1) Does this activation option need to be listed in both of these places?
> 2) If it is needed twice, the two names should read the same thing. I would suggest 'Enable Touch Events' is best.
--
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