[Design the new POJO MicroContainer] - Re: Remove eclipse files from SVN?
by Kevin.Conner@jboss.com
"adrian(a)jboss.org" wrote : I hate scripts. I always preferred make (declaritive) to ant (scripts).
Well, I was thinking more along the lines of having maven generate it :-)
"adrian(a)jboss.org" wrote : I want to download things and have it work, not waste time
| baby sitting eclipse builds (like I do now :-( )
| or remembering what order of magic incantations I need to get to a working build
| (besides rm -rf * and start again :-)
Sounds as if you need to use emacs + mvn command line :-)
"adrian(a)jboss.org" wrote : If the eclipse:eclipse was part of every build when somebody changed the pom
| then these would automatically get checked in with the pom update (even
| if they don't use eclipse) and it would be end of story.
|
Excluding other local changes of course ;-)
"adrian(a)jboss.org" wrote : Well, unless you need to do the mvn build to pull down thirdparty dependencies
| and then you are back to figuring out how to get eclipse to build it,
| i.e. whether it is a broken build or eclipse being stupid again. :-)
I can see we are not going to agree on this. ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034047#4034047
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034047
17 years, 11 months
[Design the new POJO MicroContainer] - Re: Remove eclipse files from SVN?
by adrian@jboss.org
"adrian(a)jboss.org" wrote : "Kevin.Conner(a)jboss.com" wrote : If we do not remove them then they will always show up as modified and will overwrite the current versions on an update.
| |
|
| They should only appear changed if somebody modifies the pom/dependencies.
|
I just tested this and it doesn't work.
The eclipse:eclipse plugin is not generating the files consistently.
e.g. I got this diff without changing anything
| Index: /home/ejort/microcontainer/aop-mc-int/.project
| ===================================================================
| --- /home/ejort/microcontainer/aop-mc-int/.project (revision 62024)
| +++ /home/ejort/microcontainer/aop-mc-int/.project (working copy)
| @@ -2,9 +2,9 @@
| <name>jboss-aop-mc-int</name>
| <comment>JBoss Microcontainer</comment>
| <projects>
| + <project>jboss-container</project>
| <project>jboss-kernel</project>
| <project>jboss-dependency</project>
| - <project>jboss-container</project>
| </projects>
| <buildSpec>
| <buildCommand>
|
I guess it is using HashSets or HashMaps internally so the order from the pom
is not being conserved.
V.Annoying :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034032#4034032
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034032
17 years, 11 months
[Design the new POJO MicroContainer] - Re: Remove eclipse files from SVN?
by adrian@jboss.org
"Kevin.Conner(a)jboss.com" wrote :
| BTW what do you think about generating the workspace? :-)
I hate scripts. I always preferred make (declaritive) to ant (scripts).
I want to download things and have it work, not waste time
baby sitting eclipse builds (like I do know :-( )
or remembering what order of magic incantations I need to get to a working build
(besides rm -rf * and start again :-)
If the eclipse:eclipse was part of every build when somebody changed the pom
then these would automatically get checked in with the pom update (even
if they don't use eclipse) and it would be end of story.
Well, unless you need to do the mvn build to pull down thirdparty dependencies
and then you are back to figuring out how to get eclipse to build it,
i.e. whether it is a broken build or eclipse being stupid again. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034017#4034017
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034017
17 years, 11 months