Re: [jira] Updated: (TUSCANY-834) Missing version information for junit plugin in das pom.xml
You normally don't need or want to do this - the information is inherited from the parent (das) pom.xml's dependencyManagement section which enables it to be specified in one place and shared between all modules. -- Jeremy On Oct 12, 2006, at 2:32 PM, Luciano Resende (JIRA) wrote: [ http://issues.apache.org/jira/browse/TUSCANY-834?page=all ] Luciano Resende updated TUSCANY-834: Attachment: tuscany834.lresende.20061012.txt Patch adding the junit version reference to java/das/rdb/pom.xml Missing version information for junit plugin in das pom.xml --- Key: TUSCANY-834 URL: http://issues.apache.org/jira/browse/TUSCANY-834 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Affects Versions: Java-M2 Reporter: Luciano Resende Assigned To: Luciano Resende Priority: Minor Fix For: Java-M2 Attachments: tuscany834.lresende.20061012.txt DAS RDB pom has no version information for junit dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/ Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/ software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Updated: (TUSCANY-834) Missing version information for junit plugin in das pom.xml
The problem here was that if I generate the source distribution by doing a export of das/rdb and then update the pom to point to parent pom, these default values won't be there and compilation will fail. I think what you said is true if I export the whole das subtree as part of the source distribution, then default values will be available. - Luciano On 10/12/06, Jeremy Boynes [EMAIL PROTECTED] wrote: You normally don't need or want to do this - the information is inherited from the parent (das) pom.xml's dependencyManagement section which enables it to be specified in one place and shared between all modules. -- Jeremy On Oct 12, 2006, at 2:32 PM, Luciano Resende (JIRA) wrote: [ http://issues.apache.org/jira/browse/TUSCANY-834?page=all ] Luciano Resende updated TUSCANY-834: Attachment: tuscany834.lresende.20061012.txt Patch adding the junit version reference to java/das/rdb/pom.xml Missing version information for junit plugin in das pom.xml --- Key: TUSCANY-834 URL: http://issues.apache.org/jira/browse/TUSCANY-834 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Affects Versions: Java-M2 Reporter: Luciano Resende Assigned To: Luciano Resende Priority: Minor Fix For: Java-M2 Attachments: tuscany834.lresende.20061012.txt DAS RDB pom has no version information for junit dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/ Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/ software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Updated: (TUSCANY-834) Missing version information for junit plugin in das pom.xml
It's important that all dependencies from the source distribution are to released artifacts. This does not apply just to the junit version but to the pom as a whole. If you can't rely on the parent pom being there (which is the implication of you saying that the version won't be there) then you can't rely on the das parent pom being there either and you would need to remove the parent dependency all together; otherwise you are relying on the parent and in which case you might as well avoid the duplication of the junit version info. -- Jeremy On Oct 12, 2006, at 4:37 PM, Luciano Resende wrote: The problem here was that if I generate the source distribution by doing a export of das/rdb and then update the pom to point to parent pom, these default values won't be there and compilation will fail. I think what you said is true if I export the whole das subtree as part of the source distribution, then default values will be available. - Luciano On 10/12/06, Jeremy Boynes [EMAIL PROTECTED] wrote: You normally don't need or want to do this - the information is inherited from the parent (das) pom.xml's dependencyManagement section which enables it to be specified in one place and shared between all modules. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
