[
https://issues.apache.org/jira/browse/MECLIPSE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-686.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Allow project references for PDE projects
> -----------------------------------------
>
> Key: MECLIPSE-686
> URL: https://issues.apache.org/jira/browse/MECLIPSE-686
> Project: Maven Eclipse Plugin
> Issue Type: Improvement
> Components: PDE support
> Affects Versions: 2.8
> Environment: Windows XP, Eclipse 3.6.1, Java 6
> Reporter: Jeff Torson
> Attachments: pom.xml
>
>
> When creating a PDE project, it would be since if project references were
> still used when the <useProjectReferences> is set to true. I know that PDE
> projects need JARs to run correctly but for development it's must nicer to be
> able to edit other dependent projects files and to be able to use those
> changes right away. Currently setting this to true for a multi-module
> project will not include any projects in the classpath. Setting this to
> false will add classpath entries but to the copied project JARs.
> If I set this to false, or if useProjectReferences was set to true and did
> still allow projects in the classpath, I would need to regenerate the JARs in
> order to run my application, so it seems like the developer friendly way
> would be the better way to go.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
