[Design the new POJO MicroContainer] - Re: Migration to maven
by adrian@jboss.org
"Kevin.Conner(a)jboss.com" wrote :
| To rectify do the following
| - delete projects (not contents)
| - run mvn eclipse:eclipse from root
| - File->Import
| - Choose Existing Projects
| - Browse to root
| - Import generated projects
|
This doesn't look like it is going to work unless you create your eclipse workspace
somewhere else. I guess it wants to copy the project onto itself?
The error I get is:
| Invalid project description.
| /home/ejort/microcontainer/aop-mc-int overlaps the location of another project: aop-mc-int
|
I guess it wants to copy the project onto itself?
I really don't understand why this is so difficult.
With CVS and ant I used to use eclipse project sets with no problems,
but that also doesn't work properly with the SVN eclipse plugin :-(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033947#4033947
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033947
17 years, 8 months
[Design the new POJO MicroContainer] - Re: Migration to maven
by adrian@jboss.org
"alesj" wrote : "pgier" wrote :
| | Try doing an "mvn -U -up" to make sure that you have everything up to date. If that doesn't work, the jbossxb version number that it's looking for should be picked up from the microcontainer parent. Make sure that this parent pom is up to date with svn and includes the jbossxb dependency in the dependencyManagement section.
|
| It was my mistake, my IDE doesn't update files in project's root directory (strange, but real ;-).
| Thanks for the help and also to Kevin, who also realized what the problem is.
Eclipse doesn't either. I currently have to resynch outside eclipse then refresh
which is a pain.
That is why it is better to have a top level project call
'build" instead of using the "root" of the project for the pom/build.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033944#4033944
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033944
17 years, 8 months
[Design the new POJO MicroContainer] - Re: Migration to maven
by adrian@jboss.org
"Kevin.Conner(a)jboss.com" wrote :
| "adrian(a)jboss.org" wrote : 1) It uses the wrong project name for dependencies
| | e.g. jboss-container instead of container
| My container project is calles jboss-container. It is likely that you have not imported the generated projects.
|
| To rectify do the following
| - delete projects (not contents)
| - run mvn eclipse:eclipse from root
| - File->Import
| - Choose Existing Projects
| - Browse to root
| - Import generated projects
|
| All your project names will be consistent and will work :-)
|
Ok I will try that, but since I hit the problem with a clean checkout of the
Microcontainer and a build with Maven before creating the new eclipse
projects, I don't know whether this entirely consistent? -)
I've also seen this problem before with the common project.
anonymous wrote :
| "adrian(a)jboss.org" wrote : 2) Things like src/resources/tests end up as a source import when it should be a class
| | library import. If they are source, you can't find the xml, etc. in the classpathNot sure why it can't be found on the classpath, all sources are there by default. Do you have a specific example?
src/resources/schema or src/resources/xml-tests in the container project
would be examples. After an eclipse:eclipse these are invisible to tests
run inside eclipse. They have type="src" instead of type="lib' in the .classpath
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033943#4033943
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033943
17 years, 8 months
[Design the new POJO MicroContainer] - Re: Migration to maven
by Kevin.Conner@jboss.com
"adrian(a)jboss.org" wrote : The Maven eclipse:eclipse build is currently broken.
Not for me it isn't :-)
"adrian(a)jboss.org" wrote : 1) It uses the wrong project name for dependencies
| e.g. jboss-container instead of container
My container project is calles jboss-container. It is likely that you have not imported the generated projects.
To rectify do the following
- delete projects (not contents)
- run mvn eclipse:eclipse from root
- File->Import
- Choose Existing Projects
- Browse to root
- Import generated projects
All your project names will be consistent and will work :-)
"adrian(a)jboss.org" wrote : 2) Things like src/resources/tests end up as a source import when it should be a class
| library import. If they are source, you can't find the xml, etc. in the classpathNot sure why it can't be found on the classpath, all sources are there by default. Do you have a specific example?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033937#4033937
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033937
17 years, 8 months
[Design the new POJO MicroContainer] - Re: Migration to maven
by adrian@jboss.org
"Kevin.Conner(a)jboss.com" wrote : "pgier" wrote : Yes, I think that's a good idea. I'm planning that the next version of the jboss-parent pom will use the eclipse plugin to generate eclipse project files. I just haven't had time yet to add (and test) this for microcontainer. Feel free to add it if you want.
| What needs adding? mvn eclipse:eclipse will generate them and mvn:add-maven-repo will configure the workspace. I run this on all maven projects :-)
|
The Maven eclipse:eclipse build is currently broken.
Some of the obvious things that don't work:
1) It uses the wrong project name for dependencies
e.g. jboss-container instead of container
2) Things like src/resources/tests end up as a source import when it should be a class
library import. If they are source, you can't find the xml, etc. in the classpath
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033926#4033926
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033926
17 years, 8 months