Well, this is problematic right now... there is no place on pom to declare this information, so since on 2.x maven didn't validate the scope that was the place for it =D
Hopefully on maven 3.1/project model 5 will make some room so flexmojos would stop using scopes and this problems would be done. On Fri, Nov 5, 2010 at 5:39 PM, Rafael Adson Barbosa Barros < [email protected]> wrote: > Hello, > > Understood. However, using those scopes is a must for flex programmers who > want to use maven. > So maybe a compromise solution would be creating a a validateScopes > parameter (defaults = true). > I really need to have maven copy a set of "external" scoped dependencies, > and I´d hate to have to make a "company branch" of a maven plugin > > Thanks, > Rafael. > > On Fri, Nov 5, 2010 at 5:08 PM, Brian Fox <[email protected]> wrote: > > > The use of the non-standard scopes is not currently a valid use case, > > so I'd say it's flexmojos with the bug here. It may work for now but > > who knows what those scopes could do to other tools. > > > > On Fri, Nov 5, 2010 at 1:27 PM, Rafael Adson Barbosa Barros > > <[email protected]> wrote: > > > Hi, > > > > > > I'm trying to use maven-dependencies-plugin along with flexmojos ( > > > https://github.com/Flexmojos/flexmojos). > > > What I want to do is use maven-dependencies-plugin to copy some > > dependencies > > > to the destination. However, as the project is flex (and not java), I'm > > > having problems managing it since I have to manage some > > > dependencies that are defined in the external scope. > > > > > > Searching in the maven-dependencies-plugin code base I found: > > > > > > if ( !Artifact.SCOPE_COMPILE.equals( includeScope ) && > > > !Artifact.SCOPE_TEST.equals( includeScope ) > > > && !Artifact.SCOPE_PROVIDED.equals( includeScope ) && > > > !Artifact.SCOPE_RUNTIME.equals( includeScope ) > > > && !Artifact.SCOPE_SYSTEM.equals( includeScope ) ) > > > throw new ArtifactFilterException( "Invalid Scope in > includeScope: > > " > > > + includeScope ); > > > > > > in the class > > org.apache.maven.shared.artifact.filter.collection.ScopeFilter, > > > that is not allowing me to use the plugin the way I want to. > > > > > > My question then is this: the plugin only supports today scopes that > are > > > adequate for the java programming language. Should it not be > > > language-independent > > > (thus removing the presented code)? If it should be dependent on java, > is > > > there some way that I can use the plugin to do what I want to do? > > > > > > Thanks, > > > Rafael. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
