Getting error after moving plugin location from root to plugins director. Could you help me to resolve it. I can create new but don't want to create new one.
E:\NopCommerce\Nop.Plugin.Notification.Email
\Nop.Plugin.Notification.Email.csproj : error : The project file could not be
loaded. Could not find a part of the path 'E:\NopCommerce
\Nop.Plugin.Notification.Email\Nop.Plugin.Notification.Email.csproj'.
E:\NopCommerce\Nop.Plugin.Notification.Email\Nop.Plugin.Notification.Email.csproj
Seems like you just moved the plugin into a new directory without changing the solution file.
You have to fix the path inside of the .sln file. Otherwise the solution cannot find the project and thus it cannot be loaded properly.
Related
I am trying to create a new module in my project. As soon as I specify the name of the module, Intellij throws "That this module already exists". After I exit the wizard it creates a directory with same module name but doesn't make it a module. I delete the directory and I perform "Invalidate Caches and Restart" but still the error persists.
I had this issue and went to .idea/modules.xml, found the path with the name I wanted, and deleted that line (just did ctrl+f with the name). After deleting that line and saving the file, I was able to create the module with that name.
You can try to perform the following actions:
Close the IDE and manually remove the module.
Remove .idea folder.
Open IDE and reimport the project.
Try adding the module once again according to official guide.
If the problem remains contact JetBrains support and attach a compressed log folder along with the project structure tree.
I had the same problem when I moved the code to a different directory. Detaching the workspaces, removing .idea, invalidating caches and so on did not help then.
For me what helped was this: Go to File -> Settings -> Project: workspace -> Project Structure. There you will see the all the projects you ever opened. And you will also see a button Add Content Root. There you can specify the new location of the (old) project.
It is a caching issue .
So try something on those lines
Invalidate cache and restart worked for me
But in case it doesn't you can try manually deleting .idea files or re-importing the project .
If you are using Gradle and this is a multi-project layout, which is looks like it is, you shouldn't create modules directly in IntelliJ.
Rather, create the directory manually if it doesn't already exists, create a gradle.build[.kts] file in it if needed, and then add an import statement for it in settings.gradle[.kts]. Then just refresh the Gradle configuration in IntelliJ ("Reimport All Gradle Projects").
I've started the project on Linux with root account and then this problem appeared when I've switched to user account.
For me changing the ownership of files in project directory worked.
sudo chown -R your_username:your_user_group project_directory
When this issue happens during import of existing project, then
--close intellij ide
--delete the project in explorer
--clone it again
--open intellij ide
--and try to reimport
I was working on a maven project and this project is generating some weird file.
The file name are like:
[PROJECT]/target/classes.531226305.timestamp
[PROJECT]/target/classes.1241815416.timestamp
[PROJECT]/target/test-classes.-1983166104.timestamp
And the content of the file are only a .(dot) inside it. Anyone has any idea of how this is generated? Thanks!
Does the project use the scala-maven-plugin? The scala-maven-plugin adds ".<hashcode>.timestamp" to files in the target directory. It's used for the incremental compile feature that is available for that plugin.
I accidentally deleted GeneratedBarFiles folder from IIB workspace. Now i am trying to deploy a library and getting this error.
**The following Java exception occurs:
java.lang.NullPointerException
at com.ibm.etools.mft.broker.runtime.model.BrokerRuntimeManager.getGenBarFile(BrokerRuntimeManager.java:553)
at com.ibm.etools.mft.broker.runtime.model.BrokerRuntimeManager.deployAppOrLib(BrokerRuntimeManager.java:1814)
at com.ibm.etools.mft.broker.runtime.model.BrokerRuntimeManager.deployAppOrLib(BrokerRuntimeManager.java:1810)
at com.ibm.etools.mft.broker.runtime.wizards.steps.DeployStep.run(DeployStep.java:90)
at com.ibm.etools.mft.broker.runtime.wizards.steps.Step.execute(Step.java:48)
at com.ibm.etools.mft.broker.runtime.wizards.steps.StepEngine.runStep(StepEngine.java:106)
at com.ibm.etools.mft.broker.runtime.wizards.steps.StepEngine.run(StepEngine.java:70)
**
and one more error
**The following Eclipse exception occurs:
The project description file (.project) for 'GeneratedBarFiles' is missing. This file contains important information about the project. The project will not function properly until this file is restored.**
Is there any way to restore the .project file OR any other way to solve this problem.
I created a new workspace in another directory and it worked. It generated a new GeneratedBarFiles folder with a new .project file.
I'm currently in a desperate situation right now, I already tried dropping the JAR file into both the "plugins" folder I created inside the "dropins" directory and also into the other "plugins" folder that was already created. I add the "-clean" option into the target of the eclipse shortcut and then I start eclipse. I go to the "plug-ins" section and try searching my plugin, but it does not appear.
I am using Eclipse Jee Neon and this is the JAR plugin I am attempting to use. Can anyone help me resolve this?
https://mvnrepository.com/artifact/org.codehaus.mojo/exec-maven-plugin/1.5.0
I have created a new version of my Joomla extension.
Manual upgrade via zip file or the directory works fine.
But the automatic upgrade (which used to work fine before), now gives an error 500 and the following error messages: "Unknown Archive type", "*Update path does not exist" and "Installation unexpectedly terminated: Update path does not exist".
I have no idea why those messages appear.
The update.xml references the correct zip files. Downloading it manually works just fine.
Joomla(/php/apache) has all rights on the folder containing the joomla installation.
After trying the automatic update, the tmp folder contains the downloaded zip archive with the latest extension version, interestingly without the .zip extension. Is the Joomla downloader not correctly naming the file and then failing upon finding that the file doesn't have a .zip extension?`Or what could it be?
Would be very thankful for any ideas...
Edit: My project is hosted on github, and github seems to automatically create a subfolder in the downloaded zip archive, named -.zip.
I'm using a link to the tagged github zip directly in my update.xml
I'm not sure if github always added this folder in the zip file, back when it still worked for me...
Might the Joomla problem have to do with the zip file containng such a folder, and not directly the extension stuff at root level? If so, anybody know if/how I can change github to not create that subfolder?
Right, just had a quick test of this.
I couldn't seem to find out how to automatically zip up a sub folder (there is a way but I need to do some more research/ask questions regarding this), however what you can do is the following:
Create a zip of your Repo
Open the zip, extract the folder you wish to be zipped then zip it
Create a new version and then drag your zip file into the upload box
Publish the release
Here is an example, have a look at the "Creating Releases" sections at the bottom:
https://github.com/blog/1547-release-your-software
Hope this helps
To answer my own question:
Yes, github seems to have recently changed their policy to create a root folder in the zip file, named as the repository the zip file is downloaded for (stupid, if you ask me, since the exact same information is encoded in the zip file name already anyway!).
Edit and Rewrite: It seems that either something changed in Joomla or that if you adhere to a naming convention - namely the root folder in the zip file having the exact extension name (or, I think and have to test, actually the same as the file name, without the version information), then the automatic update will work.
So as in my case, I have a Joomla package; the package is now in a repository pkg_mypkg. The zip file generated by github has the name pkg_mypkg-version.zip (e.g. pkg_myfancyext-1.0.9.zip), and contains a folder named pkg_mypkg. And inside the pkg_mypkg folder is a pkg_mypkg.xml file, the extension manifest. And this actually seems to be the configuration where automatic update works.