I don't see why not. I was going to roll an RC3 early next week anyway,
just to make sure we have a clean binary before I call the vote. Can you
make the necessary changes in the 2.1.x and 2.1.0-RC branches?
-john
Hervé BOUTEMY wrote:
Hi,
I released Modello 1.0.1 a few days ago: any objecti
Yes it is odd, but I share jason's concern that sending the source
folders directly to the compiler plugin is bad because then tools that
look at the pom won't find the sources. (which btw is the case even with
the buildhelper)
-Original Message-
From: Paul Gier [mailto:pg...@redhat.com]
S
Yeah, it probably could be done like that. But it seems a little strange way to
accomplish it.
Also that would put all the output into a single directory, and I would prefer
to keep the classes separate in the output.
Brian E. Fox wrote:
Can you do it with multiple compiler executions? I'm th
The assembly plugin can construct a repo and put it in a zip, but I
would be surprised if this case is covered. then you would have to
devise a way to unpack the zip to the users local repo.
--Brian (mobile)
On Mar 13, 2009, at 4:38 PM, Kaveh Goudarzi wrote:
Hi Brian,
I will look in
Hi Brian,
I will look in to what is involved in publishing the plugin to a
repository. But failing that is there a supported way of installing a
plugin from a file asset? e.g. a combination of mvn commands such that
the repository is set up as if it had been a normal plugin download?
tha
Hi,
I released Modello 1.0.1 a few days ago: any objection to upgrade Maven 2.1?
There was no risky change [1].
But we would benefit from an enhanced xdoc format [2].
Regards,
Hervé
[1] http://modello.codehaus.org/release-notes.html
[2]
http://modello.codehaus.org/modello-plugins/modello-plu
Ah, I see. The install-file doesn't understand what should be done for
plugins, which is why it's there for you but not someone else. Why not
publish this plugin to a repo that your users can access? It will make
your life easier.
-Original Message-
From: Kaveh Goudarzi [mailto:ka...@itkaa
Can you do it with multiple compiler executions? I'm thinking something
like add all the src folders, and then exclude them in one execution and
vice-versa in the other.
-Original Message-
From: Paul Gier [mailto:pg...@redhat.com]
Sent: Friday, March 13, 2009 4:15 PM
To: Maven Developers
Yes, we are fixing it now.
-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier
Lamy
Sent: Friday, March 13, 2009 5:26 AM
To: Maven Developers List
Subject: Fwd: maven-site-plugin pre 2.0 not in maven-metadata.xml
Hi,
First sorry for cross po
Hi Brian,
In both cases the pluginGroup is added to my settings.xml e.g
~/.m2/settings.xml
--
com.my.pacakge
--
However it only appears to work if the two maven-metadata-local.xml
files exist otherwise the short-hand or non-specific-version
The build helper plugin allows me to add more source directories, but doesn't
allow me to have different compiler configurations for the different
directories. And also doesn't allow me to specify separate output directories.
I have some situations where it is useful to have two separate test
In order for maven to look in the right place for the shorthand lookup,
you need to add a pluginGroup in your settings. By default, maven only
uses org.apache.maven.plugins and org.codehaus.mojo.
-Original Message-
From: Kaveh Goudarzi [mailto:ka...@itkaa.com]
Sent: Friday, March 13, 200
Why doesn't the buildhelper plugin work for this use case? That lets you
attach many source folders.
-Original Message-
From: Paul Gier [mailto:pg...@redhat.com]
Sent: Friday, March 13, 2009 2:58 PM
To: Maven Developers List
Subject: Re: svn commit: r753302 - in
/maven/plugins/trunk/maven
Do you have an issue with it in both the compile and test-compile mojos? Or is
the test-compile mojo ok?
The test-compile mojo is where I need it because I have multiple sets of test
classes that require different compile parameters.
Jason van Zyl wrote:
-1
I don't want people to start abusi
Same w/ my builds. All OK.
-Original Message-
From: Stephane Nicoll [mailto:stephane.nic...@gmail.com]
Sent: Friday, March 13, 2009 6:09 AM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.1.0-RC2
Still working fine on corporate builds.
Thanks,
Stéphane
On Thu, Mar 12, 2009
-1
I don't want people to start abusing this and directly using multiple
source directories. This will get abused so fast and is only required
by people who have messed up systems.
On 13-Mar-09, at 8:37 AM, pg...@apache.org wrote:
Author: pgier
Date: Fri Mar 13 15:37:13 2009
New Revision:
Hi All,
I've implemented a maven plugin which when installed via the "mvn
install" command as part of the build is installed "correctly" in the
local repository. By adding the plugin group reference to the
~/.m2/settings.xml I'm able to then invoke the plugin using it's short
hand prefix or wi
Hi to all,
Which maven plugin should be use for JSP compilation ?
org.codehaus.mojo.jspc
jspc
2.0-alpha-3
or
org.codehaus.mojo
jspc-maven-plugin
1.4.6
I tried the 2.0-alpha-3 but it failed with :
[INFO]
[ERROR] BUILD E
Still working fine on corporate builds.
Thanks,
Stéphane
On Thu, Mar 12, 2009 at 12:49 AM, John Casey wrote:
> Hi again,
>
> I've corrected the four or five issues that popped up in the last couple
> days. The new RC is here:
>
> http://tinyurl.com/maven-2-1-0-RC2
> (
> https://repository.apach
Hi,
First sorry for cross posting.
But it looks the deployement through staging via nexus override/delete metadata.
I have checked and there is the same issue with the ear plugin
(recently deployed with the new process).
Is-it possible to fix that ? (and restoring correct metadata ? )
Thanks,
--
Hi Dennis,
Dennis Lundberg wrote at Freitag, 13. März 2009 00:46:
> I saw in one of the issues that it would be good to upgrade, but the
> newest version of XStream I could find in the central repo was 1.2.2 at:
>
> http://repo1.maven.org/maven2/xstream/xstream/
>
> Is there a newer version som
21 matches
Mail list logo
