Re: Accessing licenses/license as POM properties?
This seems to be a bug or something not quite right with the
bnd-maven-plugin. I've filed an issue:
https://github.com/bndtools/bnd/issues/2454
Plugins like the maven-jar-plugin (and evidently the
maven-bundle-plugin) appear to do the right thing, but the
bnd-maven-plugin seems not to. Strangely, other expressions (like
${project.description}) are expanded properly, but more complex
expressions aren't.
--
Mark Raynsford | http://www.io7m.com
pgpFjONIzyHYR.pgp
Description: OpenPGP digital signature
Re: Accessing licenses/license as POM properties?
On 2018-05-19T14:35:25 +0200
Andreas Sewe wrote:
>
> Maybe it depends on the Maven version (here: 3.5.2)? Try to clone the
> above Github repository, do a "mvn clean verify" and check what "unzip
> -p
> bundles/com.ctrlflow.aer.client.dto/target/com.ctrlflow.aer.client.dto-2.0.2-SNAPSHOT.jar
> META-INF/MANIFEST.MF" outputs for you.
I'm on 3.5.2:
Apache Maven 3.5.2 (NON-CANONICAL_2017-10-25T13:09:52+03:00_root;
2017-10-25T11:09:52+01:00)
Maven home: /opt/maven
Java version: 10.0.1, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-10-openjdk
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.16.4-1-arch", arch: "amd64", family: "unix"
Your bundles have the correct manifest entries on my system:
Bundle-License: https://www.eclipse.org/legal/epl-v10.html;description
="Eclipse Public License"
> Also, check what "mvn help:effective-pom" produces on your project vs.
> my project.
The effective POM for my project shows the unexpanded
${project.licenses[0]} text.
I feel like I might be running into a bug here... Going to attempt to
produce a repro case and submit an issue to the tracker.
--
Mark Raynsford | http://www.io7m.com
pgpEqdLJo6A61.pgp
Description: OpenPGP digital signature
Re: Accessing licenses/license as POM properties?
Mark Raynsford wrote:
> Spoke a bit too soon. I'm using the bnd-maven-plugin, but I don't think
> that changes anything. I have:
>
>
> biz.aQute.bnd
> bnd-maven-plugin
> ${io7m.bnd-maven-plugin.version}
>
>
>
>
>
> Unfortunately, the resulting bundle manifest is:
>
> Bundle-Description Contract checking
> Bundle-License ${project.licenses[0].name}
>
> It seems that the array reference isn't being expanded. If I specify
> ${project.licenses}, I instead get:
>
> Bundle-License [org.apache.maven.model.License@3eba57a7]
>
> ... which is clearly the result of calling toString() on something
> that hasn't overridden it. Point is that the project.licenses property
> is definitely present, it's just that I'm unable to access any of the
> elements.
That is odd. I just rebuild my project [1] again and checked
MANIFEST.MF, as included in the JAR, and everything is as it should be:
> Bundle-License: https://www.eclipse.org/legal/epl-v10.html;description
> ="Eclipse Public License"
Maybe it depends on the Maven version (here: 3.5.2)? Try to clone the
above Github repository, do a "mvn clean verify" and check what "unzip
-p
bundles/com.ctrlflow.aer.client.dto/target/com.ctrlflow.aer.client.dto-2.0.2-SNAPSHOT.jar
META-INF/MANIFEST.MF" outputs for you.
Also, check what "mvn help:effective-pom" produces on your project vs.
my project.
Hope this helps to diagnose the issue.
Best wishes,
Andreas
[1]
signature.asc
Description: OpenPGP digital signature
Re: Accessing licenses/license as POM properties?
On 2018-05-18T16:50:56 +0100
org.apache.maven.u...@io7m.com wrote:
> On 2018-05-18T17:01:52 +0200
> Andreas Sewe wrote:
>
> > here's what I use as an for the maven-bundle-plugin to
> > generate a Bundle-License line in my MANIFEST.MF:
> >
> > > ${project.licenses[0].url};description="${project.licenses[0].name}"
> > >
> >
> > Works like a charm, as long as you have exactly one license.
>
> Looks good, thanks!
>
> You're also using it for the exact same reason I'd be using it. :)
Spoke a bit too soon. I'm using the bnd-maven-plugin, but I don't think
that changes anything. I have:
biz.aQute.bnd
bnd-maven-plugin
${io7m.bnd-maven-plugin.version}
Unfortunately, the resulting bundle manifest is:
Bundle-Description Contract checking
Bundle-License ${project.licenses[0].name}
It seems that the array reference isn't being expanded. If I specify
${project.licenses}, I instead get:
Bundle-License [org.apache.maven.model.License@3eba57a7]
... which is clearly the result of calling toString() on something
that hasn't overridden it. Point is that the project.licenses property
is definitely present, it's just that I'm unable to access any of the
elements.
--
Mark Raynsford | http://www.io7m.com
pgp8naM0lCYGF.pgp
Description: OpenPGP digital signature
Re: Accessing licenses/license as POM properties?
On 2018-05-18T17:01:52 +0200
Andreas Sewe wrote:
> Hi,
>
> > Is there a way to access the contents of the element as POM
> > properties? I'd like to reference the URL of the first license element
> > in a plugin execution, but there doesn't appear to be a
> > ${pom.license.url} or anything similar.
>
> here's what I use as an for the maven-bundle-plugin to
> generate a Bundle-License line in my MANIFEST.MF:
>
> > ${project.licenses[0].url};description="${project.licenses[0].name}"
> >
>
> Works like a charm, as long as you have exactly one license.
Looks good, thanks!
You're also using it for the exact same reason I'd be using it. :)
--
Mark Raynsford | http://www.io7m.com
pgp4j6uhckNwT.pgp
Description: OpenPGP digital signature
Re: Accessing licenses/license as POM properties?
Hi,
> Is there a way to access the contents of the element as POM
> properties? I'd like to reference the URL of the first license element
> in a plugin execution, but there doesn't appear to be a
> ${pom.license.url} or anything similar.
here's what I use as an for the maven-bundle-plugin to
generate a Bundle-License line in my MANIFEST.MF:
> ${project.licenses[0].url};description="${project.licenses[0].name}"
Works like a charm, as long as you have exactly one license.
Hope this helps.
Andreas
signature.asc
Description: OpenPGP digital signature
Accessing licenses/license as POM properties?
Hello.
Is there a way to access the contents of the element as POM
properties? I'd like to reference the URL of the first license element
in a plugin execution, but there doesn't appear to be a
${pom.license.url} or anything similar.
--
Mark Raynsford | http://www.io7m.com
pgppgAgtlZLqn.pgp
Description: OpenPGP digital signature
Re: Setting pom properties from Maven Plugin for resource filtering
Hi Ronen, take a look at the Properties Maven Plugin [1]. I don't have any experience with that plugin, because I haven't used it yet. But it looks like it should do exactly what You want to achieve with Your custom Maven plugin. However, if it doesn't work out for You, You could at least take a look at the source code to see how it adds the properties to the project model. The Build Helper Maven Plugin [2] also sets some properties, You could check its sources, too. One more point: I assume You checked that Your configuration of the Resources plugin works properly ... Kind regards Marc [1] http://mojo.codehaus.org/properties-maven-plugin [2] http://mojo.codehaus.org/build-helper-maven-plugin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Setting pom properties from Maven Plugin for resource filtering
I have a conf file in a java app that contains an IP address parameter. I
want to be able to put in this parameter the local ip address automatically
at build time. I used maven resources-plugin as follows:
org.apache.maven.plugins
maven-resources-plugin
2.5
copy-resources
validate
copy-resources
/home/user/config
config
true
**/*.xml
**/*.properties
Next, I've created a property that contains the parameter
${local.ip}
Then, I've created a Maven plugin that gets the local ip address and sets
the above parameter:
final Properties props = mavenProject.getProperties();
props.put("local.ip", resultAddress.getHostAddress());
lastly, I define my custom plugin in the pom.xml:
com.applango
get-local-ip-plugin
0.0.1-SNAPSHOT
get-local-ip
validate
get-local-ip
${local.ip}
The problem is that this doesn't work and I get ${local.ip} in the resulting
file instead of xxx.xxx.xxx.xxx ip address.
Any suggestions?
Re: Super pom properties in child pom
On Fri, 05 Jun 2009 14:12:50 -0500, dkowis wrote:
> Say I've got a super pom with a defined SCM section like so:
>
> scm:git:git://server/repos/${artifactId}.git
>
>
> Well in the child pom, it's taking the super pom's name and appending /
> child pom's name.
> Like so:
>
> scm:git:git://server/repos/Super/Child.git
>
>
> That's not what I wanted it to do, I need it to just have Child.git
without
> the super/ stuff
> How do I ensure that happens?
>
Actually it's still stranger than that:
I have a configured url in the scm section
http://server/gitweb/gitweb.cgi/repos/${artifactId}
This should show up in the generated site (when running mvn site) as:
http://server/gitweb/gitweb.cgi/repos/Child
But it's showing up as:
http://server/gitweb/gitweb.cgi/repos/Child/Super/Child
What is going on? I didn't specify anything else after the URL, why is
appending things for me?
Thanks,
David
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Super pom properties in child pom
Say I've got a super pom with a defined SCM section like so:
scm:git:git://server/repos/${artifactId}.git
Well in the child pom, it's taking the super pom's name and appending /
child pom's name.
Like so:
scm:git:git://server/repos/Super/Child.git
That's not what I wanted it to do, I need it to just have Child.git without
the super/ stuff
How do I ensure that happens?
Thanks,
David
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Read pom properties from a custom location
> I'd like to read POM properties from a custom file if it exists.
> ie: i'd like to read from pom.properties and pom-${user.name}.properties
>
> I can't see any examples on the web of how to do this.
Maven is not Ant. Properties in Maven belong in the pom.xml file.
There are no examples of this because it is not supported. There is a
plugin (properties-maven-plugin, I think it is called) that may
support some of this functionality.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Read pom properties from a custom location
I'd like to read POM properties from a custom file if it exists.
ie: i'd like to read from pom.properties and pom-${user.name}.properties
I can't see any examples on the web of how to do this.
Cheers,
Lance.
Re: pom properties
${one} in that case, ${project.*} should be used to access the actual
elements of the project.
- Brett
On 26/11/2008, at 2:49 AM, Randy Kamradt wrote:
There has been some confusion in the past about accessing pom
properties
using the ${} notation. I know that to access the project version you
should use ${project.version}. But for pom defined properties is the
project prefix required? for instance, in a pom.xml:
1
${project.one}
or
${one}
either seems to work, but is there a preferred method?
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: pom properties
I've noticed OS dependent effects in the expansion of such properties (I
often saw also 'pom.*' notation used) .
The one which IMHO seems to always work is though:
${project.*}
HTH,
Gab
2008/11/25 Randy Kamradt <[EMAIL PROTECTED]>
> There has been some confusion in the past about accessing pom properties
> using the ${} notation. I know that to access the project version you
> should use ${project.version}. But for pom defined properties is the
> project prefix required? for instance, in a pom.xml:
>
>
>1
>
>
>${project.one}
>or
>${one}
>
> either seems to work, but is there a preferred method?
>
--
Gabriele Columbro
Alfresco ECM Product Strategy Consultant
+31 627 565 103
Sourcesense - Making sense of open Source
pom properties
There has been some confusion in the past about accessing pom properties
using the ${} notation. I know that to access the project version you
should use ${project.version}. But for pom defined properties is the
project prefix required? for instance, in a pom.xml:
1
${project.one}
or
${one}
either seems to work, but is there a preferred method?
Re: Using POM properties in XDoc
Hi Dennis,
Thank you for your suggestion,I read the page you linked many times
but I've always missed the right section!
Thank you again,best regards
Simone
Sent from my iPhone
On Sep 22, 2008, at 7:57 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
There is built in filtering in the site-plugin starting with version
2.0-beta-6. See the "Filtering" section at
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
I haven't tried it for xdoc files myself.
Simone Tripodi wrote:
Hi everybody,
using the site plugin, I would like to know if is allowed using pom's
properties in xdoc documents - I tried with ${pom.version},
unfortunatly without any good result, the text won't change.
Do you have any suggestion? Thanks in advance!
Best regards,
Simone
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using POM properties in XDoc
There is built in filtering in the site-plugin starting with version
2.0-beta-6. See the "Filtering" section at
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
I haven't tried it for xdoc files myself.
Simone Tripodi wrote:
> Hi everybody,
> using the site plugin, I would like to know if is allowed using pom's
> properties in xdoc documents - I tried with ${pom.version},
> unfortunatly without any good result, the text won't change.
> Do you have any suggestion? Thanks in advance!
> Best regards,
> Simone
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using POM properties in XDoc
I'll try it, thank you very much :)
2008/9/22 Stephen Connolly <[EMAIL PROTECTED]>:
> You might have to hack filtering with the resource plugin
>
> On 22 September 2008 09:22, Simone Tripodi <[EMAIL PROTECTED]> wrote:
>
>> Hi everybody,
>> using the site plugin, I would like to know if is allowed using pom's
>> properties in xdoc documents - I tried with ${pom.version},
>> unfortunatly without any good result, the text won't change.
>> Do you have any suggestion? Thanks in advance!
>> Best regards,
>> Simone
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
--
My LinkedIn profile: http://www.linkedin.com/in/simonetripodi
My GoogleCode profile: http://code.google.com/u/simone.tripodi/
My Picasa: http://picasaweb.google.com/simone.tripodi/
My Tube: http://www.youtube.com/user/stripodi
My Del.icio.us: http://del.icio.us/simone.tripodi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using POM properties in XDoc
You might have to hack filtering with the resource plugin
On 22 September 2008 09:22, Simone Tripodi <[EMAIL PROTECTED]> wrote:
> Hi everybody,
> using the site plugin, I would like to know if is allowed using pom's
> properties in xdoc documents - I tried with ${pom.version},
> unfortunatly without any good result, the text won't change.
> Do you have any suggestion? Thanks in advance!
> Best regards,
> Simone
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Using POM properties in XDoc
Hi everybody,
using the site plugin, I would like to know if is allowed using pom's
properties in xdoc documents - I tried with ${pom.version},
unfortunatly without any good result, the text won't change.
Do you have any suggestion? Thanks in advance!
Best regards,
Simone
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM properties not inherited
Never mind, i figured out what the problem was. dmcgeown wrote: > > Hi, i've come across a problem which i driving me mad. My project is made > up of multiple modules which all inherit from a super pom. In this super > pom i have defined a few properties for version number of the individual > modules. When i run mvn install from the root dir (super pom) it goes thru > all of the modules perfectly and build with the correct version numbers. > If I run the mvn install command from one of the nested modules it can't > find the version properties defined in the super pom. > > Is there a workaround for this problem? Is it possible to store you > properties in a properties file and load them within the pom? If i could > do that i could just refernce the properties file via a relative path in > each pom. > > Thanks in advance. > > Darragh > -- View this message in context: http://www.nabble.com/Parent-POM-properties-not-inherited-tp19529658p19530925.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Parent POM properties not inherited
Hi, i've come across a problem which i driving me mad. My project is made up of multiple modules which all inherit from a super pom. In this super pom i have defined a few properties for version number of the individual modules. When i run mvn install from the root dir (super pom) it goes thru all of the modules perfectly and build with the correct version numbers. If I run the mvn install command from one of the nested modules it can't find the version properties defined in the super pom. Is there a workaround for this problem? Is it possible to store you properties in a properties file and load them within the pom? If i could do that i could just refernce the properties file via a relative path in each pom. Thanks in advance. Darragh -- View this message in context: http://www.nabble.com/Parent-POM-properties-not-inherited-tp19529658p19529658.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to override POM properties from CLI
Paul Gier wrote: > > This seems to work ok for me. I tried it locally and my profile > properties > override my pom properties, and cli props defined with -D override both > pom and > profile properties. I tried with maven 2.0.6 and 2.0.8. > Can you attach a small zipped project to a jira issue that reproduces the > problem? > http://jira.codehaus.org/browse/MNG-3417 -- View this message in context: http://www.nabble.com/How-to-override-POM-properties-from-CLI-tp15344487s177p15633399.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to override POM properties from CLI
This seems to work ok for me. I tried it locally and my profile properties override my pom properties, and cli props defined with -D override both pom and profile properties. I tried with maven 2.0.6 and 2.0.8. Can you attach a small zipped project to a jira issue that reproduces the problem? Igor Romanov wrote: Thank you for reply. Are you saying that properties specified in POM can not be overridden with -D option? Igor Wayne Fay wrote: You should put the properties in different profiles, and then specify which profile using -Penv1 when running Maven. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to override POM properties from CLI
I already noticed this problem and I think it is a bug. I don't know if an issue is open. Arnaud On Thu, Feb 21, 2008 at 7:43 AM, avalon <[EMAIL PROTECTED]> wrote: > > That's ugly! > > If one can't override properties then for example testing against > different > databases from an automated build system is a real pain. So first one > needs > to create profiles for all supported databases to be able to retrieve the > jdbc driver. Then how many additional profiles for all combinations one > needs? And then for developers' local runs? > > Please, anybody aware how to override pom properties? > > > Wayne Fay wrote: > > > > You should put the properties in different profiles, and then specify > > which profile using -Penv1 when running Maven. > > > > Wayne > > > > -- > View this message in context: > http://www.nabble.com/How-to-override-POM-properties-from-CLI-tp15344487s177p15605671.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: How to override POM properties from CLI
That's ugly! If one can't override properties then for example testing against different databases from an automated build system is a real pain. So first one needs to create profiles for all supported databases to be able to retrieve the jdbc driver. Then how many additional profiles for all combinations one needs? And then for developers' local runs? Please, anybody aware how to override pom properties? Wayne Fay wrote: > > You should put the properties in different profiles, and then specify > which profile using -Penv1 when running Maven. > > Wayne > -- View this message in context: http://www.nabble.com/How-to-override-POM-properties-from-CLI-tp15344487s177p15605671.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to override POM properties from CLI
Thank you for reply. Are you saying that properties specified in POM can not be overridden with -D option? Igor Wayne Fay wrote: > > You should put the properties in different profiles, and then specify > which profile using -Penv1 when running Maven. > > Wayne > -- View this message in context: http://www.nabble.com/How-to-override-POM-properties-from-CLI-tp15344487s177p15347745.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to override POM properties from CLI
You should put the properties in different profiles, and then specify
which profile using -Penv1 when running Maven.
Wayne
On 2/7/08, Igor Romanov <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have properties in a POM file I need to be able to override with
> command line –D option,
> to run build in a different environments. How can I do this? Simple
> example below doesn't work
> as I expect it should, i.e. test.txt will contain FALSE after running
>
> c:\temp\module> mvn -Dtest.result=PASS process-test-resources
>
> What am I doing in a wrong way?
>
> Sample project:
> --
>
> module/pom.xml
>
>
>
> 4.0.0
> com.test
> test
> 1.0
> jar
>
>
> FAIL
>
>
>
>
>
>${basedir}/src/test/resources
>true
>
>*.txt
>
>
>
>
>
>
> module/src/test/resources/test.txt
>
> This test ${test.result}
>
> --
> Igor.
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How to override POM properties from CLI
Hello,
I have properties in a POM file I need to be able to override with
command line –D option,
to run build in a different environments. How can I do this? Simple
example below doesn't work
as I expect it should, i.e. test.txt will contain FALSE after running
c:\temp\module> mvn -Dtest.result=PASS process-test-resources
What am I doing in a wrong way?
Sample project:
--
module/pom.xml
4.0.0
com.test
test
1.0
jar
FAIL
${basedir}/src/test/resources
true
*.txt
module/src/test/resources/test.txt
This test ${test.result}
--
Igor.
Re: Problem by injecting POM Properties via Settings.xml
Hi,
The profile in your settings need to be active.
Try with :
>
>
normal
true
>
> 3.8.1
>
>
>
Use mvn help:effective-pom to see the pom interpolated.
--
Olivier
2008/1/2, Thomas Chang <[EMAIL PROTECTED]>:
> Hi all,
>
> According to the link
> http://maven.apache.org/examples/injecting-properties-via-settings.html I do
> in my "pom.xml" and "settings.xml" followings:
>
> in the "pom.xml":
> =
> ...
>
> junit
> junit
> ${myversion}
>
> ...
>
> in the "settings.xml":
> ===
> ...
>
>
>
> 3.8.1
>
>
>
> ...
>
> But a sI run "mvn eclipse:eclipse" I get error as follow. Somebody can help?
> ...
> Downloading:
> file:sap-dev/CVSREPO/CvsMaven/junit/junit/${myversion}/junit-${
> myversion}.jar
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> Missing:
> --
> 1) junit:junit:jar:${myversion}
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=junit -DartifactId=junit \
> -Dversion=${myversion} -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit \
> -Dversion=${myversion} -Dpackaging=jar -Dfile=/path/to/file \
>-Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.wei.chen.app:TestXml:jar:1.0-SNAPSHOT
> 2) junit:junit:jar:${myversion}
> --
> 1 required artifact is missing.
> for artifact:
> com.wei.chen.app:TestXml:jar:1.0-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 1 second
> [INFO] Finished at: Wed Jan 02 14:18:48 CET 2008
> [INFO] Final Memory: 2M/5M
> [INFO]
>
> E:\Projekte\TestXml>
> ...
>
>
>
> -
> Ihr erstes Fernweh? Wo gibt es den schönsten Strand.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem by injecting POM Properties via Settings.xml
Hi all,
According to the link
http://maven.apache.org/examples/injecting-properties-via-settings.html I do in
my "pom.xml" and "settings.xml" followings:
in the "pom.xml":
=
...
junit
junit
${myversion}
...
in the "settings.xml":
===
...
3.8.1
...
But a sI run "mvn eclipse:eclipse" I get error as follow. Somebody can help?
...
Downloading:
file:sap-dev/CVSREPO/CvsMaven/junit/junit/${myversion}/junit-${
myversion}.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) junit:junit:jar:${myversion}
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=junit -DartifactId=junit \
-Dversion=${myversion} -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit \
-Dversion=${myversion} -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) com.wei.chen.app:TestXml:jar:1.0-SNAPSHOT
2) junit:junit:jar:${myversion}
--
1 required artifact is missing.
for artifact:
com.wei.chen.app:TestXml:jar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Wed Jan 02 14:18:48 CET 2008
[INFO] Final Memory: 2M/5M
[INFO]
E:\Projekte\TestXml>
...
-
Ihr erstes Fernweh? Wo gibt es den schönsten Strand.
Re: Interpolation of Pom Properties in Assembly Descriptor
I'll assume this is a regression in the latest 2.2-beta-2-SNAPSHOT.
http://jira.codehaus.org/browse/MASSEMBLY-256
On Nov 28, 2007 12:45 PM, Mark Reynolds <[EMAIL PROTECTED]>
wrote:
> That wasn't it, but thanks.
>
>
> On Nov 27, 2007 12:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> > I've seen that mentioned on this list a couple times, and I generally
> > use this notation myself as well for no particular reason.
> >
> > Wayne
> >
> > On 11/27/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> > > Some time back I encountered a problem with properties in the pom
> > using
> > > a dot-notation. I solved that by using camelHump-notation instead. In
> > > your case that would mean replacing "my.path" with "myPath". Not sure
> > if
> > > it will work in this case, but it's worth a try.
> > >
> > > Mark Reynolds wrote:
> > > > I was using maven-assembly-plugin 2.2-SNAPSHOT and tried to switch
> > to
> > > > 2.2-beta-2-SNAPSHOT but encountered a problem.
> > > >
> > > > I reference properties from my pom in the assembly descriptor, like
> > this:
> > > >
> > > >
> > > > ...
> > > >
> > > > myapp/WEB-INF
> > > >
> > > > ..
> > > >
> > > >
> > > >
> > > >
> > > > ...
> > > >
> > > >
> > > > ${basedir}/target/config/somefile.conf
> > > > ${ my.path}/etc
> > > >
> > > >
> > > > ...
> > > >
> > > >
> > > > In 2.2-SNAPSHOT, the value was substituted but in
> > 2.2-beta-2-SNAPSHOT the
> > > > literal ${my.path} is used. Is this a regression, a removed feature,
> > or has
> > > > the syntax for doing this changed?
> > > >
> > > > -- Mark R
> > > >
> > >
> > >
> > > --
> > > Dennis Lundberg
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
Re: Interpolation of Pom Properties in Assembly Descriptor
That wasn't it, but thanks.
On Nov 27, 2007 12:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I've seen that mentioned on this list a couple times, and I generally
> use this notation myself as well for no particular reason.
>
> Wayne
>
> On 11/27/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> > Some time back I encountered a problem with properties in the pom using
> > a dot-notation. I solved that by using camelHump-notation instead. In
> > your case that would mean replacing "my.path" with "myPath". Not sure if
> > it will work in this case, but it's worth a try.
> >
> > Mark Reynolds wrote:
> > > I was using maven-assembly-plugin 2.2-SNAPSHOT and tried to switch to
> > > 2.2-beta-2-SNAPSHOT but encountered a problem.
> > >
> > > I reference properties from my pom in the assembly descriptor, like
> this:
> > >
> > >
> > > ...
> > >
> > > myapp/WEB-INF
> > >
> > > ..
> > >
> > >
> > >
> > >
> > > ...
> > >
> > >
> > > ${basedir}/target/config/somefile.conf
> > > ${my.path}/etc
> > >
> > >
> > > ...
> > >
> > >
> > > In 2.2-SNAPSHOT, the value was substituted but in 2.2-beta-2-SNAPSHOTthe
> > > literal ${my.path} is used. Is this a regression, a removed feature,
> or has
> > > the syntax for doing this changed?
> > >
> > > -- Mark R
> > >
> >
> >
> > --
> > Dennis Lundberg
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: Interpolation of Pom Properties in Assembly Descriptor
I've seen that mentioned on this list a couple times, and I generally
use this notation myself as well for no particular reason.
Wayne
On 11/27/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Some time back I encountered a problem with properties in the pom using
> a dot-notation. I solved that by using camelHump-notation instead. In
> your case that would mean replacing "my.path" with "myPath". Not sure if
> it will work in this case, but it's worth a try.
>
> Mark Reynolds wrote:
> > I was using maven-assembly-plugin 2.2-SNAPSHOT and tried to switch to
> > 2.2-beta-2-SNAPSHOT but encountered a problem.
> >
> > I reference properties from my pom in the assembly descriptor, like this:
> >
> >
> > ...
> >
> > myapp/WEB-INF
> >
> > ..
> >
> >
> >
> >
> > ...
> >
> >
> > ${basedir}/target/config/somefile.conf
> > ${my.path}/etc
> >
> >
> > ...
> >
> >
> > In 2.2-SNAPSHOT, the value was substituted but in 2.2-beta-2-SNAPSHOT the
> > literal ${my.path} is used. Is this a regression, a removed feature, or has
> > the syntax for doing this changed?
> >
> > -- Mark R
> >
>
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Interpolation of Pom Properties in Assembly Descriptor
Some time back I encountered a problem with properties in the pom using
a dot-notation. I solved that by using camelHump-notation instead. In
your case that would mean replacing "my.path" with "myPath". Not sure if
it will work in this case, but it's worth a try.
Mark Reynolds wrote:
I was using maven-assembly-plugin 2.2-SNAPSHOT and tried to switch to
2.2-beta-2-SNAPSHOT but encountered a problem.
I reference properties from my pom in the assembly descriptor, like this:
...
myapp/WEB-INF
..
...
${basedir}/target/config/somefile.conf
${my.path}/etc
...
In 2.2-SNAPSHOT, the value was substituted but in 2.2-beta-2-SNAPSHOT the
literal ${my.path} is used. Is this a regression, a removed feature, or has
the syntax for doing this changed?
-- Mark R
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Interpolation of Pom Properties in Assembly Descriptor
I was using maven-assembly-plugin 2.2-SNAPSHOT and tried to switch to
2.2-beta-2-SNAPSHOT but encountered a problem.
I reference properties from my pom in the assembly descriptor, like this:
...
myapp/WEB-INF
..
...
${basedir}/target/config/somefile.conf
${my.path}/etc
...
In 2.2-SNAPSHOT, the value was substituted but in 2.2-beta-2-SNAPSHOT the
literal ${my.path} is used. Is this a regression, a removed feature, or has
the syntax for doing this changed?
-- Mark R
Re: ant tasks and pom properties
I opened a Jira issue about this: http://jira.codehaus.org/browse/MANTTASKS-101 and made the enhancement This will work in Maven Ant Tasks 2.0.8. Hervé Le mardi 20 novembre 2007, Hervé BOUTEMY a écrit : > Le lundi 19 novembre 2007, Kevin Stembridge a écrit : > > Hi all, > > Is it possible for the ant tasks to read in arbitrary pom.xml > > properties? > > > > I'm not having any trouble getting at the normal properties that are > > part of the POM schema (project.version, project.build.directory etc) > > but I can't read in any properties that I define in a tag. > > > > Is this supposed to be possible? > > no > > :) > > Hervé > > > Thanks for any help. > > Kevin > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ant tasks and pom properties
Le lundi 19 novembre 2007, Kevin Stembridge a écrit : > Hi all, > Is it possible for the ant tasks to read in arbitrary pom.xml > properties? > > I'm not having any trouble getting at the normal properties that are > part of the POM schema (project.version, project.build.directory etc) > but I can't read in any properties that I define in a tag. > > Is this supposed to be possible? no :) Hervé > > Thanks for any help. > Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ant tasks and pom properties
Hi all, Is it possible for the ant tasks to read in arbitrary pom.xml properties? I'm not having any trouble getting at the normal properties that are part of the POM schema (project.version, project.build.directory etc) but I can't read in any properties that I define in a tag. Is this supposed to be possible? Thanks for any help. Kevin
Using POM properties into the filters
Is there any way to use the propeties defined in the POM (or even the settings.xml) in the files that will be used as filters? Thanks. -- View this message in context: http://www.nabble.com/Using-POM-properties-into-the-filters-tf4569192s177.html#a13041084 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Accessing POM properties in a filter
Ah, but the filters file *is* filtered.
At least for Java System properties and for other filter tokens, and
(because of the order that the filtering mechanism is implemented) also
for values of simple POM elements (but not POM properties as they are
complex).
In order to allow replacement of POM porperties to filter files in the
same way as the others are replaced I have rasied the following JIRA and
supplied a patch.
http://jira.codehaus.org/browse/MRESOURCES-47
Its true, I could insert the POM properties directly into the resource
files. But many of the tokens are compounded from one or more POM
properties to produce understandable tokens instead of fragments.
So it would either require many more properties to be added to each
profile in my POM with much duplication between each profile, or it
would require the use of many non-intuitive tokens fragments in the
resource files.
William
-Original Message-
From: Tim Kettler [mailto:[EMAIL PROTECTED]
Sent: Friday, 24 August 2007 3:17 PM
To: Maven Users List
Subject: [***POSSIBLE SPAM***] - Re: [***POSSIBLE SPAM***] - Re:
Accessing POM properties in a filter - Email has different SMTP TO: and
MIME TO: fields in the email addresses - Email has different SMTP TO:
and MIME TO: fields in the email addresses
Hi,
The probem is that for this to work the filters file would need to be
filtered too, which is not the case. Use your declared properties
directly in the resource files you want filtered and don't do the extra
indirection via the filters file.
-Tim
William Ferguson schrieb:
> ${myProp1} doesn't work either.
>
>
> With a POM declaring
> Somevalue
>
> A filter.file of
> some.token=${myProp1}
>
> And a resource file with
> Show.me.the.value.of.some.token=${some.token}
>
>
> The resource file resolves to :
> Show.me.the.value.of.some.token=${myProp1}
>
> Instead of
> Show.me.the.value.of.some.token=SomeValue
>
>
> William
>
>
> -Original Message-
> From: Eric Redmond [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 August 2007 12:36 PM
> To: Maven Users List
> Subject: [***POSSIBLE SPAM***] - Re: Accessing POM properties in a
> filter - Email has different SMTP TO: and MIME TO: fields in the email
> addresses
>
> Why can't you just use ${myProp1} ? Why go through the trouble of
> refering via "project.properties"?
>
> --
> Eric Redmond
> http://blog.propellors.net
>
> On 8/23/07, William Ferguson <[EMAIL PROTECTED]> wrote:
>> In a resource filter, I can specify tokens like:
>>
>> token1=${project.version}
>> token2=${project.properties}
>>
>> Which when used in a resource file evaluates to:
>>
>> valueForToken1=1.0-SNAPSHOT
>> valueForToken2={myProp1=value1, myProp2=value2}
>>
>> How do I specify a token in the resource filter that resolves to the
>> value of myProp1?
>> I've tried all variants (that I can think of) of
>> ${project.properties.myProp1}.
>>
>> I'm sure there's a way, but I can't find documentation spelling out
>> the syntax that is required.
>>
>>
>> William
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Accessing POM properties in a filter
Resending as its been 24 hours and the message hasn't shown up.
In a resource filter, I can specify tokens like:
token1=${project.version}
token2=${project.properties}
Which when used in a resource file evaluates to:
valueForToken1=1.0-SNAPSHOT
valueForToken2={myProp1=value1, myProp2=value2}
How do I specify a token in the resource filter that resolves to the
value of myProp1?
I've tried all variants (that I can think of) of
${project.properties.myProp1}.
I'm sure there's a way, but I can't find documentation spelling out the
syntax that is required.
William
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [***POSSIBLE SPAM***] - Re: Accessing POM properties in a filter - Email has different SMTP TO: and MIME TO: fields in the email addresses
Hi,
The probem is that for this to work the filters file would need to be
filtered too, which is not the case. Use your declared properties
directly in the resource files you want filtered and don't do the extra
indirection via the filters file.
-Tim
William Ferguson schrieb:
${myProp1} doesn't work either.
With a POM declaring
Somevalue
A filter.file of
some.token=${myProp1}
And a resource file with
Show.me.the.value.of.some.token=${some.token}
The resource file resolves to :
Show.me.the.value.of.some.token=${myProp1}
Instead of
Show.me.the.value.of.some.token=SomeValue
William
-Original Message-
From: Eric Redmond [mailto:[EMAIL PROTECTED]
Sent: Friday, 24 August 2007 12:36 PM
To: Maven Users List
Subject: [***POSSIBLE SPAM***] - Re: Accessing POM properties in a
filter - Email has different SMTP TO: and MIME TO: fields in the email
addresses
Why can't you just use ${myProp1} ? Why go through the trouble of
refering via "project.properties"?
--
Eric Redmond
http://blog.propellors.net
On 8/23/07, William Ferguson <[EMAIL PROTECTED]> wrote:
In a resource filter, I can specify tokens like:
token1=${project.version}
token2=${project.properties}
Which when used in a resource file evaluates to:
valueForToken1=1.0-SNAPSHOT
valueForToken2={myProp1=value1, myProp2=value2}
How do I specify a token in the resource filter that resolves to the
value of myProp1?
I've tried all variants (that I can think of) of
${project.properties.myProp1}.
I'm sure there's a way, but I can't find documentation spelling out
the syntax that is required.
William
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [***POSSIBLE SPAM***] - Re: Accessing POM properties in a filter - Email has different SMTP TO: and MIME TO: fields in the email addresses
${myProp1} doesn't work either.
With a POM declaring
Somevalue
A filter.file of
some.token=${myProp1}
And a resource file with
Show.me.the.value.of.some.token=${some.token}
The resource file resolves to :
Show.me.the.value.of.some.token=${myProp1}
Instead of
Show.me.the.value.of.some.token=SomeValue
William
-Original Message-
From: Eric Redmond [mailto:[EMAIL PROTECTED]
Sent: Friday, 24 August 2007 12:36 PM
To: Maven Users List
Subject: [***POSSIBLE SPAM***] - Re: Accessing POM properties in a
filter - Email has different SMTP TO: and MIME TO: fields in the email
addresses
Why can't you just use ${myProp1} ? Why go through the trouble of
refering via "project.properties"?
--
Eric Redmond
http://blog.propellors.net
On 8/23/07, William Ferguson <[EMAIL PROTECTED]> wrote:
>
> In a resource filter, I can specify tokens like:
>
> token1=${project.version}
> token2=${project.properties}
>
> Which when used in a resource file evaluates to:
>
> valueForToken1=1.0-SNAPSHOT
> valueForToken2={myProp1=value1, myProp2=value2}
>
> How do I specify a token in the resource filter that resolves to the
> value of myProp1?
> I've tried all variants (that I can think of) of
> ${project.properties.myProp1}.
>
> I'm sure there's a way, but I can't find documentation spelling out
> the syntax that is required.
>
>
> William
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Accessing POM properties in a filter
Why can't you just use ${myProp1} ? Why go through the trouble of refering
via "project.properties"?
--
Eric Redmond
http://blog.propellors.net
On 8/23/07, William Ferguson <[EMAIL PROTECTED]> wrote:
>
> In a resource filter, I can specify tokens like:
>
> token1=${project.version}
> token2=${project.properties}
>
> Which when used in a resource file evaluates to:
>
> valueForToken1=1.0-SNAPSHOT
> valueForToken2={myProp1=value1, myProp2=value2}
>
> How do I specify a token in the resource filter that resolves to the
> value of myProp1?
> I've tried all variants (that I can think of) of
> ${project.properties.myProp1}.
>
> I'm sure there's a way, but I can't find documentation spelling out the
> syntax that is required.
>
>
> William
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
RE: Accessing POM properties in a filter
OK, well after a bit of investigation I found that the
maven-resources-plugin only resolves System properties and simple POM
elements, but not POM properties within the Filter before applying them.
So I have created a patch that resolves POM properties within filter
files too.
http://jira.codehaus.org/browse/MRESOURCES-47
If this is affecting you and I recall hearing that some of the Axis2
guys were affected by something that I suspect was this, then please
vote for it.
William
-Original Message-
From: William Ferguson [mailto:[EMAIL PROTECTED]
Sent: Thursday, 23 August 2007 5:10 PM
To: Maven Users List
Subject: Accessing POM properties in a filter
In a resource filter, I can specify tokens like:
token1=${project.version}
token2=${project.properties}
Which when used in a resource file evaluates to:
valueForToken1=1.0-SNAPSHOT
valueForToken2={myProp1=value1, myProp2=value2}
How do I specify a token in the resource filter that resolves to the
value of myProp1?
I've tried all variants (that I can think of) of
${project.properties.myProp1}.
I'm sure there's a way, but I can't find documentation spelling out the
syntax that is required.
William
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Accessing POM properties in a filter
In a resource filter, I can specify tokens like:
token1=${project.version}
token2=${project.properties}
Which when used in a resource file evaluates to:
valueForToken1=1.0-SNAPSHOT
valueForToken2={myProp1=value1, myProp2=value2}
How do I specify a token in the resource filter that resolves to the
value of myProp1?
I've tried all variants (that I can think of) of
${project.properties.myProp1}.
I'm sure there's a way, but I can't find documentation spelling out the
syntax that is required.
William
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM, properties and scm problem
Might I suggest for the time being, to download and install the
maven-pom-plugin (
http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-pom-plugin/)
and manually manage the scm fields in the projects. I know it's a hack, but
non-standard layouts tend to produce non-standard solutions. Welcome to
convention over configuration :)
--
Eric Redmond
http://blog.propellors.net
On 8/6/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
>
> Oscar Picasso wrote on Wednesday, August 01, 2007 7:31 PM:
>
> > The current Maven behaviour is fine for multimodule projects.
> >
> > However I am trying to write a organizational POM that all my projets
> > would inherited and wanted to avoid duplication of the scm section.
> >
> > So in case of independent projects it does not make sense to put all
> > them inside the same trunk.
> >
> > I guess currently I cannot avoid this duplication.
>
> Not really, and there's a simple reason: You cannot assume that everyone
> keeps his "organizational POM" in the root of all the projects. Our
> "organizational POM" has SCM URL entries that are used to release the
> "organizational POM" itself. It does not even make sense to inherit them.
>
> However, you may use properties to define the SCM URLs as we do:
>
>
> scm|svn|${my.svn.root}${my.svn.tagBase}/trunk
> scm|svn|${my.svn.root}${my.svn.tagBase
> }/trunk
> ${my.svn.view}${my.svn.tagBase}/trunk
>
>
> while "my.svn.root" and "my.svn.view" are properties that are defined in
> the "organizational POM" and "my.svn.tagBase" is defined in the POM of the
> project root (in case of a multi-module project). But keep in mind, that the
> release-plugin will rewrite the URLs after the first release, so there are
> no properties in the URL anymore anyway. So the whole definition is only
> useful as template for new POMs.
>
> - Jörg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
RE: Parent POM, properties and scm problem
Oscar Picasso wrote on Wednesday, August 01, 2007 7:31 PM:
> The current Maven behaviour is fine for multimodule projects.
>
> However I am trying to write a organizational POM that all my projets
> would inherited and wanted to avoid duplication of the scm section.
>
> So in case of independent projects it does not make sense to put all
> them inside the same trunk.
>
> I guess currently I cannot avoid this duplication.
Not really, and there's a simple reason: You cannot assume that everyone keeps
his "organizational POM" in the root of all the projects. Our "organizational
POM" has SCM URL entries that are used to release the "organizational POM"
itself. It does not even make sense to inherit them.
However, you may use properties to define the SCM URLs as we do:
scm|svn|${my.svn.root}${my.svn.tagBase}/trunk
scm|svn|${my.svn.root}${my.svn.tagBase}/trunk
${my.svn.view}${my.svn.tagBase}/trunk
while "my.svn.root" and "my.svn.view" are properties that are defined in the
"organizational POM" and "my.svn.tagBase" is defined in the POM of the project
root (in case of a multi-module project). But keep in mind, that the
release-plugin will rewrite the URLs after the first release, so there are no
properties in the URL anymore anyway. So the whole definition is only useful as
template for new POMs.
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM, properties and scm problem
I'm also experiencing this problem. As discussed here (under Inheritance v.
Aggregation):
http://www.propellors.net/maven/site/pom.html#POM%20Relationships
it appears to make sense in what is called the "aggregation" use case, but
not in the "inheritance" use case. I'm wondering if there's some way to
simply disable this functionality (maybe setting a property? don't know...)
to get these url elements to inherit as one would expect - "as is".
If this functionality isn't currently available, and somebody could point me
to the appropriate code, I would be happy to try and write a patch for it...
Thanks,
Jared
Oscar Picasso
> Thu, 02 Aug 2007 06:31:58 -0700
>
> That's exactly what I am doing.
>
> And it works fine except for the problem that I mention in this thread of
> the project artifactId being added to some urls like the scmConnection.
>
> On 8/1/07, Bryan Loofbourrow <[EMAIL PROTECTED]> wrote:
> >
> > I'm wondering if the following would work:
> >
> > - Make your organizational pom project. Don't define any entries
> > in
> > it.
> > - Have all of your projects depend on it as a parent
> > - Build and install your organizational pom to a central repository
> > accessible to all of your projects.
> >
> > I'm thinking that you can then independently build and deploy your
> > organizational pom by itself, and have your projects use it, from the
> > repository, as a parent for definition purposes, though not build
> > purposes.
> >
> > I'd be interested to know whether this works. It seems useful.
> >
> > -- Bryan
> >
> > -Original Message-
> > From: Oscar Picasso [EMAIL PROTECTED]
> > Sent: Wednesday, August 01, 2007 10:31 AM
> > To: Maven Users List
> > Subject: Re: Parent POM, properties and scm problem
> >
> > The current Maven behaviour is fine for multimodule projects.
> >
> > However I am trying to write a organizational POM that all my projets
> > would
> > inherited and wanted to avoid duplication of the scm section.
> >
> > So in case of independent projects it does not make sense to put all them
> > inside the same trunk.
> >
> > I guess currently I cannot avoid this duplication.
> >
> > On 7/31/07, Eric Redmond <[EMAIL PROTECTED]> wrote:
> > >
> > > Maven does this so that child module's scm can be defined once in the
> > > parent.
> > >
> > >
> > > scm:svn:https://url/project/trunk
> > >
> > >
> > >
> > > Child
> > >
> > > Then the Child module's scm url is automatically set as:
> > >
> > >
> > > scm:svn:https://url/project/trunk/Child
> > >
> > >
> > > Which is the convention for a multi-module project.
> > >
> > > If your "Child" project has to be seperate, with it's own trunk, etc. I
> > > would suggest (if svn) using svn:externals to access the child under the
> > > parent project. Since it ownly appends the name on a multi-module
> > project,
> > > I'm trying to figure out how you locally check out your project...
> > perhaps
> > > create a "trunks"-style setup in your version control would be best?
> > >
> > > Eric
> > >
> > > On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> > > >
> > > > I have also noticed the same behavior with the project url, the sit
> > url
> > > > and
> > > > the scm url even if in the effective the corresponding properties are
> > > > correct (without the artifactId appended).
> > > >
> > > > On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > In the parent POM I have the following:
> > > > > [...]
> > > > >
> > > > >
> > > > http://localhost/repos/repo/${groupId}/${artifactId}/trunk
> > > > <http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk>
> > > > > <http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ${scmConnection}
> > > > > ${scmConnection}
> > > > >
> > > > > [...]
> > > > >
> > > > > The child POM has nothing ex
Re: Parent POM, properties and scm problem
That's exactly what I am doing.
And it works fine except for the problem that I mention in this thread of
the project artifactId being added to some urls like the scmConnection.
On 8/1/07, Bryan Loofbourrow <[EMAIL PROTECTED]> wrote:
>
> I'm wondering if the following would work:
>
> - Make your organizational pom project. Don't define any entries
> in
> it.
> - Have all of your projects depend on it as a parent
> - Build and install your organizational pom to a central repository
> accessible to all of your projects.
>
> I'm thinking that you can then independently build and deploy your
> organizational pom by itself, and have your projects use it, from the
> repository, as a parent for definition purposes, though not build
> purposes.
>
> I'd be interested to know whether this works. It seems useful.
>
> -- Bryan
>
> -Original Message-
> From: Oscar Picasso [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 01, 2007 10:31 AM
> To: Maven Users List
> Subject: Re: Parent POM, properties and scm problem
>
> The current Maven behaviour is fine for multimodule projects.
>
> However I am trying to write a organizational POM that all my projets
> would
> inherited and wanted to avoid duplication of the scm section.
>
> So in case of independent projects it does not make sense to put all them
> inside the same trunk.
>
> I guess currently I cannot avoid this duplication.
>
> On 7/31/07, Eric Redmond <[EMAIL PROTECTED]> wrote:
> >
> > Maven does this so that child module's scm can be defined once in the
> > parent.
> >
> >
> > scm:svn:https://url/project/trunk
> >
> >
> >
> > Child
> >
> > Then the Child module's scm url is automatically set as:
> >
> >
> > scm:svn:https://url/project/trunk/Child
> >
> >
> > Which is the convention for a multi-module project.
> >
> > If your "Child" project has to be seperate, with it's own trunk, etc. I
> > would suggest (if svn) using svn:externals to access the child under the
> > parent project. Since it ownly appends the name on a multi-module
> project,
> > I'm trying to figure out how you locally check out your project...
> perhaps
> > create a "trunks"-style setup in your version control would be best?
> >
> > Eric
> >
> > On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> > >
> > > I have also noticed the same behavior with the project url, the sit
> url
> > > and
> > > the scm url even if in the effective the corresponding properties are
> > > correct (without the artifactId appended).
> > >
> > > On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Hi,
> > > >
> > > > In the parent POM I have the following:
> > > > [...]
> > > >
> > > >
> > > http://localhost/repos/repo/${groupId}/${artifactId}/trunk
> > > > <http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ${scmConnection}
> > > > ${scmConnection}
> > > >
> > > > [...]
> > > >
> > > > The child POM has nothing expect mandatory elements and the
> reference
> > to
> > > > the parent POM. Both the child and the parent are snapshots. The
> > parent
> > > POM
> > > > has been deployed to the remote repository.
> > > >
> > > > When I run mvn help:effective-pom on the child project, I get:
> > > > [...]
> > > >
> > > >
> > > http://localhost/repos/repo/com.opicasso/Child/trunk/Child
> > > >
> > > >
> > > > http://localhost/repos/repo/com.opicasso/Child/trunk/Child
> > > >
> > > >
> > > > [..]
> > > >
> > > > I would have expected:
> > > > [...]
> > > >
> > > > http://localhost/repos/repo/com.opicasso/Child/trunk
> > > >
> > > >
> > > > http://localhost/repos/repo/com.opicasso/Child/trunk
> > >
> > > >
> > > > [..]
> > > >
> > > > Why does maven happen the child artifactId to the connections? Does
> > > maven
> > > > merge the parent scm connections with the children ones ? But in the
> > > current
> > > > case the child has no scm connections defined in its pom.
> > > >
> > > > How to get rid of this extra artifactId?
> > > >
> > > > Thanks
> > > >
> > > > Oscar
> > > >
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Eric Redmond
> > http://blog.propellors.net
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
RE: Parent POM, properties and scm problem
I'm wondering if the following would work:
- Make your organizational pom project. Don't define any entries in
it.
- Have all of your projects depend on it as a parent
- Build and install your organizational pom to a central repository
accessible to all of your projects.
I'm thinking that you can then independently build and deploy your
organizational pom by itself, and have your projects use it, from the
repository, as a parent for definition purposes, though not build purposes.
I'd be interested to know whether this works. It seems useful.
-- Bryan
-Original Message-
From: Oscar Picasso [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 01, 2007 10:31 AM
To: Maven Users List
Subject: Re: Parent POM, properties and scm problem
The current Maven behaviour is fine for multimodule projects.
However I am trying to write a organizational POM that all my projets would
inherited and wanted to avoid duplication of the scm section.
So in case of independent projects it does not make sense to put all them
inside the same trunk.
I guess currently I cannot avoid this duplication.
On 7/31/07, Eric Redmond <[EMAIL PROTECTED]> wrote:
>
> Maven does this so that child module's scm can be defined once in the
> parent.
>
>
> scm:svn:https://url/project/trunk
>
>
>
> Child
>
> Then the Child module's scm url is automatically set as:
>
>
> scm:svn:https://url/project/trunk/Child
>
>
> Which is the convention for a multi-module project.
>
> If your "Child" project has to be seperate, with it's own trunk, etc. I
> would suggest (if svn) using svn:externals to access the child under the
> parent project. Since it ownly appends the name on a multi-module project,
> I'm trying to figure out how you locally check out your project... perhaps
> create a "trunks"-style setup in your version control would be best?
>
> Eric
>
> On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> >
> > I have also noticed the same behavior with the project url, the sit url
> > and
> > the scm url even if in the effective the corresponding properties are
> > correct (without the artifactId appended).
> >
> > On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi,
> > >
> > > In the parent POM I have the following:
> > > [...]
> > >
> > >
> > http://localhost/repos/repo/${groupId}/${artifactId}/trunk
> > > <http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk>
> > >
> > >
> > >
> > >
> > >
> > > ${scmConnection}
> > > ${scmConnection}
> > >
> > > [...]
> > >
> > > The child POM has nothing expect mandatory elements and the reference
> to
> > > the parent POM. Both the child and the parent are snapshots. The
> parent
> > POM
> > > has been deployed to the remote repository.
> > >
> > > When I run mvn help:effective-pom on the child project, I get:
> > > [...]
> > >
> > >
> > http://localhost/repos/repo/com.opicasso/Child/trunk/Child
> > >
> > >
> > > http://localhost/repos/repo/com.opicasso/Child/trunk/Child
> > >
> > >
> > > [..]
> > >
> > > I would have expected:
> > > [...]
> > >
> > > http://localhost/repos/repo/com.opicasso/Child/trunk
> > >
> > >
> > > http://localhost/repos/repo/com.opicasso/Child/trunk
> >
> > >
> > > [..]
> > >
> > > Why does maven happen the child artifactId to the connections? Does
> > maven
> > > merge the parent scm connections with the children ones ? But in the
> > current
> > > case the child has no scm connections defined in its pom.
> > >
> > > How to get rid of this extra artifactId?
> > >
> > > Thanks
> > >
> > > Oscar
> > >
> > >
> > >
> >
>
>
>
> --
> Eric Redmond
> http://blog.propellors.net
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM, properties and scm problem
The current Maven behaviour is fine for multimodule projects.
However I am trying to write a organizational POM that all my projets would
inherited and wanted to avoid duplication of the scm section.
So in case of independent projects it does not make sense to put all them
inside the same trunk.
I guess currently I cannot avoid this duplication.
On 7/31/07, Eric Redmond <[EMAIL PROTECTED]> wrote:
>
> Maven does this so that child module's scm can be defined once in the
> parent.
>
>
> scm:svn:https://url/project/trunk
>
>
>
> Child
>
> Then the Child module's scm url is automatically set as:
>
>
> scm:svn:https://url/project/trunk/Child
>
>
> Which is the convention for a multi-module project.
>
> If your "Child" project has to be seperate, with it's own trunk, etc. I
> would suggest (if svn) using svn:externals to access the child under the
> parent project. Since it ownly appends the name on a multi-module project,
> I'm trying to figure out how you locally check out your project... perhaps
> create a "trunks"-style setup in your version control would be best?
>
> Eric
>
> On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> >
> > I have also noticed the same behavior with the project url, the sit url
> > and
> > the scm url even if in the effective the corresponding properties are
> > correct (without the artifactId appended).
> >
> > On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi,
> > >
> > > In the parent POM I have the following:
> > > [...]
> > >
> > >
> > http://localhost/repos/repo/${groupId}/${artifactId}/trunk
> > >
> > >
> > >
> > >
> > >
> > >
> > > ${scmConnection}
> > > ${scmConnection}
> > >
> > > [...]
> > >
> > > The child POM has nothing expect mandatory elements and the reference
> to
> > > the parent POM. Both the child and the parent are snapshots. The
> parent
> > POM
> > > has been deployed to the remote repository.
> > >
> > > When I run mvn help:effective-pom on the child project, I get:
> > > [...]
> > >
> > >
> > http://localhost/repos/repo/com.opicasso/Child/trunk/Child
> > >
> > >
> > > http://localhost/repos/repo/com.opicasso/Child/trunk/Child
> > >
> > >
> > > [..]
> > >
> > > I would have expected:
> > > [...]
> > >
> > > http://localhost/repos/repo/com.opicasso/Child/trunk
> > >
> > >
> > > http://localhost/repos/repo/com.opicasso/Child/trunk
> >
> > >
> > > [..]
> > >
> > > Why does maven happen the child artifactId to the connections? Does
> > maven
> > > merge the parent scm connections with the children ones ? But in the
> > current
> > > case the child has no scm connections defined in its pom.
> > >
> > > How to get rid of this extra artifactId?
> > >
> > > Thanks
> > >
> > > Oscar
> > >
> > >
> > >
> >
>
>
>
> --
> Eric Redmond
> http://blog.propellors.net
>
Re: Parent POM, properties and scm problem
Maven does this so that child module's scm can be defined once in the
parent.
scm:svn:https://url/project/trunk
Child
Then the Child module's scm url is automatically set as:
scm:svn:https://url/project/trunk/Child
Which is the convention for a multi-module project.
If your "Child" project has to be seperate, with it's own trunk, etc. I
would suggest (if svn) using svn:externals to access the child under the
parent project. Since it ownly appends the name on a multi-module project,
I'm trying to figure out how you locally check out your project... perhaps
create a "trunks"-style setup in your version control would be best?
Eric
On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
>
> I have also noticed the same behavior with the project url, the sit url
> and
> the scm url even if in the effective the corresponding properties are
> correct (without the artifactId appended).
>
> On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > In the parent POM I have the following:
> > [...]
> >
> >
> http://localhost/repos/repo/${groupId}/${artifactId}/trunk
> >
> >
> >
> >
> >
> >
> > ${scmConnection}
> > ${scmConnection}
> >
> > [...]
> >
> > The child POM has nothing expect mandatory elements and the reference to
> > the parent POM. Both the child and the parent are snapshots. The parent
> POM
> > has been deployed to the remote repository.
> >
> > When I run mvn help:effective-pom on the child project, I get:
> > [...]
> >
> >
> http://localhost/repos/repo/com.opicasso/Child/trunk/Child
> >
> >
> > http://localhost/repos/repo/com.opicasso/Child/trunk/Child
> >
> >
> > [..]
> >
> > I would have expected:
> > [...]
> >
> > http://localhost/repos/repo/com.opicasso/Child/trunk
> >
> >
> > http://localhost/repos/repo/com.opicasso/Child/trunk
>
> >
> > [..]
> >
> > Why does maven happen the child artifactId to the connections? Does
> maven
> > merge the parent scm connections with the children ones ? But in the
> current
> > case the child has no scm connections defined in its pom.
> >
> > How to get rid of this extra artifactId?
> >
> > Thanks
> >
> > Oscar
> >
> >
> >
>
--
Eric Redmond
http://blog.propellors.net
Re: Parent POM, properties and scm problem
I have also noticed the same behavior with the project url, the sit url and
the scm url even if in the effective the corresponding properties are
correct (without the artifactId appended).
On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> In the parent POM I have the following:
> [...]
>
> http://localhost/repos/repo/${groupId}/${artifactId}/trunk
>
>
>
>
>
>
> ${scmConnection}
> ${scmConnection}
>
> [...]
>
> The child POM has nothing expect mandatory elements and the reference to
> the parent POM. Both the child and the parent are snapshots. The parent POM
> has been deployed to the remote repository.
>
> When I run mvn help:effective-pom on the child project, I get:
> [...]
>
> http://localhost/repos/repo/com.opicasso/Child/trunk/Child
>
>
> http://localhost/repos/repo/com.opicasso/Child/trunk/Child
>
>
> [..]
>
> I would have expected:
> [...]
>
> http://localhost/repos/repo/com.opicasso/Child/trunk
>
>
> http://localhost/repos/repo/com.opicasso/Child/trunk
>
> [..]
>
> Why does maven happen the child artifactId to the connections? Does maven
> merge the parent scm connections with the children ones ? But in the current
> case the child has no scm connections defined in its pom.
>
> How to get rid of this extra artifactId?
>
> Thanks
>
> Oscar
>
>
>
Parent POM, properties and scm problem
Hi,
In the parent POM I have the following:
[...]
http://localhost/repos/repo/${groupId}/${artifactId}/trunk
${scmConnection}
${scmConnection}
[...]
The child POM has nothing expect mandatory elements and the reference to the
parent POM. Both the child and the parent are snapshots. The parent POM has
been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
[..]
I would have expected:
[...]
http://localhost/repos/repo/com.opicasso/Child/trunk
http://localhost/repos/repo/com.opicasso/Child/trunk
[..]
Why does maven happen the child artifactId to the connections? Does maven
merge the parent scm connections with the children ones ? But in the current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
AW: Referencing list POM properties
I just found that someone posted the same issue. Sorry.
This was the reply:
...
You cannot do that AFAIK. However, you can do something like this.
...
...
${some.var}
put version here
Then access that ${some.var} somewhere else in your pom.
...
-Ursprüngliche Nachricht-
Von: Kanzlers, Andreas [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 12. April 2007 09:48
An: Maven Users List
Betreff: Referencing list POM properties
You can reference all properties defined in the POM xml like
project.version, project.build.finalName via ${project.version},
${project.build.finalName}.
But how can I access a list property, for example the version of a
specific dependency ?
...
...
...
junit
junit
3.8.1
test
...
Regards,
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Referencing list POM properties
You can reference all properties defined in the POM xml like
project.version, project.build.finalName via ${project.version},
${project.build.finalName}.
But how can I access a list property, for example the version of a
specific dependency ?
...
...
...
junit
junit
3.8.1
test
...
Regards,
Andreas
Re: Refer to overridden parent POM properties?
Manos Batsis wrote:
In multiproject modules i would like to refer to (soon to be) overridden
parent POM properties. For exampe, how can i do something like
${parent.project.artifactId}
Obviously this does not make sense, i meant something like
${parent.project.artifactId}-module1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Refer to overridden parent POM properties?
Hello,
In multiproject modules i would like to refer to (soon to be) overridden
parent POM properties. For exampe, how can i do something like
${parent.project.artifactId}
When i try using the pre-overridden value like
${project.artifactId}
i get an ModelInterpolationException. Using a custom property in the
parent pom and pointing to that freezes the build (feels like mvn falls
in an infinite loop or something).
Thanks,
Manos
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Using Special Chars (& etc.) in POM properties
Try again as Plain Text Hi, Does anyone know how to use an ampersand (&) as part of a property value in a POM? eg. 4.0.0 . . . text1 && text2 && text3 . . . I have tried using & and with no success. When using & I get the following message: Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: entity reference names can not start with character '&' (position: START_TAG seen ...test1 &&... @153:57) at org.codehaus.plexus.util.xml.pull.MXParser.parseEntityRef(MXParser.ja va:2209) . . . Any help would be greatly appreciated. Thanks, Graham. -- View this message in context: http://www.nabble.com/-M2--Using-Special-Chars-%28--etc.%29-in-POM-properties-tf2015885.html#a5541211 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [fixed] Problem with filtering on pom properties
Sorry - yes, meant to mention that I've still got dots in the names and it's now working fine. -- View this message in context: http://www.nabble.com/Problem+with+filtering+on+pom+properties-t1649749.html#a4470255 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [fixed] Problem with filtering on pom properties
just for reference, does it work with dots in the property element names or not ? On 5/19/06, Toni Price <[EMAIL PROTECTED]> wrote: Well, it seems this was after all a problem with the property not being activated correctly in my settings.xml. I thought it was being set OK, but clearly it wasn't since I've changed the settings.xml structure slightly and it's now working as I expect. What I still don't understand is why 'mvn help:effective-settings' yielded a result that made me think the property was being set correctly ... (maybe I was just being dumb :-) nonetheless, it's working now! Toni -- View this message in context: http://www.nabble.com/Problem+with+filtering+on+pom+properties-t1649749.html#a4469849 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [fixed] Problem with filtering on pom properties
Well, it seems this was after all a problem with the property not being activated correctly in my settings.xml. I thought it was being set OK, but clearly it wasn't since I've changed the settings.xml structure slightly and it's now working as I expect. What I still don't understand is why 'mvn help:effective-settings' yielded a result that made me think the property was being set correctly ... (maybe I was just being dumb :-) nonetheless, it's working now! Toni -- View this message in context: http://www.nabble.com/Problem+with+filtering+on+pom+properties-t1649749.html#a4469849 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with filtering on pom properties
Hi Jorg and thanks for your suggestion. If maven doesn't like property elements with dots in them that wouldn't be so good for me because I have quite a few like that! Does it cause problems sometimes and sometimes not? (I would think so, because so far most of my properties have seemed to work OK). In any event, I tried changing the relevant ones by removing the dots but unfortunately it still doesn't filter properly ... -- View this message in context: http://www.nabble.com/Problem+with+filtering+on+pom+properties-t1649749.html#a4469122 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with filtering on pom properties
For some reason maven doesn't like property elements with dots in them. Try
changing db.actual.password to db_actual_password.
On 5/19/06, Toni Price <[EMAIL PROTECTED]> wrote:
Hello Maven users
I am having a problem getting filtering to work with property values. In a
hibernate.cfg.xml I have the database password specified as "${db.password
}"
and now I'm trying to get the password in there when it's copied over. I
have:
src/main/filters/${env}_${targetHost}.properties
src/main/resources
true
hibernate.cfg.xml
[...]
I know this is working since I have some other properties (specified in
the
relevant ${env}_${targetHost}.properties) that I'm filtering too, and they
get interpolated correctly.
If I put something like the following in my pom.xml:
${project.groupId}
Or
somepasswordvalue
then it works, and the value is substituted correctly.
However, I want to be able to set the password in my settings.xml -- I
don't
want to put it in my source code. But if I set a property (say
"db.actual.password") in a profile in my settings.xml and put this in my
pom.xml:
${db.actual.password}
then I land up with the string literal ("${db.actual.password}") in my
filtered hibernate.cfg.xml.
I've tested with 'mvn help:effective-settings" that the value of
db.actual.password is being set correctly.
Am I using the filtering mechanism incorrectly? (I would have thought this
is a common sort of use case.) If anyone can point out where I'm going
wrong
I'd be grateful ...
Thanks
Toni
--
View this message in context:
http://www.nabble.com/Problem+with+filtering+on+pom+properties-t1649749.html#a4468317
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem with filtering on pom properties
Hello Maven users
I am having a problem getting filtering to work with property values. In a
hibernate.cfg.xml I have the database password specified as "${db.password}"
and now I'm trying to get the password in there when it's copied over. I
have:
src/main/filters/${env}_${targetHost}.properties
src/main/resources
true
hibernate.cfg.xml
[...]
I know this is working since I have some other properties (specified in the
relevant ${env}_${targetHost}.properties) that I'm filtering too, and they
get interpolated correctly.
If I put something like the following in my pom.xml:
${project.groupId}
Or
somepasswordvalue
then it works, and the value is substituted correctly.
However, I want to be able to set the password in my settings.xml -- I don't
want to put it in my source code. But if I set a property (say
"db.actual.password") in a profile in my settings.xml and put this in my
pom.xml:
${db.actual.password}
then I land up with the string literal ("${db.actual.password}") in my
filtered hibernate.cfg.xml.
I've tested with 'mvn help:effective-settings" that the value of
db.actual.password is being set correctly.
Am I using the filtering mechanism incorrectly? (I would have thought this
is a common sort of use case.) If anyone can point out where I'm going wrong
I'd be grateful ...
Thanks
Toni
--
View this message in context:
http://www.nabble.com/Problem+with+filtering+on+pom+properties-t1649749.html#a4468317
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] xdoc pom properties
thanks Jamie,
But I've tried this in a xdoc file and no result...
${pom.properties.value}
${project.properties.value}
$project.properties.get("value")
$pom.properties.value
$project.getProperties().get("value")
But in the velocity template of maven, these three methods are ok and return
Scratch :
$project.getProperties().get("value")
$project.properties.get("value")
$project.properties.value
Is there another method to substitute a value in xdoc file with a value in
the pom.xml or another value in a file.properties ?
--
View this message in context:
http://www.nabble.com/-M2-xdoc-pom-properties-t1512658.html#a4127432
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] xdoc pom properties
On 4/26/06, juju <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> Is it possible to use a property of pom in xdoc file ?
>
> Pom
>
>
> Scratch
>
>
> xDoc
>
> Hello $project.getProperties().get("my.value")
>
> I can to use that in a velocity template, but I would like to do that in a
> xdoc file.
>
> thanks.
> --
> View this message in context:
> http://www.nabble.com/-M2-xdoc-pom-properties-t1512658.html#a4104278
> Sent from the Maven - Users forum at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
If the POM looked like this:
Scratch
I think ${pom.properties.value} would work; however, the period in "my.value"
may be problematic. I'm not totally sure though.
--
Jamie
[M2] xdoc pom properties
Hi,
Is it possible to use a property of pom in xdoc file ?
Pom
Scratch
xDoc
Hello $project.getProperties().get("my.value")
I can to use that in a velocity template, but I would like to do that in a
xdoc file.
thanks.
--
View this message in context:
http://www.nabble.com/-M2-xdoc-pom-properties-t1512658.html#a4104278
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting pom properties in mojo
Nope that didn't work.
- sachin
On Feb 22, 2006, at 6:27 PM, Alexandre Poitras wrote:
I have no idea if it has something to do with it but have you tried to
get ride of the @readonly annotations on the project property?
On 2/22/06, Sachin Patel <[EMAIL PROTECTED]> wrote:
How can I set a property in a mojo so that it is accessible in a pom?
For example I have a dependency...
eclipse
org.eclipse.wst.server.core
${version}
I have a mojo that needs to dynamically set the versions of my
dependencies so I tried adding...
/**
* @parameter expression="${project}"
* @required
* @readonly
*/
private MavenProject project;
and the setting the version property like so..
project.getProperties().put("version", "1.0.0");
But when the compile phase ran, the ${version} property did not
resolve. Any ideas what I'm doing wrong?
Thanks.
- sachin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Alexandre Poitras
Québec, Canada
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting pom properties in mojo
I have no idea if it has something to do with it but have you tried to
get ride of the @readonly annotations on the project property?
On 2/22/06, Sachin Patel <[EMAIL PROTECTED]> wrote:
> How can I set a property in a mojo so that it is accessible in a pom?
>
> For example I have a dependency...
>
>
>eclipse
>org.eclipse.wst.server.core
>${version}
>
>
> I have a mojo that needs to dynamically set the versions of my
> dependencies so I tried adding...
>
> /**
> * @parameter expression="${project}"
> * @required
> * @readonly
> */
> private MavenProject project;
>
> and the setting the version property like so..
>
> project.getProperties().put("version", "1.0.0");
>
> But when the compile phase ran, the ${version} property did not
> resolve. Any ideas what I'm doing wrong?
>
> Thanks.
>
> - sachin
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Alexandre Poitras
Québec, Canada
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Setting pom properties in mojo
How can I set a property in a mojo so that it is accessible in a pom?
For example I have a dependency...
eclipse
org.eclipse.wst.server.core
${version}
I have a mojo that needs to dynamically set the versions of my
dependencies so I tried adding...
/**
* @parameter expression="${project}"
* @required
* @readonly
*/
private MavenProject project;
and the setting the version property like so..
project.getProperties().put("version", "1.0.0");
But when the compile phase ran, the ${version} property did not
resolve. Any ideas what I'm doing wrong?
Thanks.
- sachin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] pom properties how-to ?
Thanks Odea,
however, just a minor change to what you wrote:
HELLO
There are no "property" tag within "properties".
SaM
On 12/6/05, Odea Ching <[EMAIL PROTECTED]> wrote:
>
> Hi Samuel,
>
> You can use the properties element to set the value of a property in a
> resource file through the pom's properties section.
>
> #sample.properties
> samle.property=${hello.value}
>
> pom.xml:
>
>
> HELLO
>
>
>
> You can also use it to declare properties/variables that you can use on
> your plugin configuration, etc.
>
> Regards,
> Deng
>
>
> Samuel Le Berrigaud wrote:
>
> >Hi,
> >
> >just wanted to know how to use the "properties" in the POM (the one
> >defined under project/properties)
> >
> >
> >I tried something like:
> >
> >
> >
> > a.name
> > a.value
> >
> >
> >
> >but it does not work...
> >
> >And then can reference the properties in the POM like that ${a.name} ?
> >
> >Thanks,
> >--
> >Samuel Le Berrigaud
> >
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Samuel Le Berrigaud
Re: [m2] pom properties how-to ?
Hi Samuel,
You can use the properties element to set the value of a property in a
resource file through the pom's properties section.
#sample.properties
samle.property=${hello.value}
pom.xml:
HELLO
You can also use it to declare properties/variables that you can use on
your plugin configuration, etc.
Regards,
Deng
Samuel Le Berrigaud wrote:
Hi,
just wanted to know how to use the "properties" in the POM (the one
defined under project/properties)
I tried something like:
a.name
a.value
but it does not work...
And then can reference the properties in the POM like that ${a.name} ?
Thanks,
--
Samuel Le Berrigaud
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] pom properties how-to ?
Hi,
just wanted to know how to use the "properties" in the POM (the one
defined under project/properties)
I tried something like:
a.name
a.value
but it does not work...
And then can reference the properties in the POM like that ${a.name} ?
Thanks,
--
Samuel Le Berrigaud
Re: Parent POM Properties
Bruno or Anyone,
Was there ever a resolution to reference the parent poms properties ?
Pete
On 29/10/05, Frank Mena <[EMAIL PROTECTED]> wrote:
> BTW, there is a bug when you use ${basedir} inside of
> {$basedir}/somemodule
>
> For example, if your basedir is d:\app\module2, it expands to
> d:\app\module2d:\app\module2
>
> I'm also trying to do somewthinbg similar to you. I'm using a Java/XML
> binding library (jibx) that requires it to bytecode enhance all the classes
> that it touches. If the classes are across modules, then it needs all the
> classpaths of the modules it needs at the same time to bytecode enhance.
>
> It appears that the design of Maven as far as dependencies is to JAR your
> artifacts and place them in your repository first before you use them in
> another module. There does not seem to be a way to relatively find the base
> directory for dependent modules. If I can get the basedir of the parent root
> artifact, then I could use
> ${parent.basedir}/ovr/common/servlets
> or such to jibx my artifact and have access to other artifacts class files.
> I don't understand why this seems to be such a difficult concept and request
> to understand. I hope we get an answer to how to perform multi-module
> projects and have access each modules path.
>
> Frank
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM Properties
BTW, there is a bug when you use ${basedir} inside of
{$basedir}/somemodule
For example, if your basedir is d:\app\module2, it expands to
d:\app\module2d:\app\module2
I'm also trying to do somewthinbg similar to you. I'm using a Java/XML
binding library (jibx) that requires it to bytecode enhance all the classes
that it touches. If the classes are across modules, then it needs all the
classpaths of the modules it needs at the same time to bytecode enhance.
It appears that the design of Maven as far as dependencies is to JAR your
artifacts and place them in your repository first before you use them in
another module. There does not seem to be a way to relatively find the base
directory for dependent modules. If I can get the basedir of the parent root
artifact, then I could use
${parent.basedir}/ovr/common/servlets
or such to jibx my artifact and have access to other artifacts class files.
I don't understand why this seems to be such a difficult concept and request
to understand. I hope we get an answer to how to perform multi-module
projects and have access each modules path.
Frank
Re: POM properties
On Fri, 2005-10-28 at 09:23 -0400, Tomislav Stojcevich wrote:
> How do you reference something that is a collection in the POM?
>
> Let's say there are 2 developers and I want to get their email
> addresses to put in the notifier.address section of the ciManagement
> section (I know a mailing list is preferred but we don't have one set
> up right now and I know there are JIRA's in Continuum to propogate the
> developers into continuum as users and the users as the notifiers but
> until then...)
>
> ${project.developers.developer.xxx.email} (where xxx is ther id)
> or
> ${project.developers.developer[0].email)
Currently the interpolation won't allow that but there is a JIRA issue
for moving toward using Velocity like interpolation which would make
this easier.
> On 10/27/05, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> > On Thu, 2005-10-27 at 15:25 +1000, Michael McCrann wrote:
> > > Hi,
> > >
> > > Is there any documentation that describes what things from the POM are
> > > available as variables?
> >
> > Anything in the POM itself:
> >
> > http://maven.apache.org/maven-model/maven.html
> >
> > > How do I specify 'target' as a property? The things I have tried haven't
> > > worked:
> >
> > You can take a look at this:
> >
> > http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
> >
> > Which shows the Super POM which has most of the build elements that you
> > might want to use.
> >
> > > $(pom.build.outputDirectory}
> > > ${pom.build.dir}
> > > ${build.dir}
> >
> > Close but no cigar :-)
> >
> > ${pom.build.directory}
> >
> > >
> > > NOTICE
> > > This e-mail and any attachments are confidential and may contain
> > > copyright material of Macquarie Bank or third parties. If you are not the
> > > intended recipient of this email you should not read, print, re-transmit,
> > > store or act in reliance on this e-mail or any attachments, and should
> > > destroy all copies of them. Macquarie Bank does not guarantee the
> > > integrity of any emails or any attached files. The views or opinions
> > > expressed are the author's own and may not reflect the views or opinions
> > > of Macquarie Bank.
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > --
> > jvz.
> >
> > Jason van Zyl
> > jason at maven.org
> > http://maven.apache.org
> >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> tom
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM properties
How do you reference something that is a collection in the POM?
Let's say there are 2 developers and I want to get their email
addresses to put in the notifier.address section of the ciManagement
section (I know a mailing list is preferred but we don't have one set
up right now and I know there are JIRA's in Continuum to propogate the
developers into continuum as users and the users as the notifiers but
until then...)
${project.developers.developer.xxx.email} (where xxx is ther id)
or
${project.developers.developer[0].email)
On 10/27/05, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> On Thu, 2005-10-27 at 15:25 +1000, Michael McCrann wrote:
> > Hi,
> >
> > Is there any documentation that describes what things from the POM are
> > available as variables?
>
> Anything in the POM itself:
>
> http://maven.apache.org/maven-model/maven.html
>
> > How do I specify 'target' as a property? The things I have tried haven't
> > worked:
>
> You can take a look at this:
>
> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
>
> Which shows the Super POM which has most of the build elements that you
> might want to use.
>
> > $(pom.build.outputDirectory}
> > ${pom.build.dir}
> > ${build.dir}
>
> Close but no cigar :-)
>
> ${pom.build.directory}
>
> >
> > NOTICE
> > This e-mail and any attachments are confidential and may contain copyright
> > material of Macquarie Bank or third parties. If you are not the intended
> > recipient of this email you should not read, print, re-transmit, store or
> > act in reliance on this e-mail or any attachments, and should destroy all
> > copies of them. Macquarie Bank does not guarantee the integrity of any
> > emails or any attached files. The views or opinions expressed are the
> > author's own and may not reflect the views or opinions of Macquarie Bank.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> --
> jvz.
>
> Jason van Zyl
> jason at maven.org
> http://maven.apache.org
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM Properties
Jason van Zyl wrote:
What is it concretely you are trying to do. Often users give us
solutions to their problems without actually telling us what the problem
is. We really need to know what you're trying to do first. We definitely
don't want duplication and is something we try to avoid so we need more
details.
I'll try again with an example:
Given a project with three subprojects, I want to use a checkstyle definition
that is valid for all three subprojects. (The checkstyle definition itself
differs from project to project since it mostly depends on the style used by
the customer.)
+- toplevel/
|
+- pom.xml
+- src/
| |
| +- java/
| |
| +- resources/
||
|+- checkstyle.xml
|
+- subproj1/
| |
| +- pom.xml
| +- src/
| +- ...
|
+- subproj2/
|
+- pom.xml
+- src/
+- ...
Now, if I want to include a checkstyle configuration like the following in
toplevel/pom.xml so that it is picked up by all subprojects:
...
${topdir}/src/java/resources/checkstyle.xml
...
I cannot use ${basedir} since this always yields the base directory of the
subproject being built. What I want is to access resources relative to the
toplevel directory.
I don't want to use a fixed URL for the location since I want to have versioning
for the file and I also need it to be in a relative location since a customer
will build the project in a location that may not even have access to the
fixed URL (even though I could work around this using a profile).
Cheers,
// Bruno
PS: I am aware that I cannot currently set the checkstyle configuration, see
http://jira.codehaus.org/browse/MNG-587 and
http://jira.codehaus.org/browse/MNG-1113
(I have a local copy that allows me to do anyway until an official solution is
out).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM Properties
On Thu, 2005-10-27 at 10:51 +0200, Bruno Essmann wrote:
> Hi
>
>
> Is there any way to access property values of a parent POM?
>
> I'm aware that any tag in a POM serves as valid property, however I'm
> looking for a way to access the values of the POM defined by
> ${pom.parent.relativePath}.
>
>
> Taking this a step further:
>
> I'm also looking for a way to access values of the root parent POM
> (i.e. the toplevel POM that does not feature a parent tag).
>
> The reason behind this is to try and avoid duplication of files and
> information while at the same time being able to keep all the project
> artifacts in one place that can be stored in a repository.
What is it concretely you are trying to do. Often users give us
solutions to their problems without actually telling us what the problem
is. We really need to know what you're trying to do first. We definitely
don't want duplication and is something we try to avoid so we need more
details.
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
We know what we are, but know not what we may be.
-- Shakespeare
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM Properties
Hmm... I think I'm not clearly expressing what I want to do.
I'll try again with an example...
Imagine the parent POM states somwhere, e.g. in a plugin configuration:
...
${basedir}/somedir
...
Now my subproject inherits this configuration, however the ${basedir}
is evaluated relative to the subproject base directory.
What I want to achieve is to place configuration data as well as
input files in a parent project and then inherit it in a subproject.
In a perfect world such dependencies could simply be resolved by
accessing resources via the classloader and then use the maven engine
(along with dependencies) to resolve everything. However sometimes I
have to specify file locations as parameters, for example
"checkstyle:checkstyle" supports the parameter "headerFile". I could
use "${basedir}/header.txt" in the parent. However I would have to
copy the header file to each and every subproject. As an alternative
I could specify something like "http://somewhere.com/header.txt";.
I would however prefer to just have the file in the parent and refer
to it from a subproject. To achieve this however I either have to
define the location "../header.txt" in each and every subproject.
I am simply looking for a way to define it in the parent POM so that
the location stays for the subprojects...
Phew, sorry for being verbose, but I hope I explained a little better
what I'm trying to do...
// Bruno
Bruno Essmann wrote:
Yes, I'm aware of the propagation, hence the question if there is a way
to *explicitly* access the values of the parent POM. :-)
But from the answer I also presume that there is no way, forcing me to
put common data to a webpage or some other obscure location rather than
into a repo...
Cheers,
// Bruno
Edwin Punzalan wrote:
All of the configuration values in a parent is propagated to its
children. So you may not put a configuration in a child when the
parent already has it.
Bruno Essmann wrote:
Is there any way to access property values of a parent POM?
I'm aware that any tag in a POM serves as valid property, however I'm
looking for a way to access the values of the POM defined by
${pom.parent.relativePath}.
Taking this a step further:
I'm also looking for a way to access values of the root parent POM
(i.e. the toplevel POM that does not feature a parent tag).
The reason behind this is to try and avoid duplication of files and
information while at the same time being able to keep all the project
artifacts in one place that can be stored in a repository.
Therefore it'd be nice if I could access files in a subproject relative
to the root parent project, i.e. something along the lines of
${root.basedir} that corresponds to the ${basedir} in the root parent
project...
(Please note, I'm not talking about project resources that get created
and could be imported using a module and a dependency to it, but
rather about input files used during a maven run like license files,
company and/or client logo files, stylesheets, documentation and stuff
like this. :-))
--
Ergon Informatik AG, Kleinstrasse 15, 8008 Zürich, Switzerland
[EMAIL PROTECTED], Phone +41 44 268 89 16, Fax +41 1 261 27 50
http://www.ergon.ch/
__
e r g o n smart people - smart software
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM Properties
Yes, I'm aware of the propagation, hence the question if there is a way
to *explicitly* access the values of the parent POM. :-)
But from the answer I also presume that there is no way, forcing me to
put common data to a webpage or some other obscure location rather than
into a repo...
Cheers,
// Bruno
Edwin Punzalan wrote:
All of the configuration values in a parent is propagated to its
children. So you may not put a configuration in a child when the parent
already has it.
Bruno Essmann wrote:
Is there any way to access property values of a parent POM?
I'm aware that any tag in a POM serves as valid property, however I'm
looking for a way to access the values of the POM defined by
${pom.parent.relativePath}.
Taking this a step further:
I'm also looking for a way to access values of the root parent POM
(i.e. the toplevel POM that does not feature a parent tag).
The reason behind this is to try and avoid duplication of files and
information while at the same time being able to keep all the project
artifacts in one place that can be stored in a repository.
Therefore it'd be nice if I could access files in a subproject relative
to the root parent project, i.e. something along the lines of
${root.basedir} that corresponds to the ${basedir} in the root parent
project...
(Please note, I'm not talking about project resources that get created
and could be imported using a module and a dependency to it, but
rather about input files used during a maven run like license files,
company and/or client logo files, stylesheets, documentation and stuff
like this. :-))
--
Ergon Informatik AG, Kleinstrasse 15, 8008 Zürich, Switzerland
[EMAIL PROTECTED], Phone +41 44 268 89 16, Fax +41 1 261 27 50
http://www.ergon.ch/
__
e r g o n smart people - smart software
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM Properties
Hi,
All of the configuration values in a parent is propagated to its
children. So you may not put a configuration in a child when the parent
already has it.
Bruno Essmann wrote:
Hi
Is there any way to access property values of a parent POM?
I'm aware that any tag in a POM serves as valid property, however I'm
looking for a way to access the values of the POM defined by
${pom.parent.relativePath}.
Taking this a step further:
I'm also looking for a way to access values of the root parent POM
(i.e. the toplevel POM that does not feature a parent tag).
The reason behind this is to try and avoid duplication of files and
information while at the same time being able to keep all the project
artifacts in one place that can be stored in a repository.
Therefore it'd be nice if I could access files in a subproject relative
to the root parent project, i.e. something along the lines of
${root.basedir} that corresponds to the ${basedir} in the root parent
project...
(Please note, I'm not talking about project resources that get created
and could be imported using a module and a dependency to it, but
rather about input files used during a maven run like license files,
company and/or client logo files, stylesheets, documentation and stuff
like this. :-))
Regards,
// Bruno
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Parent POM Properties
Hi
Is there any way to access property values of a parent POM?
I'm aware that any tag in a POM serves as valid property, however I'm
looking for a way to access the values of the POM defined by
${pom.parent.relativePath}.
Taking this a step further:
I'm also looking for a way to access values of the root parent POM
(i.e. the toplevel POM that does not feature a parent tag).
The reason behind this is to try and avoid duplication of files and
information while at the same time being able to keep all the project
artifacts in one place that can be stored in a repository.
Therefore it'd be nice if I could access files in a subproject relative
to the root parent project, i.e. something along the lines of
${root.basedir} that corresponds to the ${basedir} in the root parent
project...
(Please note, I'm not talking about project resources that get created
and could be imported using a module and a dependency to it, but
rather about input files used during a maven run like license files,
company and/or client logo files, stylesheets, documentation and stuff
like this. :-))
Regards,
// Bruno
--
Ergon Informatik AG, Kleinstrasse 15, 8008 Zürich, Switzerland
[EMAIL PROTECTED], Phone +41 44 268 89 16, Fax +41 1 261 27 50
http://www.ergon.ch/
__
e r g o n smart people - smart software
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: POM properties
On Thu, 2005-10-27 at 16:30 +1000, Michael McCrann wrote:
> Jason,
>
> Thanks, I have read through those documents but it still not clear to me
> how the build directory should be expressed as
> a variable.
>
> I thought it would be:
>
> ${pom.build.directory}
You're right, it's null and that's a bug. I will file an issue in JIRA
when it comes back up.
> but this doesn't seem to work.
>
> Michael
>
>
>
>
>
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 27 October 2005 4:14 PM
> To: Maven Users List
> Subject: Re: POM properties
>
>
> On Thu, 2005-10-27 at 15:25 +1000, Michael McCrann wrote:
> > Hi,
> >
> > Is there any documentation that describes what things from the POM are
> available as variables?
>
> Anything in the POM itself:
>
> http://maven.apache.org/maven-model/maven.html
>
> > How do I specify 'target' as a property? The things I have tried
> haven't worked:
>
> You can take a look at this:
>
> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
>
> Which shows the Super POM which has most of the build elements that you
> might want to use.
>
> > $(pom.build.outputDirectory}
> > ${pom.build.dir}
> > ${build.dir}
>
> Close but no cigar :-)
>
> ${pom.build.directory}
>
> >
> > NOTICE
> > This e-mail and any attachments are confidential and may contain
> copyright material of Macquarie Bank or third parties. If you are not
> the intended recipient of this email you should not read, print,
> re-transmit, store or act in reliance on this e-mail or any attachments,
> and should destroy all copies of them. Macquarie Bank does not guarantee
> the integrity of any emails or any attached files. The views or opinions
> expressed are the author's own and may not reflect the views or opinions
> of Macquarie Bank.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
We know what we are, but know not what we may be.
-- Shakespeare
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: POM properties
Jason,
Thanks, I have read through those documents but it still not clear to me
how the build directory should be expressed as
a variable.
I thought it would be:
${pom.build.directory}
but this doesn't seem to work.
Michael
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, 27 October 2005 4:14 PM
To: Maven Users List
Subject: Re: POM properties
On Thu, 2005-10-27 at 15:25 +1000, Michael McCrann wrote:
> Hi,
>
> Is there any documentation that describes what things from the POM are
available as variables?
Anything in the POM itself:
http://maven.apache.org/maven-model/maven.html
> How do I specify 'target' as a property? The things I have tried
haven't worked:
You can take a look at this:
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
Which shows the Super POM which has most of the build elements that you
might want to use.
> $(pom.build.outputDirectory}
> ${pom.build.dir}
> ${build.dir}
Close but no cigar :-)
${pom.build.directory}
>
> NOTICE
> This e-mail and any attachments are confidential and may contain
copyright material of Macquarie Bank or third parties. If you are not
the intended recipient of this email you should not read, print,
re-transmit, store or act in reliance on this e-mail or any attachments,
and should destroy all copies of them. Macquarie Bank does not guarantee
the integrity of any emails or any attached files. The views or opinions
expressed are the author's own and may not reflect the views or opinions
of Macquarie Bank.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM properties
On Thu, 2005-10-27 at 15:25 +1000, Michael McCrann wrote:
> Hi,
>
> Is there any documentation that describes what things from the POM are
> available as variables?
Anything in the POM itself:
http://maven.apache.org/maven-model/maven.html
> How do I specify 'target' as a property? The things I have tried haven't
> worked:
You can take a look at this:
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
Which shows the Super POM which has most of the build elements that you
might want to use.
> $(pom.build.outputDirectory}
> ${pom.build.dir}
> ${build.dir}
Close but no cigar :-)
${pom.build.directory}
>
> NOTICE
> This e-mail and any attachments are confidential and may contain copyright
> material of Macquarie Bank or third parties. If you are not the intended
> recipient of this email you should not read, print, re-transmit, store or act
> in reliance on this e-mail or any attachments, and should destroy all copies
> of them. Macquarie Bank does not guarantee the integrity of any emails or any
> attached files. The views or opinions expressed are the author's own and may
> not reflect the views or opinions of Macquarie Bank.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
POM properties
Hi,
Is there any documentation that describes what things from the POM are
available as variables?
For example, I want to copy my war file into the Weblogic application dir. In
my POM I have
maven-antrun-plugin
package
run
How do I specify 'target' as a property? The things I have tried haven't worked:
$(pom.build.outputDirectory}
${pom.build.dir}
${build.dir}
NOTICE
This e-mail and any attachments are confidential and may contain copyright
material of Macquarie Bank or third parties. If you are not the intended
recipient of this email you should not read, print, re-transmit, store or act
in reliance on this e-mail or any attachments, and should destroy all copies of
them. Macquarie Bank does not guarantee the integrity of any emails or any
attached files. The views or opinions expressed are the author's own and may
not reflect the views or opinions of Macquarie Bank.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m1] How to set pom properties from maven.xml ?
Hi list, I'd like to modify some existing pom property (declared in the property tag in project.xml) from a maven.xml script. How can I achieve this? I've tried things like pom.getProperties().setProperty(), or pom.setProperties(pom.getProperties().setProperty()) or pom.context.setVariable but when I query pom.getProperty nothing has changed for my property. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pom properties after the fact [was: do something...]
Sorry about the chattiness today. I think I've finally nailed down my
actual question.
In the previous thread I commented on how I can change properties
after the fact that build on each other. For instance:
qb.name=Tommy Maddox
best.qb.ever=${qb.name}
qb.name=Ben Roethlisberger
now best.qb.ever is "Ben Roethlisberger"
however, I don't see this behavior for project.xml(pom) properties:
project.properties
--
best.qb.ever=Tommy Maddox
project.xml
-
${best.qb.ever}
maven.xml
pom.build.sourceDirectory: ${pom.build.sourceDirectory}
This outputs as:
...Tommy Maddox
Is there any way to get the above behavior to occur in the example
below? If not, I'll need to make the changes suggested in the
previous thread and I'll stop polluting this list ;-)
Thanks,
Ben
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: reference list of all pom.* properties?
This is the most comprehensive one:
http://cvs.apache.org/viewcvs.cgi/maven/src/java/org/apache/maven/project/Project.java?rev=1.99&view=markup
On Thu, 9 Sep 2004 23:14:11 -0400, Springer, Ian P. <[EMAIL PROTECTED]> wrote:
> Is there a reference available anywhere for all the pom.* properties
> (pom.artifactId, pom.currentVersion, etc..), as well as pom.* functions
> (pom.getPluginContext('maven-java-plugin'), pom.getDependency('junit'),
> etc..) that are defined by Maven?
>
> Thanks,
> Ian
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
reference list of all pom.* properties?
Is there a reference available anywhere for all the pom.* properties
(pom.artifactId, pom.currentVersion, etc..), as well as pom.* functions
(pom.getPluginContext('maven-java-plugin'), pom.getDependency('junit'),
etc..) that are defined by Maven?
Thanks,
Ian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using POM properties in xdocs
Hi, Thanks Jason, I'll look into that. I also wanted to commend Maven for stepping into a hole no product including Ant has (to my knowledge) filled - defining the processes (via plugins and goals) used through project developments. Defining a goal for every standard process (war:war for creating war files, etc) is a step in the correct path. However it seems that even though a lot of work has been put into defining these goals, they are not documented enough. I believe a document is in place to specify and diffrenciate between inner, implementation-related goals (such as site:generate) and the more public, process-oriented goals that are aimed at the developers of the project (I know there is a document specifying a complete list of WHICH goals are defined, but it does not define the correct goal, or a goal-combination, for each task during development - should I use jar:jar, dist, etc'). For trivial tasks it is sometimes obvious, but not always. None-the-less: well done Maven team! - Original Message - From: "Jason van Zyl" <[EMAIL PROTECTED]> To: "Maven Users List" <[EMAIL PROTECTED]> Sent: Sunday, October 05, 2003 10:44 PM Subject: Re: Using POM properties in xdocs > On Sun, 2003-10-05 at 18:00, Arik Kfir wrote: > > Hello, > > > > Is it possible to use POM properties in xdoc files? If so, how? > > There isn't actually a way to interpolate the POM generally into the > xdocs but now that I realize that isn't possible that seems strange. I'm > surprised you are the first to ask. > > > I imagine some sort of token filtering on these files should be applied before generating the site, but I'm not quite sure where to start, as I am a bit new to maven, and I was also hoping some sort of an automated mechanism is available before custom work needs to be done (perhaps a preGoal to the site:generate?). > > A quick fix would be simply the take the tree of produced xdocs and use > the velocity jelly tag to simply place the $pom in the context and > process all the xdocs to produce a version with the $pom values > expanded. > > This is probably something we should add generally. > > > Any help will be appreciated, > > Arik. > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using POM properties in xdocs
On Sun, 2003-10-05 at 18:00, Arik Kfir wrote: > Hello, > > Is it possible to use POM properties in xdoc files? If so, how? There isn't actually a way to interpolate the POM generally into the xdocs but now that I realize that isn't possible that seems strange. I'm surprised you are the first to ask. > I imagine some sort of token filtering on these files should be applied before > generating the site, but I'm not quite sure where to start, as I am a bit new to > maven, and I was also hoping some sort of an automated mechanism is available before > custom work needs to be done (perhaps a preGoal to the site:generate?). A quick fix would be simply the take the tree of produced xdocs and use the velocity jelly tag to simply place the $pom in the context and process all the xdocs to produce a version with the $pom values expanded. This is probably something we should add generally. > Any help will be appreciated, > Arik. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using POM properties in xdocs
Hello, Is it possible to use POM properties in xdoc files? If so, how? I imagine some sort of token filtering on these files should be applied before generating the site, but I'm not quite sure where to start, as I am a bit new to maven, and I was also hoping some sort of an automated mechanism is available before custom work needs to be done (perhaps a preGoal to the site:generate?). Any help will be appreciated, Arik.
POM Properties Reference
Where can I find a reference of all of the general Maven properties? Dave Ford Smart Soft - The Developer Training Company http://www.smart-soft.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
