You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by bfontaine <be...@gmail.com> on 2008/02/18 17:19:31 UTC
Release a multi modules project using Continuum
Hello ;
I'm currently try to get the continuum's release button to work for my
project.
My project is a multi-module project with this kind of structure :
projectRoot
-pom.xml
-subProjectMain
-- subProjectMain files
-- pom.xml
- subProjectDependency
-- subProjectDependency files
-- pom.xml
... and so on
Every subProject pom inherit of the projectRoot pom, which, himself, inherit
of my compagny superpom.
When I execute the release:prepare goal with maven, everything works just
fine. But when I'm trying to use continuum, I get an error at the second
step of the process (generate-reactor-projects). I copied the stacktrace in
the error.txt file
http://www.nabble.com/file/p15546915/Error.txt Error.txt
Obviously, maven can't find my compagny superpom.
I would like to know if there is a way to configure the release plugin of
Continuum so that my release would work.
--
View this message in context: http://www.nabble.com/Release-a-multi-modules-project-using-Continuum-tp15546915p15546915.html
Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Release a multi modules project using Continuum
Posted by Christian Edward Gruber <cg...@israfil.net>.
If the company superpom is not in a repository that your continuum
server or the user under which that server runs (via settings.xml)
knows about, then it will not find it. One solution is to import the
superpom separately and build it within continuum, because then it
will be in the local repository for the user executing continuum.
Christian.
On 18-Feb-08, at 11:19 , bfontaine wrote:
>
> Hello ;
> I'm currently try to get the continuum's release button to work for my
> project.
> My project is a multi-module project with this kind of structure :
>
> projectRoot
> -pom.xml
> -subProjectMain
> -- subProjectMain files
> -- pom.xml
> - subProjectDependency
> -- subProjectDependency files
> -- pom.xml
> ... and so on
>
> Every subProject pom inherit of the projectRoot pom, which, himself,
> inherit
> of my compagny superpom.
> When I execute the release:prepare goal with maven, everything works
> just
> fine. But when I'm trying to use continuum, I get an error at the
> second
> step of the process (generate-reactor-projects). I copied the
> stacktrace in
> the error.txt file
>
> http://www.nabble.com/file/p15546915/Error.txt Error.txt
>
> Obviously, maven can't find my compagny superpom.
> I would like to know if there is a way to configure the release
> plugin of
> Continuum so that my release would work.
>
>
>
> --
> View this message in context: http://www.nabble.com/Release-a-multi-modules-project-using-Continuum-tp15546915p15546915.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
>
Getting Version Information For Maven 2.0.8
Posted by Johnathan Gifford <jg...@wernervas.com>.
My Continuum installation has been working well with Continum 1.1 and Maven 2.0.7 for quite some time now. However, we've decided to update our installations of Maven to 2.0.8. From the command line this seems to work fine for our project, but from Continuum, a whole other issue.
We use the 'Profiles' section to set environment values for continuous builds in Continuum. I've change the profile for this project from Maven 2.0.7 to 2.0.8 after creating a new 'Installation' for Maven 2.0.8. So now our M2_HOME in the project's 'profile' is set to the location where 2.0.8 is installed.
Kicking of the build manually to test the process I get the below output. It seems to fail trying to get the version information for Maven 2.0.8 before even starting Maven build process for the project's pom.xml file.
Any help or ideas (even the silly ones) greatly appreciated!
Thanks,
Johnathan
------------------------
Build statistics:
State: Failed
Previous State: Ok
Started at: Mon 18 Feb 2008 15:03:46 -0600
Finished at: Mon 18 Feb 2008 15:03:47 -0600
Total time: 0s
Build Trigger: Forced
Build Number: 37
Exit code: 1
Building machine hostname: XXXXXXXXX
Operating system : Windows XP(Service Pack 2)
Java Home version :
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)
Builder version :
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-client to select the "client" VM
-server to select the "server" VM
-hotspot is a synonym for the "client" VM [deprecated]
The default VM is client.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
****************************************************************************
SCM Changes:
****************************************************************************
No files changed
****************************************************************************
Dependencies Changes:
****************************************************************************
No dependencies changed
****************************************************************************
Build Defintion:
****************************************************************************
POM filename: pom.xml
Goals: -PXXXX clean install
Arguments: --batch-mode
Build Fresh: false
Always Build: false
Default Build Definition: true
Schedule: EVERY_15
Profile Name: TMS
Description: XXXX every_15 buildDefinition
****************************************************************************
Test Summary:
****************************************************************************
Tests: 0
Failures: 0
Total time: 0.0
Re: Release a multi modules project using Continuum
Posted by bfontaine <be...@gmail.com>.
Thanks for your quick replies !
I've got a setting.xml file in the maven installation repository of my
continuum server which is used when I'm lauching the release from a command
line, and indeed, it doesn"t seems to be used with continuum. So I gonna try
your tip. I can't try it now but I will be back after I would have tried. In
any case, thnak you very much for your help.
Johnathan Gifford wrote:
>
> I think this is the same error I was running into a while back. Do you
> have a special 'settings.xml' file for your project or Maven installation?
> If so, where are you placing that xml file for Maven to find? If it is
> Maven's 'conf' directory, that doesn't seem to work. You may need to
> create a .m2 directory in your home directory and put the settings.xml
> file there. Once I did that, the whole release mechanism in Continuum
> worked. Not sure why Continuum didn't pickup the settings.xml file from
> Maven's 'conf' directory.
>
> Here's a link to Maven's documentation about the settings.xml file and the
> home directory (for *nix and Windows):
>
> http://maven.apache.org/settings.html
>
> Hope this helps,
>
> Johnathan
>
>>>> On Mon, Feb 18, 2008 at 1:47 PM, in message
>>>> <15...@talk.nabble.com>,
> bfontaine <be...@gmail.com> wrote:
>
>> Hello ;
>> I'm currently try to get the continuum's release button to work for my
>> project.
>> My project is a multi-module project with this kind of structure :
>>
>> projectRoot
>> -pom.xml
>> -subProjectMain
>> -- subProjectMain files
>> -- pom.xml
>> - subProjectDependency
>> -- subProjectDependency files
>> -- pom.xml
>> ... and so on
>>
>> Every subProject pom inherit of the projectRoot pom, which, himself,
>> inherit
>> of my compagny superpom.
>> When I execute the release:prepare goal with maven, everything works just
>> fine. But when I'm trying to use continuum, I get an error at the second
>> step of the process (generate-reactor-projects). I copied the stacktrace
>> in
>> the error.txt file
>>
>> http://www.nabble.com/file/p15546915/Error.txt Error.txt
>>
>> Obviously, maven can't find my compagny superpom.
>> I would like to know if there is a way to configure the release plugin of
>> Continuum so that my release would work.
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/Release-a-multi-modules-project-using-Continuum-tp15546915p15560541.html
Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Release a multi modules project using Continuum
Posted by Johnathan Gifford <jg...@wernervas.com>.
I think this is the same error I was running into a while back. Do you have a special 'settings.xml' file for your project or Maven installation? If so, where are you placing that xml file for Maven to find? If it is Maven's 'conf' directory, that doesn't seem to work. You may need to create a .m2 directory in your home directory and put the settings.xml file there. Once I did that, the whole release mechanism in Continuum worked. Not sure why Continuum didn't pickup the settings.xml file from Maven's 'conf' directory.
Here's a link to Maven's documentation about the settings.xml file and the home directory (for *nix and Windows):
http://maven.apache.org/settings.html
Hope this helps,
Johnathan
>>> On Mon, Feb 18, 2008 at 1:47 PM, in message <15...@talk.nabble.com>,
bfontaine <be...@gmail.com> wrote:
> Hello ;
> I'm currently try to get the continuum's release button to work for my
> project.
> My project is a multi-module project with this kind of structure :
>
> projectRoot
> -pom.xml
> -subProjectMain
> -- subProjectMain files
> -- pom.xml
> - subProjectDependency
> -- subProjectDependency files
> -- pom.xml
> ... and so on
>
> Every subProject pom inherit of the projectRoot pom, which, himself, inherit
> of my compagny superpom.
> When I execute the release:prepare goal with maven, everything works just
> fine. But when I'm trying to use continuum, I get an error at the second
> step of the process (generate-reactor-projects). I copied the stacktrace in
> the error.txt file
>
> http://www.nabble.com/file/p15546915/Error.txt Error.txt
>
> Obviously, maven can't find my compagny superpom.
> I would like to know if there is a way to configure the release plugin of
> Continuum so that my release would work.
>
>