[
https://jira.codehaus.org/browse/MECLIPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=298077#comment-298077
]
Dan Tran commented on MECLIPSE-718:
---
this issue is resolved, here are comments from Barrie
On Mon, May 7, 2012 at 3:51 AM, Dan Tran dant...@gmail.com wrote:
Hi Barrie,
Sorry about late response
No sure where are here, just to recap
1. Check out http://svn.apache.org/repos/asf/karaf/branches/karaf-2.2.x
and change directory to the checkout directory
2. mvn clean install
3. mvn eclipse:eclipse
4. mvn eclipse:configure-workspace -Declipse.workspace=.
5. Open the newly created workspace under checkout directory
6. Inport all generated project files
You can see that lots of red mark projects, my suspect here is
maven-eclipse-plugin does not know to connect reactor
maven-bundle-plugin packaging project together like jar packaging
project
Perhaps we can do special hack to treat packing 'bundle' as 'jar
package, thing may work
On Fri, May 4, 2012 at 3:49 AM, Barrie Treloar baerr...@gmail.com wrote:
On Fri, May 4, 2012 at 8:12 PM, Barrie Treloar baerr...@gmail.com wrote:
On Thu, May 3, 2012 at 11:38 PM, Dan Tran dant...@gmail.com wrote:
Hi Barrie,
It is best to use
http://svn.apache.org/repos/asf/karaf/branches/karaf-2.2.x which is
very stable.
Yes 'bundle' = felix's maven-bundle-plugin
I meant to mentioned you have plenty of karma to burn from the
pde-maven-plugin days :)
Can you point me directly to which project is not resolving correctly?
Something with not too many dependencies :)
I can't find any bundle package types in the parent's dependencyManagement.
And is this because apache-felix bundle just generates jar files with
OSGI manifest entries anyway?
So if you can point me to one that does not work, and what you would
expect the .classpath entries to be etc I can investigate.
This looks like an Eclipse bug
See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=225754#c38
Essentially if
* the folder is directly below the default workspace then it IGNORES
the .project/name element on the import and uses the directory name
instead
* the folder is NOT directly below the default workspace then it
correctly uses .project/name
I think this is why the recommendation is to create workspace that has
NO project's kept underneath it.
I checked out the karaf code somewhere else, had an empty workspace
and then imported the projects. There were no compilation errors.
I will update the FAQ of m-e-p and put some notes in the Jira.
Support packaging 'bundle' from org.apache.felix:maven-bundle-plugin
Key: MECLIPSE-718
URL: https://jira.codehaus.org/browse/MECLIPSE-718
Project: Maven 2.x Eclipse Plugin
Issue Type: New Feature
Affects Versions: 2.9
Environment: windows, unix
Reporter: Dan Tran
packaging=bundle is the same as 'jar' packaging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
