Re: Cannot find Test after adding maven
siegfried wrote:
I'm running maven 2.1.0 and eclipse 3.5 and the recent maven plugin for
eclipse.
When I create a simple JUnit 4 unit test, everything works. When I add maven
dependency support and try to run the test again, ALT+SHIFT+X T will no
longer find the junit test as denoted by the dialog box ("cannot find
test"). If I'm trying to run a main program, it can no longer find main.
This is probably better addressed at the mailing list for the eclipse
integration - which one is it? m2eclipse certainly has a mailing list,
I'm not sure about others.
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with site:site
This would appear to be a known issue, although there seems to be no
movement towards a fix - MPIR-132
(http://jira.codehaus.org/browse/MPIR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel)
Sam
Sam Barnett-Cormack wrote:
Mick Knutson wrote:
Your source and site plugins in your parent are under
pluginManagement, but
never declared in the parent or child as a plugin. Your javadoc plugin is
however used.
Source plugin *was* already in the child, but I tried adding the site
plugin and it made no discernable difference.
I'm thinking it must be because of the dependencies section:
sun.jdk
tools
1.5.0
system
C:/Program
Files/Java/jdk1.6.0_07/lib/tools.jar
This is the only project where I use a system dependency... so why does
it barf on this? mvn build is fine, but not site...
On Tue, Sep 8, 2009 at 9:08 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Mick Knutson wrote:
Can you post your pom.xml?
Along with it's parent... these ones are mine, not my employer's...
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Tue, Sep 8, 2009 at 8:31 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
In one project I'm building (but not in others), I'm getting a
NullPointerException when generating the dependencies report. I do not
know
why. Pasted below is the full output from mvn site. Any advice
gratefully
received.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Geekworld Java Support
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
*[INFO] Unable to load parent project from a relative path: Could not
find
the model file 'C:\Users\sdb\workspace\pom.**xml'. for project
unknown*
[INFO] Parent project loaded from repository.
[INFO] Unable to load parent project from a relative path: Could
not find
the model file 'C:\Users\sdb\workspace\pom.xml'. for project unknown
[INFO] Parent project loaded from repository.
[INFO] Generating "Project Team" report.
[INFO] Generating "Issue Tracking" report.
[INFO] Generating "Continuous Integration" report.
[INFO] Generating "Project Plugins" report.
[INFO] Generating "Dependencies" report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printArtifactsLocations(DependenciesRenderer.java:1182)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.java:641)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultL
Re: JAVA_HOME is not defined correctly!
Babak Shafian wrote: Does maven require a JDK and you are running a JRE? I'm running a basic "stock" install of Ubuntu Jaunty and haven't had any problems running maven. I've installed both JDK and JRE. Which is JAVA_HOME pointing to? Sam On Tue, Sep 8, 2009 at 11:59 AM, Babak Shafian wrote: Thanks for the quick response! did you try to run java -version ??> Yes I tried and I get : java version "1.6.0_14" Java(TM) SE Runtime Environment (build 1.6.0_14-b08) Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode) it seems, that JAVA_HOME is set correctly, at least maven complains that it cannot run /user/lib/jvm/java-6-sun/bin/java, while it has the directory info apparently from JAVA_HOME. What happens if you want to execute /user/lib/jvm/java-6-sun/bin/java from the shell directly? After executing that(if I understood you correctly) I get actually nothing special: r...@ubuntu-jaunty-amd64-webtv:/usr/lib/jvm/java-6-sun/bin# java Usage: java [-options] class [args...] (to execute a class) or java [-options] -jar jarfile [args...] (to execute a jar file) -Original Message- From: Babak Shafian [mailto:babak...@hotmail.com] Sent: Tuesday, September 08, 2009 5:17 PM To: users@maven.apache.org Subject: JAVA_HOME is not defined correctly! Hi Volks, just installed Maven with Ubuntu. After typing mvn --version I get the following message: Error: JAVA_HOME is not defined correctly. We cannot execute /user/lib/jvm/java-6-sun/bin/java And I'm pretty sure that the JAVA_HOME is correctly set in etc/bash.bashrc: export JAVA_HOME=/user/lib/jvm/java-6-sun export PATH=$PATH:/user/lib/jvm/java-6-sun/bin Do you have any idea what could be the problem?? BTW. I've searched through google and archives! Thanks in advance Babak _ With Windows Live, you can organize, edit, and share your photos. http://www.microsoft.com/middleeast/windows/windowslive/products/photo- gallery-edit.aspx - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ More than messages–check out the rest of the Windows Live™. http://www.microsoft.com/windows/windowslive/ -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Show them the way! Add maps and directions to your party invites. http://www.microsoft.com/windows/windowslive/products/events.aspx -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with site:site
Mick Knutson wrote:
Your source and site plugins in your parent are under pluginManagement, but
never declared in the parent or child as a plugin. Your javadoc plugin is
however used.
Source plugin *was* already in the child, but I tried adding the site
plugin and it made no discernable difference.
I'm thinking it must be because of the dependencies section:
sun.jdk
tools
1.5.0
system
C:/Program
Files/Java/jdk1.6.0_07/lib/tools.jar
This is the only project where I use a system dependency... so why does
it barf on this? mvn build is fine, but not site...
On Tue, Sep 8, 2009 at 9:08 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Mick Knutson wrote:
Can you post your pom.xml?
Along with it's parent... these ones are mine, not my employer's...
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Tue, Sep 8, 2009 at 8:31 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
In one project I'm building (but not in others), I'm getting a
NullPointerException when generating the dependencies report. I do not
know
why. Pasted below is the full output from mvn site. Any advice gratefully
received.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Geekworld Java Support
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
*[INFO] Unable to load parent project from a relative path: Could not
find
the model file 'C:\Users\sdb\workspace\pom.**xml'. for project unknown*
[INFO] Parent project loaded from repository.
[INFO] Unable to load parent project from a relative path: Could not find
the model file 'C:\Users\sdb\workspace\pom.xml'. for project unknown
[INFO] Parent project loaded from repository.
[INFO] Generating "Project Team" report.
[INFO] Generating "Issue Tracking" report.
[INFO] Generating "Continuous Integration" report.
[INFO] Generating "Project Plugins" report.
[INFO] Generating "Dependencies" report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printArtifactsLocations(DependenciesRenderer.java:1182)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.java:641)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven
Re: Problem with site:site
Mick Knutson wrote:
Your source and site plugins in your parent are under pluginManagement, but
never declared in the parent or child as a plugin. Your javadoc plugin is
however used.
Try to use a generic javadoc plugin generation first. You might have an
issue with your taglet.
Taglet works fine (same config) elsewhere. Looking into declaration of
source and site in child.
On Tue, Sep 8, 2009 at 9:08 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Mick Knutson wrote:
Can you post your pom.xml?
Along with it's parent... these ones are mine, not my employer's...
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Tue, Sep 8, 2009 at 8:31 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
In one project I'm building (but not in others), I'm getting a
NullPointerException when generating the dependencies report. I do not
know
why. Pasted below is the full output from mvn site. Any advice gratefully
received.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Geekworld Java Support
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
*[INFO] Unable to load parent project from a relative path: Could not
find
the model file 'C:\Users\sdb\workspace\pom.**xml'. for project unknown*
[INFO] Parent project loaded from repository.
[INFO] Unable to load parent project from a relative path: Could not find
the model file 'C:\Users\sdb\workspace\pom.xml'. for project unknown
[INFO] Parent project loaded from repository.
[INFO] Generating "Project Team" report.
[INFO] Generating "Issue Tracking" report.
[INFO] Generating "Continuous Integration" report.
[INFO] Generating "Project Plugins" report.
[INFO] Generating "Dependencies" report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printArtifactsLocations(DependenciesRenderer.java:1182)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.java:641)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.
Re: Confusion with site:deploy
Mick Knutson wrote:
This happens because ${project.artifactId} changes as you build the parent,
then the children. Then you will always have the child DIR appended to that.
${project.artifactId}/project-1 while in project-1 is ${project.artifactId}
== project-1
Sounds like you are trying to build a multi-module documentation, but NOT
want to create a multi-module structure with inheritance.
Well, I don't want all the projects under each other, and certainly not
under the parent. I have another project, let's call it 'complete', that
identifies all but the parent as modules, and when I build it it builds
everything (obviously). The aim of that one is to aggregate everything,
so I get a site with combined javadoc, etc etc, and a combined src jar
and javadoc jar. IIRC I call each module a module and a dependency, to
avoid order-of-build problems.
Layout I want:
maven/complete
maven/parent
maven/project-1
maven/project-2
Layout I'd accept:
maven/complete
maven/parent
maven/complete/project-1
maven/complete/project-2
(all referring to site directories on the generated website, of course)
On Tue, Sep 8, 2009 at 9:04 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Mick Knutson wrote:
You could define another in your children.
Otherwise, just hard-code your parent artifactId then reference:
I'd really like to understand why this is happening. As I see it, one of
the points of parent POMs and parameters is the ability to configure this
sort of thing in one place.
in Parent:
M:\public_html\maven\project-parent
Then reference your children from your Parent as:
./project-1
./project-2
I've separated aggregation from inheritance, so the parent doesn't refer to
children at all. I build them all from within another project, which also
inherits the same parent, but declares all of the others as modules.
On Tue, Sep 8, 2009 at 8:40 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
I'm a bit confused about the deployment paths used by site:deploy. I have
the following in my parent POM:
mnementh
file://M:\public_html\maven\${project.artifactId}
Now, when the parent POM's site is being generated, it puts it at
M:\public_html\maven\parent-name, which is intended. However, for the
inheritors (which we'll call project-1 and project-2), I get them at
M:\public_html\maven\project-1\project-1 and
M:\public_html\maven\project-2\project-2. This is far from handy, and
spoils
my attempts to define the URLs in the parent using
http://shed.geekworld.co.uk/~sdb/maven/${project.artifactId}<http://shed.geekworld.co.uk/%7Esdb/maven/$%7Bproject.artifactId%7D>
<http://shed.geekworld.co.uk/%7Esdb/maven/$%7Bproject.artifactId%7D>
I'm confused. Can anyone explain?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with site:site
Mick Knutson wrote:
Can you post your pom.xml?
Along with it's parent... these ones are mine, not my employer's...
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Tue, Sep 8, 2009 at 8:31 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
In one project I'm building (but not in others), I'm getting a
NullPointerException when generating the dependencies report. I do not know
why. Pasted below is the full output from mvn site. Any advice gratefully
received.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Geekworld Java Support
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
*[INFO] Unable to load parent project from a relative path: Could not find
the model file 'C:\Users\sdb\workspace\pom.**xml'. for project unknown*
[INFO] Parent project loaded from repository.
[INFO] Unable to load parent project from a relative path: Could not find
the model file 'C:\Users\sdb\workspace\pom.xml'. for project unknown
[INFO] Parent project loaded from repository.
[INFO] Generating "Project Team" report.
[INFO] Generating "Issue Tracking" report.
[INFO] Generating "Continuous Integration" report.
[INFO] Generating "Project Plugins" report.
[INFO] Generating "Dependencies" report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printArtifactsLocations(DependenciesRenderer.java:1182)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.java:641)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithE
Re: Confusion with site:deploy
Mick Knutson wrote:
You could define another in your children.
Otherwise, just hard-code your parent artifactId then reference:
I'd really like to understand why this is happening. As I see it, one of
the points of parent POMs and parameters is the ability to configure
this sort of thing in one place.
in Parent:
M:\public_html\maven\project-parent
Then reference your children from your Parent as:
./project-1
./project-2
I've separated aggregation from inheritance, so the parent doesn't refer
to children at all. I build them all from within another project, which
also inherits the same parent, but declares all of the others as modules.
On Tue, Sep 8, 2009 at 8:40 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
I'm a bit confused about the deployment paths used by site:deploy. I have
the following in my parent POM:
mnementh
file://M:\public_html\maven\${project.artifactId}
Now, when the parent POM's site is being generated, it puts it at
M:\public_html\maven\parent-name, which is intended. However, for the
inheritors (which we'll call project-1 and project-2), I get them at
M:\public_html\maven\project-1\project-1 and
M:\public_html\maven\project-2\project-2. This is far from handy, and spoils
my attempts to define the URLs in the parent using
http://shed.geekworld.co.uk/~sdb/maven/${project.artifactId}<http://shed.geekworld.co.uk/%7Esdb/maven/$%7Bproject.artifactId%7D>
I'm confused. Can anyone explain?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Confusion with site:deploy
Hi all,
I'm a bit confused about the deployment paths used by site:deploy. I
have the following in my parent POM:
mnementh
file://M:\public_html\maven\${project.artifactId}
Now, when the parent POM's site is being generated, it puts it at
M:\public_html\maven\parent-name, which is intended. However, for the
inheritors (which we'll call project-1 and project-2), I get them at
M:\public_html\maven\project-1\project-1 and
M:\public_html\maven\project-2\project-2. This is far from handy, and
spoils my attempts to define the URLs in the parent using
http://shed.geekworld.co.uk/~sdb/maven/${project.artifactId}
I'm confused. Can anyone explain?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Problem with site:site
Hi all,
In one project I'm building (but not in others), I'm getting a
NullPointerException when generating the dependencies report. I do not
know why. Pasted below is the full output from mvn site. Any advice
gratefully received.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Geekworld Java Support
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
[INFO] Unable to load parent project from a relative path: Could not
find the model file 'C:\Users\sdb\workspace\pom.xml'. for project unknown
[INFO] Parent project loaded from repository.
[INFO] Unable to load parent project from a relative path: Could not
find the model file 'C:\Users\sdb\workspace\pom.xml'. for project unknown
[INFO] Parent project loaded from repository.
[INFO] Generating "Project Team" report.
[INFO] Generating "Issue Tracking" report.
[INFO] Generating "Continuous Integration" report.
[INFO] Generating "Project Plugins" report.
[INFO] Generating "Dependencies" report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printArtifactsLocations(DependenciesRenderer.java:1182)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.java:641)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 20 seconds
[INFO] Finished at: Tue Sep 08 13:28:11 BST 2009
[INFO] Final Memory: 31M/56M
[INFO]
------------
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Mysterious error on site:site
Sam Barnett-Cormack wrote:
B Smith-Mannschott wrote:
On Sat, Aug 15, 2009 at 00:18, Sam
Barnett-Cormack wrote:
Further note:
this happened when I added the following (host address edited):
http://host.domain.co.uk/~sdb/maven/${project.artifactId}
to the *parent* POM. I comment it out, it's all fine. I call this
weird, but would love an explanation.
I've been seeing NPEs when doing site generation since updating to mvn
2.2.0. I define using a property in my parent pom.
I've looked at the release notes to 2.2.1, but it's not clear to me if
that may fix this problem. (There's talk of at least 3 NPE bugs fixed,
but none of them are obviously this one.) I'll try it out on monday
when I'm back at the office and report back.
I'm on 2.2.1... I also have 3 embedder I can try.
And with the 3 embedder in m2eclipse, nothing happens at all. I get the
series of building messages, but it doesn't so anything and terminates
claiming success.
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Mysterious error on site:site
B Smith-Mannschott wrote:
On Sat, Aug 15, 2009 at 00:18, Sam
Barnett-Cormack wrote:
Further note:
this happened when I added the following (host address edited):
http://host.domain.co.uk/~sdb/maven/${project.artifactId}
to the *parent* POM. I comment it out, it's all fine. I call this weird, but
would love an explanation.
I've been seeing NPEs when doing site generation since updating to mvn
2.2.0. I define using a property in my parent pom.
I've looked at the release notes to 2.2.1, but it's not clear to me if
that may fix this problem. (There's talk of at least 3 NPE bugs fixed,
but none of them are obviously this one.) I'll try it out on monday
when I'm back at the office and report back.
I'm on 2.2.1... I also have 3 embedder I can try.
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Mysterious error on site:site
Further note:
this happened when I added the following (host address edited):
http://host.domain.co.uk/~sdb/maven/${project.artifactId}
to the *parent* POM. I comment it out, it's all fine. I call this weird,
but would love an explanation.
Sam Barnett-Cormack wrote:
At least, it's a mystery to me. To someone who knows what's going on, it
probably makes perfect sense.
The following is the end of the output of 'mvn site' on my aggregator.
I've no idea what this "from" parameter it's talking about is. Am I
being dumb?
[INFO]
[INFO] Building ASN.1 Syntax Modelling
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] The parameter 'from' can not be null
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException: The parameter 'from' can not be null
at
org.apache.maven.doxia.tools.DefaultSiteTool.getRelativePath(DefaultS
iteTool.java:197)
at
org.apache.maven.doxia.tools.DefaultSiteTool.populateParentMenu(Defau
ltSiteTool.java:822)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(Defau
ltSiteTool.java:540)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRen
deringContext(AbstractSiteRenderingMojo.java:226)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:117
)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
0)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 26 seconds
[INFO] Finished at: Fri Aug 14 22:40:22 BST 2009
[INFO] Final Memory: 49M/254M
[INFO]
------------
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
Ah, switch the aggregator to do aggregate-jar and it all works now
(afaict). Nice.
Sam Barnett-Cormack wrote:
David Hoffer wrote:
I don't know about running from the command line...we have our CI system
auto deploy javadocs/source jars to our internal repo so IDE's get this
integrated with the binaries. This is the functionality I was looking
for.
Well, I'm getting the website combined javadocs, and I'm getting the
per-module jar'ed javadocs, but not the combined jar'ed javadocs,
because of the message below (afaict). Anyone know how I'd bring this to
the attention of the devs of the maven-javadoc-plugin?
On Fri, Aug 14, 2009 at 8:29 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
David Hoffer wrote:
No any call to install or deploy will build it. This isn't required
but
we
do wrap the build section in a profile so we only do this on the CI
system...as this takes a while.
Well, that works very well for putting the aggregated javadoc on the
generated site (once I configured it to generate a site), but the
attempt to
javadoc:jar gives me:
[INFO]
[INFO] Building ASN.1 Java Implementation
[INFO]task-segment: [javadoc:jar]
[INFO]
[WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
javadoc
:aggregate and
javadoc:test-aggregate instead.
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable
package
The deprecation I can deal with later, but the not-running-javadoc is a
pain.
On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
David Hoffer wrote:
This works for us, try this in your parent pom:
When running this, does it need site:site running to build the
javadoc
before running a build that'll generate the jar?
org.apache.maven.plugins
maven-javadoc-plugin
2.5
attach-javadocs
jar
...
org.apache.maven.plugins
maven-javadoc-plugin
2.5
true
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well,
but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the
modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can
tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Mysterious error on site:site
At least, it's a mystery to me. To someone who knows what's going on, it
probably makes perfect sense.
The following is the end of the output of 'mvn site' on my aggregator.
I've no idea what this "from" parameter it's talking about is. Am I
being dumb?
[INFO]
[INFO] Building ASN.1 Syntax Modelling
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] The parameter 'from' can not be null
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException: The parameter 'from' can not be null
at
org.apache.maven.doxia.tools.DefaultSiteTool.getRelativePath(DefaultS
iteTool.java:197)
at
org.apache.maven.doxia.tools.DefaultSiteTool.populateParentMenu(Defau
ltSiteTool.java:822)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(Defau
ltSiteTool.java:540)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRen
deringContext(AbstractSiteRenderingMojo.java:226)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:117
)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
0)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 26 seconds
[INFO] Finished at: Fri Aug 14 22:40:22 BST 2009
[INFO] Final Memory: 49M/254M
[INFO]
----------------
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
David Hoffer wrote:
I don't know about running from the command line...we have our CI system
auto deploy javadocs/source jars to our internal repo so IDE's get this
integrated with the binaries. This is the functionality I was looking for.
Well, I'm getting the website combined javadocs, and I'm getting the
per-module jar'ed javadocs, but not the combined jar'ed javadocs,
because of the message below (afaict). Anyone know how I'd bring this to
the attention of the devs of the maven-javadoc-plugin?
On Fri, Aug 14, 2009 at 8:29 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
David Hoffer wrote:
No any call to install or deploy will build it. This isn't required but
we
do wrap the build section in a profile so we only do this on the CI
system...as this takes a while.
Well, that works very well for putting the aggregated javadoc on the
generated site (once I configured it to generate a site), but the attempt to
javadoc:jar gives me:
[INFO]
[INFO] Building ASN.1 Java Implementation
[INFO]task-segment: [javadoc:jar]
[INFO]
[WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
javadoc
:aggregate and
javadoc:test-aggregate instead.
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package
The deprecation I can deal with later, but the not-running-javadoc is a
pain.
On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
David Hoffer wrote:
This works for us, try this in your parent pom:
When running this, does it need site:site running to build the javadoc
before running a build that'll generate the jar?
org.apache.maven.plugins
maven-javadoc-plugin
2.5
attach-javadocs
jar
...
org.apache.maven.plugins
maven-javadoc-plugin
2.5
true
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
David Hoffer wrote:
No any call to install or deploy will build it. This isn't required but we
do wrap the build section in a profile so we only do this on the CI
system...as this takes a while.
Well, that works very well for putting the aggregated javadoc on the
generated site (once I configured it to generate a site), but the
attempt to javadoc:jar gives me:
[INFO]
[INFO] Building ASN.1 Java Implementation
[INFO]task-segment: [javadoc:jar]
[INFO]
[WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
javadoc
:aggregate and
javadoc:test-aggregate instead.
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
The deprecation I can deal with later, but the not-running-javadoc is a
pain.
On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
David Hoffer wrote:
This works for us, try this in your parent pom:
When running this, does it need site:site running to build the javadoc
before running a build that'll generate the jar?
org.apache.maven.plugins
maven-javadoc-plugin
2.5
attach-javadocs
jar
...
org.apache.maven.plugins
maven-javadoc-plugin
2.5
true
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules) was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
David Hoffer wrote: This works for us, try this in your parent pom: When running this, does it need site:site running to build the javadoc before running a build that'll generate the jar? org.apache.maven.plugins maven-javadoc-plugin 2.5 attach-javadocs jar ... org.apache.maven.plugins maven-javadoc-plugin 2.5 true -Dave On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack < s.barnett-corm...@lancaster.ac.uk> wrote: Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
Stephen Connolly wrote:
my understanding of aggregate is that it has to go where the
(& by implication the dependencies) are
Ah, I see! I got the separation slightly wrong. I've got you now, that's
great. So everything is a module of complete, and a dependency of it,
but a-e declare parent to be their parent. Good.
2009/8/14 Sam Barnett-Cormack :
Ah. Exactly what I meant, but with the names complete and parent the other
way around. With the names your way around, the source and javadoc
aggregators would go in where?
Stephen Connolly wrote:
so to summarize:
/project-complete
+- project-parent
+- project-a
+- project-b
...
\- project-e
project-complete has the following
project-parent
project-___
project-parent
project-a
project-b
...
project-e
project-parent has no section... or at least does not
reference project-complete
project-a, project-b, ..., project-e have the following
project-parent
project-___
2009/8/14 Stephen Connolly :
2009/8/14 Sam Barnett-Cormack :
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be
project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their
parent.
That make sense?
Sam
2009/8/14 Stephen Connolly :
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer :
This works for us, try this in your parent pom:
org.apache.maven.plugins
maven-javadoc-plugin
2.5
attach-javadocs
jar
...
org.apache.maven.plugins
maven-javadoc-plugin
2.5
true
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well,
but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the
modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can
tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
--
Re: javadoc plugin aggregation woes
Ah. Exactly what I meant, but with the names complete and parent the
other way around. With the names your way around, the source and javadoc
aggregators would go in where?
Stephen Connolly wrote:
so to summarize:
/project-complete
+- project-parent
+- project-a
+- project-b
...
\- project-e
project-complete has the following
project-parent
project-___
project-parent
project-a
project-b
...
project-e
project-parent has no section... or at least does not
reference project-complete
project-a, project-b, ..., project-e have the following
project-parent
project-___
2009/8/14 Stephen Connolly :
2009/8/14 Sam Barnett-Cormack :
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their parent.
That make sense?
Sam
2009/8/14 Stephen Connolly :
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer :
This works for us, try this in your parent pom:
org.apache.maven.plugins
maven-javadoc-plugin
2.5
attach-javadocs
jar
...
org.apache.maven.plugins
maven-javadoc-plugin
2.5
true
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
So the one doing the aggregating would have the modules section *and*
have the dependencies? When I've done that and set the parent in each
module, it's complained of cyclic dependencies.
Stephen Connolly wrote:
2009/8/14 Sam Barnett-Cormack :
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their parent.
That make sense?
Sam
2009/8/14 Stephen Connolly :
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer :
This works for us, try this in your parent pom:
org.apache.maven.plugins
maven-javadoc-plugin
2.5
attach-javadocs
jar
...
org.apache.maven.plugins
maven-javadoc-plugin
2.5
true
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
David Hoffer wrote: This works for us, try this in your parent pom: org.apache.maven.plugins maven-javadoc-plugin 2.5 attach-javadocs jar ... org.apache.maven.plugins maven-javadoc-plugin 2.5 true ^^^ Isn't that deprecated now? Just using the aggregate-jar target does no good... I'll try using this. Maybe using the older version also helps. -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be
project-{a,b,c,d,e,}, the modules of project-master would be the same,
and project-{a,b,c,d,e,complete} would declare project-master as their
parent. That make sense?
Sam
2009/8/14 Stephen Connolly :
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer :
This works for us, try this in your parent pom:
org.apache.maven.plugins
maven-javadoc-plugin
2.5
attach-javadocs
jar
...
org.apache.maven.plugins
maven-javadoc-plugin
2.5
true
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack <
s.barnett-corm...@lancaster.ac.uk> wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects, which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules) was
easy. Now I want to create a combined javadoc bundle, and that's not proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by running
the eclipse javadoc builder over multiple projects, but I'd rather integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
javadoc plugin aggregation woes
Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
