I'm writing a plugin, which I want to execute during the process-
resources phase. However, I can't seem to get the plugin to execute
automatically during process-resources — the @phase annotation seems
not to work as documented.
According to the docs (and looking at the Maven source code),
Arnaud,
Let me know how the alpha-15-SNAPSHOT went and then once we are
sync'd up andy and I will track down the problem for you.
Jason.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PRO
We use the changes plugin but only the changes.xml report generator.
+1 on your changes.
On 12/26/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
Is anyone actually using this because I'd like to sync this up with
the reporting we're doing for voting. The JIRA stuff in the changes
plugin is n
On 26 Dec 06, at 8:29 PM 26 Dec 06, Luke Blanshard wrote:
Brian E. Fox wrote:
I can do the maven-dependency-plugin release. I have a few mojos that
need some more tests and then I need to update the site and it's
ready.
Hi Brian,
You wrote this on October 27th. I'm a maven newbie, but as
Brian E. Fox wrote:
I can do the maven-dependency-plugin release. I have a few mojos that
need some more tests and then I need to update the site and it's ready.
Hi Brian,
You wrote this on October 27th. I'm a maven newbie, but as far as I
can tell it hasn't happened yet. Can you give
On 26 Dec 06, at 4:50 PM 26 Dec 06, Brett Porter wrote:
Hi,
I'd like to propose two things:
1) Establish a list of emeritus committers.
2) Remove inter-project commit restrictions
The first does not depend on the second. But I think the second
does depend on the first. I would like to put
+1
You can do the same for m1 ;-)
Arnaud
On 12/27/06, Brett Porter <[EMAIL PROTECTED]> wrote:
+1
On 27/12/2006, at 11:59 AM, Jason van Zyl wrote:
> Hi,
>
> Is anyone actually using this because I'd like to sync this up with
> the reporting we're doing for voting. The JIRA stuff in the change
+1
On 27/12/2006, at 11:59 AM, Jason van Zyl wrote:
Hi,
Is anyone actually using this because I'd like to sync this up with
the reporting we're doing for voting. The JIRA stuff in the changes
plugin is now obsoleted by the Swizzle (it just kicks ass), and I
would like to remove the mail
Hi,
There is a proposal to add the following properties for continuum to
pass to m2 builds:
properties.setProperty("continuum.project.group.name",
project.getProjectGroup().getName());
properties.setProperty("continuum.project.lastBuild.state",
String.valueOf(project.getOldState()));
prop
Hi,
Is anyone actually using this because I'd like to sync this up with
the reporting we're doing for voting. The JIRA stuff in the changes
plugin is now obsoleted by the Swizzle (it just kicks ass), and I
would like to remove the mail sending stuff and put it in an
announcement component
+1
On 27/12/2006, at 11:32 AM, Jason van Zyl wrote:
Ok, headers updated.
This release contains the changes required for deploying to staging
repositories. So I would like to release this so that I can remove
the SNAPSHOT from the profile that will be used for release staging.
Revision: 4
Hi Jesse,
I see you took this one a couple of months ago. It looks like a good
feature - is the patch a good enough start to use for now?
It was submitted by John Didion - John, are you hanging around? Are
you able to help get that applied and work through some of the
limitations?
I'm p
Ok, headers updated.
This release contains the changes required for deploying to staging
repositories. So I would like to release this so that I can remove
the SNAPSHOT from the profile that will be used for release staging.
Revision: 490414
Roadmap: http://jira.codehaus.org/browse/MDEPLOY
Guys,
I just did a clean install of CentOS (redhat linux), a fresh download
of 2.0.4, no existing local repository, with java 1.5 and I get
failures in both the EAR and Eclipse plugins. Do you both happen to
use Windows? As the failures occur on my OS/X box and my Linux VM
(running Paral
On 12/26/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
I have all of archetype build from source locally. To get it to work,
I have to add
-DgroupId=org.apache.maven.archetypes
to the mvn archetype:create command line.
Should be: -DarchetypeGroupId=org.apache.maven.archetypes
--
Wendy
-
The archetypes (such as maven-archetype-quickstart) are now in group
org.apache.maven.archetypes (with an 's').
From mvn archetype:create, I get:
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org
On 26 Dec 06, at 3:54 PM 26 Dec 06, Brett Porter wrote:
I had no specific objections once the 2.1-SNAPSHOT dependency was
removed.
There are 2 open issues for the current version, though, and I'm a
bit concerned at releasing it as "final" when there are 64 other
issues open. Should it sti
Hi,
I'd like to propose two things:
1) Establish a list of emeritus committers.
2) Remove inter-project commit restrictions
The first does not depend on the second. But I think the second does
depend on the first. I would like to put each to a separate vote once
all the pros and cons have b
rahul and I have been talking on skype some working out some of the
details of this key refactor and we see an opportunity to do a few
things that might make life better for continuum.
He is going to mail soon on some things that we are wanting to do in
the store and this mail is one something to
-1: License headers still need to be updated.
I also think a couple of the other issues in JIRA could be knocked
off quickly first, but not as critical..
Cheers,
Brett
On 26/12/2006, at 2:21 PM, Jason van Zyl wrote:
This release contains the changes required for deploying to staging
repos
so you agree with me ;)
seriously, the only reason to allow users without passwords would be
to show a customized page, and we don't have that
On 12/26/06, Jesse McConnell <[EMAIL PROTECTED]> wrote:
windows? :)
On 12/26/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> That's why they can give p
I had no specific objections once the 2.1-SNAPSHOT dependency was
removed.
There are 2 open issues for the current version, though, and I'm a
bit concerned at releasing it as "final" when there are 64 other
issues open. Should it still be beta?
- Brett
On 26/12/2006, at 2:54 PM, Jason va
windows? :)
On 12/26/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
That's why they can give permissions to the guest user.
I haven't seen any app that allows empty passwords for users.
On 12/26/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 26 Dec 06, at 10:58 AM 26 Dec 06, Jesse McConnell
That's why they can give permissions to the guest user.
I haven't seen any app that allows empty passwords for users.
On 12/26/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 26 Dec 06, at 10:58 AM 26 Dec 06, Jesse McConnell wrote:
> imo, yes :)
>
> only the administrator has the ability to ma
On 26 Dec 06, at 2:33 PM 26 Dec 06, Fabrizio Giustina wrote:
Did you noticed the strange error in the log?
Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-
plugin:test:eclipse.
I never got a similar error,
Did you noticed the strange error in the log?
Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugin:test:eclipse.
I never got a similar error, do you have any idea where is that
"org.apache.maven.plugin.Mojoor
Cool - Why don't we take a look together a little
later on, as soon as I get all the mappings finished
up?
Here's a brief overview of the approach I'm using:
- Create an Ecore (Eclipse EMF Project) of the
parameters that the Spec file needs
- Set defaults that are specific to the JPackage
project
On 26 Dec 06, at 4:51 AM 26 Dec 06, Fabrizio Giustina wrote:
Hi Jason,
if you look at the logs in the build-output dir you will see that the
cause for the failure is simply the missing parent pom (version 7),
can you retry after installing/deploying it?
There are now two failures:
http://id
On 26 Dec 06, at 4:51 AM 26 Dec 06, Fabrizio Giustina wrote:
Hi Jason,
if you look at the logs in the build-output dir you will see that the
cause for the failure is simply the missing parent pom (version 7),
can you retry after installing/deploying it?
It's installed and deployed and I sti
It should of at the least taken it off my machine. It was installed
because I did the WAR plugin before that.
I'll try again. Is it trying to take it from the remote repo and not
the local repo? I could understand it not working if it wasn't
deployed to central but it should work if it's in
[EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Wed Dec 20 18:21:05 2006
New Revision: 489248
URL: http://svn.apache.org/viewvc?view=rev&rev=489248
Log:
Modifying to delete the test version of the plugin from the target directory
after it's installed in the test-time local repo.
Modified:
The reason I mentioned it is that the plugin WRITES the spec file it uses.
You might want to see how I mapped POM elements into the spec file. There
is likely to be a difference in how we are doing things, in which case it
would be good to use a uniform mapping of elements.
- Original Mes
that's ok.
Merry christmas!
^_^
TslH wrote:
"Awfully" was not the right word, I apologize. Another trick played by my
bad english ;)
2006/12/26, Edwin Punzalan <[EMAIL PROTECTED]>:
The site was last published Nov 7... and the source repository was moved
Dec 20.
Its just "a bit" outdated.
"Awfully" was not the right word, I apologize. Another trick played by my
bad english ;)
2006/12/26, Edwin Punzalan <[EMAIL PROTECTED]>:
The site was last published Nov 7... and the source repository was moved
Dec 20.
Its just "a bit" outdated... the next site deploy would fix it, thanks.
^
The site was last published Nov 7... and the source repository was moved
Dec 20.
Its just "a bit" outdated... the next site deploy would fix it, thanks.
^_^
TslH wrote:
Erm.
Thanks Edwin. :)
Someone should correct informations at
http://maven.apache.org/plugins/maven-surefire-plugin/sour
Erm.
Thanks Edwin. :)
Someone should correct informations at
http://maven.apache.org/plugins/maven-surefire-plugin/source-repository.html,
since it's awfully outdated.
Have a nice day.
2006/12/26, Edwin Punzalan <[EMAIL PROTECTED]>:
try here: http://svn.apache.org/repos/asf/maven/surefire/tr
try here: http://svn.apache.org/repos/asf/maven/surefire/trunk
^_^
TslH wrote:
Hello,
I wanted to have a look to Surefire plugin, in order to see why TestNG
5.xdon't work with it. But when I browsing SVN, I can't find surefire
sources.
I'm trying to get them through:
http://svn.apache.org/re
Hallo MDA users,
I am doing MDA with Maven. Time Tracker has successfully started
but when i try to test the application while opening in Browser using the
following link:
http://localhost:3306/timetracker
I am getting page could not find error and some times time tracker file is
opening if i
Hello,
I wanted to have a look to Surefire plugin, in order to see why TestNG
5.xdon't work with it. But when I browsing SVN, I can't find surefire
sources.
I'm trying to get them through:
http://svn.apache.org/repos/asf/maven/plugins/trunk/
Have the sources moved?
Thanks for your help.
Tom.
Hi Jason,
if you look at the logs in the build-output dir you will see that the
cause for the failure is simply the missing parent pom (version 7),
can you retry after installing/deploying it?
[INFO]
[ERROR] BUILD ERROR
[IN
40 matches
Mail list logo
