Hi,
Some notes on project import that might help to refine this plugin:
1) Eclipse (I am using 3.1 RC1) does not traverses all sub-folders
when provided with a root directory to import projects from. It stops
traversing the sub-folders when it encounters first project
definition (.project) in a parent folder. I have posted a related
message on Eclipse newsgroup as well to explain this.
http://www.eclipse.org/newsportal/article.php?id=40947&group=eclipse.platform#40947
A useful resource to refer to might be the following Eclipse plugin
that traverses all the folders:
http://eclipse-tools.sourceforge.net/projecttransfer/download.html
I think it's a bad idea to have eclipse projects under another one. If
you create sub-projects into sub-folders only for pom project, we will
not have problems because eclipse plugin generate files only for java
projetcs and not for pom projects. It's what we have for m2 project.
Yep, I agree its a bad idea but I noticed project definitions being
generated such that to result in nested projects. Anyway, this seems to
work fine with latest checkout, so thats great!
2) Eclipse project definitions are generated for projects with a
pom.xml whether or not these respect rules for nested projects. I
think these should only be generated for projects with Java sources
(and not exclude any java templates) or directory structure
restructured where we might run into situations resulting in nested
projects or uncompilable projects.
The actual svn version of eclipse plugin generate .project and
.classpath files only for project with a packaging tag != pom
Yeah, as I said these are generated fine now. I still have a few build
errors showing up in Eclipse. Attached are a few notes on the errors
found and ones that I could get around (updating classpath etc).
Thanks,
Rahul
_______
NOTES
-------
Project: maven-plugin-tools-java
- Resources under srctest/resources/ folder are not resolved to appropriate
paths.
- Think this is b'cos the 'source' folder sitting underneath above said folder
does not
follow convention of being named as 'src' (is it?)
- WORKAROUND: Adding this folder as a source folder for the project fixes it.
- SUGGESTED: might be an idea to rename 'source' to 'src'
Project: maven-artifact-ant
- org.apache.maven.artifact.ant.Pom.java has following unresolved import
import org.codehaus.plexus.util.introspection.ReflectionValueExtractor;
- This need to use plexus-utils-1.0-alpha-3.jar
Project: maven-archetype-quickstart
- File App.java sitting under
srcmain/resources/archetype-resources/src/main/java/ is not compilable.
- The package reference in the source file is '$package'. I believe the file is
a template, so might
be an idea not to resolve it as a Java source or appropriate exclusion
filters to be set up in the build path.
- Same deal as above with file AppTest.java under
src/main/resources/archetype-resources/src/test/java
Project: maven-archetype-mojo
- Same prob as in project maven-archetype-quickstart with MyMojo.java
- .classpath missing reference to
M2_REPO/org/apache/maven/maven-plugin-api/2.0-SNAPSHOT/maven-plugin-api-2.0-SNAPSHOT.jar
Project: maven-archetype-marmalade-mojo
- Same prob as in project maven-archetype-quickstart with files
CopyFileTag.java and MyMojoTagLibrary.java
- .classpath missing reference to
M2_REPO/marmalade/marmalade-core/1.0-alpha-3/marmalade-core-1.0-alpha-3.jar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
