There was an integration with fisheye and our SVN before but I think that
Ben (aka Codehaus) had a lot of performances issues with it.
I found an old maven repo in fisheye but it is no more updated that's
probably why it isn't configured in the project :
https://fisheye.codehaus.org/changelog/maven
Hello, maven dev,
A while a go, I introduced alternate local repo at
dependency:copy/unpack time. It is now not working for maven 3, any
help/advice on how to fix this issue is greatly appreciated
http://jira.codehaus.org/browse/MDEP-313
Thanks
-Dan
---
I reverted this monstrosity and fixed things up. I apologize, I have
no idea what autopilot caused me to run the reformat.
On Sat, Jun 4, 2011 at 7:51 PM, Stephen Connolly
wrote:
> that is a lot of diff... we prefer to keep reformat commits separate from
> changes
>
> - Stephen
>
> ---
> Sent fro
Stephen,
It's not as much diff as it looks. It's the result of removing tabs
with m-x untabify in emacs. I take another run at it if you like.
Obviously, I'm going to need a smaller hammer for being sure that I
haven't added any tabs.
--benson
On Sat, Jun 4, 2011 at 7:51 PM, Stephen Connolly
that is a lot of diff... we prefer to keep reformat commits separate from
changes
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 4 Jun 2011 23:14, wrote:
> Author: bimargu
I have been. Did I miss one?
This is generally a job for fisheye, after all.
On Sat, Jun 4, 2011 at 7:45 PM, sebb wrote:
> On 4 June 2011 22:02, Dennis Lundberg wrote:
>> On 2011-06-04 22:44, Benson Margulies wrote:
>>> Dennis,
>>>
>>> Points taken. The web page with developer guidance does spe
On 4 June 2011 22:02, Dennis Lundberg wrote:
> On 2011-06-04 22:44, Benson Margulies wrote:
>> Dennis,
>>
>> Points taken. The web page with developer guidance does specifically
>> give the syntax:
>>
>> [JIRA1, JIRA2, ...] comments
>
> Indeed they do.
> Looks like I have some site docs to update
I'm tagged with this, but I have no idea what my change to the changed
plugin could have done to start this cascade of failures. Help?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev
On Sat, Jun 4, 2011 at 4:16 PM, Olivier Lamy wrote:
> Hello,
> Perso, I usually use invoker plugin (more easy to test with various
> maven core version)
>
Sure, for an integration test. I was striving for a smaller-scale unit
test. I even succeeded :-)
> 2011/6/4 Benson Margulies :
>> Anyone got
oops. Well, sicne I see no reason not to keep it, I'll fix the since.
On Sat, Jun 4, 2011 at 5:22 PM, Dennis Lundberg wrote:
> Note that if we decide to keep this patch, the @since tags needs to be
> updated to 2.6.
>
> On 2011-06-04 20:13, bimargul...@apache.org wrote:
>> Author: bimargulies
>>
Oddly, I can open, close, and edit issues, but I can't assign them to myself.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I was editing the POM in aquamacs, where I thought I had banished all tabs.
On Sat, Jun 4, 2011 at 5:30 PM, Robert Scholte wrote:
>
> IIRC, Eclipse Helios has splitted the way of indentation for javacode and
> XML. I had to set it by hand for XML in the past.
>
> -Robert
>
>> From: bimargul...@g
IIRC, Eclipse Helios has splitted the way of indentation for javacode and XML.
I had to set it by hand for XML in the past.
-Robert
> From: bimargul...@gmail.com
> Date: Sat, 4 Jun 2011 17:10:23 -0400
> Subject: Re: svn commit: r1131491 - /maven/pom/trunk/maven/pom.xml
> To: dev@maven.apache.
Actually, we do. MPOM on the apache jira.
Please consider this a 'heads up' for the maven pom.
On Sat, Jun 4, 2011 at 5:16 PM, Dennis Lundberg wrote:
> On 2011-06-04 22:46, Benson Margulies wrote:
>> In rev 1131491 I made the changes to this POM for Java 1.5. I'd like
>> to release it. Shall I
Note that if we decide to keep this patch, the @since tags needs to be
updated to 2.6.
On 2011-06-04 20:13, bimargul...@apache.org wrote:
> Author: bimargulies
> Date: Sat Jun 4 18:13:08 2011
> New Revision: 1131456
>
> URL: http://svn.apache.org/viewvc?rev=1131456&view=rev
> Log:
> [MCHANGES-24
On 2011-06-04 22:46, Benson Margulies wrote:
> In rev 1131491 I made the changes to this POM for Java 1.5. I'd like
> to release it. Shall I run the release process and call a vote?
We usually give a heads up on the dev list before we intend to make a
release, to allow others to make changes to th
I personally gave a no-tab policy, I will have to figure out how I got
a tab into there.
On Jun 4, 2011, at 5:01 PM, Dennis Lundberg wrote:
> Yes, let's move to Java 5 across the board!
>
>
> Benson, we have a no-tab code style here at the Maven project. You can
> find code style guidelines here
On 2011-06-04 22:44, Benson Margulies wrote:
> Dennis,
>
> Points taken. The web page with developer guidance does specifically
> give the syntax:
>
> [JIRA1, JIRA2, ...] comments
Indeed they do.
Looks like I have some site docs to update :)
>
> --benson
>
>
> On Sat, Jun 4, 2011 at 4:33 PM
Yes, let's move to Java 5 across the board!
Benson, we have a no-tab code style here at the Maven project. You can
find code style guidelines here:
http://maven.apache.org/developers/conventions/code.html
and Maven code style templates for Eclipse and IDEA here:
http://maven.apache.org/develop
In rev 1131491 I made the changes to this POM for Java 1.5. I'd like
to release it. Shall I run the release process and call a vote? Before
I do that, what JIRA should cover this POM, I'll add an
issueManagement section.
-
To unsu
Dennis,
Points taken. The web page with developer guidance does specifically
give the syntax:
[JIRA1, JIRA2, ...] comments
--benson
On Sat, Jun 4, 2011 at 4:33 PM, Dennis Lundberg wrote:
> On 2011-06-04 22:16, sebb wrote:
>> On 4 June 2011 21:04, Dennis Lundberg wrote:
>>
>> ...
>>
>>> 2. Pl
On 2011-06-04 22:16, sebb wrote:
> On 4 June 2011 21:04, Dennis Lundberg wrote:
>
> ...
>
>> 2. Please use the following form for the commit messages:
>>
>> []
>>
>> for example:
>>
>> [MCHANGES-254] Example doesn't work - spaces not allowed in statusIds
>> and resolutionIds after a comma
>
>
On 4 June 2011 21:04, Dennis Lundberg wrote:
...
> 2. Please use the following form for the commit messages:
>
> []
>
> for example:
>
> [MCHANGES-254] Example doesn't work - spaces not allowed in statusIds
> and resolutionIds after a comma
+1
It would be useful to have done this for r1131484
Hello,
Perso, I usually use invoker plugin (more easy to test with various
maven core version)
2011/6/4 Benson Margulies :
> Anyone got an example of using the harness on a reporting plugin? I'm
> a bit stalled when the mock project can't resolve the skin.
>
> -
Hi Benson and welcome aboard!
A have couple of notes on this commit.
1. Please try to limit your commits to only one issue per commit. It
makes it easier for the rest of us to review the commits.
2. Please use the following form for the commit messages:
[]
for example:
[MCHANGES-254] Example
The only thing we should take care is to note the upgrade in the cahngelog
of each plugin updated as it could avoid the upgrade for some users using an
old maven version with Java 4 ?
On Sat, Jun 4, 2011 at 10:00 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I say bop at the hi
I say bop at the highest level, if someone has an objection they can veto...
the only exception is if you are changing a dependency of core to a
different license (in which case if the new license is out of a specified
white list, the pmc must vote on the license change)
- Stephen
---
Sent from
So I could bop the cobertura version in the overall maven parent pom?
Or just in the plugin pom?
On Sat, Jun 4, 2011 at 2:44 PM, Olivier Lamy wrote:
> Imho not
> I usually move code to 1.5 when working on releasing something
>
> --
> Olivier
> Le 4 juin 2011 20:08, "Benson Margulies" a écrit :
>
Anyone got an example of using the harness on a reporting plugin? I'm
a bit stalled when the mock project can't resolve the skin.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...
Imho not
I usually move code to 1.5 when working on releasing something
--
Olivier
Le 4 juin 2011 20:08, "Benson Margulies" a écrit :
> Some versions of plugins in the parent are still constrained,
> according to comment, by a desire to support java 1.4. Is this still
> policy?
>
> --
Does Codehaus JIRA support adding SVN commit messages to issues?
I've yet to see any such entries, but in the ASF JIRA this is used extensively.
IMO it's a very useful feature - makes it much easier to follow what
happened to an issue later on.
I don't know whether the feature is not available,
Some versions of plugins in the parent are still constrained,
according to comment, by a desire to support java 1.4. Is this still
policy?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
nike principal
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 4 Jun 2011 18:26, "Benson Margulies" wrote:
> Anyone object if I do something about this? What's the procedur
Anyone object if I do something about this? What's the procedure for
releasing the plugin parent? Do we attempt to test many plugins on it
first? If I bother to change it, I'd update plugin versions in it.
[ERROR] Error fetching link:
http://download.oracle.com/javase/1.4.2/1.4.2/docs/api/package-
Benson,
Can you try again?
Since Jim is quite busy with the OO stuff, I figured I'd help him out and
added you to the group in LDAP.
Dan
On Saturday, June 04, 2011 9:11:16 AM Benson Margulies wrote:
> Been there, done that. I fear that Jim's temporary belief that I had
> been elected to the
Been there, done that. I fear that Jim's temporary belief that I had
been elected to the PMC led him to neglect to actually edit me into
access.
/Users/benson/asf/maven-deploy-plugin svn info
Path: .
URL: https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-deploy-plugin
Repository Root: htt
On Sat, Jun 4, 2011 at 9:04 AM, Benson Margulies wrote:
> I don't seem to have commit karma:
Double check that you have it checked out from the https:// url?
(What does svn info say?)
--
Wendy
-
To unsubscribe, e-mail: dev-uns
I don't seem to have commit karma:
Sendingsrc/main/java/org/apache/maven/plugin/deploy/DeployFileMojo.java
svn: Commit failed (details follow):
svn: access to
'/repos/asf/!svn/ver/1126386/maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/apache/maven/plugin/deploy/DeployFileMojo.
38 matches
Mail list logo
