Re: Maven 3.0 and Aether
Le mercredi 6 octobre 2010, Kristian Rosenvold a écrit : You can add http://github.com/sonatype/sonatype-aether/commits/master.atom to your reader/whatever, it's a a commit feed. yes, I know there are other ways to work. I tried, but I didn't manage to change my habits: I follow Maven changes with comm...@maven.apache.org mailing-list. Github can send a mail on every commit AFAIK, even if it doesn't contain the diff, the description would be useful. And this wouldn't impact actual Maven developers with Apache mailing lists. Note that I didn't see any Aether anouncement yet: such annoucements would be useful to get traction over other communities to integrate Aether. But I also suppose this information should be added to some kind of page describing how/what to do with external dependencies (on a slightly more general basis). Is there such a page ? http://maven.apache.org/guides/development/guide-m2-development.html seems the right place Regards, Hervé Kristian on., 06.10.2010 kl. 06.35 +0200, skrev Hervé BOUTEMY: I like the rewrite of dependency resolution component. And I perfectly understand the objective of hosting it apart from Maven: I hope to see another aether-provider implementation that shows success of this strategy. I have no doubt that if a Maven committer needs to improve Aether, it's easy to start with github fork, then he'll get necessary karma on Aether canonical repo as needed. And a lot of things can be done in maven-aether-provider (a lot of extensions can be done with actual API). I know that maven-aether-provider actually is missing unit tests because everything is tested in Aether itself and in core ITs: when I have time, I'll try to initiate unit tests so that impact of Aether changes on Maven core is more visible. But after a few months living with Aether, I have a problem to follow the components' modifications: I discover Aether changes only when I see in a commit mail that Maven core pom.xml integrates a new version af Aether. Having a mail on each Aether commit is really missing me. Can Aether send a mail on every commit to comm...@maven.apache.org, since this component is really crucial for Maven? Regards, Hervé Le mardi 5 octobre 2010, Ralph Goers a écrit : -0. I have the same objection to Aether that I noted when it was introduced. It is now much more difficult for me to enhance dependency resolution in Maven to include metadata beyond what the Aether api supports since Aether is not part of Maven. Ralph - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0
+1 -Lukas Benjamin Bentmann wrote: Hi, feedback on the RCs seems to be decreasing and I am currently not aware of any major regression so let's try and cross the finishing line of this marathon. We solved 31 issues since 3.0-beta-3: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=13142 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0
+1 Bring on the 3.0! -- Pull me down under... On Wed, Oct 6, 2010 at 6:32 PM, Brett Porter br...@apache.org wrote: +1
Re: [VOTE] Release Apache Maven 3.0
+1 tested in some projects and works fine Are we doing a PR with the press team? On Wed, Oct 6, 2010 at 11:35 AM, Mark Derricutt m...@talios.com wrote: +1 Bring on the 3.0! -- Pull me down under... On Wed, Oct 6, 2010 at 6:32 PM, Brett Porter br...@apache.org wrote: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] [TAKE 2] Release Maven Assembly Plugin version 2.2
Hi, We solved 92 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126version=12617 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MASSEMBLY+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-003/ Staging site: http://maven.apache.org/plugins/maven-assembly-plugin-2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here's my +1. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] [TAKE 2] Release Maven Assembly Plugin version 2.2
FWIW, Benjamin fixed an issue with the use of ${java.io.tmpdir} in Java
1.5, where non-existent temporary directories cause File.createTempFile
to fail. Additionally, I fixed an issue with the test of the
AssemblyProxyArchiver, in which I needed to call the setForced(..)
method in order to maintain the default behavior for these test methods
(since the forced/unforced behavior wasn't under tests).
On 10/6/10 11:34 AM, John Casey wrote:
Hi,
We solved 92 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126version=12617
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MASSEMBLY+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-003/
Staging site:
http://maven.apache.org/plugins/maven-assembly-plugin-2.2/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
Here's my +1.
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0
On Wed, Oct 6, 2010 at 9:37 AM, Carlos Sanchez car...@apache.org wrote: +1 tested in some projects and works fine Are we doing a PR with the press team? I pinged Sally earlier this month and will follow up. On Wed, Oct 6, 2010 at 11:35 AM, Mark Derricutt m...@talios.com wrote: +1 Bring on the 3.0! -- Pull me down under... On Wed, Oct 6, 2010 at 6:32 PM, Brett Porter br...@apache.org wrote: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1004461 - in /maven/plugins/trunk/maven-antrun-plugin/src: it/task-encoding-test/ it/task-encoding-test/pom.xml main/java/org/apache/maven/plugin/antrun/AntRunMojo.java
On 10/04/2010 05:45 PM, Benjamin Bentmann wrote:
Hi Paul,
Author: pgier
Date: Mon Oct 4 22:22:30 2010
New Revision: 1004461
URL: http://svn.apache.org/viewvc?rev=1004461view=rev
Log:
[MANTRUN-155] Set encoding for generated Ant build. Patch from Anders
Hammar with some minor changes.
Added:
maven/plugins/trunk/maven-antrun-plugin/src/it/task-encoding-test/
maven/plugins/trunk/maven-antrun-plugin/src/it/task-encoding-test/pom.xml
(with props)
Modified:
maven/plugins/trunk/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/AntRunMojo.java
+String encoding = project.getProperties().getProperty(
project.build.sourceEncoding );
+if ( encoding == null )
+{
+encoding = DEFAULT_ANT_BUILD_ENCODING;
+}
This approach violates the usual usage pattern for the source encoding
as outlined in [0]. First, the direct query to the property cuts off the
future migration to a POM element. Second, the default value for the
property is not UTF-8 but the platform encoding.
Given that the build file for Ant is auto-generated and not meant for
human consumption/editing, I don't see any reason why its encoding
should be configurable by the user and be linked to the sourceEncoding
property. As such, why not keept it simple and just always use UTF-8 for
the encoding? Always using UTF-8 also ensures that the build file can be
written at all, even if project.build.encoding is set to a charset that
can't represent the characters given in the POM.
Benjamin
[0]
http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi Benjamin,
My concern was that a character could be added to the POM that would not
be compatible with UTF-8, but I guess that is not an issue since it can
represent all the unicode chars. I see your point that I shouldn't use
a property, it should have been a plugin param instead to maintain
forward compatibility if/when sourceEncoding becomes a POM element.
I change it to always use UTF-8 in r1005210.
Thanks!
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Maven 3.0 reading non-maven build files
All -
I'm trying to support my company's migration to maven 3.0. In doing
so, I'd like for the existing XML build files (our own schema) to
continue to work, just with Maven reading them in. Our legacy build
files are fairly simple and map very easily to a pom.
My plan is to follow the model of pmaven-cli. That is, create a maven
binary specific to my company (that I'll distribute) which uses my own
ModelReader to process the old, legacy build files.
1. Does this sound like a reasonable approach?
2. Am I on the right track with this:
public class MyCompayMavenCli extends MavenCli {
@Override
protected ModelProcessor createModelProcessor( PlexusContainer
container ) throws ComponentLookupException {
// create a new ModelProcessor which is just like
DefaultModelProcessor except it uses
// a custom ModelReader.
}
}
Thanks,
Mike
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 3.0 reading non-maven build files
Copy what's in Polyglot is what will work for now. At some point in the future
we can dynamically load those extensions but they won't right now. So adding a
JAR with your model reader/writer will work.
On Oct 6, 2010, at 5:19 PM, Mike Lenner wrote:
All -
I'm trying to support my company's migration to maven 3.0. In doing
so, I'd like for the existing XML build files (our own schema) to
continue to work, just with Maven reading them in. Our legacy build
files are fairly simple and map very easily to a pom.
My plan is to follow the model of pmaven-cli. That is, create a maven
binary specific to my company (that I'll distribute) which uses my own
ModelReader to process the old, legacy build files.
1. Does this sound like a reasonable approach?
2. Am I on the right track with this:
public class MyCompayMavenCli extends MavenCli {
@Override
protected ModelProcessor createModelProcessor( PlexusContainer
container ) throws ComponentLookupException {
// create a new ModelProcessor which is just like
DefaultModelProcessor except it uses
// a custom ModelReader.
}
}
Thanks,
Mike
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.
-- Buddha
Re: [VOTE] Release Apache Maven 3.0
+1 Niall On Mon, Oct 4, 2010 at 1:16 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, feedback on the RCs seems to be decreasing and I am currently not aware of any major regression so let's try and cross the finishing line of this marathon. We solved 31 issues since 3.0-beta-3: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=13142 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
