I think your life is going to be difficult unless you develop on a linux machine. Many of your problems could be related to this, although I'm not sure. You should get used to maven. It may or may not find the dependencies you need. Remember that everything is held locally under .m2 directory and one persons repository is not the same as another which can mean that in one case a dependency is found (available locally), in another it is not. As you are starting from scratch find all those dependencies will be more difficult. Maven does not necessarily find them all and download them. In some cases it may identify a dependency but not download it. It can be (usually is) necessary to tell maven which repositories to search, the build POM of any project often makes no assumptions about this, anyway for the non-project sub-strata of dependencies. In addition I usually have to search for some dependency or other. I find Jarvana <http://www.jarvana.com/jarvana/> invaluable for this. Finding the correct repository for any given artifact is a bit of an art form. Manual downloads have to be done with care, you will need to know how to download and then place into the correct directory structure under .m2.
[ERROR] Error resolving version for plugin 'http://localhost' from the > repositor > ies [local (C:\Users\Sabine Schmidt\.m2\repository), central > (http://repo.maven. > apache.org/maven2)]: Plugin not found in any plugin repository -> [Help 1] > [ERROR] This looks to me like maven is looking for a plugin called ' http://localhost'. In which case your POM is completely misconfigured. Have you been editing it or have I misunderstood? There are other things you need to check:- Do you have correct permissions including permission to run a web server on localhost? If you are uncertain about this I suggest you try to download and run tomcat or jetty or some other server and make sure you know how to configure it to serve to localhost. I take it that localhost is, itself, configured? That should be a mapping in your hosts file (or whatever under windows). With a simpler setup you could make sure that some basic maven based project downloads, deploys and runs. If all this is OK, take the same approach with felix:try to get a simpler OSGI project running. It is far easier to understand what is going on in the POM that way. Then move to the more complex requirements of Stanbol. Hope this helps. Adam On 1 June 2013 18:20, Sabine Schmidt <sabine.schm...@studium.uni-erlangen.de > wrote: > Hello, > > > > I am using stanbol for an university project and have been facing two > problems: > > > > 1) When I create a new enhancement chain or referenced site over > ../system/console/configMgr it is somehow not properly installed: > > a. The file are still in fileinstall but with a very long name (twice > the whole org.apache….. + Id of the file) > > b. Files are not installed where the pre-installed configurations are > stored e.g. org.apache.enhancer… but in an extra folder called > fileinstalldad….. (The files in the folder cannot be immediately deleted > because filenames are too long for Windows, only after renaming folders in > path) > > c. At the moment the only way to persistently store my configurations > is to copy them manually to the folder described in b. and add pid and > factory id à However this is quite annoying since I am just learning to use > stanbol and often have to change configurations to try out new staff. As it > is now I have to make changes directly in the files and then restart > stanbol > > > > I hope this describes the problem well. Is there another way for me to fix > this problem? > > > > 2) For some days I’ve been having the problem that I cannot install > new > bundles with maven anymore, I get the following error: > > > > [INFO] BUILD FAILURE > > [INFO] > ------------------------------------------------------------------------ > > [INFO] Total time: 1.593s > > [INFO] Finished at: Sat Jun 01 18:59:06 CEST 2013 > > [INFO] Final Memory: 10M/105M > > [INFO] > ------------------------------------------------------------------------ > > [ERROR] Error resolving version for plugin 'http://localhost' from the > repositor > > ies [local (C:\Users\Sabine Schmidt\.m2\repository), central > (http://repo.maven. > > apache.org/maven2)]: Plugin not found in any plugin repository -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > swit > > ch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > please > rea > > d the following articles: > > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionR > > esolutionException > > > > I’ve tried to get a and build a new stanbol instance but I still get the > same error. Since I don’t have much experience with maven I don’t know > where > to start searching. > > > > Thank you in advance for your help! > > Sabine > > > >
