[
http://issues.ops4j.org/browse/PAXCONSTRUCT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12289#action_12289
]
Stuart McCulloch commented on PAXCONSTRUCT-108:
-----------------------------------------------
OK, here's what I typically do when working with Eclipse:
1) create a project and add some bundles with the Pax-Construct scripts
2) at the top-level type "mvn clean install pax:eclipse" from the command-line
3) import projects into Eclipse as existing Plug-in projects
4) ... develop / add pom dependencies / etc ...
5) when I want to refresh the manifests I typically use "mvn clean install
pax:eclipse"
(sometimes I edit them in PDE directly and only use Maven at major
milestones)
6) remember to hit F5 to re-sync the project with the file-system
Note that there's an execution fragment in the top-level pom that's commented
out by default (look for the IDE comment) - if you uncomment this then manifests
will be refreshed on every "mvn package" (note that it's commented out because
not everyone uses Eclipse, and this step can slow down the build)
Otherwise you can use "mvn pax:eclipse" to re-gen the manifest for Eclipse/PDE
(I forgot you were talking about the PDE specific manifest, which has to be in a
specific location and have the correct relative paths - this is a major pain
point
about PDE which causes a lot of frustration - very rarely you can also run into
issues on Windows where Eclipse locks the file and you can't update it from
another process...)
FWIW, most of the issues wrt. Eclipse come from the fact that we don't integrate
directly into the IDE (we don't provide an Eclipse plug-in) - if someone can
spare
some time to work on this then I'd be happy to advise, but at the moment I don't
have any free time left to do this :(
We also have some developers using Pax-Construct with Eclipse, perhaps they
can share some of their experiences and "best-practices"
> MANIFEST.MF file is not refreshed (or even recreated after a delete) by the
> command mvn org.ops4j:maven-pax-plugin:compile
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: PAXCONSTRUCT-108
> URL: http://issues.ops4j.org/browse/PAXCONSTRUCT-108
> Project: Pax Construct
> Issue Type: Bug
> Components: maven-pax-plugin
> Affects Versions: 1.4
> Reporter: Charles Moulliard
> Assignee: Stuart McCulloch
>
> The content of the file MANIFEST.MF is not refreshed (or even recreated after
> a delete) by the command mvn org.ops4j:maven-pax-plugin:compile
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
