Sorry for answering so late. The described approach would activate a profile
base on a property. I don't see any relationship to a proxy profile (Whatever
that is).
Once again: There is no proxies element within profile. Thus "" can
NOT be used to configure proxies.
M.
Am 25.02.2012 um 00:47
The Page https://maven.apache.org/ref/3.0.4/maven-settings/settings.html
says for the element "proxies/proxy*":
> Multiple proxy profiles might come in handy for anyone working from a
> notebook or other mobile platform, to enable easy switching of entire proxy
> configurations by simply specif
>>
>>foo
>>LATEST
>>
>And that prevents your build from being reproducible...
Not If you combine dynamic version ranges with replacement during deploy
and release the builds remain reproducable. They are in
fact even more reproducable than now.
Example: You trunk would contain:
late
t;native" Maven Solution
> would
> > be better.
>
>
> eh... how is invoking a maven plugin not a "native" maven solution
>
The Plugin is "native". "A little script invoking the version plugin" is not
native since you need that script an
Hello Trevor,
contrary to some responses here I don't think your issues is SCM/Version
Control issue. This is not your fault.
Your issue is missing "soft" or dynamic version support in maven.
Actually the responses propose some workarounds:
1.Manual:
> An easy solution is: When Alice prepares the
I've tried hard to archive reproducable builds combined with soft versions
in maven. But I now believe
it is not possible.
Here is what I want:
I've got a project A and many Projects depending on it.
All Project shalls be build by a CI Tool.
A Build of A will trigger a build of all the other proj
; I don't have a solution to your problem, but I would
> > advice against
> > > > putting the real version number instead of
> > ${project.version}. It is
> > > > good practice to avoid such redundancy using ${project.version},
> > > > even though the release p
ing ${project.version}, even though the release
> > plugin can deal with explicit versions. Using
> > ${project.version} is also suggested by "The Definitive Guide"
> > (http://www.sonatype.com/products/maven/documentation/book-defguide).
> >
> > Reinhard
> >
I've replaced ${project.version} with 1.1-SNAPSHOT. The Release plugin
replaces this with 1.1 during release:prepare and fails with
the same message.
I think the release plugin should first trigger a install on the ejb and
then run the servlet target.
2009/3/24 Jörg Schaible
> Martin Ei
This may be a beginner question, but I haven't found any hints..
I've got a project that contains a servlet and an ejb. The Servlet depends
on the ejb. I've trouble releasing that as complete project.
My directory Layout is like:
pom.xml <- package type pom
servlet
pom.xml
ejb
Hi,
I need to have an scm section within my pom for the release plugin to work.
Entering the data manual is cumbersome. My workingcopy is under svn contrll,
so
the correct information is already there (somewhere in .svn). Is there some
magic (a plugin?) than can fill in the correct data from there
versions-maven-plugin looks like something that could fit my needs. Since
I'm new to maven I haven't understood everythingh you wrote but I'l give it
closer look as soon as I find time. Thanks for the help!
2009/3/6 Stephen Connolly
> 2009/3/6 Martin Eigenbrodt
>
> >
>
> The release plugin *is* clever enough to ask you if you want to
> replace SNAPSHOT versions in your dependencies with real release
> versions. Once it's gotten the necessary information from you, it
> makes the edits on your behalf. A good feature, that.
But that means I have to (manually?) b
se I would have to pull a
release for each dependency to get a "Snapshot Free" release. Or is this
done automatically by the release plugin?
Martin
2009/3/5 B Smith-Mannschott
> On Thu, Mar 5, 2009 at 07:50, Martin Eigenbrodt
> wrote:
> > I've tried the release plugin
I've tried the release plugin (when i wrote "performed a release" i meant
mvn release:prepare followed by mvn release:perform). That tag created in my
svn does contain the dynamic revision, as I wrote above. So the build is not
reproducible unless you backup all involved maven repositories: If a ne
Hello everybody,
I'm new to maven and have some problems: Ivy does replace dynmic revisions
with static once when delivering.
Can Maven do the same?
Example: I've got two project A and B.
B should always use the latest version of A. (My CI Server will later
trigger a Build of B on
every Change of
16 matches
Mail list logo
