Works fine for our builds :)
Brian E. Fox wrote:
> We made a minor tweak to the dependency order processing. See
> http://jira.codehaus.org/browse/MNG-3494 for more details.
>
>
>
> RC6 is staged at:
> http://people.apache.org/~brianf/staging-repository/org/apache
> /maven/apa che-maven/
>
>
Also, this may have been written before the dependency plugin had the
current feature set. I know when I first started using maven2 and the
dependency plugin, it only had copy, unpack, and a couple of other
goals. It didn't have everything it has now.
-Original Message-
From: Andrew Will
Also, check if you set Javadoc back to 2.0.6, whether 2.0.6 has the
same failure. IT might be it just fails before it gets to the circ
reference.
- Brett
On 02/04/2008, at 7:35 AM, Dennis Lundberg wrote:
2.0.9-RC5 works the same way as 2.0.8 does and fails with a build
error, because of t
On Wed, Apr 2, 2008 at 5:46 AM, Micah Hainline
<[EMAIL PROTECTED]> wrote:
> > So can we find a way to suit both sides?
> > - keep the tools we have running
> > and
> > - move to a unique id
>
> Not having a standard way to reference Eclipse artifacts is a continuing
> source of pain.
>
> It s
We made a minor tweak to the dependency order processing. See
http://jira.codehaus.org/browse/MNG-3494 for more details.
RC6 is staged at:
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/
--Brian
Heh, it looks to me like people who have had bad experiences with
maven but not known the tools that can help.
The command "mvn dependency:tree" would have saved them a paragraph of
rant at least!
Andy
On 31 Mar 2008, at 22:59, Jason van Zyl wrote:
I have something written but it's not very
2.0.9-RC5 works the same way as 2.0.8 does and fails with a build error,
because of the cyclic reference.
It might be the release-plugin that is at fault. It doesn't honor the -N
option, even if I specify it on the command line like this
mvn -N release:prepare -Darguments=-N -DdryRun=true
Can you try 2.0.9 RC5? Not that I expect it to be fixed, but at least if
it's reproducible we can attempt to fix it there.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2008 3:13 PM
To: Maven Developers List
Subject: [regression] Cannot releas
> So can we find a way to suit both sides?
> - keep the tools we have running
> and
> - move to a unique id
Not having a standard way to reference Eclipse artifacts is a continuing source
of pain.
It seems to me that the groupId serves quite well as an identifier for the
source of an artifact
I've stumbled upon some kind of regression trying to release the plugins
parent. I'm not sure where the regression is though. Sigh!
I have to use Maven 2.0.8, because maven-javadoc-plugin apparently
requires 2.0.8 now. But if I do the build fails with an error because of
a circular dependency.
Dennis Lundberg wrote:
Jason Dillon wrote:
Anyone know how to do this?
I did an IDEA configuration [1] for Velocity files before. Let me see if
I can make something useful for apt files...
It seems that the results of using only syntax highlighting is not very
useful for .apt files.
One
Jason Dillon wrote:
Anyone know how to do this?
I did an IDEA configuration [1] for Velocity files before. Let me see if
I can make something useful for apt files...
[1] http://wiki.apache.org/velocity/IntelliJSyntaxHighlighting
--jason
--
Dennis Lundberg
---
Hi,
Perhaps it could be related to bug 59 (
http://jira.codehaus.org/browse/ARCHETYPE-59) which is corrected in Maven
2.0.9 and archetype plugin 2.0-alpha3 ...
Regards,
Sébastien Deleuze
On Tue, Apr 1, 2008 at 3:37 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Hiya, I'm having some problem gett
Are you using the contribution that was contributed long ago? Some guy
implemented an editor for Eclipse. Eugene at one point tried to
integrate it into m2e but it wasn't quite there.
On 1-Apr-08, at 4:34 AM, Vincent Siveton wrote:
Hi Jason,
Don't know for IDEA but I am trying to do it for
Hiya, I'm having some problem getting my archetype module installed
into my local repository (haven't tried a remote deploy yet) with
a .jar extention. It always puts the archive into the repo with
a .maven-archetype ext, which causes problems when trying to actually
use the archetype:
Hi Jason,
Don't know for IDEA but I am trying to do it for Eclipse. See DOXIA-233
Cheers,
Vincent
2008/4/1, Jason Dillon <[EMAIL PROTECTED]>:
> Anyone know how to do this?
>
> --jason
>
> -
> To unsubscribe, e-mail: [EMAIL P
Anyone know how to do this?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
17 matches
Mail list logo