iven a project can be built only with Java8+ this should be ok.
>
> T
>
> On Sun, Apr 21, 2024 at 4:03 PM Gary Gregory wrote:
>
> > Hi,
> >
> > A POM can't seem to inherit a parent POM configuration with properties
> > redefined in a child POM profile.
>
#x27;t seem to inherit a parent POM configuration with properties
> redefined in a child POM profile.
>
> Am I doing something wrong?
>
> For example:
>
> git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> cd commons-bcel
> git checkout eba45c05365fc89b0007296fc
Hi,
A POM can't seem to inherit a parent POM configuration with properties
redefined in a child POM profile.
Am I doing something wrong?
For example:
git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
cd commons-bcel
git checkout eba45c05365fc89b0007296fc3ee188cca5d091d
maven
it doesn't support it)
There's also a "Properties Maven Plugin":
https://www.mojohaus.org/properties-maven-plugin/
--
Stanimir
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additi
On Sun, Sep 24, 2023 at 7:49 PM Stanimir Stamenkov
wrote:
> I've just noticed you're providing multiple arguments in a single
> element – I'm not sure if this is supposed to work like that.
It is; this is how -Xplugin: works; those are arguments to the ErrorProne
plugins, not to javac itself:
Sun, 24 Sep 2023 18:04:51 +0200, /Delany/:
Thank you. Its not happening though. I also tried it from the pom, so
-Xplugin:ErrorProne
-XepExcludedPaths:.*/target/.* @${build.root}/ep.config
@files are Java 9+ feature for tools other than javadoc – just making
sure you're not using Java 8 here.
adicate by adding
> >> -Dep="-XepDisableAllChecks -Xep:ReferenceEquality:ERROR"
> >>
> >> But having all those rules on one line makes reviewing changes a pain.
> >> I don't really want to config the whole build with the compiler
> arguments.
>
eAllChecks -Xep:ReferenceEquality:ERROR"
But having all those rules on one line makes reviewing changes a pain.
I don't really want to config the whole build with the compiler arguments.
Is there a way to specify these in a properties file and have each
argument on its own line?
Have you tried using @file (
Sun, 24 Sep 2023 15:45:49 +0200, /Delany/:
[...]
Is there a way to specify these in a properties file and have each argument
on its own line?
Have you tried using @file (a-la javadoc options):
https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#command-line-argument-files
es on one line makes reviewing changes a pain.
I don't really want to config the whole build with the compiler arguments.
Is there a way to specify these in a properties file and have each argument
on its own line?
Kind regards,
Delany
On Thu, Jul 27, 2023 at 3:33 PM Laird Nelson wrote:
> Now I'm running Surefire 3.1.2 and noting that this all no longer seems
> necessary: running mvn test -Dx=y without any special XML to "turn it into"
> a System property works fine (my test can assert
> System.getProperty("x").equals("y")).
>
I dimly remember that once upon a time many years ago you had to explicitly
specify the system properties to be made available to your JUnit tests
running under Surefire:
y
(The documentation for this element reads in total: "List of System
properties to pass to a provider."
Hello,
I try to optimize my maven build structure. My goal is that I can manage the
build plugins and properties globally. I have got a multi maven project with
this structure
Pom.xml
|
| service
|parent/pom.xml => has got a section to external spring-boot
|apiservice/pom.
Hi there,
JUnit5.9.0-M1 was released that allows to conditionally cleanup the files
created using @TempDir
Problem Im having is how to configure junit properties through surefire.
My attempts at the bottom of:
https://github.com/junit-team/junit5/issues/2159
Hi. I tried making the version numbers dynamic with CI friendly properties
on
https://github.com/delanym/maven/commit/92b524a74f084b5def2fd807793b0e74d1ec02ed
When I build I get
[FATAL] Non-resolvable parent POM for
org.apache.maven:maven-plugin-api:4.0.0-alpha-1-SNAPSHOT: Could not find
Hi,
I have a multi module project that I'm trying to release with the
maven-release-plugin.
In my project ( https://github.com/nielsbasjes/yauaa ) I have 2 maven
modules that are relevant for my question:
- a maven module with a library that does something that takes time.
- a maven module with b
Hi,
we're using m-antrun-p in a submodule of a multimodule build. Some of
the tasks configured in the plugin use ${project.parent.basedir} to
access a certain directory in the parent directory.
With m-antrun-p 1.3 this works, the commands are executed successfully.
Now with version 3.0.0 thi
ously always want these remote resources included whether I build
> individually or in a reactor. How can I get that?
>
> Thanks,
>
>
> On Tue, 9 Mar 2021 at 10:43, Delany wrote:
>
>> Ok, no images thank you.
>> So I was barking up the wrong tree using the properties
lways want these remote resources included whether I build
individually or in a reactor. How can I get that?
Thanks,
On Tue, 9 Mar 2021 at 10:43, Delany wrote:
> Ok, no images thank you.
> So I was barking up the wrong tree using the properties tag in the plugin.
> I still don'
Ok, no images thank you.
So I was barking up the wrong tree using the properties tag in the plugin.
I still don't know what I did wrong, but it works now.
Now there's another issue. If I bundle resources in a *descriptorgenerator*
directory, the process goal will create an empty
ma
iving project will recognize one property
> "project.version" and not another "dep.dbs.commondb". It does that because
> project.version is one of the default properties the plugin passes through
> to its templating logic, I quote
>
> "Additional properties to
It does that because
project.version is one of the default properties the plugin passes through
to its templating logic, I quote
"Additional properties to be passed to Velocity. Several properties are
automatically added:"
https://maven.apache.org/plugins/maven-remote-resources-plugin/process-
a pom property from a dependency, then you
can’t do that either. (And if you think about it, that could be dangerous
because children properties could collide or interfere with your own.)
Note that you can declare a dependency/plugin and override a dependency —
sometimes that is useful.
I
Thanks I know how to use properties, but this plugin doesn't, it seems. It
has some special way of importing them:
https://maven.apache.org/plugins/maven-remote-resources-plugin/process-mojo.html
[image: image.png]
It can do this
org.test:shared-resources:${project.version}
But this i
The tag is documented here:
https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#properties
<https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#properties>
> On Feb 23, 2021, at 3:34 AM, Delany wrote:
>
> I don't want to
Well I gave it my best shot
maven-remote-resources-plugin
process-remote-resources
process
dbs:commondb:${bully}
3
I don't want to hardcode the version number of the remote project into this
plugin config, so I've used a property made available in a parent pom.
But it's not being resolved. What am I doing wrong?
maven-remote-resources-plugin
process-remote-resourc
y
> authorize with my jira system.
> If I use a cleartext password it s working without any issue.
>
> My question would be:
>
> Does a maven plugin need to add extra code to "decrypt" properties or is
> that managed transparently for maven centrally
to successfully
authorize with my jira system.
If I use a cleartext password it s working without any issue.
My question would be:
Does a maven plugin need to add extra code to "decrypt" properties or is
that managed transparently for maven centrally ?
Thanks a lot for your support
Thanks for the reply,
While this helps with some of the "parameters", this doesn't help me with
lists of complex parameters.
Also, is it not possible to use xml structures inside the plugin properties?
Op za 1 aug. 2020 om 15:07 schreef Robert Scholte :
> The Parameter annota
All,
I am using a plugin that uses several complex types as configuration. This
all looks nice when having a single plugin config, with properties
grouped together. But now I want to be able to override several of these
properties via the commandline or via a profile.
Afaik, setting complex propert
Hi All,
I am using a plugin that uses several complex types as configuration. This
all looks nice when having a single plugin config, with properties
grouped together. But now I want to be able to override several of these
properties via the commandline or via a profile.
Afaik, setting complex
Hi,
in my plugin test case I want to inject system properties into the
execution of the test case. Reason for that is we want to run the test in
our ci environment and need to inject certain username/passwords that are
used to connect to another system.
For this I am using a SettingsStub that is
Hello! I’m using versions-maven-plugin 2.7 and I have an issue with versions
defined as properties in a multi-module project.
I have all version properties defined in the parent POM, then I have several
child POMs defining dependency and plugin management.
When running `display-property
Hi all,
I've been trying to define a Maven Archetype which would contain properties
`package` and `version` with default values:
Inside archetype-metadata.xml, I included the following:
${groupId}
1.0-SNAPSHOT
Despite this configuration, the generation fails:
[ERROR] Archetype IT &
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,
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
> MET
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}
>
>
>
>
>
>
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="${projec
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
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
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
pgppgAg
ue, 19 Dec 2017 13:01:56 +0100, wrote:
Hello everyone,
I currently have the issue that I need to write certain properties of a
Maven build into a file and import them into another Maven build.
In this special case it is the Jenkins build number as well as the
version of the built artifact itself
Hello everyone,
I currently have the issue that I need to write certain properties of a
Maven build into a file and import them into another Maven build.
In this special case it is the Jenkins build number as well as the
version of the built artifact itself.
The two Maven builds are
t you can
> put the parts related to properties with dots and the ## markdown issue
>
> On Fri, Oct 20, 2017 at 10:50 PM, Alex O'Ree wrote:
> > Excellent, thanks Hervé
> >
> > On Fri, Oct 20, 2017 at 10:33 PM, Hervé BOUTEMY
> >
> > wrote:
> >> on M
I would say it's fine as is, but one possible suggestion would be add a h4
under the "Filtering" section labeled "Common Problems". Under that you can
put the parts related to properties with dots and the ## markdown issue
On Fri, Oct 20, 2017 at 10:50 PM, Alex O'Re
>
> > On Thu, Oct 19, 2017 at 1:34 PM, Hervé BOUTEMY
> >
> > wrote:
> > > there is some doc about this:
> > > http://maven.apache.org/plugins/maven-site-plugin/
> > > examples/creating-content.html#Filtering
> > >
> > > Regar
; examples/creating-content.html#Filtering
> >
> > Regards,
> >
> > Hervé
> >
> > Le lundi 16 octobre 2017, 20:22:04 CEST Alex O'Ree a écrit :
> > > I have some pom defined properties that I'm trying to inject into a
> >
> examples/creating-content.html#Filtering
>
> Regards,
>
> Hervé
>
> Le lundi 16 octobre 2017, 20:22:04 CEST Alex O'Ree a écrit :
> > I have some pom defined properties that I'm trying to inject into a maven
> > site markdown file. The file is named "
there is some doc about this:
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering
Regards,
Hervé
Le lundi 16 octobre 2017, 20:22:04 CEST Alex O'Ree a écrit :
> I have some pom defined properties that I'm trying to inject into a maven
> si
Consider how value interpolation usually works; the periods indicate a path of
dereferencing to get a final value. In your case, the period is part of the
value key, not a path separator.
Chas
> On Oct 16, 2017, at 5:22 PM, Alex O'Ree wrote:
>
> I have some pom defined prope
I have some pom defined properties that I'm trying to inject into a maven
site markdown file. The file is named "test.md.vm" and it's referenced in
the site descriptor.
> This property is used to test PDF .vm
> project injection. If you can read this in the
Why not just use a top-level POM’s dependencyManagement section, in conjunction
with top-level POM-defined properties if desired, to control the dependency
versions?
> On Oct 10, 2017, at 6:56 AM, Bikash Chandra Barad
> wrote:
>
> Hi Russell,
>
> I am not using it a
Message-
From: Russell Gold [mailto:russell.g...@oracle.com]
Sent: Tuesday, October 10, 2017 5:13 PM
To: Maven Users List
Subject: Re: Need to pass properties to the dependency POM file
Sounds as though you may want to use “import” scope
https://maven.apache.org/guides/introduction/introduction
No there isn't. The correct value needs to be in the pom (pom-deps) itself.
If then someone says you can specify the property values on the command
line as java system properties, it will not work as it will not update the
specified values in the pom-deps pom. Thus, the pom when deployed t
-deps.pom)file and
> adding that pom file as a dependency in my project.
> I need to substitute the properties of the dependency pom file(pom-deps.pom)
> to get the latest version dependencies, like parent POM, from the dependency
> POM, in my project.
> Is it possible to do so?
Hi,
I am trying to grouping the dependencies into a pom(pom-deps.pom)file and
adding that pom file as a dependency in my project.
I need to substitute the properties of the dependency pom file(pom-deps.pom)
to get the latest version dependencies, like parent POM, from the dependency
POM
Looks like if I use nested elements inside the call it's
working. Which is contrary to the maven-antrun-plugin 'Using Maven properties'
section at http://maven.apache.org/plugins/maven-antrun-plugin/usage.html. Will
try to reduce and example project and file a bug report.
I'm using maven-antrun-plugin to execute targets in an external Ant build file,
and having an issue with inherited properties.
${skipIvyPublish}
As you might guess from the above, I h
On Thursday 27 October 2016, Robert Scholte wrote:
> In my opinion it is a good choice to make the MavenProject immutable. This
> way the content of the pom.xml will always match the model, no magic.
> To adjust properties you could use MavenSession.userProperties instead,
> and I
In my opinion it is a good choice to make the MavenProject immutable. This
way the content of the pom.xml will always match the model, no magic.
To adjust properties you could use MavenSession.userProperties instead,
and I would expect that this would result in the same behavior as changing
Are there any news regarding this topic?
Kind regards,
Maik
> Gesendet: Montag, 10. Oktober 2016 um 16:01 Uhr
> Von: "Benson Margulies"
> An: "Maven Users List"
> Betreff: Re: Aw: Re: Re: [Regression] Declared properties could not be
> modified anymore wit
>> -Original Message-
>> From: M. Richey [mailto:mric...@gmx.de]
>> Sent: Monday, October 10, 2016 4:16 AM
>> To: users@maven.apache.org
>> Cc: Maven Users List
>> Subject: Aw: Re: Re: [Regression] Declared properties could not be modified
>> anymo
ubject: Aw: Re: Re: [Regression] Declared properties could not be modified
> anymore within a plugin
>
> Thanks Benson, but it does not work for me.
>
> During the execution it says:
>
> [main] [DEBUG] define property osgi-version = "1.0.0.v20161010082844"
>
> But
Message-
From: M. Richey [mailto:mric...@gmx.de]
Sent: Monday, October 10, 2016 4:16 AM
To: users@maven.apache.org
Cc: Maven Users List
Subject: Aw: Re: Re: [Regression] Declared properties could not be modified
anymore within a plugin
Thanks Benson, but it does not work for me.
During the
as I said before, during the execution the property gets set and the
pre-initialized value is used afterwards.
Best regards,
Maik
> Gesendet: Samstag, 08. Oktober 2016 um 16:45 Uhr
> Von: "Benson Margulies"
> An: "Maven Users List"
> Betreff: Re: Re: [Regression]
https://github.com/benson-basis/prop-override-example
Seems to be a demo that
https://github.com/basis-technology-corp/basis-build-helper-maven-plugin
overrides properties.
Using:
private void defineProperty(String name, String value) {
if (getLog().isDebugEnabled()) {
getLog
On Tue, Oct 4, 2016 at 5:35 AM, M. Richey wrote:
> Thanks Benson to point that out, it's a good example.
>
> We have several use cases where we modify properties with our plugins. We
> have a large variety of our software which to build for up to three brands.
> For wh
d property like
0
before, the result is:
[echo] 'tsproperty': 0
Kind regards,
Maik
> Gesendet: Dienstag, 04. Oktober 2016 um 14:03 Uhr
> Von: "Stephen Connolly"
> An: "Maven Users List"
> Cc: "i...@soebes.de"
> Betref
create a test case using just build-helper to set properties and redefine
them
On 4 October 2016 at 10:35, M. Richey wrote:
> Thanks Benson to point that out, it's a good example.
>
> We have several use cases where we modify properties with our plugins. We
> have a large variet
Thanks Benson to point that out, it's a good example.
We have several use cases where we modify properties with our plugins. We have
a large variety of our software which to build for up to three brands. For
which brand a specific software is to build is defined outside the poms and
pro
On Fri, Sep 30, 2016 at 1:50 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> On 30/09/16 15:20, mric...@gmx.de wrote:
>>
>> Hi all,
>>
>> we discovered a problem with properties defined in a pom.xml.
>>
>> Properties could be defined in a pom.xml like:
>
Hi all,
we discovered a problem with properties defined in a pom.xml.
Properties could be defined in a pom.xml like:
default
In a maven plugin we fetch all the properties by calling:
Properties projectProps = project.getProperties();
Running all this with maven 2 we were
Hi,
On 30/09/16 15:20, mric...@gmx.de wrote:
Hi all,
we discovered a problem with properties defined in a pom.xml.
Properties could be defined in a pom.xml like:
default
In a maven plugin we fetch all the properties by calling:
Properties projectProps = project.getProperties();
Running
Hi all,
we discovered a problem with properties defined in a pom.xml.
Properties could be defined in a pom.xml like:
default
In a maven plugin we fetch all the properties by calling:
Properties projectProps = project.getProperties();
Running all this with maven 2 we were able to modify the
--
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.4:integration-test
> (default-integration-test) on project taverna-activity-archetype:
> [ERROR] Archetype IT 'dummyActivity' failed
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:2.4:integration-test
(default-integration-test) on project taverna-activity-archetype:
[ERROR] Archetype IT 'dummyActivity' failed: Missing required
properties in archetype.properties: taver
Hi again, and sorry for bothering everyone.
The problem was just in a typo. Additional properties and standard ones
are interpolated in file names equally well.
Sorry again and best regards,
Sergey
On 07.05.2016 20:32, USHAKOV, Sergey wrote:
Hi!
I got a question on using archetypes
t;Copying fileset ... -> 0: []" and "Copied 0 files".
And at the same time this additional property is successfully
interpolated in resource content filtering.
Is it possible to get additional archetype properties interpolated in
resource file names? What may
Hi Tonio,
I am facing the same issue. Is this issue resolved? Can you share the
solution.
Thanks!
Gagan
--
View this message in context:
http://maven.40175.n5.nabble.com/Settings-properties-not-resolved-when-used-in-repository-element-tp5746974p5867105.html
Sent from the Maven - Users
The MojoHaus Team is pleased to announce of the
Properties Maven Plugin Version 1.0.0
http://www.mojohaus.org/properties-maven-plugin/
The Properties Maven Plugin is here to make life a little easier when dealing
with properties. It provides goals to read properties from files and URLs and
write
Hi,
I have added a wiki page...
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Properties+Guide
On 9/5/15 11:00 AM, Hervé BOUTEMY wrote:
here is the core reference:
http://maven.apache.org/ref/3-LATEST/maven-model-builder/
it does not explain everyting that can be found in POM or in
Regards,
Hervé
Le vendredi 4 septembre 2015 15:23:19 Steve Cohen a écrit :
> What with the Codehaus "termination of Maven services" and other recent
> developments, what has happened to the handy list of predefined project
> properties and other properties that was once but no
ct: Re: Where has the list of maven project properties gone?
Here is a good reference:
http://books.sonatype.com/mvnref-book/reference/resource-filtering-sect-properties.html
There is a new project wiki, but doesn't look like has much in the way of user
help:
https://cwiki
ho is allowed to write to it, I added an account but cannot create
content.
/r
At 3:23 PM -0500 9/4/15, Steve Cohen wrote:
>What with the Codehaus "termination of Maven services" and other recent
>developments, what has happened to the handy list of predefined project
>properties a
; and other recent
> developments, what has happened to the handy list of predefined project
> properties and other properties that was once but no longer is available
> from http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide ? I
> need to look up one stinking property that I kno
What with the Codehaus "termination of Maven services" and other recent
developments, what has happened to the handy list of predefined project
properties and other properties that was once but no longer is available
from http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesG
What is their purpose now if you are not using Ant?
If these are properties for the build, they should be inside the parent
POM as properties.
Ron
On 18/08/2015 10:02 AM, aalok singhvi wrote:
It's a migration of an ant project. It's java project. Presently ant gets
build properti
Hi,
For build time use, the simplest way is to put directly properties in
pom.xml (parent or childs depending on how/where it is used).
See
https://maven.apache.org/guides/introduction/introduction-to-the-pom.html ,
last part.
If you have lots of them it could eventually be externalized with
-Maven.html
<http://www.webagesolutions.com/knowledgebase/kb001-Converting-To-Maven.html>
Cheers,
Greg Trasuk
> On Aug 18, 2015, at 10:02 AM, aalok singhvi wrote:
>
> It's a migration of an ant project. It's java project. Presently ant gets
> build properties file on com
It's a migration of an ant project. It's java project. Presently ant gets
build properties file on compile time.
On Aug 18, 2015 9:56 AM, "Ron Wheeler"
wrote:
> What are you building?
> What language and technology stack?
>
> What are the properties files used for
What are you building?
What language and technology stack?
What are the properties files used for - run-time? If so, where do you
want them to end up when you install your app?
How are you installing it?
Ron
On 18/08/2015 7:02 AM, aalok singhvi wrote:
Hello,
I have a properties files. I
Hello,
I have a properties files. I have a multi modules project
with 1 parent pom and approx 19 child modules. Where should
i be putting the properties files which can be consumed by all
the child modules.
Thanks
--
Aalok Singhvi
-plugin (v2.1) to do the update:
mvn -DincludeProperties=mylib.version versions:update-properties
This used to work, when the released version was for example 1.0-beta-13
and the new development version was 1.0-beta-14-SNAPSHOT.
After I changed the new development version to always be 1.0-SNAPSHOT
something like this
defaultValue
product-properties
${productName}.properties
${productName}.properties
lds for an
> optional feature
> - add this buildnumber-maven-plugin declaration in a profile, and set
> "buildNumber" property to empty string if this profile is not activated -->
> complex profiles activation/deactivation requiring CLI switches
>
> Do you think there's s
idn't think about ?
Thanks,
Jeremie
--
View this message in context:
http://maven.40175.n5.nabble.com/Use-quiet-reference-notation-for-properties-tp5806363.html
Sent from the Maven - Users mailing list archive at Nabble.com.
> n pom of A.B.C i have defined a property as abc where A B C are modules. Now
> i want to access that property in pom of A.D.F module
What does the parent > child > grandchild relationship look like
between these various modules? What you want may not be possible.
Wayne
A.B.C}
bundle
So it is giving me error: bundle must be a valid version but is ${A.B.C}.
EDIT:
or can i use version of C module in someway as i have defined:
${A.B.C}
--
View this message in context:
http://maven.40175.n5.nabble.com/how-to-access-properties-defined-in-other-module-p
> the sections will have mojo-injected properties evaluated,
> but that isn't the case in my example. I was trying to have such
> properties evaluated in a element inside a
> element for the ear plugin, but it would not work until I modified the
> plugin to do an extra substi
1 - 100 of 2132 matches
Mail list logo