-
Von: Barrie Treloar [mailto:baerr...@gmail.com]
Gesendet: Donnerstag, 14. Juli 2011 01:35
An: Maven Users List; joerg.schai...@gmx.de
Betreff: Re: AW: Locking down default plugin versions
On Thu, Jul 14, 2011 at 1:27 AM, Jörg Schaible joerg.schai...@gmx.de wrote:
Moser, Christian wrote
We wrote a custom enforcer rule for maven-enforcer-plugin to check whether
there is a newer revisions while maven was in install lifecycle (deploy
lifecycle is to late to enforce, already deployed..). It wasn't that difficult
but very helpful, it was really worth the work.
You could for example
I start a release build with following cmd:
Mvn -Darguments=-DskipTests=true -Denforcer.skip=true
-Dmaven.javadoc.skip=${skipJavadoc} -Dtag=${tag}
-Dmaven.javadoc.skip=${skipJavadoc} -Dgoals=deploy release:perform
With maven-release-plugin:2.1:perform, maven 3.0.1 will print out:
14:32
An: Maven Users List
Betreff: Re: Locking down default plugin versions
On Wed, Jul 13, 2011 at 8:59 PM, Moser, Christian c...@metrohm.com wrote:
I'm skipping javadoc, do you know why javadoc-plugin is needed?
Skipping a plugin isn't a built-in maven feature.
Each plugin decides
Hi,
We are using subversion 1.6 as SCM.
Is it possible to lock files during a release with maven release plugin
?
I tried -DuseEditMode=true to lock the project files during goal
:prepare and :perform with no luck, I was still able to commit into the
trunk while the plugin was at work
Hi,
We're using Maven 3.0.1 with Hudson 1.380 with a free style job and artifactory
2.3.1 as repo manager.
We experienced that maven 3 would hang for several hours / or days (we) if we
restart our artifactory server while a hudson was running. It seems like
there's no timeout to break
Hi, I would be interested to test your plugin because it would really simplify
our test environment.
We were facing simular classpath problems and were forced to copy the needed
artifacts by maven-dependency-plugin to the Fitnesse server classpath
directory. We were then be able
to execute
..takes quite some time to build it ( 30-40 minutes ), which I need to
do every morning after an svn update.
I'm not sure why do you think that it's necessary to build the whole project
locally every morning? After a commit, a maven project should be deployed as
SNAPSHOT version into the remote
I'm currently developing a maven enforcer rule.
How can I get object references to all modules of a parent pom ?
I'm currently developing a custom enforcer rule.
How can I get object references to all modules of a parent pom ?
final ListString modulesRelativePath = parentProject.getModules();
delivers only the relative path to the project pom. I need something
like :
final ListMavenProject
According to the documentation:
http://maven.apache.org/plugins/maven-release-plugin/examples/lock-files
.html
Am I right in assuming that I'd be able to lock files during a release
with:
release:prepare -DuseEditMode=true
so that nobody could commit files/directories during the
Hello
I'm using maven 3.0.1
I got following ouput everytime I've built a child project. The missing
dependencies are declared in the parent project. The curious thing is
that the build never fails and the [WARNING] messages are displayed at
the end of the build. Futhermore are all of those
with
the Artifactory web-interface?
-Chris
-Ursprüngliche Nachricht-
Von: Wendy Smoak [mailto:wsm...@gmail.com]
Gesendet: Donnerstag, 16. Dezember 2010 15:03
An: Maven Users List
Betreff: Re: no dependency information available
On Thu, Dec 16, 2010 at 8:58 AM, Moser, Christian c...@metrohm.com
I've fixed the problem with the missing checksums in artifactory, I was able to
generate them with admin rights.
The problem with the missing pom still remains, it seems this is a maven 3.0.1
bug..
-Ursprüngliche Nachricht-
Von: Moser, Christian [mailto:c...@metrohm.com]
Gesendet
be a problem with either Maven or Artifactory. However, I
do vaguely recall seeing a ticket regarding something similar to this.
Couldn't find it in jira when I searched though.
/Anders
On Tue, Nov 30, 2010 at 08:25, Moser, Christian c...@metrohm.com wrote:
Hi
Maven 3.0.1 and artifactory 2.3.1
-DoverWriteSnapshots=true
-DoverWriteReleases=true
solved the problem :-)
-Ursprüngliche Nachricht-
Von: Moser, Christian [mailto:c...@metrohm.com]
Gesendet: Dienstag, 30. November 2010 09:38
An: Maven Users List
Betreff: AW: maven 3.0.1 doesn't download sources
Thanks for your
Hi
Maven 3.0.1 and artifactory 2.3.1 with unique (non-unique won't work)
snapshot repository doesn't UPDATE sources from the repository. Calling
mvn -U dependency:sources with an empty local repository will resolve
all sources correctly. After a newer artifact was deployed and the maven
was
Don't use ranges at all, sooner or later they will lead to ugly problems..
I would recommend to use the maven version plugin with or without properties as
version placeholder.
http://mojo.codehaus.org/versions-maven-plugin/examples/display-dependency-updates.html
AM, Moser, Christian c...@metrohm.com wrote:
I'm unable to download the newest artifacts (compiled jar) with maven
3.0 and 3.0.1-RC1 from cmd line. The artifacts were deployed to
artifactory 2.3.1.
After calling mvn -U on a dependend artifact, maven just updates the
metadata, but doesn't
CM's.
-Patrick
On Tue, Nov 23, 2010 at 9:43 AM, Moser, Christian c...@metrohm.com wrote:
I'm unable to download the newest artifacts (compiled jar) with maven
3.0 and 3.0.1-RC1 from cmd line. The artifacts were deployed to
artifactory 2.3.1.
After calling mvn -U on a dependend
side, better ask on the Artifactory
user list and we'll be happy to assist you there.
Thanks,
On Wed, Nov 24, 2010 at 8:34 AM, Moser, Christian c...@metrohm.com wrote:
I could imagine the culprit could be artifactory. We were forced to update
from 2.2.2 to 2.2.3, otherwise we weren't be able
I wonder in which specific time/timezone maven 3.0 writes the timestamp
into maven-metadata for local and remote artifacts? Is it supposed to
write GMT + 0:0 or the same time set on the local machine, in my case
GMT + 1:0? There could be a problem because recently I had a different
timestamp in
I'm unable to download artifact sources with maven 3.0 and 3.0.1-RC1
with following command.
Sources classifier is: -sources (default)
mvn -U validate dependency:sources -DoverWriteSnapshots=true
-DoverWriteReleases=true
the artifacts with classifier -sources are available in the
the maven metadata my not be letting maven 3 find
the artifacts.
IIRC Maven 3 pays more attention to the metadata, whereas Maven 2 might not
trust it as much (but I could be wrong, my recollection is fuzzy)
-Stephen
On 23 November 2010 12:13, Moser, Christian c...@metrohm.com wrote:
I'm unable
I'm unable to download the newest artifacts (compiled jar) with maven
3.0 and 3.0.1-RC1 from cmd line. The artifacts were deployed to
artifactory 2.3.1.
After calling mvn -U on a dependend artifact, maven just updates the
metadata, but doesn't override the old artifacts contained in the local
it should be but I think we may have found a possible
culpret.
Check with Benjamin Bentmann, he'd know what m3 is supposed to do
-Stephen
On 23 November 2010 14:30, Moser, Christian c...@metrohm.com wrote:
They are from snapshot artifacts. We use non-unique snapshots in
artifactory
2010/11/11 Moser, Christian c...@metrohm.com:
I've got the following problem with maven 3.0 and artifactory 2.2.3 (2.2.1
won't let maven 3.0 deploy without legacy-mode flag -- metadata problem).
A quick look in the maven output shows that at the beginning of the build
maven downloads an old
I've got the following problem with maven 3.0 and artifactory 2.2.3 (2.2.1
won't let maven 3.0 deploy without legacy-mode flag -- metadata problem).
Project A depends on Project B. I created a new class in Project B and
installed it into my local repository so I can use the class in project A.
I've got following effect with the maven versions plugin 1.2.
If we release a milestone of our software, we declare the components
which are included in the milestone with [version]-[unrel]-[revision].
When the software is in the release process, we remove the additional
declaration. For
[mailto:stephen.alan.conno...@gmail.com]
Gesendet: Donnerstag, 21. Oktober 2010 13:14
An: Maven Users List
Betreff: Re: maven-versions-plugin version comparism
Did you read the FAQ?
http://mojo.codehaus.org/versions-maven-plugin/faq.html#comparisonMethod
On 21 October 2010 11:56, Moser, Christian c...@metrohm.com wrote
Is it possible to call a custom enforcer rule at first in lifecycle
phase deploy. I know I could create a custom lifecycle, but this is a
bit of an overhead for this problem, though..
The rule should prevent changes being deployed to the artifactory if
there are newer versions in the scm
I've got a multi-module project build and release it with the release
plugin. After executing release:prepare release:perform, the project
poms have changed to -SNAPSHOT and the release version of the projects
is correct deployed. Why does the plugin only deploy the release
versions in the
, Moser, Christian c...@metrohm.com wrote:
Why does the plugin only deploy the release
versions in the release:perform goal and doesn't deploy the -SNAPSHOT
project pom after the release, too? Is there a possibility to do so?
I don't think it's a job for the release plugin, but all you have
subsystem automation
Did you try the release plugin?
-Original Message-
From: Moser, Christian [mailto:c...@metrohm.com]
Sent: Thursday, April 08, 2010 11:25 AM
To: Maven Users List
Subject: Maven subsystem automation
I am currently working on subsystem automation. I've got
I am currently working on subsystem automation. I've got following
situation: http://www.christian-moser.ch/fx/subsystems_v2.pdf
e.g. depmgmt-x contains all dependencies of a subsystem and exist only
once (there are two just for illustration in the diagram). As a release
version, it holds all
a release or dev (SNAPSHOT).
/Anders
On Tue, Feb 16, 2010 at 08:44, Moser, Christian c...@metrohm.com wrote:
Thanks a lot for your fast response!
The file can be found here:
http://www.christian-moser.ch/fx/subsystems.pdf
Yes im using depmgmt poms with import. Every of the five subsystems
you'll have different version of this pom, but it's still just one
import pom (artifact). The version will determine if it's a released version
of the dep mgmt set or a dev version (SNAPSHOT).
/Anders
On Tue, Feb 16, 2010 at 10:51, Moser, Christian c...@metrohm.com wrote:
Every component
that, it is always possible to override in a childs dependencies
section.
/Anders
On Tue, Feb 16, 2010 at 14:26, Moser, Christian c...@metrohm.com wrote:
Ok I agree with your solution, it will make it less complicated and more
maintainable.
Ok if I go ahead and add depmgmt-x:1.0.0
:58, Moser, Christian c...@metrohm.com wrote:
I think you misunderstood me. I won't put dependency depmgmt-x into the
parent of Z(what would be mnet-parent). I will put it into component Z.
-Ursprüngliche Nachricht-
Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im
We've trouble creating a concept for maven using subsystems.
In the attached pdf you can see a maven/subsystem concept. In short,
we've got a component based software which is based on quiet a lot of
components (each component is a maven project). Those components are
bundled in subsystems.
, Moser, Christian c...@metrohm.com wrote:
We've trouble creating a concept for maven using subsystems.
In the attached pdf you can see a maven/subsystem concept. In short, we've
got a component based software which is based on quiet a lot of components
(each component is a maven project
41 matches
Mail list logo
