Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No eclipse .project/.classpath is created when the command mvn pax:eclipse is executed [PAXCONSTRUCT-101] #118

Open
ops4j-issues opened this issue Feb 10, 2009 · 8 comments
Labels
Milestone

Comments

@ops4j-issues
Copy link

Charles Moulliard created PAXCONSTRUCT-101

Hi,

No eclipse .project/.classpath are created when the following command is executed. By the way, PAX claim that the build is successul !!

Remark : I have downloaded from svn the last snapshot and build it.

D:\Dvlpt\Java\workspace-ganymede\osgi\reportincident.service.osgi>mvn pax:eclipse mvn clean install pax:eclipse -DdownloadSources
INFO Scanning for projects...
INFO Reactor build order:
INFO org.apache.camel.example.reportincident.service.osgi (OSGi project)
INFO reportincident.service.osgi - plugin configuration
INFO reportincident.service.osgi - wrapper instructions
INFO reportincident.service.osgi - bundle instructions
INFO reportincident.service.osgi - imported bundles
INFO Searching repository for plugin with prefix: 'pax'.
INFO ------------------------------------------------------------------------
ERROR BUILD FAILURE
INFO ------------------------------------------------------------------------
INFO Invalid task 'mvn': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupI
d:pluginArtifactId:pluginVersion:goal
INFO ------------------------------------------------------------------------
INFO For more information, run Maven with the -e switch
INFO ------------------------------------------------------------------------
INFO Total time: < 1 second
INFO Finished at: Tue Feb 10 16:32:52 CET 2009
INFO Final Memory: 3M/5M
INFO ------------------------------------------------------------------------

D:\Dvlpt\Java\workspace-ganymede\osgi\reportincident.service.osgi>mvn clean install pax:eclipse -DdownloadSources
INFO Scanning for projects...
INFO Reactor build order:
INFO org.apache.camel.example.reportincident.service.osgi (OSGi project)
INFO reportincident.service.osgi - plugin configuration
INFO reportincident.service.osgi - wrapper instructions
INFO reportincident.service.osgi - bundle instructions
INFO reportincident.service.osgi - imported bundles
INFO Searching repository for plugin with prefix: 'pax'.
INFO ------------------------------------------------------------------------
INFO Building org.apache.camel.example.reportincident.service.osgi (OSGi project)
INFO task-segment: clean, install, pax:eclipse
INFO ------------------------------------------------------------------------
INFO clean:clean
INFO site:attach-descriptor
INFO install:install
INFO Installing D:\Dvlpt\Java\workspace-ganymede\osgi\reportincident.service.osgi\pom.xml to c:.m2\repository\org\apa
che\camel\example\reportincident.service.osgi\1.0-SNAPSHOT\reportincident.service.osgi-1.0-SNAPSHOT.pom
INFO pax:eclipse
INFO Not running eclipse plugin goal for pom project
INFO Using as WTP server : null
INFO Adding default classpath contaigner: org.eclipse.jdt.launching.JRE_CONTAINER
INFO ------------------------------------------------------------------------
INFO Building reportincident.service.osgi - plugin configuration
INFO task-segment: clean, install, pax:eclipse
INFO ------------------------------------------------------------------------
INFO clean:clean
INFO site:attach-descriptor
INFO install:install
INFO Installing D:\Dvlpt\Java\workspace-ganymede\osgi\reportincident.service.osgi\poms\pom.xml to c:.m2\repository\or
g\apache\camel\example\reportincident\service\osgi\build\shared-plugin-settings\1.0-SNAPSHOT\shared-plugin-settings-1.0-
SNAPSHOT.pom
INFO pax:eclipse
INFO Not running eclipse plugin goal for pom project
INFO Using as WTP server : null
INFO Adding default classpath contaigner: org.eclipse.jdt.launching.JRE_CONTAINER
INFO ------------------------------------------------------------------------
INFO Building reportincident.service.osgi - wrapper instructions
INFO task-segment: clean, install, pax:eclipse
INFO ------------------------------------------------------------------------
INFO clean:clean
INFO site:attach-descriptor
INFO install:install
INFO Installing D:\Dvlpt\Java\workspace-ganymede\osgi\reportincident.service.osgi\poms\wrappers\pom.xml to c:.m2\repo
sitory\org\apache\camel\example\reportincident\service\osgi\build\wrapper-bundle-settings\1.0-SNAPSHOT\wrapper-bundle-se
ttings-1.0-SNAPSHOT.pom
INFO pax:eclipse
INFO Not running eclipse plugin goal for pom project
INFO Using as WTP server : null
INFO Adding default classpath contaigner: org.eclipse.jdt.launching.JRE_CONTAINER
INFO ------------------------------------------------------------------------
INFO Building reportincident.service.osgi - bundle instructions
INFO task-segment: clean, install, pax:eclipse
INFO ------------------------------------------------------------------------
INFO clean:clean
INFO site:attach-descriptor
INFO install:install
INFO Installing D:\Dvlpt\Java\workspace-ganymede\osgi\reportincident.service.osgi\poms\compiled\pom.xml to c:.m2\repo
sitory\org\apache\camel\example\reportincident\service\osgi\build\compiled-bundle-settings\1.0-SNAPSHOT\compiled-bundle-
settings-1.0-SNAPSHOT.pom
INFO pax:eclipse
INFO Not running eclipse plugin goal for pom project
INFO Using as WTP server : null
INFO Adding default classpath contaigner: org.eclipse.jdt.launching.JRE_CONTAINER
INFO ------------------------------------------------------------------------
INFO Building reportincident.service.osgi - imported bundles
INFO task-segment: clean, install, pax:eclipse
INFO ------------------------------------------------------------------------
INFO clean:clean
INFO site:attach-descriptor
INFO install:install
INFO Installing D:\Dvlpt\Java\workspace-ganymede\osgi\reportincident.service.osgi\provision\pom.xml to c:.m2\reposito
ry\org\apache\camel\example\reportincident\service\osgi\build\provision\1.0-SNAPSHOT\provision-1.0-SNAPSHOT.pom
INFO pax:eclipse
INFO Not running eclipse plugin goal for pom project
INFO Using as WTP server : null
INFO Adding default classpath contaigner: org.eclipse.jdt.launching.JRE_CONTAINER
INFO
INFO
INFO ------------------------------------------------------------------------
INFO Reactor Summary:
INFO ------------------------------------------------------------------------
INFO org.apache.camel.example.reportincident.service.osgi (OSGi project) SUCCESS 10.937s
INFO reportincident.service.osgi - plugin configuration .... SUCCESS 0.079s
INFO reportincident.service.osgi - wrapper instructions .... SUCCESS 0.203s
INFO reportincident.service.osgi - bundle instructions ..... SUCCESS 0.047s
INFO reportincident.service.osgi - imported bundles ........ SUCCESS 0.046s
INFO ------------------------------------------------------------------------
INFO ------------------------------------------------------------------------
INFO BUILD SUCCESSFUL
INFO ------------------------------------------------------------------------
INFO Total time: 12 seconds
INFO Finished at: Tue Feb 10 16:33:12 CET 2009
INFO Final Memory: 15M/28M
INFO ------------------------------------------------------------------------

