[jira] Created: (MEVENIDE-542) <Badly formed Maven project> when adding profile to pom

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

[jira] Created: (MEVENIDE-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message

<Badly formed Maven project> when adding profile to pom
-------------------------------------------------------

                 Key: MEVENIDE-542
                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
             Project: mevenide
          Issue Type: Bug
    Affects Versions: NB_2.4, NB_3.0
         Environment: Windows 2000
            Reporter: Daniel Mutch
            Assignee: Milos Kleint
            Priority: Minor


Adding the following profile to a pom.xml seems to render the project invalid

<profiles>
        <profile>
            <id>default-tools.jar</id>
            <activation>
                <property>
                    <name>java.vendor</name>
                    <value>Sun Microsystems Inc.</value>
                </property>
            </activation>
            <dependencies>
                <dependency>
                    <groupId>com.sun</groupId>
                    <artifactId>tools</artifactId>
                    <version>1.4.2</version>
                    <scope>system</scope>
                    <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
                </dependency>
            </dependencies>
        </profile>
    </profiles>

It appears to be the dependencies. Commenting them out solves the problem.

--
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-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message


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

Milos Kleint updated MEVENIDE-542:
----------------------------------

    Component/s: mevenide2-netbeans

> <Badly formed Maven project> when adding profile to pom
> -------------------------------------------------------
>
>                 Key: MEVENIDE-542
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.4, NB_3.0
>         Environment: Windows 2000
>            Reporter: Daniel Mutch
>            Assignee: Milos Kleint
>            Priority: Minor
>
> Adding the following profile to a pom.xml seems to render the project invalid
> <profiles>
>         <profile>
>             <id>default-tools.jar</id>
>             <activation>
>                 <property>
>                     <name>java.vendor</name>
>                     <value>Sun Microsystems Inc.</value>
>                 </property>
>             </activation>
>             <dependencies>
>                 <dependency>
>                     <groupId>com.sun</groupId>
>                     <artifactId>tools</artifactId>
>                     <version>1.4.2</version>
>                     <scope>system</scope>
>                     <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
>                 </dependency>
>             </dependencies>
>         </profile>
>     </profiles>
> It appears to be the dependencies. Commenting them out solves the problem.

--
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-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message


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

Daniel Mutch commented on MEVENIDE-542:
---------------------------------------

By making ${JAVA_1_4_HOME} a system variable the POM loads fine. If however it is defined in a parent project instead you get invalid project issue.

> <Badly formed Maven project> when adding profile to pom
> -------------------------------------------------------
>
>                 Key: MEVENIDE-542
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.4, NB_3.0
>         Environment: Windows 2000
>            Reporter: Daniel Mutch
>            Assignee: Milos Kleint
>            Priority: Minor
>
> Adding the following profile to a pom.xml seems to render the project invalid
> <profiles>
>         <profile>
>             <id>default-tools.jar</id>
>             <activation>
>                 <property>
>                     <name>java.vendor</name>
>                     <value>Sun Microsystems Inc.</value>
>                 </property>
>             </activation>
>             <dependencies>
>                 <dependency>
>                     <groupId>com.sun</groupId>
>                     <artifactId>tools</artifactId>
>                     <version>1.4.2</version>
>                     <scope>system</scope>
>                     <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
>                 </dependency>
>             </dependencies>
>         </profile>
>     </profiles>
> It appears to be the dependencies. Commenting them out solves the problem.

--
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-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message


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

Milos Kleint updated MEVENIDE-542:
----------------------------------

    Fix Version/s: NB_3.0

> <Badly formed Maven project> when adding profile to pom
> -------------------------------------------------------
>
>                 Key: MEVENIDE-542
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.4, NB_3.0
>         Environment: Windows 2000
>            Reporter: Daniel Mutch
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.0
>
>
> Adding the following profile to a pom.xml seems to render the project invalid
> <profiles>
>         <profile>
>             <id>default-tools.jar</id>
>             <activation>
>                 <property>
>                     <name>java.vendor</name>
>                     <value>Sun Microsystems Inc.</value>
>                 </property>
>             </activation>
>             <dependencies>
>                 <dependency>
>                     <groupId>com.sun</groupId>
>                     <artifactId>tools</artifactId>
>                     <version>1.4.2</version>
>                     <scope>system</scope>
>                     <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
>                 </dependency>
>             </dependencies>
>         </profile>
>     </profiles>
> It appears to be the dependencies. Commenting them out solves the problem.

--
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-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message


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

Milos Kleint updated MEVENIDE-542:
----------------------------------

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

> <Badly formed Maven project> when adding profile to pom
> -------------------------------------------------------
>
>                 Key: MEVENIDE-542
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.4, NB_3.0
>         Environment: Windows 2000
>            Reporter: Daniel Mutch
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.1
>
>
> Adding the following profile to a pom.xml seems to render the project invalid
> <profiles>
>         <profile>
>             <id>default-tools.jar</id>
>             <activation>
>                 <property>
>                     <name>java.vendor</name>
>                     <value>Sun Microsystems Inc.</value>
>                 </property>
>             </activation>
>             <dependencies>
>                 <dependency>
>                     <groupId>com.sun</groupId>
>                     <artifactId>tools</artifactId>
>                     <version>1.4.2</version>
>                     <scope>system</scope>
>                     <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
>                 </dependency>
>             </dependencies>
>         </profile>
>     </profiles>
> It appears to be the dependencies. Commenting them out solves the problem.

--
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-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message


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

Milos Kleint commented on MEVENIDE-542:
---------------------------------------

the correct way of referencing environment variables is to use the ${env.JAVA_1_4_HOME} pattern.
However while that seems to work for build of the project, the loading of the project fails in this case. I suppose that's an issue within maven itself. The env.JAVA_1_4_HOME property cannot only be found in the <system> element. When defined in profile's activation for example, it seems to resolve fine.


> <Badly formed Maven project> when adding profile to pom
> -------------------------------------------------------
>
>                 Key: MEVENIDE-542
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.4, NB_3.0
>         Environment: Windows 2000
>            Reporter: Daniel Mutch
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.1
>
>
> Adding the following profile to a pom.xml seems to render the project invalid
> <profiles>
>         <profile>
>             <id>default-tools.jar</id>
>             <activation>
>                 <property>
>                     <name>java.vendor</name>
>                     <value>Sun Microsystems Inc.</value>
>                 </property>
>             </activation>
>             <dependencies>
>                 <dependency>
>                     <groupId>com.sun</groupId>
>                     <artifactId>tools</artifactId>
>                     <version>1.4.2</version>
>                     <scope>system</scope>
>                     <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
>                 </dependency>
>             </dependencies>
>         </profile>
>     </profiles>
> It appears to be the dependencies. Commenting them out solves the problem.

--
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-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message


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

Milos Kleint updated MEVENIDE-542:
----------------------------------

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

most probably a maven embedder issue ->3.2

> <Badly formed Maven project> when adding profile to pom
> -------------------------------------------------------
>
>                 Key: MEVENIDE-542
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.4, NB_3.0
>         Environment: Windows 2000
>            Reporter: Daniel Mutch
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.2
>
>
> Adding the following profile to a pom.xml seems to render the project invalid
> <profiles>
>         <profile>
>             <id>default-tools.jar</id>
>             <activation>
>                 <property>
>                     <name>java.vendor</name>
>                     <value>Sun Microsystems Inc.</value>
>                 </property>
>             </activation>
>             <dependencies>
>                 <dependency>
>                     <groupId>com.sun</groupId>
>                     <artifactId>tools</artifactId>
>                     <version>1.4.2</version>
>                     <scope>system</scope>
>                     <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
>                 </dependency>
>             </dependencies>
>         </profile>
>     </profiles>
> It appears to be the dependencies. Commenting them out solves the problem.

--
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-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message


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

Jaromir Uhrik commented on MEVENIDE-542:
----------------------------------------

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

> <Badly formed Maven project> when adding profile to pom
> -------------------------------------------------------
>
>                 Key: MEVENIDE-542
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.4, NB_3.0
>         Environment: Windows 2000
>            Reporter: Daniel Mutch
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.2
>
>
> Adding the following profile to a pom.xml seems to render the project invalid
> <profiles>
>         <profile>
>             <id>default-tools.jar</id>
>             <activation>
>                 <property>
>                     <name>java.vendor</name>
>                     <value>Sun Microsystems Inc.</value>
>                 </property>
>             </activation>
>             <dependencies>
>                 <dependency>
>                     <groupId>com.sun</groupId>
>                     <artifactId>tools</artifactId>
>                     <version>1.4.2</version>
>                     <scope>system</scope>
>                     <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
>                 </dependency>
>             </dependencies>
>         </profile>
>     </profiles>
> It appears to be the dependencies. Commenting them out solves the problem.

--
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-542) <Badly formed Maven project> when adding profile to pom

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

Reply to Author | View Threaded | Show Only this Message


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

Milos Kleint closed MEVENIDE-542.
---------------------------------

    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.

> <Badly formed Maven project> when adding profile to pom
> -------------------------------------------------------
>
>                 Key: MEVENIDE-542
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-542
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_2.4, NB_3.0
>         Environment: Windows 2000
>            Reporter: Daniel Mutch
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.2
>
>
> Adding the following profile to a pom.xml seems to render the project invalid
> <profiles>
>         <profile>
>             <id>default-tools.jar</id>
>             <activation>
>                 <property>
>                     <name>java.vendor</name>
>                     <value>Sun Microsystems Inc.</value>
>                 </property>
>             </activation>
>             <dependencies>
>                 <dependency>
>                     <groupId>com.sun</groupId>
>                     <artifactId>tools</artifactId>
>                     <version>1.4.2</version>
>                     <scope>system</scope>
>                     <systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
>                 </dependency>
>             </dependencies>
>         </profile>
>     </profiles>
> It appears to be the dependencies. Commenting them out solves the problem.

--
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