[JBoss JIRA] (JBIDE-17204) Lot of NPEs when skipping dependency conversion during conversion
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17204?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-17204:
-------------------------------------
My assumption is the identification jobs are trying to update the UI even though the dialog has been closed.
> Lot of NPEs when skipping dependency conversion during conversion
> -----------------------------------------------------------------
>
> Key: JBIDE-17204
> URL: https://issues.jboss.org/browse/JBIDE-17204
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta1
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.2.0.Beta2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.maven.conversion.ui.dialog.IdentifyMavenDependencyPage$14.done(IdentifyMavenDependencyPage.java:766)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:109)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:149)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70)
> {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
11 years, 11 months
[JBoss JIRA] (JBIDE-17204) Lot of NPEs when skipping dependency conversion during conversion
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17204?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-17204:
--------------------------------
Fix Version/s: 4.2.0.Beta2
> Lot of NPEs when skipping dependency conversion during conversion
> -----------------------------------------------------------------
>
> Key: JBIDE-17204
> URL: https://issues.jboss.org/browse/JBIDE-17204
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta1
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.2.0.Beta2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.maven.conversion.ui.dialog.IdentifyMavenDependencyPage$14.done(IdentifyMavenDependencyPage.java:766)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:109)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:149)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70)
> {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
11 years, 11 months
[JBoss JIRA] (JBIDE-17204) Lot of NPEs when skipping dependency conversion during conversion
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17204?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-17204:
-----------------------------------
Assignee: Fred Bricon
> Lot of NPEs when skipping dependency conversion during conversion
> -----------------------------------------------------------------
>
> Key: JBIDE-17204
> URL: https://issues.jboss.org/browse/JBIDE-17204
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta1
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.maven.conversion.ui.dialog.IdentifyMavenDependencyPage$14.done(IdentifyMavenDependencyPage.java:766)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:109)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:149)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70)
> {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
11 years, 11 months
[JBoss JIRA] (JBIDE-11292) Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11292?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-11292.
---------------------------------
Fix Version/s: 4.2.0.Beta2
(was: 3.3.x)
Resolution: Cannot Reproduce Bug
Resolving as can't reproduce. Looks like new m2e 1.5.0 project management behaves properly now
> Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-11292
> URL: https://issues.jboss.org/browse/JBIDE-11292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 4.2.0.Beta2
>
> Attachments: project_configuration_is_not_up_to_date_0.png
>
>
> "Project configuration is not up-to-date with pom.xml. Run project configuration update"
> I have noticed, with beta1e and perhaps beta1d, that when I load up my workspace with projects - created via the archetypes, quickstarts and even File Import - perhaps, after a restart of the IDE - the next time I import (file-import or archetype) another maven project, the previous projects throw up the project configuration error msg.
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-11427) Application wizard: Importing maven application requires user to update project configuration (WATCHER)
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11427?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-11427.
---------------------------------
Fix Version/s: 4.2.0.Beta2
(was: 4.1.x)
(was: 4.2.x)
Resolution: Cannot Reproduce Bug
Resolving as can't reproduce. Looks like new m2e 1.5.0 project management behaves properly now.
> Application wizard: Importing maven application requires user to update project configuration (WATCHER)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11427
> URL: https://issues.jboss.org/browse/JBIDE-11427
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Mac OSX Lion - 32bit Eclipse with Tools 3.3.0.Beta2b
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Critical
> Labels: application_wizard
> Fix For: 4.2.0.Beta2
>
>
> When selecting "Import Application" on a openshift deployed application (not in the current workspace) requires the end-user to update his project configuration (Maven->Update Project Configuration)
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17205) Application wizard: Cannot create a new app using a simple cartridge
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17205?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17205:
-------------------------------------
Steps to Reproduce:
# EXEC: launch application wizard and pick a cartridge in the 1st wizard page (ex. BasicCartridges->JBoss Enterprise Application Platform 6/jbosseap-6)
# EXEC: in 2nd page provide some application name and hit "Finish"
Result:
Nothing happens, dialog stays open, nothing is reported in the Eclipse log
was:
# EXEC: launch application wizard and pick a cartridge in the 1st wizard page
# EXEC: in 2nd page provide some application name and hit "Finish"
Result:
Nothing happens, dialog stays open, nothing is reported in the Eclipse log
> Application wizard: Cannot create a new app using a simple cartridge
> ---------------------------------------------------------------------
>
> Key: JBIDE-17205
> URL: https://issues.jboss.org/browse/JBIDE-17205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Beta2
>
>
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-11427) Application wizard: Importing maven application requires user to update project configuration (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11427?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-11427:
------------------------------------------
as of today I cannot reproduce this any more. the 3 apps I created were all fully validated after being imported to the workspace.
> Application wizard: Importing maven application requires user to update project configuration (WATCHER)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11427
> URL: https://issues.jboss.org/browse/JBIDE-11427
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Mac OSX Lion - 32bit Eclipse with Tools 3.3.0.Beta2b
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Critical
> Labels: application_wizard
> Fix For: 4.1.x, 4.2.x
>
>
> When selecting "Import Application" on a openshift deployed application (not in the current workspace) requires the end-user to update his project configuration (Maven->Update Project Configuration)
--
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
11 years, 11 months