-Dresume=false -DdryRun=true release:prepare
I will try to play with the preparationGoals, but again, the default
behaviour seems flawed to me
Thanks for your help
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Stephen Connolly stephen.alan.conno...@gmail.com
these are not detected by a
default dryRun, some of them are. I just wanted to make the point that
releasing has many potential failure points
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Stephen Connolly stephen.alan.conno...@gmail.com
To: Maven Users List users
That's good to know Robert, thank you
I will add that to our release dryrun and hopefully it will catch more of
the uncaught problems early on
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Robert Scholte rfscho...@apache.org
To: Maven Users List users
release
can fail because a tag is already present then the dry run should fail if
the tag is already present
What do you guys think? If these points are considered valid I will open a
ticket at least for the second one, which is the worse of the two
Alejandro Endo | Software Designer/Concepteur de
Ok, I might give that a try
Thank you for your help Ron
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Ron Wheeler rwhee...@artifact-software.com
To: users@maven.apache.org,
Date: 2014-11-25 09:39 PM
Subject:Re: Maven use for integration
On 25/11/2014
, are there any other tools that
leverage pom information to download artifacts from a maven repo? i don't
want to have to maintain that dependency information in two different
places
Thank you,
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential
by the dependency plugin just because the POM already contains the
relationship information
I hope everything is clearer now, let me know
Thanks for replying
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Ron Wheeler rwhee...@artifact-software.com
To: users@maven.apache.org
option would be a maven-plugin that creates its own dependency
graph and doesn't rely on the one provided by maven core, which supports
only a single version of a given artifact (at least that's what it looks
like)
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Ron Wheeler
Mark, we are using maven 3.0.4 and encounter the same issue, it must have
been introduced before
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Mark Derricutt m...@talios.com
To: Maven Users List users@maven.apache.org,
Date: 2014-10-27 17:50
Subject:Re
That's what we figured...
we were trying to not pollute our hundreds of poms with the exact same
declaration of the scm
Thank you Robert
Alejandro Endo | Software Designer/Concepteur de logiciels
Grass Valley, A Belden Brand | Tel: (514) 333-1772 Ext: 3789
3499 Douglas-B.-Floreani, St-Laurent
-with-git
) having the same issue but none of the workarounds I tried work.
Is there an official fix or workaround for this?
we're using maven 3.0.4 and m-release-p 2.5.1
Thank you,
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information may
I've been tracking this bug for a while now
Still no progress
You can track it here. There is a workaround there that i haven't tried
Let us know if you try it and whether it works
https://jira.codehaus.org/browse/MRELEASE-875
Alejandro Endo | Software Designer/Concepteur de logiciels
i do have the latest m-release-p, but the git version i don't know how to
set that nor what it currently is. How can i check that?
Thank you Martin
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Martin Gainty mgai...@hotmail.com
To: users@maven.apache.org users
solved this issue with the DRY principle across behaviour
and build system?
The short background is that maven generates an XML schema via jaxb and
this schema file is then made available at runtime via a service
Thank you,
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER
SchemaProviderServiceImpl
so I can't grab it from the manifest at runtime. I guess the way I phrased
it in the original email implied the opposite, sorry about that
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Curtis Rueden ctrue...@wisc.edu
To: Maven Users List
only at
deploy time or early on so the snapshot-to-release changes in the pom done
by the release-plugin would happen in the flattened version
Anyone knows?
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Jörg Hohwiller jo...@j-hohwiller.de
To: annou...@mojo.codehaus.org
dependencies only while using the snapshot dependencies from the workspace
Thank you
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use
-versions without success
Any idea how to do this? I just want to change the dependencies (which are
currently SNAPSHOT due to the m-release-p) to the latest released versions
Thank you,
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information
, but
if that RC-1 happens to be released, then all your poms will be depending
on the SNAPSHOT of an RC-2 that will never be made so you have to
downgrade your dependency versions
Am I doing something out of the ordinary here?
Alejandro Endo | Software Designer/Concepteur de logiciels
From
I didn't. QA is not happy about rebuilding the system once it's been
approved so we have to release the RC as approved.
So all our versions are always RC-X-SNAPSHOT or RC-X
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Stephen Connolly stephen.alan.conno...@gmail.com
If you do open a ticket, please let me/us know. I will +1 it. I am also
interested in this feature
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Anders Hammar and...@hammar.net
To: Maven Users List users@maven.apache.org,
Date: 2014-01-15 02:47 PM
Subject
you,
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use or deliver this message to anyone. In such event, you
should destroy
signed only once. whereas i just want
to remove any existing signature
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Alejandro Endo/MontrealMIR/BeldenCDT
To: users@maven.apache.org,
Date: 2014-01-06 03:58 PM
Subject:Maven Jarsigner plugin vs Apache Maven Shared
without properties in each
child pom like this
configuration
outputDirectory${basedir}/../target/outputDirectory
/configuration
Did I misunderstand your comment about overriding the property in every
child?
Thanks again,
Alejandro Endo | Software Designer/Concepteur de logiciels
From
Another workaround if you want to do this only for projects in your
current reactor and it is done sporadically + not programatically would be
to use the maven-graph-plugin. From the image you will see the incoming
arrows.
Just an extra idea...
Alejandro Endo | Software Designer/Concepteur de
/configuration
i.e. the children end up using their own output folder like maven does by
default. Is there any way to anchor that property to be resolved to the
build directory of the pom where it is defined (the parent pom) and not
where it is accessed?
Alejandro Endo | Software Designer/Concepteur de
, is that really the case? in this case i am still building an
application, just not by compiling code but by integrating multiple jars
Any thoughts?
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you
issue or am I doing something wrong?
Let me know if someone needs more details
Thank you,
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may
it just fail the build as
soon as it detects a version mismatch? i've never seen a similar behaviour
in maven where you ask it to do something (deploy), it doesn't do it, but
finishes successfully
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Robert Scholte rfscho
with any recent
eclipse) and do a File import maven Existing Maven project if your
project is already in the filesystem. If not choose checkout maven
project from SCM instead
good luck
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Jennifer Vendetti vende...@stanford.edu
, but i don't
see the connection
good luck,
Alejandro Endo | Software Designer/Concepteur de logiciels
Miranda Technologies is a brand of Belden Inc.
From: Jennifer Vendetti vende...@stanford.edu
To: Maven Users List users@maven.apache.org,
Date: 2013-10-23 04:20 PM
Subject:Re
the SNAPSHOT and use the version
that's left (3.0.0-SNAPSHOT - 3.0.0), or even better, allow to replace the
SNAPSHOT qualifier with another specified qualifier, e.g. 3.0.0-SNAPSHOT -
3.0.0-RC-1
Alternative solutions are also welcomed
thank you
Alejandro Endo | Software Designer/Concepteur de
This is exactly what I needed a couple of weeks ago. I came up with the
same procedure but discovered that the versions plugin doesn't support
unresolving ranges. Is this something that's in the works or it's just
something you wish were there?
Alejandro Endo | Software Designer/Concepteur de
I'm trying to release a multimodule maven project cloned in github. My
project has the parent pom as a submodule of the root aggregator. if i run the
release in dryRun mode it works fine, however if I run it for real this is
what i get near the end
...
[INFO] Checking in modified
Thank you Robert
I tried MRP 2.3.2 and i got the exact same result. I also have the same setup
referenced in the OP's comment on the accepted answer (aggregator inherits from
parent, parent is a submodule of aggregator and actual code modules depend on
their sibling parent) but somehow it
from the root of the project, which is the same level as the aggregator pom.
But instead of putting the scm section there like you suggest, I just made the
aggregator inherit from its submodule (jrobocom-parent). Maybe this is what's
confusing the release plugin. i will try duplicating the SCM
There seem to be some differences to my case. The bug says It seems to think
for some reason that I am at the root of my scm tree. In my case i AM in the
root of my scm tree. Also, in his problem, the build fails on the git commit.
in my case it fails on the git push after the commit succeeds.
Ok, removing the dependency to the parent in the aggregator seemed to fix the
problem. now the push url makes sense:
git push https://github.com/theHilikus/JRoboCom.git master:master
However, now I encounter a problem i've always had in the past when releasing
and never bothered to
Hopefully someone else will complement this info
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Richard Sand rs...@idfconnect.com
To: 'Maven Users List' users@maven.apache.org,
Date: 2013-07-15 01:09 PM
Subject:introducing maven-proguard-plugin
Hi all
be soon
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Tang Kin Chuen kct...@big2.net
To: users@maven.apache.org,
Date: 2013-07-04 09:42
Subject:Filter dependencies based on OSGi bundle detection during
assembly
Hi,
I am creating a Maven assembly
bind it to package for example, your plugin will be executed
when you run mvn package
Alejandro Endo | Software Designer/Concepteur de logiciels
From: alesky alessandro.dotta...@gmail.com
To: users@maven.apache.org,
Date: 04/06/2013 01:17 PM
Subject:Re: Call a custom plugin
the changing digit is just an RC
counter, then it will change relatively often right before a release
Then add to all that a CI server, which increases the requirement of a
non-interactive scheme.
Any guidelines for this (seemingly) common scenario?
Alejandro Endo | Software Designer/Concepteur
the timeout
at 20s, will it fail the tests because the combined time is 20s or as
long as one single test doesn't go over 20s they will all pass?
Thank you
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message
to suggest a completely different (correct?) way to do
this
Thank you,
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use
What about just a simple symlink (mvn -- mvn3) on your own account? you
don't need any system (root) permission, you create it yourself in your
account in one of your folders in your PATH
Alejandro Endo | Software Designer/Concepteur de logiciels
From: José Manuel Castroagudín Silva
is there anyway
http://stackoverflow.com/questions/1625492/execute-maven-plugin-goal-on-child-modules-but-not-on-parent
Alejandro Endo | Software Designer/Concepteur de logiciels
From: laredotornado-3 laredotorn...@gmail.com
To: users@maven.apache.org,
Date: 02/04/2013 02:07 PM
Subject
Latest maven and maven-dependency-tree 2.0
Maybe we are talking about different interfaces
org.apache.maven.shared.dependency.graph.DependencyNode.getArtifact()
returns a org.apache.maven.artifact.Artifact, which does not have a
getProperties() method
Am I missing something?
Thank you,
i do something similar to fix a bug in nexus
(https://issues.sonatype.org/browse/NEXUS-5525)
since it is a jenkins build, i just trigger a scheduled (manual) task to
reindex the repo on build finish.
The command i use to trigger it is
/usr/bin/wget --user=something --password=my-pass
I have a plugin that uses DependencyGraphBuilder to find the dependencies
of a MavenProject. Traversing the graph I get a DependencyNode , however, I
need to access a particular maven property of the dependency's pom and this
is not possible AFAIK. Is this true? is it really not possible to
I have a problem where my maven plugin's unit tests fail ONLY when i run
them in jenkins. When i run `mvn test` locally everything passes fine
The error i get is
Tests in error:
testGetMyModules(com.example.AnalyzerTest): (class:
org/apache/maven/project/MavenProject, method:
I'm writing a plugin that needs to combine a bunch of artifacts into a zip
and create an XML file of it. I am currently working on creating the XML,
for the rest i use the assembly plugin. To generate the XML i need a way
(an api) to traverse the graph of maven dependencies
Here is a normal
Hello everyone,
I'm using maven-assembly-plugin to generate a zip package with some
artifacts in it. It works fine, now the only missing step is I need to
generate an XML file with some information about the artifacts. This XML
will be used by another program to basically know about the
52 matches
Mail list logo
