Re: continuum project release white site
looks about right. The only thing I'm thinking is that the view output step is not required for all of the steps - just the mvn builds and SCM operations. Or perhaps it can just be one large output that is a link at the bottom? Cheers, Brett On 29/08/2006, at 2:07 PM, Edwin Punzalan wrote: Hi, After consulting with Brett, we've come up with the white site for releasing projects using continuum. Brett, if I missed something, please do remind me. I've deployed here for your viewing: http://people.apache.org/ ~epunzalan/continuum-white-site/groupStatus.html From the above page, the release link will only be available for projects which was built successfully. If you have time, please do have a look as we haven't gone to the phase of actually making the pages. Your feedback about the usability and completeness of the pages will be much appreciated. Thank you. ^_^
send patches where?
I decided to take some time and tackle some of the very large number of issues in Jira... however I don't have svn commit access. Is there any particular place I should send patches... and what format should the patches be in? - Brill Pappin
jpox errors wwriting tests
I'm getting a number of JPOX errors while trying to write a regression test. They are mostly to do with what it claims are bad definitions. Is anybody else getting this, or have I missed something? - Brill Pappin
Re: development standards
Hi Brill, That's great to hear! Some things to be aware of with Continuum: 1) A lot of JIRA stuff may now be redundant as trunk (1.1) is based on webwork, where 1.0.3 was based on plexus-summit. 2) There is a security overhaul going on as you'll see on this list. So if you are tackling issues related to that be sure to check in with the other devs about its applicability We use the same JIRA instance and standards as Maven, so this applies: http://maven.apache.org/guides/development/guide-helping.html Please submit patches to JIRA as attachments. Have fun! Cheers, Brett On 30/08/2006, at 2:29 PM, Brill Pappin wrote: Hi all... not commit access but doing some work and have a questions. The modules I'm working in are not using standard java formatting. Are there standards for code formatting in the project, and if so, can someone export their eclipse formatting config for me please? (I didn't see it in the source tree or on the site, but I may have missed it). It's important particularly if I'm going to be sending in patches -- so I don't send in a patch full of formatting changes. - Brill Pappin
Re: Snapshot Locations for maven-plugins a maven-assembly-plugin
Thanks all for your help On 8/28/06, Brett Porter [EMAIL PROTECTED] wrote: http://maven.apache.org/guides/development/guide-testing-development- plugins.html On 25/08/2006, at 10:47 PM, Alexis Midon wrote: Hi all, I'd like to use a snapshot version of the assembly plugin, but I can't found out a snapshot repository. Can someone tell me if such a repo is available or should I build a snapshot by myself? Thanks in advance, Alexis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: continuum project release white site
I've deployed the new white site with your suggestion. Brett Porter wrote: looks about right. The only thing I'm thinking is that the view output step is not required for all of the steps - just the mvn builds and SCM operations. Or perhaps it can just be one large output that is a link at the bottom? Cheers, Brett On 29/08/2006, at 2:07 PM, Edwin Punzalan wrote: Hi, After consulting with Brett, we've come up with the white site for releasing projects using continuum. Brett, if I missed something, please do remind me. I've deployed here for your viewing: http://people.apache.org/~epunzalan/continuum-white-site/groupStatus.html From the above page, the release link will only be available for projects which was built successfully. If you have time, please do have a look as we haven't gone to the phase of actually making the pages. Your feedback about the usability and completeness of the pages will be much appreciated. Thank you. ^_^
Re: Where is the KEYS file that I can add my key to?
On 28 Aug 06, at 4:04 PM 28 Aug 06, Dennis Lundberg wrote: I'll put together a draft for review. Dennis, I made a project wide module and placed the KEYS file in it along with a script to sync the KEYS to the right place on the server: http://svn.apache.org/repos/asf/maven/project/ Everyone involved in a Maven project has access and should modify the KEYS file there and then sync it. Thanks, Jason van Zyl [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Failing to build 2.1 snapshot from trunk
-Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: mardi 29 août 2006 00:03 To: Maven Developers List Subject: Re: Failing to build 2.1 snapshot from trunk trunk does not directly reference 2.3-SNAPSHOT so it would only be used by a plugin repository reference to that effect. I did a clean checkout from trunk. Thus it has to come from somewhere in trunk. In any case it would make sense that some projects in trunk reference snapshots so adding the snapshot repo would make sense I think. The bootstrap works successfully in CI, admittedly requiring 2 or 3 goes to get past ibiblio failures which is what I assume this is. Jason told me we're not using ibiblio anymore but the contegix box. Isn't that so? Does it fail consistently at the same point for you? Yes it did, until I added the snapshot repo to my settings.xml and then it worked (there was exception in one project in the console but it seems it was normal stack trace as the build reported success. Brett, don't you think it would help adding the snapshot repo to the top level pom.xml in trunk? Thanks -Vincent On 28/08/2006, at 8:41 PM, Vincent Massol wrote: Hi, I've seen several emails saying that people has trouble building from trunk. I also have some problems. I've just removed my full local repo and ran bootstrap in components several times (to account for the sporadic download failures). Here's what I got in the end: C:\dev\maven\trunks\componentsbootstrap [...] [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Maven [INFO] Maven Artifact [INFO] Maven Repository Metadata Model [INFO] Maven Artifact Manager [INFO] Maven Model [INFO] Maven Local Settings Model [INFO] Maven Artifact Test Helper Library [INFO] Maven Plugin Parameter Documenter API [INFO] Maven Tools [INFO] Maven Profile Model [INFO] Maven Error Diagnostics [INFO] Maven Plugin API [INFO] Maven Reporting [INFO] Maven Reporting API [INFO] Maven Project Builder [INFO] Maven Plugin Registry Model [INFO] Maven Plugin Descriptor Model [INFO] Maven Monitor [INFO] Maven Core [INFO] Maven Plugin Tools Base POM [INFO] Maven Plugin Tools APIs [INFO] Maven Plugin Tools for Java [INFO] Maven Plugin Tools for Beanshell [INFO] Maven Pluggy Simplistic Plugin Generator [INFO] Maven Plugin Metadata Model [INFO] Maven Ant Plugin Tools [INFO] Maven Reporting Implementation [INFO] Maven Script Support Root [INFO] Maven Ant Mojo Support [INFO] Maven Beanshell Mojo Support [INFO] Maven Embedder [INFO] Maven Core - CLI [INFO] -- -- [INFO] Building Maven [INFO]task-segment: [clean, install] [INFO] -- -- Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin- parent/2 .0/maven-pl ugin-parent-2.0.pom 6K downloaded [INFO] [clean:clean] [INFO] Deleting directory C:\dev\maven\trunks\components\target [INFO] Deleting directory C:\dev\maven\trunks\components\target \classes [INFO] Deleting directory C:\dev\maven\trunks\components\target \test-classes [INFO] [site:attach-descriptor] [INFO] [install:install] [INFO] Installing C:\dev\maven\trunks\components\pom.xml to C: \Documents and Settings\vmassol\.m2\re pository\org\apache\maven\maven\2.1-SNAPSHOT\maven-2.1-SNAPSHOT.pom [INFO] -- -- [INFO] Building Maven Artifact [INFO]task-segment: [clean, install] [INFO] -- -- [INFO] [clean:clean] [INFO] Deleting directory C:\dev\maven\trunks\components\maven-artifact\target [INFO] Deleting directory C:\dev\maven\trunks\components\maven-artifact\target\classes [INFO] Deleting directory C:\dev\maven\trunks\components\maven-artifact\target\test-classes [INFO] -- -- [ERROR] BUILD FAILURE [INFO] -- -- [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is corr ect: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-surefire-plugin \ -Dversion=2.3-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/ path/to/file org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.3- SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2)
Re: [RANT] Maven is both heaven and hell
Sorry, I did walk away there for a little bit. On 8/27/06, Brett Porter [EMAIL PROTECTED] wrote: On 28/08/2006, at 7:14 AM, Wendell Beckwith wrote: Take toady's latest example, say you want to remove an ant build file and do things the maven way, so you decide to use the dependency plugin. The web site examples have the group and artifactId being groupIdorg.apache.maven.plugin/groupId artifactIddependency-maven-plugin/artifactId The dependency plugin was accepted to this project, but hasn't yet been released here. IMO, we should remove it from the plugin list or put it in a separate section as it shouldn't be considered ready for use here yet. Still, please do file bugs against it where there are documentation issues. Done. http://jira.codehaus.org/browse/MDEP-34 1.) Publish a project plan and commit to periodic milestones. Yes, we need a roadmap. Development on the Maven core has been on the backkburner as we fix peoples pressing issues and work on the plugins and, funnily enough, the documentation. As you'll have seen on this list recently, John has been putting a lot of topics together for discussion and they come up from time to time and get recorded. At some point in the near future we'll have a roadmap for 2.1 out. A lot of plugins still are attached to beta APIs even when there are 2 or more released versions of the artifact available. Specific examples? I don't see this in any plugins that aren't themselves beta plugins. For each milestone release all code should be compiled with the latest as the rule rather than the exception. I'm not really sure what this achieves for the end user, and whether you are talking about just maven, or all its plugins too. I assume you are referring to us learning from Callisto here, which I've already ranted about on my blog, but I'd be interested to hear from someone who is closer to that community that knows the tangible benefits it brough. I suppose this depends on where you draw the line between maven core (whatever that is) and its plugins. In all honesty I don't know where that line lies. So some of what I see may be related to the plugins and not maven itsself. At present I can't think of where I saw a maven plugin using a beta api but I do remember that while tracking something done in the repo I noticed that there were 2 full versions ( x.0 and x.0.1) already available and that the code was calling for an 2.0-beta version. I recently wiped and rebuild my local repo, and ran a search across all poms in the org.apache.maven group and didn't turn up anything, so perhaps it's all better now. Until I can produce some reliable evidence I would mark this as unreproducible. The plan will let the community know what's coming and when we can expect every milestone build between now and the release. The plan is not static as you can updated whenever you want. Yes, that's a good idea. For my team, I have been using, with minor adaptations, the eclipse dev process and in general I think it has the right amount of agility. We post our plan early with our commited, proposed, deferred and rejected items for the next release and we revise it through out the release process. We use confluence for posting so that people interested in it can subscribe just to that page to cut down on unwanted emails. Therefore, when we make updated everyone who wants to be notified is notified and they can either comment on the issues we have attached to each plan item or start a forum discussion. I've create a template that maybe of use to you all if you wanted to go this way. 2.) Produce nightly and weekly integration builds. We already do. We could do it better. I've brought this topic up a couple of times on the Continuum list. I'm not on that list but I guess I will have to be to get a better picture of what's going on. Maybe this is happening, but how would I know? Both the Maven 2 and Continuum websites have a dead link to the Continuous Integration server, http://maven.zones.apache.org:8080/continuum.http:// maven.zones.apache.org:8080/continuum This seems to be the problem. Our nightly builds are produced from an old system that we were intending to move to Continuum so hadn't published links to. On the Continuum side, we had to move the server temporarily due to resource constraints and the links haven't been updated yet. Please file an issue for these. Done. http://jira.codehaus.org/browse/MNG-2535 3. Update the website regularly. Just split the thing down the middle into released info (doc, tutorials, examples, etc) and development current info which at a minimum would be the last stable milestone. There's been significant discussion on this on the list already which I can give you pointers to if you need them, but I'm not rehashing them again. I'm happy with the plan we have. Unfortunately, when people have put forward proposals recently they've been met with silence. We need more
build maven plugins from trunk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, As fix for MSITE-138, I want to build the maven-site-plugin from trunk. As I figured out, I also need to update maven-plugin-plugin that also requires me to update maven itself. As suggested by Vincent, I got the latest integration build which was m2-20060828.203000.tar.gz (2.1-SNAPSHOT). I checked out http://svn.apache.org/repos/asf/maven/plugins/trunk and tried to build this with the new maven. Unfortunately I got stuck again. I always get: [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-plugin-plugin Version: 2.0-alpha-3 Since maven did not tell me the path to this dependency, I decided to move my complete local repository (~/.m2/repository) away and start from scratch. Then maven only downloaded apache-3.pom and maven-parent-4.pom and then failed with the same error. As I greped in the downloaded POMs for maven-plugin-plugin, I got no results. To me it seems that maven itself is wired with the dependency on maven-plugin-plugin:2.0-alpha-3 (+). Since maven-plugin-plugin:2.0-alpha-3 is not available and I can not build maven-plugin-plugin I am stuck. Any suggestions what to do? Thanks a lot... Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFE9KrGmPuec2Dcv/8RAqJhAJ9PB2HYHeFEePG4weMaLvq4K0C9dQCeJFIV 7Z8hgrMavddpHyNMsNeOLeg= =ZK2r -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failing to build 2.1 snapshot from trunk
On 29 Aug 06, at 3:32 PM 29 Aug 06, Vincent Massol wrote: -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: mardi 29 août 2006 00:03 To: Maven Developers List Subject: Re: Failing to build 2.1 snapshot from trunk trunk does not directly reference 2.3-SNAPSHOT so it would only be used by a plugin repository reference to that effect. I did a clean checkout from trunk. Thus it has to come from somewhere in trunk. In any case it would make sense that some projects in trunk reference snapshots so adding the snapshot repo would make sense I think. The bootstrap works successfully in CI, admittedly requiring 2 or 3 goes to get past ibiblio failures which is what I assume this is. Jason told me we're not using ibiblio anymore but the contegix box. Isn't that so? It's where we are housing the repository, it's not acting as central quite yet. Does it fail consistently at the same point for you? Yes it did, until I added the snapshot repo to my settings.xml and then it worked (there was exception in one project in the console but it seems it was normal stack trace as the build reported success. Brett, don't you think it would help adding the snapshot repo to the top level pom.xml in trunk? Thanks -Vincent On 28/08/2006, at 8:41 PM, Vincent Massol wrote: Hi, I've seen several emails saying that people has trouble building from trunk. I also have some problems. I've just removed my full local repo and ran bootstrap in components several times (to account for the sporadic download failures). Here's what I got in the end: C:\dev\maven\trunks\componentsbootstrap [...] [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Maven [INFO] Maven Artifact [INFO] Maven Repository Metadata Model [INFO] Maven Artifact Manager [INFO] Maven Model [INFO] Maven Local Settings Model [INFO] Maven Artifact Test Helper Library [INFO] Maven Plugin Parameter Documenter API [INFO] Maven Tools [INFO] Maven Profile Model [INFO] Maven Error Diagnostics [INFO] Maven Plugin API [INFO] Maven Reporting [INFO] Maven Reporting API [INFO] Maven Project Builder [INFO] Maven Plugin Registry Model [INFO] Maven Plugin Descriptor Model [INFO] Maven Monitor [INFO] Maven Core [INFO] Maven Plugin Tools Base POM [INFO] Maven Plugin Tools APIs [INFO] Maven Plugin Tools for Java [INFO] Maven Plugin Tools for Beanshell [INFO] Maven Pluggy Simplistic Plugin Generator [INFO] Maven Plugin Metadata Model [INFO] Maven Ant Plugin Tools [INFO] Maven Reporting Implementation [INFO] Maven Script Support Root [INFO] Maven Ant Mojo Support [INFO] Maven Beanshell Mojo Support [INFO] Maven Embedder [INFO] Maven Core - CLI [INFO] -- -- [INFO] Building Maven [INFO]task-segment: [clean, install] [INFO] -- -- Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin- parent/2 .0/maven-pl ugin-parent-2.0.pom 6K downloaded [INFO] [clean:clean] [INFO] Deleting directory C:\dev\maven\trunks\components\target [INFO] Deleting directory C:\dev\maven\trunks\components\target \classes [INFO] Deleting directory C:\dev\maven\trunks\components\target \test-classes [INFO] [site:attach-descriptor] [INFO] [install:install] [INFO] Installing C:\dev\maven\trunks\components\pom.xml to C: \Documents and Settings\vmassol\.m2\re pository\org\apache\maven\maven\2.1-SNAPSHOT\maven-2.1-SNAPSHOT.pom [INFO] -- -- [INFO] Building Maven Artifact [INFO]task-segment: [clean, install] [INFO] -- -- [INFO] [clean:clean] [INFO] Deleting directory C:\dev\maven\trunks\components\maven-artifact\target [INFO] Deleting directory C:\dev\maven\trunks\components\maven-artifact\target\classes [INFO] Deleting directory C:\dev\maven\trunks\components\maven-artifact\target\test-classes [INFO] -- -- [ERROR] BUILD FAILURE [INFO] -- -- [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is corr ect: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-surefire-plugin \ -Dversion=2.3-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/ path/to/file org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.3- SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.3- SNAPSHOT from the
maven-solaris-plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, as I promised some time ago, I wanted to provide my work in creating a maven2 plugin for solaris packaging. I uses an ant mojo and only works on a solaris machine with pkgtools installed. For the moment I set in the POM groupId to org.apache.maven.plugins and artifactId maven-solaris-plugin. Should I set groupId to org.codehaus.mojo instead? Where should I put the current state? I have the plugin itself and a dummy example project that is using the plugin. Should I create the example as archtype? Best regards Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFE9K7gmPuec2Dcv/8RAry4AJ45LMrZkDCjEuHHeBfMGv7VxNiNnwCbBfPZ F4ckVHeeS+aIYvQ7opVN9JI= =+1JG -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where is the KEYS file that I can add my key to?
Jason van Zyl wrote: On 28 Aug 06, at 4:04 PM 28 Aug 06, Dennis Lundberg wrote: I'll put together a draft for review. Dennis, I made a project wide module and placed the KEYS file in it along with a script to sync the KEYS to the right place on the server: http://svn.apache.org/repos/asf/maven/project/ Everyone involved in a Maven project has access and should modify the KEYS file there and then sync it. Thanks, Jason van Zyl [EMAIL PROTECTED] Thanks Jason. I've added my key and synced the KEYS file. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build maven plugins from trunk
Hi Jörg, Based on your comments, here are my succesfull steps to build maven-site-plugin from scratch: - dwl and install m2-20060828.203000.tar.gz - removed my repository - added snapshot repository (see [1]) - build Maven (see [2]) * svn co http://svn.apache.org/repos/asf/maven/components/trunk/ * mvn -Papache install * mvn -Pcodehaus install (if failed for some plexus or modello artefacts) - build maven site * svn co http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-plugin * mvn -Papache install To use maven-site, you need also PIR plugin so: - svn co https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin - mvn -Papache install HTH Could you provide us the full stack trace? I dont see any reference to maven-plugin-plugin:2.0-alpha-3. Cheers, Vincent [1] http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html [2] http://maven.apache.org/guides/development/guide-building-m2.html 2006/8/29, Joerg Hohwiller [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, As fix for MSITE-138, I want to build the maven-site-plugin from trunk. As I figured out, I also need to update maven-plugin-plugin that also requires me to update maven itself. As suggested by Vincent, I got the latest integration build which was m2-20060828.203000.tar.gz (2.1-SNAPSHOT). I checked out http://svn.apache.org/repos/asf/maven/plugins/trunk and tried to build this with the new maven. Unfortunately I got stuck again. I always get: [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-plugin-plugin Version: 2.0-alpha-3 Since maven did not tell me the path to this dependency, I decided to move my complete local repository (~/.m2/repository) away and start from scratch. Then maven only downloaded apache-3.pom and maven-parent-4.pom and then failed with the same error. As I greped in the downloaded POMs for maven-plugin-plugin, I got no results. To me it seems that maven itself is wired with the dependency on maven-plugin-plugin:2.0-alpha-3 (+). Since maven-plugin-plugin:2.0-alpha-3 is not available and I can not build maven-plugin-plugin I am stuck. Any suggestions what to do? Thanks a lot... Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFE9KrGmPuec2Dcv/8RAqJhAJ9PB2HYHeFEePG4weMaLvq4K0C9dQCeJFIV 7Z8hgrMavddpHyNMsNeOLeg= =ZK2r -END PGP SIGNATURE- - 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: maven-solaris-plugin
Hi I think the best way is to create an issue for the sandbox component http://jira.codehaus.org/browse/MNG Cheers, Vincent 2006/8/29, Joerg Hohwiller [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, as I promised some time ago, I wanted to provide my work in creating a maven2 plugin for solaris packaging. I uses an ant mojo and only works on a solaris machine with pkgtools installed. For the moment I set in the POM groupId to org.apache.maven.plugins and artifactId maven-solaris-plugin. Should I set groupId to org.codehaus.mojo instead? Where should I put the current state? I have the plugin itself and a dummy example project that is using the plugin. Should I create the example as archtype? Best regards Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFE9K7gmPuec2Dcv/8RAry4AJ45LMrZkDCjEuHHeBfMGv7VxNiNnwCbBfPZ F4ckVHeeS+aIYvQ7opVN9JI= =+1JG -END PGP SIGNATURE- - 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: build maven plugins from trunk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Siveton wrote:
Hi Jörg,
Hi Vincent,
thanks for your quick reply...
Based on your comments, here are my succesfull steps to build
maven-site-plugin from scratch:
- dwl and install m2-20060828.203000.tar.gz
ok
- removed my repository
again and again ;)
- added snapshot repository (see [1])
had this setup...
- build Maven (see [2])
* svn co http://svn.apache.org/repos/asf/maven/components/trunk/
no worries
* mvn -Papache install
* mvn -Pcodehaus install (if failed for some plexus or modello artefacts)
both do not work - even
mvn -Papache,codehaus install
does NOT work:
[INFO] Building Maven Core
[INFO]task-segment: [install]
[INFO]
Downloading:
http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/2.0-beta-1-SNAPSHOT/maven-assembly-plugin-2.0-beta-1-SNAPSHOT.pom
[WARNING] Unable to get resource from repository codehaus.plugin.snapshots
(http://snapshots.maven.codehaus.org/maven2)
Downloading:
http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-assembly-plugin/2.0-beta-1-SNAPSHOT/maven-assembly-plugin-2.0-beta-1-SNAPSHOT.pom
[WARNING] Unable to get resource from repository apache.snapshots
(http://people.apache.org/maven-snapshot-repository)
Downloading:
http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-assembly-plugin/2.0-beta-1-SNAPSHOT/maven-assembly-plugin-2.0-beta-1-SNAPSHOT.pom
[WARNING] Unable to get resource from repository apache.snapshots
(http://people.apache.org/maven-snapshot-repository)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-assembly-plugin
Version: 2.0-beta-1-SNAPSHOT
Reason: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-assembly-plugin:pom:2.0-beta-1-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
codehaus.plugin.snapshots (http://snapshots.maven.codehaus.org/maven2),
apache.snapshots (http://people.apache.org/maven-snapshot-repository)
- build maven site
* svn co
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-plugin
* mvn -Papache install
To use maven-site, you need also PIR plugin so:
- svn co
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin
- mvn -Papache install
HTH
Could you provide us the full stack trace? I dont see any reference to
maven-plugin-plugin:2.0-alpha-3.
Can not reproduce right now - therefore I get this for latest maven-plugins:
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/2/maven-plugins-2.pom
6K downloaded
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='org.apache.maven.plugins:maven-javadoc-plugin'}' and
'Vertex{label='org.apache.maven.plugins:maven-checkstyle-plugin'}' introduces to
cycle in the graph org.apache.maven.plugins:maven-checkstyle-plugin --
org.apache.maven.plugins:maven-javadoc-plugin --
org.apache.maven.plugins:maven-checkstyle-plugin
Cheers,
Vincent
Thanks so far
Jörg
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE9MLmmPuec2Dcv/8RAhj+AJsFH+plQQ/ll7BgasvUI6ZC9jjCNQCfZpjc
ZxNABwGRjXfswsDyBv3essU=
=O0iM
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven Sandbox for Apache Committers
Hi, I'm sending this here as folks developing Maven projects probably all subscribe here. On the PMC list we've talked about setting up a sandbox that all Apache committers would have access to so that experimentation with Maven projects can happen easily. Case in point: Jeremy and Edwin are working on a new feature in Continuum so we setup a branch for them to work on as the are both Apache committers, both have CLAs on file so we just gave them access. Now for this feature we also need some work done on the release plugin which Jeremy is also working on. So instead of doing one offs every time we want to allow people to experiment or collaborate with one another we came up with the idea of creating a sandbox that any Apache committer can work in. John asked that we air this idea on the dev list. I don't think there is any downside as it makes it easier for folks to work on Maven and contribute. We already have a sandbox so we could just open the perms on that. It's a free for all in there anyway. If we find that we have so many contributors and need sandboxes for each project then we can do that in the future but for now I think opening the perms on the sandbox would be a fine start. +1 Jason van Zyl [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Sandbox for Apache Committers
Hi All, I'm not sure if I'm allowed to vote but I will put my two cents in anyways. I think this would make things a lot easier on those like me trying to get involved in Continuum and Maven. I spent 2 hours last night trying to figure out how IntelliJ screwed up my working copy just so I didn't lose 3 days worth of work and with an actual place to have been committing source, that wouldn't had been the case. I think since all Apache Committers have filled out the same paperwork it should be permissible as long as it doesn't create too much of a burden. +1 (If my vote counts of course.) Take care, Jeremy Whitlock On 8/29/06, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, I'm sending this here as folks developing Maven projects probably all subscribe here. On the PMC list we've talked about setting up a sandbox that all Apache committers would have access to so that experimentation with Maven projects can happen easily. Case in point: Jeremy and Edwin are working on a new feature in Continuum so we setup a branch for them to work on as the are both Apache committers, both have CLAs on file so we just gave them access. Now for this feature we also need some work done on the release plugin which Jeremy is also working on. So instead of doing one offs every time we want to allow people to experiment or collaborate with one another we came up with the idea of creating a sandbox that any Apache committer can work in. John asked that we air this idea on the dev list. I don't think there is any downside as it makes it easier for folks to work on Maven and contribute. We already have a sandbox so we could just open the perms on that. It's a free for all in there anyway. If we find that we have so many contributors and need sandboxes for each project then we can do that in the future but for now I think opening the perms on the sandbox would be a fine start. +1 Jason van Zyl [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
newbie build question
I just did a clean co of maven 2 and tried to build the site and some other components. I found that the site pom, like the others that I looked at, derives from maven-parent, version 4-SNAPSHOT, with a relative path specified that points to /poms/maven/pom.xml. The version in the parent itself is now 5-SNAPSHOT. Is this an error - i.e., do the child poms need to be updated, or is there a repo that I am missing somewhere that has the 4-SNAPSHOT version of the parent? Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failing to build 2.1 snapshot from trunk
On 30/08/2006, at 5:32 AM, Vincent Massol wrote: Brett, don't you think it would help adding the snapshot repo to the top level pom.xml in trunk? Which snapshot repo? The apache one is already in the parent POM. There's something else going on here (bearing in mind that this is working just fine in the clean room build after it gets over the ibiblio hiccups). - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbie build question
The children need to be updated for the release. There is a repository - but its a chicken and egg problem (need the repo to specify the repo without doing it in every pom :) The parent should only be set to a snapshot when something is really needed from the new version, so setting it to a release is fine. - Brett On 30/08/2006, at 9:31 AM, Phil Steitz wrote: I just did a clean co of maven 2 and tried to build the site and some other components. I found that the site pom, like the others that I looked at, derives from maven-parent, version 4-SNAPSHOT, with a relative path specified that points to /poms/maven/pom.xml. The version in the parent itself is now 5-SNAPSHOT. Is this an error - i.e., do the child poms need to be updated, or is there a repo that I am missing somewhere that has the 4-SNAPSHOT version of the parent? Phil - 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: build maven plugins from trunk
Ugh. I was -1 on the commit that caused this and it hasn't yet been fixed. I'll be rolling it back later today. IT should build with Maven 2.0.4 and no changes to the plugin plugin. I can't see that it needs the latter, but it certainly requires Maven 2.1 which is not good. - Brett On 30/08/2006, at 8:12 AM, Vincent Siveton wrote: Hi Jörg, Based on your comments, here are my succesfull steps to build maven-site-plugin from scratch: - dwl and install m2-20060828.203000.tar.gz - removed my repository - added snapshot repository (see [1]) - build Maven (see [2]) * svn co http://svn.apache.org/repos/asf/maven/components/trunk/ * mvn -Papache install * mvn -Pcodehaus install (if failed for some plexus or modello artefacts) - build maven site * svn co http://svn.apache.org/repos/asf/maven/plugins/trunk/maven- site-plugin * mvn -Papache install To use maven-site, you need also PIR plugin so: - svn co https://svn.apache.org/repos/asf/maven/plugins/trunk/maven- project-info-reports-plugin - mvn -Papache install HTH Could you provide us the full stack trace? I dont see any reference to maven-plugin-plugin:2.0-alpha-3. Cheers, Vincent [1] http://maven.apache.org/guides/development/guide-plugin- snapshot-repositories.html [2] http://maven.apache.org/guides/development/guide-building-m2.html 2006/8/29, Joerg Hohwiller [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, As fix for MSITE-138, I want to build the maven-site-plugin from trunk. As I figured out, I also need to update maven-plugin-plugin that also requires me to update maven itself. As suggested by Vincent, I got the latest integration build which was m2-20060828.203000.tar.gz (2.1-SNAPSHOT). I checked out http://svn.apache.org/repos/asf/maven/plugins/trunk and tried to build this with the new maven. Unfortunately I got stuck again. I always get: [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-plugin-plugin Version: 2.0-alpha-3 Since maven did not tell me the path to this dependency, I decided to move my complete local repository (~/.m2/repository) away and start from scratch. Then maven only downloaded apache-3.pom and maven- parent-4.pom and then failed with the same error. As I greped in the downloaded POMs for maven-plugin-plugin, I got no results. To me it seems that maven itself is wired with the dependency on maven-plugin-plugin:2.0-alpha-3 (+). Since maven-plugin-plugin:2.0-alpha-3 is not available and I can not build maven-plugin-plugin I am stuck. Any suggestions what to do? Thanks a lot... Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFE9KrGmPuec2Dcv/8RAqJhAJ9PB2HYHeFEePG4weMaLvq4K0C9dQCeJFIV 7Z8hgrMavddpHyNMsNeOLeg= =ZK2r -END PGP SIGNATURE- - 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]
Re: Maven Sandbox for Apache Committers
+1 Nice idea. Regards, Alan Jason van Zyl wrote: Hi, I'm sending this here as folks developing Maven projects probably all subscribe here. On the PMC list we've talked about setting up a sandbox that all Apache committers would have access to so that experimentation with Maven projects can happen easily. Case in point: Jeremy and Edwin are working on a new feature in Continuum so we setup a branch for them to work on as the are both Apache committers, both have CLAs on file so we just gave them access. Now for this feature we also need some work done on the release plugin which Jeremy is also working on. So instead of doing one offs every time we want to allow people to experiment or collaborate with one another we came up with the idea of creating a sandbox that any Apache committer can work in. John asked that we air this idea on the dev list. I don't think there is any downside as it makes it easier for folks to work on Maven and contribute. We already have a sandbox so we could just open the perms on that. It's a free for all in there anyway. If we find that we have so many contributors and need sandboxes for each project then we can do that in the future but for now I think opening the perms on the sandbox would be a fine start. +1 Jason van Zyl [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]
Re: [RANT] Maven is both heaven and hell
Good day, About a couple of months ago, the documentation site of the maven 2 plugins have been revised [1]. Though most have already been reviewed, they are still not yet out for release. However, now that the documentation issue have been raised again, I am wondering of how we are going to go about this? Are new documentation issues be applied to (a) the current documentation in the maven site, (b) the latest documentation though they're not yet released, (c) both a b, or (d) ? Thanks, Franz [1] http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependency order in DefaultModelInheritanceAssembler
Hi All,
I've noticed that in
org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler, the
method below:
private void assembleDependencyInheritance( Model child, Model parent )
{
Map depsMap = new HashMap();
List deps = parent.getDependencies();
if ( deps != null )
{
for ( Iterator it = deps.iterator(); it.hasNext(); )
{
Dependency dependency = (Dependency) it.next();
depsMap.put( dependency.getManagementKey(), dependency );
}
}
deps = child.getDependencies();
if ( deps != null )
{
for ( Iterator it = deps.iterator(); it.hasNext(); )
{
Dependency dependency = (Dependency) it.next();
depsMap.put( dependency.getManagementKey(), dependency );
}
}
child.setDependencies( new ArrayList( depsMap.values() ) );
}
is called by the buildFromRepository method in
org.apache.maven.project.DefaultProjectBuilder (and I'm sure a few other
places too). The effect it has, is that the dependencies in the pom of the
project, come back in a different order to how they were declared in the
pom.
Now, I'm guessing the reason for the above code being implemented the way it
is, is to allow easy handling of potential duplicates, the only problem is
that the order is lost in the process. Or is this intentional, if it is can
you explain why? If its not, I would think that there would be a large
benefit in changing the above code so that it maintains the order. I'm happy
to submit a JIRA request with my patch for it if that is the case.
Regards
Gareth Tilley
--
View this message in context:
http://www.nabble.com/Dependency-order-in-DefaultModelInheritanceAssembler-tf2187909.html#a6052791
Sent from the Maven Developers forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
