[jira] Created: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

View: New views
9 Messages — Rating Filter:   Alert me  

[jira] Created: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Properties defined in the "Run Maven" dialog do not override properties defined in pom
--------------------------------------------------------------------------------------

                 Key: MEVENIDE-540
                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
             Project: mevenide
          Issue Type: Bug
          Components: mevenide2-netbeans
    Affects Versions: NB_2.3
         Environment: Window XP, JDK 1.6.0_01
            Reporter: Olivier Lafontaine
            Assignee: Milos Kleint
            Priority: Minor


Hi,

I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.

Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.

Thanx

Olivier

--
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 from this list please visit:

    http://xircles.codehaus.org/manage_email


[jira] Commented: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/MEVENIDE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100942 ]

Milos Kleint commented on MEVENIDE-540:
---------------------------------------

can you try the same setup with maven 2.0.4? The maven embedder that we are using in mevenide is very close to the 2.0.4 in terms of codebase. Unfortunately the embedder code us seriously broken in 2.0.x series and cannot be used for embedding, we use maven 2.1 code from last September.

I have some experimental code that allows to run the command line maven externally for building the project but it's not ready for primetime yet.


> Properties defined in the "Run Maven" dialog do not override properties defined in pom
> --------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-540
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.3
>         Environment: Window XP, JDK 1.6.0_01
>            Reporter: Olivier Lafontaine
>            Assignee: Milos Kleint
>            Priority: Minor
>
> Hi,
> I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.
> Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.
> Thanx
> Olivier

--
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 from this list please visit:

    http://xircles.codehaus.org/manage_email


[jira] Commented: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/MEVENIDE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101246 ]

Olivier Lafontaine commented on MEVENIDE-540:
---------------------------------------------

I just tried maven 2.0.4 on the command line and it also works.

> Properties defined in the "Run Maven" dialog do not override properties defined in pom
> --------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-540
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.3
>         Environment: Window XP, JDK 1.6.0_01
>            Reporter: Olivier Lafontaine
>            Assignee: Milos Kleint
>            Priority: Minor
>
> Hi,
> I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.
> Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.
> Thanx
> Olivier

--
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 from this list please visit:

    http://xircles.codehaus.org/manage_email


[jira] Updated: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MEVENIDE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint updated MEVENIDE-540:
----------------------------------

    Fix Version/s: NB_3.0

in NetBeans 6.0 beta1/beta2 you can define a command line instance of maven to be used by projects. That at least workarounds the problem until we upgrade to later version of maven embedder (2.1)

> Properties defined in the "Run Maven" dialog do not override properties defined in pom
> --------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-540
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.3
>         Environment: Window XP, JDK 1.6.0_01
>            Reporter: Olivier Lafontaine
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.0
>
>
> Hi,
> I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.
> Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.
> Thanx
> Olivier

--
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 from this list please visit:

    http://xircles.codehaus.org/manage_email


[jira] Updated: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MEVENIDE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint updated MEVENIDE-540:
----------------------------------

    Fix Version/s:     (was: NB_3.0)
                   NB_3.1

> Properties defined in the "Run Maven" dialog do not override properties defined in pom
> --------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-540
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.3
>         Environment: Window XP, JDK 1.6.0_01
>            Reporter: Olivier Lafontaine
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.1
>
>
> Hi,
> I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.
> Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.
> Thanx
> Olivier

--
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 from this list please visit:

    http://xircles.codehaus.org/manage_email


[jira] Commented: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/MEVENIDE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126022 ]

Milos Kleint commented on MEVENIDE-540:
---------------------------------------

it doesn't work with the latest embedder (from february 2008) either. So that could be an oustanding issue in the way maven is embedded..

> Properties defined in the "Run Maven" dialog do not override properties defined in pom
> --------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-540
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.3
>         Environment: Window XP, JDK 1.6.0_01
>            Reporter: Olivier Lafontaine
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.1
>
>
> Hi,
> I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.
> Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.
> Thanx
> Olivier

--
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 from this list, please visit:

    http://xircles.codehaus.org/manage_email



[jira] Updated: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MEVENIDE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint updated MEVENIDE-540:
----------------------------------

    Fix Version/s:     (was: NB_3.1)
                   NB_3.2

> Properties defined in the "Run Maven" dialog do not override properties defined in pom
> --------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-540
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.3
>         Environment: Window XP, JDK 1.6.0_01
>            Reporter: Olivier Lafontaine
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.2
>
>
> Hi,
> I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.
> Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.
> Thanx
> Olivier

--
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 from this list, please visit:

    http://xircles.codehaus.org/manage_email



[jira] Commented: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/MEVENIDE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156556#action_156556 ]

Jaromir Uhrik commented on MEVENIDE-540:
----------------------------------------

This bug was transferred to the NetBeans Issuezilla bug tracking system as http://www.netbeans.org/issues/show_bug.cgi?id=154504

> Properties defined in the "Run Maven" dialog do not override properties defined in pom
> --------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-540
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.3
>         Environment: Window XP, JDK 1.6.0_01
>            Reporter: Olivier Lafontaine
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.2
>
>
> Hi,
> I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.
> Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.
> Thanx
> Olivier

--
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 from this list, please visit:

    http://xircles.codehaus.org/manage_email



[jira] Closed: (MEVENIDE-540) Properties defined in the "Run Maven" dialog do not override properties defined in pom

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MEVENIDE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint closed MEVENIDE-540.
---------------------------------

    Resolution: Duplicate

closing the issue as duplicate of the newly created one in netbeans.org issuezilla.
Please post your additional comments to the new issue.

> Properties defined in the "Run Maven" dialog do not override properties defined in pom
> --------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-540
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-540
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.3
>         Environment: Window XP, JDK 1.6.0_01
>            Reporter: Olivier Lafontaine
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.2
>
>
> Hi,
> I have multi-module pom where I defined the "build_type" property with default value "DEV" (defined only in the master pom). This property is used to change the final name of builds and also to activate profiles. It is meant to be overridden on the command line to change build type, e.g. mvn clean install -Dbuild_type=PRD.
> Using Maven 2.0.7 from the command line, it works great, but with Mevenide the build final name always contains "DEV". Strangely profiles are activated according to the build_type value specified in the "Run Maven" dialog.
> Thanx
> Olivier

--
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 from this list, please visit:

    http://xircles.codehaus.org/manage_email