I need something like that. When Maven checks the pom.xml if it sees
variables it gets their value. I need something like that:
String version = something.getProperty("project.version") // to get
${project.version}
String revision = something.getProperty("svn.revision.number") // to get
${svn.revi
I am developing a Maven plugin. It will search for given token and inject
values at given files. Everything is OK but there is only one thing that I
am struggling with. I have some tokens and variables and I want to read them
from a properties file. For example:
project.version = ${project.version
copy resources requires an output directory that is what I don't want.
However I didn't check to implement a custom filter, do I need copy
resources plugin to it. I don't want to use copy resources plugin because I
am developing a plugin myself that has lightweights of some plugins. Is
there any ex
Hi,
On Fri, Feb 8, 2013 at 10:00 PM, kamaci wrote:
> I am developing a Maven plugin. It will search for given token and inject
> values at given files.
That sound exactly like something the maven-resource-plugin can do.
Everything is OK but there is only one thing that I
> am struggling with.
I am developing a Maven plugin. It will search for given token and inject
values at given files. Everything is OK but there is only one thing that I
am struggling with. I have some tokens and variables and I want to read them
from a properties file. For example:
project.version = ${project.version
Am 07.02.2013 21:43, schrieb Curtis Rueden:
Just in case you didn't see it already, the following page of the M2E
documentation explains (rather obtusely) in detail about how to configure
M2E's "lifecycle mappings" to work with various Maven plugins:
http://wiki.eclipse.org/M2E_plugin_execu
On Friday, 8 February 2013, Marshall Schor wrote:
> Thanks Stephen,
>
> I'm trying to figure out why I'm not seeing this in the actual staged
> artifacts,
> or in previous releases.
>
> Here's what I've concluded:
>
> The maven-gpg-plugin has a bug - it copies the pom.xml to the
> finalname.pom, i
Thanks Stephen,
I'm trying to figure out why I'm not seeing this in the actual staged artifacts,
or in previous releases.
Here's what I've concluded:
The maven-gpg-plugin has a bug - it copies the pom.xml to the finalname.pom, in
target, and then signs that, without substituting into the propert
Wayne Fay wrote
>> If you then need the executions in the root and only some children... put
>> the executions in pluginManagement in the root but without calling out
>> any
>> goals. Repeat the executions in
>
> in the root, calling out the
>> goals for those to execute and specifying
>
> fal
stephenconnolly wrote
> If you then need the executions in the root and only some children... put
> the executions in pluginManagement in the root but without calling out any
> goals. Repeat the executions in
>
> in the root, calling out the
> goals for those to execute and specifying
>
> fals
> If you then need the executions in the root and only some children... put
> the executions in pluginManagement in the root but without calling out any
> goals. Repeat the executions in in the root, calling out the
> goals for those to execute and specifying false and
> then finally repeat for th
Please read this:
http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072
You will conclude that the only solution is to make the finalName a
configuration parameter of the mojo so that the recursive property
evaluation code can compute the eff
Matthew Adams wrote/
> NB: I can't seem to find where the svn repo is that contains
> RequireActiveProfile.java, which is why I used the maven repo search link.
/
Found it at https://svn.apache.org/repos/asf/maven/enforcer.
Still, what gives? Why is it commented out?
--
View this message in c
I'm trying to use the requireActiveProfile rule via the
maven-enforcer-plugin, version 1.2:
=
org.apache.maven.plugins
maven-enforcer-plugin
${app.maven-enforcer-plugin.version}
require-orm-profiles
We have a POM, where the specifies a final name like this:
org.apache.uima.textmarker.engine_${parsedVersion.osgiVersion}
We use the maven-build-helper plugin to set the variable to be the same as the
version, except with a period before the SNAPSHOT qualifier, for example.
This works fine
stephenconnolly wrote
> 1. Congratulations on successfully posting XML from Nabble. Until now, I
> genuinely did not think it was possible (as evidenced by the many many
> posts via Nabble where the xml is stripped). I take your success as an
> indication that you are a smart guy with some technica
Yeah, I didn't do anything special to get XML to render. I remember problems
in the past, but forgot and just blindly pasted into the nabble text editor
from my local text editor...
I'm actually quite dumb. Just ask my wife. ;)
--
View this message in context:
http://maven.40175.n5.nabble.c
Hi Łukasz,
without the full information it's hard to guess what's wrong...my glass bulp is
under maintenance ;-)
>
> Generally I think I reached limit of of number artifacts that could be
> deployed at one time...
What does this mean? The limit of the number of artifacts ? I can't believe
that
Hello everyone,
I see that, by including a pom in compile scope, the project has the
dependencies defined as transitive dependencies in it's classpath.
Two things come to my mind, which could make a scope include sensible:
1) dependency:analyze AKA define what you depend on for compilation
- we us
Hi all,
thanks a lot for answers,
2013/2/8 Karl Heinz Marbaise :
> Hi Łukasz,
>
> unfortunately you can't disable the deployment of the metadata...
and I will not write own workaround :)
>
> But what is the real problem with load on your repository manager server ?
Generally I think I reached l
Hi Łukasz,
unfortunately you can't disable the deployment of the metadata...
But what is the real problem with load on your repository manager server ?
Really causing problems only by metadata ?
Which RM do you use ?
Kind regards
Karl-Heinz Marbaise
Original-Nachricht
> Da
Hi,
You understood exactly what I want.
Currently I have issues with repository manager, it's not able to
handle all deploys which are happening.
On repository side metadata_maven.xml is ignored, and regenerated, and
since deploys fails with metadata.xml I would like to remove it.
Łukasz Tasz
20
Hi,
Not sure to understand. Could you maybe rephrase a bit?
Getting rid of maven-metadata.xml, if this is actually what you want, is
quite impossible I think.
But if this is what you ask for, could you explain a bit more why you came
to think it would be a good idea?
Cheers
-- Baptiste
Le 8 févr.
Hi All,
I have simple question, can I somehow disable deployment of metadata_maven.xml?
my repository manager cares for it bu it's own, so it causes
unnecessary load - which is currently my problem...
thanks in advance
Łukasz Tasz
--
24 matches
Mail list logo
