The Maven team is pleased to announce the release of the Maven Enforcer
Plugin, version 1.2
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.
http://maven.ap
The Maven team is pleased to announce the release of the Maven Enforcer,
version 1.1
This plugin provides various configurable validation rules for Maven builds.
http://maven.apache.org/enforcer/
http://maven.apache.org/plugins/maven-enforcer-plugin/
You should specify the version in your projec
The Maven team is pleased to announce the release of the Maven Surefire,
version 2.10
This release includes the maven-surefire-plugin, which executes the
unit tests of an application, the maven-surefire-report-plugin, which
parses surefire/failsafe test results and renders them to DOXIA
creating t
-1671] - License download-licenses goal doesn't allow
parameters to be defined using system properties
Enjoy,
The Mojo team.
Paul Gier
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional comman
The Maven team is pleased to announce the release of the Maven Deploy
Plugin, version 2.6
This plugin allows artifacts to be deployed to a Maven repository. See
the plugin's site for more details:
http://maven.apache.org/plugins/maven-deploy-plugin/
You should specify the version in your proje
Can't skip plugin to run even if tests are skipped
and phase is set to test.
Enjoy,
The Mojo team.
Paul Gier
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
ANTLR plugin does not reorder grammars connected by
importVocab/exportVocab dependencies
* [MANTLR-29] - Impossible to utilize dependent grammars
(import/export vocabs) using different packages
Enjoy,
The Mojo team.
Paul
The Maven team is pleased to announce the release of the Maven Antrun
Plugin, version 1.6
This plugin provides the ability to run Ant tasks in a Maven build. See
the plugin's site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your proj
The Maven team is pleased to announce the release of the Maven Antrun
Plugin, version 1.5
This plugin allows Ant tasks to be run within a Maven build. See the
plugin's site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your project's p
The Mojo team is pleased to announce the release of the JBoss Maven
Plugin version 1.4.1.
http://mojo.codehaus.org/jboss-maven-plugin/
This release includes bug fixes and minor enhancements, specifically
related to the way the plugin starts and stops a JBoss server.
To get this update, simply sp
The Mojo team is pleased to announce the release of the RMI Compiler Maven
Plugin version 1.1.
http://mojo.codehaus.org/rmic-maven-plugin/
This release includes minors updates to the site and the project configuration.
To get this update, simply specify the version in your project's plugin
confi
The Maven team is pleased to announce the release of the Maven Antrun Plugin,
version 1.4
This plugin allows Ant tasks to be run inside a Maven build. See the plugin's
site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your project's p
The Maven team is pleased to announce the release of the Maven Ant Tasks,
version 2.1.0
The Maven Ant Tasks allow several features of Maven to be used in an Ant build.
This includes dependency management, reading and writing pom files, and
deployment to a Maven repository. More information i
The Mojo team is pleased to announce the release of the JBoss Packaging Maven
Plugin version 2.1.1.
http://mojo.codehaus.org/jboss-packaging-maven-plugin/
This release includes some minor bug fixes and updates to the plugin site.
To get this update, simply specify the version in your project's
The Mojo team is pleased to announce the release of the JBoss Maven Plugin
version 1.4.
http://mojo.codehaus.org/jboss-maven-plugin/
Some notable features in this release include improvements to the start-and-wait
mojo and general improvements to the plugin configuration. The plugin site has
The Mojo team is pleased to announce the release of the JBoss Packaging Maven
Plugin version 2.1.
http://mojo.codehaus.org/jboss-packaging-maven-plugin/
Some notable features in this release include handling for the par (process
archive) format.
To get this update, simply specify the version
The Mojo team is pleased to announce the release of the Build Helper Maven
Plugin version 1.4.
http://mojo.codehaus.org/build-helper-maven-plugin/
This is mainly a bug fix release.
To get this update, simply specify the version in your project's plugin
configuration:
org.codehaus.mojo
The Mojo team is pleased to announce the release of the JBoss Packaging Maven
Plugin version 2.0.
http://mojo.codehaus.org/jboss-packaging-maven-plugin/
This is mainly a bug fix and minor refactoring release.
To get this update, simply specify the version in your project's plugin
configuration
The Mojo team is pleased to announce the release of the Build Helper Maven
Plugin version 1.3.
http://mojo.codehaus.org/build-helper-maven-plugin/
Some notable features in this release include:
- A new goal to retrieve the current version of Maven to a property.
- A new goal to parse the c
The Maven team is pleased to announce the release of the Maven Ant Tasks,
version 2.0.10
The Maven Ant Tasks allow several features of Maven, (dependency management,
artifact deployment, etc.) to be used within an Ant build. More information is
available at the project site.
http://maven.ap
The Maven team is pleased to announce the release of the Maven Source Plugin,
version 2.1
This plugin is used to create jar of the project source files.
http://maven.apache.org/plugins/maven-source-plugin/
You should specify the version in your project's plugin configuration:
org.apache.m
As far as I know, it's not expected behaviour. If you can create a jira issue
with a sample project to reproduce this, I'm sure someone can take a look.
Also, try version 2.4.3 since that is the latest.
Jaikiran wrote:
I am using Maven surefire plugin 2.4.2 with the following configurations:
I think it's the duplicated artifactId's that is causing the problem. Maybe the
artifactId of the pom in the subdirectory modA/modA should be set to "modA-modA"
or something like that.
huser wrote:
Hi,
I have a situation in which the dir names are same.
Example:
/base
/base/modA
/base/mod
There is an associated JIRA issue related to this [1]. Please vote for it if
you are interested.
[1]http://jira.codehaus.org/browse/MNG-3720
Rusty Wright wrote:
Why does the url for MavenPropertiesGuide start with docs.codehaus.org?
I would think it should start with maven.apache.org. I rec
ation:
org.codehaus.mojo
properties-maven-plugin
1.0-alpha-1
Regards,
Paul Gier
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
lugin
configuration:
org.codehaus.mojo
rmic-maven-plugin
1.0
A comprehensive list of changes is attached at the end of this mail.
Regards,
Paul Gier
Release Notes - Maven 2.x RMIC Plugin - Version 1.0
** Bug
* [MRMIC-23] - rmic creates multiple stub files when run multiple times
* [
The Mojo team is pleased to announce the release of the JBoss Packaging Maven
Plugin, version 2.0-beta-1
http://mojo.codehaus.org/jboss-packaging-maven-plugin/
This plugin is a replacement of the earlier jboss-sar-maven-plugin. The plugin
has been deployed to the codehaus repository, and it s
The Mojo team is pleased to announce the release of the RMIC Maven Plugin
version 1.0-beta-1.
This release contains some minor enhancements and bug fixes.
A list of changes is attached at the end of this mail.
Enjoy!
Paul Gier
Release Notes - Maven 2.x RMIC Plugin - Version 1.0-beta-1
Assuming you are creating a DefaultArtifact object, you have to set the
classifier when you first call the constructor. Does that work for you?
https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java
Gu
This seems to work ok for me. I tried it locally and my profile properties
override my pom properties, and cli props defined with -D override both pom and
profile properties. I tried with maven 2.0.6 and 2.0.8.
Can you attach a small zipped project to a jira issue that reproduces the
problem?
For anyone that uses rmic in their builds, I have released the rmic-maven-plugin
version 1.0-alpha-1. It is now in the codehaus repository, and it should be
available via the central repository later today.
Please check it out and submit feedback through jira.
Thanks!
---
g and a branch, but that's not true in
cvs.
The "nightly x/x/x" and the "release x/x/x" are not the same code. The
pom of a release has no SNAPSHOTs dependencies.
Paul Gier wrote:
I would think checking out from the tag, and then running
release:prepare from that w
Hi Julien,
Can you create a jira issue for the jboss maven-jdocbook-plugin with some sample
input? Here is the jira URL (http://jira.jboss.com/jira/browse/MPJDOCBOOK).
Then maybe we can get it fixed.
Tahnks!
Julien Graglia wrote:
What do you use to generate PDF books?
I'am using doxia-maven
Sorry this is not much help, but I haven't had good luck with getting the
release plugin to update my snapshot dependencies either. So I always update
them manually before doing a release. If you can create a jira issue for this
(in the release plugin project) and attach a small test project t
I would think checking out from the tag, and then running release:prepare from
that would work fine for you in this case. It will create another tag, but that
shouldn't be a problem, since you probably want to keep one tag "nightly x/x/x"
and then another tag "release x.x.x" even though they ha
Hi Everyone,
I'm currently doing some work on the rmic maven plugin, and I plan to do a
1.0-alpha-1 release in the upcoming weeks. If you use this plugin or you are
interested in it, please take a look at some of the jira issues
(http://jira.codehaus.org/browse/MRMIC). If there are issues tha
Hi Everyone,
The JavaCC maven plugin version 2.3 has been released, and should show up in the
central maven repository later today. This release includes several bug fixes,
a couple new features including a new jjdoc mojo, and some improvements to the
project site (http://mojo.codehaus.org/jav
Hi Everyone,
I'm planning to do a release of the javacc maven plugin
(http://mojo.codehaus.org/javacc-maven-plugin/) sometime next week. If you use
this plugin or are interested in it, I encourage you to try out the 2.3-SNAPSHOT
that is available in the codehaus snapshots repository.
Thanks
Has anyone successfully deployed a jar file to a maven repository using the
ant task? I tried using this task with both maven 2.0.6 and
maven 2.0.8, and it would only deploy the pom files and not the jar.
I ended up using ant and just calling "mvn deploy:deploy-file". I'm
wondering if I'm
Hi Everyone,
Is there a way to tell maven to download source jars by default? I didn't see
anything in the pom or settings model to do this. I know I can download sources
using the eclipse plugin or the dependency plugin, but I would like to tell
maven to always download source jars when buil
You can also use
mvn project-info-reports:dependencies
That will generate an html page with the dependency tree in the target/site
directory. That should make it a little easier to figure out where transitive
dependencies are coming from.
Erez Nahir wrote:
Thanks Larry for the prompt and det
Anyone know how to get the current execution Id from within a plugin?
I would like to be able to compare the current execution Id to a system
property while the plugin is running.
Thanks!
-
To unsubscribe, e-mail: [EMAIL PROTE
I would like to verify that certain properties are set in my pom. If
the property is not set, I would like the build to fail. Is there a way
to do this with the enforcer plugin or with another plugin?
Thanks!
-
To unsubscrib
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most
I would like to have two profiles. One profile can be called by
itself. The second one should activate the first one so that the
configuration of the first is included.
Is this possible?
Thanks!
-
To unsubscribe, e-mail: [EM
Is there a way I can specify which snapshot build my project should use
in it's dependencies? I would like maven to ignore the latest snapshot
version, and refer to a specific snapshot build number.
Thanks!
-
To unsubscribe,
Is there a way I can access the current execution ID if I have multiple
executions of a plugin?
I have multiple executions of the surefire plugin, and I would like the
output to go to a different directory for each execution.
So in my plugin configuration I would like to have something like:
How do I change the log level of the surefire plugin? I would like to
change the log level from DEBUG to INFO.
If I have multiple execution IDs in my surefire configuration, is there
a way to run just one of the executions? I could do it using profiles,
but I was wondering if there is an e
When working on a maven plugin, I noticed that two attached artifacts
can have the same name and overwrite each other when they are deployed.
Is this by design? Maybe the artifacts attached to a project should be
a set instead of a list, and a warning should be generated when one
artifact r
I'm trying to create an assembly for a multi-module project that
includes the dependencies of the modules.
My assembly descriptor looks something like this:
standalone
zip
false
group:moduleA
group:moduleB
modules/${artifactId}
false
How are transitive dependencies handled when the artifacts have a
non-default classifier? For example, I have the following dependency
tree:
A -> B
B -> C
Now let's say I want to build a jdk1.4 version of A. So I depend on
B-jdk14.jar (B with jdk14 classifier), and B-jdk14.jar depends on
C-jdk14
What's the easiest way to download the whole central repository? Is
there a maven plugin to do that? Or is there some way to get a zip of
the whole thing?
On Mon, 2007-03-19 at 14:26 +, Andrew Williams wrote:
> If you can run maven on an internet connected computer first to
> download all
I have a project with multiple modules, and I would like to assemble the
classes of the modules into a single jar file.
If the names of the modules (and directories) match the artifact ID, the
assembly works fine. But if the artifactId does not match the module
name, then the files are not picked
gt; make the parent and all submodules using the same snapshot version number.
>
> take a look at this project
>
> http://svn.codehaus.org/mojo/trunk/mojo/maven-native
>
> -D
>
>
> On 3/8/07, Paul Gier <[EMAIL PROTECTED]> wrote:
> >
> >
> >
I have a multi-module project where some modules depend on others.
parent
|--module1
|--module2
`--module3
And module 2 depends on the current snapshot version of module 1. I
would like to release them all at the same time, but the problem is that
the release plugin tells me that module 2
that you might be talking about what was reported in
> http://jira.codehaus.org/browse/MNG-553 . This issue was reported a
> long time ago and doesn't seem to be getting much attention anymore...
> Maybe a few more votes for it?
>
> On 3/3/07, Wendy Smoak <[EMAIL PROTECTED]>
Some additional info, I'm using an svn repository, and maven 2.0.5
Thanks!
On Mon, 2007-03-05 at 15:01 -0600, Paul Gier wrote:
> When I use the dryRun option, it seems to work fine. But then if I try
> to use the standard release:prepare after a dry run, maven tells me that
> th
When I use the dryRun option, it seems to work fine. But then if I try
to use the standard release:prepare after a dry run, maven tells me that
the prepare step is finished and does not tag my release. Is this a
bug?
If I set resume to "false" then the prepare step starts over and
everything wo
Is there a way to supply a username and password for a remote repository
on the command line instead of in the settings.xml? It would be helpful
if the deploy plugin could prompt the user as needed for this
information. The password could be hidden from view this way, and
developers would not hav
2.0.4
That should be enough to get the scm information in your plugin.
..David..
-----Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 9:01 AM
To: users@maven.apache.org
Subject: Get the scm settings from plugin
I would like to
I would like to be able to access the scm settings (connection, tag,
etc) in the pom.xml from within a plugin. Is this possible? It seems
like there should be an easy way to get access to all of the pom
configuration from within a plugin, but I haven't found it yet. I tried
looking in projec
61 matches
Mail list logo