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.

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

Tweak the directory-structure to add initial Maven2 support #60

Closed
GoogleCodeExporter opened this issue Mar 16, 2015 · 7 comments
Closed

Comments

@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Mar 16, 2015

To be able to add initial Maven2 support to the project, the following
directories must move:

src/java
src/test-data

The reason they have to move is that the Ontopoly-webapp cannot reside in a
subdirectory of the "engine"-module.

To make the project familiar to Maven-users, I would suggest moving the
directories to:

src/java -> src/engine/src/main/java
src/test-data -> src/engine/src/test/resources

Later we might be able to remove the top-level src-folder.

Original issue reported on code.google.com by baard...@gmail.com on 5 Jul 2009 at 11:26

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

> The reason they have to move is that the Ontopoly-webapp cannot reside in a
> subdirectory of the "engine"-module.

Maybe I'm being stupid, but I didn't understand this. If src/java is the engine 
module, what is the problem?

Original comment by lar...@gmail.com on 8 Jul 2009 at 8:03

  • Added labels: Component-Build

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

The problem is that the pom.xml for the "engine" has to reside somewhere above 
the
Java-code and the test-resources for that module. So the only place we can put 
it now
is in the ontopia-root. If we do that the pom.xml of ontopoly will be below the
engine, and that is a problem for Maven2 and Eclipse.

Original comment by baard...@gmail.com on 8 Jul 2009 at 9:46

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

I've used the following layout before:

ontopia (parent, full dist when build)
   - pom.xml
   - ontopia-engine (module, packaged as jar)
         - pom.xml
         - src/main/java (source files)
         - src/test/java (test sources)
         - src/test/resources (test data)
   - ontopia-ontopoly (module, packaged as war)
         - src/main/webapp (webapp sources like JSP)
         - src/main/java (ontopoly specific java classes)

etc etc etc

Each module can manage it's own dependancies and version. The parent project 
can be release seperate, 
based on stable versions of the modules.

A source-less, pom-only setup maven setup is already in the sandbox 

Original comment by qsieb...@gmail.com on 4 May 2010 at 9:27

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

I've made a branch in revision r1171 to work on applying the Maven2 directory 
structures. Revision r1172 introduces the original sanbox/maven directrories as 
new ontopia-maven directory. The plan is to physically svn:move files from 
ontopia to ontopia-maven, into the appropriate subprojects. This holds for 
sources, documentation and test files. Aim would be to end up with an empty 
ontopia directory, which can then be deleted. After that the ontopia-maven 
directory can be renamed ontopia and the branch can be applied to the trunk.

Original comment by p.kruijsen on 28 Jun 2010 at 11:43

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

Original comment by qsieb...@gmail.com on 30 Sep 2010 at 9:58

  • Added labels: Management-Maven

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

Ontopia has become a Maven project in revision r2090.

Original comment by p.kruijsen on 16 May 2011 at 11:22

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

Original comment by qsieb...@gmail.com on 27 Jan 2012 at 10:39

  • Added labels: Release5.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant