asfgit closed pull request #225:
URL: https://github.com/apache/maven-site/pull/225
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
asfgit closed pull request #225:
URL: https://github.com/apache/maven-site/pull/225
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
rfscholte commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554558015
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
ide
pzygielo commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554014876
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
iden
MartinKanters commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554007128
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
michael-o commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553996067
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
ide
slawekjaranowski commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553961399
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -100,9 +100,11 @@ Introduction to Build Profiles
profile IDs
mthmulders commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553965389
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -100,9 +100,11 @@ Introduction to Build Profiles
profile IDs to us
michael-o commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554064780
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
ide
MartinKanters commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554058099
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
michael-o commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554041608
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
ide
mthmulders commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554024978
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
id
pzygielo commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554014876
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
iden
MartinKanters commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554007128
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
michael-o commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553996067
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
ide
mthmulders commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553966399
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
id
mthmulders commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553965389
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -100,9 +100,11 @@ Introduction to Build Profiles
profile IDs to us
slawekjaranowski commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553964597
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
slawekjaranowski commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553964597
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
slawekjaranowski commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553961399
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -100,9 +100,11 @@ Introduction to Build Profiles
profile IDs
mthmulders opened a new pull request #225:
URL: https://github.com/apache/maven-site/pull/225
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
The behavior is AND. You can have multiple profiles for OR.
Chas
> On Aug 15, 2016, at 11:45 AM, Christopher wrote:
>
> If there could be "AND" and "OR" primitives for profile activation
> conditions, you could do something like:
>
>
If there could be "AND" and "OR" primitives for profile activation
conditions, you could do something like:
!profilea
profilea
!true
Sadly, this feature does not exist.
On Fri, Aug
uot;
In this case, when invoking Maven with "mvn initialize", profilea
isn't defined so I would expect the profile not to be activated. This
is also what would happen if the value in the profile activation was
commented out.
To recap, this is the current result with Maven 3.
ys
"The following profile will be activated when the system property
"debug" is defined with a value which is not "true"."
In this case, when invoking Maven with "mvn initialize", profilea
isn't defined so I would expect the profile not to be acti
On 12/08/16 18:34, Robert Scholte wrote:
Maybe the documentation isn't clear enough.
I have added the documentation about the property activation with "!"
things a few days ago...
Either my assumption was wrong or the the intention is wrong...
Kind regards
Karl Heinz
--
not "true"."
In this case, when invoking Maven with "mvn initialize", profilea isn't
defined so I would expect the profile not to be activated. This is also
what would happen if the value in the profile activation was commented
out.
To recap, this is the
ot; is
defined with a value which is not "true"."
In this case, when invoking Maven with "mvn initialize", profilea isn't defined
so I would expect the profile not to be activated. This is also what would
happen if the value in the profile activation was com
Hi Karl Heinz,
you should read the activation like this:
always activate, *unless* profilea is true.
So it says nothing about the availability of the property.
Maybe the documentation isn't clear enough.
Robert
On Fri, 12 Aug 2016 17:45:21 +0200, Karl Heinz Marbaise
wrote:
Hi to all,
I h
MG>quick comment
> To: dev@maven.apache.org
> From: khmarba...@gmx.de
> Subject: Profile Activation
> Date: Fri, 12 Aug 2016 17:45:21 +0200
>
> Hi to all,
>
> I have the following profile:
>
>
>
>profile-not-value-true
>
>
Hi to all,
I have the following profile:
profile-not-value-true
profilea
!true
com.soebes.maven.plugins
echo-maven-plugin
initialize
------
Reply
message --
From: Ramón Rial
Date: 2015-08-25 19:57 GMT+02:00
Subject: About profile activation with JSR223
To: dev@maven.apache.org
Hello.
*About JSR223 support for activating Profiles*
I have a modified version of *PropertyProfileActivation.ja
Hello.
*About JSR223 support for activating Profiles*
I have a modified version of *PropertyProfileActivation.java* that allows
activate a profile evaluating a script.
I've done that with JSR223, and it is a minimal modification.
The idea is:
- Keep the old funcionality for property pr
Github user mikebrock commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46737130
I think that could be pretty cool. I see no reason why not.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46562788
@mikebrock Do you think MVEL would be suitable for a one expression
evaluator for a Maven profile activator? Imagine putting a MavenProject/pom.xml
in the MVEL context and
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46555048
I think Christian's idea is better as the logic is contained to the
specific activator. I'm not keen at all to add conditional logic to the POM
model anywhere, or any type
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46547866
Could be as simple as:
```
simple script
evaluating to a boolean
```
'engine-name' translates to javax.script.ScriptEngine.getEngineByNa
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46546268
Another option would be to provide support for activations based on some
language like:
OS IS 'Linux' AND ( PROPERTY 'Some Name' IS 'true' OR JDK IS
'1.
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46524647
First of all - thanks for your email.
I understand, that this will ruin current ORing technique, but at least it
could be fixed with copying for a while.
Github user FredipusRex commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46523185
You do realize that the current OR condition is actually out in use right
now in many POM files, right? This was previously the subject of a patch
(MNG-3106) - original
Github user MysterionRise closed the pull request at:
https://github.com/apache/maven/pull/20
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
f potentially having to duplicate a profile to get OR behavior,
> at least it's possible to have AND behaviour with multiple activators being
> AND'd. In it's current form profile activation makes it impossible to do
> often required.
>
> Unless anyone objects I'
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45826259
@jvanzyl Looks correct, please close this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your p
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45825613
Let me check.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featu
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45820916
@Konstantin, I've applied your patch and pushed the integration test. Try
it out and if it's good then close the pull request.
---
If your project is set up for it, you ca
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45811451
This change will actually make it match the book.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pr
Github user mosabua commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45811127
if we need to change something in the book - I can take care of that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45744828
Ok, I've written an integration test and I'll see what falls out on the
Maven dev list today.
---
If your project is set up for it, you can reply to this email and have yo
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45732464
Yes, that's not uncommon. The PR is fine, just waiting for any feedback on
the Maven dev list. There is one IT I would disable going forward (which tests
that the activator
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45731774
Hm, probably you are correct. I've just have strong feeling, when somebody
said 'Sonatype' - think about 'Maven' and vice-versa.
Regarding PR, let me know, if
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45731568
Yes, that is the Sonatype book which is the de facto reference for Maven
but not the official specification but probably as close to one as we have. The
actual documentatio
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45731386
http://jira.codehaus.org/browse/MNG-4565 - take a look here. It have link
for reference
http://books.sonatype.com/mvnref-book/reference/profiles-sect-activation.h
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45731097
What's the link you used for reference?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45704618
I've implement this patch, only cause it's 100% relates with official
documentation.
---
If your project is set up for it, you can reply to this email and have your
;
> At the cost of potentially having to duplicate a profile to get OR
> behavior, at least it's possible to have AND behaviour with multiple
> activators being AND'd. In it's current form profile activation makes it
> impossible to do often required.
>
> Unless anyo
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-45681556
I have argued on the Maven dev list to process your patch. The current
implementation I believe to be incorrect.
---
If your project is set up for it, you can reply to thi
plicate a profile to get OR behavior, at
least it's possible to have AND behaviour with multiple activators being AND'd.
In it's current form profile activation makes it impossible to do often
required.
Unless anyone objects I'm going to process
http://jira.codeha
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-45673757
I'm looking for a way to make this work, but this breaks MNG-3106 where the
current behaviour is to OR the activators. I agree there are cases where AND is
preferable but I
GitHub user MysterionRise opened a pull request:
https://github.com/apache/maven/pull/20
[MNG-4565] Multiple profile activation conditions does not work
Add possibilty to use multiple activators and have AND between them
You can merge this pull request into a Git repository by
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-45644286
Sorry, cut and paste error on my part when closing the other issues. Can
you reopen the PR again and I'll process it this afternoon.
---
If your project is set up for it,
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-45643803
I'm sorry, I don't understand, why you close this PR? Does it bad? I miss
something?
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/16
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-45442939
Tonight I'll try to process all the outstanding PRs. I'll let you know if I
need anything.
---
If your project is set up for it, you can reply to this email and have your
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-45431277
Just wonder, is there anything I could do?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pro
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-45138360
Cool, I'll take a look at look at the specific IT failure.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-45134460
I've update pull request. I change my approach, so it will not now a
platform dependable. But ITs are still failing at weird place. I'm 100% sure,
that it's not my fa
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44831587
Good stuff. I will try it today.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44797771
I created a simple shell script to help validate a pull request against the
Maven integration tests. This script is not great, and running the Maven
integration tests is no
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44757042
I'm 100% don't wanna rush. I will think about special activator for testing
purpose (It could be _AlwaysTrueActivator_). I will try to give it a try
tomorrow.
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44756700
Maybe creating an activator specifically for testing this might be better.
I will take a look as soon as I can. Likely tomorrow. Thanks for your patience,
we'll get this in
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44756676
I will take a look as soon as I can. Maybe making an activator specifically
for helping us test this will be better. Thanks for being patient, we'll get
this sorted and int
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44756590
Not understand your point about failing against master.
I agree that platform activators is not good idea. So same with JDK
activator, right? I'm only left wi
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44756291
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T12:37:52-05:00)
Maven home: /Users/jvanzyl/m2
Java version: 1.7.0_21, vendor: Oracle Corpora
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44755927
Awesome,this is the only platform, I couldn't test against.Could you
specify your _mvn -version_ output? I will try to fix test.
---
If your project is set up for it
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44755377
I used Maven, master branch at revision
73d35ba9597cd867717310ae8813376888debb9b. I applied your patch to master, and
ran the tests with Maven 3.2.1 on OSX.
---
If your p
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44751378
Could you tell me, what did you use?
I've run tests on Linux:
mvn -version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-
I applied your changes and your test fails. If you want to take look and
validate I will take a look later in the weekend.
---
T E S T S
---
Running org.apache.maven.model.building.ComplexActi
Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/16#issuecomment-44749028
Any updates on my pull request?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
GitHub user MysterionRise opened a pull request:
https://github.com/apache/maven/pull/16
[MNG-4565] Multiple profile activation conditions does not work
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MysterionRise/maven MNG
Validator is the *effective model*
> > validator
> > It contains validations that happen when everything is done: it's too
> > late for
> > profile activation controls
> >
> > Regards,
> >
> > Hervé
> >
> > Le dima
=HEAD1
Op Mon, 24 Mar 2014 00:20:06 +0100 schreef Hervé BOUTEMY
:
I don't think so: DefaultModelValidator is the *effective model*
validator
It contains validations that happen when everything is done: it's too
late for
profile activation controls
Regards,
Hervé
Le dimanche 23
I don't think so: DefaultModelValidator is the *effective model* validator
It contains validations that happen when everything is done: it's too late for
profile activation controls
Regards,
Hervé
Le dimanche 23 mars 2014 20:29:42 Robert Scholte a écrit :
> Hi Hervé,
>
>
vator context.
regards,
Robert
Op Sun, 23 Mar 2014 19:58:28 +0100 schreef :
Repository: maven
Updated Branches:
refs/heads/master 3c7744a9a -> 64c419506
[MNG-5608] added a warning on ${project.basedir} use for profile
activation
Project: http://git-wip-us.apache.org/repos/asf/maven/rep
Hi folks,
how is it going with this one? Is there anything planned?
I have attached a test project to the issue -
http://jira.codehaus.org/browse/MNG-5127
Hope it helps.
Thanks
Tony
1065778
>
> On Wed, Feb 9, 2011 at 9:12 AM, John Patrick wrote:
>> Hi,
>>
>> I believe this is the right mailing list, but please send me else where if
>> not.
>>
>> I would like to request that a new profile activation type be added,
>> which is
trick wrote:
> Hi,
>
> I believe this is the right mailing list, but please send me else where if
> not.
>
> I would like to request that a new profile activation type be added,
> which is based upon the maven version that is executing. What are
> people version upon this c
Vote for this jira ticket:
http://jira.codehaus.org/browse/MNG-4760
/Anders
On Wed, Feb 9, 2011 at 15:12, John Patrick wrote:
> Hi,
>
> I believe this is the right mailing list, but please send me else where if
> not.
>
> I would like to request that a new profile activa
Hi,
I believe this is the right mailing list, but please send me else where if not.
I would like to request that a new profile activation type be added,
which is based upon the maven version that is executing. What are
people version upon this change?
Base Ground
I've just done an up
I have discovered a bug in mvn 2.2.1 in relation to inheritance of profiles.
It affects profile inheritance within MavenProject and the
maven-help-plugin.
1. The help mojo issue: This appears to be a bug that has been re-introduced
into mvn 2.2.1: http://jira.codehaus.org/browse/MPH-16
There is
Hi
I'd like to have more more control on how profiles are activated. I've
registered my implementation of ProfileActivator as a plexus component
with org.apache.maven.profiles.activation.ProfileActivator role. I've
used to inject the component to the maven context. The
issue is that the extensions
Karel Vervaeke wrote:
clicky: http://jira.codehaus.org/browse/MNG-1775
Looks like a duplicate of MNG-2363, i.e. the ${basedir} expression is
already supposed to work in Maven 3.
Benjamin
-
To unsubscribe, e-mail: dev-unsu
Hi, I attached a patch to MNG-1775 today, and I would like to hear
to what extent I can you folks to apply it, and/or what needs to be changed.
My arguments pro my own patch:
- I think it works, the test2.zip serves as a test case (build fails
with maven-2.2.x, but succeeds after patch)
- http://m
I was wondering: why isn't the negation operator part of the version
range syntax anyways?
It's just a matter of keeping the syntax simple - it doesn't add
functionality since you can express the same with alternate range
boundries.
Agreed. And there's something else: what would an expressio
On 30/01/2009, at 5:14 AM, Torben S. Giesselmann wrote:
Heya,
I just submitted a patch which allows using the artifact version
range syntax for activating profiles by JDK version. The
implementation remains compatible to the way it's currently done
(prefix matching), but now also allows
Heya,
I just submitted a patch which allows using the artifact version range
syntax for activating profiles by JDK version. The implementation
remains compatible to the way it's currently done (prefix matching), but
now also allows using the negation operator "!" in conjunction with
version r
Felix Knecht wrote:
> Hi all
>
> The foofoo profile is always activated, no matter if a file 'timestamp'
> exists in the same directory like the pom.xml or
> not. It looks to me as the ${basedir} is not correctly resolved. Is this a
> known problem?
http://jira.codehaus.org/browse/MNG-3524
>
Is there a JIRA in for this?
nicolas de loof wrote:
Profile activation doesn't support property interopolation, even the
${basedir} one
This makes this feature unusable in nested modules configuration, as the
file are tested from current dir, not active project root...
I already reported
nicolas de loof schrieb:
> Profile activation doesn't support property interopolation, even the
> ${basedir} one
> This makes this feature unusable in nested modules configuration, as the
> file are tested from current dir, not active project root...
> I already reporte
Profile activation doesn't support property interopolation, even the
${basedir} one
This makes this feature unusable in nested modules configuration, as the
file are tested from current dir, not active project root...
I already reported this issue in JIRA.
Nicolas
2008/9/26 Felix Knecht &l
Hi all
The foofoo profile is always activated, no matter if a file 'timestamp' exists
in the same directory like the pom.xml or
not. It looks to me as the ${basedir} is not correctly resolved. Is this a
known problem?
Thanks
Felix
[EMAIL PROTECTED] ~/tmp $ cat pom.xml
http://maven.apache.org/P
1 - 100 of 163 matches
Mail list logo
