The Maven team is pleased to announce the release of the Maven WAR
Plugin, version 2.0 beta-7.
http://maven.apache.org/plugins/maven-release-plugin
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-7
** Bug
* [MRELEASE-124] - Impossible to depend on a deployed snapshot
*
The Apache Maven team would like to announce the availability of Maven
2.0.8. We closed out 32 issues and no major issues upgrading are
expected.
There is one slight change to be aware of, the test-classes folder is
now before the classes in the classpath to allow test resources to
override
The mojo team is pleased to announce the release of the
Ounce-Maven-Plugin 1.0. Ounce is a code security scanning tool
produced by OunceLabs. The ounce plugin enables integration with Maven
and automatic creation of Ounce application and project files as well
as on demand scanning and site report
The Maven team is pleased to announce the 2.0 release of the Maven
Dependency Plugin:
http://maven.apache.org/plugins/maven-dependency-plugin
This release fixes many issues and introduces several new goals for
dependency analysis and output.
Release Notes - Maven 2.x Dependency Plugin - Version
The Maven team would like to announce the release of Maven Archetype
2.0-alpha-2. This release corrected backwards compatibility with the
1.0 version and a few windows issues. The site has also been updated
and deployed: http://maven.apache.org/plugins/maven-archetype-plugin
Release Notes - Maven
The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.4.
NOTE: This release has many fixes, but most notably is MJAVADOC-137, which
reverses the aggregation introduced in 2.3. This can and has caused many
issues during releases because the javadoc is included
The Maven team is pleased to announce the release of the Maven
Dependency Plugin, version 2.0-alpha-3
http://maven.apache.org/plugins/maven-dependency-plugin/
The dependency plugin provides the capability to manipulate artifacts.
It can copy and/or unpack artifacts from local or remote
The Maven team is pleased to announce the release of the Maven
Dependency Plugin, version 2.0-alpha-4
http://maven.apache.org/plugins/maven-dependency-plugin/
The dependency plugin provides the capability to manipulate artifacts.
It can copy and/or unpack artifacts from local or remote
We are pleased to announce the first release of the maven-enforcer-plugin.
The Enforcer plugin provides goals to detect and enforce certain
environmental constraints such as Maven Version, JDK version, and OS
family/version/architecture. Additionally, the Enforcer can execute
custom rules
This is a minor release with just one fix:
Release Notes - Maven 2.x Enforcer Plugin - Version 1.0-alpha-2
** Bug
* [MENFORCER-1] - plugin fails on jdk 1.5
--The Maven Team.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
We are pleased to announce the third release of the maven-enforcer-plugin.
The Enforcer plugin provides goals to detect and enforce certain
environmental constraints such as Maven Version, JDK version, and OS
family/version/architecture. Additionally, the Enforcer can execute
custom rules
The Maven Team is pleased to announce the release of maven-eclipse-plugin 2.4:
Release Notes - Maven 2.x Eclipse Plugin - Version 2.4:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001styleName
=HtmlprojectId=11133Create=Create
** Bug
* [MECLIPSE-108] - .wtpmodules with version
The Maven team is pleased to announce the release of the Maven Plugin Tools,
version 2.4.1
This release fixes 3 critical issues discovered in the 2.4 release. We
recommend everyone upgrade from 2.4 to 2.4.1.
The Maven Plugin Tools contains the necessary tools to be able to produce
Maven Plugins
The reporting implementation is used to render site reports. This release
fixes an incompatibility with newer doxia implementations.
This has just one change from 2.0.4:
http://jira.codehaus.org/browse/MNG-3476
--The Maven Team
The Apache Maven team would like to announce the availability of Maven
2.0.9.
This release went through a new process that saw 8 release candidates tested
by the user community before the final release and we expect it to be more
robust than previous versions. There are several important fixes
For nexus we recommend making a group and using a mirror of *
Both of those artifacts should be in central
--Brian
On May 10, 2008, at 1:52 AM, oliver.maven [EMAIL PROTECTED]
wrote:
hi,
i am using nexus indexer,i found i cant download the
1)
How are you using these properties? A copy of your PIM would help.
Maven shouldn't hang, especially on an undefined property... It just
goes through un-interpolated
--Brian
On May 14, 2008, at 1:44 PM, EJ Ciramella [EMAIL PROTECTED]
wrote:
A colleague and I have found some strange
You can also use -Dsurefile.useFile=false to output the error to
stdout. I do this in Hudson also so that the emails contain the error.
--Brian
On May 14, 2008, at 12:39 PM, Adam Hardy [EMAIL PROTECTED]
wrote:
Wayne Fay on 14/05/08 16:03, wrote:
I am using surefire to run our unit
There appear to be no mismatches in the depmgt section, which is the
part of the tool focused on the 2.0.5 upgrade.
There are some other dependency issues you can deal with
separately..there is an explaination in chapter 8: http://www.sonatype.com/book
Sent from my iPhone
On May 28, 2008,
Yes, the other part is clean
Sent from my iPhone
On May 28, 2008, at 11:22 AM, Michael Delaney
[EMAIL PROTECTED] wrote:
I was basing my findings on the output where Maven stated Potential
problems discovered. Is Maven just referring to the Used undeclared
dependencies and Unused declared
Hi Chris,
You want the maven-assembly and maven-dependency to do this. I wrote about
it with examples[1]:
You can probably unpack directly to your target folder rather than filtering
as is shown in the example.
--Brian
[1] http://blogs.sonatype.com/brian/2008/04/17/120848550.html
On Thu, Jun
There is also the exec-maven-plugin
--Brian
On Jul 7, 2008, at 7:13 PM, Kathryn Huxtable [EMAIL PROTECTED]
wrote:
On Jul 7, 2008, at 5:34 PM, Ken Liu wrote:
Is there any easy way to have maven generate a cmd or bat file with
the java
command line populated with the classpath from the
As I said before, this was done by infra with no notice to us. The new
policy of purging is theirs, not ours. See the infra archives if you
would like to read about it.
On Aug 5, 2008, at 10:45 PM, Patrick Moore [EMAIL PROTECTED]
wrote:
Of course this means that the maven team is
Hi, I blogged about this with examples. I can't copy and paste on the
iPhone but you can find it at http://blogs.Sonatype.com/brian
Sent from my iPhone
On Aug 23, 2008, at 8:08 AM, Graham Leggett [EMAIL PROTECTED] wrote:
Hi all,
I have a need to override a specific dependency used by the
It is this goal in the dependency plugin, but in general when working
with multimodule builds, you should just do install. Other plugins can
have the same problems.
Sent from my iPhone
On Sep 12, 2008, at 10:10 PM, Build Guy [EMAIL PROTECTED] wrote:
well, the whole point is that... If
The Maven team is pleased to announce the release of the Maven
Enforcer Plugin, version 1.0-alpha-4
The Enforcer plugin provides goals to control certain environmental
constraints such as Maven version, JDK version and OS family along
with many more standard rules and user created rules.
=Create
And I've staged RC-2 here:
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.10-RC2/
Please try it out and see if we have any remaining regressions over 2.0.9.
Thanks,
Brian
--
Brian Fox
Apache Maven PMC
http
Do a clean install after changing the pom since the target folder
would already have a copy of the previous version.
--Brian (mobile)
On Nov 12, 2008, at 9:52 AM, Troy Bull [EMAIL PROTECTED] wrote:
Greetings
I am brand new to maven and I have just noticed an issue.
I have a jar file that
=10500Create=Create
And I've staged RC-3 here:
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.10-RC3/
Please try it out and see if we have any remaining regressions over 2.0.9.
Thanks,
Brian
--
Brian Fox
Apache Maven PMC
http
You can use the maven-dependency-plugin:build-classpath goal
--Brian (mobile)
On Nov 29, 2008, at 11:28 AM, Stephan Niedermeier [EMAIL PROTECTED]
wrote:
Hi,
I'm using Maven2 to build and assemble my project under Win XP.
The project contains a Java launcher. This launcher needs to know
You could save youself a lot of hassle with a repo manager. You
shouldn't use local repos as remote repos because the metadata is
different. Also with unmanaged repos, snapshot accumulation will
become a problem.
--Brian (mobile)
On Nov 29, 2008, at 5:33 AM, Alex Athanasopoulos [EMAIL
). Is there a way to make this path relatively to, let's
say lib/ of the assembled folder?
Thanks a lot.
Regards
Stephan
Brian Fox schrieb:
You can use the maven-dependency-plugin:build-classpath goal
--Brian (mobile)
On Nov 29, 2008, at 11:28 AM, Stephan Niedermeier [EMAIL PROTECTED]
wrote
Niedermeier schrieb:
Hi Brian,
thanks for the hint, but it seems that the build-classpath goal
calculates the full path to the jars (e.g. C:/project/lib/
myJar.jar). Is there a way to make this path relatively to, let's
say lib/ of the assembled folder?
Thanks a lot.
Regards
Stephan
Brian
Use the build-helper plugin
--Brian (mobile)
On Dec 4, 2008, at 8:25 AM, Sommers, Elizabeth [EMAIL PROTECTED]
wrote:
Is there anyway to attach an artifact without writing a mojo to do it?
I would like to just do it with the pom if possible.
Liz Sommers
[EMAIL PROTECTED]
We use the assembly plugin to put the nexus bundle together. I have a
Plugin mostly written that can do it also but it's focused on using
plexus and jsw in the bundle.
--Brian (mobile)
On Dec 4, 2008, at 5:20 PM, Siegfried Goeschl [EMAIL PROTECTED]
wrote:
Hi Stephan,
I doubt there is
Trying to download all 70gb from central will likely get you banned.
Instead use a repository manager and let it cache the things you
actually need.
--Brian (mobile)
On Dec 5, 2008, at 4:24 AM, prasanna.goupal [EMAIL PROTECTED]
wrote:
Hi All,
Is there any way to download complete
Yes it's right but make sure you have enabled snapshots for the repo
in question. By default only releases are enabled for repos
--Brian (mobile)
On Dec 10, 2008, at 4:19 PM, Todd Thiessen [EMAIL PROTECTED]
wrote:
If I deploy a SNAPSHOT version of a parent POM, POMs that reference it
do
Yes we do have a tool for this
--Brian (mobile)
On Dec 24, 2008, at 3:55 PM, John Stoneham ly...@lyrically.net
wrote:
On Wed, Dec 24, 2008 at 9:20 AM, Alex Athanasopoulos
alex.a.athens...@gmail.com wrote:
Is there a way to convert a local repository into a remote
repository, or
should
The Maven team is pleased to announce the release of the Maven
Dependency Plugin, version 2.1
This plugin is used to copy and unpack artifacts and dependencies. It
also provides visualization and optimization tools for your project
dependencies.
The Maven team is pleased to announce the release of the Maven
Clean Plugin, version 2.3
This plugin is used to delete artifacts to provide a clean build.
http://maven.apache.org/plugins/maven-clean-plugin/
You should specify the version in your project's plugin configuration:
plugin
The Maven team is pleased to announce the release of the Maven 2.0.10
This is a stable bug fix release and you can see the full list of
issues fixed at
http://maven.apache.org/release-notes.html
Enjoy,
-The Maven team
-
To
The Maven team is pleased to announce the release of the Maven
Enforcer Plugin, version 1.0-beta-1
The Enforcer plugin is used to fail a build if certain constraints are
not met. There are too many standard rules to describe here, but check
out the site for more details:
Hello,
We have our CI system setup to build after every commit for verification. It
happens to build on a grid with multiple
OS's and one of them deploys a snapshot to our Nexus repo. Our QA grabs the
latest snapshot of the application at
various times and validates the fixes against it. (they
1. How to distinguish snapshot build versions correctly? So that one
snapshot build would not overwrite previous one in the repository.
You don't, that's not the purpose. If you truly care about a particular
snapshot version, then it should have been a
release. It's meant only for looking at the
So your formal releases are produced by manually running the release
plugin? And if it fails, you manually do a rollback, depending on the
failure?
Yes, we manually roll it back. It's not too bad with svn, but a bit annoying
I'll admit. We haven't tackled the release
tools yet.
Some of our
Regarding snapshots and the way your QA works it all looks like you have
adjusted your team workflow to the features the maven tool provides.
Yes, this comes from years of using the tool, but is also adapted to our
current environment.
And
these features are not so flexible to cover all
The -D doesn't change the settings, -s does. This most likely only
overrides the user settings file, but the global one in the maven
install /conf folder would still be referenced if it exists.
Jim McCaskey wrote:
Hello all,
I'm having some trouble tracking down how the precedence works for
Whenever you see Maven making requests for -SNAPSHOT (and you don't have
it configured with useUnique = false) it always means that the
maven-metadata.xml file for that snapshot is wrong or couldn't be found.
It's hard to say why that could have happened, but this often happens if
you do a
That alpha copy is a very, very old version and is not even close to
what was printed (which is by now old). The latest and greatest is
published regularly here:
http://www.sonatype.com/products/maven/documentation/book-defguide
javidjamae wrote:
There is an alpha copy of The Definitive Guide
Take a look at the dependency plugin source. There are filters to get
the correct scope.
Gert Vanthienen wrote:
L.S.,
I'm writing a plugin and would like to get a list of artifacts for the
provided dependencies (including transitive dependencies) for the project.
How can I get this? I was
Please file a jira for this and use 2.1.0 as the affects version so we
can get it fixed in 2.1.1
edward eric pedersson wrote:
Hi
We use the command line to pass on system properties to the java
virtual machine when running our Hudson builds on a Linux box. It used
to work quite well in 2.0.9
This could only happen in two passes of the plugin without a clean in
between. The two files are indeed the same version, but it isn't
checking the target folder exhaustively to see if there's a file there
with another timestamped version...the overwrite only gets triggered if
the exact same
It does not support transitivity yet. You can use copy-dependencies and
combinations of the filters to get the artifacts you need
Chris Burroughs wrote:
I assumed from the frequent references to transitive dependencies at
http://maven.apache.org/plugins/maven-dependency-plugin/index.html
that
Besides starting from scratch? No. Maven 1.x is dead for all intents and
purposes.
Michael K. Craghead wrote:
It hasn't gone that far...So should I to assume from the responses that there
is no good or easy way to convert to Maven 1?
Michael K. Craghead
That's why we suggest locking down your plugin versions in your poms.
Then you'll have controll over which ones you get as snapshots.
See here for more info:
http://www.sonatype.com/people/2008/04/maven-209-released/
The eclipse plugin does not seem to be one that has a default in the
super
I don't see anything obvious. Can you attach some build logs? The dep
plugin is pretty verbose about what it's doing so it should hopefully be
obvious.
On 4/23/2009 10:54 PM, Davis Ford wrote:
Hi Brian -- I'm trying to emulate your blog:
Not really, however Maven will do this automatically for projects in the
same reactor if at least the compile phase is executed.
On 4/26/2009 2:18 PM, Lee Mighdoll wrote:
I'd like to specify a directory of .class files instead of a jar with
systemPath. Is there any way to do this?
1) It
Check that you don't have a proxy blocking you.
On 4/26/2009 11:15 AM, pjotr wrote:
Hi,
I am not able to get maven-install-plugin (when executing 'mvn
install' command)- getting the following error:
[INFO]task-segment: [install]
[INFO]
See the 9th bullet point here:
http://www.sonatype.com/people/2009/04/summary-of-maven-how-tos/
On 4/26/2009 3:17 PM, Olivier Cailloux wrote:
Hello list,
I am new to maven and couldn't find a simple and elegant solution to
this (probably) common problem.
I have three projects : A and B are
in Maven and I think there must be
somehow a simple solution to my needs which I simply overlooked. I am
wondering how the others do as this must be a very common problem
(everybody use logging framework!).
Also, sorry for my English...
Olivier
Brian Fox a écrit :
See the 9th bullet point
Thanks for finding that. It's been fixed now.
The old repo had some junk versions that were being proxied. It's been
cleaned out.
We schedule daily cleanups of the snapshots, leaving behind 3 copies
for a minimum of 10 days, the snapshots are removed when a release is
published.
You are correct. If someone is able to read the maven code and find the
default password, decrypt the master password, then they could decrypt
the user password. It's also decrypted on the wire if you aren't using
https with your repos. The trick with a build server is to make a
special
Check what command the release plugin is invoking during the perform goal.
It's checking out the code to target/checkout and then forks another maven
execution in that folder. This is the one that's failing for you.
On Wed, May 6, 2009 at 3:18 AM, Mark Derricutt m...@talios.com wrote:
Looks
It will resolve the conflicts, but here no conflict exists from Maven's
point of view. The groupid is part of the coordinates so they appear to be
the same. Jdom should insert a relocation pom to solve these issues. Your
recourse is to use an exclusion.
Assuming the group was the same, you would
take a look at dependency:build-classpath
On Thu, May 7, 2009 at 3:11 AM, James Crawford james.crawf...@distra.comwrote:
Hi,
I need to be able to get access to the runtime class path
in my tests when invoked from the maven-surefire-plugin.
I can set system properties for the surefire
set MAVEN_OPTS = -Xmx512m for example. It can't be done directly from the
cli.
On Thu, May 7, 2009 at 1:39 AM, shrimpywu imx...@gmail.com wrote:
Before i run my program like this
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
I think this will help you understand it better:
Think of inheritance as including the contents of the parents inside your
own pom. (obviously merging occurs). I used to be a C programmer so I refer
to this as #include-ing the contents.
Therefore the result of inheritance is that it updates your
I wonder if it's waiting for some password input. Make sure you have a
server setting with the proper credentials for scp.
On Tue, May 5, 2009 at 6:33 PM, Harper, Brad brad.har...@fiserv.com wrote:
While performing a deployment from the release plugin, I see
[INFO] [INFO] [install:install]
I covered some strategies in this area here[1] and there are some other
how-tos here[2]
[1]
http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/
[2] http://www.sonatype.com/people/2009/04/summary-of-maven-how-tos/
On Mon, May 4, 2009 at 12:10
Yeah, someone else was looking for this too. If you supply a patch, i'll
integrate it.
On Thu, May 7, 2009 at 8:28 PM, Manos Batsis manos_li...@geekologue.comwrote:
James Crawford wrote:
I did look at dependency:build-classpath but I could only
see how it outputs the class path to a file.
No, that would be a bug.
On Thu, May 7, 2009 at 9:01 PM, James Crawford james.crawf...@distra.comwrote:
On Thu, 2009-05-07 at 20:34 -0400, Brian Fox wrote:
Yeah, someone else was looking for this too. If you supply a patch, i'll
integrate it.
We are currently on Maven 2.0.4 so I can't
You're shoving a square peg into a round hole by doing this. You won't get
much, if any of the benefits of Maven without using a repository.
On Wed, May 6, 2009 at 4:00 PM, tubin gen fachh...@gmail.com wrote:
I have some of the jar files modified and kept them under folder ext-lib,
there jars
I said below to set MAVEN_OPTS in your environment ;-)
On Fri, May 8, 2009 at 1:46 AM, shrimpywu imx...@gmail.com wrote:
so what should i do???
BRIAN FOX-5 wrote:
set MAVEN_OPTS = -Xmx512m for example. It can't be done directly from the
cli.
On Thu, May 7, 2009 at 1:39 AM
2009/5/8 Todd Thiessen thies...@nortel.com
Your argument Jorg I think applies to provided and runtime scope, but not
to test.
The root smell here lies in the definition of scope. Test scope means
needed to compile test code. Compile scope means needed to compile
production and test code.
You can't have a pile of files as dependencies, not the way I think you're
looking at it. You want to zip them up as a single artifact and then use
those as the dependency. You can use the dependency:unpack /
unpack-dependencies goal to extract the files from the artifact prior to
compilation.
The merging inside the configuration doesn't add the things together because
it isn't known ahead of time if replacement or merging makes sense for a
given plugin.
On Fri, May 8, 2009 at 9:33 AM, REMIJAN, MICHAEL J [AG/1000]
michael.j.remi...@monsanto.com wrote:
I have javadoc reporting
They get better with patches ;-)
On Fri, May 8, 2009 at 5:57 PM, Martin Gainty mgai...@hotmail.com wrote:
fantastic..what are the chances of opening the capability to use regular
expresssions?
thanks,
Martin Gainty
__
Disclaimer and
On Fri, May 8, 2009 at 11:17 AM, Todd Thiessen thies...@nortel.com wrote:
Override the dependency defined in the POM, as Steve outline in his
earlier response. Let me quote his explanation for ease of reference:
E.g. if project P has test scoped dependency to a LIB1, and compile
scoped
10, 2009 at 5:26 AM, Brian Fox bri...@infinity.nu wrote:
On Fri, May 8, 2009 at 11:17 AM, Todd Thiessen thies...@nortel.com
wrote:
Override the dependency defined in the POM, as Steve outline in his
earlier response. Let me quote his explanation for ease of reference:
E.g
The dependency plugin uses the existence of some marker files to detect if a
given artifact has been unpacked. By default these markers are stored in
/target/dependency.
On Sun, May 10, 2009 at 11:33 AM, Melissa Tolliver mgtolli...@gmail.comwrote:
I have an unpack execution which opens up a
Brian Fox bri...@infinity.nu
By local I mean the pom currently being built. Stuff defined here always
overrides dependencies and transitive dependencies.
On Sun, May 10, 2009 at 5:34 AM, Stevo Slavić ssla...@gmail.com wrote:
Is there any reason why would local win in this particular
On Mon, May 11, 2009 at 9:48 AM, Todd Thiessen thies...@nortel.com wrote:
Are there many cases where you want something for compilation
that isn't needed at runtime? I don't see them as being separate.
Really? I am surprised. Yes there is a relation between compile and
runtime. However,
First, I'll acknowledge that it's not easy/possible to promote an artifact
from one version to another - say 1.0-RC-10 to 1.0. Lets just accept that
for now as it's a known issue that will be resolved down the road. Lets
instead discuss a few ways to work within those bounds, since discussing
what
On Tue, May 12, 2009 at 1:58 PM, Doug Hughes dhug...@alagad.com wrote:
Hi,
I've been writing to the list off and on over the past few days. I'm a
ColdFusion developer and I'm looking at Maven for a few different reasons.
Mainly, I'm exploring the option of using Groovy+Spring+Hibernate to
Does it work with the Sun JDK?
On Mon, May 11, 2009 at 12:11 PM, Mohanraj Loganathan
mohanra...@gmail.comwrote:
Hello
I was trying to build Maven source (apache-maven-2.1.0-M1-src.zip) with
Maven 1.0.10 Maven installed in the machine.
With Harmony Development Kit, building is failed with
The aggregation is probably not a good idea as it can have other side
effects. Instead I would use the dependency plugin to pull down the source
jars you need, unpack them into a common location and then use the assembly
plugin to zip them all back up. I've done this before to convert maven based
You can't reference it from another property. Why don't you just set it to
the new value?
On Thu, May 14, 2009 at 11:08 AM, Bocalinda bocali...@gmail.com wrote:
Hi List,
It is possible to reference pom properties with ${project.version} for
example.
But how can I reference plugin
unfortunately, but you
do still test the final binaries before promoting it. This is exactly what
the Nexus staging is about, it lets you test the binaries before you promote
it to your release repo, where it's too late to pull it back.
Thanks,
Sahoo
Brian Fox wrote:
First, I'll acknowledge that it's
the value.
According to the Maven webpage, it seems that was possible in Maven 1.
2009/5/14 Brian Fox bri...@infinity.nu
You can't reference it from another property. Why don't you just set it
to
the new value?
On Thu, May 14, 2009 at 11:08 AM, Bocalinda bocali...@gmail.com wrote:
Hi List
Ok remove the dependency block. Then put version 1.4.0 elements in the
plugin section (not required, but a best practice[1][2]) . Then the error is
implying that the plugin has no default phase to run it in. You have bound
the plugin via the execution and told it to run the check goal, but you
On Fri, May 15, 2009 at 8:41 AM, j_ri jochen.riedlin...@l-bank.de wrote:
I did some mor tests.
First of all I tried with deactivated antivirus software. As expected this
didn't solve the problem
What I wrote last time. That Maven builds a different classpath for JDK 1.5
and 1.6 is
try just assemble/dsitribution.xml or even better
${basedir}/assemble/distribution.xml
On Fri, May 15, 2009 at 2:37 PM, emerson cargnin echofloripa.y...@gmail.com
wrote:
I have two projects that are children of a pom type project.
When I build them alone it works fine, but if I try to build
The dependency:copy-dependencies can also produce a repository layout.
Surely some combination of that plus assembly to zip it up should work.
On Fri, May 15, 2009 at 3:39 PM, David Smiley @MITRE.org
dsmi...@mitre.orgwrote:
Any update to this? I've tried a bunch of combinations. I think at
the :help goals are relatively new, it's likely that 2.2 doesn't have that.
Just go to the maven-install-plugin page to see the help.
On Fri, May 15, 2009 at 4:10 PM, T W twell...@gmail.com wrote:
I'm attempting to try out Lift and the package installs a version of
maven. I couldn't execute
Try a newer jdk.
On Sat, May 16, 2009 at 10:46 PM, lindberg grebdn...@hotmail.com wrote:
I have an application that use the Maven then when I do debug using Maven I
get the message below but when I do the normal debug without using Maven
works. what can be? what do I do?
#
# An unexpected
release could
improve on this: We have a silent failure to copy, so it would be good to
have better tracking of when copying is REALLY needed, or at least a
clearer log line on this.
On Mon, May 11, 2009 at 4:13 AM, Brian Fox bri...@infinity.nu wrote:
The dependency plugin uses the existence
Paste the output of help:effective-pom
On Sun, May 17, 2009 at 2:09 PM, Reiner Saddey r...@saddey.net wrote:
Jan Torben Heuer-5 wrote:
Hi,
When I deploy my artifact (version 1.0-SNAPSHOT), maven puts it in the
/releases directory although I set up both, repository and
Yours looks right.
On Sun, May 17, 2009 at 8:15 PM, Reiner Saddey r...@saddey.net wrote:
BRIAN FOX-5 wrote:
Paste the output of help:effective-pom
On Sun, May 17, 2009 at 2:09 PM, Reiner Saddey r...@saddey.net wrote:
Jan Torben Heuer-5 wrote:
Hi,
When I deploy my
That's normal unless you disable automatic snapshot updates for each of
these repos in your settings.
On Mon, May 18, 2009 at 9:07 AM, Danilo Tuler tu...@pobox.com wrote:
Hi,
I have a multi-module project with a dozen modules.
Whenever I do a maven release:prepare maven checks remotely for
Because it's making sure that the build is correct, it's basic snapshot
behavior.
On Mon, May 18, 2009 at 12:53 PM, Danilo Tuler danilo.tu...@gmail.comwrote:
I have a multi-module project with a dozen modules.
Whenever I do a maven release:prepare maven checks remotely for
SNAPSHOT
1 - 100 of 453 matches
Mail list logo
