[ 
http://issues.ops4j.org/jira/browse/PAXLOGGING-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11570#action_11570
 ] 

Peter Neubauer commented on PAXLOGGING-33:
------------------------------------------

Hi there,
I just set up Eclipse 3.4 with PaxLogging by checking out a clean copy, doing

mvn clean install eclipse:eclipse

And then in Eclipse, Import->Existing project into workspace->pax/logging as 
root.

I get a few errors on the generated manifest files and teh symbolic names ("-" 
is reported as wrong but allowed by spec) but no compile errors in Java files.

If you press F3 on the super in  "super.parseAppender()" and are activating the 
"Link with source" button above the package explorer (the one with the two 
arrows), my Eclipse is correctly showing that the PropertyConfigurator resides 
in the referenced library M2_repo/.../log4j-1.2.15.jar. What is your resolution 
showing?

HTH

Peter

> Some classes have compile errors due to missing methods
> -------------------------------------------------------
>
>                 Key: PAXLOGGING-33
>                 URL: http://issues.ops4j.org/jira/browse/PAXLOGGING-33
>             Project: Pax Logging
>          Issue Type: Task
>    Affects Versions: 1.1.1 
>         Environment: Windows XP with Java 1.5 and Equinox as OSGI platform
>            Reporter: Florian
>            Assignee: Peter Neubauer
>            Priority: Minor
>
> Some classes have compile errors while integrating them into eclipse although 
> the build with maven is successful.
> Here are the classes with problems:
> PaxLoggingConfigurator
> line 45
> PaxLoggingServiceImpl 
> lines 197, 198
>         PaxLoggingConfigurator configurator = new PaxLoggingConfigurator( 
> m_appenderTracker );
>         configurator.doConfigure( extracted, LogManager.getLoggerRepository() 
> );
> PaxLoggerImpl
> lines 116 to 124
>     public int getLogLevel()
>     {
>         return m_delegate.getLevel().toInt();
>     }
>     public String getName()
>     {
>         return m_delegate.getName();
>     }
> It would be nice, if these compile errors could be removed. For me it's 
> difficult to decide what to remove or what to implement because I don't know 
> the further development plan.

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

        

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to