[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737606#action_12737606
]
Dag H. Wanvik commented on DERBY-4267:
--------------------------------------
Thanks for doing this, Kristian!
I am new to maven, but I read this helpful intro:
http://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html
and tried to understand our *.pom's, I also downloaded Maven and tried an "mvn
install" (NOTE: this had to be done from inside the maven2 directory, I found),
and then it seemed to work: I found the Derby artifacts in my ~/.m2 directory
structure.
Inspecting the poms, I only found one item which seemed to contradict the
intro: The module poms lack <version>, which the intro claim is mandatory, but
I did not see any error message, so I suppose it is inherited from the top pom,
then?
Another question: We specifiy <filtering> to true; is that needed for Derby? It
seems potentially dangerous in that
strings inside jars could be replaced?
It seems to me the dependencies from locale jars to derby.jar should be
included.
> Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
> --------------------------------------------------------------------------
>
> Key: DERBY-4267
> URL: https://issues.apache.org/jira/browse/DERBY-4267
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.5.1.1, 10.6.0.0
> Reporter: H.-Dirk Schmitt
> Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat,
> maven2.zip
>
>
> Only 10.4.2.0 and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
