bluewhale wrote:
Downloaded:
http://repo1.maven.org/maven2/org/codehaus/cargo/maven-metadata.xml
[...]
[ERROR] No plugin found for prefix 'cargo'
The proper metadata is now out such that mvn cargo:help works as intended.
Please note that Maven refetches metadata by default only once a day.
bluewhale wrote:
Downloaded:
http://repo1.maven.org/maven2/org/codehaus/cargo/maven-metadata.xml
[...]
[ERROR] No plugin found for prefix 'cargo'
It appears something went wrong during the last release of Cargo, the
mentioned metadata file lists cargo2 as the plugin prefix which
however
Stephen Connolly wrote:
i got the impression that to fix it the dependency plugin would need to
depend obey the aether apis...
Correct. mvn dependency:tree or more precisely the
maven-dependency-tree component currently relies on resolution events to
deduce the dependency tree, Aether's
makripon wrote:
A required class is missing:
org/apache/maven/shared/invoker/MavenInvocationException
[ERROR] -
[ERROR] realm =
pluginorg.apache.maven.plugins:maven-archetype-plugin:2.0
[ERROR] strategy =
Gracia, Adrien wrote:
The timestamp and the last updated value is the file modified timestamp
Just be sure to store lastUpdated in UTC.
Benjamin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
Karl Heinz Marbaise wrote:
Does exist a possibility to change the Maven Validation Level on command
line via a property etc. ? for Maven 3.0.3 ?
No.
Benjamin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
Gracia, Adrien wrote:
The problem we are having, is that even if there is a new version of a
SNAPSHOT, the newer version is not downloaded.
[...]
The way we understood the format of this file is as follow
metadata
groupIdthe group id/groupId
artifactIdthe artifact id/artifactId
versioning
Karl Heinz Marbaise wrote:
I observed a little thing which i didn't understand...
If i run the example the first time i got the following exception:
Let's start with the clarification that this exception is logged and not
thrown up.
Furthermore in the interface RepositorySystem the method
Karl Heinz Marbaise wrote:
Isn't there a better solution to the information about the repositories from
the current settings.xml file or from the system configuration settings.xml
file.
TomazM wrote:
directory/src/main/resources/persistence/sfinga2/directory
Relative paths don't start with directory separators, the plugin is
correct in this regard. You want
src/main/resources/...
Benjamin
-
To
David Balažic wrote:
http://jira.codehaus.org/browse/MCOMPILER-70
I am using mvn --version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Fix version for the above issue is maven-compiler-plugin 2.1, Maven
2.2.1 defaults to using maven-compiler-plugin 2.0.2.
Benjamin
Rafael Vanderlei wrote:
I'm just wondering if there is a suitable reason for that. So what I still
dont understand is if a property declared in a parent pom can be used on
the child pom for other purposes, WHY cant it be used to activate a profile
defined in that child pom?
Because profiles
Jason Nerothin wrote:
The drools libs are out on the jboss snapshots repository and the connector
lib is being staged in archiva. In both cases, they're sitting right where I
expect them to be in my local repository.
Robert Dare wrote:
[ERROR] Non-resolvable parent POM: [...] 'parent.relativePath' points at
wrong
local POM @ line 12, column 10 - [Help 2]
It should be as simple as fixing your POM to specify the proper path as
indicated by the msg.
Benjamin
Asmann, Roland wrote:
Is
there some way to have Maven report back on where the settings.xml files
where found?
Debug logging of Maven 3.x, i.e. mvn -X spits out the paths at the
beginning of the log.
Benjamin
-
To
Chris wrote:
The third party jar that it's looking for does not exist in maven
central; it's a proprietary app. But it does exist in the proper place
in my local repo, with the right version number and everything (I've
triple checked).
[...]
My settings.xml is empty, if that's relevant.
Could
shaun.t.erickson wrote:
[INFO] --- maven-antrun-plugin:1.3:run (metrics-for-eclipse) @ ccl ---
[DEBUG] org.apache.maven.plugins:maven-antrun-plugin:jar:1.3:
[DEBUG]org.apache.ant:ant-nodeps:jar:1.7.0:runtime
[DEBUG]ant-contrib:ant-contrib:jar:1.0b3:runtime
[DEBUG]
Javelin wrote:
[ERROR] Failed to parse plugin descriptor for
org.apache.maven.plugins:maven-ejb-plugin:1.7.3
You seem to be using a Maven 1.x plugin. So try updating to version 2.3:
http://maven.apache.org/plugins/maven-ejb-plugin/
Benjamin
shaun.t.erickson wrote:
plugin inherited='true
Try the inherited element instead, cf. [0].
Benjamin
[0] http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_plugin
-
To unsubscribe, e-mail:
Michael Remijan wrote:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
(ferris-bin-assembly) on project ferris-bible-common: Execution
ferris-bin-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single failed: Plugin
Yann Albou wrote:
It's my understanding that timestamp snapshots should only exist in remote
snapshot repositories and are created when doing a mvn deploy.
What I see though is timestamp snapshots downloaded into my local repository
when doing mvn install.
True is that mvn install of project
Yann Albou wrote:
Also we don't have a mechanism to purge the local repositories as we do on
the remote repository with Nexus, or does maven provide one I don't know of?
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
Benjamin
The Maven team is pleased to announce the release of Apache Maven 3.0.3
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of source
wytten wrote:
Specifically, when I expect it to download the latest jar from Artifactory,
all it downloads is metadata:
Unless the metadata indicates the existence of a newer snapshot, there
is nothing to download.
Benjamin
wytten wrote:
I know for a fact that a newer snapshot was uploaded to Artifactory.
To troubleshoot, you could check the maven-metadata-*.xml in your local
repository for the artifact in question. Maven picks the file with the
newest lastUpdated value. The value is a UTC timestamp.
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential regressions since
version 3.0.2 before the actual release of 3.0.3.
For the duration of the RC testing,
Gebhardt, Jörn wrote:
If I now build a project projectB that depends on the Snapshot version of project projectA
, Maven looks into the central repository and overrides my just built and installed version with an
older one from the central repository. My guess is that this happened because
Kristoffer Peterhaensel wrote:
So it is trying to resolve released a dependency on a
snapshot repository because the dependency that requires
it is a snapshot? And why does that not happen when I lock
down the dependency version of coreapi to 1.0.1-SNAPSHOT.
Shouldn't that do exactly the same?
Vidar Ramdal wrote:
I'm trying to understand how Maven updates thelatest element in
maven-metadata.xml - or more specifically, why it doesn't.
Oh it does, when Maven itself needs it. It's not a general purpose
feature of the metadata.
(I am aware that many are discouraging the use of
Vidar Ramdal wrote:
Could you elaborate on this? Does it mean thatlatest is some kind
of internal Maven stuff that cannot be relied on?
Exactly, it supports automatic plugin version resolution.
Unfortunately it doesn't work for me (could be an issue with
maven-launchpad-plugin).
I'm
Kai Hackemesser wrote:
In the project we try to build a runnable jar that depends on libraries that
are assembled into a lib folder. Under Maven 2(.2.1) we have no problem with
that, the runnable jar works as designed. The same project build under Maven
3.0.2 currently builds the project
John Prystash wrote:
From inside my plugin code, I want to be able to load the text of the resource,
contained in src/main/resources/request.xml (and presently in target/classes):
[...]
It appears to be that while the resource is on the classpath of the
project using the plugin, its not
Benson Margulies wrote:
Can mojo parameters be enums?
One of the smaller improvements that went into Maven 3:
http://jira.codehaus.org/browse/MNG-4292
Benjamin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
Tim wrote:
Is there a way to extend a parent pom's plugin configuration?
I have a situation where the parent pom configures the surefire plugin
a great deal.
I want to add one more systemProperty but I don't have to copy the
whole configuration of that plugin down because
Potentially helpful
The Maven team is pleased to announce the release of Apache Maven 3.0.2
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of source
Anders Hammar wrote:
To me it seems as
project.getReportPlugins()
don't cope with the new syntax for declaring report plugins (i.e. declared
in the configuration of the site plugin). I would start by filing a jira on
Maven core.
This is Won't fix as far as Maven core is concerned. This
fmeili wrote:
My plugin needs all dependend artifacts (includeing transitives) of the
project. With maven 2.2.1 the call to project.getArtifacts() works correct.
When using it with maven 3.0.1 the returned set of artifacts for a project
has a size of zero.
Code snippets:
/**
* @goal myGoal
Carpentier Xavier wrote:
I test m3 3.0.2-RC1 and maybe it's regression :
[WARNING] The metadata
/Users/carpentierxqvier/.m2/repository/com/greenivory/redmole/client/commons/com.greenivory.redmole.client.commons/2.3.0-SNAPSHOT/maven-metadata-local.xml
is invalid: Snapshot information
vratnagiri wrote:
Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to
deploy metadata: Could not transfer metadata
com.***.deployment:ThirdPartyDeploymentProject:0.0.1-SNAPSHOT/maven-metadata.xml
from/to deploymentRepoSnapshot
Anand HS wrote:
4. Now when I invoke mvn install from the ROOT pom, I see that ModuleA and
ModuleA-distribution.jar get build with no issues. Now when ModuleB is
built, in spite of explicit exclusion of ModuleA's dependencies , those
dependencies do not get excluded.
Could be
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential regressions since
version 3.0.1 before the actual release of 3.0.2.
For the duration of the RC testing,
Steve Cohen wrote:
Another thing I notice is that
mvn -ep {password}
when run several times in succession generates different encryptions
each time.
This is correct/expected, the encrypted value is also based on a random
salt.
Benjamin
Marcin Kuthan wrote:
http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=770
The last revision 770 is a result of deploying 1.3-SNAPSHOT by Maven 2
Only in the last case, when Maven 2 was used for deployment, element
Marcin Kuthan wrote:
After 1.1 deployment latest release version has not been updated:
http://code.google.com/p/m4enterprise/source/browse/release-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=806
Good catch, filled as http://jira.codehaus.org/browse/MNG-4952.
Benjamin
Simone Tripodi wrote:
thanks for your reply, does it mean that it won't be supported at all
or there is a plan for the future to fix it?
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-LegacystyleRepositories
Benjamin
Marcin Kuthan wrote:
You can easily reproduce the issue with direct mvn deploy:deploy
-DupdateReleaseInfo=true call.
I just ran mvn deploy:deploy on a project foo:bar:1.0:pom and got the
expected metadata. So I can only suggest you fill an issue with a
complete example project that
Simone Tripodi wrote:
[exec] [ERROR] 1) No implementation for
org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout
annotated with @Named(value=legacy) was bound.
[exec] [ERROR] while locating
org.apache.maven.plugins.mavenone.MavenOneRepositoryInstallMojo
Neither
Hauschel Fred Robert wrote:
Or did I have problems understanding the environment variables? Is there
a case sensitivity in general ??
http://maven.apache.org/pom.html#Properties
Benjamin
-
To unsubscribe, e-mail:
Andre M wrote:
I just upgraded to Maven3 from Maven2 today, and when I run mvn.bat
-version, this is what I see:
[...]
at
org.apache.maven.cli.MavenCli.buildSettings(MavenCli.java:402)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:202)
at
Hi,
as part of MNG-4893 [0] an inconsistency in the way a version string is
treated as a snapshot or release was detected. In short, the issue is
about what suffix exactly marks a snapshot version.
The current intention is to revise the logic such that the suffix
-SNAPSHOT (note the leading
martib wrote:
Return code is: 504 - [Help 1]
HTTP 5xx denotes server-side issues, so it's worth to check the
proxy/server logs and start from there.
Benjamin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
The Maven team is pleased to announce the release of Apache Maven 3.0.1
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of source
Laird Nelson wrote:
I have a pom.xml. It looks like this:
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
jonjack wrote:
Should I update m2.conf accordingly:
-
from:
set maven.home default ${user.home}/m2
You could also remove that line which has the same effect, it doesn't
matter.
Benjamin
jonjack wrote:
Also, what about the dot (.) missing from the default path to .m2 in
m2.conf?
That line has no effect as maven.home is set by the launch scripts, so
its contents doesn't matter.
Benjamin
-
To unsubscribe,
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential regressions since
version 3.0 before the actual release of 3.0.1.
For the duration of the RC testing,
Evgeny Goldin wrote:
[ERROR] urls[65] =
file:/C:/Users/evgeny/.m2/repository/plexus/plexus-utils/1.0.2/plexus-utils-1.0.2.jar
[ERROR] urls[70] =
file:/C:/Users/evgeny/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
A classpath conflict, your plugin has a
Evgeny Goldin wrote:
Anybody?
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
The debug log from Maven, in particular the lines detailing the contents
of the plugin class realm, might give a clue.
Benjamin
-
To
Steven Yamanaka wrote:
MAVEN_OPTS=-Dorg.apache.maven.user-settings=path to settings.xml
This doesn't appear to work in Maven 3. Is there an alternative other than the
command
line option --settings?
There is no alternative but support for the system property can be
restored if there's
cowwoc wrote:
dependencies
dependency
groupIdorg.eclipse.swt/groupId
artifactIdswt/artifactId
classifier${swt.classifier}/classifier
version3.6.1/version
/dependency
/dependencies
profiles
profile
chemit wrote:
Is those problem are known? I did not see anything about this on the
list, which means one thing to me : windows users does not use maven
(this was my troll sorry ;)).
Hope something will be done soon about it ;)
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Benjamin
Jacob Beard wrote:
With maven, however, the libraries are now kept in the location of the
maven repository, several directories deep, based on information kept in
the pom.xml file. I'd like to know, is there a maven solution for
extracting a particular classpath from a maven file, such that the
Jesse Glick wrote:
I am interested in experimenting with whether a plugin running in Maven
3 and declared as a build extension can *replace* a standard service.
Not possible.
I would like to replace DefaultProjectDependenciesResolver
with a variant that behaves specially on certain kinds of
jstrachan wrote:
Is there a way to activate or de-activate a profile based on the maven
version?
Have a look at
https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html#Maven3.xandsiteplugin-Usingmavensiteplugin2.xwithMaven2.xandmavensiteplugin3.xwithMaven3.x
it demonstrates such a
Tom wrote:
Could not
find artifact nl.innovationinvestments:CheyenneServlet:jar:1.11-SNAPSHOT
in kp (http://alaya.applicationplaza.com:8081/nexus/content/groups/pub
lic)
Could be related to [0], i.e. a problem with the metadata that Maven
requires to locate the timestamped snapshot. Either
Andreas Gies wrote:
[INFO] org.scala-tools:scala-mojo-support:jar:0.3-SNAPSHOT
...
[INFO] | +- org.sonatype.sisu:sisu-inject-plexus:jar:1.4.2:compile
[INFO] | | \- org.sonatype.sisu:sisu-inject-bean:jar:1.4.2:compile
[INFO] | | \- org.sonatype.sisu:sisu-guice:jar:noaop:2.1.7:compile
...
[INFO]
Tom wrote:
This wiki refers to Maven 2 clients having problems
From that wiki:
Additionally, some repository managers [...] may not cope with the
additional XML elements in the metadata file.
This applies to (unpatched) Nexus versions before 1.8 where the issue
manifests itself as the
Jörg Schaible wrote:
Is it save now in M3 to declare a different plugin artifact as dependency?
You mean plugin A having a dependency on plugin B? This shouldn't cause
an issue for Maven 3 when running the plugin (it should also work in
recent Maven 2.x releases IIRC).
That inheriting
Ryan Connolly wrote:
when will the maven site be updated to offer m3 in the downloads page?
The updated site is already deployed and merely awaits its sync to the
live server.
Benjamin
-
To unsubscribe, e-mail:
The Maven team is pleased to announce the release of Apache Maven 3.0.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of source
Hilco Wijbenga wrote:
But why would only Maven 2 complain and not Maven 3 then?
There's always a chance of a bug.
repositories
repository
idcentral/id
urlhttp://central/url
releases
enabledtrue/enabled
/releases
Hilco Wijbenga wrote:
Any ideas how I can fix this? Any ideas as to what the problem is exactly?
I personally find it helpful to start with a precise description of what
the issue actually is before trying to solve it. After all, there's a
reason why the build produces a log and even if you
Hilco Wijbenga wrote:
(The download link to RC3 is no longer
valid so I have not been able to try it with RC3.)
The RCs did they job and have been superseded with
https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
I've emptied the local
Daniel Patton wrote:
However, the
ZIP file (which is the attached artifact produced by the maven-pde-plugin)
is given a buildNumber of 4, and if I check the maven-metadata.xml file, the
buildNumber has indeed been incremented twice.
In case you refer to the pde-maven-plugin
Xavier D. wrote:
My pom structure is: pom.xml has a parent: parent-pom.xml.
Both have aresources section to include files.
The (child) pom.xml is executed directly and has the effect of only copying
the child's resources. Commenting out this resource section, results in
the parent's
Marshall Schor wrote:
Is a workaround (until Nexus is patched), to use -Dmaven.metadata.legacy=true on
the maven command line?
The workaround is no longer necessary to deploy Apache snapshots, r.a.o
has been updated to Nexus 1.8.0 by now.
Benjamin
Marshall Schor wrote:
The file underversion-SNAPSHOT/maven-metadata.xml can't be read using
http://repository.apache.org/snapshots/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/maven-metadata.xml.
r.a.o/snapshots is a group, the actual repository contains the intact file:
Marshall Schor wrote:
Is a workaround (until Nexus is patched), to use -Dmaven.metadata.legacy=true on
the maven command line?
Yes.
Benjamin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
Hi,
in preparation for the release of Apache Maven 3.0, the Maven team is
seeking your help to discover regressions since Maven 2.x. Everybody
interested in taking a preview of the upcoming release for a test drive
can get source and binary bundles from this URL:
kristian wrote:
any hints are welcome to do the better.
/** @parameter default-value=${repositorySystemSession}
* @readonly
*/
private RepositorySystemSession repoSession;
...
request.setRepositorySession( repoSesssion );
Benjamin
Hi,
in preparation for the release of Apache Maven 3.0, the Maven team is
seeking your help to discover regressions since Maven 2.x. Everybody
interested in taking a preview of the upcoming release for a test drive
can get source and binary bundles from this URL:
lukewpatterson wrote:
component-set
components
component
roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role
role-hintjar/role-hint
Before, it seems the custom goals were merged with the standard jar
packaging goals.
If you can provide a complete example
kristian wrote:
I have a plugin where I use the maven3 api.
maven-RC1 gives
Caused by: java.lang.NoSuchMethodError:
org.apache.maven.project.ProjectBuildingRequest.setForceUpdate(Z)Lorg/apache/maven/project/ProjectBuildingRequest;
maybe I should not have used that ProjectBuilder, maybe that
Hi,
in preparation for the release of Apache Maven 3.0, the Maven team is
seeking your help to discover regressions since Maven 2.x. Everybody
interested in taking a preview of the upcoming release for a test drive
can get source and binary bundles from this URL:
The Maven team is pleased to announce the release of the Maven Compiler
Plugin, version 2.3.2.
This plugin is used to compile the sources of your project. See the
plugin's site for more details:
http://maven.apache.org/plugins/maven-compiler-plugin/
To use the updated plugin in your
The Maven team is pleased to announce the release of Apache Maven
3.0-beta-3.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of
The Maven team is pleased to announce the release of the Maven Shade
Plugin, version 1.4.
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies. See the plugin's site for more
The Maven team is pleased to announce the release of Apache Maven
3.0-beta-2.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of
The Maven team is pleased to announce the release of the Maven
Repository Plugin, version 2.3.1.
This plugin assists the user in creating archived bundles that are
designed to meet all requirements for upload to the central Maven
repository. Please see the plugin's site for more details:
The Maven team is pleased to announce the release of the Maven GPG
Plugin, version 1.1.
This plugin is used to create signatures for project artifacts using the
GnuPG tool. Please see the plugin's site for more details:
http://maven.apache.org/plugins/maven-gpg-plugin/
To use the updated
The Maven team is pleased to announce the release of the Maven GPG
Plugin, version 1.1.
This plugin is used to create signatures for project artifacts using the
GnuPG tool. Please see the plugin's site for more details:
http://maven.apache.org/plugins/maven-gpg-plugin/
To use the updated
The Maven team is pleased to announce the release of the Maven Source
Plugin, version 2.1.2.
The Source Plugin creates a jar archive of the source files of the
current project. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-source-plugin/
To use the updated
The Maven team is pleased to announce the release of the Maven Shade
Plugin, version 1.3.3.
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies. See the plugin's site for more
The Maven team is pleased to announce the release of the Maven Clean
Plugin, version 2.4.1.
This plugin is used to clean the project output directories. Please see
the plugin's site for more details:
http://maven.apache.org/plugins/maven-clean-plugin/
To use the updated plugin in your
The Maven team is pleased to announce the release of the Maven Plugin
Tools, version 2.6.
This plugin assists authors of Maven plugins in the creation of a plugin
descriptor and documentation by scanning the plugin sources for mojo
annotations. See the plugin's site for more details:
The Maven team is pleased to announce the release of Apache Maven
3.0-beta-1.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of
The Maven team is pleased to announce the release of the Maven Compiler
Plugin, version 2.3.
This plugin is used to compile the sources of your project. See the
plugin's site for more details:
http://maven.apache.org/plugins/maven-compiler-plugin/
To use the updated plugin in your
The Maven team is pleased to announce the release of the Maven Shade
Plugin, version 1.3.2.
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies. See the plugin's site for more
The Maven team is pleased to announce the release of the Maven EJB
Plugin, version 2.2.1.
This plugin is used to generates J2EE Enterprise Javabean (EJB) file as
well as the associated client jar. Please see the plugin's site for details:
http://maven.apache.org/plugins/maven-ejb-plugin/
The Maven team is pleased to announce the release of Apache Maven
3.0-alpha-7.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of
1 - 100 of 163 matches
Mail list logo
