Continuum enhancement requests
I want to toss out some enhancement requests I got last week in a meeting, and see if there is any feedback before I open issues. 1. The 'use cached credentials' checkbox should default to 'on'. When adding a project, we always want that box checked. (I'd like to have a configurable default for this.) 2. The ability to edit the scm userid/password and 'use cached credentials' checkbox at the project group level. See above... when you forget to check the box when adding a project with 15 modules, there's a lot of clicking to do to fix it. 3. Prepare for Release should have group-level fields. Right now if you don't like the defaults you have to change them for every module. It would be nice to enter it once and have that take effect for all the modules you're releasing. 4. The build logs for prepare and perform release should be accessible after the fact. Maybe in the list of build results? 5. Scheduled outages. When you know your Subversion repo is going to be down for maintenance, it would be nice to be able to tell Continuum don't run any scheduled builds from 8-10PM on Friday night. 6. Better handling of errors when svn is down. Currently all the builds go into an error state and will not recover on their own. You have to either force a build, or wait for a change to trigger another build. The actual request was for this kind of error to simply take the project out of the schedule pending human intervention, to avoid the hourly error emails. Any thoughts on these? -- Wendy
Re: Continuum enhancement requests
On 21/05/07, Wendy Smoak [EMAIL PROTECTED] wrote: I want to toss out some enhancement requests I got last week in a meeting, and see if there is any feedback before I open issues. 1. The 'use cached credentials' checkbox should default to 'on'. When adding a project, we always want that box checked. (I'd like to have a configurable default for this.) 2. The ability to edit the scm userid/password and 'use cached credentials' checkbox at the project group level. See above... when you forget to check the box when adding a project with 15 modules, there's a lot of clicking to do to fix it. Agreed 3. Prepare for Release should have group-level fields. Right now if you don't like the defaults you have to change them for every module. It would be nice to enter it once and have that take effect for all the modules you're releasing. Yes, I agree - I think maybe a fill down type javascript on the page might be good. 4. The build logs for prepare and perform release should be accessible after the fact. Maybe in the list of build results? Yes, I agree - in general we need to tie this mechanism into the build queue. 5. Scheduled outages. When you know your Subversion repo is going to be down for maintenance, it would be nice to be able to tell Continuum don't run any scheduled builds from 8-10PM on Friday night. This can already be done with the schedule, but making it easier to use would be good. Also once off blackouts might be useful. 6. Better handling of errors when svn is down. Currently all the builds go into an error state and will not recover on their own. You have to either force a build, or wait for a change to trigger another build. The actual request was for this kind of error to simply take the project out of the schedule pending human intervention, to avoid the hourly error emails. Definitely agreed. - Brett
Re: Continuum 1.1-alpha-1 in action
nice, although it's a pity that people can't see all the security and user management features On 5/20/07, Wendy Smoak [EMAIL PROTECTED] wrote: If you'd like to see Continuum 1.1-alpha-1 in action, click around the instance we're using on the MyFaces zone to build Shale, MyFaces Core, and several JSF component libraries: * http://myfaces.zones.apache.org:8081/continuum/ As a guest, you can see build results and working copies, the other options such as building and releasing are disabled. -- Wendy -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride
Issue with dependency plugin, unpack goal
(Sorry, my earlier mail had a Re: in the subject by mistake, hence 'am
reposting the issue with the correct subject title.)
I have a parent project which has two modules 'my-app' and 'my-dep-app'
(both created by the archetype-create example). The 'my-dep-app' project
wants the 'my-app' dependency to be unpacked into its target\classes
folder. I am trying to merge the classes of multiple model projects
before I can run the jibx xml binding compiler on them.
This way I need only one jibx binding factory for a group of related
models. The error 'Failed to resolve artifact' and the fact that it
works when installed in the local repository suggests that reactor
artifacts are not checked to resolve the dependency. Is this a
multi-module problem?
I would like to point out that looks very similar to a resolved
dependency plugin issue (http://jira.codehaus.org/browse/MDEP-44),
except that I dont use the assembly plugin as shown in the test case.
Any help is appreciated.
Maven : 2.0.6
Maven dependency plugin : 2.0 alpha 4
This is the output I get. PFA the poms(Zip attachments are getting rejected)
*
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] my-app
[INFO] my-dep-app
[INFO] My-apps parent pom
[INFO]
[INFO] Building my-app
[INFO]task-segment: [package]
[INFO]
...
[INFO] [jar:jar]
[INFO] Building jar:
C:\test\mvn\dependency-unpack-test\my-app\target\my-app-1.0-SNAPSHOT.jar
[INFO]
[INFO] Building my-dep-app
[INFO]task-segment: [package]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [dependency:unpack {execution: default}]
[INFO] Configured Artifact: com.mycomp.app:my-app:?:jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: com.mycomp.app
ArtifactId: my-app
Version: 1.0-SNAPSHOT
Reason: 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=com.mycomp.app -DartifactId=my-app \
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
com.mycomp.app:my-app:jar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Fri May 18 15:32:07 GST 2007
[INFO] Final Memory: 7M/13M
[INFO]
*
project
groupIdcom.zafinlabs.project.miRevenue.hdfc.impl/groupId
modelVersion4.0.0/modelVersion
artifactIdmyApps/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
nameMy-apps parent pom/name
modules
modulemy-app/module
modulemy-dep-app/module
/modules
/projectproject 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
groupIdcom.mycomp.app/groupId
artifactIdmy-app/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
namemy-app/name
urlhttp://maven.apache.org/url
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
/dependencies
/project
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
groupIdcom.mycomp.app/groupId
artifactIdmy-dep-app/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
namemy-dep-app/name
urlhttp://maven.apache.org/url
dependencyManagement
dependencies
dependency
groupIdcom.mycomp.app/groupId
artifactIdmy-app/artifactId
version${project.version}/version
/dependency
/dependencies
/dependencyManagement
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
dependency
Re: Optional Runtime Dependencies
On 5/20/07, Martin Jericho [EMAIL PROTECTED] wrote: The new version (2.4) of my project Jericho HTML Parser has compile-time dependencies that are optional at runtime. It is not clear to me from the documentation what scope I should give these dependencies, as none of the scopes seem to describe a dependency that is required for compilation but optional at runtime. Add optionaltrue/optional to the dependency element. http://maven.apache.org/ref/current/maven-model/maven.html#class_dependency What page would you have expected to find this on, so we can add it? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Metamorphosis
Hi Jason, Thanks a lot for your inspiring presentation at JavaOne and for the quick reply to my inquiry :) -Original Message- From: ext Jason van Zyl [mailto:[EMAIL PROTECTED] It will be released under the ASL 2.0 license and will be available the week after next. That's great timing. Exactly beginning of next week we are planning to start our transition from a huge ant build to maven 2 (similar dimension of what you presenten), so the help of some tooling is really appreciated. Also I'm trying to push the incremental approach that you proposed (first manage dependencies with maven in ant, then switch to maven completely), hopefully my voice will get heard. How does Metamorphosis come into play in that szenario? Is it picking up from the step where the dependencies are already managed with maven, but the build is still running with ant? Another thing that you mentioned was that it could reorganize (mavenize :) the directory structure. How well does that play along with subversion as a scm tool. Will the history of the files be kept? Be patient, myself and Andy along with Contegix are working as fast as we can to make it all publicly available. Thanks again for all the work that you're doing :) _ ___ //\ndreas.[|-bbert-[]/arroum(a)nsn.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Siemens Networks Operations Business Software phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- Nokia Siemens Networks GmbH Co. KG * Sitz der Gesellschaft: München / Registered office: Munich * Registergericht: München / Commercial registry: Munich, HRA 88537 * WEEE-Reg.-Nr.: DE 52984304 Persönlich haftende Gesellschafterin / General Partner: Nokia Siemens Networks Management GmbH * Geschäftsleitung / Board of Directors: Joachim Malterer, Lydia Sommer * Sitz der Gesellschaft: München / Registered office: Munich * Registergericht: München / Commercial registry: Munich, HRB 163416 -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia Siemens Networks GmbH Co. KG does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia Siemens Networks GmbH Co. KG is a German Company. Further information about the Company is available from its offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nsn.com/ -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Optional Runtime Dependencies
On 5/20/07, Martin Jericho [EMAIL PROTECTED] wrote: Thanks for your response Wendy, but this still isn't clear to me at all. Are you saying I have to add two dependency elements for each library, once with a scope of compile, and once with a scope of runtime but with the optional flag set? Doesn't the compile scope imply runtime dependency as well? Yes. Just runtime scope should do it for you, since it will also be available for compilation. optional is useful for compile scope dependencies that you don't want to be transitive. In no case do you need two dependency elements for the same dependency. Some combination of scope and optional should work. (And I agree, optional should be discussed on the dependency mechanism page.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How configure to Multiproject Site references
Hello, actually i wonder how to generate an Site for an Multiproject ? The (Master) Project Site will be generated for all my Modules but i do not know how to link to each module's site ? Project: pom.xml | | Module A pom.xml - target/site/index.html Module B pom.xml - target/site/index.html Module C pom.xml - target/site/index.html regards, Jens Hohl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Specify Context Path for WAR project in Maven2
When I use the jboss plugin to deploy my war project to the app server the
context path is set to /{artifactId}-{version}/ which also happens if I use
the tomcat plugin to do the same thing. Is there a way to override and
specify this context path instead of using the default?
--
View this message in context:
http://www.nabble.com/Specify-Context-Path-for-WAR-project-in-Maven2-tf3787384s177.html#a10710709
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven-buildnumber-plugin question
Hi Everyone, I've been messing around with the maven-buildnumber-plugin and got it to work but I noticed a quirk. The plugin correctly gets the svn revision number and correctly names the ear file. However the maven install plugin renames the ear back to what appears to be the value in the version/version tag of the ear pom file. If I stop at the package phase, everything is fine but the install phase reverts the maven-buildnumber-plugin changes. Has anyone else experienced this? Is there a work around? Thanks, David
Re: Specify Context Path for WAR project in Maven2
Try the buildfinalNameMyWebAppName/finalName/build
in the POM.
/U
-- Original message --
From: geirgp [EMAIL PROTECTED]
When I use the jboss plugin to deploy my war project to the app server the
context path is set to /{artifactId}-{version}/ which also happens if I use
the tomcat plugin to do the same thing. Is there a way to override and
specify this context path instead of using the default?
--
View this message in context:
http://www.nabble.com/Specify-Context-Path-for-WAR-project-in-Maven2-tf3787384s1
77.html#a10710709
Sent from the Maven - Users 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]
Re: How to excludes some classes when deploy jar via jar plugin?
OH,. God,It looks like I must get it via some other method.and I am doing this now,but new troubles has become. 2007/5/19, Dennis Lundberg [EMAIL PROTECTED]: sam wrote: HI ,My friends: I used maven-jar-plugin for deploy a jar in the project,but I want to exclude some clasaes file out of the jar,is there somebody knows how to do it?Thanks advance. You are not alone: http://jira.codehaus.org/browse/MJAR-30 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Failed to resolve artifact JAX-RPC 1.1.3
Hi! I'm trying to compile my web service program developed in WSDP 2.0. The WSDP 2.0 comes with JAX-RPC 1.1.3_01 EA, see also http://java.sun.com/webservices/docs/2.0/jaxrpc/ReleaseNotes.html I specified the dependency of JAX-RPC as below, dependency groupIdjavax.xml/groupId artifactIdjaxrpc-api/artifactId version1.1.3/version scopecompile/scope /dependency and I encounter the failed to resolve artifact error! In the Maven remote repository, the javax/xml/jaxrpc-api/1.1.3 directory does not contains any JAR files. May I know how to resolve this problem? * please also point me any articles/guidelines about WSDP Maven. Thank you very much! /newbie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Specify Context Path for WAR project in Maven2
To do it right, create /src/main/webapp/WEB-INF/jboss-web.xml with the
following content:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE jboss-web PUBLIC -//JBoss//DTD Web Application 2.3V2//EN
http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd;
jboss-web
context-root/MyWebAppName/context-root
/jboss-web
- Original Message -
From: [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Cc: geirgp [EMAIL PROTECTED]
Sent: Sunday, May 20, 2007 8:01 PM
Subject: Re: Specify Context Path for WAR project in Maven2
Try the buildfinalNameMyWebAppName/finalName/build
in the POM.
/U
-- Original message --
From: geirgp [EMAIL PROTECTED]
When I use the jboss plugin to deploy my war project to the app server
the
context path is set to /{artifactId}-{version}/ which also happens if I
use
the tomcat plugin to do the same thing. Is there a way to override and
specify this context path instead of using the default?
--
View this message in context:
http://www.nabble.com/Specify-Context-Path-for-WAR-project-in-Maven2-tf3787384s1
77.html#a10710709
Sent from the Maven - Users 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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failed to resolve artifact JAX-RPC 1.1.3
If you open the pom file corresponding to that artifact: http://repo1.maven.org/maven2/javax/xml/jaxrpc-api/1.1.3/jaxrpc-api-1.1.3.pom You'll see: urlhttp://java.sun.com/webservices/jaxrpc/index.jsp/url distributionManagement downloadUrlhttp://java.sun.com/webservices/downloads/webservicespack.html/downloadUrl /distributionManagement Go to that URL, download the file, and mvn install it into your local repo. Or if you can use version 1.1, that JAR and Pom etc is available in the repo. Wayne On 5/20/07, wolverine my [EMAIL PROTECTED] wrote: Hi! I'm trying to compile my web service program developed in WSDP 2.0. The WSDP 2.0 comes with JAX-RPC 1.1.3_01 EA, see also http://java.sun.com/webservices/docs/2.0/jaxrpc/ReleaseNotes.html I specified the dependency of JAX-RPC as below, dependency groupIdjavax.xml/groupId artifactIdjaxrpc-api/artifactId version1.1.3/version scopecompile/scope /dependency and I encounter the failed to resolve artifact error! In the Maven remote repository, the javax/xml/jaxrpc-api/1.1.3 directory does not contains any JAR files. May I know how to resolve this problem? * please also point me any articles/guidelines about WSDP Maven. Thank you very much! /newbie - 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]
