[jira] Updated: (IVY-511) Use standard coding conventions

2008-01-02 Thread Markus M. May (JIRA)

 [ 
https://issues.apache.org/jira/browse/IVY-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Markus M. May updated IVY-511:
--

Attachment: ivy.diff

Added a diff with changes in the Checkstyle configuration as well as changes to 
different classes to clean up checkstyl error messages.

 Use standard coding conventions
 ---

 Key: IVY-511
 URL: https://issues.apache.org/jira/browse/IVY-511
 Project: Ivy
  Issue Type: Improvement
Reporter: Xavier Hanin
 Attachments: ivy.diff


 At the moment Ivy code base is using sun standard coding conventions, except 
 for private fields which use an underscore prefix.
 Using the plain standard conventions would help developers read the code more 
 easily, and thus could attract more developers.
 The coding conventions are described here:
 http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (IVYDE-68) IvyDE is using some internal classes of Eclipse

2007-12-30 Thread Markus M. May (JIRA)

[ 
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12555023
 ] 

Markus M. May commented on IVYDE-68:


I have editd this plugin, to support also the Eclipse 3.4 version. This patch 
does include the previous patch as well. 

The class FixedJavaSearchPage is a copy of the original file of eclipse and 
then edited like the one stated above.

 IvyDE is using some internal classes of Eclipse
 ---

 Key: IVYDE-68
 URL: https://issues.apache.org/jira/browse/IVYDE-68
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
 Attachments: IVYDE-68-r607532.patch


 Some classes in IvyDE use come classes which are in some 
 {{org.eclipseinternal... }} packages, which should not be used. Compiling 
 IvyDE with Eclipse 3.3 raise warning like :
 {quote}
 Discouraged access: The method containerPut(IJavaProject, IPath, 
 IClasspathContainer) from the type JavaModelManager is not accessible due to 
 restriction on required library 
 /Users/nicolas/tools/eclipse-3.3/plugins/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
   ivyde/src/java/org/apache/ivyde/eclipse/cpcontainer 
 IvyClasspathContainer.java  {quote}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (IVYDE-68) IvyDE is using some internal classes of Eclipse

2007-12-30 Thread Markus M. May (JIRA)

 [ 
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Markus M. May updated IVYDE-68:
---

Attachment: ivyde.diff

Patch for Eclipse 3.4

 IvyDE is using some internal classes of Eclipse
 ---

 Key: IVYDE-68
 URL: https://issues.apache.org/jira/browse/IVYDE-68
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
 Attachments: IVYDE-68-r607532.patch, ivyde.diff


 Some classes in IvyDE use come classes which are in some 
 {{org.eclipseinternal... }} packages, which should not be used. Compiling 
 IvyDE with Eclipse 3.3 raise warning like :
 {quote}
 Discouraged access: The method containerPut(IJavaProject, IPath, 
 IClasspathContainer) from the type JavaModelManager is not accessible due to 
 restriction on required library 
 /Users/nicolas/tools/eclipse-3.3/plugins/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
   ivyde/src/java/org/apache/ivyde/eclipse/cpcontainer 
 IvyClasspathContainer.java  {quote}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.