Problem updating from CVS on scheduled builds
I'm new to continuum. Have successfully configured and run Ant builds both scheduled and forced but now getting the following build failure ONLY with a scheduled build which seems to be related to the CVS update as indicated in the continuum.log. This is not encountered on a forced build. Also, the same schedule is assigned to two build definitions within the same project. :pserver:[EMAIL PROTECTED]:/cvsroot -q log -d '2006-06-14T11:05:19-0400' 4278963 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1 4279303 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm - Updated 10 files. 4279313 [Thread-2] INFO org.apache.maven.continuum.buildcontroller.BuildController - The project was not built because all changes are unknown.
Re: Problem updating from CVS on scheduled builds
Can you send more logs? like the list of updated files. Perhaps they are in an unknown state. Emmanuel David Neiman a écrit : I'm new to continuum. Have successfully configured and run Ant builds both scheduled and forced but now getting the following build failure ONLY with a scheduled build which seems to be related to the CVS update as indicated in the continuum.log. This is not encountered on a forced build. Also, the same schedule is assigned to two build definitions within the same project. :pserver:[EMAIL PROTECTED]:/cvsroot -q log -d '2006-06-14T11:05:19-0400' 4278963 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1 4279303 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm - Updated 10 files. 4279313 [Thread-2] INFO org.apache.maven.continuum.buildcontroller.BuildController - The project was not built because all changes are unknown.
[Help]how can i perform a auto build when the scm have some changes.
i want to perform a auto build when the scm have some changes,like curisecontrol 's modificationset. how can i do in continuum?
Re: Problem updating from CVS on scheduled builds
The forced build for a schedule build is a planned feature for 1.1 Emmanuel David Neiman a écrit : I think I've fixed this problem but came up with another. It seems the CVS source tree wasn't clean somehow (see extended log below). So now that I've cleaned them up I get the following on a scheduled build: 9053308 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -q update -d -rFVM_13_2_BRANCH 9053308 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1 9056993 [Thread-2] INFO org.apache.maven.continuum.buildcontroller.BuildController - The project was not built because there are no changes. When I do a forced build on the project the build happens regardless, even if there are no files updated from CVS. Is there a way to configure Continuum to do the build even though there are no changes? There are multiple builds (different EAR files created) that happen on the same schedule. These won't happen since only the first build definition gets the updated files. Thanks. 5333099 [defaultScheduler_Worker-4] INFO org.apache.maven.continuum.build.settings.SchedulesActivator - Executing build job (test_build)... 5333109 [defaultScheduler_Worker-4] INFO org.apache.maven.continuum.Continuum - Enqueuing '5VM' (Build definition id=2). 5333189 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm - Updating project: id: '1', name '5VM' with branch/tag FVM_13_2_BRANCH. 5333269 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -q update -d -rFVM_13_2_BRANCH 5333269 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? src/appconfig 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? src/certs 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? src/etc 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? src/sql 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? src/hibernate/gen 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? src/mil/navy/fvm/client 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? test/tools/webservice test tool/FvmClient/WebRoot/WEB-INF/classes/localhost 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? test/tools/webservice test tool/FvmClient/WebRoot/WEB-INF/classes/mil 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? test/tools/webservice test tool/FvmClient/src/localhost 5334801 [Thread-239] DEBUG org.apache.maven.scm.manager.ScmManager - ? test/tools/webservice test tool/FvmClient/src/mil 5337365 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -q log -d '2006-06-14T13:07:03-0400' 5337365 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1 5337485 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm - Updated 10 files. 5337605 [Thread-2] INFO org.apache.maven.continuum.buildcontroller.BuildController - The project was not built because all changes are unknown. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:25 PM To: continuum-users@maven.apache.org Subject: Re: Problem updating from CVS on scheduled builds Can you send more logs? like the list of updated files. Perhaps they are in an unknown state. Emmanuel David Neiman a écrit : I'm new to continuum. Have successfully configured and run Ant builds both scheduled and forced but now getting the following build failure ONLY with a scheduled build which seems to be related to the CVS update as indicated in the continuum.log. This is not encountered on a forced build. Also, the same schedule is assigned to two build definitions within the same project. :pserver:[EMAIL PROTECTED]:/cvsroot -q log -d '2006-06-14T11:05:19-0400' 4278963 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Working directory: C:\apache\continuum-1.0.3\apps\continuum\working-directory\1 4279303 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm - Updated 10 files. 4279313 [Thread-2] INFO org.apache.maven.continuum.buildcontroller.BuildController - The project was not built because all changes are unknown.
Re: [Help]how can i perform a auto build when the scm have some changes.
continuum works with schedulers. you can define the schedule period in the schedule configuration screen. All build definitions can be attached to a scheduler and they are attached automatically to the default one. You can access to the build definition from the project view. Emmanuel shen kai a écrit : i want to perform a auto build when the scm have some changes,like curisecontrol 's modificationset. how can i do in continuum?
Re: Problem starting Continuum webapp interface
the default http port used by continuum is 8080. Do you have an other server on this port? You can change it in apps/continuum/conf/application.xml Actually, you can't deploy continuum in a servlet container. Normally, it will be possible in 1.1 Emmanuel Punyashloka Biswal a écrit : Hi, I'm trying to set up Continuum release 1.0.3 on a ppc mac. When I try to use plexus.sh to start the program, it starts listening for XMLRPC connections on port 8000, but doesn't bring up the web interface on port 8080 like the documentation says it should. Do I need to change some configuration settings? Also, are there instructions for deploying continuum using my own servlet container? Thanks! Punya
Release schedule
Hey all, First - Continuum is awesome. It has some feature-gaps in 1.0.x that make it not quite what I need, but what it does so far is still worth the effort of the workarounds, especially since they're fairly temporary. 1.1 features look to me like they will make Continuum exactly the ticket for my CI needs. I'm really proud of you guys - especially for making such a comfortable interface with which to configure it. In the open-source world, it's kind of rare that such attention to ease-of-use gets given. Anyway, enough flattery. I mentioned temporary workarounds, and I am trying to figure out how temporary. Obviously you folks can't make commitments on release schedules, but do you have any estimates as to potential release horizons? The thing is I'm planning several roll-outs of environments, and Continuum 1.0.x is not quite enough, but if the timelines are short enough, I will possibly do so anyway, in order not to get people hooked on a less easy-to-maintain-and-configure alternative. I'm basically on pins and needles, so as much info as you can provide, the better. Also, if there is any developer build documentation for special build considerations when checking out of SVN, pointers to such docs would be great. There are bugs I think I might be able to fix, but I've had little initial luck checking out either trunk or 1.0.x and building. Now I haven't had much time to put effort into it, but if there are obvious gotchas that can be avoided with a smidge of readme, it would be awesome. Regards, Christian christian gruber + agile coach and architect Israfil Consulting Services Corporation email [EMAIL PROTECTED] + bus +1 (905) 640-1119 cell: +1 (416) 998-6023 + cell: +1 (410) 900-0796
Re: assembly moduleSet versus dependencySet
like what the names imply, moduleSets represent your pom's modules and dependencySets represent your pom's dependencies Hope that helps. ^_^ Bob Newby wrote: In an assembly, I am unclear how a moduleSet differs from a dependencySet. (I am referring to the documentation at http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html.) Anyone care to educate me? Thanks in advance, Bob -- Robert E. Newby Principal Software Engineer Vestmark, Inc. 100 Quannapowitt Parkway, Suite 205 Wakefield, MA 01880 [EMAIL PROTECTED] | 781.224.3640 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: plexus-utils 1.1 giving me a hard time
mvn -X tells me that the only plexus-utils JAR in my classpath is 1.1. As for putting 1.3-SNAPSHOT in version, I seem to have read somewhere that it doesn't really matter what version of plexus-utils your pom depends on, what you get is the version present in M2_HOME/core. This may have changed recently, though, as I think what I read was from march or something. Anyways, it all works now. Deleted the project, the maven dir and the repository and started fresh. Funny, because I have in the past deleted the project, the maven dir and the repository - just not at the same time. It would seem my computer is based on ILlogical operations. ;-) -- View this message in context: http://www.nabble.com/plexus-utils-1.1-giving-me-a-hard-time-t1778524.html#a4859672 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Default goals with maven 2
A JIRA is was raised on 19/Jul/05 for this. http://jira.codehaus.org/browse/CONTINUUM-243
Re: Best practices for multi-flavour build?
For this we use the profile in the settings.xml. We do this to avoid
creating a pom file with 30+ environments. If everyone uses a local profile
with their own unique settings you get a clean pom file. The only profiles
we do maintain in the pom file is the profile to build for the test,
acceptation and production environments.
I am also working with Maven for about one month. But this felt as the
proper way of doing things and (for what I understand) fits in the Maven
philosophy.
On 6/13/06, Toto Laricot [EMAIL PROTECTED] wrote:
I'm still trying to understand why Maven doesn't support profile
inheritance.
Would that go again the Maven philosophy?
Using settings.xml is fine to describe a developer's local environment,
not
to describe deployment properties.
Let's say I have a project with two subprojects: one for the client and
one
for the server; and 2 environments: Production and Test. In addition to
the
Production and Test environments, each developer has his/her own
development
environment.
I would expect to be able to define the test and production profiles in
the
parent POM; these profile would be inherited by the Test and Production
POMs' (no additional files to check out to build/deploy the app,
configuration is done all in one place); during development, these
profiles
would be merged with the same profiles defined in settings.xml to match
the
developer's environment.
Am I missing something?
Thanks,
Theo.
On 6/13/06, Kieran Brady [EMAIL PROTECTED] wrote:
Hi Theo,
You're correct, that solution does require duplication but in our case
its
only a couple of POMs so is manageable for the time being.
I believe that a profiles.xml may be the solution for multiple POMs but
I
haven't yet had chance to test it out.
Kieran
- Original Message -
From: Toto Laricot [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Tuesday, June 13, 2006 5:51 AM
Subject: Re: Best practices for multi-flavour build?
Hi all,
I have tried Kieran's solution myself; it works fine as long as the
profiles
are defined in the same POM that contains the variables that need to be
injected.
In other words –still using Kieran's example- if you define:
profile
iddev/id
[…]
properties
environment.namedev/environment.name
/properties
[…]
/profile
in a parent POM, and this filter in a child POM:
filters
filtersrc/main/profiles/${delivery.name}/general-
filter.properties
/filter
filtersrc/main/profiles/${delivery.name}/${environment.name}-
filter.properties/filter
filtersrc/main/resources/${operatingsys.name}-filter.properties
/filter
/filters
The properties won't be injected.
So, if you have a hierarchy of POM's, you have to duplicate you profile
definitions into every POM, which is a maintenance nightmare.
I'd be curious to find out how people deal with this issue. Is the ant
plugin the only solution? I sure hope not.
Theo.
On 6/12/06, badaud [EMAIL PROTECTED] wrote:
I will try something like this, thanks.
--
View this message in context:
http://www.nabble.com/Best-practices-for-multi-flavour-build--t1741483.html#a4826563
Sent from the Maven - Users forum 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: integration builds and version numbers
Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiple test executions
Hi, I'm getting multiple executions of all tests when adding the surefire report and the cobertura report plugins to my pom. Is it possible to have all the plugins collect info from only one test run? I'm running 2.0.4. To reproduce: 1.Try mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app 2. Add these lines to the pom: reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.0/version /plugin /plugins /reporting 3. Run this command: mvn clean package site You get that the tests runs three times. One for packaging and one for each reporting plugin used. BR /Peter
Re: plexus-utils 1.1 giving me a hard time
On 6/14/06, henrikwl [EMAIL PROTECTED] wrote: mvn -X tells me that the only plexus-utils JAR in my classpath is 1.1. As for putting 1.3-SNAPSHOT in version, I seem to have read somewhere that it doesn't really matter what version of plexus-utils your pom depends on, what you get is the version present in M2_HOME/core. This may have changed recently, though, as I think what I read was from march or something. Anyways, it all works now. Deleted the project, the maven dir and the repository and started fresh. Funny, because I have in the past deleted the project, the maven dir and the repository - just not at the same time. It would seem my computer is based on ILlogical operations. ;-) I've had a very similar issue some days ago and my solution was to remove from the local repository the plugin that requires the higher version of your jar. I.e. if you have plugin-x-version1 depends on plexus utils 1.1 plugin-x-version2-SNAPSHOT depends on plexus utils 1.3-SNAPSHOT Somehow the plugin-x-version2-SNAPSHOT was taken from my local repos. Removing the whole plugin-x directory solved it. (maven redownloaded the plugin-x-version1) Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Directory structure
Our projects are structured using the SoC principle , but they do not have the src/main/java/com/mycompany...blah blah and src/main/webapp package structure.Where would I start from to tell M2 about the existing project structure?Is it too much elbow grease and pain to get M2 to work with a different project structure? -- Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Directory structure
not really. Look at the configuration of the build element for example, you can customize source and resource directories there. The benefit of using the maven standard directory layout [1] is that things Just Work without the need for extra configuration everywhere. This is especially helpful for newcomers to the maven paradigm, as its one thing less to configure/worry about. Jorg [1] http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html On 6/14/06, Jeff Mutonho [EMAIL PROTECTED] wrote: Our projects are structured using the SoC principle , but they do not have the src/main/java/com/mycompany...blah blah and src/main/webapp package structure.Where would I start from to tell M2 about the existing project structure?Is it too much elbow grease and pain to get M2 to work with a different project structure? -- Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to make sure Foo.properties file copied to the same directory as Foo.class
Hi, My app contains a Foo.java file and a Foo.properties file in the same directory. I need to make sure the Foo.properties are compiled (copied) into the same directory as Foo.class, i.e., target/classes. How to do that? Thanks! -- Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified Manager of IT Dept, CPTTM Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag RedHat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Automatically adding NOTICE.txt and LICENSE.txt to distributions
Hi,I'm using maven 1.0.2 to build distributions of Apache JDO and I'm trying to automatically add NOTICE.txt to the source artifact and the various project jar artifacts. It appears that maven is automatically adding LICENSE.txt to these artifacts but I'm not quite sure how (and I'm not sure it's being added in the right place or places).Is there a quick reference to how I should do this? Currently, I have 20 copies of LICENSE.txt which seems a bit bizarre. I would prefer not to have 20 copies of NOTICE.txt as well.I looked at the distribution properties and there's a way to include files (maven.dist.src.include yes Comma delimited list of additional files which should be included in the source distribution)in the source distribution but it wasn't clear how to include files in the binary distribution. And where the files get included.Thanks for any help,Craig Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Parent POM across projects
Guys Gals, I think I'm missing something fairly fundamental here. I have a setup where there's a parent project, atlassian-base with some common settings on it. This project has many sub-projects which declares atlassian-base as the parent. e.g. !-- Parent Project Information -- parent groupIdcom.atlassian.base/groupId artifactIdatlassian-base/artifactId version1.1-SNAPSHOT/version /parent My problem is that whenever I rev atlassian-base, I now need to go to *all* the child projects and update the parent version manually. Ideally, I'd like to be able to declare versionlatest/version or something equivalent so it just fetches the latest jar from the local repo. Is something like this possible? Am I totally off the mark here? Cheers, Mark C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: how to make sure Foo.properties file copied to the same directory as Foo.class
Hi, Why are you placing them in the same directory ? You should follow standard directory structure Src/main/java/ com/... For your java files and Src/main/resources/ com/... For your properties files -Original Message- From: Kent Tong [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 02:31 To: users@maven.apache.org Subject: how to make sure Foo.properties file copied to the same directory as Foo.class Hi, My app contains a Foo.java file and a Foo.properties file in the same directory. I need to make sure the Foo.properties are compiled (copied) into the same directory as Foo.class, i.e., target/classes. How to do that? Thanks! -- Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified Manager of IT Dept, CPTTM Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag RedHat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Parent POM across projects
Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:26 AM: Guys Gals, I think I'm missing something fairly fundamental here. I have a setup where there's a parent project, atlassian-base with some common settings on it. This project has many sub-projects which declares atlassian-base as the parent. e.g. !-- Parent Project Information -- parent groupIdcom.atlassian.base/groupId artifactIdatlassian-base/artifactId version1.1-SNAPSHOT/version /parent My problem is that whenever I rev atlassian-base, I now need to go to *all* the child projects and update the parent version manually. Ideally, I'd like to be able to declare versionlatest/version or something equivalent so it just fetches the latest jar from the local repo. Is something like this possible? Am I totally off the mark here? So what is the difference between: versionSNAPSHOT/version and versionlatest/version ? You cannot release a final artifact, if your parent might change at any time. The effective-pom will be different then. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
compile time xerces version problem
Hello, I currently have this problem. My projects uses (specifies in its dependencies) xerces version 2.8. However, as I found out maven uses xerces 2.4 from its endorsed directory to compile. As a result, certain newer methods in xerces native API cannot be found. I do not see how to override xerces from maven's endorses directory (copying file there is not an option). Is there a solution for this. Thank you. Sergey. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Directory structure
You can specify in your pom what the directory structure looks like. Inside build, specify sourceDirectory, testSourceDirectory, etc.. build sourceDirectorysrc/sourceDirectory scriptSourceDirectory/ testSourceDirectorytest/testSourceDirectory outputDirectorytarget/classes/outputDirectory testOutputDirectorytarget/testclasses/testOutputDirectory /build Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Jeff Mutonho [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:04 AM To: Maven Users List Subject: Directory structure Our projects are structured using the SoC principle , but they do not have the src/main/java/com/mycompany...blah blah and src/main/webapp package structure.Where would I start from to tell M2 about the existing project structure?Is it too much elbow grease and pain to get M2 to work with a different project structure? -- Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM across projects
Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version Basically I've been naming the atlassian-base snapshots as: 1.1-SNAPSHOT 1.2-SNAPSHOT etc. and so whenever I rev atlassian-base, I need to change all the child projects as well. So when I release 1.3 and the latest snapshots are now 1.3-SNAPSHOT, so I need to update all child project pointers from 1.2-SNAPSHOT to 1.3-SNAPSHOT, which is a slight PITA. Specifying the parent version as: versionSNAPSHOT/version doesn't seem to pickup 1.3-SNAPSHOT (I'm assuming I need to call my atlassian-base version, SNAPSHOT). The key difference between latest and SNAPSHOT is that latest (which doesn't work) would find out what the latest version deployed on the repo is, and just try to use that? That way, I don't need to update my (unreleased) child projects every time I release atlassian-base. I'm thinking this *should* be a fairly common use-case, and wondered what other solutions there are. Cheers, Mark C Jörg Schaible wrote: Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:26 AM: Guys Gals, I think I'm missing something fairly fundamental here. I have a setup where there's a parent project, atlassian-base with some common settings on it. This project has many sub-projects which declares atlassian-base as the parent. e.g. !-- Parent Project Information -- parent groupIdcom.atlassian.base/groupId artifactIdatlassian-base/artifactId version1.1-SNAPSHOT/version /parent My problem is that whenever I rev atlassian-base, I now need to go to *all* the child projects and update the parent version manually. Ideally, I'd like to be able to declare versionlatest/version or something equivalent so it just fetches the latest jar from the local repo. Is something like this possible? Am I totally off the mark here? So what is the difference between: versionSNAPSHOT/version and versionlatest/version ? You cannot release a final artifact, if your parent might change at any time. The effective-pom will be different then. - Jörg - 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: Parent POM across projects
I think people here use the release plugin and it takes care of those tedious jobs for you. I haven't used it though. Mark Chaimungkalanont wrote: Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version Basically I've been naming the atlassian-base snapshots as: 1.1-SNAPSHOT 1.2-SNAPSHOT etc. and so whenever I rev atlassian-base, I need to change all the child projects as well. So when I release 1.3 and the latest snapshots are now 1.3-SNAPSHOT, so I need to update all child project pointers from 1.2-SNAPSHOT to 1.3-SNAPSHOT, which is a slight PITA. Specifying the parent version as: versionSNAPSHOT/version doesn't seem to pickup 1.3-SNAPSHOT (I'm assuming I need to call my atlassian-base version, SNAPSHOT). The key difference between latest and SNAPSHOT is that latest (which doesn't work) would find out what the latest version deployed on the repo is, and just try to use that? That way, I don't need to update my (unreleased) child projects every time I release atlassian-base. I'm thinking this *should* be a fairly common use-case, and wondered what other solutions there are. Cheers, Mark C Jörg Schaible wrote: Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:26 AM: Guys Gals, I think I'm missing something fairly fundamental here. I have a setup where there's a parent project, atlassian-base with some common settings on it. This project has many sub-projects which declares atlassian-base as the parent. e.g. !-- Parent Project Information -- parent groupIdcom.atlassian.base/groupId artifactIdatlassian-base/artifactId version1.1-SNAPSHOT/version /parent My problem is that whenever I rev atlassian-base, I now need to go to *all* the child projects and update the parent version manually. Ideally, I'd like to be able to declare versionlatest/version or something equivalent so it just fetches the latest jar from the local repo. Is something like this possible? Am I totally off the mark here? So what is the difference between: versionSNAPSHOT/version and versionlatest/version ? You cannot release a final artifact, if your parent might change at any time. The effective-pom will be different then. - Jörg - 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: Directory structure
Furthermore, there might be some plugins which don't use the elements from build and therefore might not work correctly with a different directory structure. Although I haven't encountered any yet, it might be another reason for following the maven directory structure. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Jorg Heymans [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:19 AM To: Maven Users List Subject: Re: Directory structure not really. Look at the configuration of the build element for example, you can customize source and resource directories there. The benefit of using the maven standard directory layout [1] is that things Just Work without the need for extra configuration everywhere. This is especially helpful for newcomers to the maven paradigm, as its one thing less to configure/worry about. Jorg [1] http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html On 6/14/06, Jeff Mutonho [EMAIL PROTECTED] wrote: Our projects are structured using the SoC principle , but they do not have the src/main/java/com/mycompany...blah blah and src/main/webapp package structure.Where would I start from to tell M2 about the existing project structure?Is it too much elbow grease and pain to get M2 to work with a different project structure? -- Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Classloader problem with antrun with run from continuum
it's strange because when we run maven in continuum it's a forked process so it must be the same
result that a run on the command line.
Emmanuel
Gautham Pamu a écrit :
Hi Emmanuel,
Thanks for responding to my question. I ran both using the root user id.
Thanks
Gautham Pamu
On 6/13/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Do you run continuum and mvn on the same machine with the same account.
It's possible that maven launched by continuum doesn't use the same
plugin
version.
Emmanuel
Gautham Pamu a écrit :
Hi Everyone,
I am using antrun plugin to run ant task during generate-resources
phase. I was able to run the task
outside continuum but when I run from continuum. I am getting
classnotfound errors.. Is this bug in maven
or the plugin or continuum.
mvn version 2.0.3
continuum version 1.0.3
plugin version: antrun version 1.1
pom file details
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
!-- idcompile/id --
phasegenerate-resources/phase
configuration
tasks
ant antfile=./src/build1.xml inheritRefs=true
target name=main/
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.apache.ant/groupId
artifactIdant-antlr/artifactId
version1.6.5/version
/dependency
dependency
groupIdorg.apache.ant/groupId
artifactIdantlrall/artifactId
version2.7.4/version
/dependency
This is the output of mvn with -X option. when I run it outside
continuum, I clearly see the dependencies in
the artifacts list... from continuum I get following output.. you can
see from the artifacts list..that the dependencies
are missing..
[DEBUG] Found deletable paths: []
[DEBUG] com.sample:sample:jar:1.0 (selected for null)
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-antrun-plugin:1.1:run' --
[DEBUG] (f) artifacts = [ant:ant:jar:1.6.5:runtime,
ant:ant-launcher:jar:1.6.5:runtime,
org.apache.maven:maven-project:jar:2.0.1:runtime,
org.apache.maven:maven-plugin-api:jar:2.0.1:runtime]
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) tasks =
[DEBUG] -- end configuration --
[INFO] [antrun:run]
[INFO] Executing tasks
[INFO] Executed tasks
[DEBUG] rpm-maven-plugin: resolved to version
1.0-alpha-2-20060116.043106-1 from repository Maven Snapshots
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::1 for
project: null:rpm-maven-plugin:maven-plugin:
1.0-alpha-2-20060116.043106-1
from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::6 for project:
null:mojo-sandbox:pom:1 from the repository.
[DEBUG] rpm-maven-plugin: resolved to version
1.0-alpha-2-20060116.043106-1 from repository Maven Snapshots
[DEBUG] changelog-maven-plugin: resolved to version
2.0-beta-2-20060307.142230-7 from repository Maven Snapshots
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project:
null:changelog-maven-plugin:maven-plugin:2.0-beta-2-20060307.142230-7
from the repository.
[DEBUG] changelog-maven-plugin: resolved to version
2.0-beta-2-20060307.142230-7 from repository Maven Snapshots
[DEBUG] com.ibm.csdp.resources:csdp.resources:jar:1.0 (selected for
null)
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-antrun-plugin:1.1:run' --
[DEBUG] (f) artifacts = [ant:ant:jar:1.6.5:runtime,
ant:ant-launcher:jar:1.6.5:runtime,
org.apache.maven:maven-project:jar:2.0.1:runtime,
org.apache.maven:maven-plugin-api:jar:2.0.1:runtime]
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) tasks =
[DEBUG] -- end configuration --
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
[DEBUG] getProperty(ns=null, name=ant.executor.class, user=false)
[DEBUG] getProperty(ns=null, name=ant.file, user=false)
[INFO] ---
Embedded error: The following error occurred while executing this line:
/opt/continuum/apps/working-directory/2/com.sample/src/build1.xml:4:
taskdef class com.sample.SampleTask cannot be found
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
executing ant tasks
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:454)
at
Re: 1.0.2-1.0.3 upgrade - JDODataStoreException: ...trying to shrink VARCHAR...ContinuumBuildExecutorE
weird. Can you try with a fresh install of continuum? Emmanuel Chris Wall a écrit : It's consistent during our builds. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: June 13, 2006 3:45 AM To: continuum-users@maven.apache.org Subject: Re: 1.0.2-1.0.3 upgrade - JDODataStoreException: ...trying to shrink VARCHAR...ContinuumBuildExecutorE Do you have always this exception or is it only on one build? Chris Wall a écrit : After upgrading from 1.0.2 to 1.0.3 (via http://maven.apache.org/continuum/upgrade.html), we are experiencing the stacktrace below. Is this an outdated schema issue? I saw two related responses in the archives (we don't know why and nothing to do with Maven or Continuum) and a couple open bugs. What is the suggested workaround? Could this be related? Is it correct to overwrite 1.0.3 with 1.0.2?: Replace Continuum 1.0.3's apps/continuum/database with Continuum 1.0.2's apps/continuum/database. yes, it's the normal way. Thanks! -Chris Stacktrace javax.jdo.JDODataStoreException: Update request failed: UPDATE BUILDRESULT SET ERROR=? WHERE ID=? at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:26 7) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2200) at org.jpox.store.StoreManager.update(StoreManager.java:786) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4596) at org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav a:3167) at org.jpox.AbstractPersistenceManager.markDirty(AbstractPersistenceManager .java:3126) at org.jpox.state.StateManagerImpl.postWriteField(StateManagerImpl.java:433 4) at org.jpox.state.StateManagerImpl.makeDirty(StateManagerImpl.java:1050) at org.jpox.state.AttachFieldManager.storeIntField(AttachFieldManager.java: 255) at org.jpox.state.StateManagerImpl.providedIntField(StateManagerImpl.java:2 571) at org.apache.maven.continuum.model.project.Project.jdoProvideField(Project .java) at org.apache.maven.continuum.model.project.Project.jdoProvideFields(Projec t.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2964 ) at org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java :4028) at org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3963) at org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManage r.java:1336) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersi stenceManager.java:1109) at org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceMa nager.java:1201) at org.apache.maven.continuum.store.JdoContinuumStore.updateBuildResult(Jdo ContinuumStore.java:238) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:324) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:595) NestedThrowablesStackTrace: ERROR 22001: A truncation error was encountered trying to shrink VARCHAR 'org.apache.maven.continuum.execution.ContinuumBuildExecutorE' to length 8192. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown Source) at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) at org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown Source) at org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknow n Source) at org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unkn own Source) at org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unkno wn Source) at org.apache.derby.impl.sql.execute.UpdateResultSet.collectAffectedRows(Un known Source) at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unkno wn Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source) at
Re: Building a project using Continuum + execute mvn site
You need to go to the project view and add a new build definition. Emmanuel Tatiana Escovedo a écrit : Hi, I'm trying Continuum 1.0.3 and I can build my project through the web interface. However, I'd like to build and execute the goal mvn site, for example. Do you know how could I do this using Continnum? I know how to execute the goal directly from command line, but I like to execute multiple goals using continuum. I imagine that I have to add something on my POM, expliciting the goals I want to execute. Could anyone help me? Thanks, Tatiana
RE: Parent POM across projects
Edwin Punzalan wrote on Wednesday, June 14, 2006 11:00 AM: I think people here use the release plugin and it takes care of those tedious jobs for you. No, this works only if your parent POM is part of your project. In case of a company wide super POM, this does not apply. I haven't used it though. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Directory structure
On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote: Furthermore, there might be some plugins which don't use the elements from build and therefore might not work correctly with a different directory structure. Although I haven't encountered any yet, it might be another reason for following the maven directory structure. Now that is worrying Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Parent POM across projects
Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:54 AM: Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version Basically I've been naming the atlassian-base snapshots as: 1.1-SNAPSHOT 1.2-SNAPSHOT etc. and so whenever I rev atlassian-base, I need to change all the child projects as well. So when I release 1.3 and the latest snapshots are now 1.3-SNAPSHOT, so I need to update all child project pointers from 1.2-SNAPSHOT to 1.3-SNAPSHOT, which is a slight PITA. Specifying the parent version as: versionSNAPSHOT/version doesn't seem to pickup 1.3-SNAPSHOT (I'm assuming I need to call my atlassian-base version, SNAPSHOT). I did not imply this (apart from the fact that no deployed SNAPSHOT currently works, see MNG-2289). The key difference between latest and SNAPSHOT is that latest (which doesn't work) would find out what the latest version deployed on the repo is, and just try to use that? That way, I don't need to update my (unreleased) child projects every time I release atlassian-base. The point is, that from a logical PoV there's absolutely no difference between latest and SNAPSHOT. How can you ever rebuild a released version, if latest is changing over time? The whole point of tagging in a SCM is about reproducability. Otherwise you may already deliver the SNAPSHOT - no difference regarding QA. I'm thinking this *should* be a fairly common use-case, and wondered what other solutions there are. So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT only, because the version of the master POM is absolutely moot. If we release, we will have to change SNAPSHOT to the next release version (e.g. 42) in all POMs of that are part of the release. You don't have to return to SNAPSHOT for those POMs though ... only if there's a need for newer global versions. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Directory structure
Maybe, but I haven't encountered any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: JeffM [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 11:19 AM To: Maven Users List Subject: Re: Directory structure On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote: Furthermore, there might be some plugins which don't use the elements from build and therefore might not work correctly with a different directory structure. Although I haven't encountered any yet, it might be another reason for following the maven directory structure. Now that is worrying Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
compile time xerces version problem
Hello, I currently have this problem. My projects uses (specifies in its dependencies) xerces version 2.8. However, as I found out maven uses xerces 2.4 from its endorsed directory to compile. As a result, certain newer methods in xerces native API cannot be found. I do not see how to override xerces from maven's endorses directory (copying file there is not an option). Is there a solution for this. Thank you. Sergey. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] How to override a mirror in local settings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Morgan, I have maven-proxy running on an internal server. I have also updated the parent pom.xml to include this: repositories repository idcentral/id nameInternal Mirror of Central Repository/name urlhttp://reposerver:/repository/url /repository /repositories pluginRepositories pluginRepository idcentral/id nameInternal Mirror of Central Repository/name urlhttp://reposerver:/repository/url /pluginRepository /pluginRepositories I'm also using maven-proxy on an internal server, but I don't use any repository settings in my pom.xml; instead I have the following entries in my settings.xml: mirrors mirror idbender/id nameinternal mirror of http://repo1.maven.org/maven2//name urlhttp://myserver:/repository/url mirrorOfcentral/mirrorOf /mirror /mirrors profiles profile activation activeByDefaulttrue/activeByDefault /activation repositories repository idbender/id nameinternal mirror of http://repo1.maven.org/maven2//name urlhttp://myserver:/repository/url releases enabledtrue/enabled /releases snapshots enabledtrue/enabled /snapshots /repository repository idtlc/id nameTLC Snapshot Development Repository/name urlhttp://commons.ucalgary.ca/pub/m2-snapshots/url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled /snapshots /repository repository idapache.snapshots/id nameApache Development Repository/name urlhttp://cvs.apache.org/maven-snapshot-repository/url releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idbender/id nameinternal mirror of http://repo1.maven.org/maven2//name urlhttp://myserver:/repository/url releases enabledtrue/enabled /releases snapshots enabledtrue/enabled /snapshots /pluginRepository pluginRepository idtlc-snapshots/id nameTLC Snapshot Development Repository/name urlhttp://commons.ucalgary.ca/pub/m2-snapshots/url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled /snapshots /pluginRepository pluginRepository idsnapshots-codehaus-org/id nameSnapshots of maven plugins at codehaus.org/name urlhttp://snapshots.maven.codehaus.org/maven2/url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled !--updatePolicyalways/updatePolicy-- /snapshots /pluginRepository /pluginRepositories /profile /profiles Using these settings Maven accesses everything apart from the snapshot repos via my maven-proxy. If you're behind a firewall, don't forget to add a corresponding proxy.../proxy entry into your settings.xml so that Maven can download optional snapshots. HTH Thorsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) iD8DBQFEj9q/QvObkgCcDe0RAljkAKCCcuB7WsBoGYm/XWx7Dje3W0CJtQCfVAvD wjQ1MsEXEZ1K9XCoelLRCjA= =jrDr -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Directory structure
I'm finding it difficult to convince my colleagues why we should refactor our codebase to introduce the M2 recommended directory structure :( On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote: Maybe, but I haven't encountered any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: JeffM [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 11:19 AM To: Maven Users List Subject: Re: Directory structure On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote: Furthermore, there might be some plugins which don't use the elements from build and therefore might not work correctly with a different directory structure. Although I haven't encountered any yet, it might be another reason for following the maven directory structure. Now that is worrying Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Parent POM across projects
Jörg Schaible wrote on Wednesday, June 14, 2006 11:30 AM: Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:54 AM: I'm thinking this *should* be a fairly common use-case, and wondered what other solutions there are. Not that I don't understand your pain: MRELEASE-96 - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
eclipse plugin
Hi All, Has anyone had success using the eclipse ide plugin (0.0.9) to execute mvn compile (or any other goal for that mater) on a parent pom. If i run mvn compile on the parent project, it simply compiles that project (i.e. does nothing as there is no source - it's a POM project) If i run mvn complile from the command line (Windows) it all works as expected Is this a known issue ? Thanks Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Parent POM across projects and versions of dependencies
So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT only, because the version of the master POM is absolutely moot. If we release, we will have to change SNAPSHOT to the next release version (e.g. 42) in all POMs of that are part of the release For me this is the qestion. Let's say we released some internal libraries in own release cycle and now I need to remember what projects uses these libraries and change there versions for them in dependecies section MANUALLY. For example if we used as dependency internal utils component in 50 projects then I need to change the version 50 times!!! Best regards, Juri. -Original Message- From: Jorg Schaible [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:30 PM To: Maven Users List Subject: RE: Parent POM across projects Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:54 AM: Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version Basically I've been naming the atlassian-base snapshots as: 1.1-SNAPSHOT 1.2-SNAPSHOT etc. and so whenever I rev atlassian-base, I need to change all the child projects as well. So when I release 1.3 and the latest snapshots are now 1.3-SNAPSHOT, so I need to update all child project pointers from 1.2-SNAPSHOT to 1.3-SNAPSHOT, which is a slight PITA. Specifying the parent version as: versionSNAPSHOT/version doesn't seem to pickup 1.3-SNAPSHOT (I'm assuming I need to call my atlassian-base version, SNAPSHOT). I did not imply this (apart from the fact that no deployed SNAPSHOT currently works, see MNG-2289). The key difference between latest and SNAPSHOT is that latest (which doesn't work) would find out what the latest version deployed on the repo is, and just try to use that? That way, I don't need to update my (unreleased) child projects every time I release atlassian-base. The point is, that from a logical PoV there's absolutely no difference between latest and SNAPSHOT. How can you ever rebuild a released version, if latest is changing over time? The whole point of tagging in a SCM is about reproducability. Otherwise you may already deliver the SNAPSHOT - no difference regarding QA. I'm thinking this *should* be a fairly common use-case, and wondered what other solutions there are. So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT only, because the version of the master POM is absolutely moot. If we release, we will have to change SNAPSHOT to the next release version (e.g. 42) in all POMs of that are part of the release. You don't have to return to SNAPSHOT for those POMs though ... only if there's a need for newer global versions. - Jörg - 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: Directory structure
So have I. But as I have said, I haven't encountered any problems yet. So as long as that pattern continues, I don't think I need to convince them anyway. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: JeffM [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 11:49 AM To: Maven Users List Subject: Re: Directory structure I'm finding it difficult to convince my colleagues why we should refactor our codebase to introduce the M2 recommended directory structure :( On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote: Maybe, but I haven't encountered any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: JeffM [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 11:19 AM To: Maven Users List Subject: Re: Directory structure On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote: Furthermore, there might be some plugins which don't use the elements from build and therefore might not work correctly with a different directory structure. Although I haven't encountered any yet, it might be another reason for following the maven directory structure. Now that is worrying Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM across projects and versions of dependencies
Well, to minimize it, you can at least use the dependencyManagement section inside a parent pom. Artamonov, Juri wrote: So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT only, because the version of the master POM is absolutely moot. If we release, we will have to change SNAPSHOT to the next release version (e.g. 42) in all POMs of that are part of the release For me this is the qestion. Let's say we released some internal libraries in own release cycle and now I need to remember what projects uses these libraries and change there versions for them in dependecies section MANUALLY. For example if we used as dependency internal utils component in 50 projects then I need to change the version 50 times!!! Best regards, Juri. -Original Message- From: Jorg Schaible [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:30 PM To: Maven Users List Subject: RE: Parent POM across projects Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:54 AM: Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version Basically I've been naming the atlassian-base snapshots as: 1.1-SNAPSHOT 1.2-SNAPSHOT etc. and so whenever I rev atlassian-base, I need to change all the child projects as well. So when I release 1.3 and the latest snapshots are now 1.3-SNAPSHOT, so I need to update all child project pointers from 1.2-SNAPSHOT to 1.3-SNAPSHOT, which is a slight PITA. Specifying the parent version as: versionSNAPSHOT/version doesn't seem to pickup 1.3-SNAPSHOT (I'm assuming I need to call my atlassian-base version, SNAPSHOT). I did not imply this (apart from the fact that no deployed SNAPSHOT currently works, see MNG-2289). The key difference between latest and SNAPSHOT is that latest (which doesn't work) would find out what the latest version deployed on the repo is, and just try to use that? That way, I don't need to update my (unreleased) child projects every time I release atlassian-base. The point is, that from a logical PoV there's absolutely no difference between latest and SNAPSHOT. How can you ever rebuild a released version, if latest is changing over time? The whole point of tagging in a SCM is about reproducability. Otherwise you may already deliver the SNAPSHOT - no difference regarding QA. I'm thinking this *should* be a fairly common use-case, and wondered what other solutions there are. So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT only, because the version of the master POM is absolutely moot. If we release, we will have to change SNAPSHOT to the next release version (e.g. 42) in all POMs of that are part of the release. You don't have to return to SNAPSHOT for those POMs though ... only if there's a need for newer global versions. - Jörg - 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: Errors using changelog plugin
Hi. I encounter the same problem, I got the v2.0.4 Maven version, with changelog plugin v 2.0-beta-1, and it doesn't work. I would like to know where it is possible to download changelog plugin sources so that I can compile them. Thanks -- View this message in context: http://www.nabble.com/Errors-using-changelog-plugin-t1093130.html#a4862302 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Parent POM across projects and versions of dependencies
Hi Juri, Artamonov, Juri wrote on Wednesday, June 14, 2006 12:02 PM: So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT only, because the version of the master POM is absolutely moot. If we release, we will have to change SNAPSHOT to the next release version (e.g. 42) in all POMs of that are part of the release For me this is the qestion. Let's say we released some internal libraries in own release cycle and now I need to remember what projects uses these libraries and change there versions for them in dependecies section MANUALLY. For example if we used as dependency internal utils component in 50 projects then I need to change the version 50 times!!! We only talk here about a snapshot *PARENT*. It is used for dependencies manageemnt though. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse plugin
I don't know the details of the eclipse plugin, but it sounds like a bug in the maven-embedder in the 2.0.x series. I had the same problem in the netbeans support. The 2.1-SNAPSHOT version have correct behaviour. I'm shipping a snapshot of that in betbeans and it works. bt the API of embedder changed, so it's not a simple issue with replacing a jar.. Regards Milos On 6/14/06, Jon [EMAIL PROTECTED] wrote: Hi All, Has anyone had success using the eclipse ide plugin (0.0.9) to execute mvn compile (or any other goal for that mater) on a parent pom. If i run mvn compile on the parent project, it simply compiles that project (i.e. does nothing as there is no source - it's a POM project) If i run mvn complile from the command line (Windows) it all works as expected Is this a known issue ? Thanks Jon - 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: Default goals with maven 2
Hello world, I'm not maven confortable with : I have projects working with continuum / maven proxy / personnal superSharedPom but I touch all this only since April... I'm starting to use qalab in my super pom Perform a copy of the internal repository seems not to do the job : maybe I don't understand your idea fine. It sounds me great to have the goal deploy in continuum since qalab source says /** * Goal that handles the merge of statistics into qalab.xml. * * @author Dave Sag . * @goal merge * @phase deploy */ currently I'm glue with dummy test on changing phase in the pom... /me take a breath and go back deep dive Cordialement -- View this message in context: http://www.nabble.com/Default-goals-with-maven-2-t1687698.html#a4862986 Sent from the Continuum - Users forum at Nabble.com.
build is not finished if start executable
hi! I spent 2 days to the following problem : I start executable in ant script target name= exec executable=cmd dir=. spawn=true arg line=/C start calc.exe/ /exec /target the execution of ant script has been finished but continuum build is not marked finished until I close calculator application I look at continuum's log file and find out that it starts ant script by following shell command: ant -f build.xml continium So I perform this command in shell and everything is ok - ant script has been finished just after calculator is launched Did I miss something or is it a bug?
build is not finished if start executable
hi! I spent 2 days to the following problem : I start executable in ant script target name= exec executable=cmd dir=. spawn=true arg line=/C start calc.exe/ /exec /target the execution of ant script has been finished but continuum build is not marked finished until I close calculator application I look at continuum's log file and find out that it starts ant script by following shell command: ant -f build.xml continium So I perform this command in shell and everything is ok - ant script has been finished just after calculator is launched Did I miss something or is it a bug?
Re: eclipse plugin
Yes, it is. It's a problem with maven embedder 2.0.4. If I am not mistaken, this is already fixed in the SNAPSHOT and should be available in the next release (2.0.5). Please remember m2eclipse plugin should add the new embedder once it's released, otherwise it won't work. Hope it helps. Dário Jon wrote: Hi All, Has anyone had success using the eclipse ide plugin (0.0.9) to execute mvn compile (or any other goal for that mater) on a parent pom. If i run mvn compile on the parent project, it simply compiles that project (i.e. does nothing as there is no source - it's a POM project) If i run mvn complile from the command line (Windows) it all works as expected Is this a known issue ? Thanks Jon - 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]
Eduction: 50 students get the same project assignement
A friend of mine asked me how far Maven 2 could help in education. Take about 50 students, that all have to do the same 10 projects. Most of these projects are small (2 hours to solve, e.g. Fibonacci), but others are big (3 months to solve, e.g. FTP client). The teacher doesn't have the time to look at every single file in the projects and he loses a lot of time even just testing all projects. If part of his work could be automated, for example using testcases to test corner cases, that would be great. Only one big problem: the students don't know Maven 2 and it's not a priority to learn it to them... Subversion could however become a priority. So I was thinking about what he should do: - Create and solve the projects and let maven generate IDE files. - Create a package problem and a package solution. Filter out the solution package when suppling the project to the student. - Create interfaces (and domain objects if needed) in the problem package - Create testcases to test the code automatically. Should he supply the student with the testcases? - Create a zip to to supply to the students OR copy on subversion (filtering out solution)? -- If subversion then the students should not be able to see to original project, only their filtered copy. - Find a way to get maven to mvn test site all projects in a directory structure like this, without having to create pom.xml all over the place: student1/project1/ student1/project2/ ... student2/project1/ ... Would this last thing be possible? Would I need a pom.xml in the projects themselves, or could I create one on the fly based on a template (and change the groupId to com.domain.exercises.student1.project1) if there is none? What do you think of this setup? Are there better idea's? -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to make sure Foo.properties file copied to the same directory as Foo.class
Hi Kent, thats pretty simple in your POM add the following configuration: build resources resource directorysrc/main/java/directory includes include**/*.properties/include /includes /resource /resources /build if as suggested by Andrew you place your properties file in resources folder than your configuration would look like this: build resources resource directorysrc/main/resources/directory includes include**/*.properties/include /includes /resource /resources /build cheers, Javed On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Why are you placing them in the same directory ? You should follow standard directory structure Src/main/java/ com/... For your java files and Src/main/resources/ com/... For your properties files -Original Message- From: Kent Tong [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 02:31 To: users@maven.apache.org Subject: how to make sure Foo.properties file copied to the same directory as Foo.class Hi, My app contains a Foo.java file and a Foo.properties file in the same directory. I need to make sure the Foo.properties are compiled (copied) into the same directory as Foo.class, i.e., target/classes. How to do that? Thanks! -- Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified Manager of IT Dept, CPTTM Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag RedHat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to make sure Foo.properties file copied to the same directory as Foo.class
No normally specifying your properites or xml or other resources directly in the resources folder should have everything copied automatically but i had some cases where some files were not copied this is why i like to specify it in my POMs ;) cheers, Javed On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I didn't have to specify any explicit build includes (I presume that because I followed standard dir structures it automatically got picked up and included) Or is this bad form not to have explicit build directives regardless ? - I am new to this myself. A -Original Message- From: javed mandary [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 13:22 To: Maven Users List Subject: Re: how to make sure Foo.properties file copied to the same directory as Foo.class Hi Kent, thats pretty simple in your POM add the following configuration: build resources resource directorysrc/main/java/directory includes include**/*.properties/include /includes /resource /resources /build if as suggested by Andrew you place your properties file in resources folder than your configuration would look like this: build resources resource directorysrc/main/resources/directory includes include**/*.properties/include /includes /resource /resources /build cheers, Javed On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Why are you placing them in the same directory ? You should follow standard directory structure Src/main/java/ com/... For your java files and Src/main/resources/ com/... For your properties files -Original Message- From: Kent Tong [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 02:31 To: users@maven.apache.org Subject: how to make sure Foo.properties file copied to the same directory as Foo.class Hi, My app contains a Foo.java file and a Foo.properties file in the same directory. I need to make sure the Foo.properties are compiled (copied) into the same directory as Foo.class, i.e., target/classes. How to do that? Thanks! -- Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified Manager of IT Dept, CPTTM Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag RedHat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eduction: 50 students get the same project assignement
On 6/14/06, Geoffrey De Smet [EMAIL PROTECTED] wrote: A friend of mine asked me how far Maven 2 could help in education. Take about 50 students, that all have to do the same 10 projects. Most of these projects are small (2 hours to solve, e.g. Fibonacci), but others are big (3 months to solve, e.g. FTP client). The teacher doesn't have the time to look at every single file in the projects and he loses a lot of time even just testing all projects. If part of his work could be automated, for example using testcases to test corner cases, that would be great. Only one big problem: the students don't know Maven 2 and it's not a priority to learn it to them... Subversion could however become a priority. So I was thinking about what he should do: - Create and solve the projects and let maven generate IDE files. - Create a package problem and a package solution. Filter out the solution package when suppling the project to the student. - Create interfaces (and domain objects if needed) in the problem package - Create testcases to test the code automatically. Should he supply the student with the testcases? I would make it simple. Stay as far as possible from the implementation, i.e. no implementation structure (except maybe in the first assignment or two). Just make it so that the same integration tests can be applied to all projects. So for that, he should define really clearly what the contract of the project is. E.g. read this file, outputs the solution to that file, using the following format. He shouldn't supply the student will all the testcases, but one or 2 simple ones together with a runner infrastructure should be enough to make sure that they get their project building correctly might be good at least for the first assignments and to make sure that students provided test cases can be added to his master test structure. Based on my experience it's very easy to put too much in this runner to influence the implementation. You don't want that. Similarly I think that would be a good way to introduce how to write test first (maybe after some assignments, letting the students get acquainted with the technology and really see the advantages later on). Some may already know the technique. As to how to organize the subversion, zip etc, I don't have a strong opinion. Hope that helped... Jerome - Create a zip to to supply to the students OR copy on subversion (filtering out solution)? -- If subversion then the students should not be able to see to original project, only their filtered copy. - Find a way to get maven to mvn test site all projects in a directory structure like this, without having to create pom.xml all over the place: student1/project1/ student1/project2/ ... student2/project1/ ... Would this last thing be possible? Would I need a pom.xml in the projects themselves, or could I create one on the fly based on a template (and change the groupId to com.domain.exercises.student1.project1) if there is none? What do you think of this setup? Are there better idea's? -- With kind regards, Geoffrey De Smet - 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 make sure Foo.properties file copied to the same directory as Foo.class
Thanks Javed. Thought I might be missing something important as I have got 1 issue that I just can't solve and hence have resigned myself to living with it ! Building an enterprise distributed global app with multi site multi project dependencies. Integrating with Cruise Control, Clearcase UCM. Bit of a headache setting up M2 for that - especially as a newbie. Though the wealth of excellent documentation and exampels is coming to my rescue ;-) A -Original Message- From: javed mandary [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 13:36 To: Maven Users List Subject: Re: how to make sure Foo.properties file copied to the same directory as Foo.class No normally specifying your properites or xml or other resources directly in the resources folder should have everything copied automatically but i had some cases where some files were not copied this is why i like to specify it in my POMs ;) cheers, Javed On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I didn't have to specify any explicit build includes (I presume that because I followed standard dir structures it automatically got picked up and included) Or is this bad form not to have explicit build directives regardless ? - I am new to this myself. A -Original Message- From: javed mandary [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 13:22 To: Maven Users List Subject: Re: how to make sure Foo.properties file copied to the same directory as Foo.class Hi Kent, thats pretty simple in your POM add the following configuration: build resources resource directorysrc/main/java/directory includes include**/*.properties/include /includes /resource /resources /build if as suggested by Andrew you place your properties file in resources folder than your configuration would look like this: build resources resource directorysrc/main/resources/directory includes include**/*.properties/include /includes /resource /resources /build cheers, Javed On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Why are you placing them in the same directory ? You should follow standard directory structure Src/main/java/ com/... For your java files and Src/main/resources/ com/... For your properties files -Original Message- From: Kent Tong [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 02:31 To: users@maven.apache.org Subject: how to make sure Foo.properties file copied to the same directory as Foo.class Hi, My app contains a Foo.java file and a Foo.properties file in the same directory. I need to make sure the Foo.properties are compiled (copied) into the same directory as Foo.class, i.e., target/classes. How to do that? Thanks! -- Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified Manager of IT Dept, CPTTM Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag RedHat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not
Re: How to report public repository problems
Thanks Edwin. After a quick cursory look at the guide, I am intrigued to know if anyone can contribute pom's for ANY project or component. For instance, I start creating a new maven project for a project called bandit ( http://www.bandit-project.org), and it has a reliance on an open source library for XACML. I discover that the XACML libraries are not in the registry, can I proactively generate a pom for those libraries, or should the pom come from the committers on the XACML project? Cheers, -Lyndon- On 6/14/06, Edwin Punzalan [EMAIL PROTECTED] wrote: Please see: http://maven.apache.org/guides/mini/guide-maven-evangelism.html Lyndon Washington wrote: So, provide an example of the missing pom.xml? Okey dokey, once I get a moment I will log an issue. Thx! On 6/13/06, Carlos Sanchez [EMAIL PROTECTED] wrote: But don't bother to complain without providing a solution or will be ignored. On 6/13/06, Wayne Fay [EMAIL PROTECTED] wrote: Issues like these are filed in the Maven JIRA at Codehaus under component MEV (Maven Evangelism). Wayne On 6/13/06, Lyndon Washington [EMAIL PROTECTED] wrote: What is the procedure for reporting problems with missing pom.xmlfiles from the Ibiblio.org public repository? I tried to use the 1.3.03 version of the xml-apis component, http://www.ibiblio.org/maven2/xml-apis/xml-apis/1.3.03/, only to discover that no pom.xml was present in that directory. Cheers, -Lyndon- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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: whats going wrong with my build?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, [INFO] Scanning for projects... [INFO] [INFO] Building Provisioning System Enterprise Application [INFO]task-segment: [install] [INFO] Downloading: http://repo1.maven.org/maven2/provisioning/provisioning-sar/1.0/provisioning-sar-1.0.sar [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR Are you behind a firewall? In that case have a look at: http://maven.apache.org/guides/mini/guide-proxies.html Sometimes ibiblio.org is quite busy, so you should try again if that solves your problem. HTH Thorsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) iD8DBQFEkA4BQvObkgCcDe0RAqh9AJ4z0VpYnQ/dcJYAm9Gr7HHYPQDerACghHh9 R5M/hOreegnE0mUb80iKASg= =Ni6h -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to set the interval?
Hi, I see in the Continuum documentation that there are interval and delay configuration points, but it doesn't specify where to put them. Does anyone have an example? I'd also like to know how to specify it not to automatically run so that later I can programmatically tell it to build when a delivery is made. Thanks, Michael
install:install-file with a URL?
Looking at the source code, it definitely does not appear possible to install a file from a URL using install:install-file. To me, this seems like it would be a useful feature and could be handled uniformly if file: URLs were supported. As it stands right now, if I want to install something into my local repo, I need to download it and save it somewhere on my computer, then I need to remember where I saved it and type that path into a maven command to make another copy in my local repository. It seems like it would be much more straightforward to just give the URL I want to be downloaded and installed. Perhaps there is another way to do this? - richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build is not finished if start executable
Can you send your continuum logs? Emmanuel Maksimenko Alexander a écrit : hi! I spent 2 days to the following problem : I start executable in ant script target name= exec executable=cmd dir=. spawn=true arg line=/C start calc.exe/ /exec /target the execution of ant script has been finished but continuum build is not marked finished until I close calculator application I look at continuum's log file and find out that it starts ant script by following shell command: ant -f build.xml continium So I perform this command in shell and everything is ok - ant script has been finished just after calculator is launched Did I miss something or is it a bug?
Re: eclipse plugin
Thanks Guys - glad it's not just me ;-) Is there any indication of when 0.0.10 will be released ? Thanks Ovidio Mallo [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Hi, actually, the current development version of the m2eclipse plugin has recently been adapted to use the new SNAPSHOT version of the Maven embedder which has many bugs fixed. Hence, the new version of the plugin (0.0.10) will probably resolve your and many other issues of the plugin which were due to the embedder. Hope the new version will be released soon... Best regards, Ovidio Dario Luis Coneglian Oliveros wrote: Yes, it is. It's a problem with maven embedder 2.0.4. If I am not mistaken, this is already fixed in the SNAPSHOT and should be available in the next release (2.0.5). Please remember m2eclipse plugin should add the new embedder once it's released, otherwise it won't work. Hope it helps. Dário Jon wrote: Hi All, Has anyone had success using the eclipse ide plugin (0.0.9) to execute mvn compile (or any other goal for that mater) on a parent pom. If i run mvn compile on the parent project, it simply compiles that project (i.e. does nothing as there is no source - it's a POM project) If i run mvn complile from the command line (Windows) it all works as expected Is this a known issue ? Thanks Jon - 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: How to report public repository problems
. and what do you know, someone had already raised the isse, http://jira.codehaus.org/browse/MEV-395, so I just added the patch. Cheers, -L- On 6/14/06, Edwin Punzalan [EMAIL PROTECTED] wrote: Please see: http://maven.apache.org/guides/mini/guide-maven-evangelism.html Lyndon Washington wrote: So, provide an example of the missing pom.xml? Okey dokey, once I get a moment I will log an issue. Thx! On 6/13/06, Carlos Sanchez [EMAIL PROTECTED] wrote: But don't bother to complain without providing a solution or will be ignored. On 6/13/06, Wayne Fay [EMAIL PROTECTED] wrote: Issues like these are filed in the Maven JIRA at Codehaus under component MEV (Maven Evangelism). Wayne On 6/13/06, Lyndon Washington [EMAIL PROTECTED] wrote: What is the procedure for reporting problems with missing pom.xmlfiles from the Ibiblio.org public repository? I tried to use the 1.3.03 version of the xml-apis component, http://www.ibiblio.org/maven2/xml-apis/xml-apis/1.3.03/, only to discover that no pom.xml was present in that directory. Cheers, -Lyndon- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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]
Maven test-compile dependency problem
Hello, I'm trying to run mvn test-compile in my build and I keep getting dependency errors (cannot find symbol ...). The thing is that those dependencies are defined in pom file, with the scope compile. I'm not sure why mvn install works, and mvn test-compile does not. I would appreciate any help on this subject. Thanks, Bratek -- View this message in context: http://www.nabble.com/Maven-test-compile-dependency-problem-t1786244.html#a4865174 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: whats going wrong with my build?
Thorsten Heit wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, [INFO] Scanning for projects... [INFO] [INFO] Building Provisioning System Enterprise Application [INFO]task-segment: [install] [INFO] Downloading: http://repo1.maven.org/maven2/provisioning/provisioning-sar/1.0/provisioning-sar-1.0.sar [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR Are you behind a firewall? In that case have a look at: http://maven.apache.org/guides/mini/guide-proxies.html Sometimes ibiblio.org is quite busy, so you should try again if that solves your problem. No you don't understand. The files are in my local repository already. They are not on ibiblio. I have no idea why maven insists on looking there. This is a purely local project. cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: integration builds and version numbers
Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - 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: eclipse plugin
Is there any indication of when 0.0.10 will be released ? I'm not sure since the version 0.0.9 has only been released recently. However, I think that the mere fact of having migrated to the new embedder deserves a new release... You may consider posting a request to the m2eclipse user mailing list if you like (see http://m2eclipse.codehaus.org). Bye, Ovidio Thanks Ovidio Mallo [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Hi, actually, the current development version of the m2eclipse plugin has recently been adapted to use the new SNAPSHOT version of the Maven embedder which has many bugs fixed. Hence, the new version of the plugin (0.0.10) will probably resolve your and many other issues of the plugin which were due to the embedder. Hope the new version will be released soon... Best regards, Ovidio Dario Luis Coneglian Oliveros wrote: Yes, it is. It's a problem with maven embedder 2.0.4. If I am not mistaken, this is already fixed in the SNAPSHOT and should be available in the next release (2.0.5). Please remember m2eclipse plugin should add the new embedder once it's released, otherwise it won't work. Hope it helps. Dário Jon wrote: Hi All, Has anyone had success using the eclipse ide plugin (0.0.9) to execute mvn compile (or any other goal for that mater) on a parent pom. If i run mvn compile on the parent project, it simply compiles that project (i.e. does nothing as there is no source - it's a POM project) If i run mvn complile from the command line (Windows) it all works as expected Is this a known issue ? Thanks Jon - 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: whats going wrong with my build?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, No you don't understand. The files are in my local repository already. They are not on ibiblio. I have no idea why maven insists on looking there. This is a purely local project. Erm, yes, haven't read it (OutOfCoffeeException...) ;-) Does your repository contain the corresponding pom for your war file? AFAIK Maven checks the central repository if the pom files do not exist in your repo, therefore the warning(s)... Apart from that, what does mvn -e -X ... show on your console? Thorsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) iD4DBQFEkBaDQvObkgCcDe0RAs0cAKDBhdqi7jrw58a96EBUZngIpPrZyACXdDwF DOJsB0cCAY0nqSOyWcCk8w== =vb1Q -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Shared properties across multiple modules
Any further suggestions about this? This is kind of a pressing issue for me. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 3:57 PM To: Maven Users List Subject: Shared properties across multiple modules Ok - so I'm filtering resources here and there and now it's come to my attention that there are places where there is some duplication. Is there a way to share properties across multiple modules? If so where do you store this? Through tons of testing, I've found this: - properties defined in the parent's pom override everything else when the build is run from the parent poms level - properties defined in the parent's pom are unavailable when run from the actual modules working directory - settings in filter.properties override anything in profiles.xml - settings in profiles.xml are available to be expanded within the pom.xml file (settings in filter.properties are not) Note that some will be building at the parent pom level for things, some will be running from the module level. For example - the automated build will be running from the top level to do the mvn install, then from the module level for one module to do the mvn assembly:assembly. The other argument would be I only want to build ONE module, how can this one module use these shared properties? How do you do this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: integration builds and version numbers
I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - 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: integration builds and version numbers
In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - 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] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: integration builds and version numbers
Its 'release:prepare' and 'release:perform' This is the best guide I know of: http://apollo.ucalgary.ca/tlcprojectswiki/index.php/Public/Project_Versioning_-_Best_Practices - Original Message - From: EJ Ciramella [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Wednesday, June 14, 2006 3:14 PM Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - 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: Eduction: 50 students get the same project assignement
Could work, though it is somewhat complex. I don't know why you'd need a solution though, since you could just provide some high-level test cases. I would worry about these constraining the program design or giving too much away, however. My professor for graduate algorithms automated grading through some scripting. His script would run the student's code a few times with different inputs (from a set of files). It would compare the program output to another set of files containing the expected output, and generate a pass/fail for each case. The professor then only needed to examine the student's code if cases failed. He had it set up rather nicely - the script would output the results of all tests plus include the student's source code, and the professor would give us this printout with our grade and any comments necessary. Also, he'd provide us with a subset of the test cases ahead of time, so we could test our program. Didn't give anything away or suggest any program structure - only the format of the input/output was defined. Usually this was made as simple as possible, and we didn't have to deal with invalid inputs. We also submitted our code as a tarball through a web page. Very convenient for all, though it requires some setup on the professor's part (but hey, he's getting paid). -- Daniel Siegmann FJA-US, Inc. (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: whats going wrong with my build?
I'm in the same boat as you teknokrat - no matter what I do, it the artifact doesn't exist in the internal remote repository, maven goes to look in repo1 for it. In addition to this, there are a few poms it simply skips looking to my internal remote repository (like all the maven plugin poms). I wish someone with more maven 2 knowledge could repair these issues. -Original Message- From: Thorsten Heit [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:01 AM To: Maven Users List Subject: Re: whats going wrong with my build? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, No you don't understand. The files are in my local repository already. They are not on ibiblio. I have no idea why maven insists on looking there. This is a purely local project. Erm, yes, haven't read it (OutOfCoffeeException...) ;-) Does your repository contain the corresponding pom for your war file? AFAIK Maven checks the central repository if the pom files do not exist in your repo, therefore the warning(s)... Apart from that, what does mvn -e -X ... show on your console? Thorsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) iD4DBQFEkBaDQvObkgCcDe0RAs0cAKDBhdqi7jrw58a96EBUZngIpPrZyACXdDwF DOJsB0cCAY0nqSOyWcCk8w== =vb1Q -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]
maven-surefire-report-plugin requires Maven version 2.0.3?
Hi, I'm new to Maven. I'm using 2.04 and tried to use the maven-surefire-report-plugin to produce a report in the Maven site. But I get this error: 'org.apache.maven.plugins:maven-surefire-report-plugin': Plugin requires Maven version 2.0.3 It's pretty obviously stated in the plugin's 2.0 pom.xml, but I figured it's a popular report and others would want to use it with 2.04 so I must be issing something. Thanks for any help, Michael
Re: install:install-file with a URL?
Sounds like a valid usecase to me. In case nobody comes up with a solution here i'ld suggest you file this in jira. On 6/14/06, Richard S. Hall [EMAIL PROTECTED] wrote: Looking at the source code, it definitely does not appear possible to install a file from a URL using install:install-file. To me, this seems like it would be a useful feature and could be handled uniformly if file: URLs were supported. As it stands right now, if I want to install something into my local repo, I need to download it and save it somewhere on my computer, then I need to remember where I saved it and type that path into a maven command to make another copy in my local repository. It seems like it would be much more straightforward to just give the URL I want to be downloaded and installed. Perhaps there is another way to do this? - richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: whats going wrong with my build?
Thorsten Heit wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, No you don't understand. The files are in my local repository already. They are not on ibiblio. I have no idea why maven insists on looking there. This is a purely local project. Erm, yes, haven't read it (OutOfCoffeeException...) ;-) Does your repository contain the corresponding pom for your war file? AFAIK Maven checks the central repository if the pom files do not exist in your repo, therefore the warning(s)... yes, its in there. whats really strange is that the war which has a dependency on the sar build just fine. Apart from that, what does mvn -e -X ... show on your console? + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\user\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\dev\maven-2.0.4\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: provisioning:provisioning::1.0 of project: null:provisioning-ear:ear:null in [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: null:provisioning-ear:ear:null [INFO] [INFO] Building Provisioning System Enterprise Application [INFO]task-segment: [install] [INFO] [DEBUG] maven-ear-plugin: resolved to version 2.2 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-ear-plugin:maven-plugin:2.2 [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 fro [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [DEBUG] maven-resources-plugin: resolved to version 2.1 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0 for project: null:maven-resources-plugin:mav [DEBUG] maven-install-plugin: resolved to version 2.1 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0 for project: null:maven-install-plugin:maven [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0 for project: null:maven-compiler-plugin:mave [DEBUG] maven-surefire-plugin: resolved to version 2.1.2 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0 for project: null:maven-surefire-plugin:mave [DEBUG] provisioning:provisioning-ear:ear:1.0 (selected for null) [DEBUG] Retrieving parent-POM: provisioning:provisioning::1.0 for project: null:provisioning-sar:jar:1.0 from [DEBUG] provisioning:provisioning-sar:sar:1.0:compile (selected for compile) [DEBUG] commons-collections:commons-collections:jar:3.1:compile (selected for compile) [DEBUG] jmock:jmock:jar:1.0.1:compile (selected for compile) [DEBUG] junit:junit:jar:3.8.1:compile (selected for compile) [DEBUG] junit:junit:jar:3.8.1:compile (removed - nearer found: 4.0) [DEBUG] junit:junit:jar:4.0:compile (selected for compile) [DEBUG] Retrieving parent-POM: provisioning:provisioning::1.0 for project: null:provisioning-war:war:1.0 from [DEBUG] provisioning:provisioning-war:war:1.0:compile (selected for compile) [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/com/mfuse/novo/provisioning/provisioning-sar/1.0/provisioning-sar-1.0.sar [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [DEBUG] 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.mfuse.novo.provisioning -DartifactId=provisioning-sar \ -Dversion=1.0 -Dpackaging=sar -Dfile=/path/to/file Path to dependency: 1) provisioning:provisioning-ear:ear:1.0 2) provisioning:provisioning-sar:sar:1.0 provisioning:provisioning-sar:sar:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) provisioning:provisioning-sar:sar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.mfuse.novo.provisioning -DartifactId=provisioning-sar \ -Dversion=1.0 -Dpackaging=sar -Dfile=/path/to/file Path to dependency: 1)
RE: integration builds and version numbers
Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - 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] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - 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-surefire-report-plugin requires Maven version 2.0.3?
You're always better off with the most up to date core version of Maven. Please download and install 2.0.4 from maven.apache.org. -Original Message- From: Michael Waluk [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:23 PM To: users@maven.apache.org Subject: maven-surefire-report-plugin requires Maven version 2.0.3? Hi, I'm new to Maven. I'm using 2.04 and tried to use the maven-surefire-report-plugin to produce a report in the Maven site. But I get this error: 'org.apache.maven.plugins:maven-surefire-report-plugin': Plugin requires Maven version 2.0.3 It's pretty obviously stated in the plugin's 2.0 pom.xml, but I figured it's a popular report and others would want to use it with 2.04 so I must be issing something. Thanks for any help, Michael -- This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: integration builds and version numbers
The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - 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] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/363 - Release Date: 6/13/2006 - 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
Re: whats going wrong with my build?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Does your repository contain the corresponding pom for your war file? AFAIK Maven checks the central repository if the pom files do not exist in your repo, therefore the warning(s)... yes, its in there. whats really strange is that the war which has a dependency on the sar build just fine. I never used Maven to build a war/ear/sar so I can't help you much. I only could imagine that there's a typo in groupId/artifactId somewhere in your POMs... I just found http://jira.codehaus.org/browse/MEAR-15, but that seems to be fixed. I don't know if that fix is contained in the plugin version you're using so perhaps you could try to check out the plugin's source code, build and install it manually into your repository and then use it...? Thorsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) iD8DBQFEkCHXQvObkgCcDe0RAmC9AJ9DMuh/Krc22/UNhk7yeNar+lSrRACgt5d9 8Y8CdphDat66TAgOT6SQJcw= =NweH -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: taglist - issue with several compile source root
Hi Raphael, For your 2nd point, there's an issue about that: http://jira.codehaus.org/browse/MTAGLIST-2 Can you please make a patch and attach it to the issue? I'll have a look at it. For your 1rst point, I'll check that. Thanks, Fabrice. On 6/14/06, leahpar [EMAIL PROTECTED] wrote: hello world 1 _ I've made a small plugin to handle generated sources with the api MavenProject.addCompileSourceRoot(String) it works fine (compile, test, run ...) but it seems that taglist is not able to handle the list of folder that I add this way. = bug in official plugin? 2 _ another not so far issue, It's seems that it's not possible to find tag in test source maybe it could be usefull to be able to : in the source test, some tag explains the purpose of this test and a taglist report can be used as an up to date protocol (QA requirement). A step forward can be: check that each test as a protocol and each method 'protocoled' is executed by junit. I've clone the official taglist to handle test source ... works cordialement -- View this message in context: http://www.nabble.com/taglist---issue-with-several-compile-source-root-t1785996.html#a4864389 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: integration builds and version numbers
The only place on that page I see passwords mentioned is in regards to repositories: settings servers server idcommons.ucalgary.ca/id usernamewoodj/username privateKey~/.ssh/id_rsa/privateKey passphrase***/passphrase password***/password /server /servers /settings I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - 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] -- No virus found in this incoming message. Checked by AVG Free Edition.
Re: How to set the interval?
the scheduler is set in the schedule configuration page and all build definitions use one of schedules. You can choose the schedule to use in the project view by editing the build definition Emmanuel Michael Waluk a écrit : Hi, I see in the Continuum documentation that there are interval and delay configuration points, but it doesn't specify where to put them. Does anyone have an example? I'd also like to know how to specify it not to automatically run so that later I can programmatically tell it to build when a delivery is made. Thanks, Michael
RE: integration builds and version numbers
Also - where should this plugin be configured? Once in each child module or one time in the parent pom? We plan on branching just the modules needed for a particular change and then just releasing those into the wild. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:54 AM To: Maven Users List Subject: RE: integration builds and version numbers The only place on that page I see passwords mentioned is in regards to repositories: settings servers server idcommons.ucalgary.ca/id usernamewoodj/username privateKey~/.ssh/id_rsa/privateKey passphrase***/passphrase password***/password /server /servers /settings I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to install artifact created with assembly artifact into Continuum's local repository
The primary artifact from each of my pom's are copied into Continuum's repository, but not the additional artifacts that are created using the assembly plugin. Is there a way to make this happen?
RE: integration builds and version numbers
The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:54 AM To: Maven Users List Subject: RE: integration builds and version numbers I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
Re: Best practices for multi-flavour build?
Hi Ivo,
So, if you have 3 sub-projects (3 POM's under the root POM), you
define the test/acceptance/production profiles in each one of them?
I.e. the DB information (jdbc url, username, etc.) - for instance-
has to be repeated 3 times?
Theo.
On 6/14/06, Ivo Limmen [EMAIL PROTECTED] wrote:
For this we use the profile in the settings.xml. We do this to avoid
creating a pom file with 30+ environments. If everyone uses a local profile
with their own unique settings you get a clean pom file. The only profiles
we do maintain in the pom file is the profile to build for the test,
acceptation and production environments.
I am also working with Maven for about one month. But this felt as the
proper way of doing things and (for what I understand) fits in the Maven
philosophy.
On 6/13/06, Toto Laricot [EMAIL PROTECTED] wrote:
I'm still trying to understand why Maven doesn't support profile
inheritance.
Would that go again the Maven philosophy?
Using settings.xml is fine to describe a developer's local environment,
not
to describe deployment properties.
Let's say I have a project with two subprojects: one for the client and
one
for the server; and 2 environments: Production and Test. In addition to
the
Production and Test environments, each developer has his/her own
development
environment.
I would expect to be able to define the test and production profiles in
the
parent POM; these profile would be inherited by the Test and Production
POMs' (no additional files to check out to build/deploy the app,
configuration is done all in one place); during development, these
profiles
would be merged with the same profiles defined in settings.xml to match
the
developer's environment.
Am I missing something?
Thanks,
Theo.
On 6/13/06, Kieran Brady [EMAIL PROTECTED] wrote:
Hi Theo,
You're correct, that solution does require duplication but in our case
its
only a couple of POMs so is manageable for the time being.
I believe that a profiles.xml may be the solution for multiple POMs but
I
haven't yet had chance to test it out.
Kieran
- Original Message -
From: Toto Laricot [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Tuesday, June 13, 2006 5:51 AM
Subject: Re: Best practices for multi-flavour build?
Hi all,
I have tried Kieran's solution myself; it works fine as long as the
profiles
are defined in the same POM that contains the variables that need to be
injected.
In other words –still using Kieran's example- if you define:
profile
iddev/id
[…]
properties
environment.namedev/environment.name
/properties
[…]
/profile
in a parent POM, and this filter in a child POM:
filters
filtersrc/main/profiles/${delivery.name}/general-
filter.properties
/filter
filtersrc/main/profiles/${delivery.name}/${environment.name}-
filter.properties/filter
filtersrc/main/resources/${operatingsys.name}-filter.properties
/filter
/filters
The properties won't be injected.
So, if you have a hierarchy of POM's, you have to duplicate you profile
definitions into every POM, which is a maintenance nightmare.
I'd be curious to find out how people deal with this issue. Is the ant
plugin the only solution? I sure hope not.
Theo.
On 6/12/06, badaud [EMAIL PROTECTED] wrote:
I will try something like this, thanks.
--
View this message in context:
http://www.nabble.com/Best-practices-for-multi-flavour-build--t1741483.html#a4826563
Sent from the Maven - Users forum 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]
[M2] release-perform vs. Cygwin with Subversion
In the last release of the maven release plugin, releases broke on my systems. I use Cygwin (under Windows XP) and for some reason the release:perform action creates an invalid combination of paths to pass to Subversion. The error I get is: [INFO] Working directory: d:\personal\JEC [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: svn: '/cygdrive/d/personal/JEC/d:/personal/JEC' is not a working copy This is the Cygwin style path (/cygdrive/d/personal/JEC) concatenated with the Windows style path (d:/personal/JEC) for the same location. This still works correctly under Linux, so I'm guessing it's Cygwin specific. I don't have a Windows environment without Cygwin, so I haven't tested that, but I haven't seen any reports of similar problems there. Chas Douglass - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subversion username and password
Hello all,I solved my problem on connecting to Subversion using SCM plugin with -Dusername and -Dpassword parameters passed to Maven. I'm wonder if there is a way to have at least the password prompted, in a way that I don't have to explicit write my password when calling Maven command line. Best regards,DouglasOn 6/13/06, Douglas José [EMAIL PROTECTED] wrote: Hello, Emmanuel,Yes, I'm using scm plugin. Your solution worked pretty fine. Thank you so much,Douglas On 6/13/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: Which plugin do you want to use? I think it's the scm plugin. You can use -Dusername=your_login -Dpassword=your_passwordor you can add an entry in your settings.xml like this:server idsvn_host:svn_port/id usernameyour_login/username passwordyour_password/password/serverEmmanuelDouglas José a écrit : Hi, I'm not able to login to my SVN repository. I configured the scm tag properly, but Maven returns an 'authorization failed' error message. Where do I put my username and password? There is a way to configure Maven to prompt for credentials when trying to connect to svn repository? Can I configure such credentials in a user-specific file? Thanks, -- Douglas José ICQ (UIN) 8024395 MSN: douglasjose[a]hotmail,com (prefer ICQ) Yahoo!: douglasjose[a]yahoo,com - Use free software. Help us make a free world.-- Douglas JoséICQ (UIN) 8024395MSN: douglasjose[a]hotmail,com (prefer ICQ) Yahoo!: douglasjose[a]yahoo,com- Use free software. Help us make a free world. -- Douglas JoséICQ (UIN) 8024395MSN: douglasjose[a]hotmail,com (prefer ICQ)Yahoo!: douglasjose[a]yahoo,com- Use free software. Help us make a free world.
RE: integration builds and version numbers
Does anyone know if mvn, when using the perforce scm config, will pull the users password from an environment variable? Mike, did you try that before you left this person logged in? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:12 PM To: Maven Users List Subject: RE: integration builds and version numbers The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:54 AM To: Maven Users List Subject: RE: integration builds and version numbers I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus
RE: integration builds and version numbers
Ok, I need more detail on how to utilize the release plugin (there's no
fully documented example anywhere I've looked - including that pdf book)
Here's a snippet of my pom.xml (which results in a Missing required
setting: scm connection or developerConnection must be specified.
Error)
scm
connectionscm:perforce:[EMAIL PROTECTED]:1666://depot/up-svcs-t
est/${project.artifactId}/.../connection
developerConnectionscm:perforce:[EMAIL PROTECTED]:1666://depot/
up-svcs-test/${project.artifactId}/.../developerConnection
/scm
dependencies
dependency
groupIdlty/groupId
artifactIdcrypto/artifactId
version1.0-SNAPSHOT/version
/dependency
/dependencies
build
resources
resource
directorysrc/main/scripts/directory
targetPath../scripts/targetPath
filteringtrue/filtering
/resource
/resources
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptorsrc/main/assembly/dep.xml/descriptor
/configuration
/plugin
plugin
artifactIdmaven-jar-plugin/artifactId
configuration
jarNamelib/${project.artifactId}-${project.version}/jarName
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
tagBase
file:///E:/work/up-svcs-test/rel/R1.5/cryptoServer
/tagBase
/configuration
/plugin
/plugins
/build
/project
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 2:48 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
Does anyone know if mvn, when using the perforce scm config, will pull
the users password from an environment variable?
Mike, did you try that before you left this person logged in?
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 12:12 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
The perforce provider does not handle passwords; it is assumed that you
are already logged in. We have a special build user who is only allowed
to log in from the build server and whose login never expires.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 9:54 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
I'm talking about passwords to perforce
-Original Message-
From: Roald Bankras [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 10:55 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
The website mentioned by Kieran Brady shows how you can store
the scm passwords.
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 4:40 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
Ok - got the pdf, but I'm confused. Does this release plugin
need to be configured at the parent or child pom level? What
if our scm tool of choose (perforce) requires passwords?
-Original Message-
From: Roald Bankras [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 10:26 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
In chapter 7 of the 'better builds with maven' book (downloadable from
www.mergere.com) there is a description on how to use the
release plugin.
The plugin website can be found at
http://maven.apache.org/plugins/maven-release-plugin/
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 4:14 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
I tried both mvn release and mvn release:release - neither exists.
What is the correct goal?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 9:51 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
Where is this documented? I'd like to read more about this.
-Original Message-
From: Roald Bankras [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 3:16 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
Updating the version numbers in the pom files can be done by
calling the release goal.
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, June 12, 2006 11:30 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
Someone must be using CC + M2, no?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, June 12, 2006 8:01 AM
To: Maven Users List
Subject:
RE: integration builds and version numbers
I wrote the Perforce integration for Maven 2.0 so I am the proverbial horse's mouth. It will not. It does not run 'p4 login' at all. You need to be logged in beforehand. You might be able to use a cron job with the P4PASSWD environment variable to automatically login the user every X hours but I've never tried that before. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 1:48 PM To: Maven Users List Subject: RE: integration builds and version numbers Does anyone know if mvn, when using the perforce scm config, will pull the users password from an environment variable? Mike, did you try that before you left this person logged in? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:12 PM To: Maven Users List Subject: RE: integration builds and version numbers The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:54 AM To: Maven Users List Subject: RE: integration builds and version numbers I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C
Re: integration builds and version numbers
Just pass it on the command line. You should check the plugin page. Tons of information like the goal names and their properties : http://maven.apache.org/plugins/maven-release-plugin/howto.html http://maven.apache.org/plugins/maven-release-plugin/plugin-info.html On 6/14/06, EJ Ciramella [EMAIL PROTECTED] wrote: Does anyone know if mvn, when using the perforce scm config, will pull the users password from an environment variable? Mike, did you try that before you left this person logged in? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:12 PM To: Maven Users List Subject: RE: integration builds and version numbers The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:54 AM To: Maven Users List Subject: RE: integration builds and version numbers I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 8:01 AM To: Maven Users List Subject: integration builds and version numbers How are people updating their pom.xml files with version numbers from say cruisecontrol? We have two types of codelines (in perforce) here, project and release lines. Everything starts out life as a project then over time one (or more) projects can be integrated to a release line. I'm curious, we're forcefully editing (with the ant replace task) some templated version.html files to reflect what version was built. Do I need to be doing this to the pom.xml files also? When something is getting built from a project branch, the build number looks like this: X.projectbranchname.buildnumber So: 8.P01.1 In the maven world, all the project branches would look like this: versionX.X-SNAPSHOT/version So in the above case - version8.0-P01-SNAPSHOT/version And when that goes to release version8.0.X/version Where X is a build number. This has a problem though - I'll have to remember the dependency order to build and make sure that module C gets built before B which is built before A (or the replace at least happens in that order). So what are people doing for this? Manually updating before every build? I _really_ don't want to have to go back to that - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this
maven ant tasks snapshot handling
Hi all, I'm using the maven tasks for ant (2.0.4) to download snapshots from a repository. My target looks like this: maven:dependencies pathId=mypath verbose=true maven:remoteRepository url=http://myrepository/snapshots; snapShots enabled=true updatePolicy=always / /maven:remoteRepository dependency groupId=myGroup artifactId=myArtifact version=1.0.0-SNAPSHOT / /maven:dependencies Now my snapshots are downloaded to ~/.m2/repository/myGroup/1.0.0-SNAPSHOT/myArtifact-...jar (like I would expect). But the mypath-path refers to ~/.m2/repository/myGroup/1.0.0-mmdd.hhmmss/myArtifact-...jar I didn't find any mention in the JIRA. Am I doing something wrong - I can't imagine everybody is having this problem ? Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] release-perform vs. Cygwin with Subversion
this pb happen when you use a windows jdk instead a jdk installed in cygwin. When we run svn, we define the working directory with workingDirectory.getAbsolutePath(). This commands returns always with a windows jdk a path like d:\personal\JEC so for cygwin, this path isn't an absolute path but a relative path, it's why it concatenate it to the current working directory. Emmanuel Chas Douglass a écrit : In the last release of the maven release plugin, releases broke on my systems. I use Cygwin (under Windows XP) and for some reason the release:perform action creates an invalid combination of paths to pass to Subversion. The error I get is: [INFO] Working directory: d:\personal\JEC[INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message:The svn command failed. Command output:svn: '/cygdrive/d/personal/JEC/d:/personal/JEC' is not a working copy This is the Cygwin style path (/cygdrive/d/personal/JEC) concatenated with the Windows style path (d:/personal/JEC) for the same location. This still works correctly under Linux, so I'm guessing it's Cygwin specific. I don't have a Windows environment without Cygwin, so I haven't tested that, but I haven't seen any reports of similar problems there. Chas Douglass - 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]
Problems rewriting dependencies
I've writing a plugin which, among other things, needs to rewrite a project's dependencies on the fly. In particular, it needs to change their scope to system and point them to a file, and it needs to do this after the transitive dependencies are resolved. (Yes, I know this is weird. No, there isn't another way. Just trust me on this.) Everything works great, until I encounter the Clover plugin. It prints out some debugging information showing the value of project.getArtifacts(), and for some reason, all of the transitive dependencies have vanished! It's behaving as if the dependency resolution started over from scratch with the system-scoped dependencies (whose transitive dependencies of course cannot be located). Does anyone know why this is happening, and how I can stop it? Essentially, I'm trying to take transitive dependencies and turn them into first-order system dependencies, in such a way that they will stick and be seen as such by later plugins in the lifecycle. --Matthew Beermann __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: integration builds and version numbers
I tried that: E:\work\up-svcs-test\rel\R1.5\cryptoServermvn -Dmaven.test.skip=true release:prepare -Dconnection=scm:perforce:[EMAIL PROTECTED]:1666://d epot/up-svcs-test/cryptoServer/... [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building Crypto Server [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Missing required setting: scm connection or developerConnection must be specified. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Wed Jun 14 16:00:06 EDT 2006 [INFO] Final Memory: 4M/8M [INFO] -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:09 PM To: Maven Users List Subject: Re: integration builds and version numbers Just pass it on the command line. You should check the plugin page. Tons of information like the goal names and their properties : http://maven.apache.org/plugins/maven-release-plugin/howto.html http://maven.apache.org/plugins/maven-release-plugin/plugin-info.html On 6/14/06, EJ Ciramella [EMAIL PROTECTED] wrote: Does anyone know if mvn, when using the perforce scm config, will pull the users password from an environment variable? Mike, did you try that before you left this person logged in? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:12 PM To: Maven Users List Subject: RE: integration builds and version numbers The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:54 AM To: Maven Users List Subject: RE: integration builds and version numbers I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:16 AM To: Maven Users List Subject: RE: integration builds and version numbers Updating the version numbers in the pom files can be done by calling the release goal. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 11:30 PM To: Maven Users List Subject: RE: integration builds and version numbers Someone must be using CC + M2, no? -Original Message- From: EJ Ciramella [mailto:[EMAIL
M2-Cargo Plugin Question
Hi all maven 2.0 users, I am still fairly new to maven 2.0 and I have to questions for anyone that can provide feedback. I wanted to know if or when will local or remote deployer support for weblogic8x be added to the Maven 2 plugin for Cargo in the near future? Second, are there any SNAPSHOTs with this support? I built the configuration settings for the cargo plugin in the super pom with the dependicies and noticed that maven doesn't support the weblogic8.1 features yet. Can anyone please help me with this? Thank all of you in advanced, Matilda - Attention: Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any system and destroy any copies.
RE: integration builds and version numbers
You need something like this in your POM. scm connectionscm:perforce://depot/modules/fabric/trunk/parent/connection developerConnectionscm:perforce://depot/modules/fabric/trunk/parent/d eveloperConnection /scm -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:02 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried that: E:\work\up-svcs-test\rel\R1.5\cryptoServermvn -Dmaven.test.skip=true release:prepare -Dconnection=scm:perforce:[EMAIL PROTECTED]:1666://d epot/up-svcs-test/cryptoServer/... [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] -- -- [INFO] Building Crypto Server [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] -- -- [INFO] [release:prepare] [INFO] -- -- [ERROR] BUILD FAILURE [INFO] -- -- [INFO] Missing required setting: scm connection or developerConnection must be specified. [INFO] -- -- [INFO] For more information, run Maven with the -e switch [INFO] -- -- [INFO] Total time: 2 seconds [INFO] Finished at: Wed Jun 14 16:00:06 EDT 2006 [INFO] Final Memory: 4M/8M [INFO] -- -- -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:09 PM To: Maven Users List Subject: Re: integration builds and version numbers Just pass it on the command line. You should check the plugin page. Tons of information like the goal names and their properties : http://maven.apache.org/plugins/maven-release-plugin/howto.html http://maven.apache.org/plugins/maven-release-plugin/plugin-info.html On 6/14/06, EJ Ciramella [EMAIL PROTECTED] wrote: Does anyone know if mvn, when using the perforce scm config, will pull the users password from an environment variable? Mike, did you try that before you left this person logged in? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:12 PM To: Maven Users List Subject: RE: integration builds and version numbers The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:54 AM To: Maven Users List Subject: RE: integration builds and version numbers I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:14 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried both mvn release and mvn release:release - neither exists. What is the correct goal? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:51 AM To: Maven Users List Subject: RE: integration builds and version numbers Where is this documented? I'd like to read more about this. -Original Message- From: Roald Bankras
RE: integration builds and version numbers
Got it - yeah, I was editing a pom in a different branch (DOH!). I have the following dependency chain C depends on B depends on A. The only real application here is C. In order to release C, I need to release B and A also? And my other question earlier was, where is this scm setup supposed to be, the parent level or child level? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:31 PM To: Maven Users List Subject: RE: integration builds and version numbers You need something like this in your POM. scm connectionscm:perforce://depot/modules/fabric/trunk/parent/connection developerConnectionscm:perforce://depot/modules/fabric/trunk/parent/d eveloperConnection /scm -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:02 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried that: E:\work\up-svcs-test\rel\R1.5\cryptoServermvn -Dmaven.test.skip=true release:prepare -Dconnection=scm:perforce:[EMAIL PROTECTED]:1666://d epot/up-svcs-test/cryptoServer/... [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] -- -- [INFO] Building Crypto Server [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] -- -- [INFO] [release:prepare] [INFO] -- -- [ERROR] BUILD FAILURE [INFO] -- -- [INFO] Missing required setting: scm connection or developerConnection must be specified. [INFO] -- -- [INFO] For more information, run Maven with the -e switch [INFO] -- -- [INFO] Total time: 2 seconds [INFO] Finished at: Wed Jun 14 16:00:06 EDT 2006 [INFO] Final Memory: 4M/8M [INFO] -- -- -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:09 PM To: Maven Users List Subject: Re: integration builds and version numbers Just pass it on the command line. You should check the plugin page. Tons of information like the goal names and their properties : http://maven.apache.org/plugins/maven-release-plugin/howto.html http://maven.apache.org/plugins/maven-release-plugin/plugin-info.html On 6/14/06, EJ Ciramella [EMAIL PROTECTED] wrote: Does anyone know if mvn, when using the perforce scm config, will pull the users password from an environment variable? Mike, did you try that before you left this person logged in? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:12 PM To: Maven Users List Subject: RE: integration builds and version numbers The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:54 AM To: Maven Users List Subject: RE: integration builds and version numbers I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:40 PM To: Maven Users List Subject: RE: integration builds and version numbers Ok - got the pdf, but I'm confused. Does this release plugin need to be configured at the parent or child pom level? What if our scm tool of choose (perforce) requires passwords? -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:26 AM To: Maven Users List Subject: RE: integration builds and version numbers In chapter 7 of the 'better builds with maven' book (downloadable from www.mergere.com) there is a description on how to use the release plugin. The plugin website can be found at http://maven.apache.org/plugins/maven-release-plugin/ Roald Bankras Software Engineer JTeam b.v. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14,
RE: integration builds and version numbers
Yes, you need to release all three. If you have a parent project with A B and C as child modules, you can release the parent and it will recursively release A B and C also at the same time. If you put it in the parent and release everything at once, it should just work. If you want to release the children separately, it will use a hueristic to determine the SCM location based on the parent's SCM config. It appends the artifactId to the parent SCM config. If the child's directory name is not equal to artifactId, you will get a Unable to submit error from Perforce. The solution is to put a scm block in each child also if you have this problem. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:44 PM To: Maven Users List Subject: RE: integration builds and version numbers Got it - yeah, I was editing a pom in a different branch (DOH!). I have the following dependency chain C depends on B depends on A. The only real application here is C. In order to release C, I need to release B and A also? And my other question earlier was, where is this scm setup supposed to be, the parent level or child level? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:31 PM To: Maven Users List Subject: RE: integration builds and version numbers You need something like this in your POM. scm connectionscm:perforce://depot/modules/fabric/trunk/parent/ connection developerConnectionscm:perforce://depot/modules/fabric/trunk /parent/d eveloperConnection /scm -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:02 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried that: E:\work\up-svcs-test\rel\R1.5\cryptoServermvn -Dmaven.test.skip=true release:prepare -Dconnection=scm:perforce:[EMAIL PROTECTED]:1666://d epot/up-svcs-test/cryptoServer/... [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] -- -- [INFO] Building Crypto Server [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] -- -- [INFO] [release:prepare] [INFO] -- -- [ERROR] BUILD FAILURE [INFO] -- -- [INFO] Missing required setting: scm connection or developerConnection must be specified. [INFO] -- -- [INFO] For more information, run Maven with the -e switch [INFO] -- -- [INFO] Total time: 2 seconds [INFO] Finished at: Wed Jun 14 16:00:06 EDT 2006 [INFO] Final Memory: 4M/8M [INFO] -- -- -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:09 PM To: Maven Users List Subject: Re: integration builds and version numbers Just pass it on the command line. You should check the plugin page. Tons of information like the goal names and their properties : http://maven.apache.org/plugins/maven-release-plugin/howto.html http://maven.apache.org/plugins/maven-release-plugin/plugin-info.html On 6/14/06, EJ Ciramella [EMAIL PROTECTED] wrote: Does anyone know if mvn, when using the perforce scm config, will pull the users password from an environment variable? Mike, did you try that before you left this person logged in? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:12 PM To: Maven Users List Subject: RE: integration builds and version numbers The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 9:54 AM To: Maven Users List Subject: RE: integration builds and version numbers I'm talking about passwords to perforce -Original Message- From: Roald Bankras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:55 AM To: Maven Users List Subject: RE: integration builds and version numbers The website mentioned by Kieran Brady shows how you can store the scm passwords. Roald Bankras Software Engineer JTeam b.v. -Original Message- From:
RE: integration builds and version numbers
In this case, we have something like this: //depot/up-svcs-test/rel/R1.0/pom.xml --- parent //depot/up-svcs-test/rel/R1.0/A/pom.xml //depot/up-svcs-test/rel/R1.0/B/pom.xml --- children //depot/up-svcs-test/rel/R1.0/C/pom.xml Without putting artifactIdR1.0/artifactId (and then changing it for every release) in the parent pom, what should these be? I'm still confused about the relationships here, but will running from the top level allow me to release a single child module, or will it attempt them all? I like the thought of having the scm entry in the parent pom, and nothing in the children (and running the release plugin from the top level) but don't want to release modules just because they are there (and have no changes since last release). -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:49 PM To: Maven Users List Subject: RE: integration builds and version numbers Yes, you need to release all three. If you have a parent project with A B and C as child modules, you can release the parent and it will recursively release A B and C also at the same time. If you put it in the parent and release everything at once, it should just work. If you want to release the children separately, it will use a hueristic to determine the SCM location based on the parent's SCM config. It appends the artifactId to the parent SCM config. If the child's directory name is not equal to artifactId, you will get a Unable to submit error from Perforce. The solution is to put a scm block in each child also if you have this problem. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:44 PM To: Maven Users List Subject: RE: integration builds and version numbers Got it - yeah, I was editing a pom in a different branch (DOH!). I have the following dependency chain C depends on B depends on A. The only real application here is C. In order to release C, I need to release B and A also? And my other question earlier was, where is this scm setup supposed to be, the parent level or child level? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 4:31 PM To: Maven Users List Subject: RE: integration builds and version numbers You need something like this in your POM. scm connectionscm:perforce://depot/modules/fabric/trunk/parent/ connection developerConnectionscm:perforce://depot/modules/fabric/trunk /parent/d eveloperConnection /scm -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:02 PM To: Maven Users List Subject: RE: integration builds and version numbers I tried that: E:\work\up-svcs-test\rel\R1.5\cryptoServermvn -Dmaven.test.skip=true release:prepare -Dconnection=scm:perforce:[EMAIL PROTECTED]:1666://d epot/up-svcs-test/cryptoServer/... [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] -- -- [INFO] Building Crypto Server [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] -- -- [INFO] [release:prepare] [INFO] -- -- [ERROR] BUILD FAILURE [INFO] -- -- [INFO] Missing required setting: scm connection or developerConnection must be specified. [INFO] -- -- [INFO] For more information, run Maven with the -e switch [INFO] -- -- [INFO] Total time: 2 seconds [INFO] Finished at: Wed Jun 14 16:00:06 EDT 2006 [INFO] Final Memory: 4M/8M [INFO] -- -- -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 3:09 PM To: Maven Users List Subject: Re: integration builds and version numbers Just pass it on the command line. You should check the plugin page. Tons of information like the goal names and their properties : http://maven.apache.org/plugins/maven-release-plugin/howto.html http://maven.apache.org/plugins/maven-release-plugin/plugin-info.html On 6/14/06, EJ Ciramella [EMAIL PROTECTED] wrote: Does anyone know if mvn, when using the perforce scm config, will pull the users password from an environment variable? Mike, did you try that before you left this person logged in? -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:12 PM To: Maven
