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

site generated from site:deploy doesn't link to modules [PAXCONSTRUCT-90] #110

Open
ops4j-issues opened this issue Jul 29, 2008 · 0 comments
Labels

Comments

@ops4j-issues
Copy link

Mike Smoot created PAXCONSTRUCT-90

After I run the sample spring pax-construct script (http://www.ops4j.org/projects/pax/construct/examples/SPRING_OSGI_EXAMPLE) followed by "mvn site" and "mvn site:deploy", I'm unable to see either the example.service or the example.bean modules on the main page (as I would expect) or any page. The module sites get generated and deployed, they're just not linked anywhere. This seems to be a result of the inheritance from poms/compiled/pom.xml.

This really seems like a bug in maven-site-plugin, but it might be worthwhile to create a workaround for pax-construct. Perhaps create a default site.xml file for pax-create-project that gets updated when pax-create-module or pax-create-bundle get run.


Affects: 1.3
Votes: 0, Watches: 0

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

No branches or pull requests

1 participant