Hi all,
I've got some unit tests in a subproject of a multiproject that run fine
when building from the subproject's basedir, but when the subproject is
built as part of the multiproject build (that is, maven is launched in the
parent directory), the basedir is that of the parent directory, and m
Thanks for the tip. Is there a JIRA on this?
baerrach wrote:
>
> On 2/7/07, matthewadams <[EMAIL PROTECTED]> wrote:
>>
>> If I have two unrelated plugins, A & B, that need to run during the same
>> build lifecycle phase, but A needs to run before B, how do I
If I have two unrelated plugins, A & B, that need to run during the same
build lifecycle phase, but A needs to run before B, how do I control that?
For example, say I needed some aspect weaving and some persistent
enhancement to go on during the process-classes phase, but I needed the
persistent
Hi all,
My plugin is failing because the classes that I'm accessing within my plugin
are not being initialized upon loading (specifically, their static
initializers are not being called). Is there some configuration setting
that I can make to cause classes that are loaded by the
org.codehaus.cla
ards
> -allan
>
>
> On 1/18/07, matthewadams <[EMAIL PROTECTED]> wrote:
>>
>> My mojo allows the user to define an extra property ("private File
>> licenseFileDirectory"), which is a directory, that I'd like to add to the
>> classpath when
My mojo allows the user to define an extra property ("private File
licenseFileDirectory"), which is a directory, that I'd like to add to the
classpath when my mojo runs so that I can find a resource (a license file)
in the given directory.
How can I programatically add this to the classpath in my
Hi all,
NB: this is mostly a sanity checking message.
I want to create a custom remote Maven repository to host our software that
uses versions in the format
.. build
For example, for version 1.2.3 build 456, is the correctly Maven2-formatted
version string "1.2.3-456"? It appears as though
owever, you
> may file an issue to: http://jira.codehaus.org/browse/MNG for this to be
> fixed.
>
> Dawn
>
>
> matthewadams wrote:
>>
>> Hi all,
>>
>> I'm using Maven 2.0.4 and the maven-antrun-plugin, and I express a
>> dependency on a
Hi all,
I'm using Maven 2.0.4 and the maven-antrun-plugin, and I express a
dependency on a version of an artifact in the plugin. If I use an exact
version number for that artifact, Maven2 succeeds. If I change the version
number from an exact version to a version range, Maven fails to resolve t
I use the assembly plugin to create a jar that contains the contents of all
jars that the application depends on. From my pom:
...
org.apache.maven.plugins
maven-assembly-plugin
Hi all,
I'm using Maven 2.0.4 and three things that I can't seem to put together
correctly: build numbers in the published remote repository, a remote
repository and version range in client project dependencies' pom.xml files.
Our company uses major.minor.revision version numbers along with bui
Dan Fabulich-2 wrote:
>
> Probably what's happening is Maven is launching a second JVM to run your
> tests.
>
> If so, you can use -DargLine="=-Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=4657" to pass
> those arguments to the launched JVM.
>
Hi,
This seems to be a FAQ, and searches on this list seem not to yield
definitive answers. I have a plain old Maven2 project whose unit tests I'd
like to debug using an IDE. I've tried launching Maven2 with debug options
set, but I never hit any breakpoints that I've set after attaching the
de
FYI, I have sent feedback to Sun requesting that the J2EE Connector
Architecture class files be rereleased under the CDDL. We'll see where this
goes...
--
View this message in context:
http://www.nabble.com/-M2--Request-for-Sun-jars-to-be-added-to-ibiblio-m2-repo-tf1977662.html#a5512591
Sent fr
Our current product is certified against JTA 1.0.1 -- we'll have to look into
certifying against 1.0.1B & then this is no longer an issue, but I don't
know when this will be. It also may not be an issue depending on the binary
compatibility between 1.0.1 and 1.0.1B.
Connector 1.5 is the latest &
I was wondering if the powers that be could add the Sun jars for JTA
(javax.transaction/jta/1.0.1) and Connector
(javax.resource/connector-api/1.5) to the central ibiblio maven2 repo. I
see that JTA 1.0.1B is there; can the previous two versions be added as well
(1.0.1A, 1.0.1)?
Thanks,
Matthew
16 matches
Mail list logo