Alan,
We are implementing at OPS4J Pax URL a simple osgi url handler (that you
could use also outside osgi) based on Mercury. I started implementing it a
while ago but then I run into problems with Mercury so was on hold for a
while. But I will be back on development soon. Once ready the only
Hi all,
snip
Whats the JIRA ticket number?
Ah sorry it's MNG-4164. I haven't created the patch yet (trying to keep the
wording small/simple as).
Cheers,
Martijn
Hi Nicolas,
Please also log a short description of the commit in addition to the issue number,
not everybody knows by heart what a specific issue is about... ;) See [1] for a
template.
Thanks,
-Lukas
[1] http://maven.apache.org/developers/conventions/svn.html
nico...@apache.org wrote:
svn log edited
Cheers,
Nicolas
2009/5/18 Lukas Theussl ltheu...@apache.org
Hi Nicolas,
Please also log a short description of the commit in addition to the issue
number, not everybody knows by heart what a specific issue is about... ;)
See [1] for a template.
Thanks,
-Lukas
[1]
Brian Fox wrote:
It's been a little slow going, but here's an update of where I'm at:
I branched assembly 2.2-beta-4-SNAPSHOT[1] from the 2.2-beta-3 tag and
renamed the trunk to 2.2-beta-5. The runOnlyOnExecutionRoot flag has been
added to 2.2-beta-4 (MASSEMBLY-406). I created a custom
If you want to use what is going to get expelled from the Maven 3.x
core for all things to use then take a look here:
http://svn.apache.org/repos/asf/maven/components/branches/MNG-2766/maven-repository/src/main/java/org/apache/maven/repository/RepositorySystem.java
Right now in that branch it
On 18/05/2009, at 12:03 PM, Wendy Smoak wrote:
On Sun, May 17, 2009 at 3:15 PM, Brian Fox bri...@infinity.nu wrote:
Bump.
Maybe it would be better to post the info and discuss here? I don't
think people are going to keep going back to a wiki page to follow the
comments, and it would be good
On 18/05/2009, at 3:56 PM, Benjamin Bentmann wrote:
Hi Brian,
Author: brianf
Date: Mon May 18 01:15:18 2009
New Revision: 775789
URL: http://svn.apache.org/viewvc?rev=775789view=rev
Log:
add new component to hold the asf specific source descriptor
+assembly
+ idsource-release/id
+ formats
Brett Porter wrote:
On 16/05/2009, at 6:44 AM, Paul Gier wrote:
Ok, it's fixed. Thanks for the suggestions! Brian are the
requirements for the source distribution defined somewhere? So I can
make sure I'm not missing anything?
What you have now looks right to me.
I would personally
On 18/05/2009, at 10:57 PM, Ate Douma wrote:
The current descriptor produces tar.gz and zip, does anyone have
strong
feelings if this is ok or should we go with only one of them? (and
which
one?)
Why drop .bz2 in the first place?
We have been using .bz2, .tar.gz and .zip based distro
Check on the list as Brian just suggested removing that and someone
from the portals project here complained.
On 18-May-09, at 9:49 AM, Paul Gier wrote:
Brett Porter wrote:
On 16/05/2009, at 6:44 AM, Paul Gier wrote:
Ok, it's fixed. Thanks for the suggestions! Brian are the
That was the bug i mentioned that needs to be fixed first ;-)
The excludes will only work for the current project, not all child projects
if they weren't already clean. Since my intents is to insert this into the
release profile, I should be able to make it work pretty reliably. I'm
concerned
My understanding of the requirements for the source release are that they
should match identically to the source used to build the binaries. For all
intents and purposes, they should have the same content as the tag.
On Mon, May 18, 2009 at 10:06 AM, Jason van Zyl jvan...@sonatype.comwrote:
Jason van Zyl wrote:
If you want Maven specific use the RepositorySystem in that branch
(will go to trunk in a few days), and use Mercury directly if you want
something Maven independent.
In case you decided to try out Mercury - look at IT
On Mon, May 18, 2009 at 8:57 AM, Ate Douma a...@douma.nu wrote:
Brian Fox wrote:
It's been a little slow going, but here's an update of where I'm at:
I branched assembly 2.2-beta-4-SNAPSHOT[1] from the 2.2-beta-3 tag and
renamed the trunk to 2.2-beta-5. The runOnlyOnExecutionRoot flag has
Brian Fox wrote:
On Mon, May 18, 2009 at 8:57 AM, Ate Douma a...@douma.nu wrote:
Brian Fox wrote:
It's been a little slow going, but here's an update of where I'm at:
I branched assembly 2.2-beta-4-SNAPSHOT[1] from the 2.2-beta-3 tag and
renamed the trunk to 2.2-beta-5. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
Quite impressive list. So there seems to be a high demand in this topic.
Maybe we should bring some things together.
I wrote this proposal:
http://docs.codehaus.org/display/MAVENUSER/EasyVersionMaintenance
I would really love to get
Hi
There is currently a proposal over at Commons to create a specially
crafted empty artifact of Commons Logging. I'd appreciate your input on
how this would affect the normal users of commons-logging. In
particular how the proposal would affect the meta data in the central
repository, both when
The most important thing is that it has the lowest version possible, which
seems to be the case in the second proposal. When it gets deployed, the
metadata would be updated, but Nexus could correct this back to the right
version pretty easily. (you'd have to do it by hand w/o nexus).
Otherwise if
On Mon, May 18, 2009 at 5:17 PM, martijnverb...@gmail.com wrote:
Hi all,
snip
Whats the JIRA ticket number?
Ah sorry it's MNG-4164. I haven't created the patch yet (trying to keep the
wording small/simple as).
Cheers,
Martijn
Thanks,
I wanted the issue so I could watch it and maybe
I've been grappling with version-expression interpolation since before
Maven 2.1.0 (See MNG-3057, MNG-4140, and now MNG-4167). It seems that
doing this transformation within an ArtifactTransformation
implementation is a flawed concept, since it means that plugins are
using old content when
21 matches
Mail list logo
