it to people.apache.org and commit manually
from there - only takes some minutes then. ;-)
Am Freitag, 31. Oktober 2014 schrieb Hervé BOUTEMY :
> > - surefire-archives/surefire-LATEST
> > +surefire-archives/surefire-${project.version}
> >
>
> are you sure it's a good id
> - surefire-archives/surefire-LATEST
> +surefire-archives/surefire-${project.version}
>
are you sure it's a good idea not to follow others components structure [1]
Regards,
Hervé
[1]
http://maven.apache.org/developers/website/deploy-component-reference-documentation.html
y, and I still need to apologise to you for my last
>>> > mistake, there is something like @{} in use in one of the (core?)
>>> plugins?
>>> > I seem to remember trying to use it elsewhere and being disappointed
>>> :-)
>>> >
>>> > Regards,
>
being disappointed
:-)
>
> Regards,
>
> Fred.
>
> [1] http://maven.apache.org/ref/3.1.0-alpha-1/maven-model-builder/
>
> > Le vendredi 24 mai 2013 06:43:35 Romain Manni-Bucau a écrit :
> > > Hi guys,
> > >
> > > Project.version seems evaluate
; >
> > Regards,
> >
> > Fred.
> >
> > [1] http://maven.apache.org/ref/3.1.0-alpha-1/maven-model-builder/
> >
> > > Le vendredi 24 mai 2013 06:43:35 Romain Manni-Bucau a écrit :
> > > > Hi guys,
> > > >
> > > > Projec
>
> Regards,
>
> Fred.
>
> [1] http://maven.apache.org/ref/3.1.0-alpha-1/maven-model-builder/
>
> > Le vendredi 24 mai 2013 06:43:35 Romain Manni-Bucau a écrit :
> > > Hi guys,
> > >
> > > Project.version seems evaluated by pom and not from
ne of the (core?) plugins?
I seem to remember trying to use it elsewhere and being disappointed :-)
Regards,
Fred.
[1] http://maven.apache.org/ref/3.1.0-alpha-1/maven-model-builder/
>
> Le vendredi 24 mai 2013 06:43:35 Romain Manni-Bucau a écrit :
> > Hi guys,
> >
> > Pro
gt;
> > Yes, that's what i expected but ATM in TomEE we have
> > hardcoded version and for half of the project it
> > matches the project.version (but only half :().
> >
> > That's not blocking at all but if maven could get this kind of feature
> > (
f the project it
> matches the project.version (but only half :().
>
> That's not blocking at all but if maven could get this kind of feature
> (maybe #{project.version}) it would be really great
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <http
Yes, that's what i expected but ATM in TomEE we have
hardcoded version and for half of the project it
matches the project.version (but only half :().
That's not blocking at all but if maven could get this kind of feature
(maybe #{project.version}) it would be really great
*Romain M
yes, it is the expected behaviour
see [1] for complete documentation of the model building algorithm:
project.version is evaluated during "model interpolation", which happens after
inheritance
AFAIK, there is no feature to evaluate before inheritance: this would require
a new not
Hi guys,
Project.version seems evaluated by pom and not from the pom it is defined
(at least in a multi modules project without a single version).
So basically you can get a version very different from the expected one.
If this is the expected behavior, could it be another variable to force the
ation
> Robert
>
> Op Sat, 22 Dec 2012 00:29:15 +0100 schreef :
>> Updated Branches:
>> refs/heads/master fe5c0331b -> 67ecba8ab
>>
>> fix site deploy for svnpubsub
>> using site:stage with
>>
${project.artifactId}-archives/${project.artifac
of using
${project.artifactId} variable: I dreamt a little too much on the pattern
simpification
>
> > Robert
> >
> > Op Sat, 22 Dec 2012 00:29:15 +0100 schreef :
> >> Updated Branches:
> >> refs/heads/master fe5c0331b -> 67ecba8ab
> >>
&g
o
file:///Users/olamy/dev/sources/maven/maven-release/target/staging/../../maven-release-manager-archives/maven-release-manager-2.5-SNAPSHOT/maven-release-manager
this is not correct
${project.artifactId}-archives/${project.artifactId}-${project.version}
then
scm:svn:https://svn.apache.org/repos/
ile:///Users/olamy/dev/sources/maven/maven-release/target/staging/../../maven-release-manager-archives/maven-release-manager-2.5-SNAPSHOT/maven-release-manager
this is not correct
${project.artifactId}-archives/${project.artifactId}-${project.version}
then
scm:svn:https://svn.apache.org/rep
ads/master fe5c0331b -> 67ecba8ab
fix site deploy for svnpubsub
using site:stage with
${project.artifactId}-archives/${project.artifactId}-${project.version}
will expand values in addition of parent so sucks for multi modules
projects.
Project: http://git-wip-us.apache.org/repos/asf/maven-
Great, thanks!
On Nov 13, 2009, at 11:55 AM, Brian Fox wrote:
In snapshots that used to be a problem but was fixed ~2.0.6ish. The
properties aren't interpolated on deploy so it works ok.
On Fri, Nov 13, 2009 at 1:23 PM, Alan D. Cabrera
wrote:
A while back this would not have been a safe thi
In snapshots that used to be a problem but was fixed ~2.0.6ish. The
properties aren't interpolated on deploy so it works ok.
On Fri, Nov 13, 2009 at 1:23 PM, Alan D. Cabrera wrote:
> A while back this would not have been a safe thing to do. Will this now
> work correctly?
>
>
> Regards,
> Alan
>
A while back this would not have been a safe thing to do. Will this
now work correctly?
Regards,
Alan
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
20 matches
Mail list logo
