You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Geoffrey (JIRA)" <ji...@codehaus.org> on 2005/03/09 10:05:53 UTC

[jira] Created: (MPCRUISECONTROL-20) Local properties

Local properties
----------------

         Key: MPCRUISECONTROL-20
         URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-20
     Project: maven-cruisecontrol-plugin
        Type: New Feature
    Versions: 1.6    
    Reporter: Geoffrey
    Priority: Minor


Some builds require local properties to work.
This local properties are loaded from PROJECT_ROOT/build.properties

While some local properties such as maven.username (and proxy authentication etc) can be put in the USER_HOME/build.properties of the CC machine, not all can.

For example CC must be able to handle 2 projects which deploy to different weblogic servers and their properties require the local path of their weblogic server.


The plugin currently is able to do cruisecontrol:checkout and could at that time for example also copy the build.properties. If it's a multiproject then all subprojects's build.properties could also be copied (the subprojects in turn can also be multiprojects).
There might a property stating the name of build.properties file too, which must also be accounted for?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Closed: (MPCRUISECONTROL-20) Local properties

Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MPCRUISECONTROL-20?page=all ]
     
Arnaud Heritier closed MPCRUISECONTROL-20:
------------------------------------------


Must be reopened if necessary

> Local properties
> ----------------
>
>          Key: MPCRUISECONTROL-20
>          URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-20
>      Project: maven-cruisecontrol-plugin
>         Type: New Feature
>     Versions: 1.6
>     Reporter: Geoffrey
>     Priority: Minor

>
>
> Some builds require local properties to work.
> This local properties are loaded from PROJECT_ROOT/build.properties
> While some local properties such as maven.username (and proxy authentication etc) can be put in the USER_HOME/build.properties of the CC machine, not all can.
> For example CC must be able to handle 2 projects which deploy to different weblogic servers and their properties require the local path of their weblogic server.
> The plugin currently is able to do cruisecontrol:checkout and could at that time for example also copy the build.properties. If it's a multiproject then all subprojects's build.properties could also be copied (the subprojects in turn can also be multiprojects).
> There might a property stating the name of build.properties file too, which must also be accounted for?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MPCRUISECONTROL-20) Local properties

Posted by "David Eric Pugh (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MPCRUISECONTROL-20?page=comments#action_41865 ] 

David Eric Pugh commented on MPCRUISECONTROL-20:
------------------------------------------------

3 months later I am looking at the comment about 1.5 of SCM being required and I come to the conclusion that I thought I was commenting on another issue!

As far as this example, I don't quite understand the challenge you are having.  If you have a build.properties in the project directory, then it will be pulled.   

If, under CC, you want to perform a build and then deploy to weblogic, isn't that process all custom stuff you are doing in maven.xml?  Can't you supply your own properties as part of project.properties?  You don't actually need build.properties as the name of the file in the project, correct? 

> Local properties
> ----------------
>
>          Key: MPCRUISECONTROL-20
>          URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-20
>      Project: maven-cruisecontrol-plugin
>         Type: New Feature
>     Versions: 1.6
>     Reporter: Geoffrey
>     Priority: Minor

>
>
> Some builds require local properties to work.
> This local properties are loaded from PROJECT_ROOT/build.properties
> While some local properties such as maven.username (and proxy authentication etc) can be put in the USER_HOME/build.properties of the CC machine, not all can.
> For example CC must be able to handle 2 projects which deploy to different weblogic servers and their properties require the local path of their weblogic server.
> The plugin currently is able to do cruisecontrol:checkout and could at that time for example also copy the build.properties. If it's a multiproject then all subprojects's build.properties could also be copied (the subprojects in turn can also be multiprojects).
> There might a property stating the name of build.properties file too, which must also be accounted for?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MPCRUISECONTROL-20) Local properties

Posted by "David Eric Pugh (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MPCRUISECONTROL-20?page=comments#action_31035 ]
     
David Eric Pugh commented on MPCRUISECONTROL-20:
------------------------------------------------

This enhancement is dependent on 1.5 of SCM being released, and until it does, I am reluctant to keep pushing the functionality forward.  Additionally the next version of CC is supposed to have some sort of bootstrap ability for checking out CVS...  However, patches are welcome!

> Local properties
> ----------------
>
>          Key: MPCRUISECONTROL-20
>          URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-20
>      Project: maven-cruisecontrol-plugin
>         Type: New Feature
>     Versions: 1.6
>     Reporter: Geoffrey
>     Priority: Minor

>
>
> Some builds require local properties to work.
> This local properties are loaded from PROJECT_ROOT/build.properties
> While some local properties such as maven.username (and proxy authentication etc) can be put in the USER_HOME/build.properties of the CC machine, not all can.
> For example CC must be able to handle 2 projects which deploy to different weblogic servers and their properties require the local path of their weblogic server.
> The plugin currently is able to do cruisecontrol:checkout and could at that time for example also copy the build.properties. If it's a multiproject then all subprojects's build.properties could also be copied (the subprojects in turn can also be multiprojects).
> There might a property stating the name of build.properties file too, which must also be accounted for?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Resolved: (MPCRUISECONTROL-20) Local properties

Posted by "Geoffrey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MPCRUISECONTROL-20?page=all ]
     
Geoffrey resolved MPCRUISECONTROL-20:
-------------------------------------

    Resolution: Cannot Reproduce

I misused the cruisecontrol plugin at first in such a way I couldn't have any local build.properties file:
My apologies for the mis issue.

Now it's cleanly under
cruisecontrol/checkout/myproject/build.properties

> Local properties
> ----------------
>
>          Key: MPCRUISECONTROL-20
>          URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-20
>      Project: maven-cruisecontrol-plugin
>         Type: New Feature
>     Versions: 1.6
>     Reporter: Geoffrey
>     Priority: Minor

>
>
> Some builds require local properties to work.
> This local properties are loaded from PROJECT_ROOT/build.properties
> While some local properties such as maven.username (and proxy authentication etc) can be put in the USER_HOME/build.properties of the CC machine, not all can.
> For example CC must be able to handle 2 projects which deploy to different weblogic servers and their properties require the local path of their weblogic server.
> The plugin currently is able to do cruisecontrol:checkout and could at that time for example also copy the build.properties. If it's a multiproject then all subprojects's build.properties could also be copied (the subprojects in turn can also be multiprojects).
> There might a property stating the name of build.properties file too, which must also be accounted for?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org