D:\Dvlpt\Java\workspace-ganymede\osgi\reportincident.service.osgi>


Fixed in: 1.7.0
Votes: 0, Watches: 0

@ops4j-issues
Copy link
Author

Stuart McCulloch commented

Did you just create a new project (ie. pax-create-project) without adding any bundles? (ie. no pax-create-bundle / pax-wrap-jar / pax-import-bundle ?)

If so then I wouldn't expect it to create any eclipse files because there are only POMs in the project tree, and by default the maven-eclipse-plugin (whose mojo we use and extend in the maven-pax-plugin) doesn't create eclipse files for POMs. This is because most versions of Eclipse don't handle hierarchical projects very well (if at all).

Once you've started adding bundles running "mvn pax:eclipse" will generate project files (one per-bundle) which you can then import by selecting the top-most directory. Each bundle project will then show up as an individual project in the workspace.

If you still seeing a problem after adding bundles, please attach a testcase along with any relevant OS / Java / Maven details.

@ops4j-issues
Copy link
Author

Charles Moulliard commented

You are right. That was the case. I create a project without bundle. After creating a bundle, it was possible to use mvn pax:eclipse.

Maybe it should be interesting to provide a comment in the mvn output in order to warn the user that no bundle exist ?

@ops4j-issues
Copy link
Author

Stuart McCulloch commented

Sure, that's possible... at the moment it says "Not running eclipse plugin goal for pom project" for each pom project, but I guess it could be made more explicit. Of course if people want to start creating wiki pages describing their use of Pax-Construct along with any hints, tips, and potential gotchas then that would also be good 😄

@ops4j-issues
Copy link
Author

Charles Moulliard commented

Is there a forum like www.nabble.com (for camel, servicemix projects) to discuss pax ideas ?

@ops4j-issues
Copy link
Author

Stuart McCulloch commented

Most people use general@lists.ops4j.org for questions / discussions - you can also to add your own pages (discussions, designs, and so on) to the OPS4J wiki at http://wiki.ops4j.org if you want something more structured. You should have edit rights to the wiki as you've got a JIRA account. HTH

@ops4j-issues
Copy link
Author

Charles Moulliard commented

How can I use the email address 'general@lists.ops4j.org' to subscribe ?

This morning I try to send an email with subject = subscribe without success

@ops4j-issues
Copy link
Author

Stuart McCulloch commented

Did you send an email to general-subscribe@lists.ops4j.org? There's also an online subscription form available at http://lists.ops4j.org/mailman/listinfo/general

@ops4j-issues
Copy link
Author

Stuart McCulloch commented

Update logging output and documentation in 1.5 to make this clearer

@ops4j-issues ops4j-issues added this to the 1.7.0 milestone Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant