MavenEmbedder and --no-plugin-updates

Hi, Sorry for cross-posting. Guess the dev list is more suitable than the users. When I'm executing a MavenEmbedder (trunk version), I have a problem with it trying to update the plugins defined in my POM. These plugins are not available when I run the embedder, so I would like to either remove t

[jira] Created: (MECLIPSE-66) Java Build Path of dependency with scope "system" is prefixed with the M2_REPO system classpath variable

ECLIPSE-66 Project: Maven 2.x Eclipse Plugin Type: Bug Environment: M2 2.0.2 Reporter: Kristian Nordal I have a dependency defined like this: oink oink 1.0.0 system ${basedir}/oink/oink/1.0.0/oink-1.0.0.jar mvn eclipse:eclipse puts a

[jira] Created: (ARCHETYPE-11) webapp archetype generate invalid POM URL

webapp archetype generate invalid POM URL - Key: ARCHETYPE-11 URL: http://jira.codehaus.org/browse/ARCHETYPE-11 Project: Maven Archetype Type: Bug Components: maven-archetype-plugin Reporter: Kristian Nordal Assigned to

[jira] Commented: (MEV-90) JUnit dependency in commons-logging is version 3.7 but Surefire requires 3.8.x

[ http://jira.codehaus.org/browse/MEV-90?page=comments#action_46945 ] Kristian Nordal commented on MEV-90: Sorry, I wasn't thinking straight. Surefire doesn't necessarily run with the junit version my tests are built with... > JUnit

[jira] Created: (MEV-90) JUnit dependency in commons-logging is version 3.7 but Surefire requires 3.8.x

: Kristian Nordal I read on the dev list that Surefire now requires JUnit 3.8. I'm getting compilation errors in my projects (on classes extending TestCase) now and I guess this is because commons-logging's dependeny on 3.7. -- This message is automatically generated by JIRA. - If you th

[jira] Commented: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency

[ http://jira.codehaus.org/browse/MNG-705?page=comments#action_44064 ] Kristian Nordal commented on MNG-705: - Yes, I just stumbled upon it while playing around =) > Declared dependency is not included when there exist an exclusion of the > artif

[jira] Created: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency

: Maven 2 Type: Bug Versions: 2.0-beta-1 Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347 Reporter: Kristian Nordal Priority: Minor I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency

Re: [m2] getting involved?

On Aug 5, 2005, at 11:14 AM, Thomas Van de Velde wrote: BTW - I like plexus. Haven't noticed the project before. I had used avalon and had a look at pico+nano before. Plexus seems to be powerfull like avalon containers but less invasive (like the spring-framework). Maybe I'll use that in my

[jira] Commented: (MEV-12) mysql-connector-java uses a classifier

[ http://jira.codehaus.org/browse/MEV-12?page=comments#action_39612 ] Kristian Nordal commented on MEV-12: How was it fixed? Will a "classifier" element be added? > mysql-connector-java uses