jochen-2 wrote:
... because the parent POM doesn't have a site and, in particular, no site
descriptor.
the parent's site.xml isn't deployed to the site repo, it's deployed to the
end-state repo alongside the primary artifact (jar,pom,etc.)
If you want your project's site descriptor to be
Marc Rohlfs wrote:
... It would e.g. be great if I could activate a profile by the
existence of a file whose path contains an interpolatable token (like
'src/main/filters/${target.environment}/something.properties'). But I
understand that something like this might lead to confusing
Evgeny Goldin wrote:
I think this issue opens a wider one: does Maven treat properties like a
mutable variables ...
Yeah, it would be nice to have some middle ground for allowing plugins to
help configure other plugins. Right now the Maven Way is to use the file
system, right? The file
In this thread, things that seem to be in agreement so far:
* Maven 2 and 3 have different interpolation behavior, and the behavior
isn't documented in the compatibility notes
* dynamic variable interpolation doesn't affect determinism, i.e. same input
yields same output
* whether the ability
I seem to remember it always being static. I remember trying that scenario
in Maven 2 and it always remained the same as what was present in
help:effective-pom. i.e. if it shows up in effective-pom, your plugin can't
change it
--
View this message in context:
I'll try to address some of your questions/concerns/suggestions with info on
what I see as practical/supported/reasonable today. I'll leave the bigger
philosophical and architectural ruminations to those more qualified. (I
will say though that you might be interested in the composition versus
you might consider throwing it in a maven plugin (sounds scary, it isn't)
use groovy's ant dsl to slap it together
http://groovy.codehaus.org/Using+Ant+from+Groovy
i'm using that pattern now to wrap around an ant task, you can take a look
at it if you want:
if one of your modules _is_ the custom ant task (one of the modules is a
maven project that codes to ant api and contains the ant task), then you can
do this:
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
...
morty wrote:
... I need to use this custom task across different projects. Do you
suggest that I create a full separate native maven project...
If you want to share build logic across different projects, and especially
if you code to (via Ant task markup in your case) the custom logic, the
you might be able to glean some help from a groovy-based maven plugin I'm
working on
http://code.google.com/p/indoorsdog/source/browse/#svn%2Fjacoco%2Ftrunk%2Fjacoco-maven-plugin
--
View this message in context:
one thing that sticks out is that you aren't binding the gmaven goals, they
are just in in pluginManagementplugins not buildplugins
--
View this message in context:
http://maven.40175.n5.nabble.com/Groovy-Maven-project-and-groovy-tests-tp3344543p3345067.html
Sent from the Maven - Users mailing
Has anyone done this before? Any tricks or hints? I was hoping to use
JaCoCo, but other tool ideas are welcome.
Links:
http://maven.apache.org/plugins/maven-invoker-plugin/examples/post-build-script.html
http://jacoco.org/jacoco/index.html
--
View this message in context:
Stevo Slavić wrote:
... appends submodule artifactId and not corresponding module name from
submodule's
aggregator modules list when constructing submodule scm ...
Is it a different problem than the many-headed*
http://jira.codehaus.org/browse/MNG-3244 ?
* dive into the issue links
target xmlns:jacoco=antlib:org.jacoco.ant
taskdef uri=antlib:org.jacoco.ant
resource=org/jacoco/ant/antlib.xml
classpath
path=/home/lukewpatterson/Desktop/jacocoant.jar /
/taskdef
jacoco:report
executiondata
file file=jacoco.exec
IMHO, a not horrible migration path is:
1. use antrun, surely it can do everything (and more) that your batch file
does
2. later, using knowledge of how you accomplished it in ANT, port it to a
groovy-based plugin that uses ANT DSL
I've found the groovy-based ANT DSL plugin approach great for
Sonja Stocker wrote:
I´ve tried it with
modules
module${project}/module
/modules
in the upper POM and using archetype.properties where this property was
declared: project=PROJECTNAME. But it didn´t work.
Just to clarify, are you saying that ${project} wasn't replaced with the
Andreas Sewe wrote:
But if there are any good workarounds other than
copy-and-pasting scm/connection in all the child POMs I would love to
hear about them.
A lot of people (30 at last count, including myself) would be interested to
see a solution for this. Many related bugs funnel to
Andreas Sewe wrote:
... Would be interesting to know why you are so against using properties
in
/project/scm/*.
Based on what I've experienced, described earlier by Jörg -
Jörg Schaible wrote:
... the release plugin will rewrite the SCM URLs during release and
reolve all
Benjamin Bentmann wrote:
lukewpatterson wrote:
Before, it seems the custom goals were merged with the standard jar
packaging goals.
If you can provide a complete example project to show this merging I
would be really surprised.
lukewpatterson wrote:
Now, it seems like they replace
Seeing different behavior around extensions enabled on jar custom
packaging type.
Using a testing plugin which contains jar as a custom packaging type.
From the plugin's components.xml:
component-set
components
component
roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role
Anyone have any info/background on the goals and properties sections of
archetype-catalog.xml ?
--
View this message in context:
http://maven.40175.n5.nabble.com/archetype-catalog-xml-and-its-properties-and-goals-elements-what-populates-them-tp2799170p2841463.html
Sent from the Maven - Users
Frederic Camblor wrote:
Looks like this maven plugin could feet your needs :
http://haroon.sis.utoronto.ca/zarar/properties-maven-plugin/index.html
you can probably get what you're looking for by using that properties plugin
(making sure it runs before cargo), and then rather than adding
Which is the new way? archetype.xml or archetype-metadata.xml ?
The Guide to Creating Archetypes
http://maven.apache.org/guides/mini/guide-creating-archetypes.html
says to use:
an archetype descriptor (archetype.xml in directory:
src/main/resources/META-INF/maven/).
but then it also says:
... more background info, trying to be more accurate and complete this time,
if anyone sees anything that should be clarified, please jump in ...
antrun is able to see property value changes during an execution run
because of two things:
* it is manually pulling xml out of its own
AFAIK, so if you're trying to configure another plugin with those properties
(i.e. using properties in the plugin's configuration section), you can only
see the antrun-updated values if you don't explicitly reference the
properties in the POM, but instead rely on lazily-resolved expressions
Brian Fox-3 wrote:
... It's possible that this would work correctly in M3
though because of the rework in the resolution.
that would be nice, then the project wouldn't have to be aware of whether or
not it was a module and if the artifact was part of its enclosing
multi-module project
--
Benson Margulies wrote:
process it in the dependency plugin.
what do you mean by process? if you mean copy or unpack, m-d-p [1] has
separate goals for working with artifacts listed in the configuration
section and working with project dependencys
e.g. see copy [2] vs. copy-dependencies
cowwoc wrote:
... one of the arguments equal to ${basedir}/target.
maybe I'm missing something here, but why won't ${project.build.directory}
work?
--
View this message in context:
http://maven.40175.n5.nabble.com/Passing-basedir-into-Exec-plugin-tp512272p696566.html
Sent from the Maven
lukewpatterson wrote:
cowwoc wrote:
... one of the arguments equal to ${basedir}/target.
maybe I'm missing something here, but why won't ${project.build.directory}
work?
nevermind, I see what you are saying now, you want a general way to create a
String parameter value
lukewpatterson wrote:
cowwoc wrote:
... this looks like a bug in the plugin. What do you think?
the parameters are resolved before the plugin even sees them though,
right?
ok, and then the plugin does some massaging, and '\' is an escape character
http://fisheye.codehaus.org
cowwoc wrote:
That works (using quotes) but based on what you wrote above I believe this
is a bug.
1. I am expecting this to work without quotes (since my path does not
contain any spaces)
2. I am expecting to be able to put anything inside the quotes
Do you agree? Should I file a
Stan Devitt-2 wrote:
Why would the recommended format here be different than the format used by
the dependency plugin?
(e.g. junit:junit:jar:3.8.1:test )
I was looking more for a URN for Maven coordinates, which is slightly
different than the flattened form of dependency elements. e.g.
It would be nice to be able to represent any Maven GAV in a string. Does
such a standard exist?
A good use case is for plugins that allow input configuration file paths.
If there was a reusable component that took an ArtifactResolver and a
String, then any plugins that currently accept file
Néstor Boscán wrote:
... custom checkstyle
configuration file. ... But the plugin generates:
Could not find resource URL
is this http://jira.codehaus.org/browse/MCHECKSTYLE-129 the problem?
remember to take into account this http://jira.codehaus.org/browse/MSITE-443
when trying to
not sure how to with antrun, here's a way with gmaven/ant:
http://pastebin.com/XsAdbbcY
two commands of interest:
mvn initialize - you'll see that the property gets changed to the value
retrieved from ant
mvn help:effective-pom - if you look at the project name, just a
reinforcement that if
I'm looking for a plugin which has a fail goal, something like:
mvn fail-maven-plugin:fail -Dfail.maven.plugin.message=you failed!
I've seen how enforcer or antrun can fail on-demand, but I'm looking for
something I can fully configure from the command line
Thanks
--
View this message in
lukewpatterson wrote:
evaluateBeanshell rule:
http://maven.apache.org/plugins/maven-enforcer-plugin/rules/evaluateBeanshell.html
... ${project.basedir} results in a String with '\' characters, which must
be escaped in Java/BeanShell
I created http://jira.codehaus.org/browse/MENFORCER
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
dahoffer wrote:
I want to set the value of a maven property using GMaven, what is the
syntax of this?
I've successfully used:
project.properties.setProperty('propertyName',propertyValue)
--
View this message in context:
What is the likelihood that Maven will someday support multiple configuration
sections of the same plugin? ( http://jira.codehaus.org/browse/MNG-1701
helps restrict the practice )
Here's the use case: In my POM, I want to list the goals in the order that
they occur in the build. It seems like
justinedelson wrote:
Did you look at wagon-svn?
wagon-svn would be great but it doesn't support mime-type auto-props, which
is crucial for site deployment
https://wagon-svn.dev.java.net/issues/show_bug.cgi?id=4
--
View this message in context:
rperez wrote:
... I can accomplish each task at a time but fail to achieve them all in
that order.
It is unfortunate that one can't compose the build section of the pom to
reflect the actual order the goals will be executed. It's not uncommon that
one goal will create the input for the
lukewpatterson wrote:
Is there a complete list of XML _attributes_ supported in the POM?
I think the following are better questions than my previous one:
Can my plugins use XML attributes as part of their configuration? If so,
are there any special attribute names that I need to avoid
Is there a complete list of XML _attributes_ supported in the POM?
e.g.
someConfigurationElement combine.children=append [1]
someConfigurationElement implementation=org.wombat.artifact.MyImpl [2]
[1]
xavier.seignard wrote:
I would like to know how to retrieve list of available versions of a given
plugin with the maven embedder.
In input I only have a groupId, an artifactId, a local repo and a list of
remote repos.
In output I would like to have a list containing all the
ronatartifact wrote:
How is this different from what Eclipse shows?
Can you use their code from the Pom editor?
Thanks, Ron, I'll look into that too.
My initial investigations lead me to DependencyNode:
org.apache.maven.shared.dependency.tree.DependencyNode
It needs a few other
-- It was suggested [1] that I ask this question in a new thread, it might
have gotten lost in the noise --
I'm looking for existing API that will give me a MavenProject's
effective-direct dependencies, taking into account grouped dependencies
[2].
By effective-direct dependencies, I mean: all
Anders Hammar wrote:
a) This is the limitation/drawback of grouped dependencies. The
dependencies
you get through a grouped dependencies will be a level down (actually they
will be transient deps).
The description in grouping dependencies should probably be changed then
from:
You can
Anders Hammar wrote:
Regarding the changes you propose, please file a jira for that.
done: https://issues.sonatype.org/browse/MVNREF-134
Thanks for the help, Anders.
As for the second part of my original questions (question b), is there any
API that will give me a hierarchical view of
Some questions about grouped dependencies [1]:
a) Should dependencies introduced through grouped dependencies be
considered first-order dependencies? In the description of a grouped
dependency pom project: You can ... add this project as a dependency and
all of its dependencies will be added to
Max Spring wrote:
One missing piece: If the instantiated archetype fails to build, I want
the integration test to fail.
So far a failure result is not getting propagated to the outer Maven
execution.
Hmm, I didn't know archetype would ignore failures, I pasted another
solution below.
Sounds like there are two separate problems:
Problem 1:
Stephen Connolly-2 wrote:
however, when you create from an archetype in a directory which
conatins a pom, the created module gets added as a new child module,
so that the build will build the parent and the newly created child
I
mihobson wrote:
... I'd probably also ditch 'src' since 'generated' conceptually replaces
this.
Good point, updated example:
${project.build.directory}/generated/generator-name/main/java
${project.build.directory}/generated/generator-name/test/scala
It seems like
${project.build.directory}/generated-sources/generator-name
and
${project.build.directory}/generated-resources/generator-name
have been mentioned [1][2], but I wonder if something like this
${project.build.directory}/generated/generator-name
is more consistent.
With
stug23 wrote:
There is a Maven XML plugin that uses XSLT to transform a document that
you may want to have a look at:
http://mojo.codehaus.org/xml-maven-plugin/
Thanks Pat, I have found that plugin to be helpful in several scenarios.
Side note, I am waiting for an enhancement of it:
Stephen Connolly-2 wrote:
perhaps versions-maven-plugin can help. (depends on what you want to edit)
Stephen, my use-case is that I rely on some plugins which are configured
exclusively via xml files, and I want to move the
creation/documentation/source of the configuration to the pom. In
Does anyone know of a Maven plugin which provides functionality similar to
the xmltask [1] Ant Task?
description:
Uses include:
* modifying configuration files for applications during builds
...
usage example:
---
original file,
Mirko Friedenhagen wrote:
goal to check classpath for duplicate resources/classes
I haven't tried it yet, but recently I was looking for the same
functionality and ran across JBoss' tattletale tool:
http://www.jboss.org/tattletale http://www.jboss.org/tattletale
JBoss Tattletale is a
Is there a Maven repo search site that can look up consumers of
plugins/dependencies? I would find that useful when I'm trying to use a
plugin that isn't documented that well, I could look at the existing
consumers' usage patterns.
--
View this message in context:
If anyone else wants this functionality, I think my patch should do the job:
https://wagon-svn.dev.java.net/issues/show_bug.cgi?id=4
Please consider voting or commenting.
--
View this message in context:
Ideally, I'd like to find a pure-Java Wagon that can deploy to an SVN repo
and can be configured to accept a file path for the svn:mime-type/auto-props
[1] file. I can deploy my end-states (jars) fine, but deploying the site
has been difficult without automatic mime-type application.
So far, I
Is there a build plugin that can generate the dependency list/tree in XML
format?
I found this open issue
http://jira.codehaus.org/browse/MDEP-145
but it hasn't been released yet.
Thanks,
Luke
--
View this message in context:
Jason van Zyl-5 wrote:
On 27-Jan-09, at 6:41 PM, Barrie Treloar wrote:
repositories. They might become OBRs at some point when OSGi becomes
more mainstream.
One thing I have been toying with for a while is to auto-magically
extend maven-jar-plugin to add the OSGi headers.
I
What is a good generic term and acronym for Nexus? Would it be repository
manager / rm
What about repo browsers (viewvc, fisheye)?
examples:
source code management - scm
continuous integration - ci
issue management system - ims
I'm trying to set up friendly URLs and dns redirects for use in
Is this what you are looking for?
[1]
/**
* All dependencies that this project has, including transitive ones.
* Contents are lazily populated, so depending on what phases have run
dependencies in some scopes won't be included.
* eg. if only compile phase has run,
Here is a snippet from something I'm currently working on. It can see the
transitive dependencies with getArtifacts().
in the mojo:
* @goal add-externalized-properties
* @phase process-resources
* @requiresDependencyResolution compile
*/
public class AddExternalizedPropertiesMojo extends
On a related note, you might want to use the
someEclipseGroupId:Bundle-SymbolicName flavor of the Eclipse dependencies.
I have been looking for official answers to the official Eclipse
coordinates question, but haven't found any. From my understanding of a
discussion [1] on the dev list, the
Andrew Robinson-5 wrote:
BTW, if you plan on using JFace, do not use the libraries from maven,
use your own from eclipse. The maven pom files for the uploaded SWT
and JFace jars are incompatible. I found it much easier to install my
own jars into my local repo than trying to fight the
These are in the repo
groupIdorg.eclipse.swt.gtk.linux/groupId
artifactIdx86_64/artifactId
[1]
groupIdorg.eclipse.swt.gtk.linux/groupId
artifactIdx86/artifactId
[2]
The (groupId/artifactId)s are different than what you had listed.
[1] -
69 matches
Mail list logo
