Re: Broken mvn site
Yes, in 2.x reporting plugins don't use the pluginManagement section, I've never understood why. It's stated *somewhere* in the docs but whether you are going to read it before first hitting the issue is probably unlikely. The whole reporting is going to be revamped in 3.x and I'm sure this is one of the issues that will be dealt with, one way or the other. If you just want your stuff to work, I wouldn't wander to 3.x just yet. How I've dealt with the issue is that I mostly configure the reports in the parent pom and then declare properties if I have to provide special configurations for the child poms. Kalle On Wed, May 19, 2010 at 10:05 AM, Tim Fulmer tful...@dslextreme.com wrote: Hello, Yesterday we noticed an error when running mvn site to generate cobertura reports to track down some coverage issues. Turns out this was caused by a snapshot update mandated by the special way Maven handles plugin versioning. Things got even more special when trying to specify a version of org.apache.maven.plugins:maven-project-info-reports-plugin. Turns out plugin management doesn't work for reporting. The version specified in plugin management is ignored in reporting and the current version is used. Even though the current documentation on configuring reporting shows a plugin management configuration. The solution was to spam a version configuration across 20 some odd POM files. I'm sure we missed a few. This isn't the first time we've been bitten by Maven's special plugin versioning and dependency management. Other's have ongoing issues with this as well. My question is why hasn't this been fixed yet? Why is plugin management the one place where Maven's own versioning and dependency management practices are completely ignored in favor of something that's obviously broken? When is it going to be fixed? -- Tim - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Hi, I'm having some trouble setting up a basic maven project structure. In this case, I'm setting up an EAR project with an EJB and a WAR project inside. I can successfully build the project, but the problem is as follows: I define a defaultJavaBundleDir lib/ on the ear pom. I want every jar dependency to be inside that folder, except the ear modules ejb and war, respectively. It all works well, but looking at the manifest, I see a problem ... the manifest of the war module has every entry with prefixed lib/, so the ejb it depends on is defined in the manifest as lib/my-ejb.jar, when in reality it is stored on the ear root. I was expecting every jar to be prefixed with lib/ except the webModule and ejbModule entries defined in maven-ear-plugin. Isn't it supposed to be like that? How can I make such setup? Note: I'm not generating the ejb client (not using generateClient in ejb pom), should this be a requirement? I'm new to maven+ejb setup like this, so I need a bit of light ... Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28618592.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: Error from maven deploy plugin during release:perform
Hi Ron, Did you end up solving this issue or did you perhaps find a workaround? I'm facing exactly the same issue. (The module deploys fine when using mvn deploy, but not when it is deployed during a mvn release:perform) In my case the project is an ear module in a multi module project. What makes it even weirder is that the distributionManagement section is defined in the parent pom, thus shared by all the other modules. And on all the other modules the deploy works during a release:perform as well. Puzzled Kind regards, Stijn rsmith wrote: I'm trying to sign release my project artifacts to a maven repository. I'm currently getting the following error when executing: mvn -e -X release:perform -Dgpg.useagent=true -Darguments=-Dgpg.useagent=true [INFO] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' -- [INFO] [DEBUG] (f) artifact = org.pyant.tasks:pyAntTasks:jar:1.3.1 [INFO] [DEBUG] (f) attachedArtifacts = [org.pyant.tasks:pyAntTasks:java-source:sources:1.3.1, org.pyant.tasks:pyAntTasks:javadoc:javadoc:1.3.1, org.pyant.tasks:pyAntTasks:jar.asc:1.3.1, org.pyant.tasks:pyAntTasks:pom.asc:1.3.1, org.pyant.tasks:pyAntTasks:asc:sources.jar:1.3.1, org.pyant.tasks:pyAntTasks:asc:javadoc.jar:1.3.1] [INFO] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] [INFO] [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.4 [INFO] [INFO] check that the following section of the pom.xml is present and correct: [INFO] [INFO] distributionManagement [INFO] !-- use the following if you're not using a snapshot version. -- [INFO] repository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /repository [INFO] !-- use the following if you ARE using a snapshot version. -- [INFO] snapshotRepository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /snapshotRepository [INFO] /distributionManagement [INFO] [INFO] Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated [INFO] [INFO] [INFO] [DEBUG] Trace [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.apache.maven.plugins:maven-deploy-plugin. Reason: Unable to parse the created DOM for plugin configuration [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) ... Section of my distributionManagement section: distributionManagement repository idsonatype-nexus-staging/id nameNexus Release Repository/name urlhttp://oss.sonatype.org/service/local/staging/deploy/maven2/url /repository snapshotRepository idsonatype-nexus-snapshots/id nameSonatype Nexus Snapshots/name urlhttp://oss.sonatype.org/service/local/staging/deploy/maven2/url /snapshotRepository /distributionManagement Info on my environment: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.2 arch: x86_64 Family: mac I've searched google/forums for solutions but haven't turned anything up. Anyone seen this before or know what I might try? Regards, Ron -- View this message in context: http://n2.nabble.com/Error-from-maven-deploy-plugin-during-release-perform-tp4822554p4822554.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 -- View this message in context: http://old.nabble.com/Error-from-maven-deploy-plugin-during-release%3Aperform-tp28078671p28618818.html Sent from the Maven - Users mailing list archive at Nabble.com. - To
Re: Problem with the release:perform
Hi Guys, Sorry for the late reply, but I'm now facing the exact same issue as Jouko. (The module deploys fine when using mvn deploy, but not when it is deployed during a mvn release:perform) In my case the project is an ear module in a multi module project. What makes it even weirder is that the distributionManagement section is defined in the parent pom, thus shared by all the other modules. And on all the other modules the deploy works during a release:perform as well. Running with -x -e doesn't really give me any useful extra information. Kind regards, Stijn [INFO] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] [INFO] [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.4 [INFO] [INFO] check that the following section of the pom.xml is present and correct: [INFO] [INFO] distributionManagement [INFO] !-- use the following if you're not using a snapshot version. -- [INFO] repository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /repository [INFO] !-- use the following if you ARE using a snapshot version. -- [INFO] snapshotRepository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /snapshotRepository [INFO] /distributionManagement [INFO] [INFO] Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated [INFO] [INFO] [INFO] [DEBUG] Trace [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.apache.maven.plugins:maven-deploy- plugin. Reason: Unable to parse the created DOM for plugin configuration [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:55 6) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:387) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) [INFO] at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [INFO] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [INFO] at java.lang.reflect.Method.invoke(Method.java:597) [INFO] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [INFO] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [INFO] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [INFO] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Caused by: org.apache.maven.plugin.PluginConfigurationException: Error configuring: org.apache.maven.plugins:mave n-deploy-plugin. Reason: Unable to parse the created DOM for plugin configuration [INFO] at org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1363) [INFO] at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:724) [INFO] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) [INFO] ... 17 more [INFO] Caused by: org.codehaus.plexus.component.configurator.ComponentConfigurationException: Class 'org.apache.maven.ar tifact.repository.ArtifactRepository' cannot be instantiated [INFO] at org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.instantiateObject(Abstra ctConfigurationConverter.java:121) [INFO] at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(O bjectWithFieldsConverter.java:88) [INFO] at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.jav a:247) [INFO] at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguratio n(ObjectWithFieldsConverter.java:137) [INFO] at
[ANN] Maven Project Info Reports Plugin 2.2 Released
Hi, The Maven team is pleased to announce the release of the Maven 2.x Project Info Reports Plugin, version 2.2 NOTE : this version is site plugin 2.1+ required. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin, version 2.2 Bug : * [MPIR-150] - the dependency report ignores mirrors * [MPIR-159] - ZipException during mvn clean compile site * [MPIR-172] - Be sure that anchor are unique * [MPIR-174] - remove use of container.getLoggerManager() (to be compatible wih maven 3.x) * [MPIR-179] - Dependency File Details and Dependency Repository Locations tables have a border when rendered with maven-site-plugin 2.1 Improvement * [MPIR-137] - Dependency Locations should work with an intranet repository and restricted internet access * [MPIR-186] - Update location for Subversion Home page * [MPIR-189] - Allow configuration of mailing list header text. New Feature * [MPIR-170] - Create a module overview page ala m1 Task * [MPIR-101] - Update to Doxia 1.1 * [MPIR-173] - Review the Doxia Sink calls Enjoy, -- The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Shade Plugin 1.3.3 Released
The Maven team is pleased to announce the release of the Maven Shade Plugin, version 1.3.3. This plugin provides the capability to package the artifact in an uber-jar, including its dependencies and to shade - i.e. rename - the packages of some of the dependencies. See the plugin's site for more details: http://maven.apache.org/plugins/maven-shade-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-shade-plugin/artifactId version1.3.3/version /plugin Release Notes - Maven 2.x Shade Plugin - Version 1.3.3 ** Bug * [MSHADE-79] - Annotations are not shaded ** Improvement * [MSHADE-80] - Mark plugin as thread-safe Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619436.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 EAR + EJB ... jars with prefixed lib/ except for EJB
More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619437.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 EAR + EJB ... jars with prefixed lib/ except for EJB
More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619438.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 EAR + EJB ... jars with prefixed lib/ except for EJB
More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619440.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 EAR + EJB ... jars with prefixed lib/ except for EJB
More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619439.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: Broken mvn site
Oh! That's what I originally expected, and then I got tanged up on
stackoverflow with someone who seemed to be complaining of a much
broader prohibition.
On Thu, May 20, 2010 at 1:23 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
no variables in
/project/parent/groupId
/project/parent/artifactId
/project/parent/version
/project/groupId
/project/artifactId
/project/version
is the policy you are refering to... which is to ensure that the project
model can be constructed from the pom.xml
that has no impact on using varibles in dependencies... in fact quite a
number of maven projects use variables in dependencies to ensure that the
same suite of dependencies is pulled
it also has no impact on using varibles in plugins/version... again used by
a number of maven projects
-Stephen
On 19 May 2010 20:43, Benson Margulies bimargul...@gmail.com wrote:
Doesn't the new 'no variables in versions' policy in mvn 3 make this
situation, ahem, even more difficult? Or doesn't that policy apply to
plugin
version elements in the reporting section.
In defense of the OP: he followed a published official example that was
actively misleading. I for one think he's entitled to a small show of
temper.
On Wed, May 19, 2010 at 2:55 PM, Wendy Smoak wsm...@gmail.com wrote:
On Wed, May 19, 2010 at 1:05 PM, Tim Fulmer tful...@dslextreme.com
wrote:
Even though the current documentation on configuring reporting shows a
plugin management configuration. The solution was to spam a version
configuration across 20 some odd POM files. I'm sure we missed a few.
What docs were you looking at, so they can be improved? At least
mention it here, but it needs to get into JIRA so it won't be
overlooked.
You might be able to set a property once and use an ${expression} for
the version to avoid repeating it all over the place, depending on how
your pom hierarchy is arranged. Do you have an organization level
parent pom in place?
What Maven version are you using? No idea if this is something that's
better in Maven 3, but you might try the latest release and see if
you're not already using it.
--
Wendy
-
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
Mojo Command Line Properties
Hi,
How can I access command line properties via a Mojo SubClass.
Now I had this:
/** @parameter default-value=${project} */
private MavenProject mavenProject;
However when I tried to get properties via mavenProject.getProperties(), I
can not access command line properties that I passed.
Any help?
Thanks
--
View this message in context:
http://old.nabble.com/Mojo---Command-Line-Properties-tp28619934p28619934.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 EAR + EJB ... jars with prefixed lib/ except for EJB
Does it work (when deploying in the app server) if you just skip the manifest config part of the war plugin? I was under the impression that the manifest file doesn't really matter for war files, but I could be wrong. (You'd be accessing the classes from the classpath and that's handled by the container.) /Anders On Thu, May 20, 2010 at 12:29, zm _m...@hotmail.com wrote: More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619436.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
How do you mavenize projects ? (EJB, Webapp, JPA under Eclipse)
Hi, I am using Eclipse Galileo. Initially I created several projects (one webapp, one EJB project, one JPA project) in Eclipse, without Maven. The output of these projects is a single EAR file (containing the JAR, WAR files ...). There is no ANT build file. The compilation and creation of the EAR file is automatically generated with Eclipse. I am using Java 6 and Maven 2.0.9. The question is : how do you mavenize these projects ? 1) If I use the command line way to use Maven, under DOS, what do i need to do for each project ? 2) I have installed the m2Eclipse (Maven Integration) plugin for Eclipse. If I use that plugin, how do i proceed ? I just noticed a feature called Enable Dependency Management if i right click on a project. what does it do ? Any suggestion or pointer would be much appreciated. Thanks in advance for helping.
Setting environment variables in the exec plugin
Hi everyone,
I'm trying to execute a Java program accessing native components, following the
very good blog post http://www.buildanddeploy.com/node/17
I however have a problem setting environment variables within the exec plugin.
Here is an extract of my POM :
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.1/version
executions
execution
goals
goalexec/goal
/goals
/execution
/executions
configuration
environmentVariables
keyDYLD_LIBRARY_PATH/key
value${project.build.directory}/thirdparty/vtk/lib/vtk-5.4//value
/environmentVariables
executablejava/executable
arguments
argument-classpath/argument
classpath /
argument
com.artenum.vtk.maven.ConeDemo
/argument
/arguments
/configuration
/plugin
When I run it, I have a java.lang.UnsatisfiedLinkError.
If I do
export DYLD_LIBRARY_PATH=mypath
then it works...
Do you know what is wrong in my exec configuration ?
Thank you
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How do you mavenize projects ? (EJB, Webapp, JPA under Eclipse)
Hi Celinio, You should download the book http://repo.exist.com/dist/maestro/1.7.0/BetterBuildsWithMaven.pdf Chapter 8 gives an example of Maven migration Hope this helps Benoît Le 20 mai 2010 à 15:46, Celinio Fernandes a écrit : Hi, I am using Eclipse Galileo. Initially I created several projects (one webapp, one EJB project, one JPA project) in Eclipse, without Maven. The output of these projects is a single EAR file (containing the JAR, WAR files ...). There is no ANT build file. The compilation and creation of the EAR file is automatically generated with Eclipse. I am using Java 6 and Maven 2.0.9. The question is : how do you mavenize these projects ? 1) If I use the command line way to use Maven, under DOS, what do i need to do for each project ? 2) I have installed the m2Eclipse (Maven Integration) plugin for Eclipse. If I use that plugin, how do i proceed ? I just noticed a feature called Enable Dependency Management if i right click on a project. what does it do ? Any suggestion or pointer would be much appreciated. Thanks in advance for helping. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mojo Command Line Properties
I thought that I could not be here but It was at here: System.getProperties() Thanks -- View this message in context: http://old.nabble.com/Mojo---Command-Line-Properties-tp28619934p28621731.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: How do you mavenize projects ? (EJB, Webapp, JPA under Eclipse)
Thanks very much for these helpful pointers. --- On Thu, 5/20/10, Jeff Jensen jeffjen...@upstairstechnology.com wrote: From: Jeff Jensen jeffjen...@upstairstechnology.com Subject: Re: How do you mavenize projects ? (EJB, Webapp, JPA under Eclipse) To: Maven Users List users@maven.apache.org, cel...@yahoo.com Date: Thursday, May 20, 2010, 7:11 AM Maven Users List rejects my reply as spam (I sent it two times; oh well), so I am sending directly to you as well this time. First item is to install m2eclipse, which you did. Second is to create Maven POMs for each module/Eclipse project (I infer you have not done this as it was not mentioned). You can use m2eclipse to help you create the POMs. Ensure each POM builds correctly from the command line too. Then you can Enable Dep Management. It enables m2eclipse to do many wonderful build things for you, using Maven. Read the features list [0]. You need to use some resources to help with your quest :-). Besides the Maven site, these [1] online free books from Sonatype are very useful. The website and books will explain how to create a POM and run Maven for builds and other activities. [0] http://m2eclipse.sonatype.org [1] http://www.sonatype.com/documentation/books On Thu, 20 May 2010 06:46:42 -0700 (PDT) Celinio Fernandes cel...@yahoo.com wrote: Hi, I am using Eclipse Galileo. Initially I created several projects (one webapp, one EJB project, one JPA project) in Eclipse, without Maven. The output of these projects is a single EAR file (containing the JAR, WAR files ...). There is no ANT build file. The compilation and creation of the EAR file is automatically generated with Eclipse. I am using Java 6 and Maven 2.0.9. The question is : how do you mavenize these projects ? 1) If I use the command line way to use Maven, under DOS, what do i need to do for each project ? 2) I have installed the m2Eclipse (Maven Integration) plugin for Eclipse. If I use that plugin, how do i proceed ? I just noticed a feature called Enable Dependency Management if i right click on a project. what does it do ? Any suggestion or pointer would be much appreciated. Thanks in advance for helping.
Dependency on assembly?
Let's say I have a dependency that looks something like dependency groupIdcom.foo/groupId artifactIdbar/artifactId version1.0/version /dependency This artifact gets deployed with an additional assembly, baz.tar.gz, that I want to make use of in this project. Is baz.tar.gz accessible from this project? If so, how do I reference it? Followup question, what I really want to do is extract baz.tar.gz to directory baz and arrange for baz to be included in an assembly to be built by this project - how would I arrange for that to happen? -- C. Benson Manica cbman...@gmail.com
Re: How do you mavenize projects ? (EJB, Webapp, JPA under Eclipse)
http://repo.exist.com/dist/maestro/1.7.0/BetterBuildsWithMaven.pdf appears to be a broken link. Maybe the server is just down temporarily. On Thu, May 20, 2010 at 8:32 AM, Celinio Fernandes cel...@yahoo.com wrote: Thanks very much for these helpful pointers. --- On Thu, 5/20/10, Jeff Jensen jeffjen...@upstairstechnology.com wrote: From: Jeff Jensen jeffjen...@upstairstechnology.com Subject: Re: How do you mavenize projects ? (EJB, Webapp, JPA under Eclipse) To: Maven Users List users@maven.apache.org, cel...@yahoo.com Date: Thursday, May 20, 2010, 7:11 AM Maven Users List rejects my reply as spam (I sent it two times; oh well), so I am sending directly to you as well this time. First item is to install m2eclipse, which you did. Second is to create Maven POMs for each module/Eclipse project (I infer you have not done this as it was not mentioned). You can use m2eclipse to help you create the POMs. Ensure each POM builds correctly from the command line too. Then you can Enable Dep Management. It enables m2eclipse to do many wonderful build things for you, using Maven. Read the features list [0]. You need to use some resources to help with your quest :-). Besides the Maven site, these [1] online free books from Sonatype are very useful. The website and books will explain how to create a POM and run Maven for builds and other activities. [0] http://m2eclipse.sonatype.org [1] http://www.sonatype.com/documentation/books On Thu, 20 May 2010 06:46:42 -0700 (PDT) Celinio Fernandes cel...@yahoo.com wrote: Hi, I am using Eclipse Galileo. Initially I created several projects (one webapp, one EJB project, one JPA project) in Eclipse, without Maven. The output of these projects is a single EAR file (containing the JAR, WAR files ...). There is no ANT build file. The compilation and creation of the EAR file is automatically generated with Eclipse. I am using Java 6 and Maven 2.0.9. The question is : how do you mavenize these projects ? 1) If I use the command line way to use Maven, under DOS, what do i need to do for each project ? 2) I have installed the m2Eclipse (Maven Integration) plugin for Eclipse. If I use that plugin, how do i proceed ? I just noticed a feature called Enable Dependency Management if i right click on a project. what does it do ? Any suggestion or pointer would be much appreciated. Thanks in advance for helping. -- Elliot - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Anders Hammar wrote: Does it work (when deploying in the app server) if you just skip the manifest config part of the war plugin? I was under the impression that the manifest file doesn't really matter for war files, but I could be wrong. (You'd be accessing the classes from the classpath and that's handled by the container.) /Anders On Thu, May 20, 2010 at 12:29, zm _m...@hotmail.com wrote: More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619436.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 If I skip manifest creation, it will probably work, because every dependencies will be copied to WEB-INF/lib, and since EJB will need manifest and many of the same libs on the EAR, I will end with a monster size EAR package because of duplicated jar dependencies ... :( -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28623056.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 EAR + EJB ... jars with prefixed lib/ except for EJB
Anders Hammar wrote: Does it work (when deploying in the app server) if you just skip the manifest config part of the war plugin? I was under the impression that the manifest file doesn't really matter for war files, but I could be wrong. (You'd be accessing the classes from the classpath and that's handled by the container.) /Anders On Thu, May 20, 2010 at 12:29, zm _m...@hotmail.com wrote: More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619436.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 If I skip manifest creation, it will probably work, because every dependencies will be copied to WEB-INF/lib, and since EJB will need manifest and many of the same libs on the EAR, I will end with a monster size EAR package because of duplicated jar dependencies ... :( -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28623057.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 EAR + EJB ... jars with prefixed lib/ except for EJB
Anders Hammar wrote: Does it work (when deploying in the app server) if you just skip the manifest config part of the war plugin? I was under the impression that the manifest file doesn't really matter for war files, but I could be wrong. (You'd be accessing the classes from the classpath and that's handled by the container.) /Anders On Thu, May 20, 2010 at 12:29, zm _m...@hotmail.com wrote: More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619436.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 If I skip manifest creation, it will probably work, because every dependencies will be copied to WEB-INF/lib, and since EJB will need manifest and many of the same libs on the EAR, I will end with a monster size EAR package because of duplicated jar dependencies ... :( -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28623059.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 EAR + EJB ... jars with prefixed lib/ except for EJB
Anders Hammar wrote: Does it work (when deploying in the app server) if you just skip the manifest config part of the war plugin? I was under the impression that the manifest file doesn't really matter for war files, but I could be wrong. (You'd be accessing the classes from the classpath and that's handled by the container.) /Anders On Thu, May 20, 2010 at 12:29, zm _m...@hotmail.com wrote: More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619436.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 If I skip manifest creation, it will probably work, because every dependencies will be copied to WEB-INF/lib, and since EJB will need manifest and many of the same libs on the EAR, I will end with a monster size EAR package because of duplicated jar dependencies ... :( -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28623061.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 EAR + EJB ... jars with prefixed lib/ except for EJB
Anders Hammar wrote: Does it work (when deploying in the app server) if you just skip the manifest config part of the war plugin? I was under the impression that the manifest file doesn't really matter for war files, but I could be wrong. (You'd be accessing the classes from the classpath and that's handled by the container.) /Anders On Thu, May 20, 2010 at 12:29, zm _m...@hotmail.com wrote: More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619436.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 If I skip manifest creation, it will probably work, because every dependencies will be copied to WEB-INF/lib, and since EJB will need manifest and many of the same libs on the EAR, I will end with a monster size EAR package because of duplicated jar dependencies ... :( -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28623062.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: Mojo Command Line Properties
Hi,
Try with
/**
* The Maven Session Object
*
* @parameter expression=${session}
* @required
* @readonly
*/
protected MavenSession session;
session.getExecutionProperties()
2010/5/20 Sessizlik cem.koc@gmail.com:
Hi,
How can I access command line properties via a Mojo SubClass.
Now I had this:
/** @parameter default-value=${project} */
private MavenProject mavenProject;
However when I tried to get properties via mavenProject.getProperties(), I
can not access command line properties that I passed.
Any help?
Thanks
--
View this message in context:
http://old.nabble.com/Mojo---Command-Line-Properties-tp28619934p28619934.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
--
Olivier
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy
http://www.viadeo.com/fr/profile/olivier.lamy7
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
javadoc throws NPE
I am trying to generate javadoc for a project but javadoc throws NPE without any information. Maven output: Generating C:/ci/svn/project/project-name/trunk/target/site/apidocs\package-use.htm l... Generating C:/ci/svn/project/project-name /trunk/target/site/apidocs\mypackage/\package-use.ht ml... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: Exit code: 1 - java.lang.NullPointerException at com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUse(P ackageUseWriter.java:180) at com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageList( PackageUseWriter.java:124) at com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUse(P ackageUseWriter.java:110) at com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUseFi le(PackageUseWriter.java:99) at com.sun.tools.doclets.formats.html.PackageUseWriter.generate(PackageUseW riter.java:78) at com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWrite r.java:116) at com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoc let.java:92) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(Ab stractDoclet.java:122) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDocl et.java:64) at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42) at com.sun.tools.doclets.standard.Standard.start(Standard.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269) at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143) at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340) at com.sun.tools.javadoc.Start.begin(Start.java:128) at com.sun.tools.javadoc.Main.execute(Main.java:41) at com.sun.tools.javadoc.Main.main(Main.java:31) Command line was: C:\Program Files\Java\jdk1.6.0_20\jre\..\bin\javadoc.exe @options @packages @argfile Refer to the generated Javadoc files in 'C:\ci\svn\isvu\razmjena-aai\trunk\target\site\apidocs' dir. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 50 seconds [INFO] Finished at: Thu May 20 17:55:53 CEST 2010 [INFO] Final Memory: 108M/453M [INFO] Here is javadoc plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.7/version /plugin mvn --version: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: C:\Program Files\Java\jdk1.6.0_20\jre Default locale: hr_HR, platform encoding: Cp1250 OS name: windows 7 version: 6.1 arch: amd64 Family: windows How to solve this? Thanks in advance. Regards, Denis Kranjcec - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is there a way to disable transitive dependencies?
There is a bug logged for it. Vote for it at http://jira.codehaus.org/browse/MNG-2315 Chetan Mehrotra On Tue, May 18, 2010 at 7:48 PM, AVSUNIL sunil...@infosys.com wrote: Hi Ron, I want to do something similar.. but I want to tell maven to exclude all dependencies instead of listing 9 to 11 inside it. Is there a way? dependency groupIdgroup_of_needed_dependecny/groupId artifactIdneeded_dependecny/artifactId version1.8.1/version exclusions exclusion artifactIdALL??/artifactId groupIdALL??/groupId /exclusion exclusion /dependency Thanks Sunil ronatartifact wrote: You can use exclusions to cut out transitive dependencies. In the following example, we want our lms-facades package but we do not want the faces and logging dragged in with it. dependency groupIdcom.artifact_software.lms/groupId artifactIdlms-facades/artifactId version1.8.1/version exclusions exclusion artifactIdjsf-api/artifactId groupIdjavax.faces/groupId /exclusion exclusion artifactIdjsf-impl/artifactId groupIdjavax.faces/groupId /exclusion exclusion artifactIdcommons-logging/artifactId groupIdcommons-logging/groupId /exclusion /exclusions /dependency Ron On 18/05/2010 8:42 AM, AVSUNIL wrote: Hi, I have project A which produces artifact as war. Project A has dependency on project B and it is mentioned in the pom of Project A. Now the build of Project A is acting indifferently in 2 environments a) When I am building from my local/development envionment, it builds the war with only the dependencies mentioned in its pom b) When I build from my test environment, it builds the war with dependecies mentioned in pom as well as dependecies of dependecies. This is undesirable as war will become very big as well as unwanted versions might cree through How do I get the behaviour of my dev env in test env also? How do I make sure dependecies of dependencies does not come inot my war? I am only using pom and and not the assembly descriptor. Both environment have the same build script which checksout the latest from SVN and then does mvn clean mvn compile mvn package Thanks Sunil - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Is-there-a-way-to-disable-transitive-dependencies--tp28595375p28596595.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: javadoc throws NPE
Denis- http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html can you provide us the configuration parameters for: outputDirectory reportOutputDirectory thanks, Martin-- __ Jogi és Bizalmassági kinyilatkoztatás Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt. Subject: javadoc throws NPE Date: Thu, 20 May 2010 18:10:57 +0200 From: denis.kranj...@srce.hr To: users@maven.apache.org I am trying to generate javadoc for a project but javadoc throws NPE without any information. Maven output: Generating C:/ci/svn/project/project-name/trunk/target/site/apidocs\package-use.htm l... Generating C:/ci/svn/project/project-name /trunk/target/site/apidocs\mypackage/\package-use.ht ml... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: Exit code: 1 - java.lang.NullPointerException at com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUse(P ackageUseWriter.java:180) at com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageList( PackageUseWriter.java:124) at com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUse(P ackageUseWriter.java:110) at com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUseFi le(PackageUseWriter.java:99) at com.sun.tools.doclets.formats.html.PackageUseWriter.generate(PackageUseW riter.java:78) at com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWrite r.java:116) at com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoc let.java:92) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(Ab stractDoclet.java:122) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDocl et.java:64) at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42) at com.sun.tools.doclets.standard.Standard.start(Standard.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269) at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143) at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340) at com.sun.tools.javadoc.Start.begin(Start.java:128) at com.sun.tools.javadoc.Main.execute(Main.java:41) at com.sun.tools.javadoc.Main.main(Main.java:31) Command line was: C:\Program Files\Java\jdk1.6.0_20\jre\..\bin\javadoc.exe @options @packages @argfile Refer to the generated Javadoc files in 'C:\ci\svn\isvu\razmjena-aai\trunk\target\site\apidocs' dir. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 50 seconds [INFO] Finished at: Thu May 20 17:55:53 CEST 2010 [INFO] Final Memory: 108M/453M [INFO] Here is javadoc plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.7/version /plugin mvn --version: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: C:\Program Files\Java\jdk1.6.0_20\jre Default locale: hr_HR, platform encoding: Cp1250 OS name: windows 7 version: 6.1 arch: amd64 Family: windows How to solve this? Thanks in advance. Regards, Denis Kranjcec - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
I'm not sure we understand each other. I'm asking you to just skip this part of the war-plugin configuration: archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive You should still keep this: warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes /Anders On Thu, May 20, 2010 at 17:41, zm _m...@hotmail.com wrote: Anders Hammar wrote: Does it work (when deploying in the app server) if you just skip the manifest config part of the war plugin? I was under the impression that the manifest file doesn't really matter for war files, but I could be wrong. (You'd be accessing the classes from the classpath and that's handled by the container.) /Anders On Thu, May 20, 2010 at 12:29, zm _m...@hotmail.com wrote: More Info: In my war pom, I have the following: ... dependencies dependency groupIdcom.test/groupId artifactIdmy-ejb/artifactId typeejb-client/type /dependency ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive /configuration /plugin So I have on ear root the war, the ejb and the ejb-client archives, but the manifest of the war as all entries prefixed with lib/ so it doesn't find the client ... I would need a way of forcing the ejb-client entry to have no prefix (or / prefix). I'm still looking for examples, but without success so far. Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28619436.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 If I skip manifest creation, it will probably work, because every dependencies will be copied to WEB-INF/lib, and since EJB will need manifest and many of the same libs on the EAR, I will end with a monster size EAR package because of duplicated jar dependencies ... :( -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28623056.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 EAR + EJB ... jars with prefixed lib/ except for EJB
On Thu, May 20, 2010 at 10:41 AM, zm _m...@hotmail.com wrote: zm, can you PLEASE hit the send button ONLY ONE TIME in the future?? This is ridiculous. If you aren't sure if a message made it through to the list, check the list archive at Nabble.com. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Project Info Reports Plugin 2.2 Released
Thanks! I tried 2.2 with the site plugin (2.1), but I'm getting: [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) which seems to be caused by: http://jira.codehaus.org/browse/DOXIA-215 Assuming the problem is that the site plugin uses an older version of doxia, is there a way to configure it use doxia 1.1 or is a new release of the site plugin required? Kalle On Thu, May 20, 2010 at 3:04 AM, Olivier Lamy ol...@apache.org wrote: Hi, The Maven team is pleased to announce the release of the Maven 2.x Project Info Reports Plugin, version 2.2 NOTE : this version is site plugin 2.1+ required. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin, version 2.2 Bug : * [MPIR-150] - the dependency report ignores mirrors * [MPIR-159] - ZipException during mvn clean compile site * [MPIR-172] - Be sure that anchor are unique * [MPIR-174] - remove use of container.getLoggerManager() (to be compatible wih maven 3.x) * [MPIR-179] - Dependency File Details and Dependency Repository Locations tables have a border when rendered with maven-site-plugin 2.1 Improvement * [MPIR-137] - Dependency Locations should work with an intranet repository and restricted internet access * [MPIR-186] - Update location for Subversion Home page * [MPIR-189] - Allow configuration of mailing list header text. New Feature * [MPIR-170] - Create a module overview page ala m1 Task * [MPIR-101] - Update to Doxia 1.1 * [MPIR-173] - Review the Doxia Sink calls Enjoy, -- The Maven team - 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: [ANN] Maven Project Info Reports Plugin 2.2 Released
I'm using Maven 2.2.1 and didn't upgrade to the new version of the project info reports and all of my site calls are broken with the same issue. On 5/20/2010 3:37 PM, Kalle Korhonen wrote: Thanks! I tried 2.2 with the site plugin (2.1), but I'm getting: [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) which seems to be caused by: http://jira.codehaus.org/browse/DOXIA-215 Assuming the problem is that the site plugin uses an older version of doxia, is there a way to configure it use doxia 1.1 or is a new release of the site plugin required? Kalle On Thu, May 20, 2010 at 3:04 AM, Olivier Lamyol...@apache.org wrote: Hi, The Maven team is pleased to announce the release of the Maven 2.x Project Info Reports Plugin, version 2.2 NOTE : this version is site plugin 2.1+ required. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin, version 2.2 Bug : * [MPIR-150] - the dependency report ignores mirrors * [MPIR-159] - ZipException during mvn clean compile site * [MPIR-172] - Be sure that anchor are unique * [MPIR-174] - remove use of container.getLoggerManager() (to be compatible wih maven 3.x) * [MPIR-179] - Dependency File Details and Dependency Repository Locations tables have a border when rendered with maven-site-plugin 2.1 Improvement * [MPIR-137] - Dependency Locations should work with an intranet repository and restricted internet access * [MPIR-186] - Update location for Subversion Home page * [MPIR-189] - Allow configuration of mailing list header text. New Feature * [MPIR-170] - Create a module overview page ala m1 Task * [MPIR-101] - Update to Doxia 1.1 * [MPIR-173] - Review the Doxia Sink calls Enjoy, -- The Maven team - 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
Preventing an inherited report from running
I have a master pom that specifies the reports to be run. In one of the child projects I do not want to run one of those reports. How do I prevent it from running? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Re: Preventing an inherited report from running
On Thu, May 20, 2010 at 4:25 PM, Timothy Mcginnis tmcgi...@aessuccess.org wrote: I have a master pom that specifies the reports to be run. In one of the child projects I do not want to run one of those reports. How do I prevent it from running? In general you can't un-inherit things, but some plugins have a skip parameter that you can configure. If that doesn't help, let us know what report it is and how it's configured... -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Preventing an inherited report from running
The skip helps. But there is one I'd like to get rid of, the Cobertura report. And it doesn't have a skip. Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: Wendy Smoak wsm...@gmail.com To: Maven Users List users@maven.apache.org Date: 05/20/2010 04:33 PM Subject: Re: Preventing an inherited report from running On Thu, May 20, 2010 at 4:25 PM, Timothy Mcginnis tmcgi...@aessuccess.org wrote: I have a master pom that specifies the reports to be run. In one of the child projects I do not want to run one of those reports. How do I prevent it from running? In general you can't un-inherit things, but some plugins have a skip parameter that you can configure. If that doesn't help, let us know what report it is and how it's configured... -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
This project has been banned...?
What are the conditions under which the following error message is output by Maven: This project has been banned from the build due to previous failures I am seeing it in a Hudson build. It happens to be marked as --fail-at-end, but I'm not sure if that's the trigger, and I'm not sure how to un-ban a project. Sorry for the clueless questioning; Google results were so skewed in favor of the actual log message that I couldn't find anything about this. Best, Laird
enforcer BeanShell script, retrieving escaped stuff from ExpressionEvaluator
evaluateBeanshell rule:
http://maven.apache.org/plugins/maven-enforcer-plugin/rules/evaluateBeanshell.html
want to do something like this:
directoryScanner = new org.codehaus.plexus.util.DirectoryScanner();
directoryScanner.setBasedir(new java.io.File(${project.basedir}));
...
but ${project.basedir} results in a String with '\' characters, which must
be escaped in Java/BeanShell
it doesn't look like any project objects are passed into the
bsh.Interpreter, e.g. like gmaven does when passing in project instance
ideas?
background: I'm trying to verify that my projects only have /pom.xml and
/src/** on the root
--
View this message in context:
http://old.nabble.com/enforcer-BeanShell-script%2C-retrieving-escaped-stuff-from-ExpressionEvaluator-tp28626298p28626298.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
unable to run jetty
I added this plugin to my pom
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
webAppConfig
contextPath/artms/contextPath
jettyEnvXml${basedir}/jetty-env.xml/jettyEnvXml
/webAppConfig
reloadautomatic/reload
/configuration
dependencies
dependency
groupIdcommons-dbcp/groupId
artifactIdcommons-dbcp/artifactId
version1.2.2/version
scopesystem/scope
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdojdbc/artifactId
version14/version
/dependency
/dependencies
/plugin
when I run the ketty:run I get this error
please tell me what is wrong
+ Error stacktraces are turned on.
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_11
Java home: C:\Program Files\Java\jdk1.6.0_11\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\sairamm\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'E:\dev\apache-maven-2.1.0-bin\apache-maven-2.1.0\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM: gov.audit:Audit.gov:pom:1 of project:
gov.audit:audit.war:war:1 in relative path: ../pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for
project: gov.audit:audit.war:war:1
[DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:8
for project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for
project: org.apache.maven.plugins:maven-plugins:pom:8 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project:
org.apache.maven:maven-parent:pom:5 from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.gmaven:gmaven:pom:1.2 for
project: null:gmaven-plugin:maven-plugin:null from the repository.
[DEBUG] Adding managed dependencies for unknown:gmaven-plugin
[DEBUG] org.slf4j:slf4j-api:jar:1.5.10
[DEBUG] org.sonatype.gossip:gossip:jar:1.2
[DEBUG] org.codehaus.plexus:plexus-classworlds:jar:1.2-alpha-13
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.5
[DEBUG] org.apache.maven:maven-core:jar:2.0.10
[DEBUG] org.apache.maven:maven-project:jar:2.0.10
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.10
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.10
[DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0.10
[DEBUG] org.apache.maven.reporting:maven-reporting-impl:jar:2.0.4.1
[DEBUG] org.apache.maven.shared:file-management:jar:1.2.1
[DEBUG] org.sonatype.gshell:gshell-io:jar:2.0
[DEBUG] jline:jline:jar:0.9.94
[DEBUG] com.thoughtworks.qdox:qdox:jar:1.8
[DEBUG] commons-lang:commons-lang:jar:2.4
[DEBUG] junit:junit:jar:3.8.2
[DEBUG] org.codehaus.gmaven.feature:gmaven-feature-api:jar:1.2
[DEBUG] org.codehaus.gmaven.feature:gmaven-feature-support:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-api:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-support:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-loader:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-1.5:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-1.6:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-1.7:jar:1.2
[DEBUG] org.codehaus.gmaven:gmaven-mojo:jar:1.2
[DEBUG] org.codehaus.gmaven:gmaven-mojo-support:jar:1.2
[DEBUG] org.codehaus.gmaven:gmaven-plugin:jar:1.2
[DEBUG] org.codehaus.gmaven:gmaven-packaging:jar:1.2
[DEBUG] Retrieving parent-POM:
org.mortbay.jetty:modules-extra:pom:7.0.0.pre5 for project:
null:jetty-maven-plugin:maven-plugin:null from the repository.
[DEBUG] Retrieving parent-POM:
org.mortbay.jetty:jetty-project:pom:7.0.0.pre5 for project:
null:modules-extra:pom:null from the repository.
[DEBUG] Retrieving parent-POM: org.mortbay.jetty:jetty-parent:pom:7 for
project: org.mortbay.jetty:jetty-project:pom:7.0.0.pre5 from the repository.
[DEBUG] Adding managed dependencies for unknown:jetty-maven-plugin
[DEBUG] org.mortbay.jetty:servlet-api:jar:3.0.pre4
[DEBUG] org.apache.maven:maven-plugin-tools-api:jar:2.0
[DEBUG] junit:junit:jar:3.8.2
[DEBUG]
Re: Preventing an inherited report from running
It is an easy fix to create that parameter. I guess your best change is to create a jira issue with the plugin and provide a patch. In the mean time, release your own version if you have an artifact repository so each developer can get your own version. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, May 20, 2010 at 10:38 PM, Timothy Mcginnis tmcgi...@aessuccess.org wrote: The skip helps. But there is one I'd like to get rid of, the Cobertura report. And it doesn't have a skip. Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: Wendy Smoak wsm...@gmail.com To: Maven Users List users@maven.apache.org Date: 05/20/2010 04:33 PM Subject: Re: Preventing an inherited report from running On Thu, May 20, 2010 at 4:25 PM, Timothy Mcginnis tmcgi...@aessuccess.org wrote: I have a master pom that specifies the reports to be run. In one of the child projects I do not want to run one of those reports. How do I prevent it from running? In general you can't un-inherit things, but some plugins have a skip parameter that you can configure. If that doesn't help, let us know what report it is and how it's configured... -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. == - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependency on assembly?
On 5/20/2010 11:29 AM, C. Benson Manica wrote: Let's say I have a dependency that looks something like dependency groupIdcom.foo/groupId artifactIdbar/artifactId version1.0/version /dependency This artifact gets deployed with an additional assembly, baz.tar.gz, that I want to make use of in this project. Is baz.tar.gz accessible from this project? Yes, I think so. If so, how do I reference it? The name baz.tar.gz is probably more likely formatted like: artifactId - version - classifier . tar.gz where artifactId = bar and the version is 1.0. So the name would be more like: bar-1.0-baz.tar.gz You can write a dependency on this using groupIdcom.foo/groupId artifactIdbar/artifactId classifierbazclassifer typetar.gz/type Followup question, what I really want to do is extract baz.tar.gz to directory baz and arrange for baz to be included in an assembly to be built by this project - how would I arrange for that to happen? The assembly descriptor supports this directly, I think: use dependencySet and specify unpack. -Marshall Schor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Preventing an inherited report from running
One technique I've had work in the normal build plugins, that probably would work in the reporting ones, is this: Let's say the Cobertura report you're inheriting (from some parent pom, I presume) is configured there with an execution idxyz/id (If it doesn't have this, then it is using some default id - you can find out what it is by running once with the -X parameter, I think) Then, configure your version of the plugin for Cobertura like: execution idxyz/id !-- must match the inherited one -- phase/ !-- override the phase to be no-phase - this keeps this from executing -- I haven't tried this myself, but if you do, I'd like to know if it succeeds in getting rid of this report :-) -Marshall Schor On 5/20/2010 4:38 PM, Timothy Mcginnis wrote: The skip helps. But there is one I'd like to get rid of, the Cobertura report. And it doesn't have a skip. Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: Wendy Smoak wsm...@gmail.com To: Maven Users List users@maven.apache.org Date: 05/20/2010 04:33 PM Subject: Re: Preventing an inherited report from running On Thu, May 20, 2010 at 4:25 PM, Timothy Mcginnis tmcgi...@aessuccess.org wrote: I have a master pom that specifies the reports to be run. In one of the child projects I do not want to run one of those reports. How do I prevent it from running? In general you can't un-inherit things, but some plugins have a skip parameter that you can configure. If that doesn't help, let us know what report it is and how it's configured... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Setting environment variables in the exec plugin
Maybe you need to set the environmentVariables this way (see [1]):
environmentVariables
DYLD_LIBRARY_PATH
${project.build.directory}/thirdparty/vtk/lib/vtk-5.4/
/DYLD_LIBRARY_PATH
/environmentVariables
-Marshall Schor
[1]
http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Mapping_Maps
On 5/20/2010 9:48 AM, Thiébault Benoît wrote:
Hi everyone,
I'm trying to execute a Java program accessing native components, following
the very good blog post http://www.buildanddeploy.com/node/17
I however have a problem setting environment variables within the exec
plugin. Here is an extract of my POM :
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.1/version
executions
execution
goals
goalexec/goal
/goals
/execution
/executions
configuration
environmentVariables
keyDYLD_LIBRARY_PATH/key
value${project.build.directory}/thirdparty/vtk/lib/vtk-5.4//value
/environmentVariables
executablejava/executable
arguments
argument-classpath/argument
classpath /
argument
com.artenum.vtk.maven.ConeDemo
/argument
/arguments
/configuration
/plugin
When I run it, I have a java.lang.UnsatisfiedLinkError.
If I do
export DYLD_LIBRARY_PATH=mypath
then it works...
Do you know what is wrong in my exec configuration ?
Thank you
-
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
Maven 2 WebSphere AS and Portal Plugins
Hello, I'm setting up a build for a series of projects that reference WebSphere Application Server 6 and Portal 6.1. Does anyone know of maven plugin that deals with those products? Please share your experiences. Thanks in advance! Dave PS. I queried the user group through google (websphere inurl: http://mail-archives.apache.org/mod_mbox/maven-users/) and found only 2 threads. Does any one know if the user group is indexed/searchable through google?
Re: Maven 2 WebSphere AS and Portal Plugins
Hi Dave, in the past I had some experiences with was6-maven-plugin ( http://mojo.codehaus.org/was6-maven-plugin/) and successfully used it to generate the needed codes for simple EJB and Webservice projects. You have to know, that this plugin actually delegates this work to the tools created by IBM and needs an installed WebSphere AS, Process Server or Portal Server on the machine you do the build. As far as I can remember, Portal projects are built into a simple war file, so strictly speaking the build should not be a problem. It is usually a problem, that into the deployment descriptors of such project you want to put environment-specific information, which may introduce the topic of maven profiles, but maybe others can give you better advice on this. As I do not know too much about your projects, but the more IBM-specific things you use, the more harder it will be to handle those situations. Another issue is that I suppose you use IBM-specific jars in your projects, that are not in the standard repositories, so you need to add them manually to your repository. Best regards, Balazs 2010/5/21 D D dawi...@gmail.com Hello, I'm setting up a build for a series of projects that reference WebSphere Application Server 6 and Portal 6.1. Does anyone know of maven plugin that deals with those products? Please share your experiences. Thanks in advance! Dave PS. I queried the user group through google (websphere inurl: http://mail-archives.apache.org/mod_mbox/maven-users/) and found only 2 threads. Does any one know if the user group is indexed/searchable through google?
Re: Release Plugin and local working copy changes
Finally got around to catching up with the guy who reported this problem to me originally - they were running 2.0-beta-8 which I think was fixed in the master pom - adding a dependency block to use 2.0 solved the problems.. Looks like at some point they had their subversion server updated. I was running the same plugin version, but our subversion server is still 1.4.x so we never encountered the problems. Mark -- Pull me down under... On Fri, Apr 30, 2010 at 1:32 AM, Tim O'Brien tobr...@discursive.com wrote: What version of the release plugin are you using?
Re: Is there a way to disable transitive dependencies?
Hi all, Somehow I fixed this after manual comparision of every maven files between the 2 environments. The environment where this problem was present, had incorrect settings.xml. The mirrorID was incorrectly mentioned same as server repository id. I changed to proxy repository id and it started working fine. Thanks Sunil chetan mehrotra wrote: There is a bug logged for it. Vote for it at http://jira.codehaus.org/browse/MNG-2315 Chetan Mehrotra On Tue, May 18, 2010 at 7:48 PM, AVSUNIL sunil...@infosys.com wrote: Hi Ron, I want to do something similar.. but I want to tell maven to exclude all dependencies instead of listing 9 to 11 inside it. Is there a way? dependency groupIdgroup_of_needed_dependecny/groupId artifactIdneeded_dependecny/artifactId version1.8.1/version exclusions exclusion artifactIdALL??/artifactId groupIdALL??/groupId /exclusion exclusion /dependency Thanks Sunil ronatartifact wrote: You can use exclusions to cut out transitive dependencies. In the following example, we want our lms-facades package but we do not want the faces and logging dragged in with it. dependency groupIdcom.artifact_software.lms/groupId artifactIdlms-facades/artifactId version1.8.1/version exclusions exclusion artifactIdjsf-api/artifactId groupIdjavax.faces/groupId /exclusion exclusion artifactIdjsf-impl/artifactId groupIdjavax.faces/groupId /exclusion exclusion artifactIdcommons-logging/artifactId groupIdcommons-logging/groupId /exclusion /exclusions /dependency Ron On 18/05/2010 8:42 AM, AVSUNIL wrote: Hi, I have project A which produces artifact as war. Project A has dependency on project B and it is mentioned in the pom of Project A. Now the build of Project A is acting indifferently in 2 environments a) When I am building from my local/development envionment, it builds the war with only the dependencies mentioned in its pom b) When I build from my test environment, it builds the war with dependecies mentioned in pom as well as dependecies of dependecies. This is undesirable as war will become very big as well as unwanted versions might cree through How do I get the behaviour of my dev env in test env also? How do I make sure dependecies of dependencies does not come inot my war? I am only using pom and and not the assembly descriptor. Both environment have the same build script which checksout the latest from SVN and then does mvn clean mvn compile mvn package Thanks Sunil - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Is-there-a-way-to-disable-transitive-dependencies--tp28595375p28596595.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 -- View this message in context: http://old.nabble.com/Is-there-a-way-to-disable-transitive-dependencies--tp28595375p28629892.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
