The pax:eclipse mojo can be very slow when processing bundles with lots of 
dependencies inside large project trees
------------------------------------------------------------------------------------------------------------------

                 Key: PAXCONSTRUCT-96
                 URL: http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-96
             Project: Pax Construct
          Issue Type: Bug
          Components: maven-pax-plugin
    Affects Versions: 1.3
            Reporter: Stuart McCulloch
            Assignee: Stuart McCulloch
             Fix For: 1.4


The default value for fixDependencies (introduced in 1.3 under PAXCONSTRUCT-85) 
does a brute-force
search of the local project tree to exclude dependencies to local projects from 
being "fixed" as non-OSGi
dependencies.

This fixing of dependencies was needed to support tests in Eclipse, which may 
have dependencies on
other OSGi artifacts that aren't referenced in the bundle manifest, so aren't 
automatically added by PDE.
In this case we need to add a non-OSGi dependency to the same artifact for the 
test to work in Eclipse.

However, applying this "fixing" to local projects meant that Eclipse didn't 
always work well when using
"hot-code-replace" style debugging, so we need a way to detect local projects - 
in 1.3 this was done by
searching the project file-system, but when that contains >100 bundles it can 
be very slow.

So in 1.4 we're going to rely on the Maven reactor - however, this means that 
local project dependencies
might be "fixed" if you use the pax:eclipse goal inside a bundle project, 
rather than from the project root
(because the Maven reactor will then just contain one project - the one you're 
currently building)

But this is a reasonable trade-off, and is how a lot of other IDE plugins work 
- note that you can still get
the 1.3 behaviour by setting "fixDependencies" in the maven-pax-plugin 
configuration to be "CUSTOM".


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