Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Top level project is missing Maven pom.xml file #3

Open
simonedavico opened this issue Sep 25, 2015 · 3 comments
Open

Top level project is missing Maven pom.xml file #3

simonedavico opened this issue Sep 25, 2015 · 3 comments
Assignees
@VincenzoFerme
Labels
enhancement
Milestone
Later

Comments

@simonedavico
Copy link
Collaborator

Top level project is missing Maven pom.xml file. As a result, when selecting Import from existing Maven project... in Eclipse, common, driver and harness are imported as separate projects into the workspace (with errors, see attached images).

screen shot 2015-09-25 at 17 04 11

screen shot 2015-09-25 at 17 04 44
@VincenzoFerme
Copy link
Member

The top level project is not a Maven project. We should make it a Maven project and integrate the ant builds utilised by Faban, in the Maven lifecycle.

@VincenzoFerme VincenzoFerme added this to the Next Tasks milestone Sep 25, 2015
@VincenzoFerme
Copy link
Member

@simonedavico is this solved?

@simonedavico
Copy link
Collaborator Author

No, not at all. I can do this after I finish the tasks for the 1.3.2 milestones, but it will take me some time to read up on Maven pom files and how to seamlessly integrate them with the already existing Ant build.xml.

@VincenzoFerme VincenzoFerme modified the milestones: Later, Sooner or Later May 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@VincenzoFerme VincenzoFerme

Labels
enhancement
Milestone
Later
Development

No branches or pull requests
2 participants
@simonedavico @VincenzoFerme