[JBoss JIRA] (JBIDE-18111) Arquillian warnings are not cleared properly
                                
                                
                                
                                    
                                        by Snjezana Peco (JIRA)
                                    
                                
                                
                                        
     [ https://issues.jboss.org/browse/JBIDE-18111?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-18111:
----------------------------------
    Fix Version/s: 4.2.0.CR2
> Arquillian warnings are not cleared properly
> --------------------------------------------
>
>                 Key: JBIDE-18111
>                 URL: https://issues.jboss.org/browse/JBIDE-18111
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: testing-tools
>    Affects Versions: 4.2.0.Beta3
>            Reporter: Lucia Jelinkova
>            Assignee: Snjezana Peco
>             Fix For: 4.2.0.CR2
>
>
> When I create an arquillian test without test method and deployment method, I get 2 warnings - that is correct. However, when I mark class as abstract, these warnings should disappear, but they do not. I need to clean the project (causing to rebuild the project) to make those warnings disappear. 
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
                                
                         
                        
                                
                                11 years, 2 months
                        
                        
                 
         
 
        
            
        
        
        
            
        
        
        
            
        
        
        
            
        
        
        
            
        
        
        
                
                        
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [JBoss JIRA] (JBDS-3134) Visual Page Editor is not supported for selected Installation Type
                                
                                
                                
                                    
                                        by Burr Sutter (JIRA)
                                    
                                
                                
                                        Burr Sutter created JBDS-3134:
---------------------------------
             Summary: Visual Page Editor is not supported for selected Installation Type
                 Key: JBDS-3134
                 URL: https://issues.jboss.org/browse/JBDS-3134
             Project: Developer Studio (JBoss Developer Studio)
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: installer
            Reporter: Burr Sutter
This message is less accurate than it once was in JBDS 8 CR1.
In JBDS 8, we have the VPV which works much like the VPE, the end-user really does not see much of a difference.  
And why is "Installation" and "Type" capitalized?  And why does it not say "VPE is not supported on your selected JVM"?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
                                
                         
                        
                                
                                11 years, 2 months
                        
                        
                 
         
 
        
            
        
        
        
            
        
        
        
            
        
        
        
                
                        
                                
                                 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [JBoss JIRA] (JBIDE-18096) could not complete update project configuration - illegalargumentexception
                                
                                
                                
                                    
                                        by Fred Bricon (JIRA)
                                    
                                
                                
                                        
     [ https://issues.jboss.org/browse/JBIDE-18096?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-18096:
-----------------------------------
    Assignee: Fred Bricon
> could not complete update project configuration - illegalargumentexception
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-18096
>                 URL: https://issues.jboss.org/browse/JBIDE-18096
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>            Reporter: Max Rydahl Andersen
>            Assignee: Fred Bricon
>
> while trying to fix import of javaee-samples I bumped into this happening when running update project configuration.
> java.lang.IllegalArgumentException
> 	at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.removeProjectFacet(FacetedProjectWorkingCopy.java:876)
> 	at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:309)
> 	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> 	at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> 	at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configure(WebProjectConfiguratorDelegate.java:150)
> 	at org.eclipse.m2e.wtp.AbstractProjectConfiguratorDelegate.configureProject(AbstractProjectConfiguratorDelegate.java:93)
> 	at org.eclipse.m2e.wtp.WTPProjectConfigurator.configure(WTPProjectConfigurator.java:70)
> 	at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> 	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> 	at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
> 	at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
> 	at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77)
> 	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> It happened on ~100 projects so was quite invasive ;/
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
                                
                         
                        
                                
                                11 years, 2 months