Dependency Tree question for ears with war dependency
I'm having difficulty understanding why performing a dependency:tree on an ear, will give me transitive dependencies for a dependent artifact with packaging type jar, but not of type war. Here is the sample output from a project (strictly for demo purposes): emiles-macbook:myapp emiles$ mvn dependency:tree [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] My Application [INFO] mywebapp [INFO] myapplib [INFO] myear [INFO] [INFO] [INFO] Building My Application 0.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ myapp --- [INFO] com.captechventures.sandbox:myapp:pom:0.0.1-SNAPSHOT [INFO] [INFO] [INFO] Building mywebapp 0.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ mywebapp --- [INFO] com.captechventures.sandbox:mywebapp:war:0.0.1-SNAPSHOT [INFO] \- com.captechventures.sandbox:mysharedlib:jar:wlssl:1.0.0:compile [INFO] [INFO] [INFO] Building myapplib 0.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ myapplib --- [INFO] com.captechventures.sandbox:myapplib:jar:0.0.1-SNAPSHOT [INFO] \- commons-lang:commons-lang:jar:2.1:compile [INFO] [INFO] [INFO] Building myear 0.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ myear --- [INFO] com.captechventures.sandbox:myear:ear:0.0.1-SNAPSHOT [INFO] +- com.captechventures.sandbox:mywebapp:war:0.0.1-SNAPSHOT:compile [INFO] \- com.captechventures.sandbox:myapplib:jar:0.0.1-SNAPSHOT:compile [INFO]\- commons-lang:commons-lang:jar:2.1:compile [INFO] [INFO] Reactor Summary: [INFO] [INFO] My Application SUCCESS [1.445s] [INFO] mywebapp .. SUCCESS [0.138s] [INFO] myapplib .. SUCCESS [0.028s] [INFO] myear . SUCCESS [0.103s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 2.421s [INFO] Finished at: Mon Apr 11 10:27:27 EDT 2011 [INFO] Final Memory: 5M/81M [INFO] You'll notice during the ear build, the transitive dependencies for the jar file are shown (and can be navigated programmatically), however the war's dependencies are not included at the ear level. This is problematic as I am writing a plugin that will navigate the entire dependency tree for the ear (should include transitive dependencies as well) and perform a business function. This is not working as expected as we get no dependencies of the war in the DependencyTreeBuilder. Thoughts? Hints? Suggestions? Thanks in advance. Eric Miles Manager / Architect | CapTech emi...@captechconsulting.comemi...@captechventures.com
plugin dependencies question
All, I have a plugin I wrote, that use framework FooBar. This plugin will work with FooBar version 1.1 through 1.8. I have numerous maven projects that use my plugin and all use different versions of FooBar. The version of FooBar is important to each project as compilation is performed (compiled units are not backwards compatible). Is there a way to create my plugin so that it uses FooBar for compilation, however the individual projects specify which version of FooBar to the plugin via the pom? Thanks in advance, Eric Miles - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin dependencies question
I see there's only 5 issues outstanding left for 2.0.9. Does anyone know when the expected release date is? Thanks so much! On Wed, 2008-03-12 at 19:22 -0400, Brian E. Fox wrote: Handy, isn't it? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 7:18 PM To: Maven Users List Subject: Re: plugin dependencies question That's new in 2.0.9. Well, not new, but now it works. ;-) Wayne On 3/12/08, Brian E. Fox [EMAIL PROTECTED] wrote: Yes. Compile against foobar normally. The users can specify the dependency they want in the plugin configuration block. This is working in 2.0.9, you can see http://jira.codehaus.org/browse/MNG-3426 and http://jira.codehaus.org/browse/MNG-2972 for more information. In this way you can say your plugin will use FooBar version x.y by default, but if they want to use another one, they can do so by overriding it in their pom. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:24 PM To: users@maven.apache.org Subject: plugin dependencies question All, I have a plugin I wrote, that use framework FooBar. This plugin will work with FooBar version 1.1 through 1.8. I have numerous maven projects that use my plugin and all use different versions of FooBar. The version of FooBar is important to each project as compilation is performed (compiled units are not backwards compatible). Is there a way to create my plugin so that it uses FooBar for compilation, however the individual projects specify which version of FooBar to the plugin via the pom? Thanks in advance, Eric Miles - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Archiva crashes after a couple of days
I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. I asked the mailing list if there was a way to clear these queue of events so I could let the app run its course, but received no answers. i eventually had to reinstall fresh to get around it but all works great now. FYI, we're on RHEL 4 update 4 as well. Eric On Fri, 2008-02-22 at 13:01 -0800, Jason Chaffee wrote: I am running on RedHat Enterprise 4 update 4. It has crashed on m2 at least 6 times in the last two weeks and I am not doing anything special with it. Also, I have noticed that it is creating almost 5 Gigs in logs files a day. I wonder if this has anything to do with it. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 12:45 PM To: archiva-users@maven.apache.org Subject: Re: Archiva crashes after a couple of days Jason, I can tell you that we've had our Archiva instance up and running for at least 3+ weeks without having to restart. We have 5 repositories and about 6 remote repositories and we too are using the standalone product and nearly all consumers. What platform are you running on? Eric On Fri, 2008-02-22 at 12:40 -0800, Jason Chaffee wrote: I am running the standalone archiva and I have about 4 managed repositories (including a proxy repo), and about 6 or 7 remote repositories. I create a single proxy connector to all of the remote repositories and changed my settings.xml to be a mirrorOf *. Currently, I only have my Continuous Integration box configured to use Archiva as a proxy and I am finding that it crashes every couple of days. Also, I am running all of default consumers and I do see the bug about invalid path for some artifacts (Bret Porter closed the bug yesterday and the fix will be in 1.0.2). Has anyone else seen this? Any ideas?
RE: Archiva crashes after a couple of days
We use: 0 30 2 * * ? - daily at 2:30 am 0 30 * * * ? - every 30 mins The default out of the box shouldn't be an issue I wouldn't think. How large are your repos? Ours: 344Mjasper 332Kplugins 203Mproxied 107Mreleases 239Msnapshots On Fri, 2008-02-22 at 13:28 -0800, Jason Chaffee wrote: I am using the defaults, out of box expressions. So, it seems those too could be fine tuned. -Original Message- From: Brown, Carlton [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:14 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 4:07 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. Me three. I didn't see any reason not to scan every minute, but in fact it was every second. Result - massive log files, Archiva hung. Did not have to reinstall it, though. The cron setup would be a good candidate for improved input forms and/or validation. - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
RE: Archiva crashes after a couple of days
Wow, you got us beat. Those are pretty large repos. Maybe the Archiva team can comment on this. I'm interested to hear what they say. Eric On Fri, 2008-02-22 at 16:39 -0800, Jason Chaffee wrote: They are pretty big, both in number of artifacts and in size. Our largest repo has around 75,000 artifacts in right now and the size is over 200 GB. This is a snapshot repo and we have many teams that are creating large installer artifacts that are basically uber artifacts, thus the size of these artifacts can be quite large. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:38 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days We use: 0 30 2 * * ? - daily at 2:30 am 0 30 * * * ? - every 30 mins The default out of the box shouldn't be an issue I wouldn't think. How large are your repos? Ours: 344Mjasper 332Kplugins 203Mproxied 107Mreleases 239Msnapshots On Fri, 2008-02-22 at 13:28 -0800, Jason Chaffee wrote: I am using the defaults, out of box expressions. So, it seems those too could be fine tuned. -Original Message- From: Brown, Carlton [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:14 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 4:07 PM To: archiva-users@maven.apache.org Subject: RE: Archiva crashes after a couple of days I too had this same issue. Make sure your cron syntax is correct as it is not standard unix cron syntax. The first entry is a second number, not minutes. I initially (and accidentally) setup our cron jobs to run at a crazy pace, I think every second. Me three. I didn't see any reason not to scan every minute, but in fact it was every second. Result - massive log files, Archiva hung. Did not have to reinstall it, though. The cron setup would be a good candidate for improved input forms and/or validation. - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
Proxied repository strategies?
All, We have just stood up an instance of Archiva and attempting to incorporate it's use into our maven build processes. However, there is a lack of documentation for suggested practices on how to use it. My biggest question is surrounding proxy connector usage. I thought it would be a good idea to proxy the central repository into a managed repository, however it seems the repository scanner is running non-stop now. In over 11 hours of uptime, we have nearly a gig of logging information and the system is scanning this particular managed repository nearly non-stop. Is this a bad idea? Can anyone give me some information on repository and database scans? I've read the documentation but I'm looking for a little more info. Thanks in advance. Eric
Re: Proxied repository strategies?
Well, part of my problem seems to stem from the fact the Cron expression is based off the open symphony cron syntax and not unix syntax :) I should have noticed it was the same as continuum. However, now I think I have a backlog of scan jobs that need to be run, at least that's what it seems like is going on. I have 4 managed repos that get scanned every minute. Is there any way to purge these jobs or do I just need to let them run their course? Thanks, Eric On Thu, 2008-01-31 at 10:57 -0500, Eric Miles wrote: All, We have just stood up an instance of Archiva and attempting to incorporate it's use into our maven build processes. However, there is a lack of documentation for suggested practices on how to use it. My biggest question is surrounding proxy connector usage. I thought it would be a good idea to proxy the central repository into a managed repository, however it seems the repository scanner is running non-stop now. In over 11 hours of uptime, we have nearly a gig of logging information and the system is scanning this particular managed repository nearly non-stop. Is this a bad idea? Can anyone give me some information on repository and database scans? I've read the documentation but I'm looking for a little more info. Thanks in advance. Eric
proxied repositories -- plugin question
I have a managed repository that I intend to use as a proxy for several remote repositories. I'm doing a test and can't get the proxy to resolve a plugin dependency to save my life. It will however resolve regular dependencies to same remote repository. I am attempting to proxy the Dev Java Net remote repoistory. Here is my pom: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdarchiva-test/groupId artifactIdarchiva-test/artifactId version0.0.1-SNAPSHOT/version description/description dependencies dependency groupIdorg.j4j/groupId artifactIdj4j/artifactId version1.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.1/version scopecompile/scope /dependency dependency groupIdorg.jtb/groupId artifactIdquickr/artifactId version0.8/version /dependency /dependencies repositories repository idproxied/id url http://myproxyserver/archiva/repository/proxied /url /repository /repositories pluginRepositories pluginRepository idproxied/id url http://myproxyserver/archiva/repository/proxied /url /pluginRepository /pluginRepositories build resources resource filteringtrue/filtering directorysrc/main/resources/directory /resource /resources plugins plugin groupIdorg.jvnet.jaxb2.maven2/groupId artifactIdmaven-jaxb2-plugin/artifactId executions execution goals goalgenerate/goal /goals /execution /executions configuration schemaIncludes schemaInclude**/*.xsd/schemaInclude /schemaIncludes extensiontrue/extension /configuration /plugin /plugins /build /project I have no problems resolving and proxying quickr and j4j dependencies, but I get the following error for the jaxb2 maven plugin: $ mvn clean package [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - archiva-test:archiva-test:jar:0.0.1-SNAPSHOT [INFO]task-segment: [clean, package] [INFO] [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from proxied [INFO] artifact org.jvnet.jaxb2.maven2:maven-jaxb2-plugin: checking for updates from proxied [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Jan 29 09:38:40 EST 2008 [INFO] Final Memory: 1M/254M [INFO] Any suggestions? Thanks in advance. Eric
Re: proxied repositories -- plugin question
The one in the Dev Java Net repo looks like this: metadata groupIdorg.jvnet.jaxb2.maven2/groupId artifactIdmaven-jaxb2-plugin/artifactId version0.1/version versioning latest0.5/latest release0.5/release versions version0.1/version version0.2/version version0.4/version version0.4.M1/version version0.4.M2/version version0.4.M3/version version0.5/version /versions lastUpdated20071215123957/lastUpdated /versioning /metadata The one in archiva looks like this: metadata groupIdorg.jvnet.jaxb2/groupId artifactIdmaven2/artifactId versionmaven-jaxb2-plugin/version versioning lastUpdated20071215123957/lastUpdated /versioning /metadata On Tue, 2008-01-29 at 13:51 -0700, Wendy Smoak wrote: On Jan 29, 2008 1:44 PM, Eric Miles [EMAIL PROTECTED] wrote: Figured out my problem although not sure why it's NOT a problem when I don't use Archiva. This particular plugin (and no others) requires that I specify the version in order for the dependency to be downloaded. This isn't desirable as I'd like to have the upgrades to the plugins when they happen, however this is a workaround. Is this particular plugin deployed incorrectly? Is that why archiva/maven can not find the correct current version information? I'm curious, what does the maven-metadata.xml file look like through Archiva? Does it match what you see in the remote repo? (If it's missing the 'latest' and/or 'release' elements for a plugin, Maven will complain.) FWIW, specifying the plugin version is a best practice to help ensure reproducible builds.
Re: proxied repositories -- plugin question
Figured out my problem although not sure why it's NOT a problem when I don't use Archiva. This particular plugin (and no others) requires that I specify the version in order for the dependency to be downloaded. This isn't desirable as I'd like to have the upgrades to the plugins when they happen, however this is a workaround. Is this particular plugin deployed incorrectly? Is that why archiva/maven can not find the correct current version information? Thanks! Eric On Tue, 2008-01-29 at 10:00 -0500, Eric Miles wrote: I have a managed repository that I intend to use as a proxy for several remote repositories. I'm doing a test and can't get the proxy to resolve a plugin dependency to save my life. It will however resolve regular dependencies to same remote repository. I am attempting to proxy the Dev Java Net remote repoistory. Here is my pom: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdarchiva-test/groupId artifactIdarchiva-test/artifactId version0.0.1-SNAPSHOT/version description/description dependencies dependency groupIdorg.j4j/groupId artifactIdj4j/artifactId version1.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.1/version scopecompile/scope /dependency dependency groupIdorg.jtb/groupId artifactIdquickr/artifactId version0.8/version /dependency /dependencies repositories repository idproxied/id url http://myproxyserver/archiva/repository/proxied /url /repository /repositories pluginRepositories pluginRepository idproxied/id url http://myproxyserver/archiva/repository/proxied /url /pluginRepository /pluginRepositories build resources resource filteringtrue/filtering directorysrc/main/resources/directory /resource /resources plugins plugin groupIdorg.jvnet.jaxb2.maven2/groupId artifactIdmaven-jaxb2-plugin/artifactId executions execution goals goalgenerate/goal /goals /execution /executions configuration schemaIncludes schemaInclude**/*.xsd/schemaInclude /schemaIncludes extensiontrue/extension /configuration /plugin /plugins /build /project I have no problems resolving and proxying quickr and j4j dependencies, but I get the following error for the jaxb2 maven plugin: $ mvn clean package [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - archiva-test:archiva-test:jar:0.0.1-SNAPSHOT [INFO]task-segment: [clean, package] [INFO] [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from proxied [INFO] artifact org.jvnet.jaxb2.maven2:maven-jaxb2-plugin: checking for updates from proxied [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Jan 29 09
Re: Maven 2 and Subversion
I'd recommend automating that via a system like Continuum or Cruise Control. I'm not sure there's any other way to do that directly with the POM or not... On Fri, 2007-09-07 at 10:06 -0400, Mark Eramo wrote: Hello, Can anyone point me to detailed information and maybe some examples on how to integrate maven and subversion. Ideally I would like to be able to have the build fetch the latest code from subversion before I do the build. I have looked at the documentation on the Maven site but I am looking for more information then that on how to actually use the commands. Regards, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spring Framework Acegi Security project
Gerard, Use an exclusion like such: dependency groupIdorg.acegisecurity/groupId artifactIdacegi-security/artifactId version1.0.3/version scopecompile/scope exclusions exclusion groupIdorg.springframework/groupId artifactIdspring-remoting/artifactId /exclusion exclusion groupIdorg.springframework/groupId artifactIdspring-support/artifactId /exclusion exclusion groupIdorg.springframework/groupId artifactIdspring-web/artifactId /exclusion exclusion groupIdorg.springframework/groupId artifactIdspring-webmvc/artifactId /exclusion /exclusions /dependency Eric On Thu, 2007-09-06 at 12:34 -0400, Gerard Lancome wrote: Hi there, I'm testing a new little project that uses the Spring Framework and Acegi Security. This the relevant section from the pom (which is attached, BTW) dependency groupIdorg.springframework/groupId artifactIdspring/artifactId version2.0.6/version /dependency dependency groupIdorg.acegisecurity/groupId artifactIdacegi-security/artifactId version1.0.4/version /dependency dependency groupIdorg.acegisecurity/groupId artifactIdacegi-security-tiger/artifactId version1.0.4/version /dependency When I issue a 'mvn package' I see that spring-2.0.6.jar is included (because I asked it to) and several spring-*-2.0.4 jars, which are needed by Acegi. How can I tell Acegi that I already have the Spring dependency covered (alberit with a newer one)? Best regards, Gerard. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Odd dependency POM validation issue
I have a dependency for my project that is provided by another company.
I have built, installed, and deployed this other dependency in my local
repository as well as our company's internal repository. This
dependency, has something that is causing an issue in it's dependency
section. It has this:
dependency
groupId${repository.database.driver.groupId}/groupId
artifactId${repository.database.driver.artifactId}/artifactId
version${repository.database.driver.version}/version
/dependency
These values are provided to this project when it is built. This works
fine.
However, in my own project, when I reference the other company's
dependency that has it's own dependency identified above, I get the
following error message during the build:
[DEBUG] Retrieving parent-POM: com.jaspersoft.jasperserver:server::2.0.0
for project:
com.jaspersoft.jasperserver:jasperserver-export-tool-package:jar:2.0.0
from the repository.
[WARNING] POM for
'com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile'
is invalid. It will be ignored for artifact resolution. Reason: Failed to
validate POM for project
com.jaspersoft.jasperserver:jasperserver-export-tool-package at Artifact
[com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile]
[DEBUG] Reason: Failed to validate POM for project
com.jaspersoft.jasperserver:jasperserver-export-tool-package at Artifact
[com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile]
[DEBUG]
Validation Errors:
[DEBUG] 'dependencies.dependency.artifactId' with value
'${repository.database.driver.artifactId}' does not match a valid id
pattern.
[DEBUG] 'dependencies.dependency.groupId' with value
'${repository.database.driver.groupId}' does not match a valid id
pattern.
[DEBUG]
Now when I do my build, the property values of
repository.database.driver.artifactId and
repository.database.driver.groupId are available as I checked the
effective POM. Is this a bug with Maven? Or is the other company's POM
doing something it shouldn't be doing?
Thanks in advance for the help.
Eric
Configuring password policies for 1.1-beta1?
I wanted to ensure I covered all my bases before I sent this message, but I have looked through the docs, FAQs, wiki, and about 1500 messages of this mailing list and I didn't see this question asked nor found information pertaining to this... How do I configure the password policies for this version? We have no need for password restrictions (must change password, can't be one from previous 6, 1 number required, etc) and I'd like to remove these from our instance. How do I go about doing this? Thanks in advance! Eric
Re: Continuum 1.1 alpha 1
Any upgrade instructions for 1.0.3 to 1.1 alpha 1? The upgrade path doesn't seem to be the same as the previous upgrades. Thanks! On Mon, 2007-04-23 at 21:17 -0500, Jesse McConnell wrote: Well, its finally happened...continuum has had an alpha release to show off some of the work that has been done over the last year. you can obtain the latest release at the following location. http://people.apache.org/builds/maven/continuum/1.1-alpha-1/org/apache/maven/continuum/continuum-plexus-runtime/1.1-alpha-1/continuum-plexus-runtime-1.1-alpha-1-bin.tar.gz war file is - http://people.apache.org/builds/maven/continuum/1.1-alpha-1/org/apache/maven/continuum/continuum-webapp/1.1-alpha-1/continuum-webapp-1.1-alpha-1.war This is the first of the alpha series of continuum, and the plan is to try and get an few alpha's out before we release. There are more issues then I care to think about resolved in this release as well as a number of fun improvements. I am hoping we get some momentum from this and and power through a number of the remaining issues in the jira. If you come a bug or feature request your more then welcome to open the issue in jira at http://jira.codehaus.org/browse/CONTINUUM. If you do open an issue, please try and include as much information as possible, if we can't replicate, we can't fix. Patches are welcome and your best response will be garnered from hopping on irc and talking to us about it. irc.codehaus.org #continuum One of the things that we need to get spruced up before release is documentation, and if you wish to contribute some, we have a wiki setup for continuum users. http://docs.codehaus.org/display/CONTINUUMUSER thanks much! jesse
1.1 alpha 1 release?
Any idea when 1.1 alpha 1 will be released? I'm certain the Continuum community is excited about a release that contains 342 resolved issues. Thanks!
maven site question, use of menu ref=parent
I am trying to create a site for my project that has modules. The creation of the modules menu in the parent's site page seems to work fine and it includes all my parent's modules' links. However I can not get the link back to the parent's site into my modules' sites. I have no other information for my site other than the site descriptors (no included apt files, etc). Here is my parent descriptor and a module descriptor: parent: ?xml version=1.0 encoding=ISO-8859-1? project name=parentproj bannerRight nameMyCompany/name srchttp://www.mycompany.com/img/logo.gif/src hrefhttp://www.mycompany.com//href /bannerRight body links item name=Maven href=http://maven.apache.org/; / /links menu ref=modules / menu ref=reports / /body /project module: ?xml version=1.0 encoding=ISO-8859-1? project name=module1 bannerRight nameMyCompany/name srchttp://www.mycompany.com/img/logo.gif/src hrefhttp://www.mycompany.com//href /bannerRight body links item name=Maven href=http://maven.apache.org/; / /links menu ref=parent / menu ref=reports / /body /project Am I missing something here? I know my module descriptor is working appropriately; when I make alterations to its site.xml the changes are represented in the site that is generated. Thanks for any help. Eric
Mojo Dev question: Binding to phases?
When you bind to a phase, when does it gets executed? Are all goals belonging to a phase executed in parallel? Or is there an order? For instance, I have 2 mojos and I'd like one executed before testing begins (and after test-compile completes) and after testing ends (before the next phase begins). What is the best way to accomplish this? Thanks! Eric Miles
