run mvn dependency:tree, I wanna see something.

VELO

On Tue, Jan 20, 2009 at 10:02 PM, Richard Rodseth <[email protected]>wrote:

> No, I tried it because Logan's concrete example used it, and I thought it
> was some uber-artifact. I already had this:
>
>         <build>
>             <plugins>
>                 <plugin>
>                     <groupId>info.flex-mojos</groupId>
>                     <artifactId>flex-compiler-mojo</artifactId>
>                     <dependencies>
>                         <dependency>
>                             <groupId>com.adobe.flex</groupId>
>                             <artifactId>compiler</artifactId>
>                             <version>3.1.0-fb3</version>
>                             <type>pom</type>
>                         </dependency>
>                     </dependencies>
>                 </plugin>
>             </plugins>
>         </build>
>
> giving this:
>
> Missing:
> ----------
> 1) com.adobe.flex.compiler:adt:jar:3.2.0.3958
>
> You said I could override dependencies specified in the super-pom. If the
> above does not do so, then I guess I need to go and find the super pom and
> try to guess what you meant.
>
>
>
> On Tue, Jan 20, 2009 at 3:49 PM, Marvin Froeder <[email protected]> wrote:
>
>> flex-maven-plugin?!
>>
>> That is not the artifactId you used a few hours ago!
>>
>>         <build>
>>>             <plugins>
>>>                 <plugin>
>>>                     <groupId>info.flex-mojos</groupId>
>>>                     <artifactId>flex-compiler-mojo</artifactId>
>>>                     <configuration>
>>>                         <mergeResourceBundle>false</mergeResourceBundle>
>>>                     </configuration>
>>>                 </plugin>
>>>             </plugins>
>>>         </build>
>>>
>>
>>
>> VELO
>>
>>
>> On Tue, Jan 20, 2009 at 9:44 PM, Richard Rodseth <[email protected]>wrote:
>>
>>>  More confusion for moi. flex-maven-plugin is not available at
>>> info.flex-mojos, so this (which I thought your suggestion implied) does not
>>> work:
>>>
>>>        <build>
>>>             <plugins>
>>>                 <plugin>
>>>                     <groupId>info.flex-mojos</groupId>
>>>                     <artifactId>flex-maven-plugin</artifactId>
>>>                     <dependencies>
>>>                         <dependency>
>>>                             <groupId>com.adobe.flex</groupId>
>>>                             <artifactId>compiler</artifactId>
>>>                             <version>3.1.0-fb3</version>
>>>                             <type>pom</type>
>>>                         </dependency>
>>>                     </dependencies>
>>>                 </plugin>
>>>             </plugins>
>>>         </build>
>>>
>>>
>>> On Tue, Jan 20, 2009 at 3:15 PM, RedBugz Software <[email protected]>wrote:
>>>
>>>>
>>>> On Tue, Jan 20, 2009 at 4:10 PM, Richard Rodseth <[email protected]>
>>>> wrote:
>>>> > Maybe the problem is I don't have 3.2 installed locally. Until I
>>>> figure out
>>>> > how to do that, can I make the super-pom use 3.1?
>>>>
>>>> Well, technically you override the super-pom's setting, but do it like
>>>> this:
>>>>
>>>> http://svn.sonatype.org/flexmojos/trunk/test-harness/projects/concept/updated-sdk/pom.xml
>>>>
>>>> You need both sections (the compiler dependency in the plugin section,
>>>> and the flex-framework dependency in the dependencies section). Just
>>>> change the version.
>>>>
>>>> Logan
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en

http://blog.flex-mojos.info/
-~----------~----~----~----~------~----~------~--~---

Reply via email to