I feel this is the most important bug that needs to be fixed. We make heavy
use of version ranges and without this fix they are unusable (we have to
manually apply a patch to each maven release).
"1) You wish a release build with no snapshots which is the normal behaviour
and so you just build t
"..It's crazy that version ranges are still unusable in 2.0.8.."
Exactly, we really need this fixed, can we apply this patch so we can use
version ranges and snapshots. This issue is killing us.
-Dave
mihobson wrote:
>
> On 10/01/2008, Michael McCallum <[EMAIL PROTECTED]> wrote:
>> another th
On Jan 18, 2008, at 12:32 PM, Brian E. Fox wrote:
-Original Message-
From: David Blevins [mailto:[EMAIL PROTECTED]
Is there any way to get or make a tree of Artifact objects?
I've tried taking the list of Artifacts returned from
project.getArtifacts(), then wrapping them in my own "nod
We are at a critical point with our usage of maven. We cannot update to
2.0.8 because 2.0.8 is broken with respect to the release plugin; RE
MNG-3351 (no releases are possible if using version ranges).
However we need to upgrade to 2.0.8 because we now have large projects that
are tripping all
Sounds perfect for me. Thanks John!
Vincent
2008/1/18, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Author: jdcasey
> Date: Fri Jan 18 11:06:04 2008
> New Revision: 613227
>
> URL: http://svn.apache.org/viewvc?rev=613227&view=rev
> Log:
> Renaming tests for error-reporting, so they're (hopefully) sho
+1
--jason
On Jan 17, 2008, at 3:22 PM, Daniel Kulp wrote:
Well, I'd prefer to not get into "version number" arguments as it
really
just doesn't matter.Hell, we have plugins (like the release
plugin,
dependency plugin, etc..) that EVERYONE uses that haven't had a real
release and ot
Dependency:tree
Or programmatically use the maven-dependency-tree jar.
-Original Message-
From: David Blevins [mailto:[EMAIL PROTECTED]
Sent: Friday, January 18, 2008 3:16 PM
To: Maven Developers List
Subject: Tree/graph of Artifact objects
Is there any way to get or make a tree of Arti
Is there any way to get or make a tree of Artifact objects?
I've tried taking the list of Artifacts returned from
project.getArtifacts(), then wrapping them in my own "node" object and
relinking them via the info in the dependency trail. This works fine
except that there is some informatio
Thanks Emmanuel! Responses inlined...
Emmanuel Venisse wrote:
Hi Rahul,
After few days to look at JPA, I'm sure now it would be good to use it
instead of the actual JDO/JPOX (I know JPOX 1.2 support JPA).
The code is very easy to write and to read with JPA.
About your continuum-jpa branch, I
+1
dkulp wrote:
>
>
> I'd like to release maven-shade-plugin 1.0-beta-1 as I kind of need it
> for some of my projects. I think Geronimo may need it as well.
>
> This fixes a couple issues we'e run into:
>
> ** Bug
> * [MSHADE-11] - Shaded jars are not unjarrable
> * [MSHADE-13] -
I'll get it fixed. I always forget about the constraints on windows
platforms...
On Jan 18, 2008, at 2:36 AM, Rahul Thakur wrote:
Hi,
There seems to be resources under:
maven-embedder\src\test\error-reporting-projects
\testReportUnresolvableArtifactWhileAddingExtensionPlugin\local-repo
\org
Hi Rahul,
After few days to look at JPA, I'm sure now it would be good to use it
instead of the actual JDO/JPOX (I know JPOX 1.2 support JPA).
The code is very easy to write and to read with JPA.
About your continuum-jpa branch, I have few remarks:
- I don't think it's good to use directly some O
Hi,
I'm progressing with the XWiki parser but I have to take a decision.
The XWiki image macro accepts several parameters:
http://code.xwiki.org/xwiki/bin/view/Macros/ImageMacro
However the Sink figure events only accepts a location and a caption.
I can see only 2 solutions:
1) Do not generat
yBenjamin Bentmann wrote:
>> There seems to be resources under:
>>
> maven-embedder\src\test\error-reporting-projects\testReportUnr
> esolvableArtifactWhileAddingExtensionPlugin\local-repo\org\apa
> che\maven\errortest\testReportUnresolvableArtifactWhileAddingE
> xtensionPlugin-maven-plugin
>>
>>
John,
I am unable too to do a fresh svn co from D:\t which t is the trunks.
As mentioned, the pb is in the error-reporting-projects:
D:\t\components\maven-embedder\src\test\error-reporting-projects\ ...
We need to allow a check out to a root directory without problem.
Could you reduce the dir nam
Brian E. Fox wrote:
It's not entirely true that versions don't matter. Alpha or Beta is
really a less important distinction and we are generally trying to move
away from more alpha/beta releases. I would argue that since Maven
requires Shade to release, that the current version should be 1.0 not
There seems to be resources under:
maven-embedder\src\test\error-reporting-projects\testReportUnresolvableArtifactWhileAddingExtensionPlugin\local-repo\org\apache\maven\errortest\testReportUnresolvableArtifactWhileAddingExtensionPlugin-maven-plugin
that causes the checkout to fail under windows.
17 matches
Mail list logo