May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19424) jiralint's ds_maint filter doesn't differentiate between JBDS 8.0.x (completed) and 8.1.0 (in progress/upcoming)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19424?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-19424. ----------------------------------------- Fix Version/s: 4.3.0.Beta1 Resolution: Won't Fix > jiralint's ds_maint filter doesn't differentiate between JBDS 8.0.x (completed) and 8.1.0 (in progress/upcoming) > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19424 > URL: https://issues.jboss.org/browse/JBIDE-19424 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > > In querying for all the open issues for 8.1.0 / 4.2.3, the ds_maint filter also returns all the 8.0 stuff, which are all closed. > Thus, to see all the Requirements for JBDS 8.1, we need this: > https://issues.jboss.org/issues/?jql=filter%3Dds_maint%20and%20component%... (10 issues) > instead of this: > https://issues.jboss.org/issues/?jql=filter%3Dds_maint%20and%20component%... (45 issues) > Should ds_maint know that it's just 4.2.3/8.1.0, without having to subfilter? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18699) Angular.js is present in both supported and Early Access

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18699?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-18699. ----------------------------------------- Fix Version/s: 4.3.0.Beta1 Resolution: Won't Fix I'm going to close this as wont fix since early access is enabled to show that you are installing early access stuff thus it is/will/can be different than the default stuff. > Angular.js is present in both supported and Early Access > -------------------------------------------------------- > > Key: JBIDE-18699 > URL: https://issues.jboss.org/browse/JBIDE-18699 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0.GA > Reporter: Karel Piwko > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > Attachments: early-access.png, no-early-access.png > > > If I click on enable early access in JBoss Central page Software/Update tab, Angular JS is in Early access. > However, it is in supported as well. I guess only Arquillian should pop up in early access. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19424) jiralint's ds_maint filter doesn't differentiate between JBDS 8.0.x (completed) and 8.1.0 (in progress/upcoming)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19424?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-19424. ----------------------------------------- Resolution: Won't Fix No response thus closing as wont fix. "ds_next_maint_unresolved" exists to handle this case. > jiralint's ds_maint filter doesn't differentiate between JBDS 8.0.x (completed) and 8.1.0 (in progress/upcoming) > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19424 > URL: https://issues.jboss.org/browse/JBIDE-19424 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > In querying for all the open issues for 8.1.0 / 4.2.3, the ds_maint filter also returns all the 8.0 stuff, which are all closed. > Thus, to see all the Requirements for JBDS 8.1, we need this: > https://issues.jboss.org/issues/?jql=filter%3Dds_maint%20and%20component%... (10 issues) > instead of this: > https://issues.jboss.org/issues/?jql=filter%3Dds_maint%20and%20component%... (45 issues) > Should ds_maint know that it's just 4.2.3/8.1.0, without having to subfilter? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19225) java.lang.IllegalArgumentException: null source after importing WFK Spring projects

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19225?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19225: --------------------------------------------- am I reading it right that these are errors happening in Spring IDE ? Have the errors been opened against their issuetracker ? > java.lang.IllegalArgumentException: null source after importing WFK Spring projects > ----------------------------------------------------------------------------------- > > Key: JBIDE-19225 > URL: https://issues.jboss.org/browse/JBIDE-19225 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.2.2.Final > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > > {code} > java.lang.IllegalArgumentException: null source > at java.util.EventObject.<init>(EventObject.java:56) > at org.springframework.ide.eclipse.core.model.ModelChangeEvent.<init>(ModelChangeEvent.java:43) > at org.springframework.ide.eclipse.core.model.AbstractModel.notifyListeners(AbstractModel.java:43) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansModel$ResourceChangeEventHandler.configAdded(BeansModel.java:598) > at org.springframework.ide.eclipse.beans.core.internal.model.resources.BeansResourceChangeListener$BeansResourceVisitor.resourceAdded(BeansResourceChangeListener.java:97) > at org.springframework.ide.eclipse.core.internal.model.resources.SpringResourceChangeListener$SpringResourceVisitor.visit(SpringResourceChangeListener.java:145) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.springframework.ide.eclipse.core.internal.model.resources.SpringResourceChangeListener.resourceChanged(SpringResourceChangeListener.java:83) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) > at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:364) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:146) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19225) java.lang.IllegalArgumentException: null source after importing WFK Spring projects

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19225?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19225: ---------------------------------------- Fix Version/s: 4.3.0.Beta1 > java.lang.IllegalArgumentException: null source after importing WFK Spring projects > ----------------------------------------------------------------------------------- > > Key: JBIDE-19225 > URL: https://issues.jboss.org/browse/JBIDE-19225 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.2.2.Final > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > > {code} > java.lang.IllegalArgumentException: null source > at java.util.EventObject.<init>(EventObject.java:56) > at org.springframework.ide.eclipse.core.model.ModelChangeEvent.<init>(ModelChangeEvent.java:43) > at org.springframework.ide.eclipse.core.model.AbstractModel.notifyListeners(AbstractModel.java:43) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansModel$ResourceChangeEventHandler.configAdded(BeansModel.java:598) > at org.springframework.ide.eclipse.beans.core.internal.model.resources.BeansResourceChangeListener$BeansResourceVisitor.resourceAdded(BeansResourceChangeListener.java:97) > at org.springframework.ide.eclipse.core.internal.model.resources.SpringResourceChangeListener$SpringResourceVisitor.visit(SpringResourceChangeListener.java:145) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.springframework.ide.eclipse.core.internal.model.resources.SpringResourceChangeListener.resourceChanged(SpringResourceChangeListener.java:83) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) > at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:364) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:146) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19224) WFK Spring examples reports error <project root> [in travel] is not on its project's build path

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19224?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19224: --------------------------------------------- [~jpeterka] please state what the errors are. > WFK Spring examples reports error <project root> [in travel] is not on its project's build path > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19224 > URL: https://issues.jboss.org/browse/JBIDE-19224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples, upstream > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > > STEP: Download and unpack: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > STEP: Import all projects > STEP: Expand first level of all project trees > STEP: See Error log > ASSERT: No errors should occur -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19224) WFK Spring examples reports error <project root> [in travel] is not on its project's build path

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19224?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19224: ---------------------------------------- Fix Version/s: 4.3.0.Beta1 > WFK Spring examples reports error <project root> [in travel] is not on its project's build path > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19224 > URL: https://issues.jboss.org/browse/JBIDE-19224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples, upstream > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > > STEP: Download and unpack: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > STEP: Import all projects > STEP: Expand first level of all project trees > STEP: See Error log > ASSERT: No errors should occur -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3328) generate/edit jboss modules content for easily deployment/config of jdbc driver

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3328?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3328: -------------------------------------- Fix Version/s: 9.0.0.Beta1 > generate/edit jboss modules content for easily deployment/config of jdbc driver > ------------------------------------------------------------------------------- > > Key: JBDS-3328 > URL: https://issues.jboss.org/browse/JBDS-3328 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 9.0.0.Beta1 > > > in EAP7-56 its asked: > "I can easily generate and deploy a JBoss Module from existing jars including JDBC Drivers and shared libraries. (Tooling to automatically generate module.xml and related artifacts by scanning classes from a library jar file, or pom.xml if provided e.g real life use case: creating modules for JDBC Type 4 Drivers )" > this would be nice to have and linked with our datasource wizards. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3328) generate/edit jboss modules content for easily deployment/config of jdbc driver

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3328?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3328: ------------------------------------------- is this something we can add to our existing datasource wizard as an option ? > generate/edit jboss modules content for easily deployment/config of jdbc driver > ------------------------------------------------------------------------------- > > Key: JBDS-3328 > URL: https://issues.jboss.org/browse/JBDS-3328 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 9.0.0.Beta1 > > > in EAP7-56 its asked: > "I can easily generate and deploy a JBoss Module from existing jars including JDBC Drivers and shared libraries. (Tooling to automatically generate module.xml and related artifacts by scanning classes from a library jar file, or pom.xml if provided e.g real life use case: creating modules for JDBC Type 4 Drivers )" > this would be nice to have and linked with our datasource wizards. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3377) Random "not responding" message when installing from central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3377?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3377: ------------------------------------------- [~mickael_istria] are we running install operations in the main thread that can make the OS think the app is frozen ? > Random "not responding" message when installing from central > ------------------------------------------------------------ > > Key: JBDS-3377 > URL: https://issues.jboss.org/browse/JBDS-3377 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, ui/branding > Affects Versions: 8.1.0.CR1 > Environment: Fedora 20 64-bit, OpenJDK 1.7.0_75 > Reporter: Jan Richter > Assignee: Mickael Istria > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Trying to install all from central sometimes causes the "not responding" dialog to pop up while the "Calculating Dependencies" dialog is active. The app is still responding when the dialog opens though. > I cannot find a particular pattern to this, it looks completely random. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2015