Re: What's the deal with the shade plugin?
This still getting moved over to the sandbox here? Maybe good to do it at the same time as archetype? - Brett On 15/06/2007, at 3:10 PM, Brett Porter wrote: On 15/06/2007, at 3:02 PM, Jason van Zyl wrote: On 14 Jun 07, at 9:33 PM 14 Jun 07, Brett Porter wrote: Hi, Took a look at this, and I see the shade plugin JIRA was created with the maven defaults for notifications and permissions, not mojos where it currently lives in the sandbox. That was my ruby script for creating projects that just default to Maven settings. Is the intent to move it into this project, or was the JIRA project created incorrectly? Yup. Given it is a required part of the build now, and very useful in general, I'd love to see it brought out of it's state of alpha- ness and included in our stable of plugins. Thoughts? Sure. Mauro, Dan, and myself have worked on it so we'd have to get a CLA for Mauro and then it's all good. Cool. Mauro is an excalibur committer, so no need. - Brett - 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]
Re: How to define a dependancy without version number
I can rename jar in my development env, not a isssue. Problem is, We want build scripts in such way so that we can use same build scripts on dev as well as on production. and for this purpose I wants to give dependancy of jar in the same way as they are reffered in production. and because of thiis reason I wants to assign dependancy reffering to Jar. Any chage in production env is not in my control and it can not be done. I agree that we should have a standord way to reffer dependancy, But this should be optional not mandatory and maven should be flexible enough to configure the way I want. brettporter wrote: > > http://maven.apache.org/maven-1.x/faq.html#unversioned-jars > > You can name that what you wish in build/deployment/production, they > just need a version in the repository. > > On 03/07/2007, at 6:27 AM, Harish Kachoria wrote: > >> >> In maven 1.0 we were using tag to define jar dependancy. >> which I think >> deprecated. >> >> How ever in my current project I'm trying to integrating Maven 2.0 >> (Before >> that we make jar using javac and used it). >> Problems which I have - >> >> - I have many jars which are third party/inbuild libraries and >> which do not >> have any version number. >> - Application is already in production and currently all libraries >> are >> stored in server/lib folder. >> - and same libraries are used by many other projects. >> >> And Management won't allow me to rename the jar files which are >> already in >> production. (That can be done step by step when all projects become >> migrated >> to Maven) >> >> And because of this reason I want's to refer Jar file in my dependancy >> section. >> One alernate way I found is to use System Path. But I think it is not >> correct way to use. >> >> So If I have feature which we already had in Maven 1.0 to refer >> library >> without version number then it would be very much help ful. >> >> >> >> >> >> >> >> Harish Kachoria wrote: >>> >>> Hello All, >>> >>> I'm trying to integrating Maven in my project. >>> >>> I was quite comfortable using maven 1.0. >>> >>> But with Maven 2.0 I have one problem to define dependency of a >>> jar file. >>> >>> I wants to define dependency without having a version number. how >>> can I do >>> that ?? >>> >>> Please suggest me >>> >>> Best Regards >>> Harish >>> >>> >> >> -- >> View this message in context: http://www.nabble.com/How-to-define-a- >> dependancy-without-version-number-tf4004825s177.html#a11401107 >> Sent from the Maven Developers mailing list archive at Nabble.com. >> >> >> - >> 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/How-to-define-a-dependancy-without-version-number-tf4004825s177.html#a11405549 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to define a dependancy without version number
I know, the material is the same (it maybe should be in the m2 faq too :) ie, the answer in m1 is "you can but you shouldn't and here's how to workaround". In m2, it's "you can't, and here's how to work around". On 03/07/2007, at 12:34 PM, Ralph Goers wrote: Brett Porter wrote: http://maven.apache.org/maven-1.x/faq.html#unversioned-jars You can name that what you wish in build/deployment/production, they just need a version in the repository. Brett, He wants to do this in Maven 2, not Maven 1. Ralph - 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]
Re: How to define a dependancy without version number
Brett Porter wrote: http://maven.apache.org/maven-1.x/faq.html#unversioned-jars You can name that what you wish in build/deployment/production, they just need a version in the repository. Brett, He wants to do this in Maven 2, not Maven 1. Ralph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: result code for mvn.bat on windows broken
I can confirm this. It was messing up the invoker tests even until I changed it manually. I'll write it up if it's not already and fix it. Thanks, Brian -Original Message- From: Tom Huybrechts [mailto:[EMAIL PROTECTED] Sent: Saturday, June 23, 2007 2:48 PM To: Maven Developers List Subject: result code for mvn.bat on windows broken Hi, can anybody confirm/deny that the changes to mvn.bat in r543625 have broken result codes ? Errors are no longer reported in 2.0.7. If I restore the @endLocal, it works as it did before. :error +if "%OS%"=="Windows_NT" @endlocal set ERROR_CODE=1 Tom - 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]
invoker test failure
I'm getting an error building the 2.0.7-snapshot invoker: Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.861 sec <<< FAILURE! testBuildShouldFail(org.apache.maven.shared.invoker.DefaultInvokerTest) Time elapsed: 3.782 sec <<< FAILURE! junit.framework.AssertionFailedError: expected:<1> but was:<0> InvocationResult result = invoker.execute( request ); assertEquals( 1, result.getExitCode() ); I'm using m2.0.7 to run this on XP. I know there were some issues around 2.0.7 at one point not returning the correct exit code. Is anyone else seeing this issue with Invoker? BTW..I'm really just trying to dig into the invoker to test why it fails to find the maven executable when running through cygwin on windows: Tests run: 29, Failures: 0, Errors: 29, Skipped: 0, Time elapsed: 4.689 sec <<< FAILURE! testProject01(org.apache.maven.plugin.eclipse.EclipsePluginTest) Time elapsed: 0.126 sec <<< ERROR! java.lang.NullPointerException at org.apache.maven.shared.invoker.MavenCommandLineBuilder.findMavenExecuta ble(MavenCommandLineBuilder.java:367) at org.apache.maven.shared.invoker.MavenCommandLineBuilder.build(MavenComma ndLineBuilder.java:33) at org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.ja va:88) at org.apache.maven.shared.test.plugin.BuildTool.executeMaven(BuildTool.jav a:89) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Non lifecycle forking eclipse:eclipse
+1. A nice future feature in plexus would be the ability to control these parameters in a pre-run/initialize phase. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, July 02, 2007 8:00 PM To: Maven Developers List Subject: Non lifecycle forking eclipse:eclipse Hi, Does anyone mind if I add a non lifecycle forking version of the eclipse:eclipse and eclipse:m2eclipse commands. I am using these commands in a set of tooling and we know that the generate sources phase has executed. Using the existing mojo forks a lifecycle so anything up to and including generate sources executes twice. In the system I'm tooling the generate sources phases takes a long time. It's not breaking the build but doubling the execution time which is unacceptable. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - 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]
Re: How to define a dependancy without version number
http://maven.apache.org/maven-1.x/faq.html#unversioned-jars You can name that what you wish in build/deployment/production, they just need a version in the repository. On 03/07/2007, at 6:27 AM, Harish Kachoria wrote: In maven 1.0 we were using tag to define jar dependancy. which I think deprecated. How ever in my current project I'm trying to integrating Maven 2.0 (Before that we make jar using javac and used it). Problems which I have - - I have many jars which are third party/inbuild libraries and which do not have any version number. - Application is already in production and currently all libraries are stored in server/lib folder. - and same libraries are used by many other projects. And Management won't allow me to rename the jar files which are already in production. (That can be done step by step when all projects become migrated to Maven) And because of this reason I want's to refer Jar file in my dependancy section. One alernate way I found is to use System Path. But I think it is not correct way to use. So If I have feature which we already had in Maven 1.0 to refer library without version number then it would be very much help ful. Harish Kachoria wrote: Hello All, I'm trying to integrating Maven in my project. I was quite comfortable using maven 1.0. But with Maven 2.0 I have one problem to define dependency of a jar file. I wants to define dependency without having a version number. how can I do that ?? Please suggest me Best Regards Harish -- View this message in context: http://www.nabble.com/How-to-define-a- dependancy-without-version-number-tf4004825s177.html#a11401107 Sent from the Maven Developers mailing list archive at Nabble.com. - 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]
Non lifecycle forking eclipse:eclipse
Hi, Does anyone mind if I add a non lifecycle forking version of the eclipse:eclipse and eclipse:m2eclipse commands. I am using these commands in a set of tooling and we know that the generate sources phase has executed. Using the existing mojo forks a lifecycle so anything up to and including generate sources executes twice. In the system I'm tooling the generate sources phases takes a long time. It's not breaking the build but doubling the execution time which is unacceptable. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Ant Tasks 2.0.7
On 2 Jul 07, at 2:20 PM 2 Jul 07, Hervé BOUTEMY wrote: Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit : Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit : patch MANTTASKS-76_site-release.diff added to MANTTASKS-76 added patch MANTTASKS-76_license.diff too, while we're at it... are these patches ok to get the release out, or should I change something? Yup, I will do it tonight. Hervé Ready for the release! Hervé Le jeudi 28 juin 2007, Jason van Zyl a écrit : On 28 Jun 07, at 1:54 PM 28 Jun 07, Hervé BOUTEMY wrote: Le jeudi 28 juin 2007, Jason van Zyl a écrit : Thanks Herve, I forgot about adding that even though you reminded me last night. Think you might make a site patch for the release notes regarding these issues? Do you mean adding release notes for Maven Ant Tasks like for Maven Core http://maven.apache.org/release-notes.html ? The change for localRepository is documented at the end of the doc, in "Type Reference>localRepository" section. But it is not really easy to find it... We should probably make separate release notes for the ant tasks. On 27 Jun 07, at 11:29 PM 27 Jun 07, Hervé BOUTEMY wrote: Hi, Just a little note on this release. There are a lot of bugfixes (SNAPSHOT downloading, for example), new features (VersionMapper, remoteRepository support for pom and install- provider tasks) documented on http://maven.apache.org/ant-tasks.html. But there are 2 incompatible changes that you must know before upgrading, to fix your Ant build files: 1. MANTTASKS-44: instead of location=""/> for Ant 1.7 compatibility (location attribute is used by Ant now) 2. MANTTASKS-65: central is not automatically added any more if a remoteRepository is set: the code has been changed to work as the documentation said Everything else should work as previously (with less bugs) Regards Hervé Le jeudi 28 juin 2007, Jason van Zyl a écrit : Hi, Repost of the vote after fixing the issues with the uber JAR that was produced. Hervé and I have tried them and they appear to work fine. The staging repository is here: http://people.apache.org/~jvanzyl/maven-ant-tasks-2.0.7- staging- repository/ The uber jar that people will want to try is here: http://people.apache.org/~jvanzyl/maven-ant-tasks-2.0.7- staging- repository/org/apache/maven/maven-ant-tasks/2.0.7/ Road map: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=11533&styleName=Html&version=13521 Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- --- --- - -- 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] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - --- - 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] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- --- -- 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] - 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] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Ant Tasks 2.0.7
Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit : > Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit : > > patch MANTTASKS-76_site-release.diff added to MANTTASKS-76 > > added patch MANTTASKS-76_license.diff too, while we're at it... are these patches ok to get the release out, or should I change something? Hervé > > > Ready for the release! > > > > Hervé > > > > Le jeudi 28 juin 2007, Jason van Zyl a écrit : > > > On 28 Jun 07, at 1:54 PM 28 Jun 07, Hervé BOUTEMY wrote: > > > > Le jeudi 28 juin 2007, Jason van Zyl a écrit : > > > >> Thanks Herve, I forgot about adding that even though you reminded me > > > >> last night. Think you might make a site patch for the release notes > > > >> regarding these issues? > > > > > > > > Do you mean adding release notes for Maven Ant Tasks like for Maven > > > > Core > > > > http://maven.apache.org/release-notes.html ? > > > > > > > > The change for localRepository is documented at the end of the doc, > > > > in "Type > > > > Reference>localRepository" section. But it is not really easy to > > > > find it... > > > > > > We should probably make separate release notes for the ant tasks. > > > > > > >> On 27 Jun 07, at 11:29 PM 27 Jun 07, Hervé BOUTEMY wrote: > > > >>> Hi, > > > >>> > > > >>> Just a little note on this release. > > > >>> There are a lot of bugfixes (SNAPSHOT downloading, for example), > > > >>> new features > > > >>> (VersionMapper, remoteRepository support for pom and install- > > > >>> provider tasks) > > > >>> documented on http://maven.apache.org/ant-tasks.html. > > > >>> > > > >>> But there are 2 incompatible changes that you must know before > > > >>> upgrading, to > > > >>> fix your Ant build files: > > > >>> > > > >>> 1. MANTTASKS-44: instead of > > > >>> > > >>> location=""/> for Ant 1.7 compatibility (location attribute is used > > > >>> by Ant > > > >>> now) > > > >>> > > > >>> 2. MANTTASKS-65: central is not automatically added any more if a > > > >>> remoteRepository is set: the code has been changed to work as the > > > >>> documentation said > > > >>> > > > >>> Everything else should work as previously (with less bugs) > > > >>> > > > >>> Regards > > > >>> > > > >>> Hervé > > > >>> > > > >>> Le jeudi 28 juin 2007, Jason van Zyl a écrit : > > > Hi, > > > > > > Repost of the vote after fixing the issues with the uber JAR > > > that was > > > produced. Hervé and I have tried them and they appear to work > > > fine. > > > > > > The staging repository is here: > > > > > > http://people.apache.org/~jvanzyl/maven-ant-tasks-2.0.7-staging- > > > repository/ > > > > > > The uber jar that people will want to try is here: > > > > > > http://people.apache.org/~jvanzyl/maven-ant-tasks-2.0.7-staging- > > > repository/org/apache/maven/maven-ant-tasks/2.0.7/ > > > > > > Road map: > > > > > > http://jira.codehaus.org/secure/ReleaseNote.jspa? > > > projectId=11533&styleName=Html&version=13521 > > > > > > > > > Thanks, > > > > > > Jason > > > > > > -- > > > Jason van Zyl > > > Founder and PMC Chair, Apache Maven > > > jason at sonatype dot com > > > -- > > > > > > > > > > > > -- > > > - -- > > > 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] > > > >> > > > >> Thanks, > > > >> > > > >> Jason > > > >> > > > >> -- > > > >> Jason van Zyl > > > >> Founder and PMC Chair, Apache Maven > > > >> jason at sonatype dot com > > > >> -- > > > >> > > > >> > > > >> > > > >> > > > >> > > > >>- 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] > > > > > > Thanks, > > > > > > Jason > > > > > > -- > > > Jason van Zyl > > > Founder and PMC Chair, Apache Maven > > > jason at sonatype dot com > > > -- > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > ---
Re: How to define a dependancy without version number
In maven 1.0 we were using tag to define jar dependancy. which I think deprecated. How ever in my current project I'm trying to integrating Maven 2.0 (Before that we make jar using javac and used it). Problems which I have - - I have many jars which are third party/inbuild libraries and which do not have any version number. - Application is already in production and currently all libraries are stored in server/lib folder. - and same libraries are used by many other projects. And Management won't allow me to rename the jar files which are already in production. (That can be done step by step when all projects become migrated to Maven) And because of this reason I want's to refer Jar file in my dependancy section. One alernate way I found is to use System Path. But I think it is not correct way to use. So If I have feature which we already had in Maven 1.0 to refer library without version number then it would be very much help ful. Harish Kachoria wrote: > > Hello All, > > I'm trying to integrating Maven in my project. > > I was quite comfortable using maven 1.0. > > But with Maven 2.0 I have one problem to define dependency of a jar file. > > I wants to define dependency without having a version number. how can I do > that ?? > > Please suggest me > > Best Regards > Harish > > -- View this message in context: http://www.nabble.com/How-to-define-a-dependancy-without-version-number-tf4004825s177.html#a11401107 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetty proxy config required?
On 7/2/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: The latest docs is there: http://docs.codehaus.org/pages/viewpage.action?pageId=73595 Thanks. This is actually someone trying to put it behind a different proxy (not httpd + mod_proxy). I don't have enough info about what's going on yet, but the basic idea is that you configure the system to proxy myserver:8080/continuum through otherserver/apps/continuum, so otherserver can use 80/443 to proxy multiple servers running different apps on different ports. In this case you'd go to http://otherserver/apps/continuum/ and expect to see the content from http://myserver:8080/continuum/. I can (sort of) get it to work if I visit http://otherserver/apps/continuum/index.action. The complaint is that Continuum is sending Location headers/redirects with hostnames in them. That's apparently why the initial redirect from continuum/ to continuum/index.action isn't working. Any ideas? -- Wendy
Generating Docs as part of Install...
I have been given a requirement to put our tagdocs inside a project WAR file. Unfortunately, the tagdocs get generated as part of the "site" phase, which comes AFTER 'mvn install', which creates the desired war file. Does anybody have any ideas how to do this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r552182 - in /maven/components/trunk: maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ maven-project/src/test/java/org/apache/maven/project/inheritance/t11/ maven-proje
On 2 Jul 07, at 8:15 AM 2 Jul 07, Patrick Schneider wrote:
Yes -- I put it in the branch for the 2.0.7 release, but hadn't
ported it
up. This, of course, was before I asked you for clarification
about putting
code in the trunk first and then merging to the branch ;o)
Cool, thanks. Not trying to be overbearing just checking as my memory
only lasts about 3 days.
On 7/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Did you put this on the branch as well?
On 30 Jun 07, at 10:31 AM 30 Jun 07, [EMAIL PROTECTED] wrote:
> Author: pschneider
> Date: Sat Jun 30 10:31:45 2007
> New Revision: 552182
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=552182
> Log:
> [MNG-2919] Add fix for depMan scope overwriting to the trunk.
>
> Added:
> maven/components/trunk/maven-project/src/test/java/org/apache/
> maven/project/inheritance/t11/
> maven/components/trunk/maven-project/src/test/java/org/apache/
> maven/project/inheritance/t11/ProjectInheritanceTest.java (with
> props)
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/p0/
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/p0/p1/
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/p0/p1/pom.xml (with props)
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/p0/pom.xml (with props)
> Modified:
> maven/components/trunk/maven-artifact/src/main/java/org/apache/
> maven/artifact/resolver/DefaultArtifactCollector.java
>
> Modified: maven/components/trunk/maven-artifact/src/main/java/org/
> apache/maven/artifact/resolver/DefaultArtifactCollector.java
> URL: http://svn.apache.org/viewvc/maven/components/trunk/maven-
> artifact/src/main/java/org/apache/maven/artifact/resolver/
> DefaultArtifactCollector.java?
view=diff&rev=552182&r1=552181&r2=552182
>
=
=
>
> --- maven/components/trunk/maven-artifact/src/main/java/org/apache/
> maven/artifact/resolver/DefaultArtifactCollector.java (original)
> +++ maven/components/trunk/maven-artifact/src/main/java/org/apache/
> maven/artifact/resolver/DefaultArtifactCollector.java Sat Jun 30
> 10:31:45 2007
> @@ -127,19 +127,14 @@
> Artifact managedOriginatingArtifact = (Artifact)
> versionMap.get( originatingArtifact.getDependencyConflictId() );
> if ( managedOriginatingArtifact != null )
> {
> -String managedVersion =
> managedOriginatingArtifact.getVersion();
> -String version = originatingArtifact.getVersion();
> -if ( !managedVersion.equals( version ) )
> +// TODO we probably want to warn the user that he is
> building an artifact with
> +// different values than in dependencyManagement
> +if ( managedVersions instanceof ManagedVersionMap )
> {
> -// TODO we probably want to warn the user that he
> is building and artifact with a
> -// different version than in dependencyManagement
> -if ( managedVersions instanceof
ManagedVersionMap )
> -{
> -/* avoid modifying the managedVersions
> parameter creating a new map */
> -versionMap = new ManagedVersionMap
> ( managedVersions );
> -}
> -versionMap.remove
> ( originatingArtifact.getDependencyConflictId() );
> +/* avoid modifying the managedVersions parameter
> creating a new map */
> +versionMap = new ManagedVersionMap
> ( managedVersions );
> }
> +versionMap.remove
> ( originatingArtifact.getDependencyConflictId() );
> }
>
> return versionMap;
>
> Added: maven/components/trunk/maven-project/src/test/java/org/
> apache/maven/project/inheritance/t11/ProjectInheritanceTest.java
> URL: http://svn.apache.org/viewvc/maven/components/trunk/maven-
> project/src/test/java/org/apache/maven/project/inheritance/t11/
> ProjectInheritanceTest.java?view=auto&rev=552182
>
=
=
>
> --- maven/components/trunk/maven-project/src/test/java/org/apache/
> maven/project/inheritance/t11/ProjectInheritanceTest.java (added)
> +++ maven/components/trunk/maven-project/src/test/java/org/apache/
> maven/project/inheritance/t11/ProjectInheritanceTest.java Sat Jun
> 30 10:31:45 2007
> @@ -0,0 +1,78 @@
> +package org.apache.maven.project.inheritance.t11;
> +
> +/*
> + * Licensed to the Apache Software Foundation (ASF) under one
> + * or more contributor license agreements. See the NOTICE file
> + * distributed with this work for additional information
> + * regarding copyright ownership. The ASF licenses this file
> + * to you under the Apache License, Version 2.0 (the
> + * "License
Re: [RESULT][VOTE] Release maven-idea-plugin 2.1
On 2 Jul 07, at 8:18 AM 2 Jul 07, Fustrated wrote: Thanks guys, new version doesn't work. I suggest you learn some basic OSS etiquette rules. Sarcasm will win your requests for help a one way ticket to /dev/null. Something like: Is anyone having any problems with the IDEA plugin, I am trying to new version and I'm getting this error ... I'm using the new version of the plugin fine, but there might be something else wrong with your environment. Sometime the metadata gets out of sync and you can try removing all versions of the plugin and try again. Then you get a fresh copy of the metadata and this often works. I get the following error when I type mvn idea:idea [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-idea-plugin:2.1:idea': Unable to find the mojo 'org.apache.maven.plug ins:maven-idea-plugin:2.1:idea' in the plugin 'org.apache.maven.plugins:maven-id ea-plugin' org/dom4j/Node Now how do I force maven to use 2.0 of the plugin instead of the bugging 2.1. Everthing was worked so ni mvn org.apache.maven.plugins:maven-idea-plugin:2.0:idea cely before. Thanks Dinesh Stephane Nicoll-2 wrote: Thanks Dennis. Stéphane On 6/23/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Done. Just wait for it to sync. Stephane Nicoll wrote: Can we stage this on please? Stéphane On 6/13/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 12 Jun 07, at 2:10 PM 12 Jun 07, Dennis Lundberg wrote: Here are the results of this vote: +1: Dennis Lundberg, Stephane Nicoll, Jason van Zyl +1 (non-binding): Jo Vandermeeren, Andrew Williams I'll work with Jason to try and move this release into the central repo using the stage-plugin. Tonight I'm going to make another attempt at 2.0.7 so I'll do a little work on the stage plugin. Dennis Lundberg wrote: Hi, I'd like to release maven-idea-plugin 2.1. There are 12 issues fixed in this version and the last release was made over a year ago. Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=11135&styleName=Html&version=12618 Tag: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-idea- plugin-2.1/ Staged at: http://people.apache.org/~dennisl/staging-repository-idea- plugin/ The vote will be open for 72 hours. Here is my +1 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- -- --- 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] -- Dennis Lundberg - 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/-VOTE--Release- maven-idea-plugin-2.1-tf3868302s177.html#a11395856 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT][VOTE] Release maven-idea-plugin 2.1
Works fine here. Show your pom and a debug execution of mvn idea:idea (mvn idea:idea -X debug.log Stéphane On 7/2/07, Fustrated <[EMAIL PROTECTED]> wrote: Thanks guys, new version doesn't work. I get the following error when I type mvn idea:idea [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-idea-plugin:2.1:idea': Unable to find the mojo 'org.apache.maven.plug ins:maven-idea-plugin:2.1:idea' in the plugin 'org.apache.maven.plugins:maven-id ea-plugin' org/dom4j/Node Now how do I force maven to use 2.0 of the plugin instead of the bugging 2.1. Everthing was worked so nicely before. Thanks Dinesh Stephane Nicoll-2 wrote: > > Thanks Dennis. > > Stéphane > > On 6/23/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote: >> Done. Just wait for it to sync. >> >> Stephane Nicoll wrote: >> > Can we stage this on please? >> > >> > Stéphane >> > >> > On 6/13/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> >> >> >> On 12 Jun 07, at 2:10 PM 12 Jun 07, Dennis Lundberg wrote: >> >> >> >> > Here are the results of this vote: >> >> > >> >> > +1: Dennis Lundberg, Stephane Nicoll, Jason van Zyl >> >> > >> >> > +1 (non-binding): Jo Vandermeeren, Andrew Williams >> >> > >> >> > I'll work with Jason to try and move this release into the central >> >> > repo using the stage-plugin. >> >> > >> >> >> >> Tonight I'm going to make another attempt at 2.0.7 so I'll do a >> >> little work on the stage plugin. >> >> >> >> > Dennis Lundberg wrote: >> >> >> Hi, >> >> >> I'd like to release maven-idea-plugin 2.1. There are 12 issues >> >> >> fixed in >> >> >> this version and the last release was made over a year ago. >> >> >> Release Notes: >> >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa? >> >> >> projectId=11135&styleName=Html&version=12618 Tag: >> >> >> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-idea- >> >> >> plugin-2.1/ >> >> >> Staged at: >> >> >> http://people.apache.org/~dennisl/staging-repository-idea-plugin/ >> >> >> The vote will be open for 72 hours. >> >> >> Here is my +1 >> >> > >> >> > >> >> > -- >> >> > Dennis Lundberg >> >> > >> >> > >> - >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> >> >> Thanks, >> >> >> >> Jason >> >> >> >> -- >> >> Jason van Zyl >> >> Founder and PMC Chair, Apache Maven >> >> jason at sonatype dot com >> >> -- >> >> >> >> >> >> >> >> >> >> - >> >> 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] >> > >> > >> >> >> -- >> Dennis Lundberg >> >> >> - >> 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/-VOTE--Release-maven-idea-plugin-2.1-tf3868302s177.html#a11395856 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT][VOTE] Release maven-idea-plugin 2.1
Thanks guys, new version doesn't work. I get the following error when I type mvn idea:idea [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-idea-plugin:2.1:idea': Unable to find the mojo 'org.apache.maven.plug ins:maven-idea-plugin:2.1:idea' in the plugin 'org.apache.maven.plugins:maven-id ea-plugin' org/dom4j/Node Now how do I force maven to use 2.0 of the plugin instead of the bugging 2.1. Everthing was worked so nicely before. Thanks Dinesh Stephane Nicoll-2 wrote: > > Thanks Dennis. > > Stéphane > > On 6/23/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote: >> Done. Just wait for it to sync. >> >> Stephane Nicoll wrote: >> > Can we stage this on please? >> > >> > Stéphane >> > >> > On 6/13/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> >> >> >> On 12 Jun 07, at 2:10 PM 12 Jun 07, Dennis Lundberg wrote: >> >> >> >> > Here are the results of this vote: >> >> > >> >> > +1: Dennis Lundberg, Stephane Nicoll, Jason van Zyl >> >> > >> >> > +1 (non-binding): Jo Vandermeeren, Andrew Williams >> >> > >> >> > I'll work with Jason to try and move this release into the central >> >> > repo using the stage-plugin. >> >> > >> >> >> >> Tonight I'm going to make another attempt at 2.0.7 so I'll do a >> >> little work on the stage plugin. >> >> >> >> > Dennis Lundberg wrote: >> >> >> Hi, >> >> >> I'd like to release maven-idea-plugin 2.1. There are 12 issues >> >> >> fixed in >> >> >> this version and the last release was made over a year ago. >> >> >> Release Notes: >> >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa? >> >> >> projectId=11135&styleName=Html&version=12618 Tag: >> >> >> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-idea- >> >> >> plugin-2.1/ >> >> >> Staged at: >> >> >> http://people.apache.org/~dennisl/staging-repository-idea-plugin/ >> >> >> The vote will be open for 72 hours. >> >> >> Here is my +1 >> >> > >> >> > >> >> > -- >> >> > Dennis Lundberg >> >> > >> >> > >> - >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> >> >> Thanks, >> >> >> >> Jason >> >> >> >> -- >> >> Jason van Zyl >> >> Founder and PMC Chair, Apache Maven >> >> jason at sonatype dot com >> >> -- >> >> >> >> >> >> >> >> >> >> - >> >> 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] >> > >> > >> >> >> -- >> Dennis Lundberg >> >> >> - >> 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/-VOTE--Release-maven-idea-plugin-2.1-tf3868302s177.html#a11395856 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r552182 - in /maven/components/trunk: maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ maven-project/src/test/java/org/apache/maven/project/inheritance/t11/ maven-proje
Yes -- I put it in the branch for the 2.0.7 release, but hadn't ported it
up. This, of course, was before I asked you for clarification about putting
code in the trunk first and then merging to the branch ;o)
On 7/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Did you put this on the branch as well?
On 30 Jun 07, at 10:31 AM 30 Jun 07, [EMAIL PROTECTED] wrote:
> Author: pschneider
> Date: Sat Jun 30 10:31:45 2007
> New Revision: 552182
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=552182
> Log:
> [MNG-2919] Add fix for depMan scope overwriting to the trunk.
>
> Added:
> maven/components/trunk/maven-project/src/test/java/org/apache/
> maven/project/inheritance/t11/
> maven/components/trunk/maven-project/src/test/java/org/apache/
> maven/project/inheritance/t11/ProjectInheritanceTest.java (with
> props)
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/p0/
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/p0/p1/
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/p0/p1/pom.xml (with props)
> maven/components/trunk/maven-project/src/test/resources/
> inheritance-repo/t11/p0/pom.xml (with props)
> Modified:
> maven/components/trunk/maven-artifact/src/main/java/org/apache/
> maven/artifact/resolver/DefaultArtifactCollector.java
>
> Modified: maven/components/trunk/maven-artifact/src/main/java/org/
> apache/maven/artifact/resolver/DefaultArtifactCollector.java
> URL: http://svn.apache.org/viewvc/maven/components/trunk/maven-
> artifact/src/main/java/org/apache/maven/artifact/resolver/
> DefaultArtifactCollector.java?view=diff&rev=552182&r1=552181&r2=552182
> ==
>
> --- maven/components/trunk/maven-artifact/src/main/java/org/apache/
> maven/artifact/resolver/DefaultArtifactCollector.java (original)
> +++ maven/components/trunk/maven-artifact/src/main/java/org/apache/
> maven/artifact/resolver/DefaultArtifactCollector.java Sat Jun 30
> 10:31:45 2007
> @@ -127,19 +127,14 @@
> Artifact managedOriginatingArtifact = (Artifact)
> versionMap.get( originatingArtifact.getDependencyConflictId() );
> if ( managedOriginatingArtifact != null )
> {
> -String managedVersion =
> managedOriginatingArtifact.getVersion();
> -String version = originatingArtifact.getVersion();
> -if ( !managedVersion.equals( version ) )
> +// TODO we probably want to warn the user that he is
> building an artifact with
> +// different values than in dependencyManagement
> +if ( managedVersions instanceof ManagedVersionMap )
> {
> -// TODO we probably want to warn the user that he
> is building and artifact with a
> -// different version than in dependencyManagement
> -if ( managedVersions instanceof ManagedVersionMap )
> -{
> -/* avoid modifying the managedVersions
> parameter creating a new map */
> -versionMap = new ManagedVersionMap
> ( managedVersions );
> -}
> -versionMap.remove
> ( originatingArtifact.getDependencyConflictId() );
> +/* avoid modifying the managedVersions parameter
> creating a new map */
> +versionMap = new ManagedVersionMap
> ( managedVersions );
> }
> +versionMap.remove
> ( originatingArtifact.getDependencyConflictId() );
> }
>
> return versionMap;
>
> Added: maven/components/trunk/maven-project/src/test/java/org/
> apache/maven/project/inheritance/t11/ProjectInheritanceTest.java
> URL: http://svn.apache.org/viewvc/maven/components/trunk/maven-
> project/src/test/java/org/apache/maven/project/inheritance/t11/
> ProjectInheritanceTest.java?view=auto&rev=552182
> ==
>
> --- maven/components/trunk/maven-project/src/test/java/org/apache/
> maven/project/inheritance/t11/ProjectInheritanceTest.java (added)
> +++ maven/components/trunk/maven-project/src/test/java/org/apache/
> maven/project/inheritance/t11/ProjectInheritanceTest.java Sat Jun
> 30 10:31:45 2007
> @@ -0,0 +1,78 @@
> +package org.apache.maven.project.inheritance.t11;
> +
> +/*
> + * Licensed to the Apache Software Foundation (ASF) under one
> + * or more contributor license agreements. See the NOTICE file
> + * distributed with this work for additional information
> + * regarding copyright ownership. The ASF licenses this file
> + * to you under the Apache License, Version 2.0 (the
> + * "License"); you may not use this file except in compliance
> + * with the License. You may obtain a copy of the License at
> + *
> + * http://www.apache.org/licenses/LICENSE-2.0
> + *
> + *
Re: svn commit: r552182 - in /maven/components/trunk: maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ maven-project/src/test/java/org/apache/maven/project/inheritance/t11/ maven-proje
Did you put this on the branch as well?
On 30 Jun 07, at 10:31 AM 30 Jun 07, [EMAIL PROTECTED] wrote:
Author: pschneider
Date: Sat Jun 30 10:31:45 2007
New Revision: 552182
URL: http://svn.apache.org/viewvc?view=rev&rev=552182
Log:
[MNG-2919] Add fix for depMan scope overwriting to the trunk.
Added:
maven/components/trunk/maven-project/src/test/java/org/apache/
maven/project/inheritance/t11/
maven/components/trunk/maven-project/src/test/java/org/apache/
maven/project/inheritance/t11/ProjectInheritanceTest.java (with
props)
maven/components/trunk/maven-project/src/test/resources/
inheritance-repo/t11/
maven/components/trunk/maven-project/src/test/resources/
inheritance-repo/t11/p0/
maven/components/trunk/maven-project/src/test/resources/
inheritance-repo/t11/p0/p1/
maven/components/trunk/maven-project/src/test/resources/
inheritance-repo/t11/p0/p1/pom.xml (with props)
maven/components/trunk/maven-project/src/test/resources/
inheritance-repo/t11/p0/pom.xml (with props)
Modified:
maven/components/trunk/maven-artifact/src/main/java/org/apache/
maven/artifact/resolver/DefaultArtifactCollector.java
Modified: maven/components/trunk/maven-artifact/src/main/java/org/
apache/maven/artifact/resolver/DefaultArtifactCollector.java
URL: http://svn.apache.org/viewvc/maven/components/trunk/maven-
artifact/src/main/java/org/apache/maven/artifact/resolver/
DefaultArtifactCollector.java?view=diff&rev=552182&r1=552181&r2=552182
==
--- maven/components/trunk/maven-artifact/src/main/java/org/apache/
maven/artifact/resolver/DefaultArtifactCollector.java (original)
+++ maven/components/trunk/maven-artifact/src/main/java/org/apache/
maven/artifact/resolver/DefaultArtifactCollector.java Sat Jun 30
10:31:45 2007
@@ -127,19 +127,14 @@
Artifact managedOriginatingArtifact = (Artifact)
versionMap.get( originatingArtifact.getDependencyConflictId() );
if ( managedOriginatingArtifact != null )
{
-String managedVersion =
managedOriginatingArtifact.getVersion();
-String version = originatingArtifact.getVersion();
-if ( !managedVersion.equals( version ) )
+// TODO we probably want to warn the user that he is
building an artifact with
+// different values than in dependencyManagement
+if ( managedVersions instanceof ManagedVersionMap )
{
-// TODO we probably want to warn the user that he
is building and artifact with a
-// different version than in dependencyManagement
-if ( managedVersions instanceof ManagedVersionMap )
-{
-/* avoid modifying the managedVersions
parameter creating a new map */
-versionMap = new ManagedVersionMap
( managedVersions );
-}
-versionMap.remove
( originatingArtifact.getDependencyConflictId() );
+/* avoid modifying the managedVersions parameter
creating a new map */
+versionMap = new ManagedVersionMap
( managedVersions );
}
+versionMap.remove
( originatingArtifact.getDependencyConflictId() );
}
return versionMap;
Added: maven/components/trunk/maven-project/src/test/java/org/
apache/maven/project/inheritance/t11/ProjectInheritanceTest.java
URL: http://svn.apache.org/viewvc/maven/components/trunk/maven-
project/src/test/java/org/apache/maven/project/inheritance/t11/
ProjectInheritanceTest.java?view=auto&rev=552182
==
--- maven/components/trunk/maven-project/src/test/java/org/apache/
maven/project/inheritance/t11/ProjectInheritanceTest.java (added)
+++ maven/components/trunk/maven-project/src/test/java/org/apache/
maven/project/inheritance/t11/ProjectInheritanceTest.java Sat Jun
30 10:31:45 2007
@@ -0,0 +1,78 @@
+package org.apache.maven.project.inheritance.t11;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import java.io.File;
+import java.util.Collection;
+import java.util.List;
+imp
Re: [m2] Conflict resolvers
On 2 Jul 07, at 7:37 AM 2 Jul 07, Mark Hobson wrote: On 29/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: Put it in the wiki. Consider it put: http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers Very nice, thanks. Feedback welcome. Will take a look today. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Conflict resolvers
On 29/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: Put it in the wiki. Consider it put: http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers Feedback welcome. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrate ArchetypeNG to Apache & commit privs for Raphael
On 2 Jul 07, at 12:57 AM 2 Jul 07, Brett Porter wrote: On 02/07/2007, at 4:54 PM, Raphaël Piéroni wrote: Please add some jira and assign them to me. I will only have time for this after the 15/07 (after holidays) Bit too much to get in there just now - we don't need to rush that part, I just wanted to make sure they were known. Most important thing is to do the licensing/packaging and get it imported (which I guess Jason is taking the lead on). Yup, it all builds and I've been running it for a couple weeks now and I have no problem taking responsibility for the code migration as a whole. Enjoy your holidays :) Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to define a dependancy without version number
Lukas Theussl wrote: No, it's still supported and not deprecated in Maven 1.1: http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/maven.html#class_dependency -Lukas It should have been. I can certainly understand why support for this was removed in version 2. Ralph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to define a dependancy without version number
No, it's still supported and not deprecated in Maven 1.1: http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/maven.html#class_dependency -Lukas Brett Porter wrote: Probably referring to the tag which let you hack the repository path. It's forbidden in Maven 2 (and was deprecated in 1.1 too I think?) - Brett On 02/07/2007, at 5:39 PM, Stephane Nicoll wrote: On 7/2/07, Ralph Goers <[EMAIL PROTECTED]> wrote: Harish Kachoria wrote: I'm really curious as to how you got that to work in maven 1.0? AFAIK version numbers have always been required. +1 Stéphane Ralph - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] g - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrate ArchetypeNG to Apache & commit privs for Raphael
On 02/07/2007, at 4:54 PM, Raphaël Piéroni wrote: Please add some jira and assign them to me. I will only have time for this after the 15/07 (after holidays) Bit too much to get in there just now - we don't need to rush that part, I just wanted to make sure they were known. Most important thing is to do the licensing/packaging and get it imported (which I guess Jason is taking the lead on). Enjoy your holidays :) Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to define a dependancy without version number
Probably referring to the tag which let you hack the repository path. It's forbidden in Maven 2 (and was deprecated in 1.1 too I think?) - Brett On 02/07/2007, at 5:39 PM, Stephane Nicoll wrote: On 7/2/07, Ralph Goers <[EMAIL PROTECTED]> wrote: Harish Kachoria wrote: I'm really curious as to how you got that to work in maven 1.0? AFAIK version numbers have always been required. +1 Stéphane Ralph - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Current ArchetypeNG trunk issues
Hi, Pumping this out to the list, since I don't have time to flood JIRA, and some may be answerable beforehand or get taken care of before the import. I'll take responsibility for collating this and any responses, retesting against the final imported code, and getting into JIRA (Which will need to first be reviewed for validity against the new codebase anyway). Here are the issues I've encountered so far: - [ ] doesn't build OOTB because of missing dependency on rt.jar. I don't understand the need for this (it worked after removing it), but if it is required on some platform it should be done like in it0063 (I think that's the one - with the system dependency). - [ ] doesn't build on versions of Maven < 2.0.7. Needs a prerequisite in the parent POM. - [ ] craps out on first use due to missing ~/.m2/archetype.xml (see [1]). - [ ] tried creating ~/.m2/archetype.xml with no content, and then with , and neither worked. All error messages were different, but both unhelpful. For those playing along at home, it's . See [2] and [3] for exceptions. - [ ] I ran... "mvn archetypeng:create -DartifactId=foo -DgroupId=bar" and got prompted with: Choose group: Choose a number: : (so, two problems here - it's still prompting by default, and there's no error handling on whatever should be determining the choices here) - [ ] I progressively added settings to the command line and it kept prompting - so it's not using any defaults for version, package, archetype*Id. - [ ] create-from-project seems to look in ~/m2/archetype.xml (note the missing '.') Some stuff/outstanding questions from before that needs to be rechecked (most already had been answered, just still on the todo list - see <[EMAIL PROTECTED]>): - [ ] Design - [ ] Carlos pointed out ARCHETYPE-38 wasn't in there, which was on archetype trunk (<[EMAIL PROTECTED]>). We need to review whether anything else has happened on trunk that is not in here due to the rewrite - [ ] currently the archetype descriptor is required, however I believe that sensible defaults could be derived making it unnecessary - [ ] The archetype descriptor seems like it's plugin configuration as well as the descriptor for inclusion - this seems to be a bad overlap - [ ] I need to review this some more for my own understanding - [ ] I was led to believe create-from-project required an archetype descriptor to work - I would have thought the information could be gathered and any remaining configuration became plugin configuration so the full descriptor is generated instead of hand crafted. - [ ] I still need to look more closely at create-from-project - it doesn't produce the acftual bundle when run so there's no way to take the generate sources and produce a JAR to release. It makes it a once off activity. - [ ] We need some documentation on how to use partial archetypes - [ ] Code - [ ] Should the interactive part of create-from-project that generates the properties file be a separate goal from the one that produces an archetype? - [ ] not all the archetype bundles have been converted to the new format (and are omitted from the parent pom modules list) - [ ] we previously agreed to remove the model from archetype-common and just use normal code - it's not read/write anywhere - [ ] Don't necessarily agree with the module structure - we should completely split out the actual archetypes, and make -core the top level - [ ] Not sure of the need for a clean goal - [ ] archetype.properties should be in target, automatically cleaned up, or not used at all (not sure why it is needed yet - seems to be inter-mojo configuration which can be achieved in other ways - see below) - [ ] I think it'd be better to compose the execution stages of various calls to components rather than orchestrating mojos in the lifecycle - I don't see the usefulness of the mojos independent of the lifecycles they are declared in so it's unnecessary complexity (unless I'm missing something?). Looks particularly weird on create and create-from-project (empty mojo) - [ ] I think the interactivity should be externalised rather than condition
Re: Jetty proxy config required?
The latest docs is there: http://docs.codehaus.org/pages/viewpage.action?pageId=73595 Brett Porter a écrit : I believe you can use that configuration, but like you I never have, just pointing it directly at :8080 from httpd. On 01/07/2007, at 3:11 PM, Wendy Smoak wrote: Is the Jetty Configuration section on this page up to date? http://maven.apache.org/continuum/guides/mini/guide-configuration.html I don't have access at the moment, but I'm pretty sure I'm using Apache httpd and mod_proxy with ProxyPass and ProxyPassReverse without configuring anything at all in Continuum. --Wendy
Re: How to define a dependancy without version number
On 7/2/07, Ralph Goers <[EMAIL PROTECTED]> wrote: Harish Kachoria wrote: I'm really curious as to how you got that to work in maven 1.0? AFAIK version numbers have always been required. +1 Stéphane Ralph - 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]
