Method calculateLink threw exception...
Hi, I'm having issues with mvn site resulting in a NullPointer exception. Could someone give me a hint what can cause these exceptions? regards Thomas [INFO] Generating Developer Activity report--- maven-changelog-plugin:2.2 [INFO] Using existing changelog.xml... [DEBUG] Multipage report: 0 subreports [DEBUG] Velocimacro : added #link( href name target img position alt border width height ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #image( img alt border width height ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #banner( banner id ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #links( links ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #breadcrumbs( breadcrumbs ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #displayTree( display item ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #menuItem( item ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #mainMenu( menus ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #copyright( ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #publishDate( position publishDate version ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #poweredByLogo( poweredBy ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #googleAnalytics( accountId ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [ERROR] Method calculateLink threw exception for reference $PathTool in template org/apache/maven/doxia/siterenderer/resources/default-site.vm at [2,29] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.564s [INFO] Finished at: Wed Jan 18 10:18:07 CET 2012 [INFO] Final Memory: 26M/618M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project mycore-parent: Error during page generation: Error while generating code. Invocation of method 'calculateLink' in class org.codehaus.plexus.util.PathTool threw exception java.lang.NullPointerException @ org/apache/maven/doxia/siterenderer/resources/default-site.vm[2,39] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project mycore-parent: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at
Re: Method calculateLink threw exception...
Check that all item elements in your site.xml have a href, see http://jira.codehaus.org/browse/MSITE-619 HTH, -Lukas Thomas Scheffler wrote: Hi, I'm having issues with mvn site resulting in a NullPointer exception. Could someone give me a hint what can cause these exceptions? regards Thomas [INFO] Generating Developer Activity report --- maven-changelog-plugin:2.2 [INFO] Using existing changelog.xml... [DEBUG] Multipage report: 0 subreports [DEBUG] Velocimacro : added #link( href name target img position alt border width height ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #image( img alt border width height ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #banner( banner id ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #links( links ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #breadcrumbs( breadcrumbs ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #displayTree( display item ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #menuItem( item ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #mainMenu( menus ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #copyright( ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #publishDate( position publishDate version ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #poweredByLogo( poweredBy ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #googleAnalytics( accountId ) : source = org/apache/maven/doxia/siterenderer/resources/default-site.vm [ERROR] Method calculateLink threw exception for reference $PathTool in template org/apache/maven/doxia/siterenderer/resources/default-site.vm at [2,29] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.564s [INFO] Finished at: Wed Jan 18 10:18:07 CET 2012 [INFO] Final Memory: 26M/618M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project mycore-parent: Error during page generation: Error while generating code. Invocation of method 'calculateLink' in class org.codehaus.plexus.util.PathTool threw exception java.lang.NullPointerException @ org/apache/maven/doxia/siterenderer/resources/default-site.vm[2,39] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project mycore-parent: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at
Re: mvn dependency:get trying to get artifact from internal repo instead of artifact
I'll check that and will get back to you. Thanks for the help. --Jose On Jan 16, 2012, at 7:59 PM, Wayne Fay wrote: I did indeed read the manual and even search the web for examples before posting on this list; My mvn installation (3.0.3) doesn't: * Recognize repositoryUrl, I get an 'repositoryUrl' for goal org.apache.maven.plugins:maven-dependency-plugin:2.1:get are missing or invalid' * remoteRepositories is completely ignored Your Maven logs shows you are using plugin version 2.1. The online plugin documentation is talking about version 2.4. This most likely explains any disparities you have encountered. Use the long form of the plugin to be sure you are using the version you intend to use. Wayne - 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
Re: Skipping the TAR packaging step
Wayne,
Thanks for the reply.
I am the resident expert with Maven, so I am the only help I have. If we
had someone like you are describing, I would very happy indeed. So far
though, things are looking good, but it's like walking through the dark with
a flashlight.
As for the other formats, I'm not looking to get rid of them forever, only
in the iterative development cycle where I compile, deploy and test upwards
to 20 times a day. The jar is all I need in this situation.
The old build was done exclusively with Ant.
My guess about why I'm generating so many different deployment artifacts is
that it is due to the assembly plugin in my project pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version${maven.assembly.plugin.version}/version
executions
execution
idcreate-project-bundle/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptorRefs
descriptorRefproject/descriptorRef
/descriptorRefs
/configuration
/execution
/executions
/plugin
Is there a way to configure this to only generate the jar? If I am to use
the shade plugin, how do I configure it to indicate the suppression I'm
looking for? I read the usage page for both plugins but haven't found what
I'm looking for (though I admit I could easily have missed it).
Thanks,
Scott
--
View this message in context:
http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5154628.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven plugin configuration and binding execution to a phase/goal
Hi Manfred,
I've already posted my Android related questions on the Android Dev forum
yesterday that motivated the need for this.
These question here remain outstanding and all pertain solely to Maven...
can someone please answer these...
(1) Configuration parameters - just using aVal did not work! There is some
other problem below that I cannot spot. Do I need a maven plugin xml to
make this happen?
(2) How do I bind to the right phase/goal without needing executions?
Thanks!
On Wed, Jan 18, 2012 at 12:03 AM, Manfred Moser manf...@mosabuam.comwrote:
On 12-01-17 07:24 PM, Jeff Trent wrote:
I am stuck on two things while writing a plugin: (1) configuration,
and (2) binding to the right goal/phase automatically. I am using
Maven 3.0.3, and trying to use the plugin for APK (android) packaged
modules.
(1) configuration.
/**
* @phase compile
* @goal myGoal
* @requiresDependencyResolution runtime
*/
public class MyMojo extends AbstractMojo {
/**
* @parameter expression=${myGoal.aVal} default-value=defaultVal
*/
String aVal;
…
}
And in my pom using the plugin:
build
plugins
plugin
groupIdmy.package/groupId
artifactIdmy-plugin-test/**artifactId
version1.0-SNAPSHOT/**version
configuration
aValmyConfiguredValue/aVal
/configuration
executions
execution
phasegenerate-resources/
**phase
goals
goalmyGoal/goal
/goals
/execution
/executions
/plugin
...
The problem is that I always get the default value instead of the
configured value. What am I missing?
Am I required to provide the plugin.xml file, even for this simple case?
(2) Binding to the right goal/phase.
Ideally in the above example I don't want to specifyexecutions for
my plugin. But I can't figure out how to vary my annotations to get
it to work.
Can someone point out the problem, or a simple concrete example that
demonstrates this case please?
Thanks,
CP
The expression should just be aVal... btw. what are you trying to do that
the Android Maven Plugin does not do? You could implement the feature as a
mojo there become part of that strong community..
manfred
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Profile activation by OS/Arch and by Property doesn't work
Hi, I'm using Maven to install two pieces of Software on several testing machines. I defined a profile in the settings.xml of every machine for every Software-OS-Arch combination I try to test. If the correct profile is activated, several properties are set, to identify the correct artifact to download from the nexus repository, to set the correct setup-executable and the correct installation directory, which are used later by a POM to install the right version of the right software to the specified directory. All with one POM and just different profiles in settings.xml. My profiles look like the following: profile idwin_32_cadenza/id activation os familyWindows/family archx86/arch /os property nameenvironment/name valueCadenzaCD/value /property /activation properties classifierWIN32/classifier responseFileresponse_win32.varfile/responseFile setupExecutableSetup-Windows.exe/setupExecutable installationDirCadenza autodeploy/installationDir /properties /profile The other profiles are nearly identical, but they are activated by archamd64/arch (or x64) for example and a different environment value (GISterm) for the other software. My problem is, that more than one of these profiles is activated. Even the profile with os familyunix/family/os is activated on a Windows-machine! I test it, with mvn help:active-profiles -Denvironment=CadenzaCD. Response is: - nexus (source: settings.xml) - win_32_cadenza (source: settings.xml) - win_32_gisterm (source: settings.xml) - win_amd64_cadenza (source: settings.xml) - win_x64_cadenza (source: settings.xml) - linux_cadenza (source: settings.xml) An interesting thing is, that on the win-32bit-machine both software-profiles (Cadenza and GISterm) are activated (even I set the property to CadenzaCD and NOT GIStermCD), while the other profiles (which should definitely not run on a windows-32-bit machine) only list the Cadenza-Profiles. Can anybody explain this behaviour to me? Thanks. Benjamin -- View this message in context: http://maven.40175.n5.nabble.com/Profile-activation-by-OS-Arch-and-by-Property-doesn-t-work-tp5154834p5154834.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skipping the TAR packaging step
Hi,
from what you provide us, I think that you are using the predefined
descriptor 'project' of maven assembly plugin which produces by default
a zip, a tar.gz and a tar.bz2 file
(http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html).
Now, if you want a single big fat jar containing all the classes, just
switch to the descriptor 'jar-with-dependencies' which will unpack all
the jar you depend on and recreate a big jar file containing all the
unpacked classes, plus, the ones of your current project.
Now, if you want to keep those three files (zip, tar.gz and tar.bz2) but
you want to have 2 different kind of builds:
* one that produces the jar file of the current project
* one that produces everything as now
You have two options:
1) you create 2 profiles, one that contains the maven assembly plugin
and another one without it.
2) you bind the assembly plugin to a phase which is after the phase
package (for example, verify), and in the first case you only call
'mvn package' and the second one you call 'mvn verify'
If what you want is to have a build with:
* one that produces the big fat jar file
* one that produces everything as now
Your only choice is to use profile and configure the maven assembly
plugin differently in each profile.
If you look for information on profiles, go here:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
If you look for information on lifecylce, phases, etc..., go here:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
Be careful with profiles because, as mentioned on the maven site, there
are several pitfalls to profiles.
Cheers,
Guillaume
Le 18/01/2012 12:52, jackett_dad a écrit :
Wayne,
Thanks for the reply.
I am the resident expert with Maven, so I am the only help I have. If we
had someone like you are describing, I would very happy indeed. So far
though, things are looking good, but it's like walking through the dark with
a flashlight.
As for the other formats, I'm not looking to get rid of them forever, only
in the iterative development cycle where I compile, deploy and test upwards
to 20 times a day. The jar is all I need in this situation.
The old build was done exclusively with Ant.
My guess about why I'm generating so many different deployment artifacts is
that it is due to the assembly plugin in my project pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version${maven.assembly.plugin.version}/version
executions
execution
idcreate-project-bundle/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptorRefs
descriptorRefproject/descriptorRef
/descriptorRefs
/configuration
/execution
/executions
/plugin
Is there a way to configure this to only generate the jar? If I am to use
the shade plugin, how do I configure it to indicate the suppression I'm
looking for? I read the usage page for both plugins but haven't found what
I'm looking for (though I admit I could easily have missed it).
Thanks,
Scott
--
View this message in context:
http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5154628.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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
Re: Method calculateLink threw exception...
Am 18.01.2012 10:27, schrieb Lukas Theussl: Check that all item elements in your site.xml have a href, see http://jira.codehaus.org/browse/MSITE-619 Thank you, I had a construct like this before item name=foo1 item name=bar1 href=../ item name=bar2 href=../ item name=bar3 href=../ /item item name=foo2 item name=baz1 href=../ item name=baz2 href=../ item name=baz3 href=../ /item After adding 'href=#' to every submenu item it works again. Mhh! regards, Thomas -- Thomas Scheffler Friedrich-Schiller-Universität Jena Thüringer Universitäts- und Landesbibliothek Bibliotheksplatz 2 07743 Jena Phone: ++49 3641 940027 FAX: ++49 3641 940022 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Profile activation by OS/Arch and by Property doesn't work
Ok. I mastered it :-) I have to use the or to combine them. activationor if1if2/or/activation -- View this message in context: http://maven.40175.n5.nabble.com/Profile-activation-by-OS-Arch-and-by-Property-doesn-t-work-tp5154834p5154899.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skipping the TAR packaging step
Thanks, Guillaume. I'll read through the links you've provided carefully to see if I can make this happen. Scott -- View this message in context: http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5154907.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven plugin configuration and binding execution to a phase/goal
On 18 January 2012 13:32, C Potter cabin.pot...@gmail.com wrote:
Hi Manfred,
I've already posted my Android related questions on the Android Dev forum
yesterday that motivated the need for this.
These question here remain outstanding and all pertain solely to Maven...
can someone please answer these...
(1) Configuration parameters - just using aVal did not work! There is some
other problem below that I cannot spot. Do I need a maven plugin xml to
make this happen?
(2) How do I bind to the right phase/goal without needing executions?
You don't... unless you implement a custom packaging type
Thanks!
On Wed, Jan 18, 2012 at 12:03 AM, Manfred Moser manf...@mosabuam.comwrote:
On 12-01-17 07:24 PM, Jeff Trent wrote:
I am stuck on two things while writing a plugin: (1) configuration,
and (2) binding to the right goal/phase automatically. I am using
Maven 3.0.3, and trying to use the plugin for APK (android) packaged
modules.
(1) configuration.
/**
* @phase compile
* @goal myGoal
* @requiresDependencyResolution runtime
*/
public class MyMojo extends AbstractMojo {
/**
* @parameter expression=${myGoal.aVal} default-value=defaultVal
*/
String aVal;
…
}
And in my pom using the plugin:
build
plugins
plugin
groupIdmy.package/groupId
artifactIdmy-plugin-test/**artifactId
version1.0-SNAPSHOT/**version
configuration
aValmyConfiguredValue/aVal
/configuration
executions
execution
phasegenerate-resources/
**phase
goals
goalmyGoal/goal
/goals
/execution
/executions
/plugin
...
The problem is that I always get the default value instead of the
configured value. What am I missing?
Am I required to provide the plugin.xml file, even for this simple case?
(2) Binding to the right goal/phase.
Ideally in the above example I don't want to specifyexecutions for
my plugin. But I can't figure out how to vary my annotations to get
it to work.
Can someone point out the problem, or a simple concrete example that
demonstrates this case please?
Thanks,
CP
The expression should just be aVal... btw. what are you trying to do that
the Android Maven Plugin does not do? You could implement the feature as a
mojo there become part of that strong community..
manfred
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-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
Re: maven-plugin-tools-ant custom parameter
On Tue, Jan 17, 2012 at 10:43:10PM +0100, Robert Scholte wrote: Hi Max, Don't confuse a mojo with a pojo. The Mojo reflects the actual goal, supports injection, etc, etc. A pojo is just that plain old java object: private fields with their getters and setters Only for mojo's the @parameters can be used. Such field can be of a lot of types: String, primitive, pojo, array or List of one of these types (as long as Plexus can transform it) The @parameter on the name of the person won't work. It would be nice if the rules were documented somewhere. I strongly advice you to first read the 5 minutes[1] and 30 minutes[2] tutorials. I wish him luck. They leave a lot out. At least, I *think* they do, because I had a lot of questions that don't seem to be answered anywhere. I went digging in the code, wound up deep inside Plexus, submitted a documentation patch for the bits I managed to understand, but still felt no certainty. So what *are* we supposed to do if we want structured parameters? And where should I have read that? -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgpPbc6RUrz87.pgp Description: PGP signature
Re: Skipping the TAR packaging step
You will probably get a big improvement by breaking your project into
smaller functional modules (Think SOA) that are more stable and do not
have to be compiled for every change.
They just become dependencies in the higher level modules and are
brought in automatically by maven as required.
Ron
On 17/01/2012 4:29 PM, jackett_dad wrote:
Hello,
I'm working on a large project that takes time to compile. I would like to
instruct Maven to only build the jar file, but after the build I have a tar,
tar.bz2, and a zip file. I am brand new to Maven, but have converted a
project to use Maven for the compilation of all component modules. In
general, I want to indicate to Maven to only create me a jar with all
dependencies rolled into that jar, and nothing else. This can be for a
particular profile, one for specific for development. The wait is too long
when I make a small change.
So I have a parent pom that is the kind that aggregates all sub-modules. In
any given module that I want to generate an executable jar for, I have a
section that looks like this:
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
version${maven.assembly.plugin.version}/version
configuration
descriptors
descriptor../config/maven/single-jar-assembly.xml/descriptor
/descriptors
archive
manifest
mainClasscom.company.MainClass/mainClass
/manifest
/archive
/configuration
/plugin
/plugins
/build
The assembly starts like this:
assembly
xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd;
idall/id
formats
formatjar/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
I don't have any concept of a profile right now, but I want right now to
simply suppress the creation of all the extra build artifacts. Is there a
way to do that?
Sorry if it's been asked before, but I have either not found it, or when I
did find it, I didn't understand what needed to be done. I barely eked out
the assembly.xml that I did create.
Thanks for any help you can provide,
Scott
--
View this message in context:
http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5152958.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Changing the working directory of the release plugin...
Am 17.01.2012 23:48, schrieb Thiessen, Todd (Todd): Does anyone know how to change the working directory, that the prepare phase of the release plugin uses, without also changing where it checkouts out the tag? Basically, I want to run the top level pom, but from a different working directory. Not quite sure I got your requirement right. mvn -f $pathToPom might be your friend. Best regards, Ansgar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Changing the working directory of the release plugin...
You got it. However, during the perform phase of the release plugin, you don't have that kind of control. The release plugin does a checkout from the tag and then issues a deploy on your behalf. I am not able to issue a mvn -f. Not that I know of anyway. -Original Message- From: Ansgar Konermann [mailto:ansgar.konerm...@googlemail.com] Sent: Wednesday, January 18, 2012 1:34 PM To: users@maven.apache.org Subject: Re: Changing the working directory of the release plugin... Am 17.01.2012 23:48, schrieb Thiessen, Todd (Todd): Does anyone know how to change the working directory, that the prepare phase of the release plugin uses, without also changing where it checkouts out the tag? Basically, I want to run the top level pom, but from a different working directory. Not quite sure I got your requirement right. mvn -f $pathToPom might be your friend. Best regards, Ansgar - 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
Re: Changing the working directory of the release plugin...
Am 18.01.2012 20:00, schrieb Thiessen, Todd (Todd): You got it. However, during the perform phase of the release plugin, you don't have that kind of control. The release plugin does a checkout from the tag and then issues a deploy on your behalf. I am not able to issue a mvn -f. Not that I know of anyway. Next guess: mvn -DworkingDirectory=$yourFavouriteDirectory release:perform Not sure if it needs to be passed via -Darguments=... also, probably not. HTH Ansgar -Original Message- From: Ansgar Konermann [mailto:ansgar.konerm...@googlemail.com] Sent: Wednesday, January 18, 2012 1:34 PM To: users@maven.apache.org Subject: Re: Changing the working directory of the release plugin... Am 17.01.2012 23:48, schrieb Thiessen, Todd (Todd): Does anyone know how to change the working directory, that the prepare phase of the release plugin uses, without also changing where it checkouts out the tag? Basically, I want to run the top level pom, but from a different working directory. Not quite sure I got your requirement right. mvn -f $pathToPom might be your friend. Best regards, Ansgar - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Changing the working directory of the release plugin...
Interesting. I didn't know there was such a property to set. Thanks for the tip. I'll play with that. -Original Message- From: Ansgar Konermann [mailto:ansgar.konerm...@googlemail.com] Sent: Wednesday, January 18, 2012 2:13 PM To: users@maven.apache.org Subject: Re: Changing the working directory of the release plugin... Am 18.01.2012 20:00, schrieb Thiessen, Todd (Todd): You got it. However, during the perform phase of the release plugin, you don't have that kind of control. The release plugin does a checkout from the tag and then issues a deploy on your behalf. I am not able to issue a mvn -f. Not that I know of anyway. Next guess: mvn -DworkingDirectory=$yourFavouriteDirectory release:perform Not sure if it needs to be passed via -Darguments=... also, probably not. HTH Ansgar -Original Message- From: Ansgar Konermann [mailto:ansgar.konerm...@googlemail.com] Sent: Wednesday, January 18, 2012 1:34 PM To: users@maven.apache.org Subject: Re: Changing the working directory of the release plugin... Am 17.01.2012 23:48, schrieb Thiessen, Todd (Todd): Does anyone know how to change the working directory, that the prepare phase of the release plugin uses, without also changing where it checkouts out the tag? Basically, I want to run the top level pom, but from a different working directory. Not quite sure I got your requirement right. mvn -f $pathToPom might be your friend. Best regards, Ansgar - 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 - 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
Re: Skipping the TAR packaging step
Right now the entire project is being refactored, so I don't have much of a choice right now. -- View this message in context: http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5156037.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Combining profile activation parameters doesn't work
http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html 5.3.1. Activation Configuration Activations can contain one of more selectors including JDK versions, Operating System parameters, files, and properties. A profile is activated when all activation criteria has been satisfied. For example, a profile could list an Operating System family of Windows, and a JDK version of 1.4, this profile will only be activated when the build is executed on a Windows machine running Java 1.4. That means my profiles should work ... Anybody else had similar problems? I definitaly can activate Windows and Unix profiles at the same time on the same machine, just by adding a property. -- View this message in context: http://maven.40175.n5.nabble.com/Combining-profile-activation-parameters-doesn-t-work-tp5154834p5156971.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
