n Developers List'
> Subject: RE: RC2 - multiproject build issues?
>
> Hard to tell - but search JIRA first because I'm sure someone
> would already have come across this if it's a problem.
>
> Thanks,
> Brett
>
> > -Original Message-
> > Fr
Brett Porter [mailto:[EMAIL PROTECTED] wrote:
> > Using the latest RC2 bits, when I do a "maven
> > multiproject:install-snapshot", it builds project A, but
> then when it
> > builds project B (which has a dependency on project A), it
> downloads
> > the snapshot from the remote repository rat
Using the latest RC2 bits, when I do a "maven
multiproject:install-snapshot", it builds project A, but then when it
builds project B (which has a dependency on project A), it downloads the
snapshot from the remote repository rather than using the snapshot I
just built for project A. Is anyone else
Is anyone successfully using Clover with the RC2 bits? I'm getting the
following error when I try and do a "maven clover:report":
Reference maven.test.compile.src.set not found.
Also, some tags are getting echoed out when the task starts, so I assume
they're not being recognized. I'm seeing the
Hold that thought...I'm an idiot...built the wrong branch. Let me build
anew before bothering you again with my trivial stupidities... ;)
> -Original Message-
> From: Sean Timm
> Sent: Wednesday, February 04, 2004 12:05 PM
> To: [EMAIL PROTECTED]
> Subject: RC2 -
I've got a project-base.xml file that sets up my basic, generic
information (including build/SourceDirectory). I've got a
project-component.xml that extends this but does not contain the build
node at all. I then have a component-specific project.xml that extends
project-component.xml. My expect
> > A comment on MAVEN-256
> > (http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-256)
> > indicates a fix for goals executed via attainGoal being called
> > multiple times. Is this something I can move forward with
> (ie. update
> > a few plugins that are causing me grief and submit pa
maven
> Components:
> plugin-clover
>Fix Fors:
> 1.0-rc2
>Versions:
> 1.0-rc2
>
>Assignee: Vincent Massol
>Reporter: Sean Timm
>
> Created: Fri, 14 Nov 2003 4:00 PM
> Updated: Sat, 15 Nov 2003 4:0
A comment on MAVEN-256
(http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-256) indicates
a fix for goals executed via attainGoal being called multiple times. Is
this something I can move forward with (ie. update a few plugins that
are causing me grief and submit patches), or is there a plan
Just started using the Dashboard plugin...very nice! :) I'd love to
see the individual cells turn into clickable links that take you to the
generated HTML report for a given project, eventually. I'll probably
try and tackle this someday if someone doesn't get around to it sooner,
but I figured I
I'm hosting an in-house remote repository via Apache 2 on a Windows
server. I recently ran into an issue where a few projects specified the
name of a dependency with the wrong case (all lowercase instead of
mixed-case). The remote repository still treats it as a valid filename
and returns the dep
> > I've successfully setup an in-house remote repository along with a
> > central Maven distribution provided via our source control
> system. At
> > this time, I can update a jar in the maven distribution's plugin
> > folder, and then when someone runs a build, they'll get the latest
> > ve
I've successfully setup an in-house remote repository along with a
central Maven distribution provided via our source control system. At
this time, I can update a jar in the maven distribution's plugin folder,
and then when someone runs a build, they'll get the latest version
installed if they don
better.
You can even omit basedir in rc1.
- Brett
> -Original Message-
> From: Sean Timm [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 October 2003 10:49 AM
> To: Maven Developers List
> Subject: RE: POM Build Resources and Path Problems
>
>
> I'm using R
ndows. This sounds
unrelated.
What does your section look like? What version of maven?
- Brett
> -Original Message-
> From: Sean Timm [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 October 2003 10:13 AM
> To: [EMAIL PROTECTED]
> Subject: POM Build Resources and Path Problems
&
I was having some bizarre issues where the jar plugin was grabbing
everything in my project folder as a resource, and I finally tracked it
down to a problem with the '/' vs. the '\' in a directory. By default,
maven.build.dir is set to something like the following:
C:\mySource\currentDirectory/tar
to this problem? Is this a known issue?
Thanks!
--
Sean Timm
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This is with the RC1 version, btw...
> -Original Message-
> From: Sean Timm
> Sent: Wednesday, October 15, 2003 11:04 AM
> To: [EMAIL PROTECTED]
> Subject: Context variables only available if plugin
> previously loaded...
>
> I've run into a problem while
The problem seems
to be that the java plugin never gets accessed, so these variables are
empty. If I do the following instead, everything works:
maven java:compile cactus:compile
Is this a known issue? I made an account on Jira to look up
bugs...should I be logging issues I run into there
19 matches
Mail list logo
