[
https://issues.apache.org/jira/browse/JDO-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705692#action_12705692
]
Andy Jefferson commented on JDO-596:
------------------------------------
Hi Craig,
but api2/pom.xml doesn't have a <parent> POM set, so doesn't use it. When I go
into "api2" and type "mvn clean install" it has no version so just dumps null
in. The only way I know of specifying a parent in a sub POM is something like
<parent>
<groupId>javax.jdo</groupId>
<artifactId>root</artifactId>
<version>2.3-SNAPSHOT</version>
<relativePath>..</relativePath>
</parent>
and that beats the point of having a parent POM to define the version. Maybe
some Maven has some undocumented option to do what you need ?
> Upgrade to maven 2
> ------------------
>
> Key: JDO-596
> URL: https://issues.apache.org/jira/browse/JDO-596
> Project: JDO
> Issue Type: Improvement
> Components: api2
> Reporter: Michelle Caisse
> Assignee: Craig Russell
> Priority: Minor
> Fix For: JDO 2 maintenance release 3
>
> Attachments: jdo-596.patch
>
>
> It would be a good idea to use maven 2. This involves rewriting the custom
> goals in maven.xml as Java plugins, among other things.
> This is for the JDO API not for the JDO TCK. We need a separate issue for the
> corresponding TCK change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
