Exactly.

franz see wrote:
> 
> Good day,
> 
> Are you saying that you added plugin dependencies for your antrun, and
> your antrun cannot see it if it's in the profile-added module?
> 
> Cheers,
> Franz
> 
> 
> takai wrote:
>> 
>> Hi Franz,
>> 
>> The profile-added module runs the integration tests. Usecase: Developer
>> usually wants to just build the project - not run the entire integration
>> test suite which takes a while. An explicit "-P integration" call is
>> needed to run them. The real reason i want to add profile specific
>> modules is to avoid cleaning them by default.
>> 
>> The profile-added module contains the antrun plugin. The plugin
>> dependencies are not accessible to the ant build files (and therefore, i
>> suppose, to the plugin).
>> 
>> Cheers,
>> Daniel
>> 
>> 
>> franz see wrote:
>>> 
>>> Good day,
>>> 
>>> Which project does not include its dependencies...the aggregating or the
>>> profile-added module? ..And which classpath?
>>> 
>>> Cheers,
>>> Franz
>>> 
>>> 
>>> takai wrote:
>>>> 
>>>> This seems to work. However i found that putting modules in the profile
>>>> somehow breaks the dependency mechanism.
>>>> 
>>>> I use the antrun plugin in an integration module. When i execute with a
>>>> regular pom or just inside the integration module everything works
>>>> fine.
>>>> 
>>>> Once i use the aforementioned module by profile approch the plugin does
>>>> not include dependencies in the classpath.
>>>> 
>>>> Using Maven 2.0.6.
>>>> 
>>>> File an issue?
>>>> 
>>>> Daniel
>>>> 
>>>> 
>>>> 
>>>> Jonathan Anstey wrote:
>>>>> 
>>>>> Try this to set up a default profile:
>>>>> 
>>>>> <profile>
>>>>>    <id>default</id>
>>>>>    <activation>
>>>>>       <activeByDefault>true</activeByDefault>
>>>>>    </activation>
>>>>>    <modules>
>>>>>    ...
>>>>>    </modules>
>>>>> </profile>
>>>>> 
>>>>> Cheers,
>>>>> Jon
>>>>> 
>>>>> Wayne Fay wrote:
>>>>>> I don't believe this is possible. Instead, I think you would need to
>>>>>> set it up as follows:
>>>>>>
>>>>>> parent/pom.xml
>>>>>> <modules/>
>>>>>> <profiles>
>>>>>> <profile>
>>>>>> <id>cpp-qa</id>
>>>>>> <modules>
>>>>>> <module>module3</module>
>>>>>> <module>module4</module>
>>>>>> </modules>
>>>>>> </profile>
>>>>>> <profile>
>>>>>> <id>default</id>
>>>>>> <modules>
>>>>>> <module>module1</module>
>>>>>> <module>module2</module>
>>>>>> <module>module3</module>
>>>>>> <module>module4</module>
>>>>>> </modules>
>>>>>> </profile>
>>>>>> </profiles>
>>>>>>
>>>>>> And then use some activation magic to decide when to turn on default
>>>>>> etc.
>>>>>>
>>>>>> No guarantee this would work as I've never done it myself, but I'm
>>>>>> fairly certain your other proposed solution will not work, so give
>>>>>> this a try.
>>>>>>
>>>>>> Wayne
>>>>>>
>>>>>> On 2/7/07, Balasubramanian, Ravi Shankar <[EMAIL PROTECTED]> 
>>>>>> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am using maven 2.0.4 and I want to be excluding certain modules
>>>>>>> while
>>>>>>> building my project in a certain profile. Following is the
>>>>>>> scenarion:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> This is how my main pom looks like:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> <?xml version="1.0" encoding="UTF-8" ?>
>>>>>>>
>>>>>>> <project xmlns="http://maven.apache.org/POM/4.0.0";
>>>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>>>>>
>>>>>>>    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>>>>>>> http://maven.apache.org/maven-v4_0_0.xsd";>
>>>>>>>
>>>>>>>    <modelVersion>4.0.0</modelVersion>
>>>>>>>
>>>>>>>    <groupId>com.informatica.metadatarepository.qa</groupId>
>>>>>>>
>>>>>>>    <artifactId>metamodels</artifactId>
>>>>>>>
>>>>>>>    <packaging>pom</packaging>
>>>>>>>
>>>>>>>    <name>${artifactId}</name>
>>>>>>>
>>>>>>>    <modules>
>>>>>>>
>>>>>>>              <module>module1</module>
>>>>>>>
>>>>>>>              <module>module2</module>
>>>>>>>
>>>>>>>              <module>module3</module>
>>>>>>>
>>>>>>>              <module>module4</module>
>>>>>>>
>>>>>>>     </modules>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>     <profiles>
>>>>>>>
>>>>>>>         <profile>
>>>>>>>
>>>>>>>           <id>cpp-qa</id>
>>>>>>>
>>>>>>>           <modules>
>>>>>>>
>>>>>>>              <module>module3</module>
>>>>>>>
>>>>>>>              <module>module4</module>
>>>>>>>
>>>>>>>           </modules>
>>>>>>>
>>>>>>>    </profile>
>>>>>>>
>>>>>>> </profiles>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> With the above pom, when I build the project activating the profile
>>>>>>> "cpp-qa", all the four modules are being built. I want to be
>>>>>>> building
>>>>>>> only module3 and module4 using certain configurations in this
>>>>>>> profile.
>>>>>>> Is there a way by which I can accomplish this in maven2?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks for any help,
>>>>>>>
>>>>>>> Ravi.
>>>>>>>
>>>>>>> "Tough times never last, but tough men do..."
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>>>
>>>>>>
>>>>> 
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Excluding-certain-modules-in-a-profile-tf3185303s177.html#a9974771
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to