I have 3 projects, action, security and service, I would like to make into a multi module maven project.
First I did is to create a parent project - actionParent, change packaging to pom, add
Next I add into each project.
But the problem is child project does not show up in the parent project
such as
actionParent
|
----action
|
----security
|
----service
|
----pom.xml
Right click parent project do import existing maven project did not do the trick, I am using myEclipse 10
Is this similar to the problem you're having? The answer is pretty verbose, it might help.
Maven - making child projects that can be independent of their parent
Related
I am using two different project within one workspace. I have one base(Say Unity-iPhone) project and i drag and drop another iOS project (Say InnerApp). Each file and folder are visible in base project as attached screenshot. I have also added the dependency in build phase of base project, and set the other linker flag and header search path.
Now I want to access the InnerApp classes and storyboard file in base project.
Now My problem is that, I want to launch the Inner App Main.storyboard into base project. But InnerApp classes are not accessible into base project.
Please guide me. Thanks.
You can follow some great step-by-step instructions on how to add static library dependencies while using multiple projects.
Use below urls -
Include one project into another one
Include static libraries into another one
I'm trying to split in modules a big XCode project. I have a main project and one submodule as an embedded framework.
I need to import some classes from the main project into the subproject but no success.
I added the subframework in the embedded binaries and in the Linked Frameworks of the parent's project target. Moreover I added in build settings "Header Search Path" in the parent project the path of the subframework.
Any help would be appreciated
You can't. Also it meaningless because if you separate some pieces of your code into framework it means that this code doesn't have any dependencies with other code. So if you have any case when your framework need to import some class outside you have only two ways:
Include it inside framework.
Refactor framework's classes and try to remove dependencies.
I have a workspace that contains multiple projects - Project A and Project B. In this case, Project B is a dependency of Project A. When Project A is built, project B is then added as a dynamic framework to Project A.
- Project A
- Framework 1
- Project B
- Framework 1
Both Project A and Project B rely on a framework (Framework 1). I add this framework to both projects by going Build Settings -> Framework Search Paths -> Add path to Framework 1. When I compile the project, I get Xcode warnings saying:
Class XXX is implemented in both PATH 1 and PATH 2. One of the two will be used. Which one is undefined.
What I really want to do is to tell Xcode to link the Framework with both sub projects but to understand that this is one common library that doesn't need to be duplicated. I have two questions:
Is this possible?
If it's not possible, will this warning cause any problems? For example, is it that Xcode will just use the source code from either Framework location or is it that Xcode could run parallel instances of the framework code which could cause issues with singletons being duplicated.
A while ago I developed an iOS application using Xcode that and created a bunch of classes that work together to communicate with a RESTful API. Now I'm creating a second app, totally separate but communicates with the same API. I want to reuse these classes, what is the best way to approach this? Should I be do the via some Version control system? Or should I use an Xcode workspace?
Thanks in advance for any help.
I prefer to create separate Git repository for selected files, and embed this repository as submodule in both projects (old and new one)
In similar situation I done it using XCode Workspace and Static Library.
I added the common classes to a Static Library project and added that to the XCode Workspace.
In my second project I added that Static Library Project.
I have two options there:
Adding that Static Library project to the new project workspace
Adding the static library (.a) project to the new project
I chose the first option because, I can add the other common files to that Static Library and also modify the existing files if needed.
As Midhun and yourself mentioned, the best way to do it us by making a workspace and adding your projects to that.
Your shared code can go into a new project that's basically empty and dragged/linked from there into any projects in your workspace.
Changes made to that code from any project will also update the shared code base, which I think is what your ultimate goal was.
Suppose I have two dart projects
Project A contains code that uses web component to create bunch of UI widget (similar to https://github.com/kevmoo/widget.dart)
Project B contains my front end code that would reuse the UI widget I created in project A.
If I dont want to publish my project A to pub, is there anyway to link project B to project A without manually copying files from project A into B?
Thanks
Take a look at this section in the pub documentation: Path Dependencies:
http://pub.dartlang.org/doc/dependencies.html#path-packages
Suppose project_a had a library file called myprojecta.dart
dependencies:
project_a:
path: /Users/me/project_a <-- root of project a
In your code, you would import project_a using
import 'package:project_a/myprojecta.dart'
Note - if you don't want to publish your project to pub, you can always use git as a dependency rather than path dependency - this lets other people in your team use your projects without relying upon your filesystem layout.