[
http://jira.andromda.org/browse/MAVEN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bob Fields closed MAVEN-62.
---------------------------
Resolution: Fixed
Fix Version/s: 3.4-SNAPSHOT
Assignee: Bob Fields (was: Plushnikov Michail)
common does not have dependencies on mda, profile, log4j, or digester artifacts
any more. Dependencies have been refactored for efficiency, to remove
unnecessary dependencies and duplications.
> pom.xml generated incorrectly. result is eclipse:eclipse fails.
> (dependencyManagement dependency missing version)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MAVEN-62
> URL: http://jira.andromda.org/browse/MAVEN-62
> Project: Maven Plugins
> Issue Type: Bug
> Affects Versions: 3.2
> Environment: shell: CYGWIN_NT-6.0 laptop 1.5.24(0.156/4/2)
> 2007-01-31 10:57 i686 Cygwin
> OS: windows Vista
> jvm:
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> Reporter: chris bedford
> Assignee: Bob Fields
> Fix For: 3.4-SNAPSHOT
>
>
> I found this bug while working through the tutorial. when i got to this
> page >>
> http://galaxy.andromda.org/index.php?option=com_content&task=view&id=134&Itemid=89
> i was able to run the tests with the expected failure.
> I wanted to use eclipse to look at the test classes that i copied over (as
> per the instructions) so i attempted to run
> mvn eclipse:eclipse at the top level project directory (timetracker).
> I got the stack trace included below.
> I then downloaded the maven sources and the sources for eclipse and i
> eventually found that the source of the
> crash was that the project/dependencyManagement/dependency entries for both
> timetracker-common and
> commons-digester
> were missing '<version>' tags. This definitely caused the crash in the
> maven eclipse:eclipse plugin...
> when i inserted the proper version tags (pls see the extract of my modified
> timetracker/app/pom.xml below)
> then mvn eclipse:eclipse executed with no more crash.
> For this reason i don't think this problem is due to a deficiency in the
> eclipse:eclipse plugin. I am guessing that this is a problem with some
> aspect of Andromda's code generator (whatever spits out the maven pom files).
> thanks,
> -chris
> STACK TRACE:
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.andromda
> .timetracker:timetracker-common:null:jar}: The version cannot be empty.
> at
> org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArt
> ifact.java:147)
> at
> org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java
> :122)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifa
> ct(DefaultArtifactFactory.java:158)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createDepend
> encyArtifact(DefaultArtifactFactory.java:58)
> at
> org.apache.maven.plugin.ide.AbstractIdeSupportMojo.createManagedVersi
> onMap(AbstractIdeSupportMojo.java:702)
> at
> org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolu
> tion(AbstractIdeSupportMojo.java:430)
> at
> org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractId
> eSupportMojo.java:398)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:420)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> Goal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 26 seconds
> [INFO] Finished at: Wed Apr 04 19:16:54 PDT 2007
> [INFO] Final Memory: 27M/48M
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>${pom.groupId}</groupId>
> <artifactId>timetracker-common</artifactId>
> <version>1.0-SNAPSHOT</version>
> <exclusions>
> <exclusion>
> <groupId>${pom.groupId}</groupId>
> <artifactId>timetracker-mda</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.andromda.profiles.uml14</groupId>
> <artifactId>andromda-profile</artifactId>
> </exclusion>
> <exclusion>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>commons-digester</groupId>
> <artifactId>commons-digester</artifactId>
> <version>1.8</version>
> <exclusions>
> <exclusion>
> <groupId>xml-apis</groupId>
> <artifactId>xml-apis</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> </dependencies>
> </dependencyManagement>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
