[jira] Created: (MNGECLIPSE-449) Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Created: (MNGECLIPSE-449) Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors

JIRA jira@codehaus.org
Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: MNGECLIPSE-449
                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-449
             Project: Maven Integration for Eclipse
          Issue Type: Bug
          Components: Wizards
    Affects Versions: 0.0.12
         Environment: Window XP, Eclipse 3.2.2
            Reporter: Irene Levina
             Fix For: dev
         Attachments: www.zip

Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors.

To reproduce issue unzip attachment to any dir on your local drive and use Maven Import Wizard to import it, you will see that imported project will contain errors.
Way around user should use project preferences to change project compiler compliance level to 5.0

However it would be nice that wizard would provide choice to the user to specify compiler complience level.




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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-449) Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors

JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116205 ]

Eugene Kuleshov commented on MNGECLIPSE-449:
--------------------------------------------

Irene, the import wizard, and "update source folders" action is reading settings from the maven-compiler-plugin to set compiler settings and JRE classpath container in eclipse. If those settings are not specified in pom.xml (or commented out like in the project you've attached), imported project will be created with default workbench settings. So, it is working as expected.

> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-449
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-449
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Wizards
>    Affects Versions: 0.0.12
>         Environment: Window XP, Eclipse 3.2.2
>            Reporter: Irene Levina
>             Fix For: dev
>
>         Attachments: www.zip
>
>
> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors.
> To reproduce issue unzip attachment to any dir on your local drive and use Maven Import Wizard to import it, you will see that imported project will contain errors.
> Way around user should use project preferences to change project compiler compliance level to 5.0
> However it would be nice that wizard would provide choice to the user to specify compiler complience level.

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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-449) Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116210 ]

Irene Levina commented on MNGECLIPSE-449:
-----------------------------------------

Eugene, yes it is correct my mistake, basically typo :)  Unfortunetly I still trying to find solution how I can avoid compile task error, so I constantly trying to comment out and comment in eclipse compiler. So far your proposed FAQ solution doesn't work for me (:

Also since you answer on this issue, where I can post integration Q's (trying to use yours plugin in our IDE to create maven complian projects) what would be a good side or email list.
Thanks a lot :)

> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-449
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-449
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Wizards
>    Affects Versions: 0.0.12
>         Environment: Window XP, Eclipse 3.2.2
>            Reporter: Irene Levina
>             Fix For: dev
>
>         Attachments: www.zip
>
>
> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors.
> To reproduce issue unzip attachment to any dir on your local drive and use Maven Import Wizard to import it, you will see that imported project will contain errors.
> Way around user should use project preferences to change project compiler compliance level to 5.0
> However it would be nice that wizard would provide choice to the user to specify compiler complience level.

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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-449) Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116212 ]

Eugene Kuleshov commented on MNGECLIPSE-449:
--------------------------------------------

Irene, I suppose compiler issue would be MNGECLIPSE-447?

I am not really sure if would be a good idea to specify compiler settings in the import wizard. It is unclear what to when importing multiple projects and how this UI should look like. More over I think it would be a good idea to encourage users to overwrite settings from pom.xml and that manual setting will be scraped anyways once user kick "update source folders" action (it is the same code as import project wizard uses).

As a middle ground, maybe we can change strategy for choosing default JRE if pom.xml does not have it specified. For example we can use the bigest version registered in workspace.

If you have any ideas or suggestions on those please comment.

As for the integration questions, the best place is probably m2eclipse-dev mailing list. You can also create page on the project wiki and outline your requirements and needs. See http://docs.codehaus.org/display/M2ECLIPSE/Home

> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-449
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-449
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Wizards
>    Affects Versions: 0.0.12
>         Environment: Window XP, Eclipse 3.2.2
>            Reporter: Irene Levina
>             Fix For: dev
>
>         Attachments: www.zip
>
>
> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors.
> To reproduce issue unzip attachment to any dir on your local drive and use Maven Import Wizard to import it, you will see that imported project will contain errors.
> Way around user should use project preferences to change project compiler compliance level to 5.0
> However it would be nice that wizard would provide choice to the user to specify compiler complience level.

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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (MNGECLIPSE-449) Import Wizard uses default compiler settings when thay are not declared in pom.xml

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

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

Eugene Kuleshov updated MNGECLIPSE-449:
---------------------------------------

    Summary: Import Wizard uses default compiler settings when thay are not declared in pom.xml  (was: Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors)

> Import Wizard uses default compiler settings when thay are not declared in pom.xml
> ----------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-449
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-449
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Wizards
>    Affects Versions: 0.0.12
>         Environment: Window XP, Eclipse 3.2.2
>            Reporter: Irene Levina
>             Fix For: dev
>
>         Attachments: www.zip
>
>
> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors.
> To reproduce issue unzip attachment to any dir on your local drive and use Maven Import Wizard to import it, you will see that imported project will contain errors.
> Way around user should use project preferences to change project compiler compliance level to 5.0
> However it would be nice that wizard would provide choice to the user to specify compiler complience level.

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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (MNGECLIPSE-449) Import Wizard uses default compiler settings when thay are not declared in pom.xml

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

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

Eugene Kuleshov updated MNGECLIPSE-449:
---------------------------------------

    Fix Version/s:     (was: dev)

> Import Wizard uses default compiler settings when thay are not declared in pom.xml
> ----------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-449
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-449
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Wizards
>    Affects Versions: 0.0.12
>         Environment: Window XP, Eclipse 3.2.2
>            Reporter: Irene Levina
>         Attachments: www.zip
>
>
> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors.
> To reproduce issue unzip attachment to any dir on your local drive and use Maven Import Wizard to import it, you will see that imported project will contain errors.
> Way around user should use project preferences to change project compiler compliance level to 5.0
> However it would be nice that wizard would provide choice to the user to specify compiler complience level.

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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Closed: (MNGECLIPSE-449) Import Wizard uses default compiler settings when thay are not declared in pom.xml

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

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

Eugene Kuleshov closed MNGECLIPSE-449.
--------------------------------------

    Resolution: Incomplete

Provided test project has commented out compiler settings, so we use defaults when importing project.

Please submit separate enhancement requests or post to the dev mailing list if you need additional integration support.

> Import Wizard uses default compiler settings when thay are not declared in pom.xml
> ----------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-449
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-449
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Wizards
>    Affects Versions: 0.0.12
>         Environment: Window XP, Eclipse 3.2.2
>            Reporter: Irene Levina
>         Attachments: www.zip
>
>
> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors.
> To reproduce issue unzip attachment to any dir on your local drive and use Maven Import Wizard to import it, you will see that imported project will contain errors.
> Way around user should use project preferences to change project compiler compliance level to 5.0
> However it would be nice that wizard would provide choice to the user to specify compiler complience level.

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


Loading...