You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Anuerin Diaz <ra...@gmail.com> on 2005/11/08 17:24:01 UTC

[m2] assembly:directory requires an install?

hi,

   does the assembly:directory goal really need the project's
sub-module artifacts to be installed in the local repository before it
will assemble them? i am a little confused becase a couple of days ago
i dont remember needing to install the sub-module artifacts prior to
calling the assembly:directory goal.

    my project has a parent project that defines two sub-modules in
its modules element. module2 depends on module1. my assembly call now
fails when trying to package module2 because it couldn't  resolve
"my.app:module1:1.0:jar". invoking "mvn package" does not produce any
problem. while "mvn install assembly:directory" will work, i am
putting this as a last resort because this might  have some
implication on our version management.

    thanks.

ciao!

--

"Programming, an artform that fights back"

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Preventing some tests from compiling

Posted by Benedict Heal <bh...@benedictheal.com>.
Brilliant. Thanks so much.
Should I have been able to find this in any documentation?
Benedict

Nik Gonzalez wrote:

> Hi Benedict,
>
>  <plugins>
>            <plugin>
>                <groupId>org.apache.maven.plugins</groupId>
>                <artifactId>maven-compiler-plugin</artifactId>
>                <configuration>
>                    <testExcludes>
>                        <testExclude 
> implementation="java.lang.String">**/App*.java</testExclude>
>                    </testExcludes>
>                </configuration>
>             </plugin>
>         </plugins>
>
> Thanks,
> -Nik
> Benedict Heal wrote:
>
>>
>>
>> How do I prevent some of my tests from compiling? (there's a 
>> temporary problem with a .jar).
>>
>> Restricting the compiler seems to affect only the application source:
>>       <plugin>
>>            <groupId>org.apache.maven.plugins</groupId>
>>            <artifactId>maven-compiler-plugin</artifactId>
>>
>> Restricting surefire seems to affect just which compiled tests get run
>>             <plugin>
>>            <artifactId>maven-surefire-plugin</artifactId>
>>
>> Presumably I need to restrict the compiler:testCompile in some way?
>>
>> Many thanks,
>> Benedict
>>        
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Preventing some tests from compiling

Posted by Nik Gonzalez <ng...@exist.com>.
Hi Benedict,

  <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <testExcludes>
                        <testExclude 
implementation="java.lang.String">**/App*.java</testExclude>
                    </testExcludes>
                </configuration>
             </plugin>
         </plugins>

Thanks,
-Nik
Benedict Heal wrote:

>
>
> How do I prevent some of my tests from compiling? (there's a temporary 
> problem with a .jar).
>
> Restricting the compiler seems to affect only the application source:
>       <plugin>
>            <groupId>org.apache.maven.plugins</groupId>
>            <artifactId>maven-compiler-plugin</artifactId>
>
> Restricting surefire seems to affect just which compiled tests get run
>             <plugin>
>            <artifactId>maven-surefire-plugin</artifactId>
>
> Presumably I need to restrict the compiler:testCompile in some way?
>
> Many thanks,
> Benedict
>        
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Preventing some tests from compiling

Posted by Benedict Heal <bh...@benedictheal.com>.

How do I prevent some of my tests from compiling? (there's a temporary 
problem with a .jar).

Restricting the compiler seems to affect only the application source:
       <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>

Restricting surefire seems to affect just which compiled tests get run
             <plugin>
            <artifactId>maven-surefire-plugin</artifactId>

Presumably I need to restrict the compiler:testCompile in some way?

Many thanks,
Benedict
         

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org