FileAlreadyLockedException when creating custom maven actions
AlexFalappa opened this issue · comments
Happened when creating a custom maven action (Run Maven
-> Goals...
):
org.openide.filesystems.FileAlreadyLockedException: /home/sasha/Sviluppo/gitrepos/nb-cfgprops/nbactions.xml
at org.netbeans.modules.masterfs.filebasedfs.fileobjects.LockForFile.registerLock(LockForFile.java:115)
at org.netbeans.modules.masterfs.filebasedfs.fileobjects.LockForFile.tryLock(LockForFile.java:104)
at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObj.lock(FileObj.java:409)
at org.openide.filesystems.FileObject.getOutputStream(FileObject.java:812)
at org.openide.filesystems.FileObject$1R.run(FileObject.java:1068)
at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:127)
at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:519)
at org.openide.filesystems.FileObject.createAndOpen(FileObject.java:1077)
[catch] at com.github.alexfalappa.nbspringboot.projects.service.spi.SpringBootServiceImpl.adjustNbActions(SpringBootServiceImpl.java:351)
at com.github.alexfalappa.nbspringboot.projects.service.spi.SpringBootServiceImpl.refresh(SpringBootServiceImpl.java:128)
at com.github.alexfalappa.nbspringboot.projects.service.spi.SpringBootServiceImpl$1.propertyChange(SpringBootServiceImpl.java:280)
at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263)
at org.netbeans.modules.maven.api.NbMavenProject.doFireReload(NbMavenProject.java:573)
at org.netbeans.modules.maven.api.NbMavenProject.access$200(NbMavenProject.java:95)
at org.netbeans.modules.maven.api.NbMavenProject$AccessorImpl.doFireReload(NbMavenProject.java:141)
at org.netbeans.modules.maven.NbMavenProjectImpl$1.run(NbMavenProjectImpl.java:151)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1443)
at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:68)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:303)
at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2058)
The problem seems to be in the new code for dealing with adaptations of restart environment properties to spring boot version